Conversion & funnel optimisation

Lead qualification frameworks, compared. BANT, MEDDIC and CHAMP, and when to use each.

Lead qualification decides whether a prospect is worth pursuing before they enter serious pipeline. BANT (Budget, Authority, Need, Timeline) suits fast, simple sales cycles. MEDDIC suits longer, multi-stakeholder enterprise deals. CHAMP leads with the prospect's problem instead of budget. Most teams end up using a hybrid of two.

The short answer. Qualification decides where effort goes.

Lead qualification is the filter that separates prospects with a genuine need, budget, authority and timeline to buy from those who are early, unfunded, or simply browsing. Get it wrong and a sales team spends weeks chasing deals that were never going to close, while genuinely ready buyers wait for a follow-up call that keeps slipping down the list.

Poor qualification is not a minor efficiency problem. Gartner's B2B buying research has repeatedly found that buyers spend only around 17% of their total purchase journey actually meeting with potential suppliers, split across every vendor they are considering. A sales team that burns a chunk of that limited window on a prospect who was never qualified to buy is losing time it will not get back with the buyers who were.

How it works in practice. The three frameworks.

BANT, developed at IBM decades ago and still in wide use, asks four questions: does the prospect have Budget, are we speaking to someone with Authority to decide, is there a genuine Need, and is there a realistic Timeline. Its strength is speed. A rep can run through BANT in a first call and know within minutes whether a deal deserves further time. Its weakness shows up in longer, more complex sales: BANT has no mechanism for identifying an internal champion or mapping a multi-person decision process, so it can wrongly qualify a deal that has an enthusiastic single contact but no real path to a signed contract.

MEDDIC goes further: Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, and Champion. It was built for enterprise software sales, where a deal can involve a dozen stakeholders and take the better part of a year, and its extra rigour is exactly what closes that gap in BANT. Confirming there is a real internal champion, and understanding the formal decision process rather than just the stated timeline, catches deals that look promising on the surface but have no realistic route to a yes. The cost is time and training: MEDDIC takes longer to run properly and asks more of a rep's discovery skill than a four-letter checklist does.

CHAMP flips the order: Challenges, Authority, Money, Prioritisation. Instead of opening with budget, it opens with the prospect's actual problem, which suits consultative selling where the challenge needs uncovering before price is even a sensible question to ask. A prospect who has not yet articulated their problem clearly is not ready for a budget conversation, and CHAMP's ordering respects that, at the cost of being slower to reach a hard qualify or disqualify decision than BANT.

What good looks like. Matching the framework to the deal.

FrameworkBest suited toMain gap
BANTShort, simple, lower-value sales cyclesNo champion or decision-process mapping
MEDDICLonger, multi-stakeholder enterprise dealsSlower to run, needs skilled discovery
CHAMPConsultative, problem-led sellingSlower to reach a hard qualify decision

None of the three is universally correct, and the deal type should decide which one leads. A founder-led team selling a lower-priced, single-stakeholder product does most of its qualifying in the first call and gets little extra value from MEDDIC's full checklist. The same team, if it starts selling into larger accounts with a formal procurement process, will find BANT alone starts missing deals that stall for reasons a champion-focused framework would have caught months earlier. The right move is usually a hybrid: a fast BANT-style filter for the first conversation, with the champion and decision-process questions from MEDDIC layered in once a deal moves into serious, multi-stakeholder evaluation. This is the same logic behind mapping out conversion rate optimisation properly, matching the depth of the process to the actual complexity of the decision, rather than applying one standard checklist to every lead regardless of size.

Pitfalls to avoid. Where qualification goes wrong.

The first pitfall is applying a heavy framework to every lead regardless of deal size. Running a full MEDDIC discovery on a small, single-stakeholder deal slows the process down for both sides and can read as over-engineered to a buyer who just wants a straightforward answer.

The second is treating qualification as a one-time gate rather than an ongoing check. A deal that was genuinely qualified at first contact can stop being qualified two months later if the champion leaves the company, the budget gets reallocated, or a new decision-maker joins the process with different priorities. Re-qualifying at each major stage, not just at the start, catches this before a deal quietly becomes dead weight in the pipeline, which is exactly the kind of drag that shows up when reviewing what a healthy sales pipeline actually looks like.

The third is confusing enthusiasm with authority. A single, highly engaged contact who loves the product is not the same as a confirmed decision-maker or a mapped buying committee, and every one of these frameworks exists precisely to catch that distinction before a rep spends months building a relationship with someone who was never going to be the one signing the contract.

The fourth is skipping qualification altogether under pressure to fill the top of the pipeline. It is tempting, especially early in a quarter, to count every inbound enquiry as an opportunity. The frameworks above exist to stop that instinct, because a pipeline padded with unqualified leads costs more in wasted sales time than it ever returns in reported coverage.

