A method you can check us against
No trophy cabinet here. Instead, the steps we follow and the tests we hold ourselves to, written down so you can quote them back at us.
Name the loop
We write the repeated task in your words: who does it, how often, what goes wrong.
Decide if it should be a tool at all
Sometimes a better checklist wins. We say so before anything is designed.
Sketch, then click
Rough screens first, then a prototype people can try on their own device.
Build in small slices
Each slice is something you can open and test, not a progress percentage.
Release with a way back
A checklist, a named approver and a plan for undoing a bad release.
Look after it
Fixes, updates and IT support, agreed in writing rather than assumed.
Quality criteria
| Criterion | How you can check it |
|---|---|
| Works by keyboard and at large text sizes | Tab through it; zoom to 200%. |
| Usable on a small phone | Open it at 390px wide; nothing scrolls sideways. |
| Errors explain themselves | Submit a form empty; it tells you what is missing and keeps your text. |
| No hidden tracking | Ask us which scripts load. The answer should be short. |
| You can carry on without us | You hold the accounts, the domain and a written hand-over. |
Questions people ask about the method
Do you give fixed prices up front?
Not before the task is understood. After scoping we can discuss how to price it. Nothing on this site is a quote.
Can we skip the prototype?
For a small website, sometimes. For an app that will be used every day, a prototype usually saves more time than it costs.
Do you promise a response time?
No. We work Monday to Friday, 09:00–18:00 UK time, and reply as soon as we reasonably can.