The 90-Day AI Operator — for UK SMEs
I don’t advise on AI. I build it — then hand you the keys.
90 days inside your company. I build the systems your team will actually use, train your people, and leave you owning it. Operator, not advisor — the difference is you end up with working systems, not a strategy deck.
The Engagement
The 90-day arc
Days 1–15
Audit & target
I map your organisation through an agents-loops-workflows lens: every recurring process, who runs it, what it costs in hours, where it breaks. Together we pick the 2–3 highest-leverage builds. Output: a scoped build plan you sign off — scope freezes here, so you always know exactly what you're getting.
Days 16–70
Build
Working systems shipped on your infrastructure — your accounts, your data, your control. Weekly demo cadence: you see real progress every Friday, not status reports. Documentation is written as it's built, not reverse-engineered at the end.
Days 71–90
Handover & train
I train your internal owner(s), hand over runbooks, monitoring and escalation paths, and record the training. The success test is blunt: the systems must run for two weeks before exit without me touching them.
Day 90
Exit
A clean exit with everything owned by your team — or a scoped renewal for a new build with a new scope. No drift into open-ended dependency: the engagement is designed to end.
Milestone-billed. Fixed scope. No day rates.
The engagement is billed across four milestones — signing, day-15 scope sign-off, mid-build, and handover — so payment tracks delivery, not time. Never hourly: the invoice buys outcomes and ownership, not my calendar.
Pricing on request
Scoped to the builds we pick at audit. You’ll have the full number before anything is signed — no surprises after day 15’s scope freeze.
What You Get
You keep everything. That’s the design.
- A scoped build plan, signed off at day 15 — the scope freeze protects your budget
- 2–3 working AI systems on your own infrastructure, not mine
- SOPs and runbooks written as-built: what it does, day-to-day operation, monitoring, escalation, running costs
- A trained internal owner for every system, plus recorded training sessions
- Two weeks of unassisted operation proven before I leave
- A team that understands what was built and why — capability, not dependency
Who It’s For
Ops-heavy UK companies where “we should be doing something with AI” is already being said out loud
The best fit: 10–50 person companies drowning in quoting, scheduling, reporting, inbox triage and document churn — with no dev team and a founder or MD who can decide quickly. Recruitment agencies, accountancy practices, property and lettings management, logistics back-offices, trade-services firms that outgrew the van.
If you’re hiring another admin or ops role right now, that’s usually the tell: a 90-day build can absorb much of what that role would do — permanently, and owned by you.
Not a fit: tech startups with in-house engineers, enterprises with procurement cycles longer than the engagement, anyone who wants a chatbot as decoration, or anyone whose real problem is sales rather than operations. I’ll tell you on the first call if that’s you.
Guardrails are part of the build: a permission-and-risk pass decides what an agent may touch, read or send before anything ships. LLMs talk; verified code acts.
Why Me
An operator’s CV, not an advisor’s
18 months inside a regulated fintech
Head of marketing at a regulated digital-assets fintech, shipping AI-native systems inside real compliance constraints — not a sandbox.
A live local-business product
The AI Visibility System runs for paying local clients: sites, booking agents, review engines, monthly proof reports. Same stack, different altitude.
I run my own company on this
My own agent stack handles briefings, content pipelines, dashboards and reporting daily. You can see it working on the call — a live tour, not a slide.
The handover library
Every engagement produces SOPs, runbooks and training your team keeps. I'll show you real (anonymised) handover artifacts so you know exactly what you receive.
Start Here
Tell me what’s eating your team’s hours
Two or three sentences is plenty. I’ll reply within 24 hours with an honest read on whether a 90-day build fits.