From first call to launch.

A clear, predictable path from the first conversation to a working system — so you always know what happens next, and what it costs.

01

Discovery call

A free, no-pressure conversation about where your time actually goes. I'll ask which tasks you repeat most, which ones you dread, and where things tend to get stuck or dropped.

You don't need to arrive with a technical brief — describing the frustration is enough. If it turns out AI isn't the right fix for what you're describing, I'll say so on this call rather than write a proposal.

02

Scoping the problem

I map the process properly before building anything — the actual steps, who touches what, where the data lives, and which parts genuinely need a human decision.

You then get a written proposal: what I'll build, what it will and won't do, a fixed price, and a timeline. No hourly billing and no open-ended scope, so the cost can't drift once work starts.

03

Building the solution

I build it and test it against your real cases — including the awkward edge cases, because those are what break automations once they're live.

You get plain updates as it comes together, and a chance to try it before it's finished. If something isn't working the way you expected, it's much cheaper to catch it here than after handover.

04

Handover & support

You get the system running, documented in plain language, and explained properly — including what to do if it stops behaving as expected.

After that I'm available to monitor and refine it as things change. That can be an ongoing arrangement or purely as-needed; either way you're not locked into a retainer to keep what you've paid for working.