Sales Discovery Frameworks: SPIN, BANT, MEDDIC and Friends
Let's start with a worry you might have. "Frameworks" sounds like a cold, salesy word. You picture someone reading a script at you. That is not what this chapter is about. A sales framework is just a list of things worth finding out on a call, in a sensible order. Think of it as a checklist a doctor keeps in their head, not a speech.
First, two plain-English definitions you'll need all chapter:
- Discovery
- The part of a conversation where you learn about the other person's situation and problems — before you talk about your product. Most of selling is discovery.
- Qualification
- Deciding whether this person is actually a good fit to buy — so you don't waste weeks chasing someone who was never going to say yes.
The golden rule before any framework: talk less
Gong, a company that records and analyzes huge numbers of real sales calls, found that on discovery calls the best-performing reps talk about 46% of the time and listen 54%. The worst performers talk around 72% of the time. So the single biggest skill is closing your own mouth. Every framework below is really just a way to spend your listening time well.
SPIN Selling — the discovery framework to learn first
SPIN comes from Neil Rackham, who studied over 35,000 real sales calls over 12 years and wrote the book SPIN Selling (1988). It is still the best starting point for a founder because it's built entirely on asking questions in a smart order. SPIN is four types of question:
- S — Situation
- Facts about how things work today. (Background.)
- P — Problem
- What's frustrating, broken, or hard right now.
- I — Implication
- What that problem costs them — in money, time, or stress. This makes the pain feel bigger.
- N — Need-payoff
- What life would look like if the problem were solved. You let them describe the value.
The genius is the order: you move from harmless facts, to a sore spot, to why the sore spot matters, to the buyer talking themselves into wanting a fix. Rackham's research showed the I and N questions are what actually move bigger deals — most beginners skip them.
Here are copy-able example questions for each letter. Steal these:
| Type | Example questions you can say out loud |
|---|---|
| Situation | "Walk me through how your team handles this today." · "What tools are you using for that right now?" |
| Problem | "Where does that process tend to break down?" · "What's the most frustrating part of doing it that way?" |
| Implication | "When that happens, what does it cost you — in hours or in lost sales?" · "How does that affect the rest of your team?" · "If nothing changes, where does this leave you in six months?" |
| Need-payoff | "If you could fix that, what would that be worth to you?" · "How would your week look different if this just worked?" |
Worked example: SPIN on a real B2B SaaS call
Imagine you sell software that auto-generates print-ready PDFs (very close to home for a print-SaaS founder). You're talking to the owner of a small print shop.
You (Situation): "How do your customers send you their artwork right now?"
Owner: "They email me files, and honestly half of them are the wrong size or low resolution."
You (Problem): "What happens when a file comes in wrong?"
Owner: "I email them back, we go back and forth, sometimes three or four times."
You (Implication): "Roughly how many hours a week does that back-and-forth eat up? And do you ever lose the order because of it?"
Owner: "Easily six or seven hours. And yeah — maybe two or three jobs a month just walk away because it's too slow."
You (Implication, going deeper): "If each of those jobs is worth, say, $200, that's a few hundred dollars a month plus a full workday gone. Is that about right?"
Owner: "...when you put it like that, it's worse than I thought."
You (Need-payoff): "If customers could only ever upload a file that was already print-ready — no wrong sizes, no back-and-forth — what would that be worth to you?"
Owner: "Honestly? That would change my whole week. How does your thing do that?"
Notice: the owner asked you to pitch. That's the goal. You never pushed. The questions did the work.
Qualification frameworks — is this deal even real?
Once you understand the problem, you check whether they can actually buy. Three names you'll hear:
BANT — the simple old-school checklist
Created by IBM in the 1950s. Four things to confirm:
- Budget — can they afford it / is money set aside?
- Authority — is this person able to say yes, or do they need a boss?
- Need — is the problem real and worth solving?
- Timeline — when do they want this fixed?
BANT is easy to remember and fine for small, simple sales. But it was built for a world with one decision-maker and a fixed budget. Today a B2B deal can involve 6–10 people, so don't treat it as a rigid "fail one, reject them" test. Use it as gentle questions: "Have you set aside budget for this, or are we still building the case?" · "Besides you, who else would weigh in on a decision like this?"
MEDDIC / MEDDPICC — for bigger, complex deals
MEDDIC was created inside the company PTC in 1996. It's a deeper checklist for expensive deals with many stakeholders. The letters:
- Metrics — the numbers that prove value (e.g. "saves 6 hours/week").
- Economic buyer — the one person who controls the money.
- Decision criteria — what they'll judge the choice on.
- Decision process — the steps they'll go through to buy.
- Identify pain — the real problem (same idea as SPIN's P and I).
- Champion — an insider who wants you to win and will fight for you internally.
MEDDPICC adds two more: Paper process (the legal/procurement paperwork that quietly kills deals) and Competition (who else they're considering, including doing nothing). Use MEDDIC only when deals get large and slow. For most early founders it's overkill — but knowing "do I have a Champion?" and "who is the Economic buyer?" is genuinely useful even on small deals.
GAP Selling and the Sandler Pain Funnel — two great extras
GAP Selling (from the author Keenan) is one simple, powerful idea: find the gap between their current state (where they are now, and what it costs) and their future state (where they want to be). The bigger the gap, the more they want to buy. Your job is to make the gap clear and concrete. SPIN's Implication questions are how you measure that gap.
The Sandler Pain Funnel (from David Sandler) is a sequence of gently deepening questions that lets the buyer convince themselves. Lines you can copy:
Putting it together — which framework, when
EARLY in a call LATER in a call ----------- ----------- SPIN / Pain Funnel ---> BANT (small deal) (understand problem) MEDDIC (big deal) GAP (size the gap) Champion + Econ buyer check
| Framework | What it's good for | When to use it |
|---|---|---|
| SPIN | Asking great questions, uncovering pain | Every discovery call — learn this first |
| GAP Selling | Making the cost of the problem vivid | When the buyer downplays their pain |
| Sandler Pain Funnel | Letting buyers talk themselves into change | When you sense real but unspoken frustration |
| BANT | Quick fit-check on simple deals | Small, fast sales with one decision-maker |
| MEDDIC / MEDDPICC | Managing big, multi-person deals | High price, 5+ stakeholders, 90+ day cycles |
Key takeaways
- A framework is a checklist and a lens, not a script — adapt it, never recite it.
- Talk less than half the time; top reps listen 54% of a discovery call (Gong).
- SPIN (Situation → Problem → Implication → Need-payoff) is the one to master first — its power is in the Implication and Need-payoff questions most people skip.
- Discovery comes before qualification: understand the problem, then check if the deal is real.
- BANT for simple deals, MEDDIC/MEDDPICC for big complex ones — and always know your Champion and Economic buyer.
- GAP Selling sizes the distance between today's pain and the desired future; a bigger gap means more motivation to buy.
- The Sandler Pain Funnel uses gentle, deepening questions so buyers convince themselves — let silence and curiosity do the work.