---
name: discovery-call-design
slug: discovery-call-design
description: This skill should be used when the user asks to "design a discovery call", "structure a discovery call", "build a discovery call framework", "plan a discovery call", "improve discovery calls", "create a discovery call template", "design the first sales call", "structure a qualification call", "build a discovery call playbook", or any variation of designing the structure, questions, and flow of a B2B SaaS discovery call.
category: general
---

# Discovery Call Design

A discovery call is the first real conversation between a sales rep and a prospect. Its purpose is to understand whether there's a genuine fit between the prospect's problem and your solution. Not to pitch. Not to demo. Not to close. To discover. The output is a decision: advance to the next stage (demo, evaluation, proposal) or disqualify and move on.

The principle: the prospect should talk 60-70% of the time. If the rep is talking more than 40%, they're pitching, not discovering. Every question should surface information that helps determine fit, urgency, and next steps.

## The Discovery Call Structure

### The 30-minute framework

| Phase | Minutes | Purpose | Rep talk % |
|-------|---------|---------|-----------|
| 1. Open | 0-3 | Set the agenda. Build rapport. Establish the format | 60% (setting context) |
| 2. Situation | 3-10 | Understand their current state. What do they do today? | 20% (asking questions) |
| 3. Problem | 10-18 | Surface the specific pain. What's broken? What's the impact? | 20% (digging deeper) |
| 4. Implication | 18-22 | Quantify the cost of the problem. What happens if they don't fix it? | 30% (connecting dots) |
| 5. Process | 22-26 | Map the buying process. Who's involved? What's the timeline? | 30% (understanding mechanics) |
| 6. Close | 26-30 | Propose next steps. Confirm mutual interest | 50% (proposing action) |

### Phase 1: Open (3 minutes)

**Purpose:** Set expectations for the call. The prospect should know what will happen and feel comfortable.

**Script framework:**
```
"Thanks for taking the time, {name}. Here's what I'd love to
do in the next 30 minutes:

First, I'd like to understand how your team handles [problem
area] today and what's working or not working.

Then, if it makes sense, I'll share a bit about how we approach
it and we can decide together if there's a reason to keep
talking.

Does that work? Anything you want to make sure we cover?"
```

**Open rules:**
- **Always set an agenda.** A call without an agenda feels aimless. The prospect doesn't know when they'll get to ask questions or when the pitch starts. Set the structure upfront
- **Get their input on the agenda.** "Anything you want to make sure we cover?" gives them ownership. If they say "I mainly want to understand pricing," now you know their priority
- **Don't spend 10 minutes on rapport.** "How's the weather in Austin?" burns time. One brief personal comment is fine. Then move to business. Prospects respect efficiency

### Phase 2: Situation (7 minutes)

**Purpose:** Understand their current state before exploring problems. You can't diagnose what's broken without knowing what exists.

**Key questions:**

| Question | What it reveals |
|----------|----------------|
| "Walk me through how your team handles [process] today." | Current workflow. Tools. Team structure |
| "How many people are involved in [process]?" | Team size. Complexity. Potential deal size |
| "What tools are you using for [area] right now?" | Current stack. Incumbent competitors. Integration needs |
| "How long have you been doing it this way?" | If recent = still evaluating. If years = entrenched process |
| "What prompted you to take this call today?" | The trigger. Why now, not 6 months ago |

**Situation rules:**
- **Don't ask questions you could answer with research.** "What does your company do?" wastes the prospect's time. Research this before the call. Ask about the specific process you affect, not the company overview
- **"What prompted you to take this call?" is the most important situation question.** The answer reveals the trigger (signal) that made them open to a conversation. This is the foundation of the entire deal
- **Limit situation questions to 5-7 minutes.** Spending 15 minutes on the current state leaves no time for problem exploration. Get the lay of the land and move to pain

### Phase 3: Problem (8 minutes)

**Purpose:** Surface the specific pain. Not hypothetical problems. Real, felt problems that the prospect cares about today.

**Key questions:**

| Question | What it reveals |
|----------|----------------|
| "What's the biggest challenge with [process] right now?" | Their #1 pain. The thing that keeps them up at night |
| "When [problem] happens, what's the impact on your team?" | Downstream effects. Helps quantify the cost |
| "How often does [problem] occur?" | Frequency. Daily pain is more urgent than quarterly pain |
| "What have you tried to fix it?" | Prior attempts. What didn't work. What they're willing to do differently |
| "On a scale of 1-10, how much of a priority is solving this?" | Self-reported urgency. Calibrates whether they'll actually act |

