Discovery Call Roleplay: 7 Scenarios to Practice Before a Live Call

Discovery breaks down when a rep stops at the first stated problem. A practical readiness standard asks whether the rep can qualify the buyer, uncover the business impact, and agree on a clear next step. Roleplay gives teams a controlled way to practice that depth before a live call.

Discovery call roleplay should train a rep to make decisions with incomplete information. The buyer may be rushed, vague, skeptical, or interested for reasons the rep has not uncovered yet. A useful exercise tests whether the rep can follow those signals without falling back on a question checklist or an early product pitch. If the rep cannot earn enough attention to reach discovery, start with cold-calling roleplay scenarios that isolate the opening moments.

Use the seven scenarios below with an SDR, AE, manager, or Quotain's AI buyer. Each includes private instructions for the person playing the buyer, an observable pass condition, and questions for the debrief. After the scenarios, you will find the discovery questions our own sales team uses, a copyable scoring rubric, and a way to score discovery against MEDDIC, SPICED, or your own framework.

TL;DR

• Give the rep only the context they could reasonably know before the call.
• Give the buyer separate private facts and clear rules for when to reveal them.
• Score one or two behaviors, cite the exact moment behind each score, and retry the weakest moment.
• A strong next step matches the buyer's commitment and names the action, owner, and reason.
• Score only the parts of your methodology that belong on this call. A first discovery call should not be graded on every letter of MEDDPICC.

How to run a discovery call roleplay

Assign three roles: seller, buyer, and observer. Give the seller the account context and objective; give the buyer a separate brief with the hidden facts and conditions for revealing them. The observer uses the scorecard and records exact moments for the debrief.

For a focused discovery segment, give the rep two minutes to prepare and run an 8- to 12-minute round. A full discovery-call rehearsal may take 15 to 20 minutes. Afterward, ask the rep to self-assess, add evidence-based feedback from the buyer and observer, then replay the weakest moment.

Set these five elements before each round:

• Buyer: role, company context, and disposition. Example: a Head of Sales Enablement at a SaaS company preparing for a new product launch.
• Known context: what the rep could reasonably know before the call. Example: the company is hiring 20 reps and preparing the sales team to sell to a new buyer.
• Hidden facts: information the buyer reveals only after a relevant follow-up. Example: the previous launch missed target, the CRO privately blamed poor rep readiness, and the enablement leader worries they will be held responsible again.
• Pressure: a constraint that shapes what the buyer can do. Example: the CRO wants reps certified before launch, while product marketing and frontline managers disagree on what a rep must show. The buyer cannot move forward until they have a defensible shared standard.
• Pass condition: the observable evidence that shows the rep completed the task. Example: the rep uncovers the previous launch failure, the buyer's personal stake, the disagreement over readiness, and the stakeholders needed to define a shared standard.

Score one or two skills per session. Keep the debrief to one or two actions the rep can apply in the immediate retry.

Run a short rep self-review

Before the manager gives feedback, ask the rep to answer four questions:

• What did I assume?
• Which buyer answer changed my next question?
• Where did I pitch before I had evidence?
• What exact moment will I retry?

The self-review shows whether the rep can diagnose their own conversation. The manager can then correct the diagnosis or add evidence the rep missed.

Copyable discovery roleplay template

• Rep brief: buyer role, known account context, call objective, and what the rep may claim.
• Private buyer facts: information the rep must earn through relevant follow-up questions.
• Opening line: the first thing the buyer says.
• Pressure: time, trust, priority, authority, or proof constraint that shapes the call.
• Reveal rules: the question or behavior that earns each hidden fact.
• Likely branches: how the buyer responds to pitching, shallow questions, and relevant follow-up.
• Pass criteria: observable evidence that the rep completed the task.
• Debrief: the exact moment to keep, change, and retry.

Seven buyer situations you can paste into Quotain

Choose the one closest to the conversation or behavior you want to practice. Each card separates what the rep knows from the buyer's private context and can be pasted directly into Quotain to create a simulation.

1. The buyer who took the call out of curiosity

Rep brief

