How it works
Map it. Build it. Leave.
Three stages, and it is the third one that makes this different from renting software. We finish, and then we leave.
Map
A day with your team, writing down how the work actually moves rather than how the org chart says it does. We are looking for the steps that only exist in somebody’s head and the workarounds people have stopped noticing.
You keep the map either way. If you never build anything with us it is still the clearest description of your own operation you have ever had written down.
Build
We build to the map, screen by screen, on a private URL you can watch from the first week. Nothing gets added because a template had a slot for it, and nothing gets left out because the plan said so.
The price was fixed after the map, so scope conversations happen before anyone is invested rather than halfway through.
Hand over
It goes live on your own hosting account with your data in it and the code in your name. We train the people who will use it, then we get out of the way.
When you want changes later, we collect them and do them in a batch, rather than billing you every month to exist.
Handover
The test is whether it survives us.
Plenty of agencies say you own the software and then host it on their account, under their domain, with the code in their repository. You own it in the way you own a rented flat.
The real test is simple: if we vanished tomorrow, would it keep running, and could another developer pick it up? Everything on this list exists to make the answer yes.
- The code, in a repository in your name
- The data, in a format you can read without us
- Hosting on your own Cloudflare account, billed to you directly
- The domain, in your name
- A training session with the people who will use it daily
- Written notes on how the thing is put together
Common questions
What the process actually feels like.
What actually happens on the map day?
We sit with the people who do the work, not just the owner, and write down how a job moves from first contact to paid. We are listening for the parts that only live in somebody's head, the steps everyone does differently, and the spreadsheet sitting beside the official system. You keep the map whether or not you build with us.
Do I see it before it is finished?
Continuously. It goes up on a private URL from the first week and you watch it come together screen by screen. Nothing is revealed at the end, because software revealed at the end is software with a month of wrong assumptions baked into it.
What does handover actually mean?
The code sits in a repository in your name, the data is in a format you can read without us, and it runs on your own Cloudflare account billed directly to you. If we disappeared entirely it would keep running, and another developer could pick it up. That is the test.
Why do you leave instead of offering support?
Because a monthly fee for software you already own is exactly the arrangement we are arguing against on every other page of this site. Changes get collected and done in a batch when you want them. If we sold you a retainer we would be the thing we criticise.
What if something breaks after you have gone?
Faults in what we built get fixed, and that does not run out. What is batched is new work: changes, additions and things you thought of later. There is a difference between a bug and a feature request and we do not pretend otherwise.
How involved do I need to be?
Heavily for the map day, lightly after that. Expect a short call each week to look at what has been built and correct anything that has drifted. Projects go wrong when the client disappears for six weeks, not when they ask too many questions.
Where to next
Bring your worst spreadsheet.
A discovery call runs about thirty minutes. We map how you actually work, tell you honestly whether a bespoke build is worth it for a business your size, and add up what you would stop paying.