Discovery Call Roleplay: 7 Scenarios to Practice 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.

Use the seven scenarios below with an SDR, AE, manager, or AI buyer. Each includes private instructions for the person playing the buyer, an observable pass condition, and questions for the debrief. Run the conversation once, review the evidence, then retry the moment where the rep lost the thread.

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 demonstrate. 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.

Seven buyer situations you can paste into Quotain

The examples below are buyer situations, not stages in a sales process. 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 explores 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 honestly 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 evaluation for the CRO and procurement, but managers have not agreed on the behaviors a rep must demonstrate.
• 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 explores 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 evaluating 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 explores 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 explores 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 justify 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 establishes 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 a normal coaching platform.”
• 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 establish 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 and explore one piece of current-state context without overclaiming.

Debrief

• How long did the rep take to answer?
• Did the answer establish 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 evaluate 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 explores 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 evaluate, 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?

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 specific and adaptive.

• Agenda and permission: Did the rep confirm the purpose of the call and earn permission to ask questions?
• Question quality: Did questions fit the buyer’s role and the context already provided?
• Follow-up depth: Did the rep move from a broad symptom to a specific workflow, behavior, or event?
• Listening: Did the next question respond to the buyer’s answer?
• Problem clarity: Could the rep summarize the problem, impact, and constraint in language the buyer recognized?
• Stakeholder map: Did the rep identify who experiences the problem, who owns it, and who would influence a decision?
• Response to pushback: Did the rep investigate the concern before answering it?
• Next step: Did both sides agree on an action, owner, and reason?

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 the scorecard is also used for conversation certification, keep the passing standard consistent across practice and live-call review.

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.

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.

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 evaluating software for this workflow, compare how different AI sales roleplay platforms handle buyer context, branching conversations, scorecards, and manager follow-through.

Common discovery call roleplay mistakes

• Making the buyer too cooperative. A buyer who answers every question clearly does not test discovery 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 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.

Build the next scenario around a real call

Choose one buyer, one pressure point, and one behavior your rep needs to improve. Write the hidden facts and pass condition before the session, then run the same difficult moment again after feedback.

To rehearse an upcoming deal, create a buyer-specific scenario and scorecard in Quotain.