AI training for teams
Your team leaves with it working. Not with notes.
Most AI training is a talk. People watch, agree it was interesting, and go back to the same workflow on Monday. I do the opposite. We take one thing your team already does every week and rebuild it live, with your own material, in the tools you already pay for. You get a working system installed — and a team trained to run it without me.
Former Senior Mentor, Tiago Forte's Building a Second Brain
Half day $3,500 · full day $6,500 · scoping call free
Why the last one didn't stick
Three things go wrong, and they go wrong everywhere.
The training happened. Nothing changed.
Someone came in, showed slides, everybody nodded. On Monday the team went back to the same workflow, because nobody had actually built anything while the expert was in the room.
Two people are flying, everyone else is stuck.
A couple of early adopters got good at this on their own. The rest are quietly guessing, and nobody wants to admit they still do not know what to use it for.
Nobody knows what is safe to put in it.
No written rule about client data, no agreed line on what a model may touch. So people either paste in everything or avoid it entirely, and both are expensive.
How I run a session
Four rules I don't break.
I taught as a Senior Mentor in Tiago Forte's Building a Second Brain — the program that shaped how a lot of people think about this work — and I spend my weeks building the systems rather than talking about them. A session is built on both halves.
01
We build on your real work
No toy exercises. Before the session I take one workflow your team already does every week and we rebuild it live, with your material, in the tools you already pay for.
02
I say the reasoning out loud
The point is not that I can do it. Your team watches every decision and hears why, so they can make the next one without me on the call.
03
Everyone leaves with the thing working
Not notes. The workflow runs when they get back to their desk, and it is written down so the person who missed the session can still follow it.
04
Rules in writing, before anything else
What a model may touch and what it may never touch, agreed and documented in plain language. Most teams have never had this conversation and it is the one that prevents the expensive mistake.
The systems I install
Named systems, built in the room, yours when I leave.
Training alone is a talk. A system built for you by someone else makes you dependent on whoever built it. So a session does both: I install one of these in your business, live, and train your team to run and extend it without me.
Quote & Proposal Generator
A request comes in; a branded draft quote comes out in minutes, built from your approved pricing and boilerplate. A person approves every number.
Replaces: 3–8 hours of assembly per quote.
Margin Guard
Checks every outgoing quote against your cost sheets and pricing rules, and flags underpriced lines before the customer sees them.
Replaces: The underpriced quote nobody caught.
The Reorder Machine
Past customers due for a reorder get a personalized, drafted reminder on schedule.
Replaces: The repeat business that never gets asked for — the cheapest revenue any business has.
Quote Follow-Up Machine
Drafts a personalized nudge for every sent-but-silent quote, on a schedule you set.
Replaces: Quotes dying of silence.
Meeting → CRM Pipeline
Turns a meeting transcript into a CRM record, agreed next steps, and a drafted follow-up.
Replaces: The meeting notes nobody typed up.
RFP Response Machine
Builds first-draft responses from your answer library and past documents, so people edit instead of starting blank.
Replaces: 15–20 hours per RFP.
What it costs
Three formats. Pick by how much needs to change.
Every one starts with a free 30-minute scoping call, because the session is built around your workflow and I can't design it until I know what it is.
The Taster
60–90 minutes · remote or on-site
$1,500
One team, or a leadership group deciding whether this is worth doing properly.
- ✓ One workflow rebuilt live, on your own material
- ✓ The plain-language rules for what AI may touch
- ✓ A written recap your team can act on
The Working Session
Half day · remote or on-site
$3,500
One team that needs to stop guessing and start using this on real work.
- ✓ One workflow, fully rebuilt and running before we finish
- ✓ Hands on keyboards — everyone builds, not just watches
- ✓ The written playbook for that workflow, yours to keep
- ✓ Your AI use rules, drafted with you and agreed in the room
- ✓ Two weeks of email follow-up while it beds in
The Build Day
Full day · on-site preferred
$7,500
A team with more than one bottleneck, or two teams that need to end up on the same system.
- ✓ Two to three workflows rebuilt and running
- ✓ The written playbook for each one
- ✓ Your AI use policy, drafted and agreed
- ✓ A named next step for each person in the room
- ✓ Thirty days of email follow-up
The Team Program
$24,000
Three sessions over six weeks
For a company that wants this to stick rather than be an event. Three build days spaced two weeks apart, so people go away, use it, hit the real problems, and bring those back. Includes the written playbooks, your AI use policy, a private channel for questions between sessions, and a closing report on what changed.
If the first system isn't live and saving measurable time within 30 days, I keep working at no charge until it is.
A Build Day credits 100% toward the Team Program if you book it within 30 days.
On-site travel outside Southern California is billed at cost. Groups over twelve are better run as a full day in two rooms — I'd rather say that upfront than have half the room watching.
Why me
I run all of this before I teach any of it.
The assistants that triage my inbox and draft my week are ones I built. So is the search engine over everything I've written, the funnel behind this website, and three pieces of software I ship and use daily. Fifteen years designing systems for how people think, a year training teams on-site at AT&T, Verizon, and Chase, and a past Senior Mentor role in Tiago Forte's Building a Second Brain.
Plenty of trainers can describe this work without having built it. Plenty of engineers can build it and lose a room in ninety seconds. Your team needs the person who does both, because the value is in hearing why a decision was made, not watching a finished screen.
How we'd start
Four steps, and the first one is free.
-
01
Scoping call
30 minutes. You tell me which weekly task costs the most and returns the least. Free, and I will say so if I am the wrong fit.
-
02
I build the session
I design it around that workflow and your actual tools, and send you what we will build before we meet.
-
03
The session
Hands on keyboards. We rebuild it live and it is running before anyone leaves the room.
-
04
The playbook
Written up within three days, in plain language, so the person who missed it can still follow it. Then follow-up email while it beds in.
Before you ask.
Do we need to be technical? +
No. Nothing I teach requires code. If someone on your team can use a spreadsheet and write an email, they can do everything in the session. The tools we use are the ones you already have.
Which tools do you teach? +
Whatever you already pay for, wherever possible. Usually that means Claude or ChatGPT plus your existing CRM, documents and note tools. I will not push you onto new software to make a session easier to run.
How many people can attend? +
Up to about twelve for a hands-on session. Past that, people stop building and start watching, which is the failure mode I am trying to avoid. Larger groups are better served by the full day split into two rooms.
Remote or on-site? +
Both work. Remote is fine for a single team and keeps costs down. On-site is better when two teams need to end up aligned, or when the room needs to talk to each other as much as to me. Travel is billed at cost for on-site outside Southern California.
What do you need from us beforehand? +
A 30-minute scoping call, and one honest answer: which weekly task eats the most time for the least reward. That answer becomes the thing we build. If your team can name it, the session more or less designs itself.
What if it does not work for our situation? +
The scoping call is free and I will tell you if I am the wrong person. I would rather lose a booking than run a session that was never going to land.
Tell me the task nobody wants to do on Fridays.
That is usually the one worth rebuilding. Thirty minutes on a call and I can tell you whether it is a good candidate, what the session would look like, and what it would cost.