MEDDICC is one of the most widely adopted qualification frameworks in B2B SaaS. There's a good book behind it, plenty of training, and a common language that a whole sales org can rally around. And yet, in company after company, it quietly decays into a box-checking ritual: fields full of buzzwords, filled in the night before a pipeline review, then forgotten.
The framework isn't the problem. The execution is. And the biggest missed opportunity is who gets left out of it — PreSales.
What MEDDICC Actually Is (and Isn't)
MEDDICC describes itself as a qualification framework, built primarily for complex B2B software and enterprise deals. In mid-market or commercial segments, it's often overkill — cannons at kittens.
The acronym: Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion. Two common variants add a P for Paper Process (what has to happen before the customer can actually issue a PO or sign) and a second C for Competition.
Here's the crucial distinction: MEDDICC answers one question — is there a deal here, and what do I need to understand to say yes or no? That's qualification. It is not the same thing as discovery, which goes deeper into defining and shaping the customer's actual problem.
Keep that boundary in mind, because it's exactly where PreSales earns its seat.
Why PreSales Belongs in the Framework — From Day One
When someone says "Sales just rolled out MEDDICC," the right reflex is to ask: and where was PreSales?
A common rollout mistake is training only the AEs. The SEs weren't in the room, don't share the language, and can't contribute. That's a waste, because Solution Engineers can materially strengthen at least four of the six elements:
- Metrics — SEs bring the technical and domain depth to push past vague claims to hard numbers.
- Identify Pain — the same depth surfaces the real business impact behind surface symptoms.
- Decision Criteria — this is the classic one. Low-maturity teams simply record "what the customer says they need." A strong SE helps shape the criteria toward what the customer actually needs — and that requires the technical and functional depth AEs usually don't have.
- Champion — SEs often build genuine credibility with technical stakeholders, which is where champions are made.
If your organization adopts MEDDICC, adapt the wording to fit your world if you like — but bring the entire sales organization along, not just the AEs. A shared framework is a rare chance for Sales and PreSales to grow closer, not further apart.
The Real Failure Mode: Shit In, Shit Out
The framework is solid. The thinking inside it shows up in every good sales methodology. So why does it fail?
Because organizations treat it as a process to complete rather than a standard to meet. They roll it out, run a thirty-minute onboarding session, and assume everyone now (a) understands it and (b) does it forever. Nobody ever defines what great looks like.
The numbers back this up. Studies — and plenty of first-hand experience at companies that used MEDDICC — show adherence collapses fast: roughly half the team stops filling in the fields properly within six months. The recurring criticism is always the same: it becomes a CRM exercise, not a sales method. Fields get populated for the forecast call, not while actually working the deal.
The symptom is unmistakable. Open two different opportunities, read the Metrics field on each, and they sound identical — the same bullshit bingo. You can't tell Deal 1 from Deal 2, because nobody ever defined what a good entry should look like.
AI Doesn't Fix Bad Discovery
Modern CRM setups can wire conversational-intelligence tools directly into the opportunity, letting an LLM auto-populate MEDDICC fields straight from a call transcript. Technically it's trivial — one click. Realistically, only 10–20% of sales orgs operate at that level today.
But automation only removes the administrative burden. It does nothing for quality. If you ran a shallow discovery call, the Metrics field will still contain garbage — because you didn't probe, didn't challenge, didn't feed in the insights that get a customer to share real numbers. Automating the pipe from a bad conversation to a CRM field just delivers the same surface-level noise faster.
Which brings it back to the one thing that's actually missing.
Define "What Great Looks Like"
This is the single highest-leverage fix. Before rollout, define a blueprint: what does an ideal entry look like — for the Metrics field, for Identify Pain — in a given industry or customer segment? That blueprint becomes the North Star. It can vary by vertical, and that's fine. The point is that people have something to aim at, and reviewers have something to hold the line against.
Then use the rhythms you already have. Forecast calls, deal reviews, one-on-ones — bring MEDDICC quality up in every one of them, refer back to the North Star, and teach the organization, deal by deal, what a good opportunity looks like and what a weak one looks like.
Here's where the SE has a structural advantage. Because of coverage ratios of 1:3, 1:4, or 1:5, a single SE sees far more deals than a single AE — sometimes 20 or 30 in a quarter versus a strategic AE's handful of named accounts. That breadth means SEs recognize patterns across industries and can judge, better than almost anyone, what a good metric looks like for a given customer type. That perspective is gold when you're calibrating what great looks like.
Where Value Actually Lives
Strip it down and value is simple: reducing cost, increasing revenue, or favorably shifting risk. Features and functions are fine, but they're never the point — the business outcome is.
In MEDDICC, value hides in two letters:
- Identify Pain — finding a problem big enough that it should be solved now. Customers are terrible at explaining their pains; they're excellent at describing symptoms. Start with the symptom, ask what negative consequence it creates, and keep driving until you reach the business level: this hurts cost, this hurts revenue, this raises risk. That's the qualitative case for change.
- Metrics — quantifying it. How much, how often, how slow? This is where Cost of Inaction and ROI live. If your solution costs €1M and the cost of inaction is only €500K, pack up. If it costs €1M and solves a €50M problem, you're in business.
Notice you can't produce a real Identify Pain entry without doing discovery first. The content that belongs in that field is the output of good conversations — which is exactly why SEs, who typically lead discovery in enterprise deals, are central to filling MEDDICC with substance rather than noise.
Stop Trying to Separate Qualification and Discovery
A final trap: treating qualification and discovery as two mechanically distinct activities. They're not. Qualification is a subset of discovery, with a fluid transition. Early on, qualification dominates — do we want to invest more time, capacity, and resources here? Once you're convinced there's business to be done, discovery takes over — let's define the problem in depth.
The output of discovery flows straight into your MEDDICC fields. Need two extra fields to capture it? Add them. It's still MEDDICC, still analyzable, still useful. Don't tear apart things that ultimately belong together in service of a definition that would only survive in a scientific paper. Be pragmatic. Do what helps people work better and win more.
The Takeaway
MEDDICC works when it's treated as a living sales discipline, not a CRM chore. That means three things: bring the whole sales organization in, PreSales included; define what great looks like and reinforce it in every deal review and one-on-one; and recognize that the value — the pain and the metrics — comes from real discovery, which is precisely where Solution Engineers create leverage. The knowledge isn't the problem. Execution and staying with it are.
Listen to the full episode
For the full conversation on MEDDICC, value selling, and the role of PreSales: PreSales Unleashed: Das Problem mit MEDDICC (269)