Discovery Call Mastery: MEDDIC and the Disqualification Test

Every closed-won deal traces back to a great discovery call. And every stalled deal traces back to a discovery call where the AE talked more than the prospect did.

If you only remember one thing from this guide, remember that. Discovery isn't the warm-up. It's the deal. Pricing leverage in week eight, the close date on your forecast, the path to the economic buyer: all of it is decided in the first 30 minutes of your first real call. If you don't set those economics, the prospect will set them for you.

Most AEs don't run discovery. They run a product demo with a few questions sprinkled at the front. They never qualify, never disqualify, and then wonder why 60% of their pipeline stalls at procurement six weeks later.

This is the playbook I wish I'd been handed in my first year as an AE: MEDDIC the way it's actually run on a call, plus a 3-question disqualification test that tells you whether to send a proposal or keep digging.

Why Discovery Sets Deal Economics

Here's the part nobody tells new AEs: the prospect is also running discovery. On you. They're trying to figure out how cheap you'll go, how long they can stretch the cycle, and whether they can use you as a stalking horse for the vendor they actually want to pick. Whoever asks better questions wins.

Skip discovery and three things happen, all bad. You anchor on features instead of outcomes, so the prospect benchmarks you on price-per-seat. You never identify the economic buyer, so in week six your contact says "I need to loop in my VP" and the cycle restarts. And you have no urgency lever, because you never asked what breaks if they do nothing.

Top AEs flip that. They use the first call to surface the metric that moves, the dollar cost of inaction, and the name of the person who actually signs. By the time they propose, the deal is already qualified, or already disqualified.

The 7 MEDDIC Pillars (With Real Questions)

MEDDIC isn't a checklist. It's a way of running a conversation. Each letter is a pillar, and each pillar has at least one question you should be able to answer in writing after the call. If you can't, you didn't run discovery. You ran a chat.

M — Metrics: What Number Does This Deal Move?

Every B2B purchase is justified to someone with a P&L. Your job is to find the number, attach a delta to it, and make the prospect say it out loud.

Sample question:

"If we deployed this in Q3, what KPI would your CRO expect
to change by Q4 — and by how much?"

That question forces a number, a date, and a chain of accountability up to the CRO. "We want better pipeline visibility" is not a metric. "Our CRO wants forecast accuracy from 65% to 85% by Q4" is. The first answer gets you a stalled deal. The second gets you a champion. If the prospect can't name a metric, you don't have a deal yet. You have a curious user.

E — Economic Buyer: Who Signs the Contract?

The economic buyer is not whoever joined the call. It's the person who can sign the PO without asking permission. In most enterprise deals, that's two or three levels above your initial contact.

Sample question:

"Walk me through the last software purchase your team made
over $50K — who actually said yes, and what did they need
to see before they said it?"

"Who's the decision maker?" is a brochure question. Everyone says "me" or "my boss." Asking about a real prior purchase pulls a real story out of them. You learn the name, the title, and the artifact (a one-pager, a board memo, a vendor comparison) that the EB needs to greenlight a buy. If you don't have the EB's first name in your CRM after call one, you don't have a deal. You have a research project.

D — Decision Criteria: What Does "Best" Mean to Them?

Decision criteria are the written or unwritten rules they'll use to pick a vendor. Security review, integration depth, time-to-value, references in their industry: all fair game. The trick is to surface them before procurement does, because procurement will rewrite them in the buyer's favor.

Sample question:

"If three vendors come back next month with similar demos
and similar pricing, what's the tiebreaker your team would
use to pick one?"

Their answer tells you where to spike your differentiation. If the tiebreaker is "fastest implementation," you bring an implementation case study. If it's "best partner ecosystem," you bring partners. If they can't name one, the criteria aren't real yet.

D — Decision Process: From "We Like It" to "PO Issued"

Most stalled deals stall because the AE never mapped the steps between "verbal yes" and "signed contract." Procurement, security review, legal redlines, board approval: every one of these can add two weeks. If you don't know they're coming, you can't sequence them in parallel.

