Home / Glossary / MEDDIC
Frameworks · enterprise sales qualification · deep dive

MEDDIC, operated properly.

The dominant enterprise sales qualification framework — Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion. Created at PTC in 1996. Still the cleanest framework taught to enterprise AEs in 2026. But most teams operate it as a checklist filled in after the deal closes — which captures none of its real value. This is the opinionated deep-dive: what MEDDIC actually is, why champion is load-bearing, when to use MEDDPICC instead, and how modern signal-anchored selling sharpens every field.

Category: Frameworks · Read time: 14 min · Updated: 2026-05-24 · MD-1.0
TL;DR
MEDDIC is a 6-field qualification framework created at PTC in 1996 and still dominant in enterprise B2B sales in 2026: Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion. The framework's real value isn't the checklist — it's the conversation guide that forces reps to surface hidden risks early. Most teams misuse MEDDIC by filling in fields after deals close (CRM theater) instead of using the fields to structure discovery conversations. Champion is the load-bearing letter: deals with an identified, met, validated champion close at 2-3x the rate of deals without. MEDDPICC and MEDDICC add Paper Process and Competition for longer/more contested cycles. Modern signal-anchored selling sharpens MEDDIC because public signals reveal real pain (the "I") that interview-elicited pain often misses.

01What MEDDIC actually is

MEDDIC is an acronym for the six qualification dimensions that a senior enterprise AE should be able to articulate on every deal above ~$25K ACV. The letters stand for:

  • M — Metrics. The quantifiable economic outcome your solution drives for this customer. Not "improved efficiency" — actual numbers ("$340K saved annually" or "4-hour reduction in dbt build times").
  • E — Economic buyer. The person who controls the budget and can override procurement. Often two layers above the champion. The person who signs.
  • D — Decision criteria. The explicit + implicit criteria the buying team will use to choose between you and alternatives. Technical, commercial, political.
  • D — Decision process. The path from current state to signed contract — every meeting, approval, security review, procurement cycle, board sign-off. Including the unwritten political steps.
  • I — Identify pain. The specific operational pain your solution removes. Verified — not assumed from the champion's pitch. Quantifiable. Tied to a metric (the M).
  • C — Champion. The internal advocate who pushes your deal forward when you're not in the room. Has personal pain the product solves, has political capital to spend, has a credible internal sponsor.

Each letter is both a question to answer ("who is the economic buyer?") and a field to fill in ("EB: Sarah Chen, CFO, joined Q3 2025"). The discipline is making sure all six are answered with confidence by stage 3 of the sales cycle — and red-flagging any that aren't.

The lineage

Created by Jack Napoli, Dick Dunkel, and John McMahon at PTC (Parametric Technology Corporation) in 1996. The framework was internal at PTC for over a decade — PTC's enterprise sales motion was so successful (compound 30%+ growth through the late 1990s) that the framework leaked into the broader enterprise software world through PTC alumni who became sales leaders at MongoDB, Snowflake, Cloudflare, Okta, and a dozen other enterprise companies.

By 2015, MEDDIC was the dominant qualification framework taught at enterprise sales bootcamps (Force Management, Winning by Design, Pavilion). By 2020, it was the default. In 2026 it remains the framework — but the way it's operated has drifted from its original intent in ways worth correcting.

02Why it became dominant (1996-2026)

MEDDIC won the qualification-framework wars for three reasons that are still true.

1. It's tuned for multi-stakeholder enterprise deals, not single-buyer SMB deals

The framework MEDDIC replaced was BANT (Budget, Authority, Need, Timing) — created at IBM in the 1960s for single-buyer mainframe sales. BANT assumes one person knows budget AND authority AND need AND timing. That model died around 2015 as enterprise deals shifted to 5-7 stakeholder buying committees. MEDDIC's six fields are structured to surface the multi-stakeholder reality: Economic buyer (different from champion), Decision process (multi-step, multi-meeting), Champion (the internal advocate). The fields map to the deal anatomy, not to a single conversation.

2. It surfaces hidden risk early

