Cookie Settings

We use cookies and other technologies across categories below. Toggle any to accept or reject related data collection. You can view our privacy policy here.

Skip to content
Onfire Glossary Term

MEDDIC

MEDDIC is a B2B sales qualification framework that helps reps decide whether a complex deal is real, winnable and worth forecasting. The MEDDIC acronym stands for Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain and Champion. Those are the six things a seller should know before a deal goes into the forecast.

Account executives use it to spot gaps in what they know about a deal. Managers use it to inspect pipeline, and RevOps teams use it to standardize forecast reviews. It earns its keep in enterprise sales, where lots of stakeholders and formal approvals make deals easy to misjudge. MEDDICC adds Competition, and MEDDPICC adds Paper Process on top of that. All of them are qualification tools, not complete sales processes.

What Is MEDDIC?

MEDDIC came out of PTC's sales organization in the 1990s as a way to qualify large enterprise software deals. In April 2026, a US federal court ruled that the eight-letter extension is a generic term, finding that sales professionals understand it as a methodology name, according to Fox Rothschild's summary of the ruling.

People often call it the MEDDIC sales methodology, but it works better as a qualification framework. It tells you what to know about a deal, not how to run each stage. Most teams pair it with a separate approach for discovery, demos and negotiation.

The Six MEDDIC Elements, Explained

Each letter is a question the seller should answer with evidence, not assumption.

LetterWhat it asksExample in a technical deal
MetricsWhat measurable outcome does the buyer expect?Cut mean time to resolution or reduce cloud spend
Economic BuyerWho has final budget authority?A VP Engineering or CISO who can approve the spend (the economic buyer)
Decision CriteriaWhat will the solution be judged on?Security review, integrations, proof-of-concept results
Decision ProcessWhat steps, and which people, lead to a yes?Technical evaluation, then architecture review, then sign-off
Identify PainWhat problem is costly enough to act on?Alert fatigue, failed audits, slow CI pipelines
ChampionWho will sell internally on your behalf?The engineer who already adopted the tool

A blank row doesn't mean the deal is dead. It just isn't qualified yet. And a Champion should be identified, tested and developed, not just liked.

MEDDICC and MEDDPICC: What the Extra Letters Add

The extended versions go after what stalls large deals late in the cycle. Competition, the second C in MEDDICC, asks who else the buyer is evaluating, including in-house builds or doing nothing. Some teams use that C for a second Champion instead. Paper Process, the P in the eight-letter form, covers the legal, security and procurement reviews that have to happen before signing.

Since the 2026 ruling cancelled the trademark registration, any team or trainer can now use the term.

MEDDIC vs. BANT: When to Use Each

BANT (Budget, Authority, Need, Timeline) is a fast four-point screen for early conversations. It doesn't map champions, decision processes or pain in any depth.

That gap matters because enterprise purchases rarely rest on one person. Gartner's May 2025 survey of 632 B2B buyers found that buying groups range from 5 to 16 people across up to four functions. Groups that reach consensus are 2.5x more likely to report a high-quality deal, yet 74% of buyer teams show unhealthy conflict during the decision.

FrameworkBest forMain limitation
BANTQuick screening of inbound leads and early callsAssumes a single authority and ignores internal dynamics
MEDDICComplex deals with multiple stakeholdersTakes more discovery time to complete

So MEDDIC vs BANT is a question of fit, not quality. Many teams use BANT to decide whether to open an opportunity, then switch to MEDDIC once they need to map the full buying committee.

Running MEDDIC on Technical Deals

Selling to engineering, security and data teams changes how several elements play out.

The Champion is often an engineer already using the product through open source, a free tier or a trial. Make sure they actually have influence with leadership. The Economic Buyer is usually a VP Engineering or CISO, a different person from the technical buyer who runs the evaluation, so map both separately.

Decision Criteria tend to be technical, mostly security reviews, integrations and proof-of-concept results. The Paper Process is dominated by security questionnaires and procurement, which can add weeks after technical approval.

Activity on GitHub, Reddit and Stack Overflow can show which engineers at an account use or discuss a tool (likely champions) and which pains they describe publicly.

FAQ

What does MEDDIC stand for?

MEDDIC stands for Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain and Champion. Together they cover the expected outcome, who controls budget, how options are judged, the steps to approval, the problem worth solving and the internal advocate. Extended versions add Competition and Paper Process.

What is the difference between MEDDIC and MEDDPICC?

The longer version adds Paper Process and Competition. Paper Process covers the legal, security and procurement reviews required before signing. Competition covers rival vendors, internal builds and the option to do nothing. Both matter most in enterprise and security-heavy deals, where late-stage reviews often cause slips.

Who created the MEDDIC sales methodology?

It was developed in PTC's sales organization in the 1990s. Most accounts credit Dick Dunkel, with Jack Napoli and John McMahon, though sources differ on dates and credit. The extended eight-letter form was coined in 2005 by former PTC employees, according to court findings.

Is MEDDIC better than BANT?

Neither is better in general, and no independent study compares them directly. BANT suits quick early screening, when a rep decides whether an opportunity is worth opening. MEDDIC suits complex deals with many stakeholders, which is the common case when buying groups include five to sixteen people.

How do you find the economic buyer and the champion in a technical deal?

Start with the champion. Look for the hands-on adopter, such as an engineer using the product or posting publicly about the problem, then confirm their influence. Ask them to walk you through the decision process. The economic buyer is usually the VP Engineering or CISO who owns the budget.

Life’s too short
for bad data