MEDDPICC in Salesforce: Fields, Color Coding and Dashboards That Don't Become a Checklist

That's the whole build. The hard part isn't Salesforce. It's keeping MEDDPICC from turning into a few fields nobody reads.

I've watched the pattern repeat: training, new CRM fields, and within three to six months, a few fields nobody reads. That's not the framework failing. That's the rollout. For the framework itself, start with the complete MEDDPICC guide.

Why do MEDDPICC fields in Salesforce usually fail?

Because most of them are naked.

A text field called "Champion" with a name in it. A "Metrics" field with a number typed in. A checkbox that says "Pain Identified." In most systems, those look done the second anything is entered.

A filled field isn't evidence. A typed number is data entry.

The fix is in how you design the fields:

1. No naked fields. Every letter gets a definition and a red, yellow or green color, so you see the gaps, not just the boxes.
2. The notes say what evidence you have. What do we know, who confirmed it, and when?
3. Colors, not scores. A score averages away the one red letter that kills the deal.
4. No strict stage gates. I'm not a fan of bogging down the CRM with painful gates. They teach sellers to click boxes.
5. Coach it every week. The fields only stay honest if a leader looks at them with the seller, deal by deal.

Video · Sales Tips

Green in the CRM. Red in reality. #shorts · David Weiss on YouTube

What fields should you create for each MEDDPICC letter?

Create these on the Opportunity object. One pair per letter, plus two optional Contact lookups.

Field	Type	Purpose
[Letter] Color	Picklist: Red, Yellow, Green	The grade. Default to Red.
[Letter] Evidence	Long Text Area	What we know, who confirmed it, when, and what's still assumed
Economic Buyer	Lookup (Contact)	Who controls funds at this deal size
Champion	Lookup (Contact), optional	Only if the color and evidence fields carry the behavior

That's 16 core fields: Metrics, Economic Buyer, Decision Criteria, Decision Process, Paper Process, Identify Pain, Champion and Competition, each with a Color and an Evidence field. Suggested API names follow the pattern Metrics_Color__c and Metrics_Evidence__c.

A few build notes:

• Make the picklists restricted so nobody invents "Light Green."
• Default every color to Red. Every deal starts red. Red isn't bad. It's honest.
• Running MEDDICC? Skip the Paper Process pair. Running MEDDIC? Skip Competition too. Not sure which you need? Look at your last 10 deals.
• Keep the order of operations visible. Lay the fields out on the page in the order you work them: Identify Pain, Metrics, Decision Criteria, Competition, Champion, Economic Buyer, Decision Process, Paper Process. Not the order of the acronym.

A word on the Champion lookup. A champion is a behavior, not a person. Your CRM doesn't need a "Champion" field. It needs an "Advocacy" field. A lookup with a name in it tells you nothing about whether that person sold for you last week. If you add the lookup, the Champion Color and Champion Evidence fields have to carry the behavior: what they did, when, and who saw it.

For the full stakeholder map, use Opportunity Contact Roles, and edit the Role picklist to match the functional roles you track (End User, Technical Buyer, Problem Owner, Executive Sponsor, Economic Buyer). Keep the behavior labels in your stakeholder map.

What goes in the evidence field?

This is the field that does the work.

The prompt I'd put in the field's help text: "What do we know, who confirmed it, and when? What's still assumed? What's the next action?" That mirrors the evidence, gap and next-action columns on the free MEDDPICC Scorecard.

Here's what the difference looks like on Metrics in an illustrative deal:

Weak evidence (reads green, is red)	Strong evidence (earns green)
"Saves 10 hours a week."	"Baseline: two planned hires to cover manual reporting. Business case agreed by the VP of Operations on the 12th and reviewed with the CFO's team on the 19th. Open item: CFO sign-off at Go / No Go."

The weak version is a benefit. The strong version has names, dates, numbers and documents. If the buyer hasn't validated it, you don't have it.

How do you put the MEDDPICC rubric in Salesforce help text?

Use field-level help text on each Color picklist. When a seller hovers, they see exactly what red, yellow and green mean for that letter. That's what keeps "green" meaning the same thing to everyone.

Use the exact rubric wording, so the CRM, the Color Coding Cheat Sheet and your deal reviews all say the same thing. Each letter's full guide goes deeper on what green takes: Metrics, Economic Buyer, Decision Criteria, Decision Process, Paper Process, Identify Pain, Champion, Competition.

