How we work
You always know what happens next
The same 7 steps on every project, whatever its size. Publishing them is deliberate — a studio that cannot describe its own process usually does not have one.
- 01
Discovery call
30 minutesWe ask four things: what the problem is, when you need it, roughly what the budget is, and who signs off. If we are not the right fit, we say so on the call.
Your part
Thirty minutes and honest answers.
- 02
Written scope
2 working days after the discovery callDeliverables, explicit exclusions, assumptions, timeline and price — in writing. The exclusions matter as much as the inclusions: most project disputes come from something both sides assumed was covered.
Your part
A read-through, and questions about anything unclear.
- 03
Build with weekly demos
Every week, same slotA staging URL goes live in week one and stays live. You watch it being built, including the weeks when progress was slow. Changes get priced in a change order before they are built.
Your part
Thirty minutes a week and feedback inside three working days.
- 04
Independent QA pass
Before launchA separate test pass against the written scope — browsers and phones, the core flows, and a re-test of every fix before it ships. This is done by a different person from the one who built it.
Your part
A short walkthrough of the features being tested.
- 05
Security baseline review
Before launchOur security specialist checks configuration and common web risks against a written baseline — HTTPS, headers, dependencies, secrets, access controls — and fixes what the review finds before anything goes live.
Your part
Admin or hosting access where the review needs it.
- 06
Documented handover
On completionRepository access, deployment documentation, environment configuration, a recorded walkthrough and — where the project warrants it — role manuals and a QA pack your team can re-run.
Your part
Final payment. The code is yours outright.
- 07
After launch
30 days and beyond30 days of bug-fix cover against the written scope, then a monthly Care plan or a written change order — your choice, on paper.
Your part
Tell us how it behaves in the real world.
Two things we will not do
Quote on the first call
A number given before we understand the problem is a guess, and guesses get corrected later — usually in an uncomfortable conversation. You get a written scope first, always.
Take a project we are wrong for
If your problem needs a specialism we do not have, or a platform we do not know, we will say so on the call and suggest where to look instead. It costs us one project and saves you a bad one.