From the service wall
scope, price, finish line
Focused sessions built around marketing, operations, product, and data teams.
The roster
sound familiar?
VPs and directors of marketing, operations, product, or data who want their own team using AI this quarter, not watching one more pilot from the sidelines.
The people on the hook for AI skills across the organization. A role-based session is the unit they can schedule, budget, and repeat, team by team.
Managers whose teams lose whole days to repeatable work. The workshop finds the pieces AI can carry and builds the first version in the room.
The finish line
what you keep
Proof
measured, not claimed
A real Role-Based AI Workshops engagement, led by the number that moved. We publish nothing we didn’t measure.
6 figures
Recovered in 8 months
Construction
A Chicago construction company started with an AI bootcamp and a workshop, then retained us to build the system the training pointed to. An automated invoice-chasing workflow delivered a six-figure return within eight months.
Job ticket
specifics, in writing
Job ticket
Role tracks
pick your lane
The team builds its brief-to-first-draft pipeline: campaign copy, variants, and repurposing workflows tuned to the brand voice, then reviewed the way real work gets reviewed.
The team picks its most repetitive process and builds the assisted version: intake, triage, drafting, and reporting with AI in the loop and a person signing off.
The team turns feedback piles into decisions: clustering user input, drafting PRDs, and pressure-testing specs with AI as the first reviewer, never the last.
The team builds analysis accelerators: query drafting, pipeline documentation, and a habit of checking AI’s work the way you’d check a new analyst’s.
Packages
no mystery pricing
One team, one focus, half-day or full-day. Fixed scope, agreed before we book the room.
A shared kickoff, then parallel tracks: every team builds on its own work under one roof.
A planned sequence across teams or quarters. One fixed scope per session, one calendar, no drift.
Numbers on the first call. No discovery-call maze.
After we ship
we answer the phone
We finish the playbook within days of the session, while the work is still warm. Want a longer runway? Thirty days of async support is available as a one-time add-on, priced on the first call: questions answered by the person who ran the room, not a ticket queue. (With bootcamps, that runway comes included.) And when a prototype earns its way toward production, you already know who to call.
Most AI training fails for a boring reason: it’s built for everyone, which means it’s built for no one. A marketing team doesn’t need what a data team needs, and both can smell a generic exercise a slide away. So we don’t run one workshop with the department names swapped. We build each track around the work your team did last week: the briefs, the tickets, the backlog. A short planning call gets us those samples, and the examples on screen are yours from the first minute.
The session itself is mostly building. We teach in short bursts and build in long ones, and everyone builds, managers included, because a manager who has shipped a workflow judges AI work differently forever after. By mid-session every person has something running. By the end, the team has working prototypes and something rarer: agreement on which ones are worth keeping, what good output looks like, and who owns what next. The first draft of that playbook gets written in the room, not promised in a follow-up.
We’re honest about what one day can do. A workshop won’t stand up production infrastructure; that’s what automation builds are for, and we’ll tell you when you’re ready for one. What a day can do is move a team from curious to competent on the work it already owns, with prototypes running and a professional habit of checking the output. Zero people replaced is still the stance. The team gets faster. The team stays.
When several teams need this at once, the multi-team day keeps it honest: one shared kickoff so everyone hears the same principles, then parallel tracks so nobody sits through another department’s examples. Same method, scaled sideways. And when one team wants more than a day gives, the bootcamp is the long version of exactly this.
FAQ
asked at the counter
Scope. A workshop is a half-day or full-day built around one team; a bootcamp is a multi-day program that trains several roles across the organization. If you’re not sure which fits, the first call settles it.
No. Every track is built around the work the team already does. The data track goes deepest technically, and even there we start from your current stack.
Your approved stack first, because a prototype your security team blocks is just a demo. If a genuine gap calls for a new tool, we’ll say so and explain why.
One intact team per track works best, because everyone builds and nobody watches. Larger groups become a multi-team day with parallel tracks, not a packed room.
Yes. Live remote suits half-day formats well; full days and multi-team days are worth doing on-site. Based in Chicago, traveling wherever your team is.
Your work shapes the session either way. On the planning call we collect work samples and agree with your security and compliance folks on what’s in bounds. Anything out of bounds gets a clean stand-in, and the workflow your team builds transfers all the same.
Working prototypes on their own tasks, a written playbook of what the team agreed to keep, and a shortlist of next use cases with owners. Nothing that lives only in slides.
For one team with a clear focus, often yes: the session, the playbook, and a shortlist of what to build next. If you want a longer runway, 30 days of async support is available as an add-on. And if prototypes keep turning into production requests, that’s a sign to talk about an automation build, and we’ll tell you straight.
In their words
I brought Dex in for workshops to get our consultancy team more comfortable with using AI, and the benefits of being able to work faster and sharper. He showed them some cool things they can do with Claude, plus tips and tricks, in person over two workshops. My team loved it and him. He's a funny guy!