**Problem discovery techniques:**

| Technique | How it works | Example |
|-----------|-------------|---------|
| Peeling the onion | Ask "why" or "what happens then" to go deeper on each answer | "You said reply rates dropped. What happened when they dropped? How did that affect pipeline?" |
| Negative question | Ask about what's NOT working instead of what is | "What's the most frustrating part of your current process?" vs "How's your current process?" |
| Hypothetical removal | Ask what happens if the problem disappears | "If reply rates went from 3% to 10% tomorrow, what would that change for your team?" |
| Peer comparison | Reference what similar companies experience | "Most teams at your stage tell us [X]. Are you seeing the same thing?" |
| Quantification probe | Ask for numbers | "Roughly how much time does your team spend on [task] per week?" |

**Problem rules:**
- **Go deep on one problem, not wide on five.** A prospect mentions 4 challenges. Don't explore all 4. Pick the one with the most energy behind it and drill deep. Depth beats breadth
- **Listen for emotion.** When the prospect's voice changes (frustration, excitement, relief), you've hit a real pain point. Lean in. Ask more about that specific point
- **Don't solve during discovery.** The rep hears a problem and immediately says "We solve that! Let me show you." Resist. Keep asking questions. Understanding the full picture before proposing a solution produces better demos and higher close rates
- **The prospect must articulate the problem in their own words.** If you're the one describing the problem and they're nodding, you don't have a confirmed need. You have a hypothesis. Push them to say it: "How would you describe the main challenge?"

### Phase 4: Implication (4 minutes)

**Purpose:** Help the prospect connect the problem to a business impact. Problems without impact don't get prioritized. Problems that cost revenue, time, or competitive position do.

**Key questions:**

| Question | What it reveals |
|----------|----------------|
| "What does this problem cost you? In time, revenue, or headcount?" | Quantified impact. The foundation of the business case |
| "What happens if this doesn't get fixed this quarter?" | Urgency test. Does the problem get worse, or is it stable? |
| "How does this affect your ability to hit [their goal/quota/target]?" | Ties the problem to their personal KPIs |
| "Who else on the team is affected by this?" | Maps the scope. If it affects 3 departments, the impact is bigger than one person's frustration |
| "Have you tried to fix this before? What happened?" | Prior failed attempts raise the stakes. "We tried X and it didn't work" = they've invested effort |

**Implication rules:**
- **Help them do the math.** "Your 5 SDRs spend 3 hours each on research daily. That's 15 hours/day, 75 hours/week, ~$75K/year in SDR time spent on manual work." This math builds the business case they'll need for internal approval
- **If the problem has no business impact, it won't get budget.** "It's annoying" is not a business impact. "It's costing us $75K/year in wasted SDR time" is. If you can't quantify the impact, the prospect can't justify the purchase
- **Don't spend more than 4 minutes here.** Implication questions are powerful but heavy. Too many feels like you're trying to scare them into buying. 2-3 implication questions is enough

### Phase 5: Process (4 minutes)

**Purpose:** Map the buying process. Who else is involved? What's the timeline? How do they typically buy tools like this?

**Key questions:**

| Question | What it reveals |
|----------|----------------|
| "If this moves forward, who else would need to be involved?" | Buying committee. Authority mapping |
| "Walk me through how your team has made a purchase like this before." | Decision process. Formal or informal |
| "Is there a specific event or deadline driving the timeline?" | External urgency. Contract renewal, board meeting, fiscal year |
| "Would this come from an existing budget, or would it need separate approval?" | Budget process. Allocated vs discretionary |
| "What would need to be true for you to feel confident moving forward?" | Their success criteria. What does "yes" look like to them |

**Process rules:**
- **Always ask "who else would be involved."** This is the multi-threading entry point. The answer maps the buying committee. If they say "just me," push gently: "Sometimes teams bring in IT for security review or finance for procurement. Would that apply here?"
- **"How have you made a purchase like this before?" reveals the real process.** Not the theoretical process. The actual process from the last time they bought a SaaS tool. That's the process this deal will follow
- **Don't skip process because the conversation is going well.** Excited prospects who love the problem-solution fit still stall on procurement, legal, and budget approval. Map the process now, not after the proposal

