Method, and the criteria we will let you hold us to.
Instead of testimonials, here is exactly how we work and what 'done' means to us. Ask about any of it.
Survey
A conversation and, where there is existing work, a review. We write down what we heard: goals, users, constraints, unknowns. You correct it.
Footings
Scope, priorities and the order of work. Accounts, repositories and hosting are set up in your name where possible, so you own them from day one.
Build in courses
Work is delivered in small, reviewable increments. Each one is demonstrable on a real device or a staging address.
Load test
Checks against the criteria below, including accessibility and failure cases, before anything is called complete.
Handover
Documentation, credentials transfer and a walkthrough. Our handover checker is the list we use.
Aftercare
Release assistance and IT support if you want them, arranged separately and described plainly.
Honest quality criteria
What we check, and how you can verify it
Usable by keyboard and screen reader
Check it yourself: Tab through the main tasks; switch on VoiceOver or TalkBack.
Readable at 390px wide and at 200% zoom
Check it yourself: Open it on a small phone; zoom your browser.
Failure is reported truthfully
Check it yourself: Forms and actions say when something did not work, rather than pretending.
Buildable by someone else
Check it yourself: A second developer follows the written steps without our help.
Accounts belong to you
Check it yourself: You hold owner access to domains, stores, hosting and repositories.
No unnecessary tracking
Check it yourself: Inspect cookies and network requests; nothing optional is added without agreement.
About the method
What if a criterion is not met?
We tell you, explain why and agree what happens next. We do not mark it complete.
Can the method be shortened for small jobs?
Yes. A small IT support request does not need six stages, but ownership and honest reporting still apply.