Delivery standards
How we deliver, step by step
These are the standards we hold ourselves to on every project. You are welcome to check us against them.
How will you keep me informed?
A weekly written update covering what was done, what is next, and anything blocking progress. Decisions are recorded in a shared log so nobody has to rely on memory.
Who owns the work?
You do, from day one: source code, designs, domains, developer accounts, signing keys and data. We work inside your accounts wherever possible.
How do you test?
Automated tests for important logic, manual testing on real phones and browsers, and accessibility checks with keyboard, screen readers and zoom. Each test version comes with a short note of what was checked.
What about security?
Passwords and keys never go into code. We keep libraries up to date, give people only the access they need, and use encrypted connections. We follow recognised guidance such as OWASP and NCSC advice; we do not claim certifications we do not hold.
What do I get at handover?
- A plain-English overview of how it all fits together
- Instructions to run, build and deploy
- A list of known limitations
- Account and access summary
- A walkthrough call with your team
Launch-readiness checklist
Use this for any product, ours or not. Ticks are remembered in this browser only if you accept optional storage.
Want these standards on your project?
Start a conversation