### Phase 6: Close (4 minutes)

**Purpose:** Propose a clear next step. The discovery call should end with a specific action and a date.

**Good closes:**

| Scenario | Next step proposal |
|----------|-------------------|
| Strong fit, need confirmed, authority present | "Based on what you've shared, I'd love to show you how we handle [specific problem]. Can we set up a 45-minute demo for [specific date] and include [stakeholder name]?" |
| Strong fit, need confirmed, need to loop in others | "This sounds like a great fit. You mentioned [VP name] would need to weigh in. Can I set up a brief call with you and [VP name] to walk through the approach?" |
| Moderate fit, need to evaluate further | "I think there could be a fit here, but I want to make sure. Can I put together a brief assessment of how we'd approach [their problem] and review it with you next week?" |
| Weak fit, not qualified | "I appreciate you sharing all this. Based on what you've described, I'm not sure we're the right fit for [specific reason]. I don't want to waste your time." |

**Close rules:**
- **Always propose a specific next step with a specific date.** "Let's reconnect sometime next week" = the deal dies. "Can we do Tuesday at 2pm with your VP?" = the deal advances
- **Include the right people in the next meeting.** If the champion mentioned a VP needs to be involved, the next meeting should include the VP. Don't schedule another 1:1 with the champion when the committee needs to be there
- **Disqualify honestly.** If the prospect doesn't qualify, say so clearly and kindly. "I don't want to waste your time" is more respectful than stringing them along for 3 more meetings. They'll remember the honesty if circumstances change later
- **Summarize what you heard before proposing next steps.** "So if I'm hearing you right, the main challenge is [problem], it's costing about [impact], and you'd like to have something in place by [timeline]. Does that capture it?" This confirms alignment and shows you listened

---

## Discovery Call Preparation

### Pre-call research (10-15 minutes per prospect)

| Research area | Where to find it | Why it matters |
|-------------|-----------------|---------------|
| Company overview | Website, Crunchbase, LinkedIn | Don't ask "what does your company do" on the call |
| Prospect's role and tenure | LinkedIn profile | Understand their authority level and whether they're new in role |
| Recent company signals | Crunchbase (funding), LinkedIn Jobs (hiring), press | Conversation hooks. "I saw you just raised" or "saw the RevOps posting" |
| Current tech stack | Job postings, BuiltWith, G2 reviews | Know what they use before asking. Focus the call on gaps |
| Competitive landscape | G2 reviews, LinkedIn activity | Know if they've looked at competitors. Be ready to position |
| MQL/lead source | CRM | What action brought them here? Demo request, content download, outbound reply? Tailor the opener accordingly |

### Pre-call preparation rules

- **10-15 minutes is the right investment.** Less than 10 and you'll ask questions you should already know. More than 15 and you're over-preparing for a 30-minute call
- **Write down 3 specific questions based on your research.** Not generic questions from a list. Questions tailored to this prospect. "Your LinkedIn says you're building the SDR function. What made you decide to build vs outsource?" 
- **Have your hypothesis ready.** Before the call, form a hypothesis about their problem based on your research. "Based on their stage and hiring, they're probably struggling with [X]." The hypothesis directs your questions. Validate or invalidate it during the call
- **Know their MQL source.** If they requested a demo, they're further along than if they downloaded a whitepaper. Adjust your opener: "You requested a demo. What specifically were you hoping to see?" vs "You downloaded our outbound playbook. What caught your eye?"

---

## Discovery Call Do's and Don'ts

### Do's

