MEDDIC in Practice: Which Elements Reps Skip Most (And Why It Matters)

Abstract checklist visualization with gaps highlighted in amber — discovery completeness concept

MEDDIC has been the dominant B2B deal qualification framework for over two decades. Most reps on teams that use it can recite the acronym: Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion. When you ask them if they use it, they'll say yes. When you listen to their discovery calls, you'll often find they're completing three or four elements out of six, and the ones they skip are not random.

We scored 3,200 discovery calls against MEDDIC completeness across teams using Tunlai. The pattern in which elements get skipped is consistent enough to be useful — and the correlation between skipped elements and deal outcomes is strong enough to be a coaching priority.

What the Data Shows

Metrics and Decision Criteria are covered in the vast majority of discovery calls — above 80% completion rate across the call set. Reps are comfortable here. Metrics are concrete (what does success look like, what are you measuring today). Decision Criteria maps easily onto product demos (what are you evaluating us on). Both elements feel natural to surface and require no political navigation.

Decision Process is covered about 65% of the time. Reps ask about procurement process, timeline, number of stakeholders. They often do this superficially — "who else needs to be involved?" gets a name, it gets logged in CRM, the box is checked. Whether the rep has actually mapped the buying process vs. received a single answer is a different question.

The two elements that fall off the table most consistently are Economic Buyer and Identify Pain. In deals that later stalled or went to closed-lost, one or both were absent from the discovery call 62% of the time. In closed-won deals of comparable size and complexity, that absence rate drops to 23%.

Why Economic Buyer Gets Skipped

Identifying the Economic Buyer — the person who actually controls the budget and has final authority to approve the purchase — is uncomfortable to pursue in discovery, especially when the discovery call is with a practitioner or middle-level manager. Asking "who owns the budget for this purchase?" can feel presumptuous or premature. Reps worry they'll offend the person they're talking to by implying that person doesn't have authority.

So instead they infer. They assume the VP they're talking to controls the budget. They put "VP of Operations" in the Economic Buyer field in CRM and move on. When deal review comes, the manager asks "have you talked to the Economic Buyer?" and the rep says "yes, I've been working with Sara." What often hasn't happened is any actual confirmation that Sara controls the budget, a direct conversation about the budget available for this initiative, or any connection between the business impact being quantified and the actual approval process Sara would navigate to get a purchase approved.

The gap shows up at stage three or four. The rep has built a relationship with Sara, done a full demo, sent a proposal. Then Sara says "this looks good, let me take it to the CFO." The CFO hadn't been part of any conversation. There's no Champion above Sara to carry the case. The deal stalls in a review cycle the rep has no visibility into and no influence over.

This isn't a failure of the MEDDIC framework. It's a failure to actually work the Economic Buyer element rather than just claiming it. The question the rep needs to ask in discovery is more direct: "For a purchase like this, who's typically involved in the final approval, and is that person someone we should have in the conversation before the proposal stage?"

Why Identify Pain Gets Shortchanged

Identify Pain is the MEDDIC element that most resembles "doing discovery" — and yet it's consistently incomplete. The problem is that reps surface pain at the symptom level and stop there. "We're spending too much time on manual reporting" is a symptom. The pain underneath it — the CFO is questioning the sales ops team's productivity, the VP of Revenue is making decisions with lagging data, the company is scaling its AE headcount but can't run effective pipeline reviews — that's what you need before you can price a business case or connect the pain to an Economic Buyer's agenda.

We're not saying surface-level pain identification is useless — it tells you whether there's a fit conversation worth having. But stopping at symptoms means the rep will build their entire pitch on the practitioner's language, not the Economic Buyer's language. The practitioner says "better reporting." The CFO says "I need accurate pipeline numbers to make hiring decisions." Those are the same underlying problem, but the CFO's version is the one that justifies budget. The rep who only heard the practitioner's version will write a proposal in the wrong language for the approval stage.

The MEDDPICC Extension and Where It Adds Complexity

Some teams run MEDDPICC — the two additional elements are Paper Process and Competition. Both are valuable but both add surface area for incompleteness. Paper Process is skipped almost as often as Economic Buyer in our data — reps ask about decision process and assume paper process is included. It isn't. A deal where the rep knows the decision timeline but hasn't accounted for a 45-day legal review or a procurement security questionnaire that requires a security review from the vendor is a deal that will miss a close date.

Competition is covered more consistently — 74% completion rate in our data — but the quality of coverage varies widely. "Who else are you looking at?" followed by logging "Acme Software" in CRM is not competitive intelligence. It doesn't tell you where Acme is in the evaluation, what the prospect likes about Acme, or whether the decision criteria the rep mapped actually differentiates from Acme's position. The call-level evidence of good competitive intelligence is: the rep probed specifically about what the prospect has heard about each competitor, connected those perceptions to the prospect's stated decision criteria, and addressed any gaps without going defensive.

What Good Looks Like: A Concrete Example

Consider a discovery call at a 50-rep B2B software team evaluating a new coaching platform. The rep on that call covered Metrics (rep ramp time, call quality scores), Decision Criteria (must integrate with Salesforce, must show ROI within 90 days), and Decision Process (three-person evaluation committee, 30-day timeline). Economic Buyer field in CRM: the VP of Sales Enablement. Pain documented: "current manual call review is too time-consuming."

What was missing: whether the VP of Sales Enablement had budget authority or needed CFO sign-off, what the business-level cost of the current pain was (not the time cost but the revenue impact of slow ramp time), and whether there was a champion who could navigate the approval process independently if the rep wasn't in the room. The deal moved to proposal on that incomplete MEDDIC set. It stalled three weeks later when the VP of Sales Enablement said she needed to get CFO approval for tools above $50,000 — a threshold the proposal clearly exceeded.

None of those missing elements were impossible to surface in discovery. They require asking harder questions earlier. "For a tool in this budget range, does the CFO typically need to be involved, and is that something we should plan for in our timeline?" That question, asked in discovery, changes the deal path. It doesn't come from MEDDIC as a checkbox. It comes from understanding why Economic Buyer matters.

How We Coach MEDDIC Gaps in Tunlai

When we score a call for MEDDIC completeness, we're not looking for the rep to say the word "Economic Buyer" or ask a templated question. We're looking for evidence of coverage — did the rep establish who has final budget authority, did they connect pain to a business impact that an Economic Buyer would recognize, did they surface a potential champion above the practitioner level.

The coaching note that comes out of a gap is specific to where in the call the coverage was missing and what opportunity existed to surface it. "At minute 22, the prospect mentioned 'taking it to leadership for approval' — that was a natural entry point to explore who in leadership owns this budget and what they'd need to see. The rep moved past it to close a next step." That kind of specificity — tied to a real moment in a real call — is what makes MEDDIC coaching land rather than becoming another acronym that reps recite and don't execute.

Want Tunlai to analyze one of your calls?

Start free trial