Lead qualification framework: BANT, MEDDIC, and when each fits
A practical walkthrough of the major lead qualification frameworks. What BANT, MEDDIC, SPICED, and GPCT actually do, and how to pick without copying someone else's playbook.
Pick any sales methodology and you will find a framework that promises to tell you whether a lead is worth pursuing. BANT. MEDDIC. SPICED. GPCT. CHAMP. ANUM. Each one is defensible, each one is marketed by someone with a book to sell, and each one works for a specific motion and fails for others.
This post is a plain-language walkthrough of the major lead qualification frameworks: what each one is, when it fits, and how to pick without copying someone else’s playbook.
Why framework choice matters
Lead qualification does two jobs:
- Decide whether to pursue. You have finite rep hours. The framework helps you spend them on leads that will close.
- Decide what to work on inside the deal. Once you decide to pursue, the framework tells you what information you still need before you can forecast confidently.
A framework that fits your motion makes those decisions fast and consistent across reps. A framework that does not fit your motion creates friction, slows down reps, and produces qualification data that nobody uses.
The right framework is the one that matches your buyer’s actual decision process. Everything else is theater. Industry benchmarks suggest cross-industry MQL-to-SQL conversion sits around 13%, with B2B SaaS at 18-22% and top-performing teams at 35-40%; the gap between those is almost always explained by qualification discipline.
The six frameworks worth knowing
BANT (Budget, Authority, Need, Timeline)
The oldest and simplest. Developed within IBM in the 1960s for enterprise sales. BANT asks: does the buyer have budget, is this person the decision-maker, do they have a real need, and do they have a timeline?
Fits: Simple transactional sales with clear decision-makers and defined budgets. Legacy enterprise sales motions. Teams where “qualified” means “has money, has pain, has authority, has a deadline.”
Fails: Modern B2B SaaS, where the buyer committee is 5-10 people, budget often does not exist until the buyer builds a case for it, and the “decision-maker” is a committee rather than a single person. BANT applied strictly to modern SaaS disqualifies 80% of real deals that would close.
MEDDIC (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion)
Developed at PTC in 1996 by Dick Dunkel and Jack Napoli for enterprise software sales. MEDDIC is more detailed than BANT and reflects a world where decisions are committee-based. It asks: what quantified metrics does the buyer care about, who writes the check, how do they decide, what is the formal process, what is their pain, and do you have an internal champion?
Fits: Mid-market and enterprise B2B SaaS with multi-stakeholder deals, formal RFP or procurement processes, and 6+ figure ACVs. Teams where qualification depth matters because deals take 6+ months.
Fails: Small business or self-serve motion, where the decision maker is also the user and the “formal process” is a Stripe checkout.
MEDDPICC (MEDDIC + Paper Process + Competition)
A MEDDIC extension that adds explicit tracking of the paper process (procurement, legal, security review) and competitive landscape. Reflects the reality that in enterprise deals, the paper process is often the longest stage and the competition shapes how the champion sells internally.
Fits: Enterprise SaaS with heavy procurement overhead. Deals where losing to a competitor is a real risk and the champion needs ammunition.
Fails: Transactional sales where paper process is a signature and competition is not a factor.
SPICED (Situation, Pain, Impact, Critical Event, Decision)
A newer framework from the Winning by Design playbook, built for modern SaaS. SPICED emphasizes buyer impact and critical events rather than budget and authority. It asks: what is the current situation, what pain does it cause, what is the impact if unsolved, is there a critical event forcing action, and how will the decision be made?
Fits: Modern B2B SaaS, especially outbound-heavy motions where you are helping the buyer discover pain they had not quantified yet. Teams running consultative sales where the buyer committee shape is fluid.
Fails: Teams that need rigor on budget and authority because they sell into procurement-heavy environments.
GPCT (Goals, Plans, Challenges, Timeline)
Developed by HubSpot and reflects the inbound sales motion. GPCT asks: what are the buyer’s goals, what are their current plans to achieve them, what challenges are blocking them, and what is the timeline for solving the challenges?
Fits: Inbound sales motions where the buyer has done research before talking to a rep. HubSpot’s own customer base is largely in this shape, which is why they developed the framework.
Fails: Outbound-heavy motions where you are creating demand rather than responding to it. The buyer in outbound often does not have formed goals or plans yet.
CHAMP (Challenges, Authority, Money, Prioritization)
A BANT reorder for modern sales. Starts with the buyer’s challenges (pain) rather than their budget, which better reflects how modern buyers actually think.
Fits: Teams that found BANT too mechanical but like its simplicity. Mid-market SaaS with a defined ICP and reasonably standard sales process.
Fails: Very similar failure modes to BANT. CHAMP is better than BANT but shares the same category.
How to pick
Three questions decide which framework fits:
1. How many stakeholders are in a typical deal?
- One (self-serve, SMB founder-sold): BANT or CHAMP are overkill, use a lightweight qualification checklist
- Three to five (mid-market): CHAMP or SPICED
- Six or more (enterprise): MEDDIC or MEDDPICC
2. Is your sales motion inbound-led or outbound-led?
- Inbound (buyer finds you): GPCT or SPICED
- Outbound (you find the buyer): MEDDIC or SPICED, depending on deal size
- Mixed: pick one and standardize across the team
3. How formal is the buyer’s decision process?
- Informal (buyer decides, writes a check): BANT or CHAMP
- Semi-formal (committee, some process): SPICED or GPCT
- Formal (procurement, legal, security review): MEDDPICC
Match the framework to the motion. If your motion changes (e.g., you move upmarket into enterprise), the framework changes with it.
The common mistake
Teams adopt a framework they read about on LinkedIn or heard from an advisor who ran a different kind of business. MEDDIC is popular right now because enterprise B2B SaaS leaders love it. If you are a 10-person SMB CRM selling $5K deals to founders, forcing MEDDIC on your reps will slow them down and lose deals.
The right framework is the one that matches your buyer’s actual decision process, not the one your industry currently fetishizes.
How a CRM supports the framework
The framework lives in your CRM through custom fields on the opportunity record. Each framework element becomes a field (MEDDIC’s “Economic Buyer” field, SPICED’s “Critical Event” field) that reps fill in as they learn.
Three capabilities matter in a CRM supporting a qualification framework:
- Custom fields on every tier. You should be able to add framework fields without a tier upgrade. If “add custom field” requires Enterprise, your qualification data is gated behind pricing.
- Required-field enforcement at stage transitions. The deal should not move from “Qualified” to “Proposal” unless the framework fields are filled. Otherwise reps skip qualification and the forecast is noise.
- Reporting on framework data. Reports that show which deals are missing framework fields, which reps are consistently qualifying thoroughly, and which framework fields correlate with won vs lost deals.
If your CRM supports those three, the framework becomes operational rather than aspirational.
How Strkr supports qualification frameworks
Strkr’s custom objects and fields are available on every paid tier, so you can add framework fields without a pricing conversation. Required-field logic at stage transitions is built into the no-code flow builder, so a flow can block a stage move if critical qualification fields are blank. Reports on qualification data are built like any other formula report, available on every tier.
The design target: whatever framework your team adopts, Strkr should hold the data cleanly and enforce the discipline automatically.
Related reading: How to choose a CRM: a practical buying framework walks through the broader buying question, and the CRM product overview covers how custom fields and required-field logic are set up in Strkr.
Conclusion
Pick the qualification framework that matches your buyer’s actual decision process. BANT for simple transactional sales. MEDDIC for enterprise. SPICED for consultative modern SaaS. CHAMP for mid-market. GPCT for inbound-heavy.
Whatever framework you pick, make it operational: custom fields in the CRM, required at stage transitions, surfaced in reporting. A framework that lives only in a sales enablement deck is a framework that does not exist.