How to Run MEDDPICC Discovery Without Sounding Like a Checklist
MEDDPICC gets a bad name because it gets asked badly. A field-by-field rework of the checklist into questions a human would actually say out loud.
MEDDPICC didn't earn its bad name by being a bad framework. It earned it by being asked badly — eight letters fired at a prospect in sequence, in the tone of a border agent checking a passport. Metrics. Economic buyer. Decision criteria. Decision process. The prospect can hear the acronym even when you never say it, because the questions arrive in a suspiciously tidy order and none of them reference anything they just said. That's the tell. A real conversation loops back on itself. A checklist marches forward regardless.
The fix isn't a new framework. It's re-authoring each letter as a question that only makes sense because of what the buyer said thirty seconds earlier. Below is the field-by-field rework, with the checklist version most reps default to under pressure alongside it, so you can hear the difference.
The checklist version vs. the conversation version
| Letter | Checklist question (avoid) | Conversation version | Why it lands |
|---|---|---|---|
| Metrics | "What metrics are you looking to improve?" | "You said late invoicing is costing you renewals — roughly how many, or is that more of a gut feeling right now?" | Anchors the number to the pain they already named, and gives them permission to say "gut feeling," which is usually the honest answer |
| Economic Buyer | "Who's the economic buyer?" | "Whose budget does this come out of if it goes ahead?" | Same information, asked as a logistics question rather than a status interrogation |
| Decision Criteria | "What are your decision criteria?" | "Last time you bought something like this, what killed the runner-up?" | Past tense, third party — easier to answer honestly than a hypothetical about the live deal |
| Decision Process | "Walk me through your decision process." | "Who else has to nod at this before it's real, and has anyone in that group been burned by a tool like this before?" | Surfaces process and political risk in one breath |
| Paper Process | "What's your procurement process?" | "Once someone says yes, what usually adds the weeks — legal, security review, or finance?" | Assumes friction exists, which is true, so it doesn't read as an accusation |
| Identify Pain | "What's your pain point?" | "What happens if you do nothing for another two quarters?" | Forces them to price the cost of inaction, which is the real pain, not the symptom they led with |
| Champion | "Who's championing this internally?" | Covered properly elsewhere — see the fake-champion test | — |
| Competition | "Who else are you evaluating?" | "If this stalls, what's plan B — another vendor, building it internally, or doing nothing?" | Widens "competition" to the true rival, which is usually inertia |
Read the right-hand column out loud. None of it sounds like a form. All of it depends on an answer you don't have yet, which is the actual definition of discovery.
Metrics: chase the story, not the number
Reps skip Metrics, or ask for it flat, because a bare number feels like homework to the buyer. Let them round. "Roughly how many deals slip when invoicing runs late?" gets further than "what's your metric for this," because rough is a socially acceptable answer this early and precise isn't. Once you have a rough number, the follow-up does the real qualifying work: "is that a number finance already tracks, or one you're estimating for me right now?" That single question tells you whether Metrics is real or invented to be polite. If you want more ways to force a number out of a vague pain statement, the Implication & Need-Payoff Question Cheat Sheet has the fuller technique — it's built for exactly this moment.
Economic Buyer: earn the intro before you ask for the name
Asking "who's the economic buyer" too early reads as trying to route around the person in front of you, and they know it. Ask about the budget mechanics instead — whose line it sits under, whether it needs a business case or just a signature — and the name usually surfaces without you asking for it directly. If it doesn't surface, you've learned something more useful than a name: your contact doesn't actually know, which tells you how far up the chain they really sit. The Economic Buyer Access Swipe File has more openers for exactly this situation, when procurement keeps routing you back to the same mid-level contact.
Decision Criteria and Decision Process: one conversation, not two
These get asked as separate interrogations when they're really one thread. Ask about the last purchase they made in this category, and both criteria and process fall out of the story naturally — what mattered, who objected, what nearly killed it. You get more honest information from "tell me about the last time" than from "tell me about your process," because a story is verifiable in a way a policy statement isn't. Confident specificity — dates, names, what actually went wrong — means you're talking to someone who's been through a buying cycle here before. Vague and generic means you're talking to someone who's guessing, which is worth knowing now rather than at contract stage.
Paper Process: the letter everyone forgets until week nine
Paper Process gets skipped almost as often as Metrics, because it's boring and feels premature to ask about legal review before there's a deal to review. Ask it as a friction question, not a procurement question: "once someone internally says yes, what usually adds the weeks?" People will happily complain about their own security review process. They will not fill in a form called "describe your procurement process" for a vendor they haven't chosen yet.
Identify Pain: price the cost of doing nothing
"What's your pain point" invites a symptom — slow reporting, manual reconciliation, whatever's annoying this month. The number you need is what happens if nothing changes. "What happens if you run this the same way for another two quarters?" makes them do arithmetic on inertia, and the answer to that question is the real business case — not the feature list you'll pitch in three weeks' time.
Competition: widen the frame past other vendors
Most reps ask "who else are you evaluating" and get two competitor names, the least useful version of this letter. The thing that actually kills a deal more often than a rival vendor is the buyer deciding to do nothing, or trying to bolt something together internally. Ask about plan B if this stalls, and you'll find out whether you're fighting a competitor or fighting apathy — two completely different sales motions requiring completely different responses.
Run these rewrites against your last five calls — or run them through the MEDDPICC Scorecard if you want a second opinion that isn't your own ear — and you'll notice what I noticed reviewing transcripts for fifteen years: the letters were never the problem. The order and the tone were. Ask them in the sequence the buyer's story creates, not the sequence the acronym creates, and the same eight questions stop sounding like an audit and start sounding like someone who was actually listening.