BANT vs MEDDICC vs SPICED: Guia Definitivo Para Escolher Seu Framework de Vendas

Cinco décadas e três frameworks dominantes. BANT (IBM, anos 60), MEDDICC (PTC, anos 90), SPICED (Winning by Design, anos 2010). Decompomos cada um, a matriz de decisão por setor/ticket/ciclo, e como escolher o certo pro seu contexto.

Publicado: 2026-04-22 · Leitura: 10 min · Categoria: comparison

Frameworks de vendas existem pra resolver um problema simples: qualificação inconsistente. Vendedor novo qualifica diferente do experiente. Gestor não consegue comparar deals. Forecast vira chute.

O problema é que existem dezenas de frameworks, e muita gente usa o errado pro seu contexto. Este guia decompõe os 3 mais importantes — BANT, MEDDICC e SPICED — e entrega uma matriz de decisão pra você escolher o certo.

Os 3 frameworks em 60 segundos

BANT (IBM, anos 1950-60)

O avô de todos. Criado pela IBM pra qualificar oportunidades em vendas de mainframes.

Letras:

Budget: tem orçamento?
Authority: é quem decide?
Need: tem dor/necessidade?
Timing: qual o prazo?

Tese: 4 perguntas binárias. Se todas forem "sim", qualifica. Se alguma for "não", descarta.

Quando nasceu: vendas transacionais de ticket alto, ciclo curto, decisor único.

MEDDICC (PTC, anos 1990)

Criado por Jack Napoli na PTC (fabricante de software CAD/PLM). Ganhou adoção ampla em 2020 com o livro de Andy Whyte.

Letras:

Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion, Competition

Tese: em vendas enterprise complexas, 7 camadas de qualificação separam deal qualificado de zombie.

Quando nasceu: vendas enterprise com 4+ stakeholders, ciclo 6-18 meses, ticket $100k+.

SPICED (Winning by Design, anos 2010)

Criado por Jacco van der Kooij na Winning by Design. Emergiu junto com o boom de SaaS mid-market.

Letras:

Situation, Pain, Impact, Critical Event, Decision

Tese: em SaaS, o deal não termina no fechamento — continua na renovação/expansão. Discovery profundo na pré-venda previne churn. Critical Event é o gatilho de urgência único do SPICED.

Quando nasceu: SaaS mid-market, ciclo 30-90 dias, ticket $20k-$500k ACV.

Matriz de decisão: qual escolher

Dimensão	BANT	MEDDICC	SPICED
Ticket	< $20k ACV	$100k+ ACV	$20k-$500k ACV
Ciclo de venda	< 30 dias	6-18 meses	30-120 dias
Stakeholders	1-2	4-10	2-5
Setor típico	SaaS transacional, inside sales volume	Enterprise SaaS, industrial, consultoria	SaaS mid-market, MarTech, FinTech B2B
Overhead CRM	4 campos	7-8 campos	5 campos
Curva de treinamento	1-2 semanas	6-12 meses	2-4 meses
Forecast accuracy típico	±40%	±15% (quando aplicado)	±20%
Ponto forte	Simplicidade, velocidade	Qualificação enterprise profunda	Discovery + urgência
Ponto fraco	Superficial, subjetivo (sim/não)	Overhead alto, curva longa	Menos estruturado que MEDDICC

A decisão em 3 perguntas

Se você tem pouco tempo pra decidir, responda 3 perguntas:

1. Qual é seu ticket médio?

< $20k ACV → BANT basta
$20k-$500k ACV → SPICED é o sweet spot
> $500k ACV → MEDDICC (ou MEDDPICC)

2. Quantos stakeholders típicos no deal?

1-2 → BANT
3-5 → SPICED
6+ → MEDDICC

3. Ciclo médio?

< 30 dias → BANT
30-120 dias → SPICED
> 120 dias → MEDDICC

Se as 3 respostas apontam pro mesmo framework, use esse. Se apontam pra mais de um, o framework do maior ticket ganha (BANT < SPICED < MEDDICC em complexidade).

Os erros mais comuns na escolha

Erro 1: Usar BANT em vendas enterprise

