MEDDIC Sales Methodology: The Complete Guide

What is the MEDDIC sales methodology?

The framework originated at PTC — a Boston-based engineering software company — in the mid-1990s. Two sales leaders, Jack Napoli and Dick Dunkel, built it after analyzing the common patterns in their highest-performing deals. The insight: every deal that closed shared six characteristics. Every deal that slipped or was lost was missing at least two of them. They built an acronym, trained a sales force, and watched annual revenue grow from $300 million to over $1 billion in less than a decade.

MEDDIC spread through the enterprise software world as PTC alumni moved into sales leadership roles at Oracle, Salesforce, SAP, and dozens of SaaS companies. Today it is the dominant qualification framework in complex B2B sales — estimated to be used by more than 60% of enterprise sales teams with average deal sizes above $50,000 (Highspot State of Sales Enablement, 2025).

What makes MEDDIC different from BANT (Budget, Authority, Need, Timing) is depth. BANT asks whether budget exists. MEDDIC asks whether the rep has met the person who controls the budget, whether that person sees the ROI, and whether the champion can defend the business case when the rep is not in the room. MEDDIC vs BANT breaks down the detailed comparison.

M — Metrics: quantify the outcome

Metrics is the first letter for a reason. It forces the deal into the language of business outcomes — revenue, cost, time, risk — and away from feature checklists. A rep who cannot answer "what does the buyer measure success by, in numbers" has not yet qualified the deal.

The discovery question that unlocks this element: "What does success look like in numbers — and by when?"

A strong Metrics answer sounds like: "We need to reduce time-to-hire by 40% before our Series B. Right now it takes 62 days to close an engineering role and we need it under 37 days or our head count plan breaks." That answer gives you the ROI frame, the benchmark, the timeline, and the consequence of inaction — all in two sentences.

A weak Metrics answer: "We want to improve efficiency." Do not accept it. Push: "If efficiency improves, what metric changes? By how much? What does that mean in dollars or headcount or risk?" A prospect who genuinely has a problem will have a number. A prospect without a number either does not have a real problem or is not far enough along in the buying process to qualify.

Metrics also serves as the ROI anchor you reference throughout the deal. When the economic buyer questions price in week six, you come back to the metric: "You told me each day of delay costs $28,000 in engineering opportunity cost. At three months of implementation versus three weeks, this decision is worth roughly $1.4 million in reclaimed capacity." That conversation is impossible without a strong Metrics answer early in discovery.

E — Economic Buyer: find the real decision-maker

The Economic Buyer is the person who controls the budget and can say yes or no without asking permission. This is not always the most senior person. It is the person whose P&L takes the charge. In a 10-person startup, it is usually the founder. In a 500-person company, it might be a VP of Engineering or VP of Sales — not necessarily the CFO.

The discovery question: "Who owns the budget for a decision like this — and who signs the approval?"

Most reps make two Economic Buyer mistakes. First, they accept "I think it goes through procurement" as a valid answer. That is not an answer — that is a shrug. Push your champion: "Walk me through the last time your team bought a tool at this price point. Who approved it? How long did that take?" Second, reps confuse identifying the EB with meeting the EB. The score is 0 until the rep has had a direct conversation with the Economic Buyer — even a 10-minute call. A name in a CRM field is not qualification.

The champion introduction plays a critical role here. Ask your champion: "Can you introduce me to [EB name] as part of our evaluation? I want to make sure we are building the business case the right way for their priorities." A champion who will not make this introduction is either not a real champion or does not have real access. Both are disqualifying signals. Read more about multi-threading at why multithreading a deal always fails.

A useful test: if your champion went on leave tomorrow, would the deal survive? If the answer is no, you are single-threaded on a non-EB and the deal is at serious risk. The Economic Buyer element of MEDDIC is designed specifically to force this conversation before it becomes a crisis at stage 4.

D — Decision Criteria: know the scorecard

Decision Criteria maps the technical, business, and personal criteria the buying team will use to make their choice. This includes the formal scorecard — feature checklist, integration requirements, security compliance, reference checks — and the informal criteria that never make it into an RFP: "We want to work with a vendor who will treat us like a real customer, not just another logo."

The discovery question: "If you were scoring vendors on a 10-point scale, what criteria would you use — and how would you weight them?"

The reason this letter matters is that it reveals the competitive landscape before the competition does. If the buyer says "integration with Workday is a hard requirement," and your product has a six-week implementation for that integration, you know this before committing your solution engineering team to a two-week evaluation. If a competitor already has a native integration, you know the criteria they will use to beat you.

Strong reps do not just collect Decision Criteria — they shape it. Early in the deal, before a formal RFP, a rep can educate the buyer on what good looks like: "In our experience, the three criteria that correlate most with successful implementations are: time-to-value under 30 days, CRM write path that does not require RevOps, and a pricing model that scales per seat rather than per event. How are those ranking in your evaluation?" This frames your strengths as the evaluation criteria before the buyer finalizes their scorecard.