Field	Help text
Metrics Color	What the problem costs and what fixing it is worth, in the buyer's numbers. RED: Metrics that matter not identified. YELLOW: Surface metrics exist, but unique outcomes not agreed. GREEN: Outcome-driven business case and change justification agreed by all needed stakeholders.
Economic Buyer Color	Who can create or allocate budget at this deal size. RED: Economic Buyer unknown or no direct contact established. YELLOW: Economic Buyer identified, but sponsorship not gained. GREEN: Direct EB engagement complete and agreement to sponsor.
Decision Criteria Color	How the buyer will judge the options. RED: Decision criteria aren't known. YELLOW: Criteria known, but only partially influenced, or slightly misaligned. GREEN: Criteria fully agreed, documented and influenced, with your differentiators explicitly agreed on.
Decision Process Color	The business lane to a decision. RED: Key process steps and owners not identified; MAP not started. YELLOW: Steps and owners identified, but not documented, or key milestones are missed. GREEN: Decision process fully understood and documented, dates agreed, and milestones tracking.
Paper Process Color	The legal lane to a signature. RED: Paper process not started. YELLOW: In procurement or legal review without a defined timeline. GREEN: Paper process fully understood, redlines are doable, and a defined timeline is being tracked.
Identify Pain Color	The real problem and what it breaks. RED: Pain at surface level with one or more stakeholders. YELLOW: Initial pain implicated with multiple stakeholders, but needs validation, broader consensus and deeper implication. GREEN: Pain fully implicated for all relevant personas and connected to a business priority.
Champion Color	A behavior, not a title. RED: No identified champion; you're still at the contact or coach level. YELLOW: A coach showing early champion behaviors, not yet tested at every level. GREEN: Champion fully validated, enabled with collateral, and actively selling for you internally.
Competition Color	Everything working against the change. RED: Threats from competitors or status quo not identified. YELLOW: Competitive differentiators not resonating or agreed on. GREEN: Strong mutual fit aligned to decision criteria, differentiators believed, Vendor of Choice stated or strongly implied.

Salesforce allows up to 510 characters of field-level help text (Salesforce Help). Each of these fits. If you add to them and run over, keep the three rubric lines in the help text and move the one-line definition to the field's Description.

How do you show the colors at a glance?

Picklist values are hard to scan in a list view. Add a small formula field per letter that turns the color into a traffic light. Salesforce documents this exact pattern with its built-in sample images (Sample Image Link Formulas):

IMAGE(
  CASE(Champion_Color__c,
    "Green", "/img/samples/light_green.gif",
    "Yellow", "/img/samples/light_yellow.gif",
    "Red", "/img/samples/light_red.gif",
    "/s.gif"),
  "Champion color")

Create one per letter and add all eight to a list view. In a 1:1, the leader and seller open the same view and the whole board shows up at once.

Why should you surface the first gap instead of a total score?

Because scores give you false positives.

Say each letter of MEDDICC is worth three points. Seven letters, 21 points. A deal at 18 looks great. But you're at zero on Metrics. Good score, no business case. An average hides exactly the risk you're looking for.

So don't build a score formula. Build one that tells you where to look. This text formula returns the first letter that isn't green, walking the order of operations:

IF(NOT(ISPICKVAL(Pain_Color__c, "Green")), "Identify Pain: " & TEXT(Pain_Color__c),
IF(NOT(ISPICKVAL(Metrics_Color__c, "Green")), "Metrics: " & TEXT(Metrics_Color__c),
IF(NOT(ISPICKVAL(Decision_Criteria_Color__c, "Green")), "Decision Criteria: " & TEXT(Decision_Criteria_Color__c),
IF(NOT(ISPICKVAL(Competition_Color__c, "Green")), "Competition: " & TEXT(Competition_Color__c),
IF(NOT(ISPICKVAL(Champion_Color__c, "Green")), "Champion: " & TEXT(Champion_Color__c),
IF(NOT(ISPICKVAL(Economic_Buyer_Color__c, "Green")), "Economic Buyer: " & TEXT(Economic_Buyer_Color__c),
IF(NOT(ISPICKVAL(Decision_Process_Color__c, "Green")), "Decision Process: " & TEXT(Decision_Process_Color__c),
IF(NOT(ISPICKVAL(Paper_Process_Color__c, "Green")), "Paper Process: " & TEXT(Paper_Process_Color__c),
"All green"))))))))

Call it First Gap. Why the order of operations and not the acronym? Because early gaps cause the biggest problems later. Fix the foundation and the deal often unsticks itself. Early in a deal, First Gap will usually say "Metrics: Yellow." That's not an alarm. It's the next conversation.

How should Path and Guidance for Success work with MEDDPICC?

Path is where MEDDPICC meets your stages without becoming a gate.

Salesforce Path shows key fields and Guidance for Success for each value of a picklist, typically Opportunity Stage. You get up to five key fields per step and up to 1,000 characters of guidance (Salesforce Ben; setup walkthrough on Trailhead).

Five key fields is a feature here, not a limit. It forces you to show only the letters that matter at that stage. Use the Color picklists as key fields, and use the guidance for the stage targets, the pulse check and the plays. Targets come from MEDDPICC by Sales Stage.