You are speaking with a Head of Sales Enablement at a growing SaaS company. They accepted after seeing a post about discovery readiness, but there is no approved initiative and they are not looking for a demo.

Private buyer instructions

• Opening line: "I saw your post about discovery readiness. It sounded relevant, but I'm not convinced we have a broad enough problem to do anything about it."
• Hidden facts: Two frontline managers have independently raised concerns about shallow discovery in strategic accounts. One weak discovery call contributed to an opportunity stalling, and the CRO has asked whether the problem extends beyond one rep.
• Pressure: You will not involve the wider manager team or propose a readiness program until there is enough evidence that the pattern is real.
• Reveal rules: Mention the two manager concerns only after the rep asks what prompted your curiosity or requests a recent example. Reveal the stalled opportunity and the CRO's question only after the rep asks what happened and why it matters.

Likely branches

• If the rep starts pitching, ask for a deck and begin ending the call.
• If the rep asks broad questions, say the team is generally performing well and the concerns may be isolated.
• If the rep asks for a recent example and follows up on what happened, explain the stalled opportunity and the CRO's response.

Pass criteria

• Identify the repeated discovery behavior and the reps or deals affected.
• Uncover the stalled opportunity, the CRO's concern, and why the buyer has not acted yet.
• Agree on a proportionate way to validate the pattern, or conclude that there is not enough evidence to act.

Debrief

• Which answer changed the rep's next question?
• Where did the rep earn, or lose, the right to continue?
• Did the next step match the buyer's level of concern?

2. The buyer who asks for a feature tour

Rep brief

A sales enablement leader has researched Quotain and is comparing several tools. They open with a request to see scoring and reporting. The rep's task is to answer without letting the call collapse into a feature checklist.

Private buyer instructions

• Opening line: "Show me how scoring works. We are looking at a few tools, and I need to understand the feature set."
• Hidden facts: Managers use the same discovery scorecard but interpret it differently. Two reps were certified last quarter and then struggled in live calls. The CRO has asked you to explain what certification actually proves.
• Pressure: You need a defensible assessment for the CRO and procurement, but managers have not agreed on the behaviors a rep must show.
• Reveal rules: Share the certification problem only after the rep asks how scores are used, who trusts them, or what decision the reporting must support. Do not volunteer the CRO's concern unless the rep asks about the consequence of inconsistent scoring.

Likely branches

• If the rep refuses to answer, repeat the feature question and become impatient.
• If the rep launches into a full demo, ask about unrelated features and compare vendors.
• If the rep answers briefly and asks what scoring must prove, explain the failed certifications.

Pass criteria

• Answer the requested feature question clearly and briefly.
• Identify who uses the score and what decision it supports.
• Uncover why the current certification process is not trusted before choosing what to show next.

Debrief

• Did the rep acknowledge the requested feature before redirecting?
• Which question exposed the job behind the feature request?
• What should the rep show next, and why?

3. The buyer with a vague pain statement

Rep brief

A director of sales enablement says new reps ramp too slowly. The company recently shifted upmarket, but the buyer has not connected that change to a specific rep behavior. The rep must turn a broad symptom into observable evidence.

Private buyer instructions

• Opening line: "The new team is ramping slowly. We have onboarding, call recordings, and managers, but reps still struggle for the first few months."
• Hidden facts: The problem is concentrated in discovery calls with technical buyers. Reps accept vague answers, then demo too early because the onboarding examples still reflect the company's former buyer.
• Pressure: The VP of Sales believes hiring quality is the problem. You believe the training is outdated, but you cannot ask for budget without evidence that distinguishes the two.
• Reveal rules: Share the upmarket shift if the rep asks what changed. Reveal the early-demo pattern only after the rep asks about a recent call, what managers observe, or the exact moment the conversation breaks down.

Likely branches

• If the rep asks only about financial impact, say too many variables changed to isolate it.
• If the rep assumes the cause, challenge the assumption with an alternative explanation.
• If the rep asks for call-level evidence, describe the shallow follow-up and early demo.

Pass criteria

