Teach
I teach the same method I used as a CTO. Roughly half of any session is hands-on, on the licences you already hold — not on a platform I want to sell you. A room runs half a day to two. You leave with an artifact, never a certificate. A clinic later, we look at what actually happened.
Separate what can be handed over from what only looks like it can.
What may be drafted, what may be executed, and who signs — before anyone builds.
Measure the work as it is, then change it. A number without a before is a slide.
The gate is a file. Take it: /gate.md.
Board, CEO, senior management
What AI changes about the business you already run, and what it does not. No tooling demonstration. We work on the decisions that are actually in front of you — where the exposure sits, what you are being sold, and what you would need to see before signing.
A written position on where AI does and does not touch your business this year.
Function heads and P&L owners
Function heads, P&L owners and the team leads under them. Most AI programmes fail because nobody found the right work first. We go through your actual processes and separate what can be handed over from what only looks like it can.
A ranked list of the work worth handing over, with the reason each one ranks where it does.
Engineers, QA and security
Engineers, QA and security, working on the licences you already hold. What breaks under real load, why the model is rarely the thing that stalls, and how you write a gate that survives an incident.
A tested method and a written engineering standard your team wrote, not one I handed over.
Risk, compliance, audit, finance
Risk, compliance, audit and finance — in the first room, not the last one. What may be drafted, what may be executed, what the approver sees, and how you undo it the same day.
An approval design the person accountable would actually put their name to.
The four rooms are who is in the session. Underneath is the course I actually teach: Foundation, the job you are accountable for, the function’s files, then after. Same files. Three jobs — produce, review, or own.
I disclose what I build and sell at the start of every engagement. Advice from someone with a product is only worth having if they will tell you when not to buy it. The full disclosure is on my About page.