Method
Secure the pitch.
Then move.
Five stages, each with an agreed exit point. You always know which stage you are on and what has to be true to leave it.
Survey
We listen, read what already exists and write a short brief in your words. Exit point: you agree the brief describes the problem.
Footing
Flows and prototypes. We test the main path before building it. Exit point: designs signed off for the first release only.
Traverse
Build in short cycles with installable test versions. Exit point: the main task works on the agreed devices and known issues are listed.
Summit check
Release preparation: listings, privacy, accounts, rollback. Exit point: you approve submission or go-live.
Descent
The often-forgotten half. Updates, support routes, handover notes. Exit point: you can run the product without us if you choose.
In place of trophies
Criteria we hold our own work to
Readable
Text meets WCAG contrast guidance; the main task works with keyboard and screen reader.
Honest under failure
When a form, network or server fails, the user is told and their work is kept.
Owned by you
Repositories, accounts and design files sit with your organisation from the start.
Measured on real devices
We test on small, slow and older hardware, not only on our own screens.
Documented
Handover notes explain how to build, release and recover, in plain language.
Scoped aloud
What is out of scope is written down as clearly as what is in.
These are commitments to check, not claims of results. If a project misses one, we will tell you which and why.
Local planning aid - not a quote, not automated advice
Release milestone selector
Pick the stage your product has reached and tick what is genuinely true. Nothing leaves your browser and nothing is saved; refresh to clear.