Time B2B enterprise tentando qualificar deal de R$ 1M com 4 perguntas binárias do BANT. Deal fecha (porque tinha Budget e Authority), mas depois de 8 meses descobre-se que faltou Economic Buyer real, Decision Process, e Competition — deal morre na aprovação do board.

Sintoma: forecast bate pouco, surpresas recorrentes em deals que "estavam certos".

Erro 2: Usar MEDDICC em SaaS mid-market

Time SaaS com 10 reps vendendo $60k ACV tentando aplicar MEDDICC com 7 campos. Overhead mata adoção. Reps preenchem "validated" sem validar. Framework vira teatro.

Sintoma: CRM com MEDDICC preenchido em 100% dos deals, mas forecast continua impreciso.

Erro 3: Não ter framework

Pior cenário: cada rep qualifica do seu jeito. Gestor não consegue comparar. Cada pipeline review vira subjetividade. Forecast ±50%.

Sintoma: "tive um bom feeling nesse deal" vira padrão de resposta.

Como usar múltiplos frameworks (avançado)

Operações maduras usam mais de um framework em camadas:

Camada 1 — SDR fazendo qualificação inicial: BANT. Leve, rápido, 30 segundos no SQL handoff.

Camada 2 — AE fazendo discovery: SPICED. Profundo, discovery-first, sustenta o deal até fechamento.

Camada 3 — Enterprise AE com deal >$200k ACV: MEDDICC. Overlay sobre SPICED pra capturar Champion, Competition, Paper Process.

Essa estrutura evita overhead onde não precisa e aumenta rigor onde importa.

Como operacionalizar com IA em 2026

O problema histórico: vendedor esquece de aplicar o framework, preenche CRM por obrigação, vira teatro.

A mudança de 2026 é usar LPH Meet pra detectar em tempo real quais perguntas do framework não foram feitas na call. Ex: vendedor usou SPICED, cobriu Situation/Pain/Impact, mas não perguntou sobre Critical Event. IA sugere pergunta no momento — ou marca o gap pra próxima call.

Isso transforma framework de checklist esquecido em bússola viva.

Conclusão

Três frameworks, três contextos. BANT é o bisturi pequeno — rápido e simples. MEDDICC é a cirurgia enterprise — profunda e demorada. SPICED é o ponto de equilíbrio moderno — suficientemente rigoroso pra qualificar, suficientemente leve pra adotar.

Escolha pelo seu ticket, ciclo e número de stakeholders. Adapte conforme cresce. E, acima de tudo, tenha um — a única coisa pior que o framework errado é não ter framework nenhum.

Leads Per Hour Research Team — Abril 2026

Relacionados: MEDDICC Completo → · SPICED Winning by Design → · Discovery Call Script →

BANT vs MEDDICC vs SPICED: The Definitive Guide to Choosing Your Sales Framework (English)

Five decades and three dominant frameworks. BANT (IBM, 60s), MEDDICC (PTC, 90s), SPICED (Winning by Design, 2010s). We break each one down, the decision matrix by sector/ticket/cycle, and how to pick the right one for your context.

Sales frameworks exist to solve a simple problem: inconsistent qualification. A new rep qualifies differently than an experienced one. The manager can't compare deals. Forecast becomes a guess.

The problem is that dozens of frameworks exist, and many teams use the wrong one for their context. This guide breaks down the 3 most important — BANT, MEDDICC, and SPICED — and delivers a decision matrix to help you pick right.

The 3 frameworks in 60 seconds

BANT (IBM, 1950-60s)

The grandfather of all. Created by IBM to qualify opportunities in mainframe sales.

Letters:

Budget: do they have budget?
Authority: are they the decision-maker?
Need: is there pain/need?
Timing: what's the deadline?

Thesis: 4 binary questions. If all are "yes," qualify. If any is "no," disqualify.

Born for: transactional sales with high tickets, short cycles, single decision-maker.

MEDDICC (PTC, 1990s)

Created by Jack Napoli at PTC (CAD/PLM software maker). Gained broad adoption in 2020 with Andy Whyte's book.

Letters:

Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion, Competition

Thesis: in complex enterprise sales, 7 layers of qualification separate qualified deals from zombies.

Born for: enterprise sales with 4+ stakeholders, 6-18 month cycle, $100k+ ticket.

