SaaS Sales Qualification Frameworks: When BANT, MEDDIC, SPICED, and ANUM Each Apply — and Where Each Breaks Down

Every SaaS sales team has a qualification framework. Most of them inherited it — from a previous VP, baked into the CRM setup, or carried in from a training program designed for a different selling environment. This piece covers how the four major frameworks work, where each one fails, and how to build a hybrid model that incorporates the behavioral product data most frameworks were not designed to use.

What a Sales Qualification Framework Actually Does

A sales qualification framework is a structured method for determining whether a prospect has the characteristics that predict conversion and retention. A framework is not a checklist to complete before advancing a deal — it is a model that describes the pattern of qualified accounts so reps can recognize that pattern efficiently, early enough to act on it.

Each major framework was built for a specific selling environment. BANT was developed by IBM for transactional hardware and software sales when budgets were discrete and buying committees were small. MEDDIC emerged at PTC for high-value enterprise technology sales with long evaluation cycles and distributed decision authority. The frameworks that dominate modern SaaS were mostly inherited from enterprise software, then adapted — with varying degrees of success — to the subscription model.

The Four Frameworks: What Each One Gets Right

The four major frameworks each capture a different slice of the buyer qualification picture. None is complete in isolation — each is a useful lens on a particular aspect of deal quality, and applying any one of them alone will leave the others' signals uncaptured.

BANT: Budget, Authority, Need, Timeline

BANT asks four questions: Does the prospect have budget? Are you talking to someone with authority to approve the purchase? Do they have genuine need? Do they have a timeline? All four yes: the deal advances. Any no: the deal stalls or goes to nurture.

BANT was effective in the environment it was designed for: transactional hardware sales with clear budget cycles and identifiable budget holders. Filtering for confirmed budget at first contact made sense when buyers arrived with approved capital allocations.

Where BANT breaks in modern SaaS is at the budget step. Budget is rarely confirmed before need is established. The prospect needs to understand what the product does and whether it solves their specific problem before finance approves the spend. Filtering on confirmed budget at top of funnel means disqualifying the accounts that would become best customers given a proper evaluation.

The authority criterion has the same structural problem. In modern enterprise buying, authority is distributed. The economic buyer, the champion, the IT security reviewer, the legal team reviewing the MSA — they each hold veto power over different aspects of the deal. "Are you talking to the decision maker?" is the wrong question. The right question is: who are all the people whose absence from the conversation creates deal risk?

MEDDIC: Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion

MEDDIC is the qualification standard for complex enterprise SaaS. It shifts the question from "does this buyer want to buy?" to "do we understand this buying organization well enough to win this deal?" Six components: Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, and Champion.

The Champion criterion is where MEDDIC captures something the other frameworks miss entirely. A deal without a champion — an internal advocate with organizational credibility and a personal stake in the outcome — stalls after the demo and never gets picked up again. Identifying whether a champion exists is a better predictor of deal velocity than any of the other MEDDIC criteria.

"MEDDIC is not a qualification framework — it's a map of a buying organization. The reps who use it well aren't collecting data for the CRM. They're building a picture of the internal dynamics that will determine whether their deal closes or dies in committee."

— Jack Napoli, co-creator of MEDDIC at PTC, in an interview with Sales Assembly

MEDDIC's limitation is resource cost. For enterprise deals with ACV above $50,000 and sales cycles longer than six months, the time investment is justified. For mid-market deals at $10,000–$30,000 ACV, the qualification process often takes longer than the sales cycle itself.

SPICED: Situation, Pain, Impact, Critical Event, Decision

SPICED was developed by Winning by Design for subscription-revenue SaaS businesses. Its emphasis on Impact and Critical Event addresses two gaps that both BANT and MEDDIC leave open: the economic case for buying, and the urgency driver that creates a real timeline.

Situation captures the current state of the prospect's business as a baseline for understanding what change they are trying to achieve. Pain is the specific obstacle preventing that change. Impact quantifies the economic consequence — "We have a problem with our data pipeline" is pain; "We lose an estimated $200,000 per quarter in engineering time to manual data reconciliation" is impact. The rep who can quantify impact has a materially stronger economic case than one who can only describe the category of pain.

Critical Event is what most distinguishes SPICED. A critical event is a specific, time-bounded trigger in the prospect's world — a product launch, a board review, a regulatory deadline. Without one, timelines are soft and deals drift. With one, urgency is real because it is anchored to something external to the sales process.

SPICED is particularly effective for mid-market SaaS where churn is a material revenue risk. A rep who fully completes SPICED has collected enough context to hand off a well-qualified account to the customer success team — not just a deal that closed.

ANUM: Authority, Need, Urgency, Money

ANUM reorders BANT to correct its most significant sequencing error. By leading with Authority rather than Budget, ANUM ensures reps verify they are talking to someone who can advance the purchase before developing the economic case. Budget — renamed Money — moves to last, where it belongs after need and urgency are established.

