Core Skills
Discovery Call Templates
A structured discovery call flow with MEDDIC-aligned question sets, plus weak-vs-strong examples and a copy-ready script you can adapt to any first meeting.
is the highest-leverage call in the cycle — every later step inherits the quality what you uncovered here. Weak discovery sounds like a feature interview. Strong discovery sounds like a business diagnosis: you leave the call with quantified , named decision-makers, a sense of the , and a confirmed .
This module gives you a structured call flow, a -aligned question set, two contrasting examples, and a one-page script you can copy into your or notebook.
Discovery call flow
How to use this template
- Send the 24 hours before the call so the buyer can pre-align internally.
- Aim for 70/30 talk ratio: the buyer talks more than you do.
- Capture exact phrases the buyer uses — re-use them in the follow-up email and exec summary.
- Never end without a confirmed, calendared .
Link it back to the broader frameworks: every question maps to a letter, and the follow the SPIN model.
Discovery Call Script — 30 to 45 minutes
Adapt the bracketed parts before the call
# DISCOVERY CALL — [Account Name] Date: [date] Attendees: [names + roles] Goal: Validate fit, quantify pain, confirm decision process, secure next step. ## 1. OPENING (3 min) - "Thanks for the time. I have us for [X] minutes — does that still work?" - "Here's what I'd love to cover: (1) understand how [team] runs [process] today, (2) where the friction is, (3) what good looks like, (4) agree on a sensible next step. Anything you want to add?" - "Before we dig in — what made you take this meeting?" ## 2. CONTEXT & CURRENT STATE (8 min) - Walk me through how [process / workflow] works today, end to end. - Who owns each step? How long does each take? - What changed in the last 6–12 months that put this on your radar? - What have you already tried? What worked, what didn't? ## 3. PAIN & IMPLICATIONS (10 min) — MEDDIC: Metrics + Identify Pain - When [problem] happens, what's the downstream impact on [revenue / cost / risk]? - How often does it happen? What does each instance cost you? - If nothing changes in the next 12 months, what's the business impact? - Who else inside [Company] feels that pain? Whose number is it tied to? ## 4. FUTURE STATE & CRITERIA (8 min) — MEDDIC: Decision Criteria - If we solved this perfectly, what would be different in 90 days? In a year? - What does "good" look like — what would you measure? - What's a non-negotiable for any solution? What's a nice-to-have? ## 5. DECISION PROCESS (8 min) — MEDDIC: EB + Decision Process + Paper Process - Who else needs to weigh in on a decision like this? - Who ultimately signs off on the budget? - Walk me through how a purchase like this typically gets approved here. - What's the realistic timeline if everything goes well? - Anything in procurement / security / legal we should plan for early? ## 6. CONFIRM & NEXT STEP (3 min) - Quick recap: "Here's what I heard — [summary in their words]. Did I miss anything?" - Proposed next step: [specific meeting + attendees + date] - "I'll send a written summary and a draft MAP within 24 hours." ## NOTES — captured verbatim [ ... ]
MEDDIC-aligned question library
Cherry-pick from this list based on what you still need to learn. Do not ask all them in one call — score the deal and target the lowest-confidence letter.
Discovery questions by MEDDIC letter
| Letter | Question | Listening for |
|---|---|---|
| What does [pain] cost you in dollars or hours per quarter? | A defendable number, not a guess | |
| Who ultimately approves an investment of this size? | A name, a title, and a path to access | |
| What would make you choose option A over option B? | Both technical and business criteria | |
| Walk me through how this gets approved here. | Sequence of gates, not just an end date | |
| What does procurement/security typically need from a new vendor? | Lead time, required docs, gatekeepers | |
| If nothing changes in 12 months, what happens? | An acknowledged business consequence | |
| Who else inside [Company] is feeling this pain? | A potential internal seller | |
| What other approaches are you weighing — including doing nothing? | Named alternatives + status quo |
Weak vs. strong discovery — same call, two outcomes
Same buyer, same 30 minutes. Notice what each version learns.
Weak vs. Strong — side by side
Read both. The difference is question depth, not personality.
WEAK DISCOVERY STRONG DISCOVERY
────────────────────────────────────────── ──────────────────────────────────────────
"Tell me about your team." "Walk me through how [process] runs end
to end today — who owns each step?"
"What are you looking for in a tool?" "If we solved this perfectly, what would
be different in 90 days, and how would
you measure it?"
"What's your budget?" "How does an investment of this size
typically get approved here?"
"Sounds great — I'll send over a demo." "Quick recap of what I heard: [...].
Did I miss anything? Sensible next step
is [X] with [name] on [date] — okay?"
OUTCOME: A demo on the calendar. OUTCOME: Quantified pain, named EB,
No quantified pain, no EB, no MAP. draft MAP, calendared exec meeting.
Key terms in this topic
Related topics
Discovery That Earns the Next Meeting
Discovery is not interrogation. It is the meeting where you trade insight for information — and earn the right to a next step.
Advanced Discovery Questioning Frameworks
Strategic discovery is not a script — it is layered questioning that moves from observable surface to root cause to quantified business impact, while the buyer leads themselves to the conclusion.
MEDDIC & MEDDPICC
The dominant qualification framework for complex enterprise B2B deals — the discipline that separates forecast from fiction.
SPIN Selling
Neil Rackham's question framework — distilled from 35,000 observed sales calls — for moving buyers from latent pain to acknowledged need.
Mutual Action Plans (MAPs)
The single most effective deal-control instrument in enterprise selling — when the customer signs it, when it lives in the deal, and when it surfaces slips early.