THE PRICE
IS ON
THE PAGE.
Nine engagements, from £450 to £75,000. No discovery call required to find out what any of them costs, because a discovery call that exists to qualify your budget is not a discovery call, it's a credit check with a calendar invite.
Every one is fixed fee and fixed date. Every one has a what this is not section, because undefined scope is what actually kills this kind of work, not underpricing. Every clock starts when access is granted, not when you sign, because I've never met a change-advisory board that moves at the speed of a contract.
Starting something
For a person with an idea, a founder who has stalled, or anyone whose first go at AI produced nothing. Same expertise as below, aimed at the stage where the question is still whether the thing should exist.
The Straight Answer
Ninety minutes on your idea, then one written page telling you whether it is real and what the first buildable piece is.
The Post-Mortem
You tried AI, it went nowhere, and nobody can tell you why. This is the written answer.
Build It With You
Three weeks, one working first version, built with you rather than for you, so it does not die when I leave.
Already in production
For teams with a system already running, usually somewhere regulated or expensive to get wrong. Fixed fee, fixed date, published scope ceiling, and a written boundary you can hold me to.
The First Look
Two days, one written page, one straight answer on whether you actually have a problem.
Go / No-Go
Seventeen categories, a one-word verdict on page one, and the first fixes arrive as pull requests, not as a list for somebody else to implement.
The Replay Test
Fifteen days to find out, capability by capability, whether you have an AI system or a demo with a try/except around it.
The Evidence Layer
The record-keeping architecture your legal team needs in order to make the claim, ending with a verifier your auditor can run against an export, with no access to me and no access to you.
On The Hook
You have the diagnosis. What you do not have is the person. One name against the architecture decisions, and code in your repository.
The Standing Verdict
The same audit, re-run every quarter as a dated diff: what regressed, what is new, what is still open, what shipped.
The terms, in one place
- 50% on signature, 50% on delivery. The signature invoice clearing is what holds your slot.
- Every clock starts at access granted, never at signature.
- Where fixes are included, the promise is the pull request opened, your reviewer, your CI and your branch protection decide what merges.
- Scope ceilings are published. Anything above them is agreed in writing before work starts, never invoiced after.
- Nothing here is legal advice, and architecture supports a conformity case rather than conferring one.
Not sure which one?
Start with The First Look. Two days, one page, and roughly half of them end with me telling you there isn't a problem worth paying to fix.
Tell me what's broken →