The most expensive deals are the ones that look great in stage 2 and die in stage 4 because of something the AE didn't know existed. MEDDIC's structure forces those unknowns to be named: "What's the Decision process? Who has to sign? When does procurement get involved?" An AE who can't answer those questions by stage 3 has a deal with hidden landmines. Forcing the question early — before forecasting commit, before exec involvement — saves the org from late-stage surprises.

3. It scales to deal review meetings

Sales managers running weekly deal reviews need a shared vocabulary for talking about pipeline. MEDDIC provides it. "What's the M on this deal?" "Have you met the EB?" "How's the champion?" Six standard questions that map across every deal in the pipeline. Without a shared framework, deal reviews devolve into anecdotes; with MEDDIC, they become structured triage.

The structural advantage
SPIN selling (1988) was a discovery technique — useful in the conversation. Challenger Sale (2011) was a positioning approach — useful in the pitch. MEDDIC is the only major framework that's a pipeline-management system: it works across every stage, every deal, every manager-rep conversation. That structural property is why it outlasted the others as the dominant enterprise framework.

03The 6 fields, in depth

The shallow version of MEDDIC is the letters. The operational version is what each letter actually demands of the AE and what questions surface the answer.

M
Metrics
The quantified outcome
The dollar-amount or measurable improvement your solution drives. Must be a number the customer can defend internally — not your value claim, their value claim. "30% reduction in warehouse query time" or "$340K saved annually." Generic ROI claims fail this test; specific customer-validated numbers pass.
If we delivered this perfectly, what would you measure to know it worked?
E
Economic buyer
Who actually signs
The person who can release budget and override procurement objections. Almost never the champion. Often two layers above the user. Title varies — CFO, CRO, VP Eng, depending on deal type. The test: if procurement says no, this person can override.
If you wanted to push this through without delay, who would you escalate to?
D
Decision criteria
The yes/no framework
The explicit AND implicit criteria the buying team will use to evaluate. Explicit: feature list, security requirements, pricing. Implicit: political fit, exec preference, "we don't want to switch vendors twice in 6 months." The implicit criteria kill more deals than the explicit ones.
What would have to be true for this to be an obvious yes? And what would make it a no?
D
Decision process
The path to signed
Every meeting, approval, security review, legal redline, board sign-off between today and the contract. Including the political steps the champion will downplay. Maps to the Mutual Action Plan — same artifact, different vocabulary.
Walk me through the steps between today and a signed contract. Who's involved at each step?
I
Identify pain
The verified problem
The specific operational pain your product removes. Verified via multiple sources, not just the champion's claim. Tied directly to the Metrics field — if the pain isn't quantifiable, the M is fiction. Modern signal data sharpens this dramatically (covered in §8).
If we did nothing, what would still be broken in 90 days? In 12 months?
C
Champion
The internal advocate
The person who pushes your deal forward when you're not in the room. Three required properties: (a) personal pain your product solves, (b) political capital to spend, (c) credible internal sponsor. "Friendly contact" is not a champion. (Covered in depth in §4.)
Who is going to sell this internally when I'm not on the call? What's their motivation?

Notice how each field requires multi-source verification, not single-source belief. The champion can claim to be the economic buyer; you verify by asking three other stakeholders. The champion can claim the pain is huge; you verify by reading public signals, customer-voice mentions, and competitor analyst reports. MEDDIC fields are confirmed, not asserted.

04The 1 letter that does 60% of the work

Of the six MEDDIC fields, one is structurally load-bearing. The Champion is the single most predictive variable for deal outcome — more than ACV, more than industry, more than competitive intensity. Deals with an identified, met, validated champion close at 2-3x the rate of deals without one.

What a real champion is

A champion has three properties simultaneously. Miss any one and they're not a champion:

  1. Personal pain your product solves. Not company pain — personal pain. The champion themselves benefits when this deal closes (faster work, better data, less manual labor, exec credit for shipping). If the champion only benefits abstractly ("good for the company"), they won't fight for the deal when it stalls.
  2. Political capital to spend. Has been at the company long enough, performed well enough, and built enough relationships that other stakeholders will listen to them. New hires (under 6 months) usually lack the capital. Junior ICs usually lack the access.
  3. Credible internal sponsor. Reports to someone who would back them up in a budget fight. Without an internal sponsor at one level above, the champion is fighting alone — and most lose.

