01 · Ownership
Source code, design files, store accounts, domains and hosting are registered to you. We are given access, and that access is removed cleanly when work ends.
Handling
These standards apply to every engagement. If we ever need to set one aside, we explain why in writing first.
Source code, design files, store accounts, domains and hosting are registered to you. We are given access, and that access is removed cleanly when work ends.
A working build every two weeks during active development, with a short note of what changed and what to test. No long silences followed by a big reveal.
Estimates are ranges with written assumptions. When an assumption changes, we tell you and agree the effect before continuing.
WCAG 2.2 AA is the baseline for design and build. Known gaps go into an accessibility statement rather than being hidden.
Individual accounts with two-factor authentication, secrets outside code repositories, dependencies kept current, and personal data collected only when there is a reason.
Automated tests where they save time, real-device testing always, and a short checklist for each release covering the journeys that matter most.
Small releases with a way back. Database changes are planned so a release can be rolled back without losing data.
No false urgency, hidden fees, pre-ticked boxes or confusing cancellation paths. Time windows shown to customers are the real ones.
We tell you promptly, in plain English, what happened, who is affected, what we have done and what happens next. Then we write down how to prevent a repeat.
Support arrangements