MEDDIC is a six part qualification framework for complex B2B sales: Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain and Champion. It was built for account executives managing enterprise deals over months. It was not built for a seven minute cold call. Used properly by SDRs it is one of the most useful tools in outbound, because it tells you what a qualified meeting actually needs to contain. Used badly it turns a cold call into an interrogation.
This guide explains each element, which ones an SDR can realistically qualify on a first conversation, how MEDDIC compares with BANT and MEDDPICC, and how to hand a MEDDIC snapshot to an AE so the first meeting starts in the right place. For a broader comparison of frameworks, see our BANT vs MEDDIC vs SPIN guide.
TLDR
- MEDDIC is a deal management framework. BANT is a lead triage filter. They do different jobs and most good teams use both.
- On a cold call an SDR can usually confirm Identify Pain, get a read on Economic Buyer and sometimes spot a Champion. Metrics, Decision Criteria and Decision Process belong to the AE's discovery.
- Do not try to complete MEDDIC on a first call. Try to book a meeting that gives the AE the best chance of completing it.
- Hand over a MEDDIC snapshot with every meeting: what was confirmed, what was inferred, what is unknown.
- MEDDPICC adds Paper Process and Competition. Relevant for enterprise AEs, rarely for SDRs.
Where MEDDIC came from
MEDDIC was created inside PTC, the Boston based software company, in the mid 1990s. Dick Dunkel coined the acronym in 1996 while working under sales leader John McMahon and alongside Jack Napoli on the internal training team (1). PTC grew from inception to a billion dollars in revenue in about a decade through forty consecutive quarters of growth, and the qualification discipline behind that run spread through the enterprise software industry as PTC alumni moved on (2).
The point of the history is the context. MEDDIC was designed for large, multi stakeholder software deals where losing late in the cycle was catastrophically expensive. Its purpose was to force reps to know, at every stage, whether a deal was real. That purpose translates directly to outbound: the SDR's job is to make sure the meeting handed to the AE is real.
The six elements, and what they mean for an SDR
M: Metrics
What it means. The quantifiable business outcome the buyer expects. Revenue, cost, time, risk, in numbers.
Can an SDR get this on a cold call? Rarely, and you should not push for it. A decision maker who has known you for ninety seconds will not tell you their target for reducing churn by a percentage. What you can do is listen for a number they volunteer ("we're losing about two days a week on this") and capture it.
What to hand the AE. Any number the prospect mentioned unprompted, and the topic where metrics are likely to live.
E: Economic Buyer
What it means. The person who can release budget for this purchase. Not the person who evaluates it. Not the person who uses it.
Can an SDR get this on a cold call? Often, partially. One question does most of the work: "If this turned into something, who else would need to be involved in the decision?" The answer tells you whether the person you are speaking to holds the budget, and who does if they do not.
What to hand the AE. Confirmed or inferred economic buyer, and whether the meeting is with them or with an influencer.
D: Decision Criteria
What it means. How the buyer will evaluate options. Features, integrations, security, price, references, vendor size.
Can an SDR get this on a cold call? No. This is AE discovery. Forcing it on a cold call sounds like a sales script and kills rapport.
What to hand the AE. Nothing, unless volunteered. Note anything the prospect said about a current vendor or a failed evaluation.
D: Decision Process
What it means. The steps, approvals and timeline the buyer will follow to purchase.
Can an SDR get this on a cold call? Only the edges. Whether there is a budget cycle, a project already scoped, or a renewal date. "Is this something you're looking at this financial year or further out?" is as far as you should go.
What to hand the AE. Any timing signal. Renewal dates and budget cycles are the most valuable.
I: Identify Pain
What it means. The specific business problem, and its cost, that your product addresses.
Can an SDR get this on a cold call? Yes. This is the element cold calls are built for. A good opener is a pain question, not a product statement. "How are you handling X today?" followed by "and what does that cost you when it goes wrong?" surfaces pain in under two minutes with a willing prospect.
What to hand the AE. The pain in the prospect's own words. Verbatim if you can. This is the single most valuable line in the handover.
C: Champion
What it means. Someone inside the account who wants you to win and has the influence to help.
Can an SDR get this on a cold call? Sometimes you can spot one. The person who engages, asks a second question, or says "I've been trying to get us to look at this" is a potential champion. You cannot confirm a champion on a cold call; you can flag a candidate.
What to hand the AE. Whether the contact showed champion behaviour, and what they said that suggested it.
MEDDIC on a cold call: the realistic scorecard
| Element | Realistic on a cold call? | SDR target | Hand to AE as |
|---|---|---|---|
| Metrics | Rarely | Capture volunteered numbers | Inferred |
| Economic Buyer | Partially | Confirm who holds budget | Confirmed or inferred |
| Decision Criteria | No | Do not push | Unknown |
| Decision Process | Edges only | Timing signal | Inferred |
| Identify Pain | Yes | Pain in their words | Confirmed |
| Champion | Flag only | Note engagement | Candidate |
An SDR who confirms Pain, gets a read on Economic Buyer and flags a Champion candidate has done an excellent job. That is a qualified meeting. Trying to do more usually costs you the meeting.
A MEDDIC question bank for SDRs
Questions phrased as conversation, grouped by the element they surface. Use two or three per call, never the lot.
Identify Pain. - How are you handling [process] today? - Where does that break down, if it does? - What does it cost you when it goes wrong, roughly, in time or money or risk? - Has that got better or worse over the last year?
Economic Buyer. - If this turned into something, who else would need to be involved? - Where do decisions like this usually get made, at your level or above? - Is there a budget owner for this area, or does it sit across a few?
Champion (spotting, not confirming). - Have you tried to get this looked at before? - Is this something you personally want fixed, or is it more of a background irritation?
Decision Process (edges only). - Is this something you would look at this financial year or further out? - Is there a renewal or a project that would bring it forward?
Metrics (listen, do not push). - When they volunteer a number, repeat it back: "so roughly two days a week across the team".
Decision Criteria and Competition. Do not ask on a cold call. Capture if volunteered.
An illustrative cold call, annotated
A composite sketch, not a transcript of any real call, showing how the elements surface naturally in under four minutes.
SDR: Morning, it is [name] from [company]. I will be quick. I work with finance teams at firms your size on month end close, and I wanted to ask how long yours is taking at the moment.
Prospect: Too long. About eight working days.
*(Pain, volunteered, with a number. Metrics captured.)*
SDR: Eight days. Is that mostly the reconciliation side or the reporting side that drags?
Prospect: Reconciliation. We have three entities and it is all spreadsheets.
*(Pain sharpened. Situation confirmed.)*
SDR: Right. Has anyone tried to fix that before, or has it just been lived with?
Prospect: I have raised it twice. It never gets prioritised.
*(Champion candidate. Also a signal about Decision Process: someone above is deciding.)*
SDR: Who does it get raised to?
Prospect: The CFO, and then it goes to the IT committee.
*(Economic Buyer identified. Decision Process edge captured.)*
SDR: Makes sense. Look, I am not going to try to sell you anything on this call. What I can do is put twenty minutes with one of our team who has helped a few multi entity finance teams get close down under five days, and you can compare notes on how they did it. Would Thursday or Friday suit?
*(The ask: a conversation, not a demo. Framed around the pain the prospect named.)*
Prospect: Friday morning.
Handover to the AE: Confirmed pain (eight day close, spreadsheet reconciliation across three entities). Confirmed economic buyer (CFO, via IT committee). Champion candidate (has raised it twice). Metric volunteered (eight days). Unknown: criteria, competition, budget. Suggested opening: "you mentioned the eight day close and the three entities, I would like to start there".
Common MEDDIC mistakes on SDR teams
Interrogating. Asking all six elements in order. The prospect hears a form and disengages.
Confusing evaluator with economic buyer. The person who will run the trial is rarely the person who signs. Ask who signs.
Booking the champion candidate without mapping the buyer. A meeting with an enthusiastic influencer and no path to budget produces a good conversation and no opportunity.
Writing "N/A" for unknowns. The handover should say unknown, not not applicable. The AE needs to know what to find out.
Treating metrics as a question. Metrics come from listening and repeating back, not from asking a stranger for their KPIs.
MEDDIC and the CRM
If the handover lives in a free text field it gets lost. Six fields on the meeting or lead record, each with a confirmed / inferred / unknown selector and a short text box:
- Pain (verbatim)
- Economic buyer (name and title)
- Champion candidate (name and evidence)
- Metrics (any number volunteered)
- Decision process (timing and route)
- Criteria and competition (usually unknown at SDR stage)
Report on the share of booked meetings with pain confirmed and economic buyer confirmed or inferred. Those two fields predict meeting to opportunity rate more reliably than anything else the SDR captures.
MEDDIC vs BANT: which should SDRs use?
This is the most searched question about MEDDIC, and the answer is that they are not alternatives.
BANT (Budget, Authority, Need, Timeline) is a triage filter. It was developed at IBM decades ago to sort high volumes of inbound interest quickly (3). Four questions, a yes or no, move on. It works at the SDR stage for fast qualification of simpler deals and as a first pass on anything.
MEDDIC is a deal management framework. Six dimensions, each scored and re scored as the deal progresses. It works for AEs managing complex, multi stakeholder opportunities over weeks or months.
Most good teams use BANT logic to decide whether to book the meeting and MEDDIC to run the deal after it. On a cold call, an SDR is effectively running a soft BANT (need first, authority second, timing if offered, budget rarely) and capturing the MEDDIC elements that surface naturally. Our companion post on BANT in 2026 covers the triage side in depth.
| BANT | MEDDIC | |
|---|---|---|
| Purpose | Lead triage | Deal management |
| Stage | First touch, SDR | Discovery onward, AE |
| Elements | 4 | 6 |
| Output | Qualify in or out | Deal health score |
| Best for | Volume, simpler deals | Complex, multi stakeholder |
| Weakness | Misses how decisions get made | Too heavy for a first call |
MEDDIC vs MEDDPICC
MEDDPICC adds two letters: Paper Process (procurement, legal, security review, contracting) and a second C for Competition (who else is being evaluated, including doing nothing). Both matter in enterprise deals where a signed contract can take months after a verbal yes.
For SDRs, neither is a cold call question. If a prospect volunteers "we're looking at two other vendors" or "anything over fifty grand goes to procurement", capture it and hand it over. Do not ask.
For AEs selling into Australian enterprise and government, MEDDPICC is usually the better fit because paper process is where Australian deals stall: security questionnaires, procurement panels, legal review, and in government, probity requirements.
The MEDDIC handover: what every booked meeting should include
The most common failure between SDR and AE is a calendar invite with a company name and nothing else. The AE walks in cold, re asks the questions the SDR already asked, and the prospect wonders why they agreed to this.
Every meeting an SDR books should carry a short MEDDIC snapshot in the CRM or the invite notes.
Confirmed. What the prospect actually said. Pain, in their words. Who holds the budget if stated. Timing if stated.
Inferred. What the SDR believes based on the conversation but did not confirm. Likely economic buyer. Likely champion.
Unknown. What the AE needs to find out. Metrics, decision criteria, decision process, competition.
Suggested opening. One line the AE can use to pick up where the call left off. "You mentioned the team is losing roughly two days a week on manual reconciliation. I'd like to start there."
Programs that hand over a snapshot like this consistently land in the 40 to 60 percent meeting to opportunity range we publish for well run agency programs (6). Programs that hand over a name and a time see materially less, because the first ten minutes of the meeting are wasted re qualifying.
Using MEDDIC to define "qualified" with an agency
If you outsource SDR, MEDDIC gives you a precise way to define what a qualified meeting means, which is the single most important line in the contract. A workable definition for complex B2B: the contact is the economic buyer or a confirmed influencer with access to them, the company fits the ICP, a specific pain relevant to your product was confirmed on the call, and a timing signal or active initiative exists. Anything less is a conversation, not a qualified meeting. Our post on how an outbound agency should define a qualified meeting goes into contract language.
Running MEDDIC without sounding like a form
Three rules from our call reviews.
Ask about their world, not your checklist. "How does that get decided here?" surfaces decision process. "Who would need to sign off?" surfaces economic buyer. Neither sounds like a framework.
Let pain lead. Every MEDDIC element flows from pain. Once a prospect has told you what hurts, the questions about who owns it and when it needs fixing feel natural.
Stop when you have enough. The goal of a cold call is a meeting the AE can win, not a completed MEDDIC. Two confirmed elements and a booked meeting beats five half confirmed elements and a prospect who has stopped answering.
How Nousu uses MEDDIC
Nousu Collective trains its Australian SDR team to qualify on Pain and Economic Buyer, flag Champion candidates, capture Metrics and Process signals when volunteered, and hand every booked meeting to the client's AE with a confirmed, inferred and unknown snapshot. We agree the qualified meeting definition with each client before the campaign starts and report against it weekly. See our outsourced SDR service and our discovery call question set for the AE side.
The bottom line
MEDDIC is the best tool available for making sure a meeting is real, but it is an AE's framework. SDRs should use it to know what a qualified meeting must contain, confirm Pain and Economic Buyer on the call, flag Champions, and hand over a clean snapshot. Use BANT logic to decide whether to book. Use MEDDIC to run the deal. Do not try to complete either on a cold call.
Want to see how we qualify and hand over meetings for a client in your sector? Book a 15 minute call.
Frequently asked questions
What does MEDDIC stand for? Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain and Champion. It is a six part qualification framework for complex B2B sales, created at PTC in the 1990s.
What is the difference between MEDDIC and BANT? BANT (Budget, Authority, Need, Timeline) is a fast lead triage filter used at the SDR stage. MEDDIC is a deal management framework used by AEs across a sales cycle. Most teams use BANT to decide whether to book a meeting and MEDDIC to manage the deal afterwards.
What is the difference between MEDDIC and MEDDPICC? MEDDPICC adds Paper Process (procurement, legal, contracting) and Competition to MEDDIC. It suits enterprise deals where contracting takes months, which is common in Australian enterprise and government sales.
Can SDRs use MEDDIC on a cold call? Partially. An SDR can realistically confirm Identify Pain, get a read on the Economic Buyer and flag a potential Champion. Metrics, Decision Criteria and Decision Process belong to the AE's discovery meeting.
Who invented MEDDIC? The acronym was coined by Dick Dunkel at PTC in 1996, working under sales leader John McMahon and alongside Jack Napoli on the company's internal sales training team.
What MEDDIC questions should an SDR ask on a cold call? Two or three at most, focused on pain ("how are you handling this today, where does it break, what does it cost you") and on the economic buyer ("if this turned into something, who else would need to be involved"). Metrics are captured when volunteered, not requested. Criteria and competition wait for the AE.
How should MEDDIC be captured in the CRM at the SDR stage? Six fields on the meeting record, each marked confirmed, inferred or unknown: pain, economic buyer, champion candidate, metrics, decision process, criteria and competition. Report the share of meetings with pain and economic buyer confirmed; those two predict opportunity conversion.
Sources and references
- MEDDICC. Who Created MEDDIC?.
- MEDDPICC.net. MEDDPICC Definition. (PTC history: founded 1988, Boston, billion dollar revenue in ten years, forty consecutive quarters of growth.).
- Pipedrive. BANT Meaning: How to Use BANT in 2026.
- Flow State Sales. The History of MEDDIC: Interview With Dick Dunkel.
- Nousu Collective. BANT vs MEDDIC vs SPIN: Which Sales Qualification Framework to Use and When.
- Nousu Collective. Top 8 Outsourced SDR Providers in Australia 2026. (40 to 60 percent of meetings become opportunities with a good agency.).
Ready to grow your pipeline?
Let's discuss how we can help you book more qualified meetings.
Book a Call with Our Outbound Team