The test: would they sell this for free?

The cleanest diagnostic: would this person be selling the deal internally even if we weren't paying them, even if we weren't on the call? If yes, they're a champion. If no — if they're being nice but they wouldn't push the deal when nobody's watching — they're a friendly contact, which is something different and considerably weaker.

Champion absence is silent until it kills the deal

Most deals that die from "we decided to stay with our current vendor" or "the timing isn't right anymore" died because no real champion was selling internally when the AE wasn't there. The AE often doesn't realize there was no champion until they read the dead-deal postmortem. By then it's too late.

The political reality
Champions get hired away, promoted, reorganized, or leave companies. The expected lifespan of a champion at any single company is roughly 18 months. The implication: if your sales cycle is 90+ days and you don't have at least two champions multi-threaded by stage 3, you're one departure away from losing the deal. The "multi-threaded with backup champion" requirement is what multi-threading is actually solving for — it's not just relationship-building, it's champion redundancy.

05The mistake every team makes

The single most common MEDDIC failure mode: operating it as a CRM checklist filled in after the deal closes, rather than a conversation guide that drives discovery.

Walk into 100 sales orgs that say they "use MEDDIC" and ~70 of them will show you a beautiful Salesforce dashboard with MEDDIC fields populated on every opportunity. Click into the field history and you'll see: blank, blank, blank, blank, all-fields-filled-in-one-day-the-day-after-closed-won.

That's not MEDDIC. That's CRM theater.

The real value of MEDDIC is the discovery conversation it forces. The fields aren't records to fill in; they're questions to answer in the deal itself. If you don't know who the economic buyer is by stage 3, MEDDIC tells you that fact — and tells you to find out before stage 4. If you don't have a verified champion, MEDDIC tells you that fact — and tells you to either identify one or downgrade the deal's forecast.

Common · MEDDIC as CRM theater
Stage 4: "Yeah this deal is great, champion is super excited."
Stage 5: "Procurement is being a little tough but we'll get through it."
Closed-lost: "Customer decided to delay. We'll fill in MEDDIC fields for the postmortem."
The fields get filled in once. They never inform the work.
Correct · MEDDIC as deal-shaping tool
Stage 2: "We haven't met the EB. Action: champion intro by next Friday."
Stage 3: "Decision process unclear — security review timing unknown. Action: scoping call with InfoSec."
Stage 4: "Champion is solid but no backup. Action: thread to VP Engineering by EOQ."
Every field is either confirmed or blocking the next move.

How to fix it organizationally

Three changes a sales manager can make to shift the team from theater to operational use:

  1. Make MEDDIC fields required at stage transitions, not at close. Salesforce can enforce field validation on stage change. If the rep can't move a deal from stage 2 to stage 3 without a populated Economic Buyer field, the rep does the work to identify the EB — or honestly admits they don't know.
  2. Run deal reviews against MEDDIC, not against forecast. Instead of "what's your commit number this quarter," ask "what's the C on the Acme deal?" The conversation forces the rep to think in framework terms, not just dollar terms.
  3. Coach reps on the conversations, not the fields. The skill is asking the questions that surface MEDDIC answers — "If you wanted to push this through faster, who would you escalate to?" — not filling in the field after the fact. Sales coaching is conversation coaching; MEDDIC is the scaffolding.

06MEDDPICC and MEDDICC variants

MEDDIC evolved over its 30-year history. Two variants are worth knowing.

MEDDIC
M · E · D · D · I · C
Original 1996. Six fields. Best for deals under 6 months, with light competitive presence, and predictable procurement. Most B2B SaaS deals at $25K-100K ACV fit here.
MEDDICC
M · E · D · D · I · C · C
Adds Competition. Explicitly tracks who else is in the deal, their positioning, your relative strengths/weaknesses. Important for deals over $100K ACV where 2-4 vendors are usually in the room.
MEDDPICC
M · E · D · D · P · I · C · C
Adds Paper Process. Explicitly tracks legal, procurement, security-review, and contract-redline timelines. Critical for enterprise deals over $250K ACV where the paper process alone can take 60-90 days.

Which variant to use

