Lead qualification framework: BANT vs MEDDIC and a simple version for SMBs

What is a lead qualification framework?

A lead qualification framework is a short, agreed list of criteria that decides whether a lead moves forward, waits or drops out. It replaces gut feeling with the same questions on every deal, so two reps looking at the same account reach the same conclusion.

The framework matters most at the handoffs. An SDR books a meeting, an account executive (AE) runs discovery, and a manager decides what goes into the forecast. Without a shared definition, each person uses a different bar, and the pipeline fills with deals nobody can explain. Predictable Revenue by Aaron Ross and Marylou Tyler makes the same point about specialization: when prospecting and closing are separate jobs, the definition of a qualified lead becomes the contract between them.

A useful framework does three things:

• Filters leads that will not buy, so reps stop spending weeks on them.
• Exposes gaps in a deal that is real but not yet winnable, such as an unknown decision maker.
• Creates data you can review later to learn which criteria actually predict a closed deal.

Qualification starts before the first call. Your ideal customer profile decides which accounts get contacted at all, and the framework decides which conversations are worth continuing.

BANT vs MEDDIC: how do the two frameworks compare?

BANT is a quick four-point check suited to simple, transactional deals. MEDDIC is a six-point map of how a complex organization makes a buying decision. The table shows the difference side by side.

Neither framework is better in general. The right choice depends on deal size, the number of people involved and how long a decision takes. Variants exist for both: MEDDPICC adds paper process and competition to MEDDIC, and CHAMP reorders BANT to start with challenges instead of budget.

When does the BANT framework work, and where does it break?

The BANT framework works when the buyer already knows the problem, the price range is familiar and one person can say yes. It breaks when the buyer has not yet decided that the problem is worth solving.

The four BANT criteria are easy to teach, which is why BANT is often the first framework a new team adopts:

• Budget: is money available or can it be found?
• Authority: is this person the decision maker, or how close are they?
• Need: does the company have a problem you solve?
• Timeline: when do they want it fixed?

The common failure is order. In outbound, the buyer did not ask to talk to you, so many do not have a budget line yet. Asking "what is your budget?" in the first call disqualifies good accounts that would have created budget once they saw the cost of the problem. Authority has a similar trap: in many SMBs the person who feels the pain is not the one who signs, but that person is still the right first contact.

Use BANT as a late check, not a first gate. Confirm need and timing early, then confirm budget and authority once the buyer agrees the problem is worth solving.

When is MEDDIC sales qualification worth the effort?

MEDDIC sales qualification is worth it when a deal involves several stakeholders, a formal evaluation and a cycle measured in months. For a two-person decision made in two weeks, it adds more admin than insight.

MEDDIC shifts the focus from the lead to the buying organization:

• Metrics: the measurable result the buyer expects, such as hours saved or meetings booked per month.
• Economic buyer: the person who controls the money and can approve the purchase.
• Decision criteria: what the buyer will compare vendors on.
• Decision process: the steps, people and dates between interest and signature.
• Identify pain: the business problem and its cost if nothing changes.
• Champion: someone inside who wants the change and will sell it internally.

The strength of MEDDIC is that it shows why a deal is stuck. A deal with strong pain but no champion and an unknown decision process is not "in negotiation", whatever the CRM stage says. The weakness is that SMB teams often try to fill all six fields on a first meeting, which turns discovery into an interrogation.

A simple lead qualification framework for SMB sales teams

For most B2B SMB teams, a four-question lead qualification framework covers what matters: fit, problem, owner and priority. It takes the useful parts of BANT and MEDDIC and drops what a small deal does not need.

1. Fit: does the account match the ICP on size, model and market? This is checked before outreach, then confirmed in the call.
2. Problem: can the buyer describe a specific problem you solve, in their own words, with a cost attached?
3. Owner: who owns the problem, who signs, and are both involved or reachable?
4. Priority: why now? Is there a trigger, a deadline or a target that makes this a top-three issue this quarter?

Each question has three answers: yes, unknown or no. A lead with no "no" and at least two "yes" answers is a qualified meeting. A lead with four "yes" answers is a qualified opportunity. Any "no" on fit or problem ends the deal politely.

Priority often comes from what you saw before the call. A buying signal such as a new sales leader or a hiring push is a hypothesis about priority, and the first call confirms or rejects it.

When a deal grows past three stakeholders or a formal evaluation, add the MEDDIC fields that are missing: decision criteria, decision process and champion. You do not need to choose one framework forever.

Where should qualification happen: SDR, AE or AI agent?

Qualification works best in stages, with each role checking only what it can actually know. An SDR confirms fit and interest, an AE confirms problem, owner and priority, and an AI agent prepares the evidence for both.

• Before outreach: fit is checked against the ICP. An AI agent can research accounts and flag signals, with a person approving the list.
• At reply: the SDR checks that the person is relevant and open to a conversation. Our planning target for well-targeted outbound is an 8-12% reply rate, with about one in three replies becoming a booked meeting, so most of the filtering happens here.
• First meeting: the AE scores problem, owner and priority and records the answers.
• Before forecast: the manager checks that every criterion is "yes" or has a dated next step.

Keep the bar for a booked meeting low enough that SDRs are not running discovery by email. Keep the bar for a forecast opportunity high enough that the forecast means something. A clear handoff rule between the two is part of any first SDR playbook, and it is one of the pieces we set up when we build an outbound sales system.