01
Scope
Define requirements, fixed price, and delivery date.
You get: written scope, fixed quote, delivery date.
How we work
Four stages.
Fixed at each one.
Most builds go wrong in the gap between what was agreed and what was assumed. Each stage below ends in something written down, so there is no gap to fall into.
02
Architect
Map the data model, permissions, and user flows.
You get: schema, flow map, wireframes.
03
Build
Design and code advance in weekly reviewable increments.
You get: a staging URL, updated every week.
04
Ship and hand over
Deploy, hand over all assets, and provide 30 days of support.
You get: production deploy, repo access, docs, 30 days of support.
When plans change
Fixed scope,
not fixed reality.
Scope is agreed up front, and briefs still change. Here is exactly what happens when they do, so it is a known process rather than an awkward conversation.
- 01
You tell us, or we tell you
Whoever spots the change raises it the same week. Nothing gets quietly absorbed into the build and billed later.
- 02
We re-quote before we work
A written note: what it adds, what it costs, what it moves. You approve it or you do not, and the original scope stands either way.
- 03
The date moves, or the scope does
One of the two has to give. We will tell you which we recommend, and we will not promise both.
Start a build
Ready to
scope something?
The first call is the scoping call. Bring the problem, and you'll leave with a view on what it takes to solve.