1 · Intake
We listen, then write back a short summary of what we understood. You correct it before anything else happens.
Process line
Method, then proof.
We have no awards or client logos to show here, and we will not invent any. Instead, here is the line every job runs along and the checks it must pass.
2 · Dependency map
We list what each piece of work relies on — accounts, content, decisions — and flag anything missing.
3 · Agreed slice
We agree a first slice of work small enough to review properly, with what will be delivered and how you will check it.
4 · Build and review
Work is shown in progress, not only at the end. Feedback is recorded so decisions do not get lost.
5 · Release and hand-over
We release with a checklist and a rollback note, then hand over access and documentation.
What we will not do
- Promise a response time we cannot guarantee
- Quote before understanding the scope
- Keep your accounts or files hostage
- Claim results we cannot evidence
Quality criteria
Checks applied before we call something finished. You are welcome to hold us to them.
Q-01 READABLE
Text meets accessible contrast and can be enlarged without breaking layout.
Q-02 KEYBOARD
Every control can be reached and used without a mouse, with a visible focus.
Q-03 SMALL SCREENS
Pages and screens work at narrow phone widths without sideways scrolling.
Q-04 HONEST FORMS
Forms never claim success unless the server actually accepted the request.
Q-05 OWNERSHIP
You hold the logins, source and documentation at hand-over.
Q-06 REVERSIBLE
Each release has a written note on how to step back if needed.