ANUM was designed for inbound-heavy motions where prospects arrive after engaging with content or signing up for a trial. Need is partially self-qualified before the first conversation — the prospect reached out because they believe they have the problem your product solves. ANUM verifies that the person who reached out can actually influence the purchase decision, not just that they experience the pain.

Its limitation mirrors BANT's: it is entirely conversation-based. In a PLG motion where trial users generate behavioral signals before any rep conversation, both BANT and ANUM leave that data on the table.

Sales Qualification Framework Comparison

The table below compares the four frameworks across the dimensions that matter most when choosing which one to implement — or which elements to combine in a hybrid model.

Why BANT Fails in Modern SaaS — The Structural Problem

Three structural mismatches explain why training reps to use BANT more rigorously does not fix the problem.

The budget assumption. BANT treats budget as a pre-existing condition. In SaaS, budget is typically created through discovery — prospects establish the business case before finance approves the spend. Filtering on confirmed budget at top of funnel disqualifies the accounts that would become best customers given a proper evaluation.

The authority assumption. "Are you the decision maker?" has a single-person answer embedded in it. In Gartner's B2B buying research, the typical enterprise technology purchase involves 6 to 10 stakeholders. The BANT authority check catches one name and misses the buying committee.

The timeline assumption. A timeline without a critical event is a stated hope, not a constraint. BANT records the stated date without questioning whether it is real.

The MEDDIC Advantage for Enterprise — and Its Limits

MEDDIC outperforms other frameworks in complex enterprise sales because it maps the buying organization, not just the buyer's intent. The deal is won or lost inside the prospect's organization before the rep is fully aware of it. MEDDIC makes those internal dynamics explicit qualification requirements: who holds the budget, what criteria the committee will use, how decisions get made, who is the internal champion.

The Champion criterion is the most predictive element and the one most often skipped. A champion is not the enthusiastic contact on the call. A champion has organizational influence, can explain your value proposition internally without you in the room, and has a personal stake in the evaluation outcome. That combination is the strongest single predictor of deal closure in enterprise sales.

MEDDIC's limit is practical. Completing a full qualification on a $15,000 ACV deal takes more rep time than the deal is worth. The process pencils out on $120,000 enterprise deals; on $15,000 mid-market deals, qualification overhead consumes rep time faster than it generates revenue.

Trial Usage Is the Highest-Signal Qualification Data in PLG Motions

In a product-led growth motion, the product answers the qualification question before any discovery conversation occurs. What the trial user does — which features they activate, how often they return, whether they invite teammates — is a direct behavioral signal of fit, intent, and organizational need. Observed behavior is more reliable than self-reported intent.

Three behavioral signals have the strongest correlation with trial-to-paid conversion:

• Feature breadth: the number of distinct capabilities the trial user has activated. Single-feature trial users are browsing; multi-feature trial users are evaluating.
• Team expansion: whether the trial user has invited colleagues. A multi-user trial has already demonstrated organizational need — someone told a colleague this was worth trying. That single signal answers BANT's "need" criterion more reliably than anything a prospect can say on a call.
• Return session frequency: how many times the trial user returns within the trial window. Return frequency is a direct proxy for perceived value during the trial period.

The discovery call in a PLG motion should not begin the qualification conversation — it should continue one the product already started. A rep who enters a call knowing which features the prospect has activated, how many team members are in the account, and how many sessions have occurred in the past two weeks is not gathering qualification data. They are confirming it and identifying the next friction point in the conversion path.

Building a Hybrid Qualification Model

A hybrid qualification model combines the structural rigor of an established framework with the behavioral signal layer that trial-period product data provides. The goal is not to replace discovery conversations with product data — it is to ensure discovery happens with the right accounts, at the right moment, with behavioral context already in hand.

Step 1: Choose a framework skeleton appropriate to your deal profile

Match skeleton to median ACV and cycle length. Under $20,000 ACV with a cycle under three months: ANUM. Between $20,000 and $80,000 ACV with cycles of two to six months: SPICED. Above $80,000 ACV with cycles longer than six months: MEDDIC. The skeleton gives reps the structural criteria relevant to their deal type without requiring the full overhead of a more complex framework on smaller deals.

Step 2: Add a behavioral signal threshold for PLG accounts

Define the minimum behavioral signal combination a trial account must hit before receiving active rep attention. Build this threshold from your own trial-to-paid conversion data. Common starting points: two or more users in the account with at least three return sessions in the first fourteen days, or any account that has activated a core workflow and invited a colleague. The principle is that product behavior defines call priority, not time elapsed since signup.

Step 3: Map framework criteria to product signals where possible

Many qualification criteria can be partially answered by product data before any conversation. Need — answered by feature activation pattern. Urgency — approximated by session frequency and recency. Team expansion — directly observable. Where a criterion can be informed by product data, reps enter the conversation with a hypothesis rather than a blank slate.

Step 4: Reserve discovery for criteria that require conversation

Some criteria cannot be answered by behavioral data: the economic buyer's identity, the decision process, the critical event, and the champion's organizational influence. These justify a discovery call. Framing the call as "completing the qualification the product started" rather than "beginning qualification from zero" changes both rep preparation and the conversation itself.