• Identify one observable conversation behavior and the cohort affected.
• Separate evidence from competing explanations.
• Clarify what the team would need to observe before choosing an intervention.

Debrief

• Which questions produced evidence instead of another hypothesis?
• Where did the rep assume causation?
• What evidence would distinguish a hiring issue from a training issue?

4. The buyer who cannot add another initiative

Rep brief

A revenue leader agrees that reps may not be ready for an upcoming product launch. The readiness problem is real, but reviewing and rolling out a new program would compete with the launch work already consuming frontline managers.

Private buyer instructions

• Opening line: "This is relevant, but the launch comes first. I cannot ask managers to add meetings or build a new program this quarter."
• Hidden facts: In an early design-partner call, two experienced reps failed to uncover the new buyer's approval process and gave the wrong demo. The CRO now wants every rep certified before launch.
• Pressure: Product marketing and frontline managers disagree on what readiness means. Any test must use launch work already underway and produce a shared standard without adding manager meetings.
• Reveal rules: Share the failed call only if the rep asks what made readiness urgent. Reveal the disagreement only if the rep asks how reps will be certified, who defines success, or what work managers are already doing.

Likely branches

• If the rep makes a generic time-saving claim, challenge it.
• If the rep manufactures urgency, say the launch already supplies enough urgency and begin closing the call.
• If the rep asks about the launch workflow, describe the design-partner call and the disagreement over readiness.

Pass criteria

• Learn what changed for reps and what failure has already occurred.
• Identify the stakeholders who must agree on readiness.
• Define the constraints of a small test, including what it must reuse and what overhead it must avoid.

Debrief

• Did the rep treat the launch workload as a design constraint or an objection to defeat?
• What constraint should shape the proposed test?
• Was there enough evidence to act now?

5. The buyer who has tried roleplay before

Rep brief

A director of sales enablement rolled out a roleplay or coaching tool last year. Adoption faded after the kickoff, and the buyer is wary of repeating the experience.

Private buyer instructions

• Opening line: "We have done roleplays before. People liked the launch, then managers stopped using the process and it became another item in the enablement library."
• Hidden facts: Reps completed generic scenarios every week, but managers received scores with no clear coaching action. You sponsored the rollout and were criticized for low adoption, so you are personally cautious about another broad launch.
• Pressure: You will consider only a small pilot with a named rep cohort, manager workflow, and evidence that practice changes behavior on live calls. Do not name the previous vendor.
• Reveal rules: Share the generic-scenario problem if the rep asks what reps practiced. Reveal your personal stake and pilot requirements only if the rep asks what made the rollout risky or what would need to be different this time.

Likely branches

• If the rep asks which vendor failed, decline to share.
• If the rep blames implementation or the buyer, become defensive.
• If the rep reconstructs the old workflow, explain where manager follow-through stopped.

Pass criteria

• Map what reps and managers were expected to do.
• Locate where the operating process failed without criticizing the buyer.
• Define what a limited pilot would have to prove before expansion.

Debrief

• Did the rep investigate without assigning blame?
• What failed: the exercise, the operating process, or both?
• What evidence would support a broader rollout?

6. The buyer who wants proof before sharing context

Rep brief

A senior sales leader is open to the category but will not discuss pipeline or coaching gaps until the rep earns credibility. The task is to give enough explanation to earn context, not to deliver a full pitch.

Private buyer instructions

• Opening line: "Before I get into our process, tell me how this differs from call recording or ordinary coaching software."
• Hidden facts: The team already records calls, but managers usually find discovery problems after an opportunity stalls. You were previously burned by an AI vendor whose simulations felt scripted, so claims about realism make you skeptical.
• Pressure: You will give the rep one concise answer to show relevance. If they evade the question or overstate what the product can do, you will keep company information private.
• Reveal rules: Share the delayed coaching problem after a clear category explanation and a relevant follow-up. Reveal the failed AI pilot only if the rep asks what proof you need or why realism matters.

Likely branches

• If the rep avoids the question, ask it again.
• If the answer becomes a product history or feature list, interrupt and ask for the distinction in one sentence.
• If the rep explains the practice-versus-review distinction and checks relevance, share the coaching delay.