Stage	Key fields	Guidance for Success (starter text)
Discovery	Pain, Metrics, Decision Criteria, Competition, Champion	Leave with a verified baseline: pain and metrics in their numbers. Criteria directional (yellow). Red on Economic Buyer and both process letters is fine. Pulse check: "Is what I described actually the problem, or are there layers underneath?" Plays: Account Planning, Peel the Onion, Face of Discovery.
Demo	Decision Criteria, Metrics, Competition, Champion, Decision Process	Create contrast, one need and one outcome at a time. Most letters yellow leaving. Pulse check: "Does the solution justify changing now that everyone would support?" Plays: Cinematic Demo, Reverse RFP Scorecard.
Solution Alignment	Decision Criteria, Competition, Champion, Metrics, Decision Process	Decision Criteria and Competition green before you leave. Start the mutual action plan. Pulse check: "If we locked the requirements today, would anyone push back?" Plays: Why Us, Side by Side.
Business Alignment	Metrics, Pain, Champion, Economic Buyer, Decision Process	Metrics, Pain and Champion green before you leave. Never let the first executive exposure be the final one. Pulse check: "What's the first question the economic buyer will ask?" Plays: Business Case One-Pager, Cost of Delay.
Go / No Go	Economic Buyer, Champion, Decision Process, Paper Process, Metrics	Everything but Paper Process green leaving. Pulse check: "Is there any reason this doesn't move forward?" Plays: PRFAQ, Fast Track to Procurement.
Proposal / Negotiation	Paper Process, Economic Buyer, Champion, Competition, Decision Process	All green to commit. Pulse check: "Are there terms other vendors have pushed back on?" Plays: Legal and Procurement Alignment, Give to Get.

Different stage names? Map them to the closest row, and consider adding the two alignment stages most processes skip. Notice what Path doesn't do: it doesn't stop a seller from moving the stage. It shows them what good looks like, at the moment they're looking.

What reports and dashboards should you build for deal reviews?

Build fewer than you think. Each one should answer a question a leader actually asks in a 1:1, deal review or forecast call.

1. Commit deals with a gap. Forecast Category = Commit and First Gap ≠ "All green." Commit means green across all letters and milestones tracked in a mutual action plan. Put this at the top of the dashboard. It protects the number.

2. Where open deals are stuck. Open pipeline grouped by First Gap. If half your pipeline says "Metrics: Yellow," you don't have a deal problem. You have a pattern. Coach the pattern.

3. Color by stage. A matrix report per letter: Stage down the side, Color across the top. Compare it to the stage targets.

4. Colors that moved this week. Turn on Field History Tracking for the Color fields and report on Opportunity Field History. The question isn't whether the deal is busy. It's whether any color changed since last week.

Forecast categories: each Stage value maps to a default Forecast Category. Default the alignment stages and Go / No Go to Best Case (what I call Upside). Commit is earned by evidence, not handed out by a stage. And the colors in the CRM should match what the seller says on the forecast call.

Should you add a validation rule for Commit?

My default is no. Strict gates teach sellers to click boxes, and when the color-coding rhythm runs well, you don't need forced exit criteria at all.

If your leadership team insists on one guardrail, make it the lightest possible: block Commit when any letter is red. Leave yellow visible on reports instead of blocked, so sellers stay honest instead of rounding up.

AND(
  ISPICKVAL(ForecastCategoryName, "Commit"),
  OR(
    ISPICKVAL(Pain_Color__c, "Red"),
    ISPICKVAL(Metrics_Color__c, "Red"),
    ISPICKVAL(Decision_Criteria_Color__c, "Red"),
    ISPICKVAL(Competition_Color__c, "Red"),
    ISPICKVAL(Champion_Color__c, "Red"),
    ISPICKVAL(Economic_Buyer_Color__c, "Red"),
    ISPICKVAL(Decision_Process_Color__c, "Red"),
    ISPICKVAL(Paper_Process_Color__c, "Red")
  )
)

Error message: "Commit means the buyer is executing a shared plan with you. A red letter means we don't know something yet. Move it to Best Case, or close the gap first."

ForecastCategoryName stores Commit as "Commit" (Salesforce Object Reference). Don't confuse it with the older ForecastCategory field, which stores the same bucket as "Forecast."

Never put a gate on stage changes. A red in the right place is completely appropriate. Red on Paper Process in Discovery is normal. Red in Commit is a problem.

How do you keep MEDDPICC in Salesforce from becoming a checklist?

The fields are the easy part. The rhythm is what makes them true.

• Sellers color their own deals before every call, after every call, and before every internal deal conversation. Once the habit is built, it takes a few minutes per deal.
• Leaders look at the same screen. Pressure-test green: what did we see, hear and validate? Who confirmed it, and when? For red and yellow, don't criticize. Ask, "What's your plan to close the gap?"
• Coach color first, then the order of operations. Start with where the deal is and why the seller thinks it's stuck, based on their own colors.
• Weekly, deal by deal. One deep deal review a week on a top-quartile deal. Skip the rhythm and MEDDPICC becomes flavor of the month.
• Don't ask the letters out loud. The CRM uses MEDDPICC language. Your buyer doesn't. "Who's the economic buyer?" becomes "If there isn't budget allocated, who can create it?"

Drive it top-down. Design it for the rep. That's when adoption takes off.

Video · Sales Leadership Rhythms

Why Your MEDDPICC Rollout Failed (7 Fixes for Sales Leaders) · David Weiss on YouTube

Running HubSpot instead? Same approach, different build: MEDDPICC in HubSpot.