What we train
People don't fail AI because they're stupid. They fail it because someone dropped a tool on their desk with a lunch-and-learn and called it enablement. We train against the real work: how to brief an agent, when to override it, what "good" looks like in your CRM, which automations you never touch, and which exceptions still need a human.
Two audiences, same firm:
- The business: leadership and ops owners: what to buy, what to skip, how to read a pilot receipt, where judgment has to stay.
- The employees: the people in the workflow: how to work with the agent or automation on Monday morning, without becoming the helpdesk for it.
Formats
Operator workshop
Half-day or full-day, live, on your stack. Small group. They leave having run the real workflow, not watched a demo.
Role playbooks
Short written rules per role: what the system does, what you still own, when to escalate. Sits next to the software.
Office hours
A time-boxed window after go-live so the first week of "wait, what does this button do" doesn't kill adoption.
Leadership briefing
One session for the people who have to defend the plan. No slides-as-the-deliverable. A coherent answer they can reuse.
How it sits with the rest of the work
Training is strongest when it's attached to something real. The best version: we built the agent or automation, then we train the team on that system. The second-best version: you already have tools, they're sitting unused, and you need the people trained before you buy more.
If the problem is "we don't know where AI belongs at all," that's transformation first, training second.
Fit / not a fit
Good fit
- A real stack (or a pilot about to go live) and people who have to use it
- Operators, not a 400-person all-hands
- Willingness to change how the job is done, not just attend
- A named owner on your side after we leave
Not a fit
- Inspiration keynotes and "AI for everyone" town halls
- Prompt-trick listicles dressed up as training
- No access to the actual tools the team uses
- Training as a substitute for building the system
Pricing signal
- Operator workshop: typically $3k–$12k depending on group size, depth, and whether it's on a system we built.
- Playbooks + office hours: scoped with the workshop, or as a follow-on after a Pilot.
- Bundled with Pilot / Run: often the right shape. The people who will own the system get trained as part of going live.
You get one number before we run it. We do not sell vague "enablement retainers." Detail: Services pricing.
FAQ
Is this ChatGPT training?
No. Generic chat-tool literacy is cheap and everywhere. We train on the agents and automations in your workflows, including when not to trust them.
Can you train a whole company?
We train the people in the workflow and the people who own it. Company-wide inspiration sessions are not the product. If you need a cascade, we train the trainers and leave the playbooks.
Do we need to have bought a system from you first?
No. We can train on a stack you already have, as long as we can see it. The best results are still when build and training come from the same team.
Remote or in person?
Both. Live, not pre-recorded. In person when the team is in one room and the work is hands-on enough to justify it.
The system is live. The team isn't.
Tell us who has to use it on Monday, and what they do today. We'll tell you if a workshop is the right next step.