MEDDPICC Qualification

MEDDPICC qualifies and progresses enterprise deals on 8 dimensions: Metrics, Economic Buyer, Decision Criteria, Decision Process, Paper Process, Identify Pain, Champion, and Competition. It's the standard framework for complex B2B sales with multiple stakeholders, long cycles, and high ACV. Where BANT answers "should we pursue this?" MEDDPICC answers "can we win this, and what do we need to do to close it?"

The principle: MEDDPICC is not a one-time qualification checklist. It's a living deal assessment that's updated at every stage. A deal that scores well on MEDDPICC in discovery but deteriorates by proposal is a deal in trouble. Score early. Score often. Update at every interaction.

The 8 Dimensions

M - Metrics

The quantifiable business outcomes the prospect needs to achieve.

How to uncover:

• "If this works, what does success look like in 6 months? What numbers would change?"
• "What are the KPIs your team is measured on? Which ones are you missing right now?"
• "What would you need to show your board/VP to justify this investment?"

Metrics rules:

• If the prospect can't name a metric, they can't build a business case. Help them quantify: "Most teams at your stage measure [X]. Is that on your radar?"
• The metric must be theirs, not yours. "We'll improve your reply rates" is your claim. "We need reply rates above 8% to hit pipeline targets" is their metric
• Metrics anchor the entire deal. Every proposal, ROI slide, and closing argument references these numbers. Get them early

E - Economic Buyer

The person with final budget authority. Can say yes when everyone else says no. Can kill the deal when everyone says yes.

How to uncover:

• "Who would ultimately approve the budget for a purchase like this?"
• "When [champion] recommends a tool, who gives the final go-ahead?"
• "Has your team ever bought a tool in this price range? Walk me through how that decision was made"

Economic buyer rules:

• You must engage the EB directly before the proposal stage. An EB who hasn't heard the business case from you will rely on the champion's translation, which is never as strong
• The EB is not always the most senior person. A CRO may delegate tool purchases to the VP Sales. The VP is the EB for this deal, even though the CRO outranks them
• If the EB won't take a meeting, the deal is at risk. It means either the priority is low, the champion isn't strong enough to get you access, or the EB has already decided against

D - Decision Criteria

The specific criteria the prospect will use to choose between vendors.

How to uncover:

• "What are the top 3 things that would make or break this decision for your team?"
• "If you're evaluating multiple options, what will you compare them on?"
• "Are there any must-haves vs nice-to-haves you've already defined?"

Decision criteria rules:

• If you don't know the criteria, you can't win on the criteria. The demo, the proposal, and the negotiation must map to their stated criteria, not your feature list
• Shape the criteria. If a criterion is missing that you uniquely satisfy, introduce it: "Most teams at your stage also evaluate [criterion]. Is that on your list?"
• Document the criteria in CRM. When the deal gets to proposal, reference each criterion and show how you meet it. This is the structure of the winning proposal
• Watch for criteria shifts. A competitor may introduce new criteria mid-evaluation to tilt the playing field. If criteria change after evaluation starts, investigate who changed them and why

D - Decision Process

The steps the prospect's organization goes through to approve a purchase.

How to uncover:

• "Walk me through how your company has bought a SaaS tool in the $30-50K range before. What were the steps?"
• "Between 'yes, we want this' and 'contract signed,' what happens?"
• "Is there a security review or legal review involved? How long does that typically take?"

Decision process rules:

• Map every step with a timeline. "Technical review: 2 weeks. Business case: 1 week. Procurement: 3 weeks. Legal: 2 weeks." Total: 8 weeks. If the prospect says they want to close in 4 weeks, the process says 8. Trust the process, not the hope
• The decision process tells you when to do what. If security review is step 3, send the SOC 2 report at step 2, not step 5. Anticipate each step and have materials ready before they ask
• Processes change. A new stakeholder can add a step. A budget freeze can pause everything. Update the process map after every interaction

P - Paper Process

The procurement, legal, and contract mechanics that happen after the business decision is made.

How to uncover:

• "Once you decide to go forward, what's the process for getting the contract signed?"
• "Does your company have a standard procurement process or security review for SaaS tools?"
• "Who on your side handles contracts? Is there a legal team or does your exec sign directly?"

Paper process rules:

• Paper process is the most underestimated deal killer. 80% of "slipped" deals slip because of procurement, not because the business decision wasn't made
• Get paper process details before sending the proposal. If their procurement takes 4 weeks and you need to close by end of quarter, start the paper process at the same time as the evaluation, not after
• Pre-fill what you can. Security questionnaire already filled out. MSA/DPA ready to send. SOC 2 report attached. Every document you prepare in advance saves 1-2 weeks on the paper process
• Know the signing authority. If contracts above $50K need board approval and your deal is $60K, that board meeting schedule is your real timeline

I - Identify Pain

The specific, acknowledged, quantified pain the prospect is experiencing.

Identify Pain rules:

• Pain must be acknowledged BY the prospect, not inferred by you. "I think they have a pipeline problem" is your hypothesis. "Our pipeline is $500K short of target this quarter" is their pain
• Quantified pain builds its own business case. $150K in wasted SDR time makes a $40K tool purchase obvious. Unquantified "it's inefficient" doesn't move budget
• Pain that affects the economic buyer's KPIs gets funded. SDR frustration is pain. But "pipeline is 40% below target and the board is asking questions" is the EB's pain. Connect the team's pain to the EB's pain
• No pain = no deal. If discovery can't surface acknowledged pain, disqualify. A prospect without pain will evaluate forever and never buy

C - Champion

An internal advocate who has power, influence, and a personal stake in your success.

Champion vs coach:

Champion rules:

