Method · five gates
Nothing passes a gate on trust
We have no awards to show you. What we can show is how work is checked before it moves to the next station.
Map agreed
A diagram of the process, each step marked manual, checklist or software. You sign it off before design starts.
Flows walked
Every key task is walked through on paper or prototype with someone who actually does it.
Build checked
Features compared against the map, including the error and empty states nobody asks for.
Release rehearsed
The release checklist is run on a test build before the real one.
Handed over
Code, accounts and notes are in your name, so you are never locked to us.
When we say no to automation
We recommend keeping a step manual when:
- it needs judgement that changes case by case;
- it happens so rarely that building it costs more than doing it;
- a mistake would be serious and hard to undo;
- the rules behind it are not yet stable.
That advice sometimes makes a project smaller. That is fine.
Quality criteria you can hold us to
Accessibility
Keyboard reachable controls, visible focus, readable contrast and labelled form fields.
Phones first
Checked at small widths, without sideways scrolling.
Honest states
Errors say what went wrong and keep the user's input.
Ownership
You hold the accounts, domains and source.
Plain records
Decisions written down in language your team can read.
No invented numbers
Estimates are labelled as estimates and explained.