Practical guidance: use the simplest variant that captures your deal complexity. Over-frameworking small deals creates rep frustration and field-fatigue. Under-frameworking large deals creates late-stage surprise.

  • Under $25K ACV, single-buyer: Even MEDDIC is overkill. Use a lighter 3-field framework (pain, decision-maker, timeline) and save the energy.
  • $25K-100K ACV, 2-4 stakeholders: Standard MEDDIC. The 6 fields scale to this deal size cleanly.
  • $100K-$250K ACV, 3-7 stakeholders, competitive bake-off: MEDDICC. Adding the Competition field surfaces positioning risks that pure MEDDIC misses.
  • $250K+ ACV, 5+ stakeholders, formal procurement: MEDDPICC. The Paper Process field is what keeps enterprise deals from slipping a quarter unexpectedly.

Most modern enterprise sales orgs default to MEDDPICC because the deal mix has shifted upmarket. Most mid-market and SMB-focused orgs stay on MEDDIC. Pick based on your ACV band, not based on what the latest book recommended.

07MEDDIC vs SPIN, Challenger, BANT, GAP

MEDDIC isn't the only qualification framework taught in B2B sales. The honest comparison:

What it does well
Where it fails
Best fit
MEDDIC
Multi-stakeholder enterprise deals, surfaces hidden risk early, pipeline-management vocabulary.
Overkill for small/transactional deals. Becomes CRM theater if not operationally enforced.
$25K+ ACV enterprise B2B
Fast disqualification, simple to teach, works in 5 minutes of phone qualification.
Assumes single-buyer model. Disqualifies good deals where champion can't immediately answer all 4 fields.
Inbound qualification, SDR pre-quals, SMB
SPIN selling
Discovery technique — orders questions to surface pain before pricing. Excellent for first conversations.
Doesn't help with multi-stakeholder dynamics or deal-process management. Conversation-level, not pipeline-level.
Discovery calls, paired with MEDDIC
Challenger Sale
Positioning approach — teach buyers something new about their problem, control the conversation. Strong in commoditized markets.
Requires high-skill reps and deep market expertise. Hard to scale to junior teams.
Differentiated enterprise pitches
GAP selling
Modern (2018) — focuses on gap between current state and desired state. Heavy on discovery discipline.
Light on the deal-management mechanics MEDDIC covers. Often paired with MEDDIC rather than replacing it.
Discovery-heavy AE training, paired with MEDDIC

The honest answer: most teams use multiple frameworks layered

The framing-war between MEDDIC vs Challenger vs GAP is mostly publishing-industry positioning. In practice, mature enterprise sales orgs use MEDDIC as the pipeline-management framework + SPIN or GAP as the discovery technique + Challenger as the pitch positioning. The frameworks operate at different layers; combining them isn't contradictory.

The exception is BANT — which is genuinely outdated for modern B2B and should probably be retired from most playbooks except inbound pre-qualification.

08How signals sharpen every MEDDIC field

The most-overlooked evolution in modern MEDDIC operation is what public buying signals do to the qualification process. Pre-signal-era, every MEDDIC field was answered through the champion's interview-elicited claims. In 2026, with mature signal-anchored data, every field can be cross-validated against public ground truth.

Metrics — sharpened by industry benchmarks

The champion claims "this saves us 40 hours per week." Without external reference, you have no way to validate. Public benchmarks (from glossary entries like reply rate, or industry analyst data) give you a calibration anchor. "Saves 40 hours per week" is plausible if the industry benchmark for your category is 25-60 hours; suspicious if it's 5-15 hours.

Economic buyer — sharpened by exec move signals

The champion says "the CFO Sarah signs deals like this." A signal-mining tool tells you Sarah joined as CFO 90 days ago, replacing the previous CFO who left after 4 years. That changes everything about how the EB will evaluate your deal — Sarah is making her first big budget decisions and will be more cautious than a 4-year veteran would be.

Decision criteria — sharpened by tech-stack data

