How to Sell an AI Workshop to a Company (And Why It Beats a Cold Pitch)

- A workshop is a small budget decision, so it clears approval in days instead of quarters. That is the whole advantage.
- Sell the outcome, not the training. The deliverable is a shortlist of their own automations with effort and value attached, not a slide deck.
- Charge for the workshop and credit it against the first build. You get paid to write your own scope document.
The Short Answer
To sell an AI workshop to a company, pitch a half-day paid session that ends with a prioritised list of their own automation opportunities, price it in the low four figures so it fits a manager's discretionary budget, and offer to credit the fee against the first build if they proceed. You are not selling training. You are selling a decision document about their business, which is why it sells to people who would never approve a build project cold.
Why a Workshop Clears Approval and a Build Does Not
A build proposal asks a company to commit money to a thing that does not exist yet, which pushes the decision up to whoever owns the budget for new systems. That person is busy, risk-averse, and probably needs another meeting. A workshop asks for a much smaller amount out of a training or consulting line, and the person you are already talking to can usually approve it themselves. Same buyer, different door.
The second reason is that a workshop is easy to defend internally. Nobody gets in trouble for booking a session that helps the team understand what is possible. Plenty of people get in trouble for approving a build that then underdelivers. You are removing the career risk from the first yes, and the first yes is the only hard one.
| Cold build pitch | Paid workshop | |
|---|---|---|
| Who decides | Budget owner, often two levels up | The manager you are already speaking to |
| Typical time to yes | Weeks to a quarter | Days |
| What they are risking | A project that might fail | A half day of their team's time |
| What you learn first | Whatever they tell you on a call | Their actual systems, in the room |
| What you leave with | A maybe | A paid engagement and a scope document |
| Who writes the requirements | You, guessing | Them, out loud, with you facilitating |
The two doors into the same company
What You Are Actually Selling
The pitch that fails is a training session. Companies have been burned by generic AI training and they know a session about prompt tips changes nothing on Monday. The pitch that works names a deliverable that is specific to them and has a number attached to it. Something like: at the end of the afternoon you will have a ranked list of eight to twelve tasks in your business that can be automated, each with a rough effort estimate and a rough hours-saved estimate, and we will have built one of them in the room.
- The audit. A written list of their repetitive tasks, sourced from the people who do them rather than from the org chart.
- The prioritisation. Each item scored on effort versus hours returned, so the list is a plan and not a wish list.
- One thing built live. Small, real, and theirs. This single moment does more for the follow-on sale than anything you say.
- A short written recap. One page they can forward to whoever owns the budget, in their language, with their examples.
How to Price It So the Build Follows
Price the workshop so it is a small decision but not a free one. Free workshops attract audiences, not clients, and a company that paid nothing sends whoever is least busy. A paid session gets the people who actually run the processes into the room, which is exactly who you need in order to write a useful scope. Charge enough that it is taken seriously and little enough that it does not need a committee.
Then remove the last objection with a credit. Say plainly that if they choose to build anything from the shortlist within a set window, the workshop fee comes off the first invoice. Now the workshop costs them nothing in the scenario where it works, and you have been paid to write your own scope document in the scenario where it does not. Both outcomes are good, which is why this offer is easy to say out loud with a straight face.
- Quote one fixed price for a half day, all-inclusive. No day rates, no per-head pricing, no travel line items to argue about.
- State the credit in one sentence in the proposal, with a window on it. A window creates a reason to decide.
- Cap the room. Eight to twelve people, and name the roles you need present. Scarcity of seats is real here, not a tactic.
- Ask for the fee up front. A company that will not prepay a small workshop fee will not pay a build invoice either.
The Pitch Itself
Keep the outreach short and make it about a problem they have already said out loud. If they have posted a job for a coordinator whose duties are all copying data between systems, that is your opening line. The workshop is the offer, but the hook is always their own visible inefficiency, because that is the thing they have already decided is a problem.
Do not send a deck. Send four sentences: the inefficiency you noticed, what the session produces, how long it takes, and what it costs. A price in the first message is not aggressive, it is respectful, and it filters out everyone who was never going to pay. The people who reply to a message with a price in it are buyers.
Running It So the Build Is Obvious
Spend the first half of the session getting the room to describe their week honestly. The useful material is never in the process documentation, it is in the workaround someone invented two years ago that everyone now depends on. Ask what they do that feels like retyping, what they check twice because they do not trust it, and what happens when the person who normally does it is on holiday.
Then pick the smallest item with a real number behind it and build it while they watch. Narrate the judgement calls, not the keystrokes. When it works, do not oversell it. Say plainly what it does, what it does not do, and roughly what the properly built version would take. That honest boundary is what turns the room from impressed into ready to buy, because it tells them you are not going to promise the moon and disappear.
- Get the doers in the room, not just the managers. Managers describe the process as designed; doers describe it as performed.
- Write on a shared screen so the list is theirs by the end, not yours.
- Refuse to build the biggest item live. Pick something you are certain will work in the time available.
- Send the one-page recap within a day, while the session is still the most interesting thing that happened that week.
What to Do When They Do Not Buy the Build
Some companies will take the shortlist and do nothing with it for six months. That is fine, and it is why the workshop is paid. You have been compensated for your time, you have a written record of their priorities, and you are the person they call when the item at the top of the list finally becomes urgent. Follow up when the trigger appears rather than on a schedule, and reference their own words from the session.
The workshop also produces the asset most solo builders lack, which is a named company that will confirm you have worked with them. That reference clears the credibility bar for the next pitch even if no build ever followed, which means the offer is doing work for you long after the day itself.
Short, practical drops on offers, outreach, pricing, and closing clients with Claude Code. No spam, unsubscribe anytime.
Frequently asked
How much should I charge for a half-day AI workshop?
Price it as a small discretionary decision rather than a project. Low four figures for a half day is the range that gets approved by the manager you are already speaking to without needing a committee, while still being high enough that the company sends the people who actually run the processes. Quote one fixed all-inclusive number rather than a day rate, and offer to credit it against the first build.
Should I offer the workshop for free to get in the door?
No. A free workshop attracts an audience rather than a client, and a company that paid nothing sends whoever is least busy that afternoon. The fee is what gets the right people in the room, which is the entire reason the workshop produces a usable scope. Remove the risk with a credit against the first build instead of by dropping the price to zero.
What should the workshop actually deliver?
A ranked shortlist of automation opportunities sourced from their own team, each scored on rough effort against rough hours saved, plus one small thing built live in the room and a one-page written recap they can forward internally. The list is the product. Training content is not, because a session about general AI capability changes nothing on Monday.
Who should be in the room?
Eight to twelve people, weighted toward the people who perform the repetitive work rather than the people who manage it. Managers describe processes as they were designed, and doers describe them as they are actually performed, including the workarounds everyone depends on. Those workarounds are where the buildable opportunities are.
What if they take the shortlist and never hire me for the build?
You were paid, so the engagement was not a loss, and you now hold a written record of their priorities plus a named company you can reference. Follow up when a trigger appears rather than on a fixed schedule, and quote their own words from the session. A surprising share of workshop clients buy the build months later, when the top item on their own list becomes urgent.
Last reviewed August 17, 2026.

Co-founder of the Claude Code Profit Room. Built and sold AI services to real clients; writes about offers, pricing, outreach, and closing with receipts.
More from Duncan Rogoff →