Pass criteria

• Give a concise and accurate category explanation.
• Check whether the distinction matters to the buyer.
• Earn one piece of current-state context and ask a useful follow-up without overclaiming.

Debrief

• How long did the rep take to answer?
• Did the answer show relevance or list features?
• Which follow-up earned the buyer's context?

7. The buyer who will not commit to a next step

Rep brief

The discovery conversation was useful. The buyer described a real problem and asked thoughtful questions, but they are not ready for a demo or stakeholder meeting. The rep must find a useful, proportionate next action.

Private buyer instructions

• Closing line: "This was helpful. Send me something and I will take a look."
• Hidden facts: You need to check whether two frontline managers see the same discovery problem. There is no agreed internal owner or budget yet, and you do not want another vendor meeting until the issue is validated.
• Pressure: You will not accept a calendar hold for a generic demo. You will accept a short artifact that helps the managers assess the pattern, followed by a decision point you control.
• Reveal rules: Explain the manager validation step only if the rep asks what you need to learn internally or what would make the follow-up useful. Reveal the lack of owner and budget only if the rep asks how a decision would happen.

Likely branches

• If the rep pushes for a demo without a reason, decline.
• If the rep accepts "send me something," agree politely without committing.
• If the rep asks what the managers need to assess, request a short scenario or example you can share.

Pass criteria

• Identify the internal validation the buyer must complete.
• Agree on a useful artifact, owner, and decision point.
• Either earn a specific follow-up or close cleanly; a vague promise to check in does not pass.

Debrief

• What evidence showed interest without readiness?
• Did the next step match the buyer's commitment?
• What would make the follow-up useful to the managers?

Discovery questions our own sales team uses

Our own sales team sells to sales leaders and enablement teams, so the buyers in the scenarios above are close to the people on our own calls. We work from a written discovery guide. Its goal is to leave the call knowing the rep cohort, the conversation, the behavior, the current workaround, the consequence, the owner, and the smallest test worth running.

These are the ten questions we ask on almost every first call. Keep the structure and swap in your own buyer's problem.

Follow up on broad answers

When the buyer gives a broad answer, we work down this sequence until the answer is concrete:

1. What do you mean by that?
2. Can you give me a recent example?
3. What did the rep do?
4. What happened next?
5. How often does that happen?
6. Why does that matter?
7. What would good have looked like?

In a roleplay, the observer can use this sequence to score follow-up depth. A rep who stops after the first question has not reached the evidence.

Replace hypothetical questions with past behavior

Our guide tells reps to skip questions a buyer can answer politely without revealing anything, such as "What is your biggest sales challenge?" or "Would you use this?" Ask about something that already happened.

Use one sentence as the pass condition

By the end of a first call, our reps should be able to fill in every bracket of this sentence:

"[Cohort] needs to improve [observable behavior] during [specific conversation] because [trigger]. Today they prepare through [current process], which breaks at [failure point]. The consequence is [impact]. [Owner] would run the workflow, and [stakeholders] would need to trust [evidence]. The smallest useful test is [pilot] with success defined as [leading signal] by [decision date]."

If a rep cannot complete it, the guidance is to keep asking or to conclude that the opportunity is not ready. The same sentence works as a pass condition for a full discovery-call rehearsal: after the round, ask the rep to fill it in and check each bracket against the transcript.

Use an evidence-based discovery scorecard

A discovery scorecard should point to what happened in the conversation. Avoid labels such as "confidence" or "rapport" unless the reviewer can identify the behavior behind the score.

Score each criterion from 1 to 4 so there is no neutral midpoint: 1 means the behavior was absent or harmful, 2 means it fell below the standard, 3 means it met the standard, and 4 means it was precise and adaptive. The rubric below defines a 3 and a 1 or 2 for each criterion. A 4 meets the standard and adapts to something the buyer said that the rep could not have planned for.

Require one quote or timestamp for each score. End the review with one retry instruction tied to a precise moment. For example: "When the buyer says this is not a priority, ask what prompted them to take the call before discussing implementation."

