Handling

Handling instructions, printed on every box.

These standards apply to every engagement. If we ever need to set one aside, we explain why in writing first.

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.

02 · Rhythm

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.

03 · Estimates

Estimates are ranges with written assumptions. When an assumption changes, we tell you and agree the effect before continuing.

04 · Accessibility

WCAG 2.2 AA is the baseline for design and build. Known gaps go into an accessibility statement rather than being hidden.

05 · Security basics

Individual accounts with two-factor authentication, secrets outside code repositories, dependencies kept current, and personal data collected only when there is a reason.

06 · Testing

Automated tests where they save time, real-device testing always, and a short checklist for each release covering the journeys that matter most.

07 · Reversibility

Small releases with a way back. Database changes are planned so a release can be rolled back without losing data.

08 · Honest interfaces

No false urgency, hidden fees, pre-ticked boxes or confusing cancellation paths. Time windows shown to customers are the real ones.

When something goes wrong

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