The spreadsheet is the system
A key company process runs on a file that one person understands. That person goes on holiday and everyone hopes nothing needs changing.
CUSTOM SYSTEMS · CRM · B2B PANELS
A process no off-the-shelf tool
will ever handle.
First there was a spreadsheet. Then three tools, none of which talk to the others. We design and build custom systems — CRMs, B2B panels, web applications and integrations — shaped around how your team actually works.
- Laravel, Vue and React — no licences that lock you in
- The code and the repository are handed over to you
- Development and maintenance after launch, not just a handover
FROM OUR PROJECTS
- 47
- integrations in one B2B system for a packaging manufacturer
- 92%
- of our clients stay with us for more than three years
- 2016
- the year our longest client relationship began
- 900+
- projects delivered since 2013
SOUND FAMILIAR?
The system you do not have
costs you too.
Three tools, no conversation
CRM in one place, orders in another, the warehouse in a third. Data moves between them through a human being, copy-paste and file exports.
A report takes two days
Every time the board asks for numbers, someone sits down and assembles them by hand from four sources. By the time the report is ready it is already out of date.
Salespeople work from memory
The history of contact with a customer lives in one person's inbox. When they leave, the knowledge leaves with them.
The off-the-shelf tool almost fits
You pay a subscription for a system you use 30% of, and you work around its limits with side procedures. That "almost" costs more than it looks.
The previous supplier vanished
The system runs, but nobody knows how it is built, there is no documentation, and every change requires archaeology in the codebase.
A custom system makes sense when the process is your advantage — not when you simply want something of your own. If an off-the-shelf tool would be enough, we will tell you so on the first call.
WHAT WE BUILD
Tools written around a process, not around a feature list.
01
CRM and sales systems
Contact history, pipeline, quotes, orders and settlements in one place — arranged around your process rather than around what the vendor of an off-the-shelf CRM decided was standard.
- Pipeline and contact history
- Quotes and orders
- Role and team permissions
- Reports assembled automatically
02
B2B panels and customer portals
A place where a contractor checks an order status, downloads documents, files a complaint or reorders on their own — instead of calling your support team.
- Contractor self-service
- Documents and settlements
- Ordering and reordering
- Multi-level company structures
03
Web applications and workflow
Document flows, approvals, production schedules, booking systems and internal operational tools. Anywhere the process is too specific to buy off the shelf.
- Document flow and approvals
- Scheduling and bookings
- Integrations with ERP and external systems
- Operational panels and dashboards
SCOPE AND TIMING
How we usually split a project like this.
A custom system cannot be quoted honestly before the process is understood. So we split the project into stages, each of which leaves you with a concrete result and a real decision to make.
Workshop and scope
1–2 weeks
We understand the process and turn it into a documented scope.
- Workshop with the people who run the process
- Process and role map
- Prioritised feature list
- Technical direction and risks
- Quote and stage schedule
First working version
2–4 months
The shortest path to a system people can actually use.
- Interface and flow design
- The key process end to end
- Roles and permissions
- Integrations needed for launch
- Testing and production deployment
Development and operations
ongoing
The system grows with the company instead of freezing on handover day.
- Further modules in cycles
- Monitoring and a contractual response time
- Integration development
- Optimisation against real usage
- 12 months of warranty on delivered features
After the first stage you hold a documented scope, a quote and a schedule — and every right to take them elsewhere.
TECHNOLOGY AND PRINCIPLES
What it runs on, and what you can hold us to.
We do not have one technology for everything. We pick tools for the job, then stick to a handful of principles that protect you even if the relationship ends.
Backend
- PHP
- Laravel
- Symfony
- Node.js
- REST API
- GraphQL
Frontend
- Vue
- Nuxt
- React
- TypeScript
- Tailwind CSS
Data
- MySQL
- PostgreSQL
- Redis
- Elasticsearch
- Data migrations
Security and access
- SSO sign-in
- Roles and permissions
- Two-factor authentication
- Change logs
- GDPR
Deployment and operations
- GitLab CI/CD
- Staging environments
- 24/7 monitoring
- Backups
- SUPPORT agreements
How we work
- The code belongs to the client
- We hand over the repository
- Technical documentation
- 12 months of warranty
- NDA on request
We do not sell licences for an in-house engine and we do not lock you into our infrastructure. If you stay with us, it is by choice.
OUR WORK
Systems running in production.
From CRMs to systems for public administration. Selected projects we develop together with our clients' teams.
CT Poland
CMS · CRM · Services · Custom
Custom solution combining CMS, CRM elements and service process support.
MZDW
Public administration · CMS · Custom
CMS system for public administration, focused on structured publishing and stable content management.
Mavibo
E-commerce · PrestaShop · B2B · Manufacturing
Sales platform for a manufacturer, combining e-commerce with B2B customer processes.
OR START LIGHTER
Workshop and scope estimate in 5 working days
Not ready to commit to a whole system? Let's start with one stage. We sit down with the people who actually run the process, break it into roles and steps, and you walk away with a documented scope, a quote and a schedule.
- A workshop with your team, not just the board
- A documented scope and a prioritised feature list
- The document is yours — including if you take it elsewhere
QUESTIONS
What people ask us most often.
How long does it take to build a custom system?
The workshop and scope documentation take 1–2 weeks. A first working version usually takes 2–4 months, depending on the number of roles, integrations and how far the process departs from the standard. After that we develop the system in stages rather than holding the launch until every feature is finished.
How do you quote a system that does not exist yet?
We do not quote it from a brief. We start with a workshop that breaks the process down into roles, steps and data. The output is a documented scope, a prioritised feature list and a quote per stage. That document belongs to you — you can use it to compare offers from other suppliers.
What if the scope changes along the way?
We assume it will, and that is normal. We work in stages, so changes enter when the next stage is planned rather than as emergency rework. Changes with a material effect on cost or deadline are quoted separately before we start them.
Who owns the code and the data?
The client. After launch we hand over the repository, the technical documentation and the infrastructure access. We do not sell licences for an in-house engine and we do not keep the system on infrastructure you cannot reach.
Will you take over a system from another supplier?
Yes. We start with an audit of the code, the dependencies and the infrastructure to gauge the real risk. After the audit we say plainly whether the system is worth developing or whether rewriting the key part will cost less. Sometimes we recommend the latter.
How is this different from an off-the-shelf CRM subscription?
An off-the-shelf system is cheaper to start with and available sooner — if your process fits its assumptions, it is the better choice and we will say so. A custom one makes sense when the process is a company advantage, when you work around the tool's limits with side procedures, or when licence costs grow with every user.
What happens after launch?
Delivered features carry 12 months of warranty. Beyond that we offer SUPPORT agreements with monitoring and a guaranteed response time. 92% of our clients stay with us for more than three years and 24% for over ten — our longest relationship has run unbroken since 2016.
Do you sign NDAs?
Yes, and before we discuss details if that is what you need. Business processes can be sensitive, so we treat this as a normal part of the conversation rather than an exception that needs justifying.
LET'S TALK
Describe the process, not a specification.
We do not need a finished requirements document. Just tell us who should use it, what goes wrong today and how you will know it worked. We will pull the rest out with questions.