MEDDIC is less a selling style than a disqualifier. Each letter is a question the rep must answer with a real name, number, or document before the deal is allowed to move forward in the pipeline.
MEDDIC is a six-part sales qualification framework used in complex B2B deals: Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, and Champion. It was built at PTC in the mid-1990s to lift win rates on seven-figure enterprise sales. Reps use it as a checklist on every opportunity so forecasts are grounded in evidence instead of hope, and deals without a filled-in MEDDIC do not count as committed pipeline.
The six letters of MEDDIC, what each one actually asks, and the single rule that separates a filled-in MEDDIC from a wishful one.
Dick Dunkel and Jack Napoli developed MEDDIC inside PTC (Parametric Technology Corporation) in the mid-1990s to qualify large CAD and PLM deals. PTC quadrupled revenue over the five years that followed, and MEDDIC became the default qualification language in enterprise software sales. Napoli later took it to companies like BMC, EMC, and MongoDB, where it kept producing the same outcome.
Metrics (the quantified business impact), Economic buyer (the person who signs), Decision criteria (how they will choose), Decision process (how the deal gets approved), Identify pain (the problem being solved), and Champion (the internal advocate who sells for you). Six boxes. Each one needs a specific, verifiable answer, not a guess.
MEDDIC does not help reps sell harder. It helps them walk away faster. A deal with four of six letters filled is a deal where thirty-three percent of the information is missing, and the forecast reflects that. The discipline is uncomfortable because it removes deals from the board, which is exactly why forecasts built on it are more accurate.
MEDDIC is designed for complex B2B sales with multiple stakeholders, six-figure or seven-figure contracts, legal review, and procurement cycles. On transactional SMB deals the overhead is too high and the framework starts to feel like paperwork. Match the methodology to the deal shape or the team will quietly abandon it.
A real MEDDIC rollout is six fields on the opportunity record (one per letter) plus a stage rule that blocks advancement if any field is empty. Managers inspect the fields in deal reviews. Leadership rolls them into forecast categories. If the letters are not fields, MEDDIC is a slide, not a method.
MEDDPICC is the modern expansion: it inserts Paper process (the legal and procurement path) and Competition (who else is in the deal) between the original letters. MEDDICC with a single extra C adds only Competition. The acronyms grew because the two gaps they fix are where enterprise deals most commonly stall at the end.
The temptation with MEDDIC is to treat the letters as topics and check the box the moment the rep can say something about each one. The whole point of the framework is the opposite. Each letter is a specific question with a specific type of answer: a name, a number, a date, a document, or a signed email. If the answer is a shrug or a theory, the letter is not filled in, and the forecast should reflect that.
Not "they want to grow." The specific number the buyer will measure the project against: cut procurement cycle time from eighteen days to five, lift support deflection by thirty percent, recover eighty hours a month per rep. If the metric is not a number the buyer agrees to in writing, the deal has no success criterion and renewal is already at risk.
The one human with discretionary authority over the budget. Not the champion, not the IT director, not the person running the evaluation. The economic buyer is the person who can override everyone else and say yes. If the rep has never met them, has not confirmed the signing threshold, or is relying on someone else to carry the pitch, the letter is empty.
The explicit list the buyer will compare vendors against: integrations required, security certifications, implementation timeline, reference customers in the industry, total cost of ownership. The rep should have the list in writing, know which criteria are table stakes versus differentiators, and have already shaped at least one criterion that favors their product.
The step-by-step path from "we like it" to signed contract: security review, legal review, procurement, finance sign-off, board approval, executive sponsor sign-off. Who touches it, in what order, how long each step takes, and where it typically stalls. A rep who cannot draw the process diagram is forecasting a close date they cannot defend.
The business pain severe enough that the buyer will spend money and political capital to fix it. Pain is not a feature wishlist, it is a cost the company is paying today: churn eating ten percent of ARR, deals leaking at proposal stage, finance closing books five days late. If no one at the company is currently losing sleep over the problem, the project will lose funding when the budget tightens.
Someone inside the account who has power, has access to the economic buyer, benefits personally from the project succeeding, and will advocate when the rep is not in the room. Test the champion with real asks: can they introduce you to the EB, can they share the internal buying process document, can they tell you why the last vendor was rejected. If every ask hits a wall, you have a coach, not a champion.
BANT (Budget, Authority, Need, Timing) was built at IBM in the 1960s for a world where one person signed one contract on one timeline. It is still useful for simple deals. For modern enterprise sales, the gaps between BANT and MEDDIC are the gaps where seven-figure deals most often die. The two frameworks overlap in roughly the places you would expect, but the differences matter.
BANT asks who has authority. MEDDIC splits that into the economic buyer, the champion, the decision criteria, and the decision process. In a modern SaaS deal with legal review, security review, procurement, and an executive sponsor, "authority" is five people and a sign-off chain, not a single contact.
BANT asks if the buyer has a need. MEDDIC asks if the buyer is actively paying a cost big enough to justify the project. A need can be put off indefinitely. A pain that is costing the business money has a self-destruct timer attached, which is why MEDDIC deals have a close date and BANT deals have a close month.
BANT confirms a budget exists. MEDDIC asks what the buyer will measure the project against. A budget tells you if the deal can be signed. A metric tells you if the project will be renewed. The difference is why MEDDIC-trained teams win expansions and BANT-trained teams fight renewal cliffs.
BANT asks when the deal will close. MEDDIC asks how the deal will close, step by step, with names on each step. A date is a hope. A process is a plan. Forecasts built on process close in the quarter they promise. Forecasts built on dates slip, which is why MEDDIC teams have tighter forecast accuracy than BANT teams by meaningful margins.
BANT does not mention a champion. MEDDIC makes the champion a required field. The reason is simple: in enterprise sales, the rep is not in the room for most of the buying conversation. The champion is. Without a tested champion, every internal meeting is a gamble on whether the right argument gets made.
BANT still works for simple one-signer deals with short cycles. MEDDIC pays for its overhead on deals above roughly $25K ACV, with three or more stakeholders, a security review, and a procurement step. Mixing the two on one team is fine; forcing MEDDIC on $500 transactions is not.
MEDDIC on a wall poster is decorative. MEDDIC on an opportunity record is a method. The rollout that actually changes forecast accuracy is boring and specific: six custom fields, a stage gate that blocks advancement when any field is empty, a dashboard that counts filled letters per rep, and a deal review where the manager asks for the evidence behind each letter instead of accepting a yes.
Add six fields to the opportunity record: Metric, Economic buyer, Decision criteria, Decision process, Identified pain, Champion. Economic buyer and Champion should be contact lookups so you can confirm the person exists in the system. The others are long-text so reps capture the real answer, not a yes-or-no that teaches them to game the field.
Tie each letter to a pipeline stage. By Qualified, Metric and Identified pain are required. By Proposal, Economic buyer and Champion are required. By Negotiation, Decision criteria and Decision process are required. Advancement is blocked until the field is filled, so the pipeline board tells the truth about what is actually qualified.
The weekly deal review question changes from "where is this deal" to "show me the champion test, the written metric, the process map, the EB email." The rep learns quickly that unsupported MEDDIC fields do not survive the review, and the fields fill with real content instead of placeholder text.
A deal with six letters filled is a different forecast call than a deal with three. Build a report that counts filled MEDDIC fields per opportunity and roll it into forecast categories (Commit requires six, Best Case requires four, Pipeline allows two). The forecast conversation moves from gut feel to evidence in one quarter.
A dashboard that shows which letters each rep fills consistently and which they skip surfaces coaching targets. Reps who never fill Economic buyer need help getting to power. Reps who never fill Decision process need help running mutual action plans. The pattern is visible in the data instead of waiting for a lost deal.
On every closed deal (won or lost), run a review that compares the MEDDIC fields at close to the outcome. Lost deals almost always had missing or weak letters. Won deals almost always had full ones. The pattern becomes a trainable rulebook for the next ramping rep, which is the real multiplier of a MEDDIC rollout.
Strkr lets you add required MEDDIC fields per stage, block advancement when they are empty, and roll filled-letter counts into forecast categories. Start free. See the pipeline the way a MEDDIC-trained manager wants to see it.
MEDDIC stands for Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, and Champion. The six letters are the six questions a sales rep is expected to answer about every active opportunity before the deal is considered qualified. Each letter is a required field, not a topic to discuss.
MEDDIC was created in the mid-1990s by Dick Dunkel and Jack Napoli at PTC (Parametric Technology Corporation), a CAD and PLM software vendor. The framework was credited with helping PTC roughly quadruple revenue over five years. Napoli later taught it at BMC, EMC, MongoDB, and other enterprise software companies, and now runs the MEDDIC Academy that formalizes the training.
MEDDIC is the original six-letter framework. MEDDICC adds a seventh letter for Competition. MEDDPICC adds both Paper process (the procurement, legal, and signature path) and Competition, making it eight letters. The extensions exist because enterprise deals in the 2010s and 2020s increasingly stall on procurement cycles and multi-vendor evaluations that the original framework did not explicitly cover.
A qualification framework. MEDDIC does not prescribe how to run a discovery call, how to deliver a demo, or how to handle objections. It tells you what information you need to have confirmed about an opportunity before it belongs in your forecast. Most teams pair MEDDIC with a full methodology (Challenger, Sandler, Command of the Sale) that handles the selling behavior MEDDIC does not cover.
MEDDIC fits complex B2B sales with multiple stakeholders, meaningful contract sizes (roughly $25K ACV and above), security or procurement review, and sales cycles of a quarter or longer. On transactional SMB deals the overhead outweighs the value and the team will abandon the fields within a quarter. Match the framework to the deal shape, not the vendor preference.
Confusing a coach with a Champion. A coach gives the rep information. A Champion sells the deal when the rep is not in the room, has power inside the account, and benefits personally from the project succeeding. Teams that mark anyone friendly as the Champion routinely lose deals they thought were qualified, because the "Champion" never actually advocated internally.
BANT (Budget, Authority, Need, Timing) was built in the 1960s for simpler, single-signer deals. MEDDIC was built for modern enterprise deals with buying committees, security reviews, and procurement. The key differences: MEDDIC separates the economic buyer from the champion, asks for a quantified metric instead of a budget confirmation, and maps the decision process instead of just the close date. BANT still works for small, fast deals.
No. MEDDIC is six custom fields on the opportunity record, a stage rule that blocks advancement when fields are empty, a dashboard that counts filled letters, and a deal review habit that asks for evidence. Any modern CRM can be configured this way in an afternoon. The hard part is the discipline, not the tooling.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
