Write it down plainly
Before anything is designed, the ambition is stated in one page, in plain language, with the constraint that shapes it. Once it is written, everyone builds toward the same thing.
04.0Approach
A fold is a decision.
A crease is permanent. Whatever the first fold decides, every later fold builds on — which is why we spend the first part of a project deciding slowly and the rest of it moving quickly.
04.1The method
Five stages
Draw the boundary
Scope is a fence with a gate. We name what is in, what sits outside for now, and what would change the price — so the build moves fast inside a boundary everyone trusts.
Build the spine first
The data model and the access rules come before a single screen. Schemas are expensive to change once real records exist; buttons are cheap.
Prove it against reality
Tests, then a live run against the real API with real credentials. Every feature earns its place by working where it will actually live.
Hand it over properly
Source, schema, migrations and the reasoning behind every decision. The measure of a hand-over is that your own team can take it anywhere.
04.2Convictions
Four things we stand on
01
Every number is checked
Every figure we put in front of a client has been measured — counted at the source, and verified twice.
02
Say the important part early
What we flag in week one becomes a decision made together, while every option is still open.
03
Built to be owned
We build assuming your team will one day run this themselves. That assumption raises how everything is written.
04
Written, then confirmed
If a requirement can be read two ways, we pick one, write it down, and get it confirmed.