Qualification frameworks — BANT, MEDDIC, SPICED done right.

The premise — architecture vs checklist

The dominant failure mode is the seller who reads a framework as a script — runs through the BANT four in sequence, exits with four data points the buyer answered honestly only on the easiest, logs them in the CRM, treats them as qualifying signal. Conversion from this posture runs 5 to 10 percentage points below the conversion achieved by a seller running the same framework as a conversational architecture.

The architectural posture is the inversion. The framework is a mental model of what the seller needs to learn; the conversation is whatever shape produces that signal naturally. The seller asks about a recent initiative; the buyer mentions a budget reallocation; the budget dimension is qualified without the seller asking the budget question directly.

Selecting the wrong framework for the segment produces a discipline mismatch — too much rigor on a transactional deal, too little on an enterprise one — that suppresses conversion at the margin.

BANT — budget, authority, need, timeline

The oldest canonical framework and the most over-deployed. Four dimensions: budget allocated, authority to commit it, need present and acute, timeline that produces a forcing function.

BANT's strength is speed. A BANT-qualified call closes the four dimensions in 15 to 20 minutes and produces a clear advance-or-disqualify signal at the end of the first conversation. For high-velocity transactional motions — ACV $5K to $30K, single decision-maker, sub-30-day cycle — this is the right posture. The cost of over-qualifying a transactional deal exceeds the cost of mis-qualifying it, because closed-deal value is bounded by the ACV.

BANT's failure modes are structural. It does not specify a champion dimension or a decision process. On deals with three or more stakeholders it under-qualifies — the seller leaves the call with all four dimensions confirmed and discovers, six weeks later, that the deal has stalled in a procurement process the BANT call never surfaced. Above $30K ACV or with more than one stakeholder, BANT alone is not sufficient.

MEDDIC — metrics, economic buyer, decision criteria, decision process, identify pain, champion

The complex-enterprise framework. Six dimensions: the quantified outcome the buyer is trying to produce; the individual who signs the contract, distinct from user and champion; explicit and implicit decision criteria; the sequence of approvals the contract has to traverse; the underlying pain; and the internal advocate.

MEDDIC's strength is rigor. On a complex enterprise deal — $75K+ ACV, four or more stakeholders, 90+ day cycle, procurement and security and legal in the path — it surfaces the signal BANT misses by construction. The deal that stalls in procurement because the decision process was never mapped does not stall under MEDDIC.

MEDDIC's failure mode is over-structuring early conversations. A seller who walks into a first discovery call with the explicit checklist in hand produces a procedural call — every question detectable as a framework question, narrative coherence collapses, the seller exits with three of six dimensions partially filled. MEDDIC works as a multi-call qualification architecture; treating it as a single-call checklist destroys the conversational quality that produces the signal.

SPICED — situation, pain, impact, critical event, decision

The narrative-driven framework. Five dimensions arranged as a story: current situation, pain inside the situation, quantified impact, critical event forcing the decision, decision process itself. The framework reads as a narrative arc — where they are, what hurts, what it costs, what is forcing the action, how the decision gets made.

SPICED's strength is narrative coherence. The buyer experiences the call as a conversation about their business, not as a qualification exercise. The critical-event dimension is the load-bearing component BANT's timeline misses — timeline answers "when," critical event answers "why now," and the latter produces a forcing function the former does not. For mid-market deals — $30K to $100K ACV, two to four stakeholders, 30 to 90 day cycle — SPICED produces the conversation the buyer wants to have.

SPICED's failure mode is quantification. The impact dimension is intended to be quantified — dollars, hours, headcount — but the framework provides less rigor than MEDDIC's metrics dimension on how to extract the number. Sellers running SPICED loosely exit with a qualitative impact statement, lacking the metric required to anchor the proposal in Chapter 05. Pairing SPICED with explicit impact-quantification discipline closes the gap.

GPCT — goals, plans, challenges, timeline

The inbound-driven framework. Four dimensions oriented around the buyer's stated objectives rather than the seller's qualifying criteria. Goals — what the buyer is trying to accomplish. Plans — what they are currently planning. Challenges — what is blocking the plan. Timeline — when they need it done.

GPCT's strength is the buyer-led posture. For inbound motions — prospect arrived via content, demo request, or referral, intent already declared — the qualifying conversation leads with the buyer's goals. The buyer experiences a strategic conversation; qualifying signal surfaces as a side effect.

