A Teardown of the Discovery Call Playbook Every Company Seems to Have
A line-by-line walk through a generic, all-too-familiar discovery playbook, showing exactly where a list of questions gets mistaken for actual qualification logic.
You've seen this playbook. You may well have written it. It opens with "build rapport," moves through a tidy block of open questions, and closes with "confirm next steps." Strip the branding off a hundred of these and they're the same document: "Tell me about your current process." "What's prompted you to look at this now?" "What happens if you don't solve this?" "Who else needs to be involved in a decision like this?" "What's your timeline?" Every box on the MEDDIC acronym gets a line item. Every line item gets a question. And almost none of it tells a rep what to do with the answer, which is the only part of qualification that was ever actually hard.
Here's the composite playbook, assembled from the real thing across a dozen client audits with the serial numbers filed off. Then the teardown, question by question.
The playbook, as written
- "Tell me about how you handle this today."
- "What's driving you to look at this now?"
- "What would success look like for you?"
- "What happens if this doesn't get solved?"
- "Who else, besides you, would be involved in a decision?"
- "What's your budget for something like this?"
- "Walk me through how a decision like this typically gets made here."
- "What's your timeline for making a change?"
Read on its own, it looks fine. It maps neatly to MEDDIC — Metrics (3), Economic Buyer (5, 6), Decision Criteria (7), Decision Process (7), Identify Pain (1, 2, 4), Champion (nowhere, notably). That mapping is exactly the problem. The playbook was built backwards from the acronym, question-per-letter, rather than forwards from the actual job qualification is supposed to do, which is produce a decision: pursue, and how hard, or don't.
Line by line
| Question | Meant to surface | Where it actually breaks | What real qualification requires instead |
|---|---|---|---|
| "Tell me about how you handle this today." | Baseline pain | Produces a description, not a cost. Reps accept "it's a bit clunky" as an answer and move on. | A follow-up that forces quantification: hours lost, deals slipped, cost of the workaround — and a rule that if the prospect can't put a number or a name to the pain, the call moves to disqualifying, not to question two. |
| "What's driving you to look at this now?" | Compelling event | Almost any answer sounds like a compelling event if you want it to. "Our old contract's up for renewal" gets treated the same as "our CEO mandated this by Q3 or we lose the board's confidence," when only one of those forces a decision by a date. | A test for whether the event actually forces action versus merely permits it — does something bad happen on a specific date if nothing changes, and can the prospect name that date. |
| "What would success look like for you?" | Metrics | Accepted as a metric the moment it's a sentence, even when it's a feeling. "Success would be a smoother process" gets logged in the CRM's Metrics field verbatim. | A number, a unit, and a baseline. If the prospect can't turn their answer into a figure with a "from X to Y," it isn't a metric — it's a mood, and the deal shouldn't be scored as if it has quantified value. |
| "What happens if this doesn't get solved?" | Cost of inaction / urgency | Almost always answered with a shrug — "we'd keep muddling through" — and the rep moves on rather than treating a weak answer as the disqualifying signal it is. | A branch: a strong answer (named, dated consequence) earns a follow-up on stakes; a weak answer should trigger a deprioritise-or-probe-harder decision, not a polite nod and question five. |
| "Who else, besides you, would be involved in a decision?" | Buying committee | Gets a list of names and titles, logged as "stakeholders identified," which is treated as equivalent to those people being engaged. Nobody follows up to actually reach them. | A distinction between named and engaged. A name on a slide with no conversation, no email thread, no meeting is not a mapped stakeholder — it's a rumour of one. |
| "What's your budget for something like this?" | Economic buyer / funding | Answered by whoever's on the call, who is frequently not the person who controls the money, and their guess gets recorded as if it were confirmed budget. | Verification from the person who actually owns the line item, not an estimate relayed secondhand — and a flag distinguishing "confirmed by the budget owner" from "guessed by my champion." |
| "Walk me through how a decision like this typically gets made here." | Decision process & criteria | Takes the stated process at face value, with no check against how the org's last three purchases actually went, and no revisit if the story changes later in the deal. | A cross-check against precedent — has this org actually made a purchase this way before — and a standing instruction to re-verify if a new stakeholder later contradicts the story. |
| "What's your timeline for making a change?" | Decision timing | Recorded as a close date and dropped straight into the CRM's forecast field, with no distinction between a date the buyer committed to and a date the rep hopes for. | A source check: did the buyer state the date, or did the rep infer it from politeness? Only the former belongs in a forecast. |
Where MEDDIC quietly becomes trivia
Run down that right-hand column and a pattern shows up fast: every fix is a branch, and the playbook has none. It's a list of questions to ask, not a decision tree for what a good answer versus a bad one should trigger. That's the difference between qualification as logic and qualification as trivia. Trivia rewards knowing the question. Logic rewards knowing what a wrong answer means for the deal.
The Champion letter doesn't even make the list above, and that's the tell that gives the whole document away. A playbook built to actually qualify would have a question, and a hard follow-up, dedicated to testing whether anyone in the account will fight for this internally when the rep isn't in the room — will introduce the rep to their boss, will push back on a competing priority, will actually spend political capital. A playbook built to look thorough skips it entirely, because "who's your champion" doesn't fit neatly into a single open-ended question the way the others do, and whoever assembled this deck was optimising for acronym coverage, not for the thing acronym coverage is supposed to produce.
The missing half: disqualification
Look again at the table and notice what's absent across all eight rows: not one of them has a stated "and if the answer is bad, here's what you do." Real qualification logic is symmetric. It should be exactly as easy to walk away from a deal as to advance one, and a genuine discovery framework builds that walk-away path in from the start — a weak-pain answer should route to a specific next step (probe harder, or flag at low priority), not to the next question on autopilot. Most playbooks we've audited make disqualifying a deal something a rep has to invent unassisted, against every incentive in their comp plan, using judgment the document never gave them permission to exercise.
That's the actual line between MEDDIC as a working framework and MEDDIC as theatre. Theatre has all six letters covered and a shrug where the decision logic should be. A working version treats a bad answer to any single question as data serious enough to change what happens next — including, sometimes, ending the call early and moving on to a deal that's actually winnable.
If you want to see the difference in a document rather than a paragraph, run your current script against a proper MEDDIC Deal Qualification Checklist and score each answer, not just each question, using a Discovery Call Scorecard for Managers. And if the Champion letter is missing from your own playbook the way it was missing here, a Champion Identification & Development Checklist is the fastest way to make political capital a thing reps are trained to test for, rather than a thing they assume because someone smiled on a call.
A checklist tells a rep what to ask. It takes a manager willing to build in the branches to tell them what a bad answer means.