Sales Discovery Call English Role-Play: Questions and Script

A discovery call is successful when both sides understand the problem, impact, desired result, fit, decision process, and next step. It is not successful merely because the seller asked many questions or delivered a polished pitch.

This guide teaches English conversation structure. Use your organisation's sales process, product claims, pricing authority, privacy rules, recording consent, and industry requirements during real calls.

Key takeaways

• Research enough to ask relevant questions without pretending you know the answer.
• Confirm purpose, time, and agenda at the start.
• Move from current process to problem, impact, and desired outcome.
• Clarify stakeholders, criteria, timing, and resources respectfully.
• Summarise before recommending or demonstrating.
• End with a mutual action, owner, date, and reason.

In this guide: call map | prepare | opening | current state | problem | future | decision | fit | summary | role-play | practice | FAQ

Discovery call map

Salesforce describes discovery as uncovering wants, needs, motivations, root problems, economic impact, stakeholders, resources, and approval process. HubSpot's current guide recommends researching the prospect, setting an agenda, qualifying fit, and establishing clear next steps.

The order should flex with the conversation. Do not interrogate the buyer through a checklist.

Prepare without writing a script

Review:

• The company, role, and market.
• Why the meeting was booked.
• Previous interactions and approved CRM notes.
• A likely use case, clearly labelled as a hypothesis.
• Product capabilities and non-capabilities.
• Typical implementation requirements.
• Questions that would determine fit.
• A possible next step if fit exists.

Write hypotheses as questions:

Weak:

"Your team is losing money because reporting is manual."

Better:

"I saw that your team expanded into three markets. Has that changed how reporting is collected or reviewed?"

Research should create relevance, not false certainty.

Open and agree the agenda

Use Time, Purpose, Agenda, Permission:

"We have thirty minutes. I would like to understand your current process, the result you need, and how you will evaluate options. If there is a fit, we can agree the next step. What would you add to that agenda?"

Other useful openings:

• "What made this conversation useful to schedule now?"
• "Before I describe our product, could I understand how the work happens today?"
• "Is there a decision or deadline this discussion should support?"
• "Who else will use the outcome of this call?"

Do not use rapport questions that feel disconnected from the buyer's time and purpose.

Understand the current process

Ask for a sequence rather than a general complaint:

• "Walk me through the process from request to completed result."
• "Which people or systems are involved?"
• "Where does information enter and leave the process?"
• "Which step takes the most time?"
• "What is manual, and what is automated?"
• "How do you measure whether it worked?"
• "What happens when there is an exception?"

Clarify terminology:

"When you say approved lead, what criteria must be true?"

Repeat the process map briefly so the buyer can correct it.

Find the problem and impact

Move from symptom to consequence without manufacturing fear.

Problem

• "Where does the process fail most often?"
• "What creates rework?"
• "Which step cannot scale?"
• "What have you already tried?"

Impact

• "Who is affected when that happens?"
• "How often does it occur?"
• "What time, cost, risk, or opportunity does it create?"
• "Which business result is delayed?"
• "What happens if nothing changes this year?"

Use only numbers the buyer can support. Do not convert a vague concern into invented ROI.

Summary:

"Today six people copy results into three systems. The process adds approximately six hours a week and delays the Monday report when one file is late. Is that accurate?"

Define the desired outcome

Ask what success looks like in use:

• "What should be different six months after implementation?"
• "Which metric should move?"
• "What must remain unchanged?"
• "Which users need to adopt the process?"
• "What would make the project not worth doing?"
• "What is the smallest useful result?"

Separate requirement from preference:

"Which capabilities are required for approval, and which would simply be useful?"

This prevents a later demo from becoming a tour of irrelevant features.

Clarify the decision process

Use respectful, transparent questions:

• "Who will use the solution?"
• "Who owns the budget?"
• "Who approves security, legal, or procurement?"
• "What criteria will the group use?"
• "Have you purchased a similar system before?"
• "What timeline is connected to the decision?"
• "What implementation capacity is available?"
• "Are you comparing other approaches, including doing nothing?"

Budget phrase:

"To avoid recommending an option that cannot pass approval, could you share the budget range or how funding is decided?"

Accept that the buyer may not know. Record the unknown and identify who can answer.

Test fit and disqualify honestly

Use Fit, Gap, Condition, Recommendation:

"We fit the need for automated qualification and weekly reporting. We do not currently provide the on-premise deployment your security policy requires. If that condition is fixed, we are not a fit for this project. If a managed cloud exception is possible, the next useful step is a security review."

Useful phrases:

• "Based on what you described, the strongest fit is..."
• "The limitation is..."
• "We would need to verify..."
• "This would require a partner or another product."
• "I do not recommend a demo until..."
• "It sounds as if the current process may be sufficient."

