CRM Stage-to-MEDDIC Field Mapping Template
A blueprint for mapping MEDDIC fields onto your CRM's stage gates, complete with field names and validation rules, so the methodology is enforced by the system instead of relied on from memory.
What's inside
- A 6-stage pipeline model with the MEDDIC gate required to advance out of each stage
- Suggested CRM field names and data types for every gate
- A validation rule for each stage that blocks advancement until the gate is genuinely met
- An explicit Paper Process gate at the contract stage covering legal, security, and procurement
- A closed-lost reason taxonomy tied to which MEDDPICC letter actually failed
- Platform-specific implementation notes (Salesforce validation rules, HubSpot required properties, Pipedrive field requirements)
- A phased rollout tip for turning on gates without breaking an existing pipeline overnight
Methodology only sticks when the CRM refuses to let a deal advance without the qualification behind it. Use this table as the blueprint for your stage-gate configuration.
| CRM Stage | Stage Definition | Required Gate to Advance | Suggested CRM Field(s) | Validation Rule |
|---|---|---|---|---|
| 1. Qualify | Initial contact confirmed as a real opportunity | Pain confirmed + Economic Buyer named (even if not yet met) | pain_confirmed (checkbox), economic_buyer_name (text), economic_buyer_title (text) | Cannot advance to Stage 2 unless both fields are populated |
| 2. Discovery | Problem and stakeholders mapped | At least 1 quantified Metric + draft Decision Criteria + Champion identified | metric_1_name, metric_1_value (numeric), decision_criteria (multi-line/multi-select), champion_name, champion_title | metric_1_value must be numeric — "TBD" or blank is rejected |
| 3. Solution / Value Validation | Buyer agrees this is the right solution | Decision Process mapped (steps + dates) + Champion has taken a validated action | decision_process_steps (structured list), close_plan_date (date), champion_action_taken (checkbox + date) | close_plan_date cannot be null and must be on or before the forecast close date |
| 4. Proposal / Negotiation | Commercial terms under discussion | Economic Buyer engaged directly (logged call/meeting) + Decision Criteria finalized and ranked | eb_direct_contact_date (date), decision_criteria_ranked (checkbox) | eb_direct_contact_date is required — deal cannot advance without a logged direct EB touchpoint |
| 5. Contract / Legal (Paper Process) | Commercial terms agreed, paperwork in motion | Legal, security, and procurement status all explicitly set | legal_review_status, security_review_status, procurement_status (each: Not Started / In Progress / Complete / N/A), po_required (checkbox) | Cannot move to Closed Won unless all three status fields are explicitly "Complete" or "N/A" — blank is rejected |
| 6. Closed Won | Signed | All above gates satisfied | close_reason (auto-populated from methodology data) | — |
Closed-Lost reason taxonomy
Tag every loss to the MEDDPICC letter that actually failed — this is what makes win/loss analysis useful instead of just a list of "lost to competitor."
| Reason Code | Meaning |
|---|---|
Lost-NoEB | Never got real access to the economic buyer |
Lost-NoMetrics | Could never get buyer to quantify the problem |
Lost-NoBudget | Decision Process/budget never materialized |
Lost-PaperProcess | Died in legal, security, or procurement after verbal agreement |
Lost-Competition | Lost to a named competitive alternative |
Lost-NoPain | Never confirmed a real, budgeted pain |
Lost-ChampionLeft | Champion left the company or changed roles |
Lost-NoDecision | Buyer chose to do nothing / status quo |
Platform implementation notes
- Salesforce: build these as Validation Rules on the Opportunity object, keyed to
StageName, usingISPICKVAL/ISBLANKchecks against the fields above. - HubSpot: set the MEDDIC fields as required Deal properties per pipeline stage under Deal Stage settings; HubSpot will block manual stage moves until required properties are filled.
- Pipedrive: use custom fields with "Required to progress" enabled per stage in Pipeline settings.
Rollout tip
Don't turn on all six stage gates at once — reps will route around a system that suddenly blocks everything. Turn on Stage 1's gate first, run it for two weeks, fix the inevitable data-hygiene issues, then add the next stage's gate. By the time you reach the Paper Process gate at Stage 5, the team will already be in the habit of filling in the earlier fields as they go.
How to use it
Hand this table to whoever administers your CRM as the direct build spec, roll the validation rules out one stage at a time starting with Stage 1, and require the Closed-Lost reason taxonomy on every lost deal so win/loss reporting ties back to a specific MEDDPICC letter.