Sample question:

"Between today and a signed contract, what has to happen
on your side — security review, legal, procurement, board
approval? Walk me through it in order."

Get the sequence in writing. Ask who owns each step and how long each one takes. A 90-day cycle with five gates is fine if you know about them on day one. The same cycle is a forecast killer if you find out in week eight.

I — Identify Pain: What Does "Do Nothing" Cost Them?

Pain is the cost of the status quo, denominated in dollars and time. "Do nothing" is always an option for the prospect, and it's the option you're most often competing against, not your nearest commercial rival.

Sample question:

"If you delay this initiative six months, what specifically
breaks? Walk me through the second-order effects on the
team and the number."

If they can't answer in dollars, hours, or missed targets, they don't have pain. They have curiosity. Curious prospects don't sign contracts this quarter.

When the answer is good ("we miss our Q4 forecast number, the CRO loses board confidence, we lose two reps to attrition") you have a deal. Write that sentence down verbatim and feed it back in every follow-up.

C — Champion: Who Sells This When You're Not in the Room?

A champion is not someone who likes you. A champion is someone with internal credibility who actively wants the problem solved and will burn political capital to solve it. Big difference.

Sample question:

"Who else inside your company most wants this problem
solved — and what do they stand to gain personally if
it gets solved this year?"

"Personally" is doing a lot of work in that question. Champions show up because the problem solves something for them: a promotion, a number they own, a team they want to grow. If the answer is "everyone wants it solved," you have a focus group, not a champion.

Test the champion. Ask them to set up a call with the EB. Ask them to share a one-pager internally. If they won't, they're a coach, not a champion, and the deal is more fragile than your CRM thinks.

C — Competition: What Else Is on the Shortlist?

Competition isn't just other vendors. It's status quo, internal build, and the consultant who suggested they "wait until next fiscal year." All three kill more deals than your nearest commercial rival.

Sample question:

"What other options is the team weighing — including
building this in-house or sticking with what you have?
And what's the in-house engineering team's view of doing it?"

If they say "no other options," they're either lying or they haven't started a real evaluation. Both are problems. Push back gently: "In our experience, every team weighs at least build-vs-buy. Has that come up?"

The Disqualification Test

Now the part that actually changes your number.

Before you send a proposal, run this 3-question test. If you can't answer "yes" to at least two of three, the deal isn't real yet. Don't propose. Keep discovering.

1. Can I name the economic buyer by first name?
2. Do I know the dollar cost of inaction?
3. Is there a forcing function (renewal, board mandate,
   headcount, regulatory deadline) tied to a specific date?

That's it. Three questions. If two answers are "no," the deal isn't a deal. It's a relationship you're nurturing. Nothing wrong with that, but don't put it on your forecast and don't waste a proposal on it.

I know AEs who rejected this test for a year, then adopted it after a brutal Q3. The pattern is always the same: close rate goes up, proposal volume goes down, forecast accuracy goes from 60% to 85%. Disqualifying earlier is how top AEs hit quota, not running more demos. This is also why reverse-engineering your number from average deal size matters: fewer real deals beats more pretend ones every time.

MEDDIC Scoring Rubric (1–5 Per Pillar)

Score each pillar 1 to 5 after the call. Threshold to advance: total of 24+ across all 7 pillars, with no individual pillar below 3.

If your total is below 24 after the first call, run a second discovery call before demoing. If it's below 18, the deal isn't real. Go work the next opportunity.

Discovery Agendas: 30 vs 45 vs 60 Minutes

Different slots demand different scope. Don't try to run full MEDDIC in 30 minutes.

30-minute slot. Metrics, Pain, Decision Process. You're triaging. The goal is to learn whether this is real enough to book a 60-minute call. End with: "Based on what you've shared, the next useful step is a 60-minute working session with [champion + EB]. Can we get that on the calendar before you leave today?"

