lead-qualification-meddic
Qualify enterprise opportunities using MEDDIC/MEDDPICC framework for complex B2B sales cycles
What this skill does
# Lead Qualification: MEDDIC > Qualify complex enterprise opportunities using the MEDDIC framework to ensure deal viability and improve forecast accuracy. ## When to Use This Skill - Enterprise deal qualification - Complex sales cycles (60+ days) - Multiple stakeholder deals - High ACV opportunities ($50K+) - Improving forecast accuracy ## Methodology Foundation Based on **PTC's MEDDIC methodology** (developed by Dick Dunkel), extended to MEDDPICC: - **M**etrics - Quantified value - **E**conomic Buyer - Decision authority - **D**ecision Criteria - How they'll choose - **D**ecision Process - How they'll buy - **I**dentify Pain - Business problem - **C**hampion - Internal advocate - **C**ompetition - Competitive landscape - **P**aper Process - Legal/procurement ## What Claude Does vs What You Decide | Claude Does | You Decide | |-------------|------------| | Structures MEDDIC questions | Deal prioritization | | Scores each component | Resource investment | | Identifies gaps | Coaching focus | | Creates deal summaries | Forecast commit | | Suggests next actions | Win strategy | ## Instructions ### Step 1: Define MEDDIC Components | Component | Definition | Key Question | |-----------|------------|--------------| | **Metrics** | Quantified outcomes | "What numbers will improve?" | | **Economic Buyer** | Person with budget authority | "Who can say yes and write the check?" | | **Decision Criteria** | How they evaluate | "What criteria will you use to decide?" | | **Decision Process** | Steps to purchase | "What happens between now and signed contract?" | | **Identify Pain** | Business problem | "What happens if this doesn't get solved?" | | **Champion** | Internal advocate | "Who's fighting for this internally?" | | **Competition** | Alternatives | "What else are you considering?" | | **Paper Process** | Procurement/legal | "What's involved in getting contracts signed?" | ### Step 2: Discovery Questions by Component **Metrics:** - "If this project succeeds, what numbers will change?" - "How will you measure ROI?" - "What's the cost of the current problem?" - "What KPIs are you trying to impact?" **Economic Buyer:** - "Who ultimately approves the budget for this?" - "Have you worked with them on similar initiatives?" - "Can I meet them before we finalize a proposal?" **Decision Criteria:** - "What are the must-haves vs nice-to-haves?" - "How will you compare solutions?" - "Who developed these criteria?" - "How important is [your differentiator]?" **Decision Process:** - "Walk me through the steps from here to signed contract." - "Who else needs to evaluate this?" - "Are there approval committees or board reviews?" - "What could delay or derail this process?" **Identify Pain:** - "What's driving this initiative now?" - "What happens if you do nothing?" - "How is this affecting your team/business/customers?" - "Have you tried to solve this before?" **Champion:** - "Who's the biggest advocate for this project?" - "What happens to them if this succeeds/fails?" - "Can they get us access to [stakeholder]?" - "How much influence do they have?" **Competition:** - "What alternatives are you considering?" - "How far along are you with other vendors?" - "What do you like about what you've seen?" - "How does that compare to what we've shown you?" **Paper Process:** - "What's your typical procurement timeline?" - "Are there security or legal reviews required?" - "Have you worked with vendors like us before?" - "What can we do to expedite the process?" ### Step 3: Score Each Component | Score | Criteria | |-------|----------| | ๐ข 3 | Confirmed, documented, verified | | ๐ก 2 | Identified but not confirmed | | ๐ 1 | Weak or incomplete | | ๐ด 0 | Unknown or missing | **Deal Qualification Levels:** | Score | Status | Action | |-------|--------|--------| | 21-24 | Strong | Commit to forecast | | 16-20 | Developing | Address gaps | | 11-15 | Early | More discovery needed | | <11 | Weak | Qualify out or restart | ## Examples ### Example 1: Full MEDDIC Analysis **Output:** ``` ## MEDDIC Deal Scorecard: GlobalTech ($250K) ### Deal Overview - **Account:** GlobalTech Inc - **Value:** $250,000 ARR - **Stage:** Proposal - **Close Date:** March 15 - **Sales Cycle:** 90 days (Day 60) --- ### MEDDIC Score: 18/24 ๐ก Developing | Component | Score | Status | |-----------|-------|--------| | Metrics | 3/3 | ๐ข | | Economic Buyer | 2/3 | ๐ก | | Decision Criteria | 3/3 | ๐ข | | Decision Process | 2/3 | ๐ก | | Identify Pain | 3/3 | ๐ข | | Champion | 3/3 | ๐ข | | Competition | 1/3 | ๐ | | Paper Process | 1/3 | ๐ | --- ### Component Details #### Metrics: 3/3 ๐ข **Status:** Strong - Quantified and agreed **Evidence:** - ROI target: 3x in Year 1 - Specific KPIs: Reduce CAC by 20%, increase pipeline by 40% - CFO signed off on business case - Baseline metrics documented **Quote:** "If we can hit these numbers, this pays for itself in 6 months." --- #### Economic Buyer: 2/3 ๐ก **Status:** Identified but not met **Evidence:** - EB: CFO Jennifer Walsh - Champion confirmed she has budget authority - Haven't had direct meeting yet - Email correspondence only **Gap:** Need face-to-face with CFO before proposal review **Action:** Request 15-min executive alignment call --- #### Decision Criteria: 3/3 ๐ข **Status:** Strong - Criteria aligned with our strengths **Evidence:** - Formal RFP with weighted criteria - Our top differentiators match their priorities: - Integration depth (30% weight) - โ Our strength - Time to value (25% weight) - โ Our strength - Price (20% weight) - โ ๏ธ Neutral - Support (15% weight) - โ Our strength - References (10% weight) - โ Have 3 ready **Quote:** "Integration is non-negotiable for us." --- #### Decision Process: 2/3 ๐ก **Status:** Mapped but timeline fuzzy **Evidence:** - Step 1: Technical evaluation โ Complete - Step 2: Business review โ Complete - Step 3: Proposal review โณ This week - Step 4: CFO approval โณ Pending - Step 5: Legal/Procurement โณ Unknown timeline - Step 6: Contract signed โณ Target March 15 **Gap:** Steps 4-6 timeline not confirmed **Action:** Get specific dates for approval meeting and legal review --- #### Identify Pain: 3/3 ๐ข **Status:** Strong - Urgent, quantified pain **Evidence:** - Current problem: 40% of leads fall through cracks - Business impact: $2M estimated lost revenue - Trigger: Missed Q3 target, board pressure - Previous attempts: Tried 2 solutions, both failed **Quote:** "This is keeping our CEO up at night." --- #### Champion: 3/3 ๐ข **Status:** Strong - Active, influential champion **Champion Profile:** - Name: Marcus Chen, VP Revenue Operations - Motivation: His initiative, career impact - Influence: Direct report to CFO - Actions taken: - Built internal business case - Scheduled all meetings - Defended us vs. competitor - Sharing our content internally **Quote:** "I'm putting my reputation on this." --- #### Competition: 1/3 ๐ **Status:** Weak - Incomplete intel **Evidence:** - Know they evaluated CompetitorX - Don't know current status - Champion said "we've narrowed to two" - No details on competitor proposal **Gap:** Critical blind spot **Action:** - Ask champion directly about competitor status - Understand their proposal/pricing - Prepare competitive battle card response --- #### Paper Process: 1/3 ๐ **Status:** Weak - Unknown **Evidence:** - They have a procurement team - Security review likely required - No timeline documented - Haven't met procurement **Gap:** Could add 2-4 weeks we haven't planned for **Action:** - Ask champion about typical procurement timeline - Offer to start security questionnaire early - Get intro to procurement contact --- ### Gap Summary | Gap | Priority | Owner | Action | Due | |-----|----------|-------|--------|-----| | Meet CFO | High | AE | Request exec call | Day 62 | | Competition intel | High | AE | Discovery with champion | Day 63 | | Paper process | Medium | SE | Start security review | Day 65 | | Dec
Related in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work โ this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.