LaunchWeek.ai

Back to Day 4: Convert

Sales Discovery Call Playbook: The Questions That Decide Whether You Have a Deal Or a Tire-Kicker

Most founders running their first sales calls jump straight to demo. The prospect says "show me the product"; the founder demos enthusiastically; the prospect says "looks great, send me a quote"; the deal stalls forever. The missing step: discovery — the call BEFORE the demo where you find out whether this prospect actually has a problem you solve, has budget, has urgency, and has authority. Done well, discovery turns 30-min calls into qualified pipeline. Done badly, you demo to anyone who'll click "book a call" and waste 6 months in your forecast.

A working discovery playbook answers: what to learn (problem / impact / process / people / timeline / budget), how to ask (open-ended; layered), how to qualify (MEDDPICC / BANT / your variant), how to capture notes, when to advance vs disqualify, what NOT to demo on the call, and how to set up the next step. Distinct from sales-demo-calls (the demo itself) and from cold-outreach (getting the call).

This guide is the playbook for running discovery calls. Companion to Sales Demo Calls, Sales Playbook, Demo Request Flow, B2B Procurement Navigation, Enterprise POC Management, Sales Onboarding Ramp, and First Sales Hire.

What Done Looks Like

By end of this exercise:

  • Standard discovery framework picked (MEDDPICC / BANT / SPICED / etc.)
  • 15-25 question bank with branching logic
  • Discovery call structure: 30-45 min agenda
  • Note-taking template (Salesforce / HubSpot / Gong-friendly)
  • Disqualification criteria — knowing when to walk
  • Advance criteria — knowing when to set up demo / POC
  • Recording + review cadence
  • Pipeline stages aligned to discovery progress

This pairs with Sales Demo Calls, Sales Playbook, Demo Request Flow, B2B Procurement Navigation, Enterprise POC Management, Sales Onboarding Ramp, First Sales Hire, Cold Outreach, Customer Discovery Interviews, Pricing Strategy, Pricing Packaging Tier Design, Annual Contract Negotiation, Win Loss Analysis, and Customer References.

Why Discovery Matters More Than Demo

Help me understand the value model.

The math:

**Without discovery**:
- 50% of demos go nowhere (wrong fit)
- 25% stall (no champion / no budget)
- 25% close

Win rate: 25%
Sales cycle median: 90 days
AE time per close: hours of demo + follow-up wasted on bad fits

**With good discovery**:
- 30% disqualified BEFORE demo (saved time)
- Of remaining 70%: 60% close
- Effective win rate of demos: 60%

Win rate of leads: 42% (70% × 60%)
Sales cycle: 45-60 days (faster because better-qualified)
AE time per close: half the wasted demos

**The mindset shift**:

Bad sales: "How do I close this person?"
Good sales: "Is there a deal here, and if so, what does it look like?"

Discovery determines the second; demo serves it.

For my company:
- Win rate today
- Demo:close ratio

Output:
1. Current state
2. Gap to good
3. Where discovery would help

The mistake to avoid: demoing on every call. The product is exciting; you want to show it. But every demo without discovery is a leak. Force yourself to discovery first.

The Discovery Frameworks

Multiple frameworks; pick one.

Help me pick a framework.

The major frameworks:

**BANT (the classic; weakening)**:
- Budget — do they have money?
- Authority — can they buy?
- Need — do they have the problem?
- Timeline — when do they need solution?

Pros: simple; widely-known
Cons: too transactional for modern B2B; misses champion / process

**MEDDIC (the late-90s update)**:
- Metrics — what numerical impact would solving this have?
- Economic buyer — who has budget authority?
- Decision criteria — what factors decide the choice?
- Decision process — how does an enterprise buy?
- Identify pain — what problem is real?
- Champion — who internally fights for you?

Pros: rigorous; used by enterprise SaaS
Cons: complex for SMB; can feel formal

**MEDDPICC (MEDDIC++; modern enterprise)**:
- M, E, D, D, I, C from MEDDIC
- Paper process — what's the procurement / legal flow?
- Competition — who else are they evaluating?

Pros: most thorough; what enterprise companies use
Cons: overkill for transactional sales

