Your BANT or MEDDPICC framework works in theory. On the actual call, reps improvise, skip steps, or chase bright objects. Here's why—and how to lock it in.
You pick a framework. You train the team. But on discovery calls, your reps abandon it anyway—they follow whoever talks loudest, chase the easy question, or skip the hard one because the buyer said "not relevant." Now your qualification is inconsistent, your deal reviews are fiction, and you can't tell if a lead is actually qualified.
The problem isn't the framework. The problem is that frameworks assume a linear conversation. Real conversations don't work that way.
BANT, CHAMP, MEDDPICC, GPCTBA/C&I—these all require a specific sequence. You ask about Budget, or Authority, or Need, in an order that builds to a yes or no. On the call, the prospect derails. They jump to technical questions. They answer one question with three others embedded inside it. They say "we're still evaluating" when you need to know if they have authority.
The rep has two choices: stick to the script and sound robotic, or abandon the framework and wing it.
Most reps wing it. They reason that being conversational matters more than rigor. They're half right—but the cost is that qualification becomes whatever they felt during the call.
The prospect answers a different question than you asked. You ask about budget; they describe their current vendor's pricing. You can use that signal, but it's not the same as knowing if they have money to spend and authority to approve it. A rep without a fallback plan either pushes the same question again (awkward) or moves on (incomplete).
The rep encounters an objection and stops asking. They hear "we're still in vendor selection" and check the Authority box as a maybe instead of probing: "Who's making the final choice—is it you, your boss, or a committee?" That one question turns maybe into either yes or no. Without the discipline to ask it anyway, the deal stays soft.
The conversation feels productive, so qualification gets skipped. The buyer is engaged, asking questions, talking about their problems. The rep thinks the deal is warm and moves to the next stage. Two weeks later, it turns out no one was authorized to buy, or the budget was already spoken for. The call felt good; the qualification was invisible.
Write your framework into your discovery template before the call starts. If your process is BANT, your template has four sections: Budget, Authority, Need, Timing. The rep fills in what they heard in each section during the call, not after. That creates a forcing function—if a section is blank, they see it immediately.
Use branching language, not linear questions. "Do you have budget?" is fragile—one no and the rep stops. "What does budget look like for a solution like this?" or "How are budget conversations typically handled on your team?" survive an evasive answer. Bake these branches into your playbook so reps don't have to invent them.
Train on the hard qualifications first. Most reps nail Need and Timing. Authority and Budget are where frameworks fail. Spend your call time in role-play focused on how to get a real yes or no on those two, specifically. That's where the skeleton of qualification actually lives.
Hold reps accountable to filled-in templates in your deal reviews, not to what they say about the deal. "This is a warm lead" doesn't mean anything. "Authority: Yes, she's the CFO and signs off on software purchases over $50k" or "Authority: No, procurement committee decides, and they don't include end-users" does. If the template is blank for a critical qualification criterion, the deal doesn't advance—or it advances with a flag for the AE to go back and fill it in.
Codify your framework in your CRM workflow so it's visible, not optional. If your sales process requires a CHAMP qualification before the deal moves to Stage 2, make that a hard gate. The rep can't click forward without filling in Challenges, Authority, Money, and Priority. Friction creates habit.
If your sales cycle is short and intent is high (SMB, self-serve motion), ANUM or CHAMP work better than BANT. They prioritize Urgency and Challenges—the signals that matter when a buyer is already leaning in. BANT asks about things you already know from intent signals and wastes time.
If you're selling into enterprise with a long cycle, MEDDPICC or GPCTBA/C&I give you the edges—Metrics, Economic Buyer, Decision Criteria for MEDDPICC, or Implications and Negative Consequences for GPCTBA/C&I. Those frameworks assume complexity and multi-step buying; they survive contact better when deals actually have it.
If your deal size is variable, use different frameworks for different deal tiers. A $5k SMB deal doesn't need Economic Buyer and Buying Process and Decision Timeline; a $500k enterprise deal needs all of it. Bake both into your process so reps apply the right rigor to the right deal size.
Spot-check call recordings. Pick two or three deals a week, listen to the call, and score it against your framework. Did the rep ask the hard question, or work around it? Did they accept an evasive answer, or press? Did they fill in the template during the call or make it up after?
Coach to the gaps you hear. Don't coach to the rep's self-assessment or the deal outcome—coach to what you actually heard. That turns a framework from a category to a discipline.
Qualification frameworks work. But they only work when you assume contact will be messy, build systems to navigate that mess, and hold reps to the rigor the framework is supposed to create. Without that, you're not running a framework—you're running therapy for whatever deal the rep wants to believe in.
BANT asks Budget, Authority, Need, and Timing in a linear sequence; CHAMP asks Challenges, Authority, Money, and Priority, starting with the prospect's problem first. CHAMP works better for solution-based selling and shorter cycles where urgency signals are stronger. BANT fits longer, more formal buying processes.
Match the framework to your sales cycle and deal complexity. Use ANUM or CHAMP for SMB or short cycles under three months; use MEDDPICC or GPCTBA/C&I for enterprise with multiple stakeholders and budgets over six months. If deal sizes vary, use different frameworks per tier.
Frameworks assume linear conversations, but real calls jump around. Reps face objections, evasive answers, or technical tangents. Without branching language and accountability in your template, winging it feels more conversational. Lock it in with CRM gates, pre-call templates, and recorded call audits.
Bake it into your CRM as a hard gate before stage advancement. Use a discovery template with sections for each criterion that must be filled during the call. Spot-check two or three recordings weekly and coach to what you hear, not what the rep claims about the deal.
An evasive answer is still a signal—it usually means no, and the rep is avoiding it. Train reps to rephrase and probe: 'Help me understand how this normally works on your side' or 'What does the process look like when budget is approved?' Branch around objections instead of stopping.
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