45-minute slot. Add Economic Buyer and Champion. You can probably get partial Decision Criteria too. Skip Competition unless they bring it up.

60-minute slot. Full MEDDIC with competition mapping. This is where you earn the right to demo. You should leave with the EB's name, the dollar cost of inaction, the decision process in steps with owners, and the tiebreaker criteria. If you don't have all four, the call wasn't discovery. It was a chat.

Never let a 30-minute slot become a demo. If the prospect pushes for one, redirect: "A generic demo will waste both our time. Give me ten minutes of context and I can show you the three things that actually matter for your team."

Common Pitfalls

Asking "what are your goals?" without follow-up. You'll get a brochure answer ("grow revenue, retain customers"). Always follow up:

"By how much, by when, and who specifically inside
your company is on the hook for that number?"

Talking instead of listening. Target 70% prospect, 30% AE on a discovery call. Record your calls and check the ratio. It's almost always worse than you think.

Skipping budget and process questions because they feel rude. They're not rude. Procurement will ask them anyway, and if you didn't ask first, you've lost the framing.

Accepting "yeah we have budget" without asking who controls it. Budget that lives with your contact is a different deal from budget that sits with their VP. Always ask:

"Who controls the budget line item for this purchase —
your team's P&L or your VP's? And if it's your VP's,
how does it get allocated to your team?"

Running the same script for SMB and enterprise. SMB discovery is faster, lighter, often skips Decision Process because the EB is the user. Enterprise needs all 7 pillars and probably two calls. Calibrate.

Post-Call Summary Template

Send this within two hours of the call. Every time. No exceptions.

Subject: Recap — [Their Company] / [Your Company] discovery call

Hi [Name],

Thanks for the time today. Quick recap so we're aligned:

WHAT I HEARD
- The metric that matters: [verbatim from them]
- The cost of inaction: [verbatim, with numbers]
- The decision process: [steps with owners and dates]
- The tiebreaker if vendors are close: [their words]

WHAT WE AGREED
- [Their next step] by [date]
- [Your next step] by [date]
- [Joint next step] on [date]

WHAT I'LL BRING NEXT TIME
- [Specific artifact tied to their tiebreaker]
- [Reference customer in their industry]

If I got any of the above wrong, just hit reply and correct me —
I'd rather be wrong on email than wrong in your CRO's office.

— [You]

The "I'd rather be wrong on email" line earns more deal intelligence than any other tactic I've used. People will correct you in writing when they won't correct you on a call. That correction is gold for the next conversation, and it's the foundation of how you'll run the buying committee event when it's time to close.

Measuring Success

Three numbers tell you whether your discovery is working.

Discovery-to-demo conversion: 60%+ if discovery is real. Lower means you're not surfacing real pain in call one, so prospects ghost. Higher than 80% means you're not disqualifying.

Demo-to-close conversion: lifts 15–25% with clean MEDDIC. Most AEs sit at 18–22%. Clean MEDDIC pushes that to 30–35%. The lift comes from disqualifying weak deals before they consume demo cycles.

Deal velocity drops, not rises, when you disqualify earlier. Counterintuitive but true. The deals that survive discovery have real urgency. The stalls never make it to forecast. This is also why pricing and timing objections almost evaporate when discovery is real. Most pricing objections are pain objections in disguise, and you fixed them on call one.

If your stack includes call recording with AI summarization, use it to score yourself on talk ratio and MEDDIC coverage after every call. The tools are good enough now to give you an automated 1–5 score per pillar within an hour. We cover the full stack in AI in the AE workflow. Short version: stop reviewing calls manually. The AI is better at it.

A clean discovery call ends with you knowing the metric, the dollar pain, the EB's first name, the decision process in steps, the tiebreaker, and at least one champion who'll burn capital. You leave ready to disqualify or advance, no in-between.

The AEs at the top of the leaderboard didn't get there by demoing more. They got there by asking better questions on the first call and walking away from the deals that didn't pass the test.

Run the framework. Run the test. Run the next call.