Fractional AI operations & business systems

How I work

I help growing businesses turn AI from ad-hoc tool use into governed, repeatable operations. Because I build and run these systems myself, the designs I hand you are grounded in what actually ships, not slideware.

The engagement, end to end

A deliberate, repeatable method, so you always know what happens next and what you'll have at each step.

1
Listen & capture
Working sessions with your team to map how the work really happens today, the friction, the workarounds, the repeated effort.
You get: a shared, accurate picture of current state.
Consent-based interviews · transcript capture
2
Diagnose & brief
I turn those conversations into a clear brief: prioritised opportunities, current- vs future-state, scope, and how we'll measure success, presented back for your sign-off before anything is built.
You get: an agreed brief and opportunity matrix.
Analysis · workflow mapping
3
Design & build
I deliver the solution: workflow standards, reusable prompt libraries, configured Claude Projects & skills, governance, and working assets, with a human in the loop by design.
You get: a working solution + clear documentation.
Claude · Cowork · Code
4
Enable & hand over
I train your team and AI champions and leave editable SOPs and a runbook, so you own and run it without me, then we track benefits against the baseline and prioritise what's next.
You get: capability that stays, and a measured result.
Training · SOPs · benefits tracker

How I handle your data

I'm selling governed AI, so I hold my own work to the same standard. Concretely:

Conversations are recorded only with your explicit consent.
Transcripts and documents live in an agreed, access-controlled location.
Client data stays in approved, business-tier tools with model-training turned off.
Identifiers are de-identified where practical during drafting.
Material output is reviewed by a qualified human before it's used.
Your data is retained only as long as needed and deleted on request.

The principle behind every build

AI drafts, a human decides.
Automation removes the repetitive effort; accountability stays with your people.
Captured once, reused by everyone.
Good prompts and standards become shared assets, so quality compounds instead of staying in one person's head.
You own it after handover.
The goal is capability that runs without me, not a dependency on me.

Grounded in systems I build and run

My advice is shaped by hands-on work, not theory. Alongside client engagements I architect and run my own systems, including a production client-outreach CRM (built on Resend and Supabase) and a multi-agent operations stack (Claude, plus my own Paperclip/Hermes/Openclaw setup). It means when I design a workflow for you, I know what it takes to actually ship and maintain it.