# Discovery Call

> Structure and prepare for a sales discovery call. Use when the user says "prep for discovery call", "discovery call questions", "how to structure my discovery call", "first call with a prospect", "what to ask on a discovery call", "sales call prep", "plan my discovery call", "initial call framework", or wants to prepare for or debrief a first sales conversation.

- Skill: `qa-aman/discovery-call` (Agent Skill)
- Install (CLI): `npx skillmds@latest add qa-aman/discovery-call`
- Raw SKILL.md: https://api.skillmd.com/api/skills/qa-aman/discovery-call/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: qa-aman (https://skillmd.com/u/qa-aman)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/qa-aman/discovery-call

---


## Overview

Based on **"SPIN Selling"** by Neil Rackham. Rackham's 12-year, 35,000-call research study found that top performers don't pitch - they ask questions in a specific sequence that leads prospects to articulate their own pain and desired outcomes. The SPIN framework (Situation, Problem, Implication, Need-Payoff) structures discovery to surface explicit needs before any solution discussion.

## Workflow

### Step 1: Set call objectives before dialing

Define three things before the call starts:
- **Minimum outcome**: the one thing you must leave with (e.g., a confirmed pain point, a next meeting)
- **Ideal outcome**: what a perfect call ends with (e.g., confirmed budget, sponsor identified, demo scheduled)
- **Opening statement**: one sentence on why this call is worth their 30 minutes

Write these down. Do not improvise the opening.

### Step 2: Run Situation questions - establish context (5-8 min)

Gather facts about the prospect's current state. Keep this section short - prospects find these questions low-value. Limit to 3-4 questions.

Examples:
- "How does your team currently handle [relevant process]?"
- "How many people are involved in [relevant workflow]?"
- "What tools are you using today for [relevant area]?"

Do not ask questions whose answers are on their website or LinkedIn. That signals you didn't prepare.

### Step 3: Run Problem questions - surface dissatisfaction (8-12 min)

Shift to asking about difficulties, frustrations, and gaps. This is where top performers spend the most time.

Examples:
- "Where does that process break down for you?"
- "What's the biggest friction point when [relevant scenario] happens?"
- "How often does that cause issues downstream?"
- "What happens when it doesn't work the way you need it to?"

Listen for language that signals explicit pain. Write it down verbatim - you'll use their words back in your proposal.

### Step 4: Run Implication questions - expand the problem (5-8 min)

Make the prospect feel the cost of inaction. Connect the problem to business impact: revenue lost, time wasted, team morale, customer churn, competitive risk.

Examples:
- "When that breaks down, what's the downstream effect on [team/metric/customer]?"
- "How much time does your team spend working around that?"
- "What does that mean for your [quarterly target / renewal rate / customer satisfaction]?"
- "If this isn't solved in the next six months, what happens?"

You are not inventing urgency - you are helping them calculate the cost of the status quo.

### Step 5: Run Need-Payoff questions - let them sell themselves (5 min)

Ask questions that get the prospect to articulate the value of solving the problem. Do not pitch. Let them describe the benefit.

Examples:
- "If you could eliminate that friction, what would that unlock for your team?"
- "How valuable would it be to get that time back?"
- "What would it mean for your roadmap if this was no longer a bottleneck?"

The prospect describing the solution in their own words is worth more than any demo slide.

### Step 6: Confirm, summarize, and advance

Before ending the call:
1. Summarize what you heard: "So the core issue is [X], and if left unaddressed it impacts [Y]. Is that right?"
2. Confirm explicit interest: "Does solving this feel like a priority right now?"
3. Propose a specific next step with a date: "I'd like to put together a recommendation and walk through it with your team on [date]. Does that work?"

Never leave a call with "I'll follow up." Leave with a confirmed next step.

## Anti-Patterns

**1. Pitching too early**
Bad: "Great, sounds like you have [problem] - we actually solve that. Let me show you how..."
Good: Ask an Implication question to expand the problem before saying anything about your product.

**2. Asking Situation questions you could have researched**
Bad: "How many employees does your company have?"
Good: "Your team grew 40% last year - how has that affected your [relevant process]?"

**3. Treating a surface-level pain as a green light**
Bad: Moving to demo scheduling the moment a prospect says "yeah, that's a challenge for us."
Good: Follow up with an Implication question to understand scope and severity before advancing.

**4. Vague next steps**
Bad: "I'll send over some materials and we can reconnect."
Good: "Can we put 45 minutes on the calendar for Thursday at 2pm? I'll bring [specific deliverable]."

## Quality Checklist

- [ ] Wrote down minimum outcome and ideal outcome before the call
- [ ] Asked fewer than 5 Situation questions - did not over-research on the call
- [ ] Asked at least 2 Implication questions that tied the problem to business impact
- [ ] Asked at least 1 Need-Payoff question and let the prospect answer fully
- [ ] Captured the prospect's exact words for their pain and desired outcome
- [ ] Left the call with a specific next step confirmed (not "I'll follow up")
- [ ] Did not pitch the product before the prospect articulated an explicit need