GPCT's failure mode is the inverse of BANT's. It under-specifies authority and budget — they live inside "plans" and "challenges" by implication — and a GPCT-qualified deal can advance through three conversations before the seller discovers the buyer was a research lead. Applied to outbound, where intent is the thing being qualified, GPCT surfaces too little signal too late.

Empirical per-framework fit

The bands overlap intentionally. The ACV band is a proxy; the determinant is the shape of the buying organization. A $50K mid-market deal with a procurement-heavy buyer is structurally enterprise and warrants MEDDIC; a $40K deal with a single buyer is structurally SMB and warrants BANT.

Operational selection criteria

The selection question is "which framework matches the deal in front of the seller." Four signals drive it:

• Stakeholder count. One: BANT. Two to four: SPICED. Four-plus: MEDDIC. Inbound at any count: GPCT-first, layered with the structural framework once intent is confirmed.
• Cycle length. Under 30 days: BANT. 30 to 90: SPICED. 90+: MEDDIC. Cycle length is downstream of stakeholder count — confirmatory, not independent.
• Procurement intensity. If the deal will traverse procurement, security, and legal, the decision-process dimension is load-bearing. Only MEDDIC names it explicitly.
• Origination channel. Inbound: GPCT-led. Outbound: BANT, SPICED, or MEDDIC by stakeholder count.

Frameworks as conversational architecture

The checklist seller extracts answers. The architecture seller constructs a conversation whose natural shape produces the answers as artifacts. The first buyer notices the extraction; the second experiences a strategic conversation about their business.

The operational discipline is to convert each framework dimension into a discovery-question family rather than a single question. The MEDDIC metrics dimension is not "what metric do you track for this?" — that reads as a survey item. It is the family that surfaces the metric: "what does the team report up to the executive on this area?", "when this initiative is reviewed, what number gets cited?", "if the budget gets cut, what number does the cut have to be defended against?" Same qualifying signal, different surface language.

Per-framework discovery question architecture

• BANT — budget. "What's the typical investment range for an initiative like this?" — not "do you have budget."
• BANT — authority. "Beyond yourself, who else would weigh in on a decision like this?" — not "are you the decision-maker."
• MEDDIC — economic buyer. "When this gets signed, whose signature is on the contract?" — surfaces the economic buyer without naming the role.
• MEDDIC — decision process. "What's the typical path from a decision like this being made to it being operational?" — surfaces procurement, legal, and security gates as side effects of describing the path.
• SPICED — critical event. "If this doesn't get solved by [stated timeline], what happens?" — surfaces the forcing function or its absence.
• GPCT — challenges. "What's blocking the plan you described from working as-is?" — surfaces the pain without leading with the seller's solution.

The qualified-vs-disqualified threshold

Each framework has an explicit threshold below which the deal is de-prioritized — moved out of active pipeline into longer-cycle nurture. The threshold separates a qualified pipeline review from a hopeful one.

• BANT. Three of four dimensions confirmed, with timeline inside 60 days. Two of four: nurture.
• MEDDIC. Four of six dimensions confirmed, with economic buyer and champion both named. Three or fewer: nurture, regardless of which three.
• SPICED. Pain and critical event both confirmed, with at least a qualitative impact statement. Missing the critical event: nurture.
• GPCT. Goals and challenges both confirmed, with at least one explicit plan articulated. Missing the plan: research-stage, route to content nurture.

Per-stage qualification depth

A pipeline operating a single framework at uniform depth across stages mis-allocates qualifying effort. Early-pipeline: BANT-minimum — confirm need, rough timeline, that a stakeholder is meaningful. Mid-stage (second to third call): full framework per the segment-fit selection above; the qualification is the call. Late stage: explicit decision-process mapping — every approval, signature, and gate, with named owners and date estimates. The map becomes a deliverable shared back with the champion in Chapter 05.

The multi-framework hybrid

The empirically strongest pattern across mid-market and enterprise teams is the BANT-then-MEDDIC hybrid. BANT runs as the first-call screen — exit-or-advance in 20 minutes. Deals that pass receive MEDDIC depth on the second and third call. The hybrid requires CRM discipline: BANT fields and MEDDIC fields are separate; deal-stage advance is gated on the MEDDIC fields. Sellers who collapse the two — treating BANT as sufficient for any deal — surface the BANT failure mode at the proposal stage, where it is too late to recover.

Framework as coaching tool

For new AEs ramping in the first 90 days, the framework is the coaching scaffold. The AE runs MEDDIC explicitly — every dimension named, probed, logged. The conversation reads as procedural; the early calls suffer for it. The discipline produces a six-month outcome the architectural posture cannot: the AE internalizes the dimensions as reflex, after which the framework moves from script to mental model and the calls regain conversational quality. The 90-day procedural phase is the cost of the 12-month reflex.

