Field design
Build one field per element and resist the urge to expand. Metrics holds the quantified business outcome the buyer named, stored as a number and a unit. Economic Buyer Access is a picklist reading identified, met, or validated. Decision Criteria is a checkbox for whether a written criteria list exists, paired with a text field for what it says. Decision Process holds the steps and their owners. Identified Pain is a picklist mapped to your standard problem categories so it can be sliced later. Champion Status is a picklist reading none, potential, or tested.
Add two supporting fields. A rolled-up qualification score, and a last-verified date so a manager can see stale qualification without opening the record.
Enforcement at the stage boundary
Validation rules belong at stage transitions, not at record creation. Blocking the move from discovery into evaluation until Economic Buyer Access is at least identified turns qualification into a gate. Requiring the same field the moment an opportunity is created produces placeholder text and trains reps to work around the system.
Write the rule so the error message states what evidence is missing rather than which field is blank. Reps respond to a prompt about the buyer. They ignore a prompt about a field name.
Consistency beats cleanliness
The usual objection is that the CRM is too messy for any of this to matter. ORM's position on that is blunt: every company believes its data is uniquely bad, and the belief is wrong. Garbage in does not have to mean garbage out. What breaks modeling is inconsistency, not imperfection. A picklist that every rep interprets the same way carries signal even when the underlying qualification is optimistic. A free-text field interpreted six ways carries none.
That is the argument for controlled vocabularies over open text on every element where you plan to run a report.
Measuring whether it took hold
Track two numbers. Completion rate tells you whether reps fill the fields. Verification rate tells you whether the entries are real, measured by sampling late-stage deals and checking whether the named economic buyer shows up in logged activity or calendar records.
The gap between those numbers is where coaching goes. High completion with low verification means the fields have become paperwork. Once verification holds, the qualification score can be joined to outcomes and used as a weighting input for sales forecasting. Teams that skip the verification step usually find their forecast accuracy unchanged and blame the framework rather than the data behind it.
Frequently Asked Questions
How many custom fields does MEDDIC need?
Six to eight. One per element, plus a rolled-up score and a last-verified date. Teams that build twenty fields get partial completion on all of them, which is worse than full completion on six because partial data cannot be filtered or modeled.
Should MEDDIC fields be required?
Require them at stage boundaries, not at record creation. A validation rule that blocks the move from discovery into evaluation until the economic buyer field is populated enforces the discipline at the moment it matters. Requiring fields on a brand new opportunity produces placeholder values.
Text fields or picklists?
Picklists for status, text for evidence. Economic Buyer Access should be a picklist with values like identified, met, and validated. A free-text box next to it holds the name and the meeting date. The picklist is what reporting runs on; the text is what a manager reads in a deal review.
How do you know reps are actually using it?
Compare field completion against field accuracy. Completion is easy to hit and easy to fake. Sample twenty late-stage deals per quarter, check whether the named economic buyer appears in any logged activity, and report the mismatch rate. That number tells you whether the framework is real.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like how to track meddic in your crm into prescriptive action for your team.
Schedule a Demo