How a request becomes finished work
No achievements list. Here is the route and the checks instead.
Intake
We restate your request in our own words and send it back. If it does not match what you meant, we fix that before anything else.
Scope
A short written scope: what is included, what is not, what we need from you. Changes later are written down too.
Build or fix
Work in small, viewable pieces. For apps and sites you see test versions; for IT issues you see what we changed.
Check
Each item passes the criteria below before we call it ready.
Handover
Access, notes and anything you own goes back to you. No hostage logins.
Quality criteria we use
| Check | Pass means |
|---|---|
| Keyboard | Every control reachable and visible with focus. |
| Small screens | No sideways scroll at 390px width. |
| Contrast | Text meets WCAG AA contrast. |
| Errors | Forms say what went wrong and keep what you typed. |
| Ownership | You hold the accounts, domains and credentials. |
| Notes | A plain written record of what was done. |
Questions about the method
What if a check fails late?
We tell you, explain the trade-off and agree whether to fix now or record it.
Do you work to fixed prices?
That depends on how clear the scope is. We discuss it once we understand the request; nothing on this site is a quote.