| Do | Why |
|----|-----|
| Ask open-ended questions | "Tell me about..." and "Walk me through..." produce better answers than "Do you have..." |
| Take notes visually (share screen or show you're noting key points) | Signals you're listening and their answers matter |
| Summarize back what you heard | "So the main challenge is..." confirms understanding and shows respect |
| Ask "what else?" after every answer | The first answer is the surface answer. The second answer is the real one |
| Name the specific problem before proposing next steps | The prospect should hear their problem articulated back to them before seeing a solution |
| Send a recap within 2 hours | Per post-demo-followup skill. Reinforces what was discussed and locks in next steps |

### Don'ts

| Don't | Why |
|-------|-----|
| Pitch the product during discovery | Discovery is for understanding, not selling. Premature pitching kills trust and reduces close rates |
| Share your screen unless asked | Sharing your screen shifts the dynamic from conversation to presentation. Keep it conversational |
| Ask yes/no questions | "Do you have a problem with [X]?" gets "kind of." "Tell me about the biggest challenge with [X]" gets a real answer |
| Talk for more than 2 minutes straight | Any monologue longer than 2 minutes loses the prospect's attention. If you're talking that long, you're pitching, not asking |
| Skip to the demo when the prospect says "just show me the product" | "I want to make sure I show you the right things. A couple more questions will help me tailor the demo. [Question]." Then move to Phase 5 and close |
| End without a next step | "This was great, let's stay in touch" is not a next step. It's a slow death. Always propose a specific next meeting with a date |

---

## Adapting Discovery by Lead Source

| Lead source | Discovery adjustment | Why |
|------------|---------------------|-----|
| Demo request | Shorter situation phase. They know what they want. Move to problem quickly. May combine discovery + demo in one call | Highest intent. Don't over-qualify a prospect who's ready to evaluate |
| Content download MQL | Longer situation phase. They may not know your product well. Build context | Lower intent. They engaged with content, not a product. More discovery needed |
| Outbound cold reply | Skip "what does your company do." You researched them. Start with "What made you reply?" | You chose them. You already know their company. Discover their reaction to your signal |
| Referral intro | Ask who referred them and what context was shared. "What did [referrer] tell you about us?" | Warm intro. Some discovery is pre-done. Don't re-cover what the referrer already shared |
| Event follow-up | Reference the event and any conversation. "We talked at [event] about [topic]. Has anything changed since then?" | Warm context. Build on what was already discussed |
| Free trial / PQL | Skip product education. They've used it. Ask "What have you tried so far? What's working?" | They know the product. Discovery is about expanding usage and justifying the paid upgrade |

---

## Measurement

| Metric | Definition | Target | Frequency |
|--------|-----------|--------|-----------|
| Discovery-to-demo rate | % of discovery calls that advance to a demo/next meeting | 50-70% | Weekly |
| Discovery-to-opportunity rate | % of discovery calls that become opportunities | 30-50% | Monthly |
| Prospect talk ratio | % of call time the prospect spoke | 60-70% | Per call (use Gong, Chorus, or manual tracking) |
| Average discovery call length | How long the call lasted | 25-35 minutes | Weekly |
| Questions asked per call | Number of open-ended questions the rep asked | 8-12 | Per call |
| Next step booked on the call | % of discovery calls where a next meeting was scheduled before hanging up | > 80% | Weekly |
| Disqualification rate | % of discovery calls that resulted in a disqualification | 20-40% (healthy. It means you're qualifying, not just advancing everyone) | Monthly |

---

## Anti-Pattern Check

- Pitching the product in the first 10 minutes. The prospect mentions a problem and the rep immediately says "Great, let me show you how we solve that." This skips the rest of discovery. The rep doesn't understand the full picture. The demo will be generic. Keep asking questions
- Rep talks 70% of the time. The prospect got a pitch, not a discovery call. They leave feeling talked at, not heard. The rep misses critical information. Target 60-70% prospect talk time
- No pre-call research. "So, tell me about your company." This wastes 5 minutes on information that's on their website. Research before the call. Spend the call time on questions that only the prospect can answer
- Yes/no questions dominate. "Do you have a problem with outbound?" "Yes." "Do you have budget?" "Maybe." "Is this a priority?" "Sort of." Replace with open-ended questions: "Walk me through..." "Tell me about..." "What happens when..."
- Ending without a next step. "This was really helpful. I'll send you some info and we can reconnect." This is how deals die. Always propose a specific next step: "Can we do a demo on Tuesday at 2pm with your VP?"
- Skipping the process phase. The conversation went great. Strong need. Strong fit. But nobody asked about the buying process. Two months later the deal is stuck in procurement and nobody saw it coming. Always map the decision process
- Not disqualifying anyone. If 100% of discovery calls advance to the next stage, the qualification bar is too low. 20-40% disqualification is healthy. It means reps are qualifying honestly and not wasting the team's time on bad-fit deals
- Asking all BANT questions in the first 5 minutes. "Budget? Authority? Need? Timeline? OK, you're qualified." BANT is a framework for structured thinking over 30 minutes, not a 2-minute checklist. Weave the questions naturally through the conversation