Delivery standards
How do you work?
In the open, in small steps, with everything written down.
These are the standards we hold ourselves to on every project. They are promises about behaviour, not certificates, and you can check each one as we go.
How do you handle what you don't know?
Every project keeps an assumptions list, sorted into known, hunch and unknown. Dangerous unknowns get tested first, with the cheapest experiment that could answer them.
When is something “done”?
When it is built, reviewed by a second person, tested, checked for accessibility, demonstrated to you and documented. Until then we call it in progress.
How do you test?
Automated tests on every change, end-to-end tests for the journeys that matter most, and manual testing on a list of devices and browsers agreed with you in advance.
What accessibility standard?
WCAG 2.2 level AA as our design and test target. Anything we could not meet is listed in the handover with a suggested fix.
And security?
No secrets in code, minimal access rights, minimal personal data, regular dependency checks, and access removed for anyone who leaves the project.
How will I know what's happening?
A short written note after every cycle: what shipped, what slipped and why, what we learned, and what we need you to decide.
What happens at the end?
Code, designs, accounts and documents are handed to you, in your name, complete enough for another team to continue without us.
Sort your own unknowns?
Write down what you believe about your idea. Then be honest: is each one known, a hunch, or genuinely unknown? It is the first exercise we run with every founder.
Kept on this device only if you accept optional storage.