SPICED (Winning by Design, 2010s)

Created by Jacco van der Kooij at Winning by Design. Emerged alongside the mid-market SaaS boom.

Letters:

Situation, Pain, Impact, Critical Event, Decision

Thesis: in SaaS, the deal doesn't end at close — it continues at renewal/expansion. Deep pre-sale discovery prevents churn. Critical Event is SPICED's unique urgency trigger.

Born for: mid-market SaaS, 30-90 day cycle, $20k-$500k ACV ticket.

Decision matrix: which to pick

Dimension	BANT	MEDDICC	SPICED
Ticket	< $20k ACV	$100k+ ACV	$20k-$500k ACV
Sales cycle	< 30 days	6-18 months	30-120 days
Stakeholders	1-2	4-10	2-5
Typical sector	Transactional SaaS, volume inside sales	Enterprise SaaS, industrial, consulting	Mid-market SaaS, MarTech, B2B FinTech
CRM overhead	4 fields	7-8 fields	5 fields
Training curve	1-2 weeks	6-12 months	2-4 months
Typical forecast accuracy	±40%	±15% (when applied)	±20%
Strength	Simplicity, speed	Deep enterprise qualification	Discovery + urgency
Weakness	Shallow, subjective (yes/no)	High overhead, long curve	Less structured than MEDDICC

The decision in 3 questions

If you have little time to decide, answer 3 questions:

1. What's your average ticket?

< $20k ACV → BANT is enough
$20k-$500k ACV → SPICED is the sweet spot
> $500k ACV → MEDDICC (or MEDDPICC)

2. How many typical stakeholders per deal?

1-2 → BANT
3-5 → SPICED
6+ → MEDDICC

3. Average cycle?

< 30 days → BANT
30-120 days → SPICED
> 120 days → MEDDICC

If all 3 answers point to the same framework, use it. If they split, the framework of the larger ticket wins (BANT < SPICED < MEDDICC in complexity).

The most common picking mistakes

Mistake 1: Using BANT in enterprise sales

Enterprise B2B team trying to qualify a $1M deal with BANT's 4 binary questions. Deal closes (because they had Budget and Authority), but 8 months in they discover no real Economic Buyer, no Decision Process, no Competition awareness — deal dies in board approval.

Symptom: forecast rarely hits, recurring surprises in deals that "were certain."

Mistake 2: Using MEDDICC in mid-market SaaS

SaaS team of 10 reps selling $60k ACV trying to apply MEDDICC with 7 fields. Overhead kills adoption. Reps mark "validated" without validating. Framework becomes theater.

Symptom: CRM with MEDDICC filled on 100% of deals, but forecast remains imprecise.

Mistake 3: Having no framework

Worst scenario: each rep qualifies their own way. Manager can't compare. Every pipeline review becomes subjective. Forecast ±50%.

Symptom: "I had a good feeling about this deal" becomes the default response.

How to use multiple frameworks (advanced)

Mature operations use more than one framework in layers:

Layer 1 — SDR doing initial qualification: BANT. Light, fast, 30 seconds at SQL handoff.

Layer 2 — AE doing discovery: SPICED. Deep, discovery-first, sustains the deal until close.

Layer 3 — Enterprise AE with deal >$200k ACV: MEDDICC. Overlay on top of SPICED to capture Champion, Competition, Paper Process.

This structure avoids overhead where it's not needed and adds rigor where it matters.

How to operationalize with AI in 2026

Historical problem: the rep forgets to apply the framework, fills CRM out of obligation, becomes theater.

The 2026 shift uses LPH Meet to detect in real time which framework questions weren't asked on the call. Example: rep used SPICED, covered Situation/Pain/Impact, but didn't ask about Critical Event. AI suggests the question in the moment — or flags the gap for the next call.

This turns a framework from forgotten checklist into living compass.

Conclusion

Three frameworks, three contexts. BANT is the small scalpel — fast and simple. MEDDICC is enterprise surgery — deep and slow. SPICED is the modern balance point — rigorous enough to qualify, light enough to adopt.

Pick by your ticket, cycle, and stakeholder count. Adapt as you grow. And above all, have one — the only thing worse than the wrong framework is having no framework at all.

Leads Per Hour Research Team — April 2026