Every framework—MEDDPICC, BANT, CHAMP—assumes you already know what matters to the buyer. But discovery calls rarely start there.
You walk into a discovery call with MEDDPICC fields to fill. Ten minutes in, the buyer is talking about something your framework doesn't have a category for—something that matters more to them than budget or decision timeline. Your framework breaks.
Qualification frameworks exist for a reason: they force clarity, reduce guesswork, and give your manager something to audit. But they're built on a hidden assumption that doesn't hold up on most calls—that you already know which signals matter before the buyer tells you what they actually need.
A qualification framework is a filter, not a discovery tool. MEDDPICC tells you what to look for—Metrics, Economic Buyer, Decision criteria, Champions. But it assumes those things matter equally to every buyer, and that you'll know them because you've qualified the lead correctly before the call started.
In practice, discovery calls expose a gap: the framework was designed for situations you've already solved. When you step into a new use case, a new buyer type, or a deal with an unusual stakeholder structure, the framework suddenly feels like a multiple-choice test where none of the options fit.
Take a common breakdown: you've identified the economic buyer and the champion, checked the box. But on the call, you discover the buyer's real friction isn't decision-making power—it's that they're being evaluated by their board on a metric the champion doesn't understand. Your framework has no field for "evaluation risk." So you either force-fit the information into an existing field and lose nuance, or you stop using the framework at all.
The stronger AEs in your shop don't abandon their framework on discovery calls—they use it as a checklist after the call, not a script during it. They let the buyer lead, listen for what's actually blocking progress, and then map those signals back to their framework later.
This works because discovery isn't about filling in boxes. It's about understanding what the buyer is trying to do, why the current situation isn't working, and whether you can help. The framework helps you evaluate fit afterward. But if you're checking fields during the call, you're divided: half listening to the buyer, half listening to your internal checklist.
The call recording will later show you exactly where you stopped listening and started checking boxes. It's visible. It kills the conversation.
Sometimes you've picked the right framework for your deal size and sales cycle. MEDDPICC makes sense for your $200K enterprise deals. But then you're on a call with a buyer who hasn't yet admitted they have a problem at all—they're in education mode, not evaluation mode. Your framework is useless because the buyer hasn't reached the stage where Metrics or Decision Criteria matter.
This happens constantly with inbound leads that haven't actually started a buying process. You have a framework built for deals in motion, but the prospect is still trying to understand if change is possible.
The framework was right for a different stage of the deal. Now you're using it incorrectly, and the buyer feels like they're being interrogated instead of helped.
Keep the framework in your CRM and your pre-call prep, not in the call itself. Review it before you dial: "These are the things I need to know about this deal type. What does the buyer already know? What are they likely to care about? What am I listening for?"
Then run the call like a conversation. Ask open questions about what they're trying to accomplish and what's in the way. Listen for pain, priority, and perspective. Write notes during the call if it helps—but not framework-shaped notes. Write what they actually said.
After the call, spend five minutes mapping what you learned back to your framework. "They mentioned headcount scaling as the real metric. That's the Metric. The VP of Ops is making the call, but the CFO has to sign off—that's Economic Buyer and Champion. They've already looked at Competitor X and ruled it out because of integration."
Your framework becomes a structure for thinking about what you learned, not a test you're administering.
If you're using a framework as a gate for pipeline—"this deal doesn't go into stage 2 until MEDDPICC is filled"—you've already lost. You're incentivizing AEs to fill boxes with guesses instead of asking the buyer.
Better: discovery call happens, AE takes notes, AE fills framework afterward based on what they actually learned. Manager reviews the framework in the deal review and asks: "What did the buyer say that made you mark Economic Buyer as strong?" If the AE says "I didn't ask them directly," that's a coaching moment.
The framework is still a gating tool—it just gates based on what you know, not on what you told yourself you were supposed to learn.
Your framework breaks fastest when AEs interpret it differently. One person thinks "Decision Criteria confirmed" means the buyer mentioned their approval process. Another thinks it means they've told you exactly what they're evaluating you on.
Embed framework fields into your CRM as fields, not as prose. Run call reviews on recordings where AEs are applying the framework. Calibrate quarterly: "When we say 'Strong Champion,' here's what we mean: the buyer has explicitly said they'd advocate for this internally, they understand the business case, and they have skin in the game."
Record the definitions. Make them searchable in your CRM. Train new AEs on what each field actually means by showing them examples from deals you've won.
That consistency is what makes the framework stick—not the framework itself.
No. A short sales cycle with transactional deals needs ANUM or CHAMP—lightweight frameworks that qualify fast. Enterprise deals with long cycles and buying committees need MEDDPICC or GPCTBA/C&I to map stakeholders and decision complexity. Match the framework to your deal type, then apply it consistently within that category.
BANT (Budget, Authority, Need, Timeline) is simpler and faster—four fields, designed for shorter sales cycles. MEDDPICC (Metrics, Economic Buyer, Decision process, Decision criteria, Paper process, Identified pain, Competitor, Champion) is more detailed and designed for complex, multi-stakeholder deals where understanding the buying process matters as much as the decision-maker.
Review call recordings. Listen for whether the AE asked about the framework elements directly or is filling fields from inference. In deal reviews, ask follow-up questions: 'How did the buyer describe their metric?' or 'What exactly did the economic buyer say about budget?' If the AE can't cite what the buyer actually said, they're guessing.
Not effectively. If the buyer is in education mode, they won't have a decision timeline or identified criteria yet. Use a simpler framework for early-stage conversations—Pain, Priority, Perspective—then transition to full qualification once they're actually evaluating. Forcing MEDDPICC on a prospect who hasn't admitted they have a problem kills the call.
Part of our guide to Discovery calls.
Repwing listens to your discovery calls and puts the next question on your phone while you are still in the conversation. Fourteen days free, no card.
Start free trial