The complete guide to MEDDPICC, BANT, and SPICED -- the three frameworks that separate high-performing revenue teams from everyone else. No gates, no email walls. Just the playbook.
The average B2B sales team closes between 0% and 0% of the opportunities in their pipeline. That number has stayed stubbornly flat for over a decade, even as companies have invested billions in CRM, outreach tools, and sales enablement platforms. The bottleneck is not activity volume. The bottleneck is qualification.
When a team lacks a rigorous qualification process, the failure mode is predictable: reps spend weeks nurturing deals that were never going to close. They demo for prospects who have no budget authority. They build proposals for committees that have already selected a competitor. According to Forrester, more than 0% of pipeline deals end in "no decisionA deal outcome where the prospect neither buys from you nor a competitor -- they simply stop engaging." -- not a competitor win, not a pricing objection, just a slow fade to nothing. That is the cost of unqualified pipelineDeals in your CRM that lack confirmed qualification criteria -- budget, authority, need, or timeline..
The math compounds quickly. A mid-market AE running 30 active opportunities is typically spending real time -- research, custom demos, proposal drafts, internal reviews -- on at least 15 deals that will never convert. At a blended cost of $150/hour for AE time, that is easily $0 per rep per quarter in wasted effort. Multiply across a 20-person sales floor and you are looking at $0 million annually spent pursuing deals that were dead on arrival.
Qualification is not about gatekeeping. It is not about finding reasons to say no. Effective qualification is a service to the buyer. When you ask sharp, structured questions early in the process, you help the prospect understand whether this is worth their time too. You surface internal blockers they had not considered. You reveal gaps in their buying process before those gaps become deal killers. The best qualification conversations are the ones where the prospect says "I had not thought about that" -- because that moment builds trust and credibility faster than any pitch deck.
The three frameworks in this playbook -- MEDDPICC, BANT, and SPICED -- represent three different philosophies for this same essential discipline. Each is designed for a different selling motion, a different deal complexity, and a different buyer relationship. None of them is universally "best." The right choice depends on your average contract value, your sales cycle length, and the level of organizational complexity in your target accounts. We will walk through all three, compare them directly, and give you a concrete implementation plan to deploy the one that fits.
MEDDPICC is the qualification framework most associated with enterprise sales excellence. Originally developed by Jack Napoli and Dick Dunkel at PTC in the 1990s (as MEDDIC), it was later extended to include Paper Process and Competition -- the two Ps and the C that distinguish modern enterprise selling from mid-market motions. Today it is the standard at companies like Snowflake, MongoDB, and CrowdStrike, where complex buying committees, long procurement cycles, and high ACVs demand rigorous deal inspection.
MEDDPICC works because it forces you to map the entire buying ecosystem, not just the relationship with your primary contact. Each letter represents a dimension of deal health that you need to validate independently. Skipping any one of them creates a blind spot that will surface at the worst possible moment -- usually during a forecast call or, worse, on the day you expected to close.
Metrics are the numbers that justify the investment. Not your product metrics -- their business metrics. This is the ROI case expressed in the buyer's own language: revenue gained, cost reduced, time saved, risk mitigated. Without clear metrics, there is no compelling eventA time-bound business reason that forces the prospect to act now rather than later.. The deal stalls because no one internally can build the business case to justify procurement effort and budget allocation. The best reps co-develop the metrics with the championAn internal advocate with power, access to decision-makers, and personal motivation to see your deal win., using the prospect's own data, so the business case feels like the prospect's idea rather than a vendor pitch.
The economic buyerThe person who can approve budget -- including unbudgeted spend -- and has final sign-off authority on the purchase. is the individual with the authority to sign off on the purchase, including the power to create budget that does not yet exist. This is not always the person with the fanciest title. In many organizations, a VP can approve up to $100K without C-suite involvement. In others, any new vendor requires CFO sign-off regardless of deal size. Your job is to identify exactly who this person is, understand their priorities (which may differ from your champion's), and ensure they see value in your solution before the decision point. Deals without economic buyer access are the single most common reason enterprise deals slip quarter to quarter.
Decision criteria are the specific requirements the buying committee will use to evaluate your solution against alternatives. These fall into three categories: technical criteria (integrations, security, performance), business criteria (ROI, time to value, vendor stability), and personal criteria (career risk, political dynamics, relationship trust). Most reps only uncover the first category. The best reps map all three and ensure their solution is positioned favorably against each. If you discover that the decision criteria favor a competitor, you either need to change the criteria through champion coaching or qualify out.
The decision process is the sequence of events that must happen between today and a signed contract. This includes technical evaluation, security review, legal review, budget approval, executive sign-off, and procurement. In enterprise deals, there are often steps that your champion does not even know about until they encounter them. Mapping the decision process early lets you plan backwards from a target close date and identify the steps most likely to introduce delay. It also signals deal maturity: if your prospect cannot articulate how they make purchasing decisions, they may not be serious enough to close.
Paper processThe legal, procurement, and contractual steps required to get a deal signed -- MSAs, security reviews, vendor onboarding. is the operational reality of procurement. It includes MSA redlining, DPA negotiation, procurement system onboarding (think Coupa, Ariba, or SAP), InfoSec questionnaires, SOC 2 validation, and vendor risk assessments. In large enterprises, paper process alone can add 4 to 8 weeks to a deal cycle -- and that is after the "yes" decision. Reps who ignore paper process will consistently miss close dates. The antidote is to start these workstreams in parallel with the evaluation, not sequentially after it. Ask about procurement timelines in your first meeting, not your last.
Identifying pain is table stakes. Implicating the pain is what separates MEDDPICC from simpler frameworks. Implication means tracing the problem to its downstream consequences -- financial losses, missed targets, team attrition, competitive disadvantage, career risk for the executive sponsor. The deeper the implication, the more urgent the deal becomes. When you can connect a prospect's workflow inefficiency to their board's growth targets, you have created a compelling event that exists independently of your sales cycle. The pain now has organizational gravity.
A champion is not just someone who likes your product. A true champion has three qualities: power (the organizational authority to influence the decision), access (the ability to get you in front of decision-makers), and motive (a personal reason to see this deal succeed -- a promotion, a strategic win, a mandate they own). The champion test is straightforward: will this person sell internally when you are not in the room? Will they fight for your deal when competing priorities arise? If the answer is not clearly yes, you have a coachA friendly contact who shares information but lacks the power or motivation to actively drive the deal internally., not a champion. Coaches provide information. Champions drive action.
Competition in MEDDPICC is not limited to named competitors. It includes the status quo (keep doing what they are doing), internal builds (an engineering team that wants to build a homegrown solution), and alternative budget allocation (spending the money on a different initiative entirely). Understanding the competitive landscape lets you position proactively rather than reactively. You should know who else is in the evaluation, what their perceived strengths are, and where your solution has a defensible advantage. The most dangerous competitor is always "do nothing," because it requires zero effort and zero risk from the buyer.
Complex enterprise deals with multiple stakeholders, long procurement cycles, and ACVs above $50K. If your average deal involves a buying committee of 5+ people and takes 3-9 months to close, MEDDPICC gives you the rigor to inspect and control the process. It is overkill for transactional or self-serve motions.
For a deeper look at how MEDDPICC compares to its predecessor, see our breakdown of MEDDPICC vs MEDDIC and our full What is MEDDPICC guide.
BANT is the oldest and most widely recognized qualification framework in B2B sales, developed by IBM in the 1960s. It is also the most criticized -- often unfairly. BANT gets a bad reputation because it is frequently misapplied to enterprise sales cycles where it does not belong. But for its intended use case -- high-velocity, transactional, and SMB sales motions -- BANT remains remarkably effective precisely because of its simplicity. Four dimensions. Four yes-or-no gates. Fast decisions about where to invest your time.
The criticism of BANT centers on its linear, seller-centric structure. Critics argue that asking about budget before understanding the problem puts the cart before the horse. That is true in consultative selling. But in motions where the buyer already knows what they need, the price point is transparent, and the decision maker is the person on the call, BANT cuts straight to the qualification signals that matter: can they afford it, can they decide, do they need it, and when do they need it by?
Budget in BANT is straightforward: does the prospect have funding approved or accessible for this purchase? In enterprise deals, budget can be created. In SMB and mid-market velocity sales, it usually cannot. If a small business tells you they need to "find budget," that typically means the deal will not happen in the near term. For PLG and self-serve motions, budget qualification is often replaced by pricing page behavior -- if they are on your pricing page comparing tiers, budget intent is implicit.
Authority in BANT is binary: can this person sign the contract, or do they need someone else's approval? In SMB sales, you are often speaking directly with the founder, CEO, or VP who owns the budget and the decision. That is the BANT sweet spot. In larger organizations, the person on your call may be an individual contributor or a manager who can champion but not close. Identifying authority early prevents you from investing in lengthy evaluation cycles with someone who cannot pull the trigger. If they are not the decision-maker, your next question is how to get to the person who is.
Need is the most fundamental qualification criterion. Without a real, felt pain point, no framework will save the deal. In BANT, need assessment is relatively surface-level compared to the deep implication work in MEDDPICC or SPICED. You are looking for confirmation that the prospect has a problem, that the problem is active (not theoretical), and that they are motivated enough to solve it now rather than later. Gartner research shows that 0% of B2B buyers rate their most recent purchase as "very complex or difficult." If you can make the problem and the solution feel simple and clear, you win.
Timeline is the urgency signal. A prospect with budget, authority, and need but no timeline is a deal that will sit in your pipeline for months, consuming forecasting bandwidth without converting. Effective timeline qualification goes beyond "when do you want to start?" and into the reasons behind the urgency: a board mandate, a competitor move, a contract renewal, a new quarter starting, a seasonal spike approaching. When you understand the driver behind the timeline, you can reference it to create natural urgency without applying artificial sales pressure.
SMB and velocity sales motions with ACVs under $25K, sales cycles under 30 days, and single or dual decision-makers. BANT excels in inbound-heavy motions where leads arrive with existing intent and the qualification question is "how fast can this close?" not "how do we navigate a buying committee?" It also works well for SDR-to-AE handoff criteria, where you need a simple, repeatable framework for determining whether a lead is worth an AE's time.
For teams evaluating AI-assisted qualification for high-velocity motions, see our roundup of the best AI SDR tools and how they compare.
SPICED was developed by Winning by Design, a firm that has trained sales teams at over 700 SaaS companies. It reflects a more modern, buyer-centric philosophy than BANT and is less procurement-focused than MEDDPICC. The core insight behind SPICED is that qualification should not feel like interrogation -- it should feel like a diagnostic conversation that naturally surfaces the information both parties need. SPICED structures discovery around the buyer's situation and journey, not the seller's checklist.
What makes SPICED distinctive is its emphasis on the Critical Event -- the external or internal deadline that creates urgency independently of the sales process. Frameworks that rely on seller-created urgency ("we can do a discount if you close this month") produce weak deals. SPICED forces you to find urgency that already exists in the buyer's world, which produces deals with stronger conviction and lower churn risk.
Situation is context-gathering. What does the prospect's business look like today? What tools are they using? How is their team structured? What processes are in place? This is not about finding problems yet -- it is about building an accurate mental model of how the organization works so that everything that follows is grounded in specifics rather than assumptions. The best discovery reps can describe a prospect's current workflow back to them better than the prospect can describe it themselves. That level of understanding builds instant credibility.
Pain in SPICED goes deeper than a surface-level complaint. You are looking for pains that are felt, not just acknowledged. The difference: "Our response time could be better" is acknowledged pain. "We lost three enterprise deals last quarter because we took 48 hours to respond to demo requests and the prospect went with the vendor who replied in two hours" is felt pain. Felt pain creates urgency. Acknowledged pain creates interest. You need urgency to close deals reliably.
Impact quantifies the pain. If the pain is "we are losing deals because of slow response times," the impact is the revenue left on the table, the increase in CACCustomer Acquisition Cost -- the total sales and marketing spend divided by the number of new customers acquired., the decline in win rate, the effect on team morale and attrition. Impact is what turns a tactical conversation into a strategic one. When you can articulate the impact in the buyer's language -- tied to their KPIs, their board metrics, their OKRs -- you have built a business case that sells internally even when you are not in the room. Impact is also where you establish the value benchmark that makes your pricing feel reasonable: if the impact is $500K/year, a $50K solution is an obvious yes.
The critical event is the single most important qualification signal in SPICED. It is the answer to "why now?" that does not depend on sales pressure. Critical events include: a contract renewal with an existing vendor, a board meeting where the CRO needs to present pipeline improvements, a new product launch that requires scaled lead handling, a competitor entering the market, a new fiscal year with fresh budget, or a mandate from the CEO. The critical event creates a natural deadline that pulls the deal forward. Without one, deals default to the prospect's natural pace, which is almost always slower than what you need for accurate forecasting.
The economic buyer in SPICED carries the same definition as in MEDDPICC: the individual who can approve, accelerate, or kill the deal. In consultative, mid-market sales, the economic buyer is often one or two levels above your primary contact. What SPICED adds is an emphasis on understanding the economic buyer's priorities, which may be different from your champion's. The VP of Sales cares about pipeline coverage. The CFO cares about payback period. The CEO cares about strategic differentiation. You need to speak to whoever is holding the budget in the language of their priorities, not your champion's.
Decision in SPICED encompasses both the criteria used to evaluate options and the process used to reach a conclusion. This combines MEDDPICC's separate Decision Criteria and Decision Process into a single, more conversational dimension. The goal is to understand who is in the evaluation, what they are comparing, and how the final decision will be made. Is it consensus-driven? Does one person have veto power? Is there a formal RFP, or will the decision emerge from an informal conversation? Knowing this lets you tailor your approach: a consensus-driven committee needs broad stakeholder alignment, while a single decision-maker needs a tight executive summary.
Consultative, solution-selling, mid-market motions with ACVs from $15K to $80K, sales cycles of 1-4 months, and 2-5 stakeholders. SPICED is ideal when the buyer relationship matters as much as the deal mechanics -- when you need to build trust and demonstrate expertise throughout the sales process, not just check boxes. It is the framework of choice for teams that sell through discovery and value articulation rather than feature comparison.
For scoring configuration specific to SPICED, check the frameworks documentation and scoring setup guide.
No single framework is universally best. The right choice depends on your selling motion, deal complexity, and team maturity. Here is how the three frameworks stack up across the dimensions that matter.
| Dimension | MEDDPICC | BANT | SPICED |
|---|---|---|---|
| Best for | Enterprise, complex sales | SMB, velocity, transactional | Mid-market, consultative |
| Ideal ACV | $50K+ | Under $25K | $15K -- $80K |
| Sales cycle | 3 -- 9+ months | Under 30 days | 1 -- 4 months |
| Number of criteria | 8 | 4 | 6 |
| Stakeholders | 5 -- 15 (buying committee) | 1 -- 2 (decision-maker on call) | 2 -- 5 (small committee) |
| Complexity | High -- requires significant training and management reinforcement | Low -- can be learned and applied in a single session | Medium -- intuitive flow but requires practice to do well |
| Key strength | Deal control and forecast accuracy through comprehensive buyer mapping | Speed and simplicity; fast disqualification of unfit leads | Buyer-centric discovery that builds trust and uncovers urgency naturally |
| Key weakness | Can feel like a checklist interrogation if applied mechanically; overkill for simple deals | Too shallow for complex deals; does not map buying committees or procurement | Less prescriptive on procurement and competitive mapping; relies on rep skill |
| Adoption difficulty | High -- needs CRM customization, deal reviews, and ongoing coaching | Low -- most reps already know the acronym | Medium -- requires discovery skill development and roleplay practice |
| Forecast impact | Very high -- the most predictive framework when implemented rigorously | Moderate -- good for pipeline velocity, less useful for deal-level prediction | High -- strong urgency signals (Critical Event) improve forecast timing |
Many organizations use a hybrid approach: BANT for initial SDR qualification and lead routing, then MEDDPICC or SPICED for AE-led discovery and deal progression. This gives you speed at the top of the funnel and rigor in the middle. The key is to define clear handoff criteria so both teams know exactly what "qualified" means at each stage.
Frameworks fail not because the models are wrong but because the execution breaks down. These are the six most common failure modes we see in sales organizations that have adopted a qualification framework but are not getting the results they expected.
Running frameworks as interrogation checklists. The rep fires through MEDDPICC questions like a survey, ticking boxes without listening to the answers. The prospect feels like they are being processed, not consulted. Trust erodes. Information quality drops because the prospect starts giving short, guarded answers.
Train your team to use frameworks as conversation maps, not scripts. Each MEDDPICC or SPICED element should emerge naturally from discovery. The prospect should never feel like they are being qualified -- they should feel like they are having a valuable diagnostic conversation with an expert who understands their world.
Qualifying too late in the process. The rep runs a full demo, invests in a custom proposal, involves a solutions engineer -- and only then asks basic qualification questions. By that point, the rep is emotionally and professionally invested in the deal and will rationalize poor qualification signals to justify the effort already spent.
Qualification happens before the demo, not after. The first substantive conversation with any prospect should be a discovery call that covers enough qualification criteria to decide whether the deal deserves a demo. This is not about gatekeeping -- it is about ensuring the demo is tailored to what actually matters, which also makes the demo more effective.
Accepting vague answers as qualification data. "We have budget" becomes a green checkbox. "My boss is supportive" becomes confirmed economic buyer access. "We need to move quickly" becomes a defined timeline. Each of these is an assumption that will fail under pressure during deal review or forecast inspection.
Require specificity for every qualification criterion. Budget means a named dollar amount or budget line. Authority means a named person with their title and approval threshold. Timeline means a specific date with a specific business driver. Train managers to push back on vague qualification data during deal reviews.
Failing to re-qualify as deals evolve. A deal qualified in January may not be qualified in March. Budgets get cut. Champions leave. Priorities shift. New competitors enter the evaluation. The organization restructures. Treating qualification as a one-time event at the beginning of the sales cycle means you are making decisions based on stale data for the rest of the deal.
Build re-qualification checkpoints into your deal stages. At minimum, re-qualify after every major milestone: post-demo, post-proposal, pre-negotiation, and any time there is a material change in the account (reorg, leadership change, budget cycle). Update your CRM fields -- do not just check the box once and forget it.
Only qualifying the champion, not the economic buyer. Your champion says all the right things. They are enthusiastic, responsive, and actively driving the evaluation forward. But you have never spoken to the person who actually controls the budget. When the deal reaches the approval stage, the economic buyer has questions, objections, or priorities that were never addressed.
Establish direct access to the economic buyer as a non-negotiable stage gate. If you cannot get a 15-minute conversation with the budget holder by the time you deliver a proposal, the deal should be downgraded in your forecast. Coach your champion to facilitate this meeting, and provide them with an agenda that addresses the economic buyer's priorities specifically.
Treating "no decision" as bad luck rather than a qualification failure. When a deal dies to "no decision," most teams blame timing, budget cuts, or external factors. But in the vast majority of cases, "no decision" is a symptom of insufficient qualification: no compelling event was established, the pain was not implicated deeply enough, or the champion did not have the organizational power to push through.
Conduct post-mortems on every "no decision" deal against your qualification framework. Which criteria were confirmed with specifics, and which were assumed? Over time, this analysis will reveal your team's blind spots and inform targeted coaching. Most teams find that 2-3 specific criteria are consistently weak -- focus there.
For decades, qualification has been a manual process. A rep gets on a call, asks a structured set of questions, takes notes, updates the CRM, and scores the deal. The quality of the output depends entirely on the skill of the individual rep, and the data is only as good as what the prospect is willing to share in a 30-minute meeting scheduled for some time next Tuesday.
AI is fundamentally reshaping this model in three ways.
Traditional qualification happens on a human schedule. A lead comes in, an SDR reviews it within 24-48 hours, books a discovery call for next week, and qualification begins. By that point, the prospect's urgency may have cooled, they may have already engaged a competitor, or they may have moved on entirely. Research from Harvard Business Review found that firms that responded to leads within one hour were nearly 0x more likely to have a meaningful conversation with a decision-maker than firms that waited even 60 minutes longer. AI qualification happens in the moment -- when the visitor is on your website at 11pm on a Sunday, when the buyer is actively researching, when the intent signal is at its peak. That timing advantage compounds across every deal in your pipeline.
In a manual model, qualification data is captured in discrete events: the discovery call, the demo follow-up, the proposal review. Between these events, the buyer may have dozens of interactions with your content, your website, and your team that go uncaptured. AI systems can extract qualification signals from every touchpoint -- a pricing page visit, a support question, a chatbot conversation, a content download. This creates a continuous qualification signal rather than a point-in-time snapshot, which is more accurate and more current than anything a human rep can maintain in a CRM.
The biggest operational challenge with qualification frameworks is not adoption -- it is consistency. When 20 reps are each running MEDDPICC discovery, you get 20 different interpretations of what "confirmed" means for each criterion. Some reps are rigorous. Others check the box based on hope. AI qualification applies the same rubric to every conversation, producing structured, scoreable output that makes pipeline reviews objective rather than subjective. The result is forecast accuracy that improves not just for the best reps, but for the entire team.
The shift is not about replacing reps. The best sales teams will use AI as the first pass -- qualifying at the moment of intent, across every channel, with consistent rigor -- and then deploy their experienced reps against the opportunities that are already understood and scored. Tools like Kilo run MEDDPICC, BANT, and SPICED qualification through natural AI conversations -- so your reps get a scored brief before the first call. That means every human conversation starts further along in the deal cycle, and no high-intent visitor slips through because the team was asleep.
For a broader look at the AI SDR landscape, see our guide to AI SDR tools and comparisons against Drift and Intercom.
Choosing a framework is the easy part. Embedding it into your team's daily operations is where the real work begins. Here is a step-by-step timeline for rolling out a qualification framework that actually sticks.
Audit your deal data from the last four quarters. What is your average ACV? How many stakeholders are involved in a typical deal? What is your average cycle length? Use the comparison table to select the framework that matches your motion. If you sell across multiple segments, you may need different frameworks for different deal sizes -- and that is fine.
For each criterion in your chosen framework, write a clear definition of what constitutes a confirmed green flag versus an unconfirmed assumption. "Budget: confirmed" should mean a specific dollar amount tied to a budget line, not "they said money is not an issue." Document these definitions and make them the shared language for your entire revenue team -- SDRs, AEs, and managers.
Create custom fields for each qualification criterion at the opportunity level. Make them required at specific deal stages so reps cannot advance a deal without confirming qualification data. Add a composite qualification score that rolls up across all criteria. This is the backbone of your pipeline reviews -- without CRM integration, the framework lives in reps' heads and dies in forecast calls.
Run a half-day training session where the team qualifies their current pipeline using the new framework. Take two live deals per rep and walk through every criterion as a group. This surfaces gaps immediately -- deals they thought were qualified turn out to have missing criteria, and deals they were about to abandon turn out to have strong signals they had overlooked. Roleplay discovery calls using the framework questions with managers playing the prospect.
Qualification frameworks die when managers stop inspecting against them. Dedicate the first 15 minutes of every pipeline review to framework-based deal inspection: pick two or three deals and go criterion by criterion. Ask "what evidence do we have?" for each. This creates accountability and keeps the framework alive after the initial training buzz fades. Within six weeks, the framework language should be the default vocabulary in every pipeline conversation.
After one full quarter on the framework, analyze the data. Compare win rates for fully qualified deals versus partially qualified deals. Look at the correlation between specific criteria (Champion confirmed vs. not, Critical Event identified vs. not) and deal outcomes. Adjust your scoring weights based on which criteria are most predictive for your specific motion. Share the data with the team -- nothing reinforces adoption like seeing proof that the framework predicts their success.
Kilo runs MEDDPICC, BANT, and SPICED on your website visitors -- automatically. Every conversation qualifies, every lead gets scored, and your reps get a brief before the first call.
Start free trial →