• A champion without power is a coach. A champion without willingness to sell internally is a fan. You need both: power AND willingness
• Test the champion. Ask them to do something: introduce you to the EB, share a document internally, schedule a technical review. If they do it, they're a champion. If they deflect, they're a coach
• Arm the champion. Give them the materials they need to sell internally: a one-pager for the EB, a technical overview for IT, an ROI calculator for finance. They can't sell what they can't articulate
• If the champion leaves the company, the deal may die. Multi-thread (per multi-threading-strategy skill) so the deal survives a champion departure

C - Competition

Who else the prospect is evaluating, and how you stack up.

How to uncover:

• "Are you looking at any other tools alongside us? I ask because it helps me tailor what I show you"
• "What other approaches are you considering? Including doing nothing or building internally?"
• "What would a competitor need to offer to beat us in your evaluation?"

Competition rules:

• The most dangerous competitor is "do nothing." 40-60% of qualified deals are lost to no decision, not to a competitor. Always treat the status quo as a competitor
• Know the prospect's perception of the competitor, not just your perception. "They think [competitor] is easier to implement" matters more than "we have more features"
• Don't trash competitors. Acknowledge their strengths. Then position your differentiation: "[Competitor] is strong on [X]. Where we're different is [Y], which matters because [prospect's criterion]"
• If the prospect won't tell you who they're evaluating, they're hiding information. This is a yellow flag for champion strength and trust level

MEDDPICC Scoring

The deal scorecard

Score each dimension 0-3. Total ≥ 16/24 for a healthy deal. Score per dimension in CRM.

Scoring thresholds by deal stage

Scoring rules

• Score after every interaction, not just at pipeline reviews. A discovery call should update 3-4 dimensions. A demo should update Decision Criteria and Competition. Score continuously
• A deal advancing stages but declining in MEDDPICC score is in trouble. The deal moved from Evaluation to Proposal but the champion stopped responding and the EB hasn't engaged. The stage says progress. The score says risk
• MEDDPICC score should inform forecast category. Commit = MEDDPICC ≥ 20. Best Case = 16-19. Pipeline = 12-15. Below 12 = not forecastable

MEDDPICC in Deal Reviews

The 5-minute deal review format

Use MEDDPICC to structure weekly deal reviews. Each deal gets 5 minutes.

Rep presents:
1. "The pain is [I]: [specific, quantified pain]"
2. "The metrics they care about [M]: [specific KPIs]"
3. "The champion is [C]: [name, title, what they've done for us]"
4. "The economic buyer is [E]: [name, title, engagement status]"
5. "The competition is [C]: [who else, our positioning]"
6. "The decision criteria are [D]: [top 3 criteria]"
7. "The decision process is [D]: [steps and timeline]"
8. "The paper process is [P]: [procurement, legal, security status]"
9. "The biggest risk right now is: [which dimension is weakest]"
10. "My next action to de-risk: [specific action]"

Manager challenges:
- "Have you met the EB?" (if E < 2)
- "What has the champion done for us this week?" (if C is claimed but unproven)
- "What happens if you lose to [competitor]?" (if Competition is under-explored)

Deal review rules

• Lead with the weakest dimension. The purpose of the review is to identify risk and plan de-risking actions. Starting with what's strong wastes time. Start with what's weak
• "I don't know" is a valid answer that must be followed by an action. Not knowing the decision process is fine at Discovery. It's not fine at Proposal. The action should close the gap before the next review
• The manager's job is to challenge, not to accept. "The champion loves us" from the rep should be met with "What specific action has the champion taken this week?" Champions are proven by actions, not by sentiment
• Every deal review ends with one specific action. Not "keep working it." One action: "Meet the EB by Friday." "Get the security questionnaire to IT by Thursday." "Ask the champion to schedule an internal review." Specific. Time-bound

CRM Implementation

MEDDPICC fields on the Opportunity

When to Use MEDDPICC vs BANT

Many teams use both: BANT for SDR-level initial qualification (should this deal exist?), then MEDDPICC for AE-level deal progression (can we win it?).

Measurement

Anti-Pattern Check

• MEDDPICC scored once at discovery and never updated. MEDDPICC is a living scorecard. Update it after every call, every email exchange, every stakeholder meeting. A score from 6 weeks ago is stale
• Champion scored as 3 but the champion hasn't done anything. A champion is proven by actions. Did they introduce you to the EB? Schedule an internal meeting? Share your materials? "They really like us" is sentiment, not action. Score on actions, not feelings
• Paper process not explored until after the proposal. Procurement takes 3-4 weeks at most enterprise companies. If you don't know the paper process until after the business decision, you've added a month of invisible timeline. Explore by Evaluation stage
• MEDDPICC used for $10K SMB deals. Overkill. MEDDPICC is for complex, multi-stakeholder deals. A $10K deal with one decision-maker doesn't need 8 dimensions. Use BANT for simple deals
• All 8 dimensions scored 1 ("partially uncovered"). No deal should advance past Evaluation with nothing validated. At least Pain and Champion should be at 2 by Evaluation. At least 4 dimensions at 2 by Proposal
• Competition scored 0 throughout the deal. Every deal has competition. Even if no named competitor is in the evaluation, the status quo ("do nothing") is always a competitor. Score Competition on status quo awareness if no vendor competition exists
• Manager accepts the rep's MEDDPICC scores without challenging. The scores are self-reported. The manager's job is to test them: "You say the champion is a 3. What did they do for us this week?" Trust but verify in every deal review
• MEDDPICC fields exist in CRM but nobody fills them in. The fields are empty on 60% of open deals. Without consistent scoring, MEDDPICC is an idea, not a process. Make MEDDPICC scoring a required activity at each stage advancement