Framework as pipeline-review tool

A weekly pipeline review run against the explicit framework surfaces the qualification gaps the in-call seller missed. The review question is per-deal, per-dimension: is the metric named, is the economic buyer named, is the decision process mapped, is the champion identified. Deals with two or more gaps on dimensions appropriate to their stage are flagged for re-qualification, not advance. Pipelines without this discipline grow by accumulation; forecast accuracy collapses; AE effort spreads across deals that will not close.

Qualifying-out as discipline

The hardest operational habit is the explicit qualifying-out conversation. A deal stalled on three calls without the champion materializing does not need another touch — it needs a "what would have to be true for this to move forward" conversation, followed by either a clear advance commitment or an explicit close-lost. Sellers who run this honestly close 15 to 25% of stalled deals to advance and the remainder to close-lost. Sellers who avoid it carry the stalled deal for three to six months at zero advance probability. The framework provides the structural language: the seller is not asking "do you still want this" — they are naming the unqualified dimension and asking what it would take to qualify it.

Multi-thread engagement

The authority dimension across all four frameworks underspecifies the operational reality of B2B buying. A deal qualified on a single named authority is a single-thread deal; the failure mode is the champion who loses internal politics. Multi-thread engagement (Chapter 04) is the operational extension: not "who is the decision-maker" but "who are the three to five people who will weigh in." The framework names the dimension; Chapter 04 operationalizes it.

Common operator failures

• Framework-as-checklist. The seller reads the dimensions as questions and asks them in sequence. The call reads as a survey; pipeline conversion runs 5 to 10 percentage points below the architectural posture. Most common in operators who learned the framework from a one-day training and never internalized it.
• No qualifying-out discipline. Deals accumulate regardless of qualification depth. Forecast accuracy collapses. Visible as a slow-growing tail of 90+ day deals without recent advance signal.
• Single framework across segments. The team runs BANT on every deal, including the $200K enterprise pursuit with seven stakeholders. The deal stalls in procurement because the decision-process dimension was never named. The team concludes enterprise deals "just take longer" and continues mis-qualifying.
• No per-stage depth variation. Every deal receives full MEDDIC qualification on the first call. First-call conversion suffers; the buyer never engages on the problem. Full-funnel conversion drops despite rigorous late-stage qualification.
• Framework theater in CRM, not in the conversation. All six MEDDIC fields are populated, filled in after the call from memory and inference. The reviewer sees a qualified deal; the AE knows it is not. The forecast inherits the fiction.
• Champion-equals-economic-buyer collapse. The seller treats one stakeholder as both because the same person introduced themselves as both. In approximately 60% of enterprise deals these are different people. The difference surfaces at the contract stage.

Pre-deployment checklist

• Per-segment framework selection documented — ACV band, stakeholder count, cycle length, origination channel — with explicit defaults per segment
• Per-framework dimension-to-discovery-question family authored and AE-reviewed; CRM fields aligned to the framework dimensions, not to legacy fields from a prior framework
• Qualified-vs-disqualified threshold defined per framework, with an explicit pipeline-stage gate on the threshold
• Per-stage qualification depth defined — early-pipeline minimum, mid-stage full framework, late-stage explicit decision-process mapping
• Multi-framework hybrid (BANT-then-MEDDIC, or equivalent) documented if the team is operating across segment bands
• Weekly pipeline review structured around per-deal, per-dimension qualification gaps, not around pipeline totals
• Qualifying-out conversation script authored, with explicit language for the "what would have to be true" prompt
• Per-AE coaching plan distinguishing the explicit-procedural phase from the architectural phase, with a defined transition criterion at ~90 days

Where this fits

Qualification is the discipline that prevents the discovery call architecture from Chapter 01 from advancing un-qualified deals into the demo, proposal, and close mechanics that follow. The framework is the structural language; the operational primitive is the architectural posture — a strategic conversation that surfaces qualifying signal as a side effect of the conversation the buyer wanted to have.

Chapter 04 (multi-thread engagement) operationalizes the authority dimension into a per-role engagement architecture. The decision-process dimension becomes a deliverable in Chapter 05 (proposal design). The framework is the connective tissue between discovery and close — operated as architecture, the deal advances on qualified signal; operated as a checklist, the deal advances on the seller's optimism, and the forecast inherits the cost.