D — Decision Process: map the paper trail

Decision Process is the sequence of steps, approvals, and reviews between "yes in principle" and "contract signed." It covers the people, stages, and timelines involved in moving from verbal commitment to closed-won. This is the letter most responsible for late-stage slippage.

The discovery question: "Walk me through how you evaluated and approved the last vendor purchase at this price point. Who was involved? What were the stages? How long did each take?"

A detailed Decision Process answer might sound like: "IT has to approve the integration plan — that takes about two weeks. Legal reviews the MSA and it usually takes 10 business days. Security does a vendor questionnaire, which can add another week if they have follow-up questions. Then the CFO signs anything over $50,000." That timeline — IT plus legal plus security plus CFO — is 30 to 40 working days. A rep who did not ask this question will forecast the deal to close in Q2 and discover in week eight that procurement adds another 20 days minimum. That is how Q2 deals slip to Q3.

Map the Decision Process visually in your CRM as a multi-step list with owners and expected durations. Share it with the champion and ask them to validate it. The act of sharing a draft timeline often surfaces stages the champion forgot to mention — and creates a shared commitment to hitting the end date. This is the foundation of a Mutual Action Plan. Read more at why deals slip every quarter.

I — Identify Pain: connect to urgency

Identify Pain is about more than listing problems. It is about connecting the pain to a cost that the economic buyer feels personally. A pain without a cost is a wish list. A pain without a deadline is a research project. A pain with both — a number and a date — is a deal.

The discovery question: "What happens to you, specifically, if this problem is not solved by [date the buyer mentioned]?"

There are three layers of pain worth probing. Surface pain is what the buyer mentions first: "Our reps spend too much time on admin." Business pain is the cost of that surface pain: "It is costing us 28 hours per rep per week in selling capacity, which means we are leaving roughly $2.4 million in pipeline unworked every quarter." Personal pain is the consequence to the buyer's career or performance review: "If we miss plan again this year, I will have a hard conversation about the team's headcount for 2027."

The third layer — personal pain — is the most powerful motivator and the least often asked about. Most reps stop at business pain because personal pain feels uncomfortable to probe. But the champion who has a personal stake in solving the problem is the champion who calls you on a Sunday to keep the deal alive when procurement adds a delay. That is the champion you want. Ask about their career context, not just the business context. Read the full discovery framework at discovery call framework.

The MEDDPICC variant converts "Identify Pain" to "Implicate Pain" — a subtle but important shift. Implicate Pain means the rep actively draws out the consequences of inaction, not just confirms the pain exists. "If this is not resolved by the time your Series B closes, what does that mean for the headcount plan?" forces the buyer to say the cost out loud, which increases their commitment to finding a solution.

C — Champion: build an internal ally

The Champion is the person inside the buyer's organization who wants you to win, has credibility with the economic buyer, and will actively advocate for your solution when you are not in the room. A champion is not a sponsor (who supports you passively), not a contact (who likes talking to you), and not a power user (who wants the features). A champion sells on your behalf.

The discovery question: "Who inside your organization is most invested in solving this problem — and would go to bat for the budget?"

Qualifying the champion requires testing their access and their willingness. Access test: "Can you set up a 30-minute call with [Economic Buyer's name] so I can make sure we are building the right business case?" A champion who cannot — or will not — make this introduction does not have the access your deal needs. Willingness test: ask the champion to do a small thing: review a one-pager, attend an internal meeting, or send a message to a stakeholder on your behalf. How quickly and completely they do it tells you how much political capital they are willing to spend.

Champions have personal stakes. A VP of Sales who wants the deal to close because it will make her team more efficient and prove her judgment to the CRO is a stronger champion than a manager who likes the product but has no budget authority and nothing to lose. Map the champion's personal pain (from the I letter) to their motivation to advocate. If the connection is clear, invest in arming them: give them the ROI one-pager, the competitor comparison, the security FAQ, and the implementation timeline. A champion without ammunition is a champion who loses the internal fight.

MEDDIC vs MEDDICC vs MEDDPICC: which version fits your team

Three variants dominate the market. They share the same six-letter core. The differences are additive — each variant adds complexity to handle a specific deal challenge.

When to add Competition (MEDDICC)

Add the Competition letter when your team is regularly losing late-stage deals to a named competitor — and the loss was not because of product gaps but because the competitor shaped the evaluation criteria early and your team found out late. MEDDICC forces the question: "Who else are you evaluating, what do they do well, and what do we need to do to win?" Ask it in discovery, not in week six.

When to add Paper Process (MEDDPICC)

Add Paper Process when deal cycles consistently exceed 90 days and when procurement, legal, InfoSec, or IT reviews regularly add 20 to 40 days after the verbal commitment. Paper Process treats the administrative review as a sales stage, not an afterthought. It maps who reviews the contract, what their typical timeline is, whether they use a standard MSA or require a custom SOW, and whether a security review is required. A rep who maps Paper Process in week two avoids the "everything was great but legal took four weeks" forecast disaster in week twelve.

