MEDDIC: The Sales Qualification Framework Explained (With Examples)

Focus keyphrase: meddic

TL;DR

MEDDIC is a B2B sales qualification framework that helps reps decide which deals deserve their time and which will quietly die in the pipeline. The acronym stands for Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, and Champion. It was developed at PTC in the 1990s by Jack Napoli and Dick Dunkel, and it remains one of the most widely used qualification methods in enterprise and mid-market sales. Use MEDDIC when your deals are complex, involve multiple stakeholders, and run long enough that a bad-fit deal can waste weeks of effort. It is a checklist for deal health, not a script for how to sell.

What is MEDDIC?

MEDDIC is a qualification methodology: a structured way to test whether an opportunity is real, winnable, and worth pursuing. Instead of relying on gut feel (“the prospect seemed excited on the call”), MEDDIC forces you to answer six concrete questions about every deal.

Each letter represents one of those questions:

• M, Metrics: what measurable business outcome does the buyer expect?
• E, Economic buyer: who actually controls the budget and can say yes?
• D, Decision criteria: what standards will the buyer use to evaluate options?
• D, Decision process: what steps, approvals, and timelines lead to a signed contract?
• I, Identify pain: what problem is painful enough to force change?
• C, Champion: who inside the account is actively selling on your behalf?

If you can answer all six with evidence (not assumptions), the deal is well qualified. If two or three are blank, you either have work to do or a deal you should walk away from.

MEDDIC came out of PTC (Parametric Technology Corporation), where the sales team used it to sustain years of aggressive growth. Its popularity spread because it is simple to teach, easy to audit in a CRM, and brutally effective at exposing weak deals early.

The MEDDIC components explained

M: Metrics

Metrics are the quantifiable outcomes the buyer expects from solving their problem. Not “we want to be more efficient” but “we want to cut onboarding time from 45 days to 20” or “we need to reduce churn by 3 points this year.”

Metrics matter for two reasons. First, they let you build a business case the economic buyer will accept. Second, they anchor the deal to value rather than price, which protects you in negotiation.

Example question: “If this project succeeds, what number changes, and by how much? How is that number measured today?”

Red flag: the prospect cannot name a single metric. Deals without metrics tend to stall at the business-case stage because nobody can justify the spend.

E: Economic buyer

The economic buyer is the person with final authority over the budget for this purchase. They can approve spending, veto it, or reallocate it elsewhere. In a mid-market deal that might be a VP; in enterprise it is often a C-level executive or a budget-holding director.

Your contact is frequently not the economic buyer. A sales ops manager may love your product, but if the CRO owns the budget, the CRO’s priorities decide the deal.

Example question: “Whose budget does this come out of? Who signed off the last purchase of this size, and what did they need to see?”

Red flag: you are three months into a deal and have never spoken to, or been referenced by, the economic buyer.

D: Decision criteria

Decision criteria are the standards the buyer will use to compare vendors: technical requirements, integration needs, security reviews, pricing model, support expectations, references. Some criteria are formal (an RFP scorecard), many are informal (the CTO’s preference for a particular architecture).

Knowing the criteria lets you do two things: confirm you can actually win, and influence the criteria early so they favor your strengths. The vendor who helps write the scorecard usually wins the evaluation.

Example question: “When you compare options, what are the top three things that will decide it? Who wrote those requirements?”

Red flag: the criteria were clearly written around a competitor’s feature set. You are probably column fodder in someone else’s deal.

D: Decision process

The decision process is the sequence of events between “we like your product” and “the contract is signed”: evaluation steps, security and legal review, procurement, budget approval cycles, and the people who own each step.

This is where deals slip. A rep forecasts a deal for March 31 without knowing that procurement takes six weeks and the security review has not started. Mapping the process turns your forecast from hope into a plan.

Example question: “Walk me through what happened the last time you bought software like this. What were the steps, how long did each take, and where did it get stuck?”

Red flag: the buyer cannot describe their own process. Either they have never bought anything like this (expect delays) or your contact is too junior to know (find someone who does).

I: Identify pain

Pain is the business problem that makes change necessary. Not mild annoyance: real cost. Lost revenue, missed targets, compliance exposure, teams burning hours on manual work. The pain has to be big enough that doing nothing is more expensive than buying your solution, because “do nothing” is the competitor you lose to most often.

Good pain discovery goes three layers deep: what is the problem, what does it cost, and what happens if it is still unsolved in twelve months?

Example question: “What happens if you don’t fix this by the end of the year? Who feels that first?”

Red flag: the pain is real but nobody senior owns it. Pain without an owner rarely gets budget.

C: Champion

A champion is a person inside the account who wants you to win and has the influence and access to help you do it. A champion is not just a friendly contact: they sell for you in meetings you are not in, give you intel on competitors and politics, and pull you toward the economic buyer.

Champions need three qualities: they personally benefit from your solution winning, they carry credibility with the decision makers, and they are willing to act. Test all three. Ask them to set up a meeting with the economic buyer; a real champion does it, a coach makes excuses.

Example question: “If the CFO pushes back on this in the budget meeting, what will you say?” (A champion has an answer. A contact changes the subject.)

Red flag: your “champion” only talks to you when you call them.

How to use MEDDIC in your sales process

MEDDIC is not a stage in the pipeline. It runs across the whole cycle:

Qualification (first calls). Use the I and M elements first: is there real pain, and is it measurable? If the answer is no, disqualify politely and move on. Fast disqualification is one of MEDDIC’s biggest returns.

