Discovery Call: Uncover Real Pain Beyond Surface Needs
Practice a mid-market discovery call that uncovers real business pain, urgency, and the cost of doing nothing. Use it to move a guarded operations lead from vague “efficiency” talk to a concrete problem worth solving.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Saas · B2b Services · Technology · Business Operations
Overview
This template is a sales roleplay for practicing a first discovery call with a mid-market operations lead who sounds interested but stays vague. The situation is built around a common early-stage sales challenge: the prospect says they want to improve efficiency and streamline workflows, but they have not yet named a real business problem, a measurable impact, or a reason to act now.
Use it when you want a rep to practice moving from surface needs to concrete pain. The learner should ask sharper situation questions, use implication questions to uncover consequences, quantify the cost or frequency of the status quo, and reflect back a clear problem statement before suggesting next steps. The persona is guarded and practical, so the rep has to earn detail instead of getting it handed over.
Do not use this template when the goal is product demo practice, pricing negotiation, or closing. It is also not the right fit if the prospect already has a well-defined use case and is ready for solution mapping. The value of this scenario is in the discovery phase itself: identifying what is happening now, why it matters, and what the business stands to lose by waiting. If the learner can finish with a crisp, validated problem statement, the call has done its job.
How to use this template
- Read the situation and learner objective so you know the exact discovery outcome the rep is expected to reach.
- Start the roleplay with Morgan’s opening line and let the learner lead the conversation with situation, implication, and quantification questions.
- Answer as Morgan in a guarded, practical way that rewards specific follow-up and gets more detailed only when the learner demonstrates real listening.
- Score the attempt against the rubric criteria, focusing on whether the learner uncovered impact, frequency, and a clear problem statement instead of pitching early.
- Review the missed moments, then retry the scenario with a tighter opening, better follow-up questions, and a stronger close.
Best practices
- Ask about the current workflow before asking about tools, because the learner needs context before they can diagnose pain.
- Use implication questions that connect the issue to time, risk, revenue, or team friction instead of stopping at surface inconvenience.
- Quantify frequency and scope with plain language such as “how often,” “who else is affected,” and “what happens when this slips.”
- Reflect back the prospect’s words before moving on so the persona can confirm, correct, or deepen the pain.
- Avoid pitching features until the prospect has named a problem that is specific enough to justify a solution discussion.
- End the call with a problem statement the prospect would recognize, not a vague promise to follow up later.
- Keep the tone curious and practical; Morgan should feel like a busy operator, not a theatrical objection machine.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What kind of discovery call is this template for?
This template is for a first discovery call in a mid-market SaaS sales motion. It focuses on moving past broad statements like “improve efficiency” or “streamline workflows” and into specific pain, impact, urgency, and current process. It is best when the prospect is polite but vague and you need to earn a real problem statement before pitching.
Who should run this roleplay?
A sales manager, enablement lead, or the rep themselves can run it. It works well for new account executives practicing discovery fundamentals and for experienced reps who want tighter questioning and better problem framing. The persona is designed to push back just enough to reveal whether the learner is listening or rushing.
How often should a team use this scenario?
Use it during onboarding, before live call practice, and anytime discovery quality starts slipping into feature pitching. It also works as a recurring drill when reps are preparing for a new segment or product line. Because the scenario is repeatable, teams can run multiple attempts with different opening lines and still score against the same rubric.
What makes this different from an ad-hoc mock call?
An ad-hoc mock call often turns into a loose conversation with no clear scoring standard. This template gives you a concrete situation, a realistic persona, a learner objective, and behavioral rubric criteria so the rep gets specific feedback on what they asked, what they missed, and whether they defined the problem clearly. That makes practice more consistent and easier to coach.
What should the learner be trying to accomplish by the end?
The learner should leave the call with a clearly defined problem statement, not just a list of vague needs. That usually means identifying the current workflow, the pain it creates, how often it happens, who feels it, and what it costs the business in time, risk, or missed outcomes. A strong ending also includes a concrete next step tied to the uncovered pain.
What are the most common mistakes this template surfaces?
The most common mistake is jumping to solutions before the prospect has named a real problem. Reps also tend to ask broad, generic questions, fail to quantify frequency or impact, and miss chances to reflect back what they heard. Another common issue is ending the call with “let’s keep talking” instead of a specific next step tied to the pain they uncovered.
Can this be customized for different products or segments?
Yes. You can swap in your own product context, industry language, pain points, and buying triggers while keeping the same discovery structure. For example, you can adapt the persona from operations to finance, HR, or customer support, as long as the learner still has to uncover situation, implications, and cost before proposing a fit.
Does this template work with CRM or call-coaching workflows?
It can be used alongside call coaching, scorecards, and CRM review, but the roleplay itself is focused on practice rather than system integration. Many teams pair it with a coaching rubric or post-call reflection so managers can compare the learner’s attempt to real discovery calls. That makes it useful both for training and for reinforcing live-call habits.
What should I look for when scoring attempts?
Score whether the learner asked specific situation questions, used implication questions, quantified the status quo, and reflected the pain back accurately. Also check whether they resisted the urge to pitch too early and whether they ended with a clear problem statement or next step. The best attempts sound curious, grounded, and commercially useful rather than scripted.
Related templates
Ready to use this template?
Get started with MangoApps and use Discovery Call: Uncover Real Pain Beyond Surface Needs with your team — pricing built for small business.
