Your framework is a checklist, not a conversation guide. Here's how to keep discovery natural while actually testing fit.
You pick a framework — BANT, CHAMP, MEDDICC — load it into your prep notes, and dial in. Then the buyer talks, and none of it goes the way you planned.
That gap between framework and reality is where most qualification fails.
Frameworks are essential. They're a repeatable filter that separates real opportunities from busy researchers. But they're filters for after the call, not scaffolding for during it. The moment you try to force a BANT checklist into natural conversation, buyers smell the script and close up.
Think of qualification like a doctor's intake form. The doc doesn't read the form aloud to you. She asks questions that sound human — "How long has this been bothering you?" — and listens for the answers that map onto the framework behind her notepad. The form structures her thinking, not your experience.
Your discovery call should work the same way.
You know what you need to know: Does this person have authority? Is there a real problem? Do they have budget? Is timing realistic? But you don't lead with those questions in that order. You lead with what matters to the buyer — the thing that got them on the call — and let the framework shape how you listen and probe.
A buyer calls because their team is missing close deadlines. You don't respond with "So, Budget, Authority, Need, Urgency — which do you want to tackle first?" You ask what's breaking. You dig into the cost of staying stuck. You find out who cares enough to fix it. Then you map those answers onto your framework and know whether to advance or pass.
Here's a detail most qualification guides skip: the framework you use should match the deal size and complexity you're selling into.
For a smaller deal with a shorter cycle, CHAMP or ANUM works because you're looking for quick intent. You need Challenges and Priority to move fast. Budget and Authority are usually simpler.
For enterprise, MEDDICC makes sense because you need to map the entire economic buyer, understand decision criteria, and identify a champion within the buying committee. That's a different conversation shape entirely.
But here's what actually changes the call: your account-level research beforehand.
If you know the company just hired a new VP of Operations, or they're integrating an acquisition, or they published a press release about a new product line, you're not asking generic questions. You're asking specific ones tied to signals that suggest timing is real. "I saw you brought on a new ops lead — what's the first thing she's looking to improve?" That's a qualification question dressed as curiosity. It's specific to their moment.
Frameworks don't monitor markets, hiring, or leadership changes. You do. The framework just tells you which signals matter and which ones don't.
So here's the operating model that works in practice:
Before the call: Do account research. Understand their ICP fit. Know what signals suggest they're in-market. Load your framework as a mental checklist. Brief yourself on a small set of topics you need to confirm — maybe three things. That's it.
During the call: Lead with their context. Ask about the challenge. Listen more than you talk. Let the conversation breathe. When they mention a pain point, probe it. When they name a stakeholder, remember it. When they give you a timeline, test it.
After the call: Score the conversation against your framework. Did they name a specific problem? Check. Do they have authority to evaluate, or do we need to thread in other voices? Note it. Is there budget, or do we need to prove ROI first? Document it. Is the timing real, or is this a "sometime next year" conversation? That's the filter.
That last part — the score — is where frameworks do their actual work. They convert a messy conversation into a yes, no, or "needs one more signal" decision.
Here's what separates teams that actually convert: they use the same framework the same way every cycle. Not rigidly. Not in order. But with enough consistency that they know what "qualified" looks like and what "maybes" should wait.
A team that runs BANT on 80% of calls builds judgment about what a borderline deal looks like. They know that "authority is unclear but urgency is strong" means something specific for their business. A team that mixes three different frameworks ends up with a pipeline that looks good on a spreadsheet and closes at 15%.
Pick one framework that fits your deal size. Train your team to ask the questions naturally. Score the result with discipline. That's the practice. The framework itself is just the language.
Your discovery call should sound like two people having a real conversation about a real problem. The framework is the invisible structure underneath that makes sure you're actually learning whether it's a conversation worth having again.
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