What you get, month by month
Twelve weeks, six sessions, and three months that each close on something you own and keep. Running through all three is one document: your AI plan, drafted in month one, refined in month two by what building actually taught you, and only defined in month three — because a plan written before anyone has built anything is a guess.
Two group sessions
Twice a monthOne hour of instruction, then one hour working in the same room. Nobody leaves stuck on setup.
One-on-ones
Once a month, an hour eachTime on each champion’s own systems, and whatever did not connect.
AI office hours
The weeks in betweenDrop in with whatever is stuck. No agenda, no obligation to attend.
Executive coaching
Monthly with the sponsorSeparate from the group. Building their own capability, and clearing blockers that need authority.
One plan, three drafts
The plan for what AI does in your company is not something we hand you in week one and it is not something you could write yet. It gets drafted early, refined by what actually happens when your people build against real systems, and only then defined well enough to run on. Each month closes on a better version of the same document.
- Month 01
Drafted
Written from what the champions and the sponsor know today: where work already breaks as it crosses between departments, what looks worth doing, and what nobody can reach yet. It will be wrong in places. That is what the next two months are for.
- Month 02
Refined
Evidence replaces opinion. What connected and what refused to. What turned out trivial, and what turned out to be the real work. A plan written before anyone had built anything is a guess; this is the version that stops being one.
- Month 03
Defined
Sequenced, costed in the terms a board or a sponsor will accept, and owned by your sponsor rather than by us — with the pieces that need outside help named and scoped by the people who ran into the limit themselves. This is what you run the next ninety days from, and you are free to take it to anyone.
- Month 01
Access and the first draft
Every champion is working against real company data, and the plan exists on paper for the first time.
What you have at the end of the month- 01.1
A provisioned environment per champion
Tooling running under real permissions against real company data, owned by the person using it and rebuildable without us. Plus a clear line on what does not go into a chat window, drawn before anything real is connected.
- 01.2
The first draft of your AI plan
A short document, written in the room: where work already breaks as it crosses between departments, what looks worth doing, and what nobody can reach today. It is a first draft on purpose. Anyone offering you a finished AI plan four weeks in is selling you a document nobody has tested.
How it gets madeWeek 11 hr taught · 1 hr workingYour working environment
No theory until the tools run. Every champion leaves the room with one real task from their own job done live.
Week 31 hr taught · 1 hr workingGetting connected
Connecting what is connectable, live, with real permissions rather than a demo account — and honest workarounds for what will not connect, because some of it will not.
In the weeks between- A working session with the sponsor and whoever holds the systems, drafting the plan
- Office hours in the off week
- An hour with each champion on their own systems
- 01.1
- Month 02
Judgment and repeatable work
The company gets a written position on how it uses AI, and the first work that runs without being asked.
What you have at the end of the month- 02.1
A written data-use position
What may leave your walls and what may not, tested against what your insurers and your customers’ contracts already require. Short enough that people actually read it.
- 02.2
A verification standard
The checks that run before anything reaches a customer, and the list of what is never delegated. This is the deliverable that keeps generic AI output out of the work people pay you for expertise on.
- 02.3
One workflow per champion, running on its own
Against live company data, on a schedule, documented well enough that somebody else could pick it up. Not a demo — something that produces work whether or not anyone is watching.
- 02.4
The second draft of your AI plan
Refined against what building actually taught you. Things that looked easy in month one turned out to be the hard part, and vice versa. This is the draft where the plan stops being a guess.
How it gets madeWeek 51 hr taught · 1 hr workingJudgment, compliance and guardrails
Where these tools fail and what the failures actually look like, which is what the data-use position and the verification standard get written from.
Week 71 hr taught · 1 hr workingFrom tasks to systems
The shift from asking a tool for something to building work that repeats without being asked.
In the weeks between- Executive coaching: the sponsor sees what has been built, and blockers that need authority get cleared here
- Office hours in the off week
- An hour with each champion on what they are building and what it needs
- 02.1
- Month 03
Transfer
The work moves beyond the champion group, and the plan is finished and handed to your sponsor.
What you have at the end of the month- 03.1
A workflow running outside the champion group
Piloted with people who were never in the room, with the context package that made it transfer. This is the evidence the capability spreads rather than sitting with whoever attended.
- 03.2
A capstone record per champion
What they built, what it produces, what it cost, and an honest account of what did not work. Written down, because in twelve months this is what tells you whether it was worth it.
- 03.3
Your AI plan, defined and owned by your sponsor
The same document, third time round: sequenced, costed in terms a board or a sponsor will accept, and drafted by the champions who have to execute it rather than handed down as a recommendation nobody signed up for. The pieces that need outside help are named and scoped inside it, by the people who ran into the limit themselves — which is a better statement of work than a procurement process produces, and you are free to take it to anyone.
How it gets madeWeek 91 hr taught · 1 hr workingBuilding for the team
Handing a workflow to two other people and packaging the context so it survives the trip. Where adoption stalls, which is never the technology.
Week 12Two and a half hoursCapstone and the next ninety days
Each champion presents what they built and what it cost. The next ninety days get drafted by the group and presented to the sponsor in the room.
In the weeks between- Executive coaching: the sponsor drafts how this runs once we are gone
- Office hours in the off week
- An hour with each champion, prepping the capstone
- 03.1
The twelve weeks
Sessions land twice a month. The weeks in between are not empty: that is where the one-on-ones, the office hours and the sponsor’s own coaching sit.
- wk 01Session 1 · Your working environment
- wk 02First-draft working session · office hours
- wk 03Session 2 · Getting connected
- wk 04One-on-ones
- wk 05Session 3 · Judgment, compliance and guardrails
- wk 06Executive coaching · office hours
- wk 07Session 4 · From tasks to systems
- wk 08One-on-ones
- wk 09Session 5 · Building for the team, with the sponsor in the room
- wk 10Executive coaching · office hours
- wk 11One-on-ones, prepping the capstone
- wk 12Session 6 · Capstone and the next ninety days
Before week one
- Paid AI seats for every champion, before the first session
- Two hours a week per champion, formally allocated
- An executive sponsor who attends monthly coaching
- Admin access, or a direct line to whoever holds it
- Real work to bring
The full picture of the program, including who it is for and where it ends up, is on the In-Company Acceleration page.
Would this fit your calendar and your champions?
The assessment names who from your company should be in the room, and what they would need access to before week one.