AI training for teams that have real work to do
Five live sessions, built on the work your team already does. We teach the tools we build with — Claude and Claude Code, fundamentals before features — then walk through building the helpers and automations your own week needs. Everyone leaves with something running, not a subscription and a story about how they tried it once.
What your team can actually do afterwards.
No fixed curriculum, because the sessions are built around your work rather than ours. This is what the program is for.
Hours come back, starting the first week
We do not begin with what AI is. We begin with the report someone rebuilds every Monday, the proposal that gets rewritten for every job, the inbox that swallows an afternoon — and we fix one of them live, in the first session, with the person who owns it. The rest of the program compounds from there.
It runs on your work, not a demo
Your documents, your customers, your pricing, your tone. Generic training produces people who are impressed and unchanged; the moment someone watches their own task get done in four minutes, the argument is over and the habit starts. That is the entire difference between a webinar and a working session.
One assistant per role, not one chat box for everyone
A blank text box is not enablement — it is a spreadsheet program with no spreadsheet in it. Each person ends the program with an assistant configured for their actual job: what it knows, what it drafts, what it is never allowed to decide.
Judgment stays with your people
We are direct about where these tools fail — confident wrong answers, invented numbers, quiet drift in tone — and we build the checkpoint into every workflow before it ever touches a customer. Teams that learn the failure modes early are the ones still using this in a year.
It survives the person who loved it most
The usual outcome of AI adoption is one enthusiastic employee doing impressive things and everyone else opening the app twice. We write the playbook in your language — the prompts, the workflow, the guardrails — so the capability belongs to the company and not to whoever happens to be curious.
What we cover
We teach the tools we build with, in the order they become useful: fundamentals before features, features before anything is left running unattended. The last two are the ones your team builds themselves, on their own work, while we are in the room.
Claude, and the fundamentals under it
What the model is actually doing, where it is strong, and how it fails — invented figures, confident nonsense, a slow drift in tone. Everything after this rests on being able to tell a good answer from a plausible one, so it comes first.
Claude Code
For the people who touch files, data, and systems: running real work in a terminal or a repository instead of pasting between windows. This is usually where an operations person stops needing a developer for every small thing.
Connectors
Attaching Claude to the systems the work already lives in — email, calendar, files, the CRM — so it stops being a box you paste into. What it may read and what it may never touch gets settled before anything is connected.
Skills
Packaging a process you repeat — the quote, the weekly report, the intake summary — so it runs the same way every time, in your language, whoever asks for it. This is the piece that turns one person's knack into a company asset.
Artifacts
Turning an answer into something the rest of the team can actually use: a document, a checklist, a calculator, a small internal tool. Work that ends as a chat message is work nobody else can find next month.
Projects
A workspace per role, client, or service line that already holds your documents, your tone, and your standing instructions. Nobody should have to re-explain the business every morning before they can get an hour back.
Cowork
Handing longer, multi-step work to an agent that keeps going while your team does something else. We are specific about where the human checkpoint sits, because unattended work is exactly where an unreviewed mistake travels furthest.
The helpers your week needs
Then we build, live, with the person who owns the task: the assistant for the Monday report, the proposal drafter, the inbox triage, the call-notes-to-CRM step. Each one is configured for a real job — what it knows, what it drafts, what it is never allowed to decide.
Custom automations, tools, and workflows
The ones that run without anyone opening a chat window: triggered or scheduled, connected to your systems, logged, and loud when they fail. This is where the hours stop depending on somebody remembering to ask.
Who it’s for
- Owner-operated and mid-market teams, roughly five to a few hundred people
- Operations, admin, finance, and marketing staff drowning in repeated work
- Leadership teams who have bought licences and seen no change
- Professional services and healthcare organizations with real confidentiality constraints
What you keep
- A configured assistant per role, built during the sessions on your own material
- A prompt library written in your language, not a generic pack
- A written internal playbook new hires can follow
- Session recordings and reference guides
- The Projects, Skills, and connectors set up in your own workspace during the sessions
- A check-in thirty days later, against hours actually returned
The case for this program, at length: Nobody at a Ten-Person Company Has Time to Be Trained
Also offered: Sales Training — same price, same format. Most teams take both.
Tell us you’re interested and we’ll be in touch.
Leave your details and a partner replies personally — usually within a business day — with dates that work and a couple of questions about your team. Nothing is booked and nothing is owed until you say so.
- Program
- AI Training
- Format
- 5 live 90-minute sessions
- Price
- $3,000