Standing orders
The rules we hold ourselves to.
These standards apply to every engagement. If one ever needs to be set aside, we will say so in writing and explain why.
Decisions are recorded
Every significant product or technical decision is logged with date, options considered, the choice and the reasoning. The log belongs to you.
You own everything
Source code, design files, app store accounts, domains and hosting sit in your accounts. We are invited in; we never hold your product hostage.
Estimates are ranges
We estimate in ranges and state the assumptions behind them. When an assumption breaks, we tell you before the work continues, not after the invoice.
Accessibility is baseline
WCAG 2.2 AA from the first sketch. Known gaps are listed in an accessibility statement rather than hidden.
Security basics are not optional
Dependencies are kept current, secrets stay out of repositories, access uses individual accounts with two-factor authentication, and personal data is minimised by design.
Releases are small and reversible
We ship in small increments with a way back. A release that cannot be rolled back needs a written reason.
Disagreement has a process
If we disagree with a direction, we say so once, clearly and in writing, with evidence. If you decide otherwise, we record it and build it well. We do not relitigate every week.
No manipulation
No dark patterns, fake urgency, hidden opt-outs or pre-ticked consent boxes. We will argue against them even when asked.
What we measure
We agree a small number of signals per project, such as task completion in testing, crash-free sessions or time to publish an update, and we report them honestly, including when they move the wrong way. We do not publish marketing statistics about past work.
Hold us to these