Why a workshop first
Most AI training is a demo you forget by Friday. People watch someone else use a tool and go back to their inbox. I run it the other way: your team does the work in the room, on their own tasks, with their own data. The session that follows a clean pre-flight is the one that sticks, because people leave having already done something useful, not having watched.
How it works
Before (pre-flight, included).
I set up Claude on your real work ahead of time, so we do not lose the session to setup. This is part of the product, not an afterthought.
The session (half a day).
Your leadership team works on real tasks. A useful output in the first twenty minutes, then we build the first workflow together and set the rules: what AI is for here, what data goes in, what never does.
After.
You keep the brain we started, the first Skill we built, and a short roadmap of what to do next, by department.
From the executive room to the whole company
The executive workshop is where the leaders get it. The rollout is where the company does. After the session, the same work goes department by department, sales, operations, finance, so each team learns Claude on the work that eats their week. The workshop is step one of that path, not a one-off event. See the training and adoption rollout, and the Claude for Your Whole Team offer it leads into.
Proof
A nonprofit cut a grant application from eight hours to three after a single 90-minute session. That is the shape of a good workshop: one real task, measurably faster, the same day.
What you get
You leave with the brain, the first Skill, the rules, and the roadmap, all yours. Most teams take the next step into the Plan de Evolución, where every month the system does more than the month before.