If response to pushback is the weakest row, drill it on its own with objection handling roleplay scenarios before the next full round.

Pick a scale your reviewers can defend

Teams we interviewed disagree about the scale:

• One enablement leader scores onboarding roleplays from 1 to 4 and shares the scorecard with the new hire in advance, so nobody walks in guessing the standard.
• An SDR enablement leader uses a 1 to 5 rubric because performance is rarely black and white. Reps must score 80% on a final certification roleplay with their manager to advance.
• Another enablement leader called yes-or-no scoring too reductive and recommended a 4- or 6-point scale with no midpoint, with a behavioral example for every level.
• An enablement consultant who tested our discovery scorecard was comfortable with yes-or-no checkpoints for AI scoring, as long as each one was specific to the call.

A RevOps advisor who tested our scorecards saw a different problem: when a scorecard showed too many metrics or too many words, reps fixated on the number and missed the feedback.

Our recommendation: keep the 1 to 4 scale above while reviewers calibrate, define every level with behavior, and show the rep only the one or two changes that matter for the retry. Use the sales call scorecard calibration guide when several managers score the same call differently.

If the scorecard is also used for conversation certification, keep the passing standard consistent across practice and live-call review.

Score discovery against your methodology

A generic discovery rubric is a starting point. Most teams need it translated into the methodology they already use.

What we have seen:

• A fractional CRO we interviewed pointed out that teams use different methodologies: SPICED, MEDDIC, MEDDPICC, BANT, Sandler, or a custom one. They choose a framework for each client based on ACV and ICP, and noted that many fast-growing startups have not picked one yet.
• A sales coach suggested roughly 70% to 80% standard methodology and 20% to 30% company-specific priorities.
• An enablement consultant warned that MEDDPICC checklists get misapplied when every letter is expected on the first call. Asking about the contract process in a first discovery call is one example.

How to map your framework to a discovery rubric:

1. Name the methodology the team uses, or state that it uses none. With no methodology, the rubric above is enough to start.
2. For each element, decide which call it belongs to. Score only the elements that belong on this call, and leave the rest for later stages.
3. Turn each element into a behavior a reviewer can hear. "Critical event" becomes "asked what date or event makes the problem urgent, and got an answer."
4. Add the company-specific behaviors your managers already coach, such as how reps position a new product or handle a known competitor.
5. Use the same criteria in practice and live-call review so a rep is graded on one standard.

Quotain supports a shared methodology across simulations and real-call review. See sales methodology rollout if you are introducing a new framework.

Turn real call patterns into better roleplays

Call review can show where the team loses control: questions stay shallow, price appears too early, or the call ends without a mutual next step. Use that pattern as the behavior to practice, then build a buyer context that causes it to appear. For the full workflow, see how to turn sales call recordings into roleplay scenarios.

Remove details that identify the buyer or account. Give the simulated buyer a plausible motive, a reason to withhold information, and clear conditions for revealing it. Do not hand the rep the correct answer in the setup.

A manager can then turn a missed moment into the next drill and use the same evidence when reviewing the retry.

If you are comparing software for this workflow, use the AI sales roleplay buyer's guide to check buyer context, branching conversations, scorecards, and manager follow-through.

Build the roleplay from a live opportunity

One enablement leader we interviewed runs AE onboarding checkpoints on real deals. The new hire gets an actual CRM opportunity with the SDR's qualification notes and prepares the way they would for a real discovery call, including outside research on the account. A manager plays the CFO or controller. Because those managers are on live deals every week, they know which objections and pain points to raise, and they are free to be stubborn. The scorecard is shared in advance.

A sales productivity founder described the use case they wanted next: a junior rep whose deal has stalled rehearses the next call with a specific stakeholder, grounded in what the CRM already says about the deal.

To build that roleplay:

• Rep brief: the stage, the open questions, and the notes the rep would see in the CRM.
• Buyer brief: what the manager knows about the stakeholder's priorities, the objection most likely to come up, and a reason to withhold it.
• Pass condition: the one answer the deal is missing, such as who approves the purchase or what event sets the timeline.

