Approach & quality
Slow at the start. Calm at the end.
Most of the risk in a digital project is decided in the first fortnight. We spend that time carefully.
The order of work
- A
Listen
A conversation about the problem, the people and the constraints. No pitch deck.
- B
Define
A written scope: users, core tasks, what is out of scope, phases and fixed prices.
- C
Design
Wireframes, then a clickable prototype you can test with real people before build.
- D
Build
Short cycles with a working build to review at the end of each one.
- E
Check
Testing against the criteria below, with results written up.
- F
Release
Store listings, hosting, a rollback plan, and handover notes.
Quality criteria
| Criterion | How we check it |
|---|---|
| Readable | Text contrast meets WCAG 2.2 AA; layouts hold at 200% zoom and large system text. |
| Operable | Every action reachable by keyboard or screen reader; touch targets at least 44 by 44 points. |
| Honest | Errors explain what happened; forms never pretend to succeed; privacy text matches real data use. |
| Light | Pages and screens load quickly on a mid-range phone over a slow connection. |
| Maintainable | Code and designs are documented well enough for another competent team to continue. |
| Releasable | Store and hosting checklists completed and signed off before launch. |
Achievements, honestly
We have no awards to list and no client results we are permitted to publish yet. What we can point to is this website: built to the same criteria above, with no tracking, plain HTML, and a contact form that tells you the truth about delivery.