How much to charge for an AI workshop
How much to charge for an AI workshop comes down to one question: what will this team do differently the week after, and what is that worth to the business? Nobody books a workshop because they want a workshop. They book it because a piece of work is slow, a manager has seen what Claude Code can do, and they want their own people doing it. That change has a price the client can already feel, in the hours a task takes or the backlog it creates. Quote a fixed fee that is an obvious fraction of that number, built around one workflow the team leaves with running, in three tiers. Do not quote a day rate. The moment you say "a full day is this much," you have told the client your ceiling and invited them to ask for a half day.
This is the CCC Change-Value Method, and it exists because the workshop is the offer that new Claude Code builders underprice the most. It feels like teaching, teaching feels like a day rate, and the day rate feels like it should be modest because you are not shipping code. But a room of people who go back to their desks and run one workflow with Claude Code every day is worth more to that company than most of the builds you will sell them, and the workshop is also the cheapest possible way for a company to find out whether it wants you on retainer. Price it like the front door it is.
Find out what the team has to do differently before you say a number
You cannot price a workshop until you know what it is meant to change, so the first call is a measurement, not a pitch. Five questions get you there, in this order, because each one makes the next easier to answer honestly.
- What is the task you want this team doing with Claude Code by the end? Writing the internal tools they currently request from engineering, cleaning the weekly report, drafting the client proposals. If the answer is "using AI," the workshop is not defined yet and the price has to include defining it.
- How do they do it now, and what does that cost? Let the client say it. A task that takes someone most of a day each week has a cost in that person's salary, and the client knows it. Your quote is going to sit next to that number.
- Who is in the room, and are they all doing the same job? Ten people who share one workflow is a workshop. Ten people from four departments is four workshops, and the price should say so.
- What do they already have? Whether everyone has a Claude plan that includes Claude Code, whether the desktop app is installed, and whether anyone on the team has used it changes the day completely. The [day-one setup](/blog/claude-code-day-one-setup) is either pre-work or the first hour of your session, and it is priced either way.
- What happens on Monday? Who checks that people are actually using it, and what does the manager want to see in a month? If nobody owns this, the workshop will evaporate, and the honest quote includes the follow-up that stops that.
Say the answers back before you quote. "So the goal is that the ops team builds their own reporting scripts in Claude Code instead of waiting on engineering, and that wait is currently costing you roughly this a month" is a sentence the client has to agree with, and once they have, your price is a fraction of a number they already accepted. The full question set I run on every deal is in [client discovery questions before you quote](/blog/client-discovery-questions-before-you-quote).
Define the workshop as one workflow out the door, or it becomes a demo
The CCC One-Workflow Rule: an AI workshop is one team, one task they do by hand today, and by the end of the session that task is running in the Claude Code desktop app on their own machines with their own files. That sentence is the scope. If the client cannot name the task, the workshop is not ready to be booked, and the price should cover the discovery that gets it there. If they can, everything outside that sentence is a second session, priced as one, and written on the proposal as a second session so nobody is surprised.
This rule is what makes the fixed fee safe, and it is also what makes the workshop work. A session that tours every Claude Code feature produces a room of impressed people who change nothing. A session where each person leaves with the desktop app open, a project folder set up, and one real task done in it produces a habit. Teach the desktop app, keep the terminal optional, and make the last hour hands-on with their actual work. [How to sell AI builds to non-technical clients](/blog/sell-ai-to-non-technical-clients) has the language for the room; the same rule applies to the manager who booked it.
The CCC Workshop Price Ladder: three tiers
Present three tiers, all built around the same workflow, and let the client pick how much change they want guaranteed. The bottom tier is for a manager who wants their team to see it work. The middle is for a manager who wants their team to keep doing it. The top is for a company that has already decided and wants the next team queued up.
The CCC Workshop Price Ladder
| Tier | What the client gets | How to price it |
|---|---|---|
| Session | One group, one sitting, one workflow. Setup check at the start, the workflow built live on their files, every person leaving with it running. A recording and a one-page recap | A fixed fee that is a small, obvious fraction of what the workflow costs them today. Priced so a manager can approve it without a second meeting |
| Sprint | Everything in Session, plus pre-work: you get their real files and processes a week before and build the workflow so the day starts from something that works. Plus two weeks of follow-up, a short office-hours call and a shared channel for the questions that only appear once they are using it | The anchor tier. Priced against the workflow sticking, not the session happening. Most clients land here once they see the difference is the follow-up |
| Rollout | Everything in Sprint, plus a setup of the team's shared Claude Code instructions and project templates so every new session starts the same way, and a second Session for the next team. A handover of the material at the end | Priced for the company that has already decided. This tier is what becomes the retainer, because someone has to maintain those shared instructions as the work changes |
The middle tier wins because of the follow-up. A session proves that Claude Code can do the task. Two weeks of questions and a working setup on everyone's machine proves that this team will keep doing it, and that is the change the manager is actually buying. Put the difference in the table and they will choose it themselves. The three-tier shape is the same one in [how much to charge for a chatbot](/blog/how-much-to-charge-for-a-chatbot), [how much to charge for an AI automation](/blog/how-much-to-charge-for-an-ai-automation), and [how much to charge for an MVP](/blog/how-much-to-charge-for-an-mvp); the tiers change, the logic does not.
What moves a workshop quote up or down
- Seats. More people means more hands-on time and more setup problems on the day. Price by group, with a cap, and quote a second group as a second session rather than squeezing thirty people into a room built for twelve.
- Pre-work on their real material. Building the workflow on the client's own files before the day is the single thing that separates a demo from a change, and it is priced as work, because it is. If they cannot share files in advance, say so on the quote and price the Session tier only.
- Setup state. A team with plans, the desktop app installed, and a shared folder ready is a workshop. A team with none of that is a setup engagement plus a workshop, and the setup has its own line. [Claude Code desktop app](/blog/claude-code-desktop-app) is what I send the client's IT contact a week before, so that line is as small as possible.
- On-site or remote. Travel is a line item, never absorbed. Remote sessions are shorter and more of them, and the price reflects the format, not the location.
- Who is in the room. Practitioners want the workflow. Leadership wants to know what to ask for and what it costs; that is a different, shorter session with a different price, and putting both groups in one room serves neither.
- Recording and material rights. If the client wants to reuse your recording and slides internally for people who were not there, that is a licence, and it is priced separately from the day.
- The follow-up window. Two weeks is the default. A month, or a second office-hours call, moves the Sprint price up, and it is worth it to the client because that is where the habit forms.
- Whether it feeds a build. If the workshop is the discovery for a project you will then quote, price it like [paid discovery](/blog/paid-discovery-phase-ai-projects), and say on the proposal that the fee is credited if they go ahead.
The mistakes that turn a paid workshop into a free lunch-and-learn
- Quoting a day rate. "A full day is this much" becomes the ceiling and the half-day request arrives within the hour. Talk about the workflow and the change, nothing else.
- Doing the first one free to "show value." A free session is a demo, and the company will treat the next one like a demo too. If you want a low-risk way in, sell the Session tier small, not free; [the "can you do it cheaper" objection](/blog/can-you-do-it-cheaper-objection) has the words.
- No pre-work. If the first hour is people installing the desktop app and finding their login, you have sold a setup session at workshop prices and delivered a bad one. Send the setup a week ahead, and check it.
- Touring features instead of doing the task. The room applauds, nobody changes. One workflow, on their files, running on their machines, or it did not happen.
- Letting the follow-up become free consulting. Two weeks of questions about the workflow is included. A new workflow, a build request, or a second team is a new line, and the retainer conversation, not a favour.
- Handing over the material without a licence. Your slides and recording are the product a second time. Price the internal reuse, or keep it.
- No deposit. A workshop is a date on a calendar and a room full of people whose time has been booked. [How much deposit to charge before an AI project](/blog/how-much-deposit-to-charge-before-an-ai-project) covers the number; for a dated session it is the full fee before the day.
How to present the workshop number so it closes
Lead with the change you agreed on, then put the three tiers under it. "You said the goal is that your ops team builds their own reports in Claude Code instead of waiting on engineering, and we agreed what that wait costs; here are three ways to make that happen" is a sentence a manager can say yes to on the call, and it is a sentence they can repeat to their director without you in the room. Send it as [a one-page proposal](/blog/one-page-ai-proposal-that-closes) with the workflow written in one line, the tier scope, the pre-work you need from them and the date you need it by, the date of the session, and the follow-up window with an end date. [How to package an AI service](/blog/how-to-package-an-ai-service) is how the same workshop becomes an offer you can sell to the next company without rewriting it.
The push-back you will hear is "can't they just watch some videos" or "our engineering team could run this internally." Both are answered by the change: videos do not put the workflow on anyone's machine, and engineering has the backlog the workshop exists to relieve. If the objection is really about budget, the honest answer is the Session tier, and ["let me think about it"](/blog/let-me-think-about-it-objection) covers the stall that follows a workshop quote more than any other, because a date on a calendar feels bigger than a build that starts whenever.
Quote your next workshop against the change, not the day
A workshop is the best front door in this business when it is priced right and the cheapest day you will ever sell when it is not. Get the workflow and its cost from the client, write it in one line, quote the ladder, take the fee before the date, and put an end date on the follow-up. The company whose team is now using Claude Code every day needs the shared instructions maintained, the next team trained, and the first real build scoped; [how to turn a one-off client into a monthly retainer](/blog/how-to-turn-a-one-off-client-into-a-monthly-retainer) is what that conversation looks like, and [the memory engineering retainer](/blog/selling-claude-code-memory-engineering-retainer) is the shape it usually takes.
Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.
Frequently asked questions
How much should I charge for an AI workshop?
Price it against the change it produces, not the hours. Find out the one task the team should be doing with Claude Code afterwards, get the client to say what that task costs them now, and quote a fixed fee that is an obvious fraction of that number, in three tiers: Session, Sprint, and Rollout. Never quote a day rate; it becomes your ceiling the moment you say it.
Should I charge per person or per session for an AI workshop?
Per group, with a cap on seats, and quote a second group as a second session. Per-person pricing invites the client to trim the list, and the value of the workshop is that a whole team changes how it works, which does not scale down neatly by headcount.
What should an AI workshop include?
One workflow out the door: one team, one task they do by hand today, running in the Claude Code desktop app on their own machines with their own files by the end. A setup check at the start, the workflow built live, a recording and a one-page recap. Pre-work on their real material and a follow-up window belong in the Sprint tier; shared instructions, templates, and a second team belong in Rollout.
Should I run the first AI workshop for free to win the client?
No. A free session is treated as a demo and the next one will be too. If you need a low-risk entry, sell the Session tier small rather than free, and if the workshop is really discovery for a build you will quote afterwards, price it as paid discovery with the fee credited if they go ahead.
How do I stop a workshop from turning into free consulting afterwards?
Put an end date on the follow-up window and write what it covers: questions about the workflow you taught, for that team, for that period. A new workflow, a build request, or a second team is a new line on a new proposal, and that is the start of the retainer conversation, not a favour you owe.
Last reviewed by Duncan Rogoff on September 28, 2026