Set how much the AI buyer knows and when it pushes back

Several practitioners gave us realism feedback about how the buyer behaved, on our discovery simulations and on other tools:

• A RevOps advisor said our early buyers felt like a manager quizzing the rep. They spoke perfectly, knew the product, and volunteered information. Real VP-level buyers are guarded and reveal information gradually.
• A sales productivity founder found the buyer over-informed. It raised deep objections before the rep had diagnosed any pain.
• An enablement consultant found that the buyer pushed back hard and fast, which matched what we had seen: simulated buyers can skew aggressive.
• An SDR enablement leader whose team stopped using another vendor's AI roleplay said its buyer never followed up on a vertical-specific capability, even after the rep raised it. The same leader said conversation trees that stay on rails feel like a survey.

The same RevOps advisor added a useful counterpoint. Articulate, cooperative buyers still help new reps learn industry language and get comfortable speaking. The enablement consultant suggested a path from low-stakes calls to certification-level calls, with the stakes visible before the rep starts.

What to put in the buyer brief as a result:

• Knowledge level and seniority: what the buyer knows about the category and your product.
• Pushback timing: when resistance starts, and what earns a calmer response.
• One topic the buyer must follow up on if the rep raises it.
• Difficulty: cooperative for a new hire's first rounds, guarded for practice, and certification-level only when the rep is ready.

Common discovery call roleplay mistakes

• Making the buyer too cooperative. A buyer who answers every question clearly does not test discovery skill.
• Making the buyer too informed or too aggressive. A buyer who raises deep objections before the rep has asked about pain tests the wrong skill.
• Giving the rep the hidden facts. The rep should have to earn important information with a relevant follow-up.
• Putting five skills into one scenario. Choose one primary behavior and, at most, one supporting behavior.
• Scoring every methodology element on the first call. Grade only what belongs at this stage of the deal.
• Scoring impressions instead of evidence. Record the phrase, question, or missed moment behind each score.
• Giving feedback without a retry. Practice the weak moment again while it is still fresh.
• Treating a booked meeting as proof of good discovery. A next step counts only when the buyer has a reason to take it.

Frequently asked questions

What is a discovery call roleplay?

A discovery call roleplay is a practice conversation with separate seller and buyer briefs. The seller works from known context. The buyer follows private facts, reveal rules, and likely branches. An observer scores what happened and identifies the moment to retry.

How long should a discovery call roleplay take?

Use an 8- to 12-minute round for one discovery segment. A full call may take 15 to 20 minutes. Keep the review focused enough that the rep can replay the weak moment during the same session.

What should a discovery roleplay scorecard measure?

Score agenda and permission, question quality, follow-up depth, listening, problem and impact (including the cost of doing nothing), stakeholder mapping, response to pushback, and next-step quality. Attach a quote or timestamp to each score so feedback points to evidence. If your team uses a methodology such as MEDDIC or SPICED, score only the elements that belong on a first discovery call.

What questions should a discovery call template include?

Cover why the buyer took the call, what changed recently, which people and conversation are affected, a recent example, how the team handles it today, where that breaks, how they define good, the consequence, who owns it, and what a small test would need to prove. Ask about events that already happened, since hypothetical questions get polite answers.

How do you make discovery roleplay realistic?

Keep the buyer's behavior consistent, hide facts until the rep earns them, and give the buyer a reason to resist. Build scenarios from recurring call patterns after removing details that identify the real buyer or account.

What is the best way to prepare for a high-stakes discovery call?

Build a short practice case from the account context, buyer role, meeting purpose, likely constraints, and the question the rep most needs to earn an answer to. Give the buyer private facts and resistance rules, use a scorecard shared before the attempt, then review and retry the hardest moment instead of rehearsing a perfect script.

Build the next scenario around a real call

To rehearse an upcoming deal, create a buyer-specific scenario and scorecard in Quotain. Start with one call, one pressure point, and one behavior to score. Then connect the result to real-call grading so the next practice assignment comes from live evidence.