Discovery before writing code
We map the real process, not the documented one. They almost always differ, and that's where the value is.
Service
Software that adapts to your process, not the other way round.
There comes a point where the shared spreadsheet stops coping and no SaaS fits without forcing you to change how you work. That's when building makes sense: a tool that does exactly what you do, without the ninety features you'd never use.
- 4–10 weeks
- First version
- Custom project
- Scope
- Your code
- Ownership
Why it matters
Bending the business to fit generic software has a cost that never shows up on the invoice: processes twisted to fit the product, data in three places and people acting as the bridge between tools. Building custom is only justified when that cost is already higher than the development.
Scope
What's included
A first version with the smallest useful scope
The least product that already works for you in production. It grows with real use, not assumptions.
An interface built for daily users
If your team will have it open eight hours a day, speed and shortcuts matter more than looks.
Authentication and access control
Who sees what and who can change what, defined from the start and not patched later.
Code, repository and deployment in your name
Everything stays on your infrastructure. You can change providers without renegotiating anything.
Technical documentation
Architecture, decisions and how to run it, so another team can pick it up.
Process
How we do it
- 01
Discovery
Sessions with the people who do the work today. We come out with the process mapped and the minimum scope agreed.
- 02
Clickable prototype
You see and use the interface before the logic exists. Fixing things here costs hours, not weeks.
- 03
Build module by module
Each module goes live and gets used before the next one starts.
- 04
Handover
Access, documentation and team training, with agreed support while things settle.
Stack
What we build it with
Technologies with large communities and open documentation, so finding another developer never becomes your problem.
- Next.js
- React
- TypeScript
- Node.js
- PostgreSQL
- Supabase
- Docker
- Vercel
FAQ
Before you hire us
When is custom worth it, and when is a SaaS better?
If a product covers 80% of what you need, buy it: it's cheaper and already proven. Custom is justified when your process is your competitive advantage, when no product fits without bending it, or when per-user licences already cost more than building.
Who maintains it afterwards?
You can, we can under a support agreement, or another team can. That's why the code, repository and documentation are in your name from day one and we use standard technologies: we don't want you depending on us for lack of alternatives.
How long does a first version take?
Between four and ten weeks depending on scope. We work in modules, so you start using the first part before the project ends. A longer timeline usually means the initial scope is too ambitious.
Related
Often combined with
Is this what you need?
Tell us about your case in four questions. We'll tell you honestly whether this service solves it, whether another one fits better, or whether we're not right for you.