AI systems and automations
Built in full, in the tools you already use, and handed over running.
It fits when the work is routine but still waits on you: replies, follow-ups, invoices, reports, onboarding, scheduling.
I map the work first, then build each system as a role with one job: a reply desk, a call-back, a collections clerk, a weekly report, an onboarding coordinator, a morning list. Each one drafts and prepares. A named person on your team reads, decides and sends. My human in the loop AI guide shows where that person goes in each system.
Everything is written down before I hand it over, so your team can run and change it without me. For my own practice I run the same kind of system: an AI system I built in Claude Code reads my calendars, inboxes and project files every morning and hands me one ordered list. The AI Chief of Staff Starter Kit is that workspace as a template.
What you get
- A map of the work, and the order to build in
- Each system built and tested on real work
- A named owner and a written procedure for each one
- Clear limits: what it may draft, and what always comes to a person
- Training for the people who run it
- A support window after handover
Two of these start with a fixed two-week setup. In the Speed-to-Lead Setup, I set up and tune the lead reply tool you pick, then run what happens after the booking. The AI Operations Setup connects the AI you already pay for to your inbox, calendar and job software.


