Sales qualification · Framework selection
SPICED vs MEDDPICC vs BANT: which framework fits each sales role
Sohrab Mostaghim, Founder · 2 October 2026 · Updated 23 October 2026 · 10 min read
Use SPICED for discovery and MEDDPICC for complex deals. SPICED, from Winning by Design, helps SDRs understand situation, pain, impact, critical event and decision before handoff. MEDDPICC helps account executives qualify and forecast multi-stakeholder enterprise deals. BANT is a quick filter for simple, transactional leads. Customer success needs an expand-and-renew lens instead.
The short answer: one framework per seat
"Which framework is best?" is the wrong question. Frameworks are checklists. They make sure the details that matter get covered, and they don't teach anyone judgment on their own. The useful question is best for which seat, and for which decision that person has to defend on Monday?
| Seat | Framework | What "qualified" means for that seat | What they hand over |
|---|---|---|---|
| SDR / BDR | SPICED | A meeting the AE can work: real pain, a reason to act now, the right person | A SPICED handoff note with sources |
| Account executive | MEDDPICC | A deal you can forecast: economic buyer, decision and paper path mapped, champion tested | A deal record with evidence for each letter |
| Customer success | Expand and renew | A defensible call to expand, renew or hold, based on what the customer actually achieved | A renewal or expansion case |
| Simple, transactional leads | BANT | Worth a conversation at all | A yes or no |
For the longer argument against one curriculum for every seat, read One path for all is the worst we can do.
SPICED vs MEDDPICC vs BANT compared
| SPICED | MEDDPICC | BANT | |
|---|---|---|---|
| Origin | Winning by Design (Jacco van der Kooij) | MEDDIC, created at PTC in 1996, plus Paper Process and Competition | Commonly attributed to IBM |
| Purpose | Diagnose before you pitch: why change, why now, how they'll decide | Qualify and forecast complex deals: can this close, when, and against whom? | Filter quickly: is this worth a conversation? |
| Stage | First contact through discovery and handoff. Winning by Design also uses it later in the customer journey | From qualified opportunity to signature | First call |
| Usual owner | SDR / BDR, and AEs in discovery | Account executive and their manager | SDR or inside sales |
| Typical questions | "What happens if this stays the same for six months?" "Is there a date this has to be solved by?" | "Who can approve this without another layer?" "Who signs, and what has to happen first?" | "Do you have budget?" "Are you the decision maker?" |
| What it produces | A handoff note the AE can pick up cold | A deal record a manager can inspect and forecast | A yes or no |
| How it fails | Thin on paper process and competition, so enterprise deals stall after a good discovery | When SDRs use it, the economic buyer and paper fields fill up with guesses | Budget and authority are assumed early, and pain and urgency go unasked |
Full guides: SPICED framework training and MEDDPICC training.
One deal, qualified three ways
Fictional example: Brightwater Logistics, a 2,000-person freight company, downloads a guide about dispatch planning. Its head of operations agrees to a call. The company, people and numbers are invented, and the same deal appears in our MEDDPICC guide.
BANT, on the first call
- Budget: "There's a line for transport tooling this year." ✓
- Authority: the head of operations says she decides. ✓
- Need: late deliveries. ✓
- Timeline: "This year." ✓
Four ticks, so BANT says qualified, and the deal goes into the forecast for Q2. Nobody has asked what late deliveries cost, why this year, who else approves, or what happens after a yes.
SPICED, on the same call
- Situation: 40 depots, dispatch on spreadsheets plus a legacy tool, four planners per region.
- Pain: 9% of deliveries are late, in her words.
- Impact: about €40 in customer credits per late delivery. Two large retail customers have sent formal warnings.
- Critical Event: the biggest of those retail contracts renews in September.
- Decision: she'd need the CFO, and IT approves anything that touches the ERP. She wants a pilot first.
Verdict: ready for handoff, with Decision only partly known. The AE now knows why now (September) and that the buying group is bigger than one person, which BANT missed.
MEDDPICC, over the next five weeks
- Metrics: late deliveries from 9% to under 5% by Q3, the board target.
- Economic Buyer: the CFO. Met once. She'll fund it only if it replaces two existing tools.
- Decision Criteria: works with their ERP without custom code; drivers adopt it in four weeks; costs less than the two tools it replaces. EU data residency is pass/fail.
- Decision Process: pilot review on 3 May, steering committee on 20 May, then CFO sign-off.
- Paper Process: about three weeks of vendor onboarding, a security questionnaire and a data processing agreement. Anything over €150k needs a second signature from the COO.
- Identify Pain: the retail warnings and the September renewal, confirmed by the ops director and the CFO.
- Champion: the ops director set up the CFO meeting and pushed back on IT's objection when the AE wasn't there.
- Competition: one vendor, a half-built internal tool whose owner wants six more months, and doing nothing.
Verdict: a real deal, but not a Q2 deal. With the steering committee on 20 May and about three weeks of paperwork after that, the earliest realistic signature is mid-June, and the internal build is a live alternative.
What each framework caught
| BANT | SPICED | MEDDPICC | |
|---|---|---|---|
| Is there real pain? | Assumed | Yes, in her words | Yes, confirmed by two people |
| Why now? | "This year" | September renewal | September renewal, tied to the board target |
| Who decides? | One person | She'd need the CFO and IT | CFO met, criteria known, second signature identified |
| What happens after a yes? | Not asked | Not asked | Mapped: three weeks of paperwork and a COO signature |
| Alternatives? | Not asked | Not asked | Vendor, internal build, do nothing |
| Forecast | Q2 (wrong) | Not its job | Mid-June at the earliest, internal build is the risk |
No single framework is "better" here. BANT was too thin. SPICED gave the AE a strong start in one call. MEDDPICC turned that start into a forecast a manager can defend. Each one did the job of its seat.
When to use which, by seat
SDR and BDR: SPICED
An SDR's job is a meeting the AE can work. SPICED asks for exactly that: the buyer's situation, a pain they named, what it costs, a date that forces a decision, and an early picture of how they'll decide. Decision can be partial at handoff, as long as it's labelled. Don't ask SDRs for the economic buyer's approval criteria or the paper process. They can't own those yet, so they'll guess. Use the SQL handoff checklist.
Account executives: MEDDPICC
Enterprise deals rarely die in discovery. They die later: in a budget meeting the AE never attended, in a procurement process nobody mapped, or to an internal build nobody counted as competition. MEDDPICC exists for those failure points. AEs should keep using SPICED-style questions in discovery, then hold the deal to MEDDPICC from qualification to signature. What breaks when a letter is skipped.
Sales managers: inspect both, on one evidence scale
Managers don't need a third framework. They need to inspect the two they already have in the same way. Score every SPICED element and every MEDDPICC letter on one scale, from 0 (unknown) to 4 (validated by more than one stakeholder or a document), and always ask for the proof. Inspect SDRs on handoffs (ready, partial, not ready) and AEs on deals (MEDDPICC scorecard). Then a "ready" SDR handoff and a "confirmed" AE letter mean the same thing in every team.
Customer success: expand and renew
There's no single dominant CSM acronym the way MEDDPICC dominates for AEs. What CSMs need is a lens for an account they inherit: what was promised (the metrics), what the customer actually achieved, whether the champion is still there, and which critical events are coming. Then they make a defensible call to expand, renew or hold. Winning by Design also uses SPICED after the sale, and revisiting Impact and Critical Event before a renewal works well. See the expand and renew guide.
How SPICED and MEDDPICC hand off
You can combine them. Most teams that run both do it like this: the SDR's SPICED note becomes the AE's starting point.
| SDR captures (SPICED) | AE builds on it (MEDDPICC) |
|---|---|
| Situation, Pain | Identify Pain |
| Impact | Metrics |
| Critical Event | Decision Process (the timeline) |
| Decision | Decision Process, Decision Criteria, Economic Buyer |
| Not in scope for the SDR | Paper Process, Champion, Competition |
Three rules keep the handoff honest:
- The AE confirms, and doesn't start from zero. The first AE call re-checks Pain, Impact and Critical Event in a few minutes, then moves on to what's missing.
- The AE can send a handoff back, with a reason. "Critical Event was our quarter-end, not theirs" is useful feedback. A silent re-qualification isn't.
- Partial is allowed, but fake isn't. An SDR who writes "Decision: heard about the CFO, not confirmed" is doing it right. One who claims a decision stage they never heard will lose the AE's trust in every future handoff.
The same logic applies at closed-won: the AE's evidence on Metrics, Champion and open risks becomes the CSM's starting point.
What goes wrong with the wrong framework
- SDR team forced into MEDDPICC. Six weeks in, every opportunity shows the economic buyer as "identified" and paper process as "in progress", with no evidence behind either. AEs re-qualify from zero, ramp slows, and nobody trusts the forecast.
- AE team coached only on SPICED. Discovery looks great. Then legal and procurement stall with no owner, and a quiet incumbent comes back. The deal dies after a "qualified" discovery, which is exactly the gap Paper Process and Competition were added to cover.
- CSMs scored on new-business MEDDPICC. Reps invent Metrics and Champion stories for accounts they inherited, instead of checking what was actually delivered and who still cares. Renewals get decided on stories, not evidence.
What about CHAMP, ValueSelling and Command of the Message?
- CHAMP (Challenges, Authority, Money, Prioritisation) puts the problem first, which makes it a better first-call filter than BANT. It's still a filter, not a deal-inspection or handoff system.
- ValueSelling is a methodology for structuring value conversations. It's strong on conversation craft and complements a qualification framework rather than replacing one.
- Command of the Message (Force Management) is about positioning and messaging discipline. Many teams pair it with MEDDICC or MEDDPICC: one shapes what you say, the other checks whether the deal is real.
Where these frameworks come from
SPICED was developed by Winning by Design, founded by Jacco van der Kooij. MEDDIC was created at PTC in 1996: Dick Dunkel wrote it down, working with Jack Napoli under sales leader John McMahon (Jack Napoli's account). Competition and Paper Process were added later, giving MEDDICC and MEDDPICC. BANT is commonly attributed to IBM. The methodologies belong to their originators. We teach practice on them, not the methods themselves.
FAQ
SPICED or MEDDPICC: which is better?
Neither is better in general. They do different jobs. SPICED suits SDRs and early discovery: real pain, a reason to act now, and an early view of how the buyer will decide. MEDDPICC suits account executives qualifying and forecasting complex deals with several stakeholders, procurement and competitors. Most B2B teams use SPICED before the handoff and MEDDPICC after it.
Is MEDDPICC better than BANT?
For complex B2B deals, yes. BANT checks budget, authority, need and timeline, usually on the first call, and often takes the answers at face value. MEDDPICC asks for evidence on eight points, including the economic buyer, the decision and paper process, a tested champion vs coach and every alternative. For simple, transactional sales, BANT can still be a sensible first filter.
Can SDRs use MEDDPICC?
They can learn the letters, but they rarely own what MEDDPICC asks for. SDRs aren't in the room for economic buyer conversations, procurement or competitive displacement, so those fields fill up with guesses that AEs then discard. SPICED fits the SDR's job of producing a meeting the AE can work. SDRs can still note early hints on Decision.
What is the difference between MEDDIC and MEDDPICC?
MEDDIC has six elements: Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain and Champion. It was created at PTC in 1996. MEDDPICC adds Paper Process (legal, security, procurement and signature) and Competition (other vendors, an internal build or doing nothing), the two places many enterprise deals stall after discovery looked fine.
Can you combine SPICED and MEDDPICC?
Yes, and many teams do. The SDR qualifies with SPICED and hands over a note with sources. The AE confirms Pain, Impact and Critical Event, then builds the MEDDPICC picture: Impact feeds Metrics, Critical Event feeds the Decision Process timeline, and Decision feeds the economic buyer and decision criteria. Paper Process, Champion and Competition start with the AE.
Which framework suits customer success?
There is no single dominant customer success framework. CSMs need a lens for an inherited account: what was promised, what was achieved, whether the champion is still there, and which events are coming. They then make a defensible call to expand, renew or hold. Revisiting SPICED's Impact and Critical Event before a renewal is a useful habit.
Where Game Is Serious fits
We built Deal IQ around this seat map. SDRs practise SPICED on an outbound week and are scored on whether the AE could work the meeting. AEs research an account and run a full MEDDPICC deal against simulated buyers who push back. Managers see the evidence for each element or letter in a debrief. A session takes 60 to 90 minutes, and players can type or speak their actions in English or German.
- SDR / BDR seat · Account executive seat · Customer success seat
- Play a practice deal without logging in
- Individuals: SPICED Qualifier and MEDDPICC Qualifier, verifiable training credentials after a scored run. They're work samples, not certifications. The same idea sits behind how to assess sales candidates before you hire.
- Pricing: no public tiers. It starts with a discovery call.
Limits. We don't certify SPICED or MEDDPICC, and we aren't their originators. A simulation result describes judgment in one scenario. It doesn't replace your own deal and handoff reviews. Game Is Serious is not affiliated with Winning by Design, PTC or the creators of MEDDIC and MEDDPICC.
About the author. Sohrab Mostaghim founded Game Is Serious in Berlin and is a published board game designer.
Sources: SPICED, Winning by Design · The origins of MEDDIC, Jack Napoli · Who created MEDDIC?, MEDDICC