Discovery Call: Uncover Real Pain and Business Impact

It helps you practice a sales discovery conversation where the buyer starts vague, polite, and slightly skeptical. The goal is to move from surface statements like "we need better visibility" to specific pain, business impact, and urgency. You also practice closing the call with a next step tied to what you uncovered. This is useful when the prospect sounds interested but has not yet named a real problem.

No, but it is written for a mid-market SaaS operations context. The same structure works for other B2B discovery calls where the buyer needs help articulating the cost of the status quo. If you sell into operations, RevOps, finance, IT, or enablement teams, the scenario will still feel familiar. You can customize the product, terminology, and business metrics to match your deal.

A sales manager, enablement lead, or the rep themselves can run it. It works well as 1:1 coaching, team practice, or self-directed repetition before a live call. Because the persona reacts to how the learner frames questions, it is especially useful for managers coaching reps on discovery depth. The rubric makes it easy to score the attempt and give specific feedback.

Use it whenever discovery calls are stalling at the surface level or before a high-stakes first meeting. It is also useful after a lost deal where the rep suspects they never uncovered the real problem. Many teams will revisit it during onboarding, before pipeline reviews, or when a rep needs to sharpen qualification. Repetition matters because discovery is a skill built through realistic reps and immediate feedback.

Ad-hoc practice often stops at generic questions and vague feedback like "ask better questions." This template gives you a concrete situation, a realistic persona, a learner objective, and behavioral rubric criteria so the rep knows what good looks like. That structure makes practice more consistent and easier to coach. It also helps the learner see whether they actually quantified pain and earned a next step.

Yes. You can change the company type, buyer title, pain points, and the level of skepticism to match your market. If your product is tied to a specific workflow, swap in the relevant operational details and metrics. You can also adjust the persona temperament to make the conversation easier or harder. The best customizations preserve the same discovery arc: surface need, implication, cost, urgency, and next step.

A strong attempt uses layered questions, not a rapid-fire list. The learner should acknowledge the buyer's surface concern, then ask about impact, frequency, workarounds, and consequences. Good attempts quantify the cost of the current process and connect it to business outcomes the buyer cares about. The call should end with a concrete next step, such as a follow-up with stakeholders, a demo tied to the pain, or a deeper assessment.

This template works well as a discovery-call module in onboarding, manager coaching, or certification practice. Start with one attempt, review the rubric, then have the rep retry with a sharper opening and better follow-up questions. You can pair it with other templates for objection handling, demoing, or pricing conversations to build a full sales practice path. It also fits neatly into a library organized by buyer stage.