[ 01 — PROCESS ]
Five stages. The detail changes depending on what we are building; the shape does not, because it is what keeps a project honest.
01 — Discover
We sit with the people doing the job and map what actually happens, including the workarounds. The workarounds are usually where the real requirements are hiding.
[ 02 — IN DETAIL ]
What each stage produces
A stage is not finished because time passed. It is finished when the thing it was supposed to produce exists.
- 01
Discover
3–10 daysWe sit with the people doing the job and map what actually happens, including the workarounds. The workarounds are usually where the real requirements are hiding.
You getA written map of the process, the problems ranked by cost, and a recommendation — sometimes to do nothing.
- 02
Design
1–2 weeksScreens and data model on paper first, reviewed with the people who will use them. Changing a design costs minutes; changing a built system costs weeks.
You getA clickable prototype of the main flows, the data model, and a fixed-price proposal with a date.
- 03
Build
4–12 weeksWorking software every two weeks, on a URL you can open. You steer with what you can see rather than with what you imagined in a meeting.
You getA staging environment that is always current, a demo every fortnight, and a changelog.
- 04
Deploy
1 weekData migrated and reconciled, the team trained, monitoring and backups on. We run the old and new side by side until the numbers agree.
You getA live system, a trained team, documentation, and a tested restore.
- 05
Run
ongoing, optionalPatching, backups, monitoring and a set number of change hours each month. Or a clean handover with documentation if you would rather run it yourselves.
You getAn agreed response time, a monthly report, and someone who answers the phone.
[ 03 — ENGAGEMENT ]
Three ways to work with us
We will tell you which one fits. It is usually fixed scope to start and a retainer afterwards, but not always.
Fixed scope
A defined piece of work for a defined price. Best when the problem is clear and the finish line is obvious. Changes are priced in writing before they happen.
Retainer
A monthly block of our time for ongoing work: running systems, a steady stream of changes, or a long build. Best when the work is continuous rather than a project.
Hourly
For short, unpredictable work — a rescue, an audit, a second opinion. Honest, but the least comfortable for both sides on anything long.
[ 04 — FAQ ]
How we work: questions people ask
Let's build something.
Tell us what is slowing your business down. We will tell you what we would build, what it costs and how long it takes — before you commit to anything.