The MEDDIC deal scorecard: 0 to 60

Score each MEDDIC element 0 to 10. The total score out of 60 drives pipeline decisions:

• 0–29Disqualify or return to discovery. Do not advance stage.
• 30–45Qualified but gaps present. Name the missing letters before the next forecast call.
• 46–60Advance with confidence. Focus on execution, not qualification.

How to score each element:

Run this scoring exercise on every deal above a threshold (typically 50% of quota attainment value or above) once per week. Use the result to prioritize where to spend the next five selling days. A deal at 35/60 with a weak Champion deserves a different investment than a deal at 50/60 with a weak Decision Process. The fix for each is different: the first needs a champion-building play; the second needs a procurement discovery call. Read more about pipeline health at why win rate drops below 20%.

Common MEDDIC mistakes that kill adoption

MEDDIC fails in most teams not because the framework is wrong, but because it is implemented wrong. Six failure modes account for the majority of MEDDIC rollouts that quietly collapse within 90 days.

• 1

  Running MEDDIC once, at stage 1

  Fix: MEDDIC is not a checkbox at discovery. Re-score every element after every call. A deal that was 50/60 at stage 3 can fall to 30/60 when the economic buyer changes.

• 2

  Accepting "I think" as an answer

  Fix: When the champion says "I think the CFO approves this," your Decision Process score is 3, not 8. Push for verified information, not assumptions.

• 3

  Skipping the Economic Buyer meeting

  Fix: Getting the champion to confirm a budget number is not the same as meeting the economic buyer. If the EB has not seen your demo or proposal, the deal is single-threaded and fragile.

• 4

  Documenting MEDDIC in free-text notes

  Fix: Free-text CRM notes do not give a manager visibility into what is missing. Use structured fields — one per letter — so gaps surface in the pipeline review, not at forecast.

• 5

  Using MEDDIC to justify the deal instead of qualify it

  Fix: The framework is a disqualification tool as much as a qualification tool. A deal with a 2/10 Champion is a deal to walk away from, not to close harder.

• 6

  Not translating Identify Pain to a compelling event

  Fix: Pain without a deadline is a wish list. Add a date: "What changes for you if this is not solved by June 30?" That date becomes your close date anchor.

One structural fix covers most of these: treat MEDDIC as a living document inside the CRM, not a one-time checklist. Every call should update at least one element. A manager who reviews deals in a MEDDIC-first pipeline review — "show me the scorecard, not the stage" — reinforces the habit without adding training time. Review the full pipeline discipline playbook at why your Salesforce pipeline looks bigger than it is.

How Gangly installs MEDDIC into every call workflow

The biggest MEDDIC adoption failure is the documentation tax. Reps know the framework. They do not always fill in the fields — because doing so means switching to the CRM mid-call or spending 20 minutes post-call reconstructing a conversation from memory.

Gangly removes the documentation tax by listening to the call and filling MEDDIC fields automatically. After every discovery or advancement call, Gangly generates a structured MEDDIC brief with:

• A score for each element (0–10) based on what was confirmed in the conversation
• Exact quotes from the transcript that support each score
• A list of gaps — elements that were not confirmed — with suggested next questions
• A draft CRM update with the MEDDIC fields pre-filled for rep review before pushing to Salesforce or HubSpot

The rep reviews the brief, edits any scoring that does not match their judgment, and approves the CRM push. The total time is under two minutes. The total time for the equivalent manual workflow — re-listening, note-taking, CRM entry — is 18 to 25 minutes per call (Gangly internal time-audit data, Q1 2026).

The scoring consistency is the second benefit. When MEDDIC scores are filled by the rep from memory, the Economic Buyer element gets marked 8/10 whenever the rep had a good conversation — even if they never confirmed the EB had budget. When Gangly fills the score based on what was actually said in the transcript, the 8 becomes a 4 when the budget question was not asked. That difference shows up in the pipeline review before the deal slips, not after.

The Gangly MEDDIC workflow also surfaces recommended next questions before the following call — pulling from the gap analysis in the current MEDDIC brief. If Decision Process was scored 3/10 because no procurement or approval steps were mapped, Gangly adds a suggested question to the call prep brief for the next meeting: "Walk me through how you approved the last vendor at this price point." The rep sees it before the call. The qualification improves without additional training. See the full AI sales assistant guide for the broader workflow.

For managers, the consistency gain is significant. When every deal has a MEDDIC score backed by transcript evidence, pipeline reviews shift from "tell me what you know" to "show me the gaps." That change alone — from rep memory to documented qualification — typically cuts pipeline review time by 30 to 40 minutes per deal, according to reps on the Gangly platform in Q1 2026.