Custom Development
We build the product and then run it. That changes what we design: nothing ships that we would not be willing to be paged for at 3am.
- Product & platform engineering
- API and data architecture
- Migration from legacy stacks
Sound familiar?
The prototype became the product
Something built to prove an idea is now carrying real customers, and every change breaks two things. Rebuilding the foundation without stopping the business is a specific skill.
Off-the-shelf almost fits
You are paying for a platform and then paying again for the workarounds. At some point the workarounds cost more than the software would have.
Nobody owns the whole picture
The agency finished and left, the host points at the code, the developer points at the server. There is no one who can answer for the system end to end.
Scope of work
Product & platform engineering
Web applications, internal tools, customer portals and the APIs behind them. TypeScript, Next.js, Node, Postgres — chosen because they are boring and well understood, not because they are new.
Data & API architecture
The schema is the part you cannot cheaply change later, so it gets designed first and explicitly. Migrations are versioned, reversible and rehearsed against a copy of production.
Integrations
Payment providers, government and banking APIs, messaging, accounting. Including the ones with bad documentation, which is most of them.
Legacy migration
Moving a running system without a big-bang cutover: run both, mirror the writes, move traffic gradually, keep the way back open until the last day.
From first call to steady state.
Scope
A short engagement that ends in a written plan: what gets built, in what order, what it costs, and what we deliberately are not doing. Yours to keep either way.
Build
Two-week increments against a staging environment you can open at any time. No demo day theatre — you watch it come up.
Launch
Deployed on infrastructure we operate, with monitoring and backups configured before the first real user arrives.
Operate
It keeps running, and when something breaks the same people who wrote it are the ones fixing it.
Do you work with our existing codebase?
Yes. Most engagements start that way. The first step is a read-through and a written assessment of what is worth keeping.
Who owns the code?
You do, from the first commit, in your own repository. There is no lock-in clause and no licence to buy back.
Can we host it ourselves?
Yes. We deploy it wherever you want, including your own cloud account. Hosting with us is an option, never a condition.