Honest disqualification saves both sides time and protects trust.

Summarise and confirm next steps

Use Current state, Impact, Desired outcome, Fit, Unknown, Action:

"Let me summarise. Your team manually combines three sources, which delays weekly reporting and creates duplicate review. You want one approved workflow before the November expansion. Our qualification and reporting features appear relevant, but security and data residency need verification. I will send the architecture note Friday, and you will invite security and operations to a thirty-minute review Tuesday. Is that the right next step?"

Every next step needs:

• Useful outcome.
• Owner on each side.
• Date and time.
• Required participants.
• Material to prepare.
• Condition for continuing.

Do not end with "I will follow up sometime next week."

Complete fictional role-play

Seller: We have thirty minutes. I would like to understand your current lead process, the result you need, and how options are evaluated. If there is a fit, we can agree a next step. What should we add?

Buyer: I mainly want to see the product.

Seller: I can show the relevant workflow, but first could you walk me through how a lead becomes sales-ready today?

Buyer: Marketing sends a spreadsheet. Sales checks every row manually.

Seller: Where does that process create the most difficulty?

Buyer: Duplicates and slow follow-up. It takes six hours each week.

Seller: What happens because follow-up is slow?

Buyer: Some leads contact competitors first.

Seller: So the immediate problem is duplicate review and delayed response, and the desired result is a faster approved handoff. Is that accurate? Who else defines the approval criteria?

Buyer: Sales operations and security.

Seller: The next useful step may be a workflow review with both teams rather than a broad demo. I can prepare an example using fictional data. Shall we schedule that for Tuesday?

Seven-day practice plan

Review your ratio of questions to pitches, the quality of follow-ups, and whether the next step follows logically from the evidence.

What real sellers and buyers commonly report

Recurring problems include sellers asking a list of generic questions without listening, pitching after the first pain point, and dragging the call after fit and next steps are already clear. Structure should support curiosity rather than replace it.

Non-native sellers also report preparing perfect questions but struggling with unpredictable answers. Practise summaries and follow-up stems, because discovery quality depends on what happens after the first question.

Where SpeakShark fits

SpeakShark can act as a fictional buyer with changing problems, authority, budget knowledge, objections, and fit. It cannot inspect your CRM, validate product claims, or approve pricing.

Use sales-call product demo English, international client meetings, and polite disagreement for later-stage conversations.

Related workplace speaking practice

• Project status updates
• Stakeholder presentations
• Deadline negotiation
• Customer escalation calls
• Remote-meeting phrases
• Promotion interviews
• English presentations
• Job-interview role-plays
• Daily speaking drills
• Free speaking-level test
• Overcome fear of speaking
• Best English speaking apps

Start a fictional discovery call, review whether each follow-up used the buyer's answer, then repeat with a poor-fit prospect.

How we researched this guide

We used current Salesforce and HubSpot discovery guidance for problem, impact, desired state, decision process, fit, agenda, and next steps. We separated vendor frameworks from our original teaching structure and did not reproduce proprietary scripts. Real calls must follow approved product claims, privacy, recording, and sales policy.

Sources

1. Salesforce discovery call guide, reviewed October 21, 2026 for pain, impact, wants, stakeholders, resources, agenda, and next actions.
2. HubSpot discovery-call questions, updated July 30, 2026 and reviewed for research, agenda, qualification, summaries, buying process, and next steps.
3. Salesforce prospecting questions, reviewed for pain, prior solutions, decision process, timeline, and budget questions.
4. HubSpot pre-call planning, reviewed for prospect context, questions, decision criteria, agenda, and action planning.

FAQ

Confirm the time, purpose, and agenda, invite additions, and explain that the goal is to understand fit before deciding on a next step.

Explore current process, problem, impact, desired outcome, prior attempts, urgency, stakeholders, criteria, resources, timing, fit, and next step without interrogating mechanically.

Explain why the range or process matters, ask neutrally, and accept that the buyer may not know or may decline to answer.

Combine current process, problem, impact, and desired state, then ask whether the summary is accurate and what important detail is missing.

Only when enough context exists to make it relevant. A focused follow-up demo can be better than showing every feature too early.

Use fictional data and unpredictable buyer answers. Practise follow-ups, summaries, honest disqualification, and mutual next steps without uploading confidential sales information.

SpeakShark details

• Site: speakshark.com
• Support: speaksharksupport@gmail.com
• Free tier: three AI conversation sessions per day with no card required

We are a speaking improvement tool. SpeakShark is not an exam preparation provider and is not affiliated with any employer, school, test provider, or any exam board. For official equipment, monitoring, identification, score, and test-day rules, go to the exam body, test provider, administrator, or invitation. Use SpeakShark to make your spoken English stronger, and use official material to learn the test.