A practical example. The same lead, run through two frameworks.

Take an inbound enquiry from a 40-person operations manager at a mid-market logistics firm. Run through BANT on the first call, the rep confirms a rough budget range, gets a straight answer on timeline, hears a clear need described, and notes that the contact does not have final sign-off, procurement does. On four of four counts BANT gives a soft yes, and a fast-moving team would reasonably book a demo and move the deal to the next stage.

Run the same call through MEDDIC and a gap appears immediately: there is no confirmed economic buyer, no visibility into the formal decision process procurement will run, and no identified champion inside the business willing to advocate once the rep is no longer in the room. None of that means the deal is dead. It means the deal is BANT-qualified but MEDDIC-incomplete, and the next two calls should be aimed squarely at closing that gap, securing an introduction to the economic buyer and identifying who inside the business actually wants this to happen, rather than proceeding straight to a demo as if the deal were fully qualified.

This is precisely the pattern a hybrid approach is built to catch. A team using BANT alone would have booked the demo and only discovered the missing champion and unclear decision process weeks later, once the deal stalled in "evaluation" for no obvious reason. A team using the hybrid correctly treats the BANT pass as permission to keep going, not confirmation that the deal is fully qualified, and uses the MEDDIC gaps as the actual agenda for the next conversation.

The same logic applies in reverse for a CHAMP-led conversation. A prospect who opens by describing a specific operational challenge, rather than asking about price, is signalling that the conversation needs to stay on the problem before it moves to budget. Jumping straight to a BANT-style budget question in that first call risks shutting down a prospect who has not yet framed their own problem clearly enough to discuss cost, and loses information a slower, challenge-first conversation would have surfaced. Matching the order of questions to how the prospect is actually engaging, not just to which framework the team defaults to, is what separates qualification that closes deals from qualification that simply fills in a form.

Disqualifying without burning the relationship. The half of qualification most guides skip.

Every qualification framework spends most of its attention on what a qualified lead looks like and very little on how to say no well. That is a mistake, because the majority of leads any founder-led team sees will not qualify, and how that "not now" conversation is handled affects whether the prospect ever comes back once their situation changes. A blunt "you're not a fit" ends the relationship. A specific, honest explanation of what is missing, whether that is budget, a confirmed champion, or a clear enough problem statement, keeps the door open and often produces a better-qualified re-approach six or twelve months later.

The clearest signal that a lead should be disqualified rather than nurtured further is usually a mismatch on need, not on budget or timeline. A prospect with a genuine problem but no budget this quarter is a nurture candidate; a prospect who cannot describe a problem the product actually solves, no matter how enthusiastic the conversation, rarely becomes a customer regardless of how long a rep keeps the deal open. Recognising that distinction early, and being willing to close a deal as disqualified rather than leaving it to age quietly in the pipeline, is what keeps a qualification framework doing its job instead of becoming a formality everyone works around.

Common questions.

What is lead qualification?

Lead qualification is the process of deciding whether a prospect is worth a sales team's time, based on whether they have a genuine need, the budget and authority to buy, and a realistic timeline. It happens before a deal enters serious pipeline, so effort goes toward prospects who can actually become customers.

What is the difference between BANT and MEDDIC?

BANT (Budget, Authority, Need, Timeline) is a quick checklist suited to shorter, simpler sales cycles. MEDDIC (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion) is a deeper framework built for longer, multi-stakeholder enterprise deals, and its extra rigour around the economic buyer and champion is what BANT misses.

Is CHAMP better than BANT?

CHAMP (Challenges, Authority, Money, Prioritisation) leads with the prospect's problem rather than their budget, which suits consultative selling where the challenge needs uncovering before price is even relevant. It is not universally better than BANT, it fits a different conversation: problem-first rather than checklist-first.

Which framework should a founder-led team use?

Most founder-led B2B teams do well starting with a lightweight BANT-style filter for the first call, then layering in the champion and decision-process questions from MEDDIC once a deal moves into a serious, multi-stakeholder evaluation. Running the full MEDDIC checklist on every inbound enquiry usually slows the process down more than it helps.

Can you use more than one qualification framework at once?

Yes, and it is common practice. A hybrid approach, using a fast framework for initial screening and a deeper one once a deal reaches serious evaluation, is the pattern used by most established B2B SaaS revenue teams, since no single framework covers both a five-minute discovery call and a nine-month enterprise cycle equally well.

Not sure which framework fits your sales process? Let's work it out.

Get in touch and we'll build a qualification process matched to your actual deal sizes and buying committees, not a generic checklist copied from an enterprise playbook.

Let's talk