The buying team's tech stack tells you what their unstated technical criteria are. A team running heavy Snowflake + dbt + Looker has implicit modern-data-stack alignment criteria they won't mention in discovery — but you can position against. Public tech-detection data (BuiltWith, Wappalyzer, Mama's tech-stack signals) makes these implicit criteria visible.

Decision process — sharpened by past procurement data

Past procurement timelines (visible via vendor case studies, past deal announcements, internal blog posts) reveal how this company actually buys. A company that announced a Snowflake deal 9 months after their first conversation tells you their procurement runs 9 months. The champion will tell you "we can move fast." The data tells you they can't.

Identify pain — sharpened by voice mining

The single biggest sharpening. The champion describes pain through their own framing — often softened to make their team look competent. Public voice mining (HN comments from their engineers, Reddit posts in industry subs, G2 review themes, conference Q&A) reveals the unfiltered version of their pain. "We've had some warehouse cost concerns" (champion's version) vs "we burned $200K in surprise Snowflake bills last quarter and the CFO is furious" (voice-mined version) — same pain, very different deal urgency.

Champion — sharpened by job-change signals

Your champion's career trajectory tells you about their political capital. A champion who's been at the company 18+ months in a stable role has accumulated capital. A champion in their first 60 days has none. A champion whose past two companies were acquired by your customer's competitors has different motivations than a champion whose past companies are happy customers of yours. Job-change signals reveal these patterns.

The modern MEDDIC AE
In 2026, the senior enterprise AE who hits 130%+ of quota operates MEDDIC against signal-anchored data, not just champion interviews. Every field gets cross-validated. The champion's claim is the hypothesis; the signal data is the test. Reps who only interview their champions get filtered information. Reps who pair MEDDIC with signal-mining get the ground truth.

09Common mistakes that kill the framework

Mistake 1 · Treating champion as a single role rather than a property bundle
"Sarah is our champion." Maybe. Does Sarah have personal pain (not company pain)? Does Sarah have political capital to spend? Does Sarah have a credible internal sponsor? If any answer is no, Sarah is a friendly contact, not a champion. Calling friendly contacts "champions" is the most common cause of forecast-miss surprise.
Mistake 2 · Confusing the user with the economic buyer
"The VP Data is signing." Sometimes — for tools the data team buys autonomously under their own budget. Often not — most procurement above $50K goes to the CFO or COO regardless of who uses the tool. If the AE hasn't met the EB by stage 3, the EB is a wildcard the deal will hit unprepared in stage 5.
Mistake 3 · Filling Metrics with vendor marketing claims
"We help customers achieve 4x ROI." That's not a Metric. The M field must contain a number THIS customer will defend internally — sourced from their own data, validated by their finance team, defensible to their CFO. Vendor-side ROI claims fail the M test. If you can't get the customer to commit to a specific number, the M field is empty regardless of what you've written in there.
Mistake 4 · Skipping the Decision process discovery
"They told me they want to start in Q1." Great — but what are the 14 steps between today and Q1 start? Who has to approve the security questionnaire? What's the procurement intake timeline? When does legal review begin? Most deals slip not because of customer reluctance but because the AE didn't map the process and missed a sub-step. The Decision Process field is where slippage gets caught early.
Mistake 5 · Using MEDDIC as a closing tool instead of a qualifying tool
MEDDIC's primary job is disqualification, not closing. The framework is meant to kill bad deals early so AE capacity goes to deals that will close. Teams that use MEDDIC only to confirm "great deal, we're going to win" miss the framework's actual value — which is "we don't have a champion, downgrade this from commit to upside." Reps who downgrade aggressively beat reps who don't.
Mistake 6 · Filling the framework once and never updating it
MEDDIC fields drift. The EB you identified in stage 2 might leave the company by stage 5. The Decision criteria the champion told you in stage 3 might shift after a board meeting in stage 4. MEDDIC fields need a stage-by-stage revalidation — confirm the EB is still in seat, confirm the criteria haven't changed, confirm the champion is still selling. Static MEDDIC is dead MEDDIC.
Try Mama free

MEDDIC discovery is only as good as the data behind it.

Champion interviews give you the filtered version. Signal-anchored data gives you the ground truth. Mama surfaces the public signals — funding rounds, exec moves, tech changes, public voice — that let you cross-validate every MEDDIC field before the deal reaches stage 4. Start the free trial and run signal-anchored MEDDIC on your next 5 deals.