How we work
A process built to remove surprises — because on a remote engagement, surprises are what cost money.
You tell us the problem. We work out whether we can help and say so honestly. Free, no obligation, and no pressure to book anything.
We map what you actually need. Where scope is genuinely unclear we quote a short paid discovery stage rather than guess at a fixed price.
Scope, exclusions, assumptions, timeline and price. You take it away and read it. Nothing starts until it is signed.
Access, accounts and a named lead on both sides. We agree the weekly rhythm and what "done" means for the first stage.
Work arrives in reviewable stages with a weekly written update. You see progress and can redirect early instead of at the end.
Each stage is reviewed against what was agreed. Problems surface here, while there is still time and budget to act on them.
Code, files, accounts and documentation transfer to you. We walk your team through anything they will maintain.
An optional arrangement for updates, changes and fixes, handled by people who already know your system.
Engagements work better when the client side does three things
None of them are onerous, and all three are the difference between a project that lands and one that drifts.
- 1Name one ownerSomeone who can answer questions within a day and has authority to decide. Not a committee.
- 2Review each stage properlyHalf an hour of real review at each stage boundary prevents weeks of rework later.
- 3Say when something is wrongEarly. We would much rather hear it in week two than at handover.
Tell us what you are trying to fix
Send us a short description of the problem and we will come back within one working day with a straight answer on whether we can help, roughly what it would take, and what it is likely to cost.