Most teams treat discovery as a call. A rep, a prospect, a list of questions, and a demo waiting at the end of them. It looks like diagnosis, but most of the time it is a pitch wearing a lab coat: the rep already knows how the story ends, and the questions are just the runway to the product tour. A discovery workshop, run the way it should be, breaks that pattern. You put the buying committee in a room and co-build the problem definition and the success criteria before any demo, pilot, or proposal. That is diagnosis before prescription, and it is the difference between selling at someone and thinking with them.
It is also why real discovery still qualifies harder than any pitch. When the room agrees on the problem and on what solving it is worth, the serious buyers lean in and the tire-kickers show themselves early, long before a dead proposal would.
What is a discovery workshop?
A discovery workshop is a structured, cross-functional working session where a seller and the buying committee co-define the problem, align stakeholders, and agree on measurable success criteria before any demo, pilot, or proposal. Run before the solution rather than after it, it front-loads qualification, surfaces the real economic buyer, and reduces misqualified opportunities that would otherwise surface late.
| Best For | Account Executives and sales leaders running complex, multi-stakeholder deals |
| Deal Size | Enterprise (works down-market for any multi-threaded deal) |
| Difficulty | Medium |
| Funnel Stage | Discovery (before the demo, pilot, or proposal) |
| Impact | High |
| Time to Execute | Medium: booked within 10 business days of the first call, 60 to 90 minutes in the room |
| AI Ready | Yes: agenda personalization, pre-work drafting, real-time synthesis, recap and MAP generation |
Run this play when:
Don’t run this when:
Here is the quiet part: the offer itself is a qualifier. A buyer who will put four cross-functional people in a room for ninety minutes is telling you something real. A buyer who will not is telling you something even more useful, and a lot earlier than a dead proposal would.
This is a Motion play, so treat it like a short campaign with a clear sequence, not a single event. Five phases, roughly ten business days from the first discovery call to a co-owned outputs document. The goal of the motion is not to book a workshop. It is to run a diagnosis a demo could never replace. Roughly 63% of losses happen in discovery and qualification, not in the demo or the negotiation, so this is the play that attacks that number where it actually lives.
The offer is not a favor. It is a filter. Propose the workshop as a standard part of your evaluation, framed entirely around their outcome, not your product: before we show you anything, let’s get the right people in a room for ninety minutes and agree on the problem we are actually solving and what a win is worth. They leave with a requirements and success checklist either way.
“Who in your organization would need to be in the room for us to agree on the problem, and not just the symptom?”
What good looks like: A verbal commitment to a 60 to 90 minute session with the operational owner and the approver named, booked within ten business days of the first call. If you cannot get that, you have learned the deal is not real yet, which is worth knowing now.
Send a short pre-work questionnaire and an invite list by role. The pre-work is itself diagnostic. Who fills it out, who they add to the invite, whether finance shows: all of it is signal before the session even starts. The questionnaire is not a form. It is the first Open-Probe-Confirm loop, on paper.
What good looks like: At least four cross-functional attendees confirmed, including someone who can say yes to money. Two of the right people beat eight of the wrong ones.
Do not present. Facilitate. This is the phase where the whole play lives or dies, and the discipline is simple to say and hard to do: map the whole system before anyone talks features. What people tell you first is almost never the biggest thing. Every business is aimed at something, and it is rarely the first thing they say. Use Open-Probe-Confirm grounded in genuine empathy, and push past the stated ask to the structural cost underneath it.
“If we solved the thing you came in worried about and nothing else changed, what would still be broken six months from now?”
What good looks like: A problem statement written on the shared screen that the whole room agrees is the real one, not the first one. If the person who signs is in the room, you are already building the Economic Buyer and Metrics muscle that most teams only autopsy after the loss, the same discipline behind MEDDIC deal qualification, applied before the evaluation instead of after it.
Before anyone leaves, co-write three to five measurable success criteria, each tied to a number the business already cares about, and capture them in a one-page outputs document the buyer owns. Not “improve reporting.” Something like “cut the monthly close from nine days to four, measured by quarter end.” Buyer-owned. Measurable. Tied to money, not features.
“What would have to be true, and by when, for your CFO to call this an obvious yes?”
What good looks like: A co-signed requirements and success-criteria doc. The buyer leaves with something genuinely useful whether or not they ever buy from you, which is exactly what makes the exercise honest.
Send the recap, the mutual action plan, and the agreed criteria while the room is still warm. Now the demo, pilot, or proposal is aimed at the real problem and judged against criteria the buyer wrote themselves. Or you qualify out, on purpose, with a clean diagnosis instead of a slow fade. Either way the next step was co-designed, not proposed, which is why discovery-to-next-step conversion climbs when you run this well.
Take the objection seriously, because the fair version is true. Sandler has warned for years that a session which hands over the how is unpaid consulting: the prospect extracts your plan, thanks you, and buys nothing. So do not hand over the how. A real diagnostic co-defines what is broken and what success is worth; it does not give away your build plan. The buyer leaves clearer about their own problem and its cost, not holding your blueprint. That is why a real workshop qualifies instead of leaks.
The tell is investment. A real buyer puts real time and the right people in the room; a tire-kicker will not. In the consulting world a priced diagnostic, often between $2,000 and $6,000, does that filtering explicitly, and serious buyers treat it as normal due diligence. Most B2B SaaS workshops are unpaid, and that is fine: time and attendance are commitment enough. But the principle transfers. If a buyer will not invest a fraction of the deal size to diagnose the problem, whether that fraction is a fee or an hour of their economic buyer’s time, they were never a buyer. Price is one proxy for commitment; the workshop is another. Neither is a revenue grab; both are honesty tests.
Earlier in my career I spent time inside the enterprise value-engineering world: the structured value-workshop culture big software vendors built into their motion, where a cross-functional group quantifies a problem before anyone scopes a solution. The lesson that stuck was not the template. It was that the workshop was the qualifier. Ask a buyer to co-build the problem and the number solving it is worth, and the serious ones lean in while the tire-kickers evaporate, months earlier than a lost proposal would.
I made that my default move as an operator: walk in and diagnose the whole system before anyone talks solutions. A company I worked with brought me into a stalled enterprise deal the team was sure it understood. The champion had run a forty-five minute product tour, called it discovery, and swore the problem was reporting. I proposed a ninety-minute workshop and asked for the operational owner, someone from IT, and someone from finance in the room. Twenty minutes in, the reporting complaint fell apart: it was a symptom. The real cost was a manual reconciliation process quietly eating something like fifteen hours a week across two teams, and no one had ever put a dollar figure on it. Finance, in the room for the first time, priced it on the spot. That number, not the reporting request, became the deal, and the demo that followed was aimed at the problem that actually mattered. We did not create that clarity by pitching harder; we created it by diagnosing first.
Here is a real diagnostic workshop next to what most teams still call discovery. The gap is not effort. It is whether anyone in the room actually agreed on the problem before someone booked the demo.
| Metric | Target | What Most Teams Actually See |
| Stakeholders in the room | 4 or more cross-functional, including the economic buyer | One champion and maybe a plus-one; the signer never shows |
| The problem definition | Co-written and agreed in the room | Inherited from the champion’s first sentence |
| Success criteria | Measurable, buyer-owned, tied to a number | Vague, seller-authored, never revisited |
| Discovery-to-next-step conversion | Up roughly 15 points | Flat; the demo is the default next step |
| Misqualified opportunities | Down roughly 20%; tire-kickers self-select out | Found at proposal or late stage, after the work |
| Time to a real decision | Shorter; the criteria are already written | Open-ended, re-litigated on every call |
The middle two rows are the tell. Almost no team can point to a problem statement the buyer co-wrote or a success metric the buyer owns, which is precisely why so many demos land in a silence nobody books a follow-up to break.
“We don’t have time for a workshop.”
“That is exactly why we should run one. Ninety minutes now prevents weeks of back-and-forth aimed at the wrong problem. What does it cost to get three months into this and find out we solved the wrong thing?”
Time is the most common objection and the weakest, because the workshop is not additional work; it replaces the slow, expensive rework that happens when you skip it. Been there: the deals that felt too rushed for discovery are the same ones that die in a procurement loop nobody scoped.
“Just show us the demo.”
“Happy to, and it will be a far sharper demo if we first agree on the top two workflows and what a win looks like. Otherwise I am guessing at what matters to you, and you are watching features that may not.”
A demo with no agreed problem behind it is a product tour, and product tours are forgettable. When the buyer has co-defined the two workflows that matter, the demo stops being a broadcast and starts being an answer.
“This sounds like paid consulting.”
“It is a standard part of how we evaluate fit, and you leave with a requirements and success checklist either way. We are not handing you an implementation plan; we are making sure we are solving the right problem before anyone spends real money.”
Name it plainly and the worry dissolves. The buyer keeps the diagnosis, not the build plan, and that is a fair trade that signals confidence rather than desperation.
“We can’t get everyone in a room.”
“We do not need everyone. We need the person who owns the process and the person who owns the budget. Who are those two, and what would it take to get ninety minutes with them?”
The inability to assemble even two decision-makers is not a scheduling problem; it is diagnostic information about how real, and how prioritized, this actually is. Sometimes the block is logistics; more often the block is the answer.
“Leadership has basically already decided.”
“Then a workshop is the fastest way for us both to find that out. If we are a formality, let’s not waste each other’s time. If there is still a real problem to solve, let’s make sure it gets solved right.”
This is where truth-telling beats hope. Surfacing a done decision early costs you a deal you were never going to win and gives you back the weeks you would have spent pretending otherwise.
C-Suite and Economic Buyer: They do not want a workshop; they want a decision. Frame the ninety minutes as risk reduction: we will not scope a solution until we have agreed what the problem is worth. They show up for the number, not the agenda, so lead with the economics and let the process fade into the background.
VP and Approver: They own the outcome and the budget line. Bring them the success criteria to pressure-test, and make the workshop the place their priorities get encoded, so the eventual business case reads as theirs rather than yours. Cross-functional alignment is not a soft benefit here: aligned teams post materially higher win rates, on the order of 38% in recent benchmarks, and the workshop is where that alignment gets manufactured on purpose.
Director and Operational Owner: Usually your champion, and the person who feels the pain daily. Arm them to convene the room and sell up, but do not make them carry the economic story alone. That gap, between the person who feels the problem and the person who funds fixing it, is exactly where deals quietly stall.
SaaS and Technology: The buying committee is large and the problem is usually a workflow no single team owns end to end. Use the room to find the seam between functions, because that seam is where the real cost hides.
Financial Services: Governance-driven and multi-level. Map the decision and approval process inside the workshop itself, and expect the true success criterion to be risk or compliance exposure, not just efficiency.
Healthcare: Many stakeholders and legitimately slow cycles. Keep the workshop tight and outcome-first, and name the budget owner early, because clinical enthusiasm rarely reaches the person who signs on its own.
Manufacturing: Tie the problem to one line or one site and one hard operational number, downtime or throughput. The workshop’s job is to convert a vague complaint into that number, because the number is what travels up to the approver.
AI has quietly rewritten the economics of preparation. What used to take three hours, researching the account, drafting discovery questions, building an agenda, now takes about five minutes. AI will generate the questions, personalize the agenda by industry, and score the call afterward on half a dozen dimensions. For everyone. Which means asking good questions is no longer a differentiator. It is table stakes.
When every rep runs the same model against the same account, the signal is not where the edge lives; the interpretation is. We have pulled that thread before, and it holds here. The edge moved to the part of the room AI cannot reach: running it live, noticing the thing that is not in the transcript, reading the VP who went quiet the moment the number came up, knowing which soft answer to push on. Silence is data, and AI is bad at hearing it. That is the whole premise of the silent discovery rescue: the disengagement is the diagnosis, and only a human in the room can catch it in time to change the conversation.
There is a fresh wrinkle worth naming. The AI note-taker bot that silently joins the call to help does not put prospects at ease. A visible bot in a first workshop changes the room before anyone speaks; some people ask who it is, and some simply stop talking freely. The market’s 2026 answer has been to make the bot invisible: silent capture that records from your browser so the prospect never knows it is there. Sit with that for a second. The fix for a tool that flattens the human room was to hide it better, not to make the room more human. In a session whose entire purpose is a candid, cross-functional conversation, that trade deserves a decision, not a default.
This is also where persistent context earns its place. Walking into a workshop cold, re-deriving what you already learned last quarter, is its own kind of theater. A learning system that actually remembers the account, like Tempreon, means the hypothesis you carry into the room is informed by everything you have already heard from this buyer, not a blank CRM record and a rep’s fading memory. The workshop is where you test that hypothesis with humans; a persistent context system is what keeps you from starting from scratch every time.
Used with judgment, AI is genuinely useful for the parts of this play that are not the room:
Ready-to-use AI prompt for designing a diagnostic discovery workshop:
You are a diagnostic discovery workshop designer. I am running a 60 to 90 minute cross-functional workshop with a buying committee BEFORE any demo. Help me diagnose, not pitch. Inputs: - Account and industry: [ ] - What the champion says the problem is: [ ] - Who will be in the room (roles): [ ] - What I already know about this account: [prior notes] - The outcome our product actually drives: [ ] Output: 1) A hypothesis for the REAL problem that may sit upstream or downstream of the stated one, and why 2) The five questions most likely to surface it, sequenced Open to Probe to Confirm 3) Three measurable success criteria to co-write with the room, each tied to a business number 4) The disengagement signals to watch for live (who goes quiet, and when) that you cannot read from a transcript 5) A one-page outputs template: problem statement, success criteria, stakeholders, risks, next step Do NOT write me a product pitch. If the stated problem looks like a symptom, say so.
The model can design the room. It cannot run it. The judgment, the read, and the nerve to tell a buyer their stated problem is a symptom are still yours.
A discovery workshop is not a favor you give away. It is how you earn the right to prescribe, and how the buyer earns clarity they would have paid for.
If you remember nothing else: most discovery is a pitch wearing a lab coat, and buyers can smell it. Real diagnosis, done in the room with the people who feel the problem and the person who funds the fix, qualifies harder and builds more commitment than any demo ever will. So stop performing discovery. Run one.
If you have found a sharper way to design the room, I would genuinely like to hear it.
What is a discovery workshop in sales?
A discovery workshop is a structured, cross-functional working session where a seller and the buying committee co-define the problem, align stakeholders, and agree on measurable success criteria before any demo, pilot, or proposal. It replaces the traditional discovery call, which is often a pitch in disguise, with a real diagnosis built in the room with the people who own the problem and the budget.
Is a discovery workshop just free consulting?
No, as long as you run it correctly. A real discovery workshop co-defines what is broken and what solving it is worth; it does not hand over your implementation plan. The buyer leaves clearer about their own problem, not holding your build blueprint. The commitment required to attend, the right people and real time, is exactly what filters serious buyers from tire-kickers.
How long should a discovery workshop be, and who should attend?
Plan for 60 to 90 minutes with at least four cross-functional stakeholders, including the operational owner who feels the problem and the economic buyer who funds the fix. If you can only get two people, get those two. The workshop is worthless if the person who feels the pain and the person who signs the check are both missing.
What is paid discovery?
Paid discovery is a priced diagnostic engagement, often between $2,000 and $6,000 in the consulting world, that a buyer pays for before any solution is scoped. The fee filters out unserious buyers and signals that problem definition has real value. Most B2B SaaS workshops are unpaid, but the same principle applies: a buyer who will not invest a fraction of the deal size to diagnose the problem was never a real buyer.
How is AI changing discovery calls?
AI now generates discovery questions, personalizes agendas, and scores calls for everyone, which collapses prep from hours to minutes and makes asking good questions table stakes. The human edge has moved to what AI cannot do: running the room live, reading disengagement, noticing what is missing from the transcript, and knowing which answer to push on. AI designs the diagnosis; a human still has to run it.
About the Author
Brandon Briggs is a fractional CRO and the founder of It’s Just Revenue. He’s built revenue engines at six companies — including Bold Commerce, Emarsys/SAP, Dotdigital, and Annex Cloud — scaling teams from zero to eight-figure ARR and helping build partner ecosystems north of $250M. He now helps growth-stage companies fix the gap between activity and revenue. Connect on LinkedIn.
Part of the It’s Just Revenue Sales Plays Library — practical frameworks for revenue teams who want to stop the theater and start closing.