**SPICED (HubSpot's modern variant)**:
- Situation — context
- Pain — problem
- Impact — what changes if solved
- Critical event — why now?
- Decision — process / criteria

Pros: tighter than MEDDPICC; works mid-market
Cons: less recognized than BANT

**SPIN (Neil Rackham; consultative classic)**:
- Situation — context questions
- Problem — pain questions
- Implication — what's it costing them?
- Need-payoff — what would solving be worth?

Pros: question-flow oriented; coachable
Cons: doesn't cover budget / process

**The 2026 recommendation by ACV**:

- $0-5K ACV: BANT (light); fast cycles
- $5K-50K ACV: SPICED or SPIN
- $50K-500K ACV: MEDDIC
- $500K+ ACV: MEDDPICC

For my motion:
- Average ACV
- Cycle complexity

Output:
1. Framework pick
2. Why
3. Customizations

The pragmatic answer for indie / mid-market SaaS: SPICED. It's modern, focused, and covers the essentials without enterprise-process overload.

The Question Bank

Help me build a question bank.

The structure (using SPICED as example):

**Situation questions (5 min; "tell me about your world")**:

- What's your role? What do you do day-to-day?
- Tell me about your team / company / function.
- What does your tech stack look like? What tools are you using today?
- How long have you been doing X?
- Walk me through your current process for [the thing we solve].

**Pain questions (10 min; "where does it hurt")**:

- What's the most frustrating part of [current process]?
- When did you realize [problem] was a problem?
- What've you tried to solve this? Did it work?
- If you could wave a magic wand, what would change?
- What's the cost of NOT solving this?

(The trick: questions go from observable to emotional. People reveal more on the second / third round.)

**Impact questions (5-10 min; "what changes if we fix this")**:

- If you solved this, what would change for you / the team / the business?
- How would you measure success? (Looking for numbers)
- What's the financial impact of [problem] today? (Cost of inaction)
- Who else is affected by this besides you?
- What's the biggest win this would unlock?

**Critical event questions (5 min; "why now")**:

- Why are you looking at this now (vs 6 months ago)?
- What changes if this isn't solved by [date]?
- Is there a deadline / event forcing this?
- What's the consequence of doing nothing for another quarter?

(If "no critical event" — this is a weak signal. Discovery may end here.)

**Decision questions (10 min; "how do you actually buy")**:

- Walk me through how a tool like this would get bought at your company.
- Who else needs to be involved in the decision?
- What does your boss / their boss think about this?
- What's your budget cycle? When does the next budget window open?
- What would procurement / IT / security need from us?
- Have you bought tools like this before? How did that go?
- What other vendors are you evaluating?
- If we were the right fit, what would your timeline look like?

**Champion-development questions (woven throughout)**:

- (Listening for) Are they personally invested? Will they fight for this?
- What's THEIR stake? Career win? Pain relief? Bonus?
- Who could block this internally? Why?

For my product: [adapt]

Output:
1. 25 questions adapted to your product
2. Branching logic
3. Disqualifying answers

The discipline: listen 70% of the call. Most founders run discovery and talk 80%. Reverse it. Long pauses after questions get truthful answers. Most prospects fill silence with information.

Call Structure: 30-45 Minute Agenda

Help me structure the call.

The agenda (30-min variant):

**Open (2 min)**:
"Thanks for taking time. Here's how I'd love to use our 30 min:
- 5 min: introduce myself + Acme briefly
- 20 min: learn about you + your situation
- 5 min: discuss next steps
Sound good?"

(Setting expectations builds trust + reserves their patience for discovery.)

**Brief intro (5 min)**:
"Acme helps [audience] do [outcome] without [pain]. We're at [stage]; about [size]; customers like [logo]. I'd love to learn whether we're a fit before showing anything."

(Don't pitch; just situate. Demo comes later if they want it.)

**Discovery (18-20 min)**:
- Situation / pain / impact / critical event / decision
- Layer follow-ups
- Take notes; reflect back ("So what I'm hearing is...")

**Recap + qualifying (3-5 min)**:
"Quick recap: you're dealing with X; the cost is Y; you'd ideally fix this by Z; your decision involves [people]. Is that right?"

(Reflecting back proves you listened; surfaces miscommunications.)

**Next steps (3-5 min)**:

If qualified:
"Based on what you've shared, I think we're a fit. Here's what I'd suggest:
- I'll send a brief recap by end of day
- Let's book a 45-min demo for [date], with [you + manager + technical lead]
- I'll share our security/compliance docs in advance for your IT team"

If unqualified:
"I appreciate the time. Based on what you've shared, I don't think Acme is the right fit because [honest reason]. If [conditions change], let's reconnect."

If unsure:
"Let me think on what you've shared. I'll follow up tomorrow with either a proposed next step or honest feedback."

**Close-out**:
"Anything I should have asked but didn't?"

(Often surfaces the real concern they were holding.)

For my call:
- Length
- Variations

Output:
1. Agenda template
2. Time per section
3. Adaptation by call length

The "anything I should have asked" question is the secret weapon: prospects often hold back the real concern until you explicitly invite it. Use the question; wait through silence.

Disqualifying: Knowing When to Walk

Help me build disqualification rules.

The signals to walk away:

**Hard disqualifiers** (end the call gracefully):

- "We're just doing research; not buying for 6+ months" (no critical event)
- "I don't have budget; I'd need to pitch to leadership" (no economic buyer engagement; not a champion)
- "We're locked in with [competitor] for the next 2 years" (timing wrong)
- "We're 50 employees" (when your ICP is 1000+)
- "Our CTO has to evaluate every tool" (long process, no immediate path)
- "Just sent your link to my team; not sure who'll be involved" (low engagement)

The graceful walk:
"Based on what you've shared, I don't think Acme is the right fit right now. We typically work with [ICP] who [trigger]. If [conditions change], I'd love to reconnect. Best of luck with [their goal]."

This frees:
- Their time (no demo they don't need)
- Your time (no zombie pipeline)
- The relationship (honesty preserves future opportunity)

**Soft disqualifiers** (advance with caution):

- "I'm new to this role; figuring out what we need"
- "We have a tool but it's not quite right; not urgent though"
- "I'm not the decision-maker but my boss might be"

These can advance, but with explicit checkpoints:
"To make sure we don't waste each other's time, can you bring [decision-maker] to the demo?"

If they can't / won't → real disqualifier hidden.

**Counter to common founder bias**:

Founders WANT to advance every prospect because pipeline = hope.
But unqualified pipeline rots forecasts.
Discipline is to disqualify when signals say so.

For my motion:
- Top 3 disqualifiers in your category
- Walk script

Output:
1. Hard / soft / advance criteria
2. Scripted walk-aways
3. Pipeline impact estimate

The contrarian discipline: walk away from 30-50% of discovery calls. If you're advancing 95%+, your bar is too low; pipeline is full of stalls. If you're walking from 60%+, your top-of-funnel is bad; fix qualification at lead stage.

Champion Development

Help me develop champions.

A champion is someone INSIDE the prospect company who actively wants this to happen and will fight internally.

**Champion vs not-champion**:

Champion:
- Has personal stake (career win, real pain, bonus)
- Knows the budget process
- Will introduce you to others (manager, IT, end users)
- Returns your messages quickly
- Sends you internal context unprompted

Not-champion:
- Asked because boss said to
- Doesn't know the process
- Slow to respond
- Won't introduce you
- "Let me check with my team" (where 'team' is opaque)

**Identifying champion early**:

In discovery, listen for:
- Personal investment language: "I've been pushing for this"
- Specific career stakes: "If I solve this, I get [outcome]"
- Frustration with status quo: deeply felt, not abstract
- Returning from prior tools / categories: "I've used X before"

If discovery surfaces a champion, advance.
If not, find one before advancing — or politely disqualify.

**Developing champion further**:

After discovery:
- Send recap; ask them to forward to manager / team
- Provide ammo: ROI calculator, comparison docs, customer-quote
- Co-create the internal pitch with them
- Schedule meeting with their manager (champion intros you)
- Make them look smart

The champion-development arc:
1. Identify in discovery
2. Equip with materials
3. Help them build internal coalition
4. Co-pitch to economic buyer
5. Close

Without a champion, deals stall. With a champion, deals close 5-10x faster.

For my deals:
- Champion-identification heuristics
- Equipment kit (ROI calc, deck, references)

Output:
1. Champion criteria
2. Discovery questions to find them
3. Equipment per stage

The hardest discipline: walk away from a "warm" deal with no champion. The prospect is friendly; says nice things; never advances. Without a champion fighting internally, you're dead in the water. Better to walk and find a real champion elsewhere.

Note-Taking + CRM Hygiene

Help me capture discovery efficiently.

The note structure (during call):

Date: 2026-04-30 Prospect: Jane Smith, VP Eng, Acme Corp Call type: Discovery (1st call)

Situation:

  • Acme Corp; 200 employees; B2B SaaS for retail
  • Jane: VP Eng; reports to CTO; 40-person team
  • Stack: AWS, React, Node.js, Postgres, Datadog

Pain:

  • Currently using [competitor] for [function]
  • Pain point #1: [specific quote]
  • Pain point #2: [specific quote]
  • Cost of inaction: [their words]

Impact:

  • If solved: estimate savings $X / time Y / capability Z
  • Measurement: [their KPIs]

Critical event:

  • [Why now]
  • Deadline: [if mentioned]

Decision process:

  • Other vendors evaluated: [list]
  • Decision-makers: [Jane + her CTO + IT + Procurement]
  • Budget: [stated or "to be determined"]
  • Timeline: [stated]
  • Procurement: [requirements]

Champion signals:

  • [Yes / No / Strength]
  • [Personal stake]

Next step:

  • Send recap by EOD
  • Demo on [date] with [people]
  • Share [docs] in advance

Honest assessment:

  • Qualification score: [Low / Medium / High]
  • Why

After call:

1. Send recap email within 24h (locked in their memory; surfaces miscommunications)
2. Update CRM with structured fields
3. Share notes with internal team (not just "had a call; good")
4. Pipeline stage updated

**CRM hygiene**:

Field discipline:
- Stage = where this REALLY is (not where AE wishes)
- Next step = concrete date + action
- Blocker = if any
- Champion = name if applicable; "none yet" if not

Stages:
1. Discovery scheduled
2. Discovery completed
3. Demo scheduled
4. Demo completed
5. POC / paid pilot (if applicable)
6. Proposal
7. Negotiation
8. Closed-won / Closed-lost

Don't skip; don't fudge.

For my CRM:
- Tool (Salesforce / HubSpot / etc.)
- Field structure

Output:
1. Note template
2. CRM field structure
3. Stage definitions

The leadership reality: AEs hate CRM hygiene; founders need it. Without disciplined CRM, you can't forecast, can't see patterns, can't coach. Build the discipline early; require it; review weekly.

Recording + Review Cadence

Help me set up recording and review.

The 2026 standard:

Record EVERY discovery call (with consent). Don't try to remember.

**Tools**:
- **Gong** — enterprise standard; expensive ($150-300/seat/mo)
- **Chorus.ai** — alternative; ZoomInfo-owned
- **Avoma** — modern mid-market
- **Fireflies.ai** — affordable indie
- **Tactiq** — browser extension; cheap
- **Otter.ai** — basic transcription

Even at indie scale, $50-100/mo on Fireflies / Avoma pays for itself in deal velocity.

**What recordings give you**:

- Searchable transcripts (find "they mentioned competitor X")
- Coaching material (review junior AE calls)
- Truth-checking (was champion really committed?)
- Win-loss analysis input
- AI-generated summaries (Gong / Avoma do this well)

**Review cadence**:

Weekly (founder / sales leader): random-sample 2 calls; coach 1
Monthly: review patterns (what's getting lost in handoffs; common objections; pricing pushback)
Quarterly: pull insights into product / messaging

**Coaching pattern**:

For 30-min call, watch 10 min:
- First 5: did they set agenda? listen?
- Middle 3: how did they handle objections?
- Last 2: was next step concrete?

Coach on 1 specific thing per call. Don't dump all feedback.

**Privacy**:

- Always announce recording at start of call
- Comply with state laws (US: 1-party vs 2-party consent states)
- EU: GDPR consent
- Honor "off-the-record" requests; pause recording

For my team:
- Tool budget
- Review owner

Output:
1. Tool pick
2. Recording policy
3. Coaching cadence

The cheapest highest-leverage indie sales investment: call recording + AI summary. $50-100/mo lets you re-watch any call, share with team, build coaching library. Skip if budget-constrained; otherwise: buy.

Common Discovery Mistakes

Help me avoid mistakes.

The 10 mistakes:

**1. Demoing instead of discovering**
First call should reveal fit. Demo is reward for qualification.

**2. Not listening (talking >50%)**
Aim for 70/30 prospect/you ratio.

**3. No critical event**
"Why now?" is the most-skipped question. Without urgency, deals stall.

**4. Asking only "happy path" questions**
Ask about pain; cost of inaction; what's been tried + failed.

**5. Believing the qualification on faith**
"Yes I have budget" needs follow-up: "what's your fiscal year? when does next budget cycle open?"

**6. No champion development**
Without a champion fighting internally, you're not closing.

**7. Skipping decision process questions**
"Walk me through how this gets bought" is awkward but essential.

**8. Not setting next step on the call**
Vague "we'll be in touch" = stalled deal. Concrete next step (date + people).

**9. No recording / no notes**
Memory fails. Recording + structured notes = pipeline truth.

**10. Advancing every prospect**
Disqualification is a discipline, not a failure. Walk away from bad fits.

For my team: [risks]

Output:
1. Top 3 risks
2. Coaching focus
3. Process changes

The single most-painful mistake: advancing a deal without a confirmed champion. You demo; you negotiate; the deal stalls; six months later it dies. Discovery is where champion-presence is verified. Skipping = paying later.

What Done Looks Like

A working discovery process delivers:

  • Framework picked (SPICED / MEDDPICC) and consistently applied
  • Question bank used by all AEs
  • 30-45 min agenda with discovery > demo time
  • 30-50% disqualification rate (yes, walking away)
  • Champion identified before demo advance
  • Recap email within 24h of every call
  • CRM updated with structured discovery data
  • Recordings + AI summaries on every call
  • Weekly call review by sales leadership
  • Demo:close ratio >40% (high-quality demos because qualified)
  • Sales cycle median 30-50% shorter than pre-discovery-discipline

The proof you got it right: when an AE says "I just had a call with X," you can read the discovery notes and predict whether the deal will close — because the notes contain critical-event, champion, and budget signals. Surprises in pipeline are rare.

See Also

← PreviousRun Sales Demo Calls That CloseNext →Sales Onboarding & Ramp: Get a New Rep to Quota in 90 Days (Not 9 Months)