A working session with your team's real work in the room.
Someone on your team is probably already using Claude or ChatGPT to get through the week faster — quietly, on their own, with nobody else watching. A workshop is where we put that in the room with everyone: your documents, your actual workflows, not a slide deck about the future of AI. Everyone leaves having built or used something they'll open again Monday.
Start a conversation →30 minutesno deckbring a workflow or a question
Not a course. Not a keynote.
A workshop is a bounded working session, not an add-on training day. It only works if what we build in the room is something your team keeps using after we've left.
- A session built around the documents and workflows your team already has open
- Two halves — we teach against your real work first, then build something live
- Something everyone in the room is still using the following week
- A follow-up four to six weeks later, to catch what didn't stick
- A slide deck about "the future of AI"
- Generic examples that don't match anything your team actually does
- A one-off with no plan for what happens after we leave
- Someone from outside installing a tool your team never learns to run
Four formats. Half-day is where most teams start.
The strategy call helps decide which one fits your team and how much of the room's time is worth spending.
Every format includes the 30-minute strategy call up front and a written summary plus recording after. Standalone bookings also include a short review of the documents and processes your team uses, so we know what's worth building before we walk in. Priced per session — ask on the call.
Three phases. The room is the middle one.
Discovery sets the workshop up. The clinic makes sure it stuck.
Strategy call, then it depends where you're starting from.
If you've already run a Blueprint or a Busywork Audit with us, the discovery is done — we confirm priorities on the call and walk in ready to build. Coming in cold, we do a quiet read of the documents and processes your team uses first, enough to know what's worth building, not a full audit.
Teach, then build live.
The first half teaches the patterns we found against your team's own documents, not a generic example. The second half picks the highest-value workflow on the list and builds it live, with everyone watching and asking questions as it comes together.
We come back to catch what slipped.
Four to six weeks later, a 60 to 90 minute clinic checks what's actually being used. Some of it will have broken. We fix what's fixable and adjust the rest before the momentum from the room fades.
Not a feeling. A list you can point to.
Every workshop ships the same set, whatever the format.
What we keep hearing
Real things owners and team leads have said to us. If you find yourself nodding at one of these, we should talk.
“We’ve started doing that so many times. Innovation discussions always circle back to ‘we should,’ but nothing ever gets done. Institutional knowledge keeps walking out the door when people leave.”
“I want to be the leader who empowers my team to use AI well — actively shaping how they use it, not just observing it. But I feel like I don’t have the knowledge to teach them.”
“I’ve been building presentations with Claude myself because no one else on the team knows how. I’m the bottleneck, and I don’t have time to be the bottleneck. I just want this to work without me thinking about it.”
“I want our workflows tightened first, before we automate anything. Most of our process lives in my head, and that’s not scalable.”
Different firms, same shape underneath: the team is ready to use AI on the work that matters, and nobody has taught them how yet. That's what the room is for.
For
- Teams that were told to “figure out AI” and never shown how
- Places where one or two people are flying with AI and everyone else is stuck
- Companies that bought the tools and adoption never spread past the early adopters
- Leadership that wants to direct where this goes, not watch it happen to them
Not for
- Anyone who wants a generic AI class taught on generic examples
- Teams looking for one workshop and no follow-through after
- A room where leadership won’t show up
- Anyone who wants an outsider to install AI without the team learning to run it
Workshops stand alone, or sit inside something bigger.
Book it on its own, or fold it into a longer engagement.
Most of the workshops we run sit inside a longer engagement. If you've already worked with us on a Busywork Audit, the workshop is where the findings turn into something your team actually uses — we walk in with the priority list already written. If you want that discovery first — the interviews, the ranked plan, the governance starter — that's the Blueprint or the Implementation Partnership, and either one credits toward whatever you book with us next.
Bring a workflow. We'll build it in the room.
Start a conversation →30 minutesno deckbring a workflow or a question