MEDDIC

What each MEDDIC letter means

Metrics are measurable outcomes the buyer wants. A rep might hear that the team spends too much time preparing reports. The relevant metric could be analyst hours, reporting delays, or errors that require rework. Do not invent a savings number because a buyer used the word "inefficient." Ask how they measure the current problem and whether anyone has agreed on a target.

Economic Buyer is the person with authority over the spending decision. A department user may be enthusiastic but unable to allocate budget. The seller needs to understand who can approve the purchase and what that person expects to see. Authority can be shared across a buying group, so a job title is not a substitute for asking how approval works.

Decision Criteria are the standards the buyer will use to compare options. Requirements may include security, integration, cost, user adoption, or an internal policy. Ask which are mandatory and who set them. A criterion voiced by one user may not survive procurement or security review.

Decision Process is the sequence of steps and people between evaluation and a decision. It includes demonstrations, technical reviews, stakeholder meetings, and final approval. The framework's original form does not give the later paperwork its own letter; MEDDPICC adds a Paper Process. MEDDICC, another variant, adds Competition. The MEDDICC methodology explanation distinguishes these versions.

Identify Pain means establishing the buyer's actual business problem and the consequences of leaving it unresolved. A complaint about a slow tool can be real without being urgent. Ask who is affected, what has happened because of the delay, and why the team is evaluating a change now.

Champion is a person inside the buying organization who understands the proposed solution, has influence, and actively helps the evaluation move forward. A friendly contact isn't necessarily a champion. Ask whether the person can explain the case to colleagues when the seller is absent and whether they have a reason to do so.

How MEDDIC works on a real opportunity

Use the six dimensions as a map of uncertainty. At the start of a deal, the team may know the problem but little about budget authority. After a demonstration, the buyer may explain the technical criteria but still avoid naming the approval process. Revisit the map after each conversation and record the evidence behind each answer.

For example, an operations leader says they want to cut weekly reporting work. The AE asks how many people prepare the report and how they would measure an improvement. The buyer can describe the workflow but does not know the current hours. That is a promising Metrics hypothesis, not a quantified outcome. Mark it as unverified and arrange to review the baseline with the reporting team.

The same buyer says the CFO "should be fine" with the purchase. Do not mark Economic Buyer complete. Ask whether the CFO has approved similar purchases, what threshold triggers review, and who will present the business case. The difference between "should be fine" and an actual approval path can decide whether a deal closes this quarter.

The discovery call questions guide gives ways to explore these topics without reading an acronym aloud. A natural conversation starts with the buyer's situation. Follow-up questions then reveal missing evidence. If you ask for budget before understanding why the buyer took the call, you may get a defensive answer and learn little.

There is no universal order for collecting the letters. Pain may surface first on one call, while decision criteria lead another. MEDDIC is a qualification framework, not a fixed presentation sequence. Use the buyer's answers to decide the next useful question.

When MEDDIC is useful and when it is too heavy

MEDDIC helps most when a deal involves multiple stakeholders, a material purchase, and a real evaluation period. It gives the AE and manager a shared way to discuss missing evidence. A manager can ask, "Who confirmed the decision criteria?" rather than "Do you feel good about the deal?" The second question invites confidence; the first invites a source.

A short, low-value transaction may not justify a formal six-part review. The buyer may be able to decide during one conversation. Even then, the underlying questions still matter: what problem is being solved, who can decide, and what must happen next? Use judgment about how much documentation the deal warrants.

Before a meeting, prepare the unresolved questions and the likely stakeholders. The discovery call preparation guide explains how to assemble a focused call plan. Do not arrive with a script that forces every MEDDIC category into one call. If the buyer offers a new concern, follow it and return to the checklist after the meeting.

During a live call, distinguish an answer from proof. "Security is important" does not identify a decision criterion until the buyer names the review or standard. "Our VP supports this" does not establish a champion until you know what the VP will do internally. A useful live follow-up is, "What will your security team need to see before they can approve a vendor?" It turns a vague priority into a testable next action.

Common MEDDIC mistakes

Treating MEDDIC as a CRM completeness score is the most common failure. A rep can populate every field with assumptions and still know almost nothing about the buyer's decision. Record the source of each answer: buyer statement, document, meeting outcome, or seller inference. Where the source is inference, write the question needed to confirm it.

Do not confuse a sponsor with an economic buyer. A sponsor may persuade colleagues and arrange meetings but still lack spending authority. A budget owner may approve a proposal without championing it. Both relationships matter, and the framework asks different questions about each.

Avoid treating the lack of a metric as a reason to invent one. Some buyers know a problem is serious but have not measured its cost. Offer a method for estimating a baseline and invite the buyer to validate it. If nobody will help quantify or sponsor the problem, the opportunity may not yet be ready for a forecast. That limitation is worth stating plainly.

How Sales Copilot uses MEDDIC

Sales Copilot by Cluely AI can put a Prospect brief and Playbook in place before the call, let the rep rehearse with an AI buyer, show an answer and a question to ask back during the live conversation, and provide a transcript-linked Debrief afterward. A team can use that loop to practice identifying an unverified MEDDIC answer and carry the open question into the next meeting. The live-call assistant supports the conversation; the rep must still establish what the buyer actually said.

Frequently asked questions

What is MEDDIC?

MEDDIC is a B2B qualification framework covering Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, and Champion. It helps sales teams test whether a complex opportunity has the evidence and buyer support needed to progress.

What is the difference between MEDDIC and MEDDPICC?

MEDDPICC expands MEDDIC by adding Paper Process and Competition. Some organizations also use MEDDICC, which adds Competition without a separate Paper Process category.

Is MEDDIC a sales process?

No. It is a framework for examining deal qualification. A team's sales process defines stages and required actions; MEDDIC helps the team assess what it knows about the buyer within those stages.

Should reps ask all six MEDDIC questions in one call?

No. The categories are a map for a deal, not a script. Ask questions that fit the conversation, document what was confirmed, and revisit missing evidence in later meetings.