Three ways to start. Either way, you leave with tools that fit your work and the skills to run them without me.
01 / The free assessment Two calls, one per company. You show me the work; I show you what I'd fix, what you can fix yourself for free, and what I'd charge for the rest. | 02 / Customized training A live session built on your actual work. Not a workshop, not a curriculum. | 03 / Build + handover You bring the problem. I build the whole thing and leave you an interface your team runs. | |
|---|---|---|---|
| What you bring | What you bringA repo, or last month's reports and one recurring task | What you bringThe report you rebuild every month, or the process nobody wants to own | What you bringThe problem, and access to the systems it has to plug into |
| What happens | What happensTwo calls: discovery, then a readout on your actual files | What happensA live session built around that work, one on one or a small group | What happensI build it end to end, in your accounts, with one working session a week |
| What you leave with | What you leave withA readout you can forward, a fix-it-yourself list, and a scoped proposal if there's paid work worth doing | What you leave withYou've done it once on your own files, and you have the written version to do it again | What you leave withA working tool, a plain interface your staff runs, and the written version of how it works |
| What it costs | What it costs$0, one per company | What it costsPaid, scoped to your team's size and what you bring | What it costsPriced per phase, scoped to what we agree to build. You see the number before you commit. |
| How the assessment works → | Ask about a session → | Ask about a build → |
346 independently verified records, fully built, reaching zero users. The assessment found it. A free punch list and a scoped three-phase plan came out of it.
One product manager, five skills built around their actual work, trained one on one.
Less AI than the others — and the clearest picture of how the handover works.
Governance first, then 25 tools built with their staff and 7 switched on out of the box — 3 of them plain automation with no AI. Every one is run by their own team.
Three phases, each with a written exit review. Governance comes first (about two weeks) because it's the part most people skip.
Governance means the rules and accounts for who can put what into which AI system. We write those rules down and set up the accounts before any tool. If there's code, the tests and checks you already have get wired in so they run on every change. Rules that live in documents fail silently; rules that live in machines don't. You leave with a written policy your team wrote with me and the checks that catch it when someone forgets.
One working session a week, screen-share, recorded. Everything lands somewhere your team can open and change: a pull request, a shared doc, a tool in your own accounts, never in mine. You're at the keyboard for enough of it that you can change it later. Some of what we build won't use AI at all.
Someone on your team runs a full cycle without me, while I watch. The skills and the docs are packaged as yours. Then I leave.
The thing that does the work, in your accounts, built to be changed.
A written set of instructions your AI tools follow by default: your brand voice, your rules, your format, so nobody re-explains it every time.
You've done it yourself, at least twice, with me in the room.
Happy to talk through which one fits before you pick. The first two calls are free either way.