MEDDIC: The Qualification Framework for Complex B2B Deals

MEDDIC is a checklist for working out whether a complex business deal is real. It takes the six things that most reliably determine whether an enterprise purchase closes, gives each one a letter, and asks a salesperson to be able to answer all six with evidence from the buyer rather than assumption. It originated in enterprise software sales in the 1990s and spread because it addresses the specific way large deals fail: not through a dramatic rejection, but through a quiet discovery late in the cycle that nobody could approve the spend, that the evaluation criteria were written around a competitor, or that a purchase order takes six weeks nobody budgeted for.

Metrics

The quantified outcome the buyer expects, in their own numbers. Not the vendor claim, but the customer's own baseline and the improvement they would consider worth the money.

Economic buyer

The individual who can release the budget. This is frequently not the person running the evaluation, and a deal where the seller has never spoken to this person is exposed regardless of how well the evaluation is going.

Decision criteria

The standards the purchase will be judged against, technical, commercial and political. Some are written in a requirements document, and the ones that actually decide the outcome frequently are not.

Decision process

The sequence of steps between agreement and signature: who reviews, who approves, what security or legal checks apply, and how long each takes.

Identify pain

The business problem serious enough that doing nothing has a cost. A deal built on a nice-to-have improvement rarely survives a budget review.

Champion

Someone inside the account who wants the outcome, has internal credibility, and will argue for it when the seller is not in the room. The third condition is the one that distinguishes a champion from a friendly contact.

A worked scoring example (illustrative)

Score each element from zero to three, where zero is unknown, one is assumed by the seller, two is stated by the buyer, and three is stated and verified independently. A deal might score: metrics 2, economic buyer 1, decision criteria 3, decision process 0, pain 3, champion 2. That totals 11 out of 18. The total matters less than the shape. This deal has a clear problem and clear criteria, but the seller has assumed who controls the budget and knows nothing about how a purchase actually gets approved. Those two zeros and ones are where the next two conversations should go, and until they move, forecasting the deal for this quarter is guesswork.

The framework drives two decisions. The first is where a salesperson spends the next hour. A pipeline of twenty opportunities contains a handful that are genuinely advancing and a long tail that are pleasant conversations, and the qualification gaps are the fastest way to tell them apart. The second is what goes into the forecast. A deal with unknown budget authority and an unmapped approval path is not a commit, however enthusiastic the user contact sounds.

It also changes management conversations. Reviewing a pipeline by deal value produces a discussion about optimism. Reviewing it by qualification gaps produces a discussion about specific next actions, because every gap implies a person to contact and a question to ask. That is why the framework survives in teams that have abandoned most of their other sales processes.

The form-filling failure

The most common failure is turning it into administration. Fields get completed the evening before a review with reasonable-sounding answers that came from the seller's imagination rather than the buyer's mouth. The framework then produces false confidence, which is worse than no framework at all, because the gaps that would have prompted action are hidden behind a completed form. The fix is to demand a source for every answer and treat unsourced entries as unknown.

The definitional traps

Three confusions recur. A coach is mistaken for a champion: someone who gives you information is valuable but is not the same as someone who will spend their own credibility arguing for you. The economic buyer is confused with the most senior person on the call, who may have delegated the decision entirely. And pain is recorded as a general industry problem rather than a specific cost this organisation is bearing, which is the version that does not survive a finance review. Filling in six fields is easy. Filling them in honestly is the whole exercise.

Treat the score as a diagnostic, not a probability. A deal scoring high across all six elements is well understood, which is not the same as certain to close, and a low score early in a long cycle is entirely normal rather than a reason to abandon the opportunity. What matters is the trend: a deal whose score has not moved across three weeks of activity is one where the conversations are pleasant and nothing is being learned.

Look for lopsided shapes. Strong pain with no economic buyer usually means the seller is talking to a user who cannot buy. Strong criteria with no decision process is the classic pattern behind deals that slip a quarter. Everything strong except competition, in the extended version of the framework, is often a deal where the buyer is comparing you against doing nothing and has not said so.

These four are frequently discussed as alternatives when they operate at different points in the process.

The practical distinction is that a qualification framework judges an opportunity while a questioning method produces the information that gets judged. Teams that adopt one and expect it to do the work of the other usually conclude the framework failed when the mismatch was structural.

Qualification only holds if the answers live somewhere durable. Start with what a CRM is, then look at lead management software, sales automation for follow-up discipline, CRM with a built-in dialer for logged discovery calls, AI CRM for thread summaries before a meeting, and sales use cases for how teams apply this in practice.