Standards
What you can hold us to.
These are not aspirations. They are the commitments written into how every project is run, and you are welcome to quote them back to us.
Scope
Every project starts with a written scope: purpose, users, what is in, what is out, known risks and how changes are agreed. Changes are logged with their effect on time and cost before work starts on them.
Communication
One weekly written note in plain English covering progress, next steps, blockers and decisions needed. Calls during working hours when useful, always followed by a written summary.
Working builds
Test builds you can install or open yourself, at least every two weeks during active development. You see real behaviour, including the unfinished parts, labelled honestly.
Quality
Code review on every change, automated tests where they protect important behaviour, and manual testing on a range of real devices and browsers before release.
Accessibility
Designed and checked to WCAG 2.2 AA: keyboard operation, screen reader labels, contrast, zoom and reduced motion. Known gaps documented, not hidden.
Security basics
Least-privilege access, secrets kept out of code, dependencies updated, personal data minimised. We are not a security certification body and will not claim to be.
Ownership
Repositories, store accounts, domains and hosting sit in your name. At handover you receive documentation, credentials and a walkthrough.
Honesty
If something will be late, you hear it as soon as we know. If we are the wrong studio for a piece of work, we will say so.