Discovery (early-mid cycle). Fill in decision criteria and decision process, and start identifying the economic buyer and potential champions. Every discovery call should close at least one MEDDIC gap.

Deal reviews and forecasting. Score each deal on the six elements (many teams use a simple 0-2 per letter). Deals scoring below a threshold do not get committed to the forecast, no matter how enthusiastic the rep feels. This is where MEDDIC changes forecast accuracy: the six letters replace optimism with evidence.

CRM hygiene. Most teams add six fields (or one scorecard object) to their opportunity records. If a field is blank, the next call’s objective writes itself.

MEDDIC also pairs naturally with your outbound motion: the earlier you gather qualification signals, the fewer bad-fit deals enter the pipeline in the first place. Teams running structured outbound in a tool like Salesgear often bake early MEDDIC questions (pain, metrics) into their first two live conversations so that only real opportunities graduate to the pipeline.

MEDDIC example: qualifying a realistic deal

Imagine you sell a data integration platform. An enterprise retailer’s Director of Analytics books a demo. Here is what a MEDDIC-qualified version of that deal looks like after three weeks of discovery:

• Metrics: the analytics team spends roughly 30 hours a week on manual data pipeline fixes. Leadership wants that under 8 hours, freeing about 1.5 FTEs worth of capacity, valued at around $220,000 a year.
• Economic buyer: the CDO, Priya, owns the data platform budget. Your champion arranged a 20-minute intro; Priya confirmed budget exists in the Q3 planning cycle and asked for a business case in her template.
• Decision criteria: must support their Snowflake environment, pass SOC 2 review, include role-based access, and come in under $150,000 in year one. Weighting: reliability first, price third.
• Decision process: technical evaluation (2 weeks) → security review (3 weeks, queue starts on submission) → CDO approval → procurement (4 weeks, redlines expected on liability caps). Realistic close: 10 weeks out, so you forecast next quarter, not this one.
• Identify pain: two pipeline failures last quarter delayed weekly executive reporting, and the CEO noticed. The Director of Analytics is personally on the hook for reliability.
• Champion: the Director of Analytics, Marco. He benefits directly (his team’s pain, his reputation), has Priya’s ear, and has already forwarded your ROI one-pager internally without being asked.

Compare that to the same deal three weeks in with only “they liked the demo” in the notes. Same account, completely different forecast confidence.

MEDDIC vs other methodologies

MEDDIC vs BANT. BANT (Budget, Authority, Need, Timeline) is a lighter, faster qualification checklist suited to shorter, simpler sales cycles. MEDDIC goes deeper on how the decision gets made (criteria, process, champion), which matters in complex deals where BANT’s four checks are too shallow. See our full [BANT methodology guide].

MEDDIC vs MEDDPICC. MEDDPICC is MEDDIC plus two elements: Paper process (legal and procurement) and Competition. Enterprise teams with long contract cycles and crowded competitive fields tend to prefer MEDDPICC. See the [MEDDPICC guide].

MEDDIC vs SPICED. SPICED (Situation, Pain, Impact, Critical event, Decision) is a discovery and customer-lifecycle framework rather than a pure qualification checklist, popular with recurring-revenue and product-led teams. See the [SPICED selling guide].

MEDDIC also coexists with selling methodologies like Challenger or Sandler: those tell you how to sell, MEDDIC tells you whether the deal is worth selling into. For the full landscape, see our [complete guide to sales methodologies] (hub post).

When MEDDIC is (and is not) the right fit

MEDDIC fits well when:

• Deal sizes are large enough that losing late is expensive
• Sales cycles run weeks to months with multiple stakeholders
• Forecast accuracy is a leadership priority
• Reps need a shared language for deal reviews

MEDDIC is probably overkill when:

• You sell low-cost, single-decision-maker, transactional products
• Cycles close in days and velocity matters more than depth
• Your motion is mostly self-serve or product-led with light sales assist

In those cases BANT or SPICED gives you enough rigor with less overhead. And even in complex sales, MEDDIC fails when it is treated as a form-filling exercise: the letters are prompts for real conversations, not fields to guess at before a pipeline review.

FAQ

What does MEDDIC stand for?

MEDDIC stands for Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, and Champion. Each element is a qualification checkpoint for a B2B sales opportunity.

What is MEDDIC in sales?

MEDDIC is a sales qualification framework used to assess whether a deal is real, winnable, and worth pursuing. Reps gather evidence for six elements of the deal and use the gaps to plan next steps or disqualify early.

What is the difference between MEDDIC and BANT?

BANT checks four surface-level factors (Budget, Authority, Need, Timeline) and suits fast, simple sales. MEDDIC digs into how the decision is made, who influences it, and what measurable value is at stake, which suits complex, multi-stakeholder deals.

Is MEDDIC still used?

Yes. MEDDIC and its extended version MEDDPICC are among the most widely adopted qualification frameworks in B2B SaaS and enterprise sales, particularly in organizations that emphasize forecast accuracy.

How do you implement MEDDIC?

Start by adding the six elements to your opportunity records, train reps to close one MEDDIC gap per call, and make the six letters the agenda of every deal review. Score deals consistently, and only forecast opportunities that clear a minimum score.

Related sales frameworks

• MEDDIC sales methodology
• MEDDPICC
• SPICED selling
• BANT
• All 20 sales methodologies compared

Once you have qualified a deal, the next step is reaching the right people. See how to run research-led outbound in the sales prospecting guide.