Pricing
No packages with names on them. No bronze, silver, gold. And you won't need a call just to hear a number, because the typical number is printed on this page. Three stages, and the first one carries a fixed price, in writing, before I touch anything.
First piece, fixed price
One bounded thing with a start and an end. £750 to £1,500 is typical, quoted before anything starts, and the number doesn't move. It's small on purpose: you judge me on one working piece. Not a deck and a handshake. Yours to keep either way.
How long? Here are two real ones. A coaching company's monthly setup was running within about 21 hours of the first line of the build, and my own email migration ran over one weekend. You get a date along with the fixed price.
Then per project
If the first piece earns it, each build after is scoped and priced on its own. A number per piece, agreed up front. No day rate ticking away in the background, no invoice for scope nobody agreed.
Month to month, when trust has receipts
Once systems are live, some owners want them watched, patched and extended. That's month to month, and you can stop it whenever you like. I don't pitch it on day one and I won't. A retainer before anything is running is paying for a promise.
What I'll tell you not to buy
I'd rather lose the build than sell you one you don't need. That's why the first piece is usually an audit: it finds out what's actually worth building before you commit to building it. Most businesses I look at are quietly paying for a stack of tools nobody has opened in two years, half of them doing the same job. A cost audit is often the fastest ROI I deliver.
I ran it on myself before running it on anyone else. Of the automations in my own business, 4 of 215 had actually run in the previous 30 days. The rest just sat there. I cut £12,000+ a year of my own software, 6 tools replaced with things I built, before advising anyone else to spend a pound.
The same audit moved my email platform from £650 a month to £73. That's about £7,000 a year, found before anything new was built. The audit had paid for itself right there. The cancelled-subscription ledger itself, line by line, is on the AI that didn't land page.
What it costs to run
In my own operation, 14 of 22 AI jobs run on models on my own machine. No per-call bill, and private work never leaves the building. Where a paid cloud model genuinely earns its cost, every call passes through one door, so every pound of AI spend shows up on one screen.
I track 127 recurring costs in my own subscription audit, because forgotten software is where operating money leaks out. Your build gets the same treatment: the running costs named, line by line, before you sign off.