How a ticket moves
There is no portfolio of claimed results on this site. Instead, here is the route each job takes and the checks you can hold us to.
Three rules
Write it down. Change one thing at a time. Say plainly when something is unknown.
Intake
Your message is read and sorted into a lane. If key facts are missing, you get questions rather than assumptions.
Triage note
A short written note: what the job is, what it is not, known risks and the very next step.
Agreement
Scope and any cost are confirmed in writing before work starts. Nothing in the sorter or on this site is a quote.
Work in slices
Small, checkable pieces. You see progress in something you can open, not a percentage.
Check against criteria
Each slice is tested against the table below before it is called done.
Hand-over
Access, files and notes handed to you, so the work does not depend on us remaining involved.
Honest quality criteria
What “done” means here. These are commitments to check, not claims about past results.
| Criterion | How it is checked | What it does not mean |
|---|---|---|
| Readable at 390px wide | Each screen viewed at phone, tablet and desktop widths with no sideways scrolling | Pixel-identical on every device ever made |
| Usable by keyboard | Menus, forms and dialogs reachable and closable without a mouse | A formal accessibility certification |
| Fails honestly | Forms and errors tell the truth when something has not worked | That nothing will ever fail |
| Written record | Changes and decisions noted in plain English | A guarantee of any fixed turnaround |
| You keep control | Accounts, code and content handed back to you | Ongoing support unless separately agreed |
Questions about the method
Can you skip the triage note?
For a tiny support issue the note may be a few lines, but it is not skipped. It is what stops the wrong problem being fixed.
Why no case studies or testimonials?
Because this site does not publish anything it cannot back up. Ask about relevant experience directly and you will get a straight answer.