How it works
No mystery, no jargon. Just four honest steps.
From first message to a finished build, here's exactly how a project runs, what you can expect at each stage, and when you're asked to make a decision.
-
01
Initial conversation
We start with a quick call or a few emails, whatever's easiest for you. Tell me what's slowing you down or what you're trying to build. No sales pitch, no discovery-call theatre, just a straight conversation about whether this is worth solving and roughly what it would take.
-
02
Scoped proposal
You get a written proposal: what I'll build, how long it will take, and what it costs, fixed, not an hourly estimate that creeps. If the scope is unclear on either side, we talk it through before anything is agreed. Nothing starts until you've said yes to a specific number. For a general sense of how long each service tends to take, see the indicative timelines on the pricing page.
-
03
Build, with check-ins
I build in stages, not one long silent stretch followed by a surprise. You'll see working versions as they're ready, not just at the end, and you can flag changes early instead of after everything's finished.
-
04
Handover and support
When it's done, you get everything: the code, the credentials, a plain-English explanation of how it works, not a black box you're locked into me for. There's no ongoing commitment once the project is finished, you're free to walk away and maintain it yourself. If you'd rather not, an optional monthly retainer is available for anyone who wants ongoing support, but it's never required.
Ready to start the conversation?
Tell me what's costing you time or money. I'll tell you honestly whether it's worth solving, and how.
Thanks, that's sent. I'll get back to you as soon as possible. Usually within 1-2 business days.