Custom software, built around how your company works
When nothing on the market fits and bending the company around the software costs more than the software, you build to measure. We build business applications that follow your real process, not one invented by somebody else.
When it is worth it and when it is not
We will say it plainly: most of the time it is not. If you need invoicing, accounting or an ordinary CRM, buy a €30-a-month subscription and you are done. Anything we build would be more expensive and less complete.
It is worth it when your process is the difference between you and your competitors. When you have a way of pricing, allocating crews, checking goods or tracking jobs that no standard product understands — and that your people currently keep in spreadsheets nobody fully understands any more.
It is also worth it when you pay for ten modules to use two, or when moving data between three systems that do not talk to each other consumes a full-time person.
We start with the process, not the screens
The first phase produces no code. We sit with the people doing the work and map the flow as it actually happens, exceptions included — the case that comes up three times a year and that everyone resolves over the phone.
Those exceptions are why software rollouts fail. A system that covers 95% of cases and has nothing to say about the rest is a system people route around, and six months later you are back in spreadsheets with an extra invoice to show for it.
Delivered in modules, not in one piece
We do not build for a year and deliver at the end. The first module — the one that hurts most — reaches production in two to three months and gets used by real people. What we learn there changes what we build next.
That gives you two things. You see results early, so you can stop the project if it is going the wrong way, losing one instalment rather than a year. And your people adapt gradually instead of being moved to a new system overnight.
- Phase 1: map the process and decide the first module
- Phase 2: first module in production, used by a real team
- Phase 3: extend based on what was learned, not what was assumed
- Phase 4: migrate the old data and retire the spreadsheets
Integrating with what you already run
New software does not live alone. It has to talk to accounting, to invoicing, to the ERP, to the till, sometimes to machines speaking protocols older than the company.
We integrate over APIs where they exist and through controlled import-export where they do not. When a vendor refuses access, we say so at the quote stage, not after the contract is signed.
What you get
- Process mapThe document showing how the company works today, exceptions included.
- The application, in modulesFirst module in production in 2-3 months, the rest in turn.
- Roles and permissionsWho sees what, who can approve what, with an audit trail.
- IntegrationsWith the systems you already run, over API or controlled import.
- Data migrationWhat you hold in spreadsheets or the old system, moved and verified.
- Training and documentationFor the people using it daily, not only for IT.
What we build it with
- Java
- Spring Boot
- Node.js
- .NET
- Python
- PostgreSQL
- Redis
- Elasticsearch
- Next.js
- React
- TypeScript
- Docker
- Linux
- GitHub Actions
What custom software costs
from €599
Price follows the number of workflows, not the number of screens. A well-scoped first module starts at the entry package; an application with several roles, integrations and data migration falls into the higher ones. You get a firm price for the first module after the process mapping, and the rest is quoted as it becomes clear.
Frequently asked questions
How do I know I need custom software rather than an off-the-shelf product?
If your process is standard — invoicing, accounting, an ordinary CRM — buy a subscription; it is cheaper than anything we would build. Custom becomes worth it when the way you work is your competitive advantage, or when you run operations out of spreadsheets nobody fully controls any more.
How long until I see something working?
The first module reaches production in 2-3 months and is used by real people, not demonstrated in a slide deck. The rest is built on what we learn from that use.
What happens to the data in the old system?
We migrate and verify it before the switch. Migration is its own phase, with validation and the option to run both systems in parallel for a while.
Do I become dependent on you?
The code is yours from day one, in your repository, with a runbook. The monthly retainer is for hosting, maintenance and continued development — not for the right to use what you paid for.
Can you integrate with our accounting software?
If it has an API, yes. If it does not, we do controlled import-export with validation. We check this before quoting, so nobody discovers after signing that the vendor will not grant access.
Tell us what you want to build
Three steps, a few minutes. You get a code to follow your request and the project's progress in real time.