How it works
From prototype
to production. Provably.
Nine steps, one free. You decide what the app should do. We do the rest, and show our work.
-
0
Your free assessment
Connect your app's code: a GitHub link, or a zip. We read it and show you what it does, what it needs to be production-ready, and a price range. Every assessment is checked by a person before you see it.
You connect your codeYou get the assessment, and a summary for your customer -
1
Your prototype
The app you built shows us what it should do. That's all we take from it: no accounts, no data, no secrets cross over.
-
2
Getting started
We take your code at a fixed version. You give us a test login for each kind of user, and answer what the code can't tell us, like how many people will use it.
You answer a few questions -
3
Reading your app
We write down every rule your app follows, and every question it raises. Nothing is decided yet.
You get your rulebook -
4
Agreeing the rules
Area by area, you accept what's right and question what isn't. Signing off an area fixes what we'll build. Your customer co-signs the rules that matter most to them.
You sign off each areaYou get a fixed price -
5
Recording how it behaves
We run your prototype as each kind of user and record what it does. You confirm each recording is right. They become the standard the new app is checked against.
You confirm the recordings -
6
Rebuilding
We rebuild your app properly, piece by piece, on our standard platform. Every piece is reviewed by an engineer and checked against the recordings.
You see progress as it happens -
7
Going live
Final checks and your sign-off. Then the new app goes live with fresh accounts and data, on its own instance.
You give the final sign-offYou get a governance pack for your customer's auditors -
8
Live and improving
We run it: monitoring, backups, support. Ask for changes in plain words. Each one goes through a short version of the same steps, with the same proof.
You ask for changesYou get proven releases
What makes it different
People decide.
Machines do the legwork.
Your intent, in writing
Nothing is built until you've said it's right. The rulebook is yours to read, question and sign.
Two human gates
An engineer approves every piece of work before it starts, and reviews it before it's accepted. Always.
Proof, not promises
Every rule is checked. Every change is tested before it reaches your customer. The evidence is kept.