How a build works.
We scope the build, learn your workflow with you, and build you a working demo of your system, all free, before you commit to anything. If it's not worth building, we'll say so.
Scope
We sit with the people who do the work and learn how it actually runs — not from a spec handed over at the start. You get a written scope, a fixed price and a working demo of your system before you commit to anything.
Build
Fixed scope, fixed price, half paid on start. We keep learning how you operate over the course of the build, so the system fits the way the work actually runs. You see it grow — no big reveal at the end.
Go live, and after
An acceptance certificate signed at go-live: you agree the system does what the scope says, and the second half is due. Then daily backups, continued monitoring, and the person who built it a phone call away.
No surprises in the invoice.
Fixed scope, fixed price, half on start and half on completion. An acceptance certificate signed at go-live. The price you agree at scoping is the price you pay, because the scope is written down before we start, not discovered as we go.
No per-seat fee. Hire ten people next year and the licence costs the same. Only usage-based costs like SMS, mapping or AI calls vary, and those are passed through at cost, not marked up into a subscription.
What you own at the end: everything. The system and its data are yours. It isn't our product rented to you — it's your system, built once, that keeps adding value as the business changes.
The hard questions.
The ones people actually want to ask a two-person studio, answered straight.
What happens if you get hit by a bus?
A fair question, and one we would ask too. There are two of us, so no single bus takes the knowledge with it. Beyond that: every system we build lives in its own repository, escrow-ready, with a documented handover, and you own the code and the data outright. The worst case is finding someone new to look after a system you already own — not losing the system.
What if it goes wrong?
The scope we both sign says what the system must do, and the second half of the price is not due until it does it. The acceptance certificate at go-live is you agreeing that it does. After go-live, if something breaks, you ring the person who built it and we start fixing it within the hour. And if the honest answer at scoping is that the build is not worth doing, we say so before you have spent anything.
Who owns the system?
You do. The system and its data are yours — the code, the database and everything in it. We do not licence it back to you, and there is no per-seat fee: hire ten people next year and the licence costs the same.
What is the three-stage safety audit?
Three checks, and the third never stops. One: the code itself. We review it and run automated checks across it and every third-party package it depends on, looking for known weaknesses and for the ordinary mistakes that matter — data or keys ending up somewhere they should not be, a page that forgets who is allowed to see it. Two: the running system. Before you go live we scan it the way an outsider would probe it, across the log-in, the forms and anything else reachable from the internet, and fix what that turns up while nobody else has found it. Three: monitoring, from go-live onwards. Errors report themselves to us, we watch for newly published weaknesses in the packages your system uses, and we are alerted if it goes down — which is why you will usually hear about a problem from us first.
What happens after go-live?
The system is backed up daily, it has been through the safety audit above, and the third stage of that audit keeps running. Support means ringing the person who built it, not a ticket queue and not an account manager, and we start fixing any issue within the hour. Because we learned how you operate during the build, a fix takes minutes rather than a week of somebody getting up to speed.