Software shaped like your process, not a template

Yes. We start with a paid review of code, database, plugins and hosting, and give you a written report with risks and a prioritised plan before any development begins.

Clearly scoped work is quoted as a fixed price. Continuous development runs on a monthly retainer with a transparent hour report. We tell you which one fits.

You do, from the first commit. It lives in your Git repository with documentation that lets another team take over.

There is no list price, but the shape is predictable: a focused internal tool that solves one process is a few weeks of work, a system several departments depend on is months, and anything meant to replace an ERP is a project you should think very hard about. We quote after a paid discovery, not before — a number given without seeing your data is a guess dressed as an offer.

You keep working. The code is in your repository, the stack is deliberately ordinary — Node, React, a relational database — and the deployment is scripted and documented, so any competent agency can pick it up. That is also why we refuse to build clever things: cleverness is a lock-in you only notice once we are gone. Ask every vendor this question and take the vague answers seriously.

Almost always, and you should buy it wherever your process is not the thing you compete on. Accounting, payroll, e-mail — buy. The one workflow your company does differently and better than everyone else is exactly where a template forces you to become average. Build there, buy everywhere else. Anyone selling you custom software for both is selling hours.

We aim to put something real in front of the people who will use it within the first few weeks, covering the single process that hurts most rather than the full feature list. It will be incomplete on purpose. Software your team has actually touched for a month tells you more about what to build next than any specification workshop ever will.