sales
Discovery Call
The first sales conversation - focused on understanding the prospect's situation, not pitching.
Definition
A discovery call is the first real sales conversation. Its purpose is NOT to pitch your product - it's to deeply understand the prospect's situation, problem, decision process, and constraints. Reps who pitch in discovery lose deals; reps who ask great questions in discovery win them. The standard structure: rapport, agenda, current state questions, problem questions, impact questions, decision-process questions, next step. Frameworks like SPIN selling (Situation, Problem, Implication, Need-Payoff) formalize this.
The SPIN selling framework
Neil Rackham's SPIN selling (1988) remains the most validated US B2B discovery framework. The four question types in sequence. Situation: factual questions about the prospect's current state ('what tools do you use today,' 'how many people on your team'). Problem: questions surfacing pain ('where does the current setup break down,' 'what frustrates you about this'). Implication: questions amplifying the cost of the problem ('what does that delay cost you per month,' 'how does it affect customer satisfaction'). Need-Payoff: questions where the prospect articulates the value of solving it ('if you could cut that delay in half, what would that be worth'). Rackham's research across 35,000+ sales calls found that high performers asked dramatically more implication and need-payoff questions than low performers. Train reps on this sequence; do not let them improvise discovery.
MEDDIC and MEDDPICC for enterprise discovery
For US enterprise B2B sales (100K+ ACV), the MEDDIC and MEDDPICC frameworks add structure beyond SPIN. The letters cover: Metrics (how is success measured), Economic buyer (who has budget authority), Decision criteria (how will they choose), Decision process (how the decision will be made), Identify pain (what specifically hurts), Champion (who internally is selling for you), Paper process (procurement and legal flow), Competition. MEDDIC originated at PTC and became the gold standard for enterprise SaaS discovery (used at Snowflake, MongoDB, Salesforce). For each letter, document the answer in CRM and confirm with the champion before advancing. Deals missing data on three or more letters typically have under 20 percent close rates; deals with all letters answered close at 50 to 70 percent.
What to do in the first 90 seconds of discovery
The first 90 seconds of a discovery call determine the rest of the conversation. Best practice. Open with brief rapport (one minute max - reference their LinkedIn, company news, or a mutual connection). State the agenda explicitly: 'I would love to spend the first 15 minutes understanding your situation, then walk you through whether we are a fit, with 10 minutes at the end for your questions - sound good?' This sets expectations and prevents the prospect from launching into questions before you have done discovery. Confirm time available (most calls slip; pre-confirm 30 or 45 minutes). Begin discovery with a broad situational question ('walk me through how you came to look at solutions like ours'). The structured opening converts more nervous prospects into talkative ones; without it, you fight uphill the rest of the call.
Ending discovery with a clear next step
The end of a discovery call is the highest-leverage 3 minutes of the entire sales cycle. Bad endings: 'I will send you some materials,' 'let me think about whether we are a fit,' 'I will reach out next week.' These send deals into stall. Good endings follow a script. One, summarize what you heard: 'so based on what you described, the priorities are X, Y, Z and the constraints are A, B.' Two, confirm fit honestly: 'we typically work best with companies that have exactly this pattern, so this seems like a fit.' Three, propose a specific next step with a calendar invite sent during the call: 'I would like to send a proposal addressing X and Y, then walk through it together next Tuesday at 2pm - does that work?' Send the invite before hanging up. This single discipline doubles cycle velocity and forecast accuracy.
FAQ
How long should a discovery call be?
30 to 45 minutes is standard in US B2B. 30 minutes for SMB or simple offerings. 45 minutes for mid-market. 60 minutes only for enterprise with multiple stakeholders. Shorter than 30 minutes does not allow sufficient depth; longer than 60 minutes loses prospect attention and creates scheduling resistance. Always end on time or early; running over signals lack of discipline. If you genuinely need more time, propose a follow-up rather than extending.
Should I demo the product on the discovery call?
Generally no. The exception: lightweight product walkthroughs where the demo IS the discovery (true for some PLG SaaS). For most US B2B services and software, separate discovery (first call) from demo (second call). Demoing in discovery before you understand the prospect's situation produces generic demos that miss what they actually care about. Better sequence: 30 to 45 minute discovery, customized demo 3 to 5 days later showing exactly the use cases the prospect described. Demo-first reps lose deals to demo-second reps consistently.
What questions should I always ask in discovery?
Five questions that work across US B2B contexts. One, 'what triggered you to look at this now?' (surfaces real urgency). Two, 'walk me through how decisions like this typically get made at your company' (surfaces process and stakeholders). Three, 'what does success look like 12 months from now if you choose someone?' (surfaces metrics and value). Four, 'what would have to be true for this to be the right decision?' (surfaces criteria and concerns). Five, 'who else is involved in evaluating this?' (surfaces buying committee). These five answers identify whether the deal is real, qualified, and actionable.
How do I keep the prospect talking 80 percent of the time?
Three techniques. One, ask open-ended questions starting with what, how, why, walk me through - never yes/no questions. Two, use silence after their answer; 5 seconds of quiet often produces deeper detail than another question would. Three, follow up with 'tell me more about that' or 'why does that matter to you' to push past surface answers to root causes. Avoid: filling silence with your own commentary, jumping in with product features when they mention a problem, answering your own questions. The discipline of staying quiet is harder than asking questions; train it deliberately.
Should I record discovery calls?
Yes, where US legal allows. Two-party consent states (California, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Pennsylvania, Washington) require explicit consent before recording. One-party consent states (most others) allow recording with rep's consent only. Best practice everywhere: ask explicitly at start of call - 'I would like to record this for my notes - any concerns?' US tools that record and transcribe: Gong, Chorus (Salesforce), Fathom, Otter, Fireflies. Recordings enable: better follow-up, training new reps, quality coaching, AI-powered call analysis. Most modern US B2B sales teams record 80 to 100 percent of calls and find it transformative for coaching and forecast accuracy.
In your business
- →80/20 rule: prospect should talk 80% of the time, you 20%
- →Ask impact questions ('what happens if you don't solve this?') - they surface real urgency
- →Always end with a clear next step on the calendar - 'I'll send a proposal' is too vague