How the work is set, proofed and printed.
Understand
Conversations, the one-page brief, and a list of what is out of scope. We agree what a first release must do.
Shape
Task flows, wireframes and a clickable prototype. You see the product before it is expensive to change.
Build
Short cycles with working builds you can install or open. Progress notes each week in plain language.
Release
Store listings, privacy answers, testing tracks, a checklist and a plan for the first fortnight after launch.
The house style: standards we check against
Usability
A new user can complete the main task without instructions. We test this with real people before release.
Accessibility
We work towards WCAG 2.2 AA: contrast, focus visibility, labelled controls, text scaling and reduced-motion support.
Reliability
Every screen has loading, empty and error states. Forms never silently lose what someone typed.
Privacy
Collect only what the product needs. No third-party tracking is added unless you choose it knowingly.
Maintainability
Code in version control, a README that works, and decisions recorded so the next developer is not guessing.
Honest release
Store listings describe what the app does today, not what it might do later.
Achievements, honestly
We have no awards to list and we do not publish client names or results without permission. What we can point to is this website itself: built without trackers, with readable type, working without images, and with a contact form that tells you the truth about whether your message was accepted.