How should you design custom fields in Salesforce to enforce MEDDPICC capture without making the AE's job miserable, and which fields are mandatory vs nudge-only?

Question

Pulse RevOps · The Machine · Accepted Answer

## Designing MEDDPICC Custom Fields in Salesforce: Mandatory vs. Nudge-Only

**DIRECT ANSWER:** Gate stage progression with Salesforce validation rules that hard-block advancement unless 4 core MEDDPICC fields are populated — Metrics, Economic Buyer, Identified Pain, and Champion. The remaining four (Decision Criteria, Decision Process, Paper Process, Competition) work better as scored nudges that surface in manager dashboards rather than deal-stopping blockers.

---

### THE DETAIL

If a rep can progress a deal from Qualification to Proposal without completing a single MEDDPICC field, then the methodology is optional — and optional methodologies don't get followed. That's the whole design problem. The fix is a two-tier architecture: **hard gates** at specific stage transitions, **soft nudges** everywhere else.

#### Tier 1 — Hard Gates (Validation Rules = Stage-Exit Blockers)

Use Salesforce validation rules to enforce field completion as exit criteria between each stage — Qualification → Discovery, Discovery → Solution Alignment, Solution Alignment → Proposal, Proposal → Negotiation, and Negotiation → Closed Won.

Map gates to the stage where the intel is *discoverable*, not where it's *needed*:

| Stage Exit | Required Field(s) | Field Type |
|---|---|---|
| Qualification → Discovery | **Identified Pain**, **Metrics** | Long Text (≥50 chars) |
| Discovery → Solution Alignment | **Economic Buyer** (contact lookup) | Lookup (Contact object) |
| Solution Alignment → Proposal | **Champion** (contact lookup) | Lookup (Contact object) |
| Negotiation → Closed Won | **Paper Process** | Long Text (≥50 chars) |

Make key MEDDPICC fields mandatory before a deal can move to late-stage pipeline — e.g., a rep can't move to "Contract Sent" without a completed "Paper Process" field.

**Wire Economic Buyer and Champion as Contact lookups**, not free-text. The AE should tag the contact record directly — that forces them to ensure the contact information actually exists in the system rather than just typing a name.

#### Tier 2 — Nudge-Only Fields (Scored, Visible, Not Blocking)

**Decision Criteria**, **Decision Process**, and **Competition** live as picklist + long-text combos with a Red/Yellow/Green score field per element. Use a single Global Value Set with Red/Yellow/Green values applied across every scored field — this keeps values consistent and means only one place needs updating if the scale changes.

A row of eight picklists on an Opportunity layout doesn't help during a deal review — add a visual layer so that instead of displaying "Red" and "Green" as text, color-coded icons are shown that a manager can read at a glance.

Build dashboards to monitor MEDDPICC compliance for active deals — highlight deals missing Champions or with unqualified Economic Buyers.

#### The Third Layer: Behavioral

Managers must review MEDDPICC fields during deal inspections — not as a compliance check, but as the basis for coaching. Forecast calls should reference identified pain and decision process rather than anecdotal confidence. The qualification data has to influence actual pipeline decisions.

**Native-build alternatives:** **Scratchpad** for rep-side quick updates that sync to SFDC, **iSEEit** or **SalesMethods Plan2Close** for AppExchange-native scoring, **Gong** or **Clari** for AI-assisted field population from call transcripts.

Organizations that master MEDDIC typically see 25–40% improvement in win rates and 30–50% better forecasting accuracy — but only when the system enforces it, not when it's faith-based.

---

```mermaid
flowchart LR
    A[Opportunity Created] --> B{Stage: Qualification}
    B -->|GATE: Pain + Metrics filled| C{Stage: Discovery}
    C -->|GATE: Economic Buyer lookup| D{Stage: Solution Alignment}
    D -->|GATE: Champion lookup| E{Stage: Proposal/Validation}
    E -->|NUDGE: Decision Criteria score
NUDGE: Decision Process score
NUDGE: Competition score| F{Stage: Negotiation}
    F -->|GATE: Paper Process filled| G[Closed Won]
    
    subgraph Nudge Layer
        H[RAG Scorecard Dashboard
Red/Yellow/Green per element]
        I[Manager Deal Review
Coaching basis, not audit]
        J[Gong/Scratchpad
AI field population]
    end
    
    E --> H
    H --> I
    J --> E
```

---

Stage Exit	Required Field(s)	Field Type
Qualification → Discovery	Identified Pain, Metrics	Long Text (≥50 chars)
Discovery → Solution Alignment	Economic Buyer (contact lookup)	Lookup (Contact object)
Solution Alignment → Proposal	Champion (contact lookup)	Lookup (Contact object)
Negotiation → Closed Won	Paper Process	Long Text (≥50 chars)

How should you design custom fields in Salesforce to enforce MEDDPICC capture without making the AE's job miserable, and which fields are mandatory vs nudge-only?

Designing MEDDPICC Custom Fields in Salesforce: Mandatory vs. Nudge-Only

THE DETAIL

What does the score mean?