Sales Discovery Calls: 27 Questions Top Reps Ask
Marketing

Sales Discovery Calls: 27 Questions Top Reps Ask

The discovery questions that separate top sales reps from average ones — pain, impact, decision process, and timing — with a 30-minute call framework.

Rachel Brennan
By Rachel Brennan
12 min read

Why Discovery Is the Highest-Leverage Sales Skill

The single biggest gap between top sales reps and average reps isn't closing — it's discovery. Closing is what happens when discovery was done well. Hard closes on poorly-discovered deals produce churn, refunds, and damaged reputation. Soft closes on well-discovered deals close themselves.

Gong's analysis of more than 500,000 sales calls found that the top quartile of reps ask 11–14 thoughtful questions in a discovery call. The bottom quartile ask 4–6 and shift to demo or pitch within the first 10 minutes. That single behavioral difference explains roughly 40% of the variance in close rate between reps in their dataset.

This guide gives you the 27 discovery questions worth asking, organized by the four areas top reps cover, plus a 30-minute call framework. It's the tactical companion to building your broader cold email outreach and LinkedIn presence.

The 4 Stages of a Great Discovery Call

StageGoalTime Allocation (30-min call)
1. Current StateUnderstand the buyer's world today7–10 min
2. Pain & ImpactSurface the specific problem and its consequences8–10 min
3. Decision ProcessMap who decides, how, and when5–7 min
4. Timing & Next StepConfirm urgency, agree on what happens next3–5 min

The discipline is to cover all four stages, even when the conversation pulls toward demo or pitch. A "we already love it, can you just show me the product?" prospect who hasn't articulated their pain almost always ghosts after the demo.

Stage 1: Current State Questions

Goal: understand how they operate today, what tools they use, and where the friction is. Without this baseline, you can't identify the gap your product fills.

  1. "Walk me through how your team handles [the workflow your product touches] today." Why it works: Forces a concrete walkthrough, not an abstract description.

  2. "What does a typical week look like for the person who'd own this?" Why it works: Surfaces operational reality and identifies the actual end user.

  3. "What tools are you using for this today, and how did you end up with that stack?" Why it works: Reveals incumbents and switching cost. "How did you end up" surfaces the buying history.

  4. "Who else is involved in [the workflow] besides the person who'd own it?" Why it works: Identifies stakeholders early, before they show up unexpectedly in stage 3.

  5. "What's working well about your current setup?" Why it works: Honest reps acknowledge what works. It builds credibility and shows you're not trying to fabricate problems.

  6. "What's the volume / scale we're talking about?" (transactions, users, customers, whatever's relevant) Why it works: Quantifies. Lets you map their data to your pricing and packaging.

Stage 2: Pain & Impact Questions

Goal: surface the specific problem and quantify the cost of not solving it. This is the most-skipped stage and the highest-leverage one.

  1. "What specifically led you to take this call today?" Why it works: Anchors to the trigger event. Reveals whether they're actively in pain or just window-shopping.

  2. "When does [the problem] hurt the most?" Why it works: Forces specificity. "Always" is rarely true. The specific moments of pain are where your value lives.

  3. "What does the cost of [the problem] look like? Time? Money? Missed opportunities?" Why it works: Gets the buyer to do the math on their own pain. Their number is more credible than yours.

  4. "What happens if you don't solve this?"Why it works: The single most predictive question in B2B sales. Buyers who can articulate consequences buy. Buyers who can't are window-shopping.

  5. "Have you tried to solve this before? What happened?" Why it works: Reveals past failures, internal political resistance, and how serious they are. Three failed attempts means real commitment to solving.

  6. "On a scale of 1–10, how big a problem is this for you?" Why it works: Forces ranking. Anything below a 7 is unlikely to close in the next 90 days.

  7. "What would solving this be worth to your team?" Why it works: Establishes value framing for the upcoming pricing conversation. Asked too early, this feels intrusive; asked here, it feels collaborative.

  8. "What's the alternative if you don't go with a product like ours?" Why it works: Surfaces the real competition — which is usually "do nothing" or "build internally," not your direct competitors.

Stage 3: Decision Process Questions

Goal: map who decides, how the buying decision will be made, and what could derail it. Most lost deals come from missed stakeholders or unrecognized procurement complexity.

  1. "Walk me through how a decision like this typically gets made at your company." Why it works: Open-ended; lets them describe the process in their words.

  2. "Who else needs to be involved in the decision?" Why it works: Direct. Surfaces names you need to add to the deal.

  3. "What does the approval process look like for a purchase of this size?" Why it works: Reveals procurement, security review, legal review, and budget approval hoops.

  4. "Has your team purchased something like this before? What was that process like?" Why it works: Past purchase history predicts future process better than any other signal.

  5. "What's the budget situation? Is there allocated budget for this, or would it need approval?" Why it works: Distinguishes "budget exists" from "we'd need to find budget." The latter dramatically lengthens cycles.

  6. "Who could veto this decision even if you're enthusiastic?" Why it works: Surfaces hidden decision blockers — security teams, IT, finance, legal — who you might not naturally identify.

  7. "What would have to be true for this to be a yes?" Why it works: Pre-handles objections. Their answer maps your future homework.

Stage 4: Timing & Next Step Questions

Goal: pin down urgency and what happens next. Vague next steps mean lost deals.

  1. "What's your timeline for solving this?" Why it works: Distinguishes "this quarter" from "sometime in the next year." Affects how you prioritize the deal.

  2. "What's driving that timeline?" Why it works: Verifies the timeline is real. Internal initiatives, customer commitments, contractual deadlines all count. "We just want to look around" usually means no timeline.

  3. "What other initiatives are competing for attention and budget right now?" Why it works: Identifies competing priorities that could de-prioritize your deal.

  4. "If we're a fit, what would the next 30 days look like from your side?" Why it works: Forces them to imagine the next steps. If they can't, the deal won't close in 30 days.

  5. "What would be the ideal next step from here?" Why it works: Lets them propose the path. Their proposal is more likely to be honored than yours.

  6. "Is there anything I should have asked but didn't?" Why it works: Surfaces information you didn't think to ask for. Top reps consistently get gold from this question at the end of every call.

The 30-Minute Discovery Call Framework

MinuteActivity
0:00–2:00Build rapport, set agenda. "I have 30 minutes. My plan is to ask questions for 20, then I'll show you what we do, and we'll figure out next steps. Sound right?"
2:00–9:00Current State (questions 1–6). Listen more than you talk.
9:00–19:00Pain & Impact (questions 7–14). The most important segment.
19:00–24:00Decision Process (questions 15–21).
24:00–28:00Quick product framing (NOT a demo). 4 minutes max: "Based on what you said, here's the 3 things that would matter most for you in our product."
28:00–30:00Next steps (questions 22–27). Confirm a specific calendar event for follow-up.

The framework gives 60% of the time to discovery and only 4 minutes to product framing on the first call. This feels wrong to most reps, who want to demo. The data is clear: discovery-heavy first calls produce higher close rates.

Common Discovery Call Mistakes

Demoing in the First 10 Minutes

The most common mistake. Once you start showing the product, you've lost the discovery posture and gained a demo posture. The buyer evaluates features instead of articulating problems. Always do discovery before any product demonstration, even when the buyer asks for it.

Accepting Vague Answers

"It's a problem" is not an answer. "We waste 8 hours/week on this and it's making our customer success team unhappy" is. If a buyer answers vaguely, follow up with "What specifically?" or "Can you give me an example?"

Talking More Than the Prospect

Discovery calls should be 35% rep talking, 65% prospect talking. Top reps consistently hit this. Average reps invert it. Use a tool like Gong or Chorus to measure your actual talk ratio — most reps overestimate how much listening they do.

Skipping Stage 3 (Decision Process)

Reps who don't map the buying process before pitching get blindsided by procurement, legal, and unexpected stakeholders later. The deal stalls, then dies. Discovery includes mapping the path to close, not just the pain.

No Specific Next Step

"Let me follow up next week" is not a next step. "Let's get [their security lead] on a 20-minute call Thursday at 2pm" is. Specific calendar events with named people convert; vague follow-ups don't.

When Heavy Discovery Doesn't Make Sense (Not For You)

Skip the full 27-question framework if:

  • ACV is under $5K and self-serve is the right motion. Discovery is expensive labor. For low-ACV products, lead with product trial and let usage data do the qualification.
  • You're selling to a single named buyer with no committee. Stages 3 (decision process) and elements of stage 2 (impact across stakeholders) compress dramatically when there's one decision-maker. Drop to 12–15 questions.
  • The product is a no-brainer for a known pain. Sometimes prospects come in ready to buy — they self-discovered. Don't force them through questions they've already answered. Compress to the most important 6–8 questions.
  • You're testing whether to qualify out. Sometimes the goal of a first call is to disqualify a poor fit, not to advance the deal. In that case, 5–6 disqualifying questions are enough.

Conclusion

Discovery is the highest-leverage skill in sales. The 27 questions in this guide are not a script — they're a reference set. Pick the 11–14 that fit your specific call. Cover all four stages. Talk less, listen more. Get a specific next step before ending.

The best reps treat discovery as a craft they refine for years. The data is unambiguous: reps who do discovery well close at 1.5–2x the rate of reps who skip it. Pair this with disciplined follow-up via cold email, strong marketing attribution to know which leads to prioritize, and a defined pricing strategy so the post-discovery conversation lands cleanly.

Frequently Asked Questions

How many questions should I ask in a sales discovery call?

Top reps ask 11–14 thoughtful questions in a 30-minute discovery call. Below 8 questions typically means you're pitching too early; above 18 questions can feel interrogative. The right count depends on the prospect's openness and your ACV — higher ACV deals justify more discovery.

What's the most important question to ask in a discovery call?

'What happens if you don't solve this?' is the single most predictive question for deal closing. Prospects who can articulate consequences buy. Prospects who can't are window-shopping. Asked early in the pain stage, it separates real opportunities from polite interest.

Should I demo the product during a discovery call?

Not as the main event. A 4–6 minute targeted product framing at the end of the call — showing only the 2–3 features that match the prospect's stated pain — works better than a full demo. Save the full demo for a second call with the right stakeholders in attendance.

What talk-to-listen ratio should I target?

35% rep talking, 65% prospect talking is the empirical ideal. Top reps consistently hit this; average reps talk 60–70%. Most sales reps overestimate how much they listen. Record your calls (with consent) and review them with a stopwatch to get a real baseline.

How long should a discovery call be?

30 minutes is the standard for most B2B deals. Longer (45–60 min) for enterprise deals with multiple stakeholders. Shorter (15–20 min) for SMB or self-serve products. Don't ask for more time than the deal size justifies — over-asking signals that your product isn't valuable enough to evaluate quickly.

What if the prospect doesn't want to answer my questions?

Two patterns work. First, set expectations early: 'I want to ask you a few questions so I can tailor what I show you — if any feel off-base, let me know.' Second, if they push for a demo, agree to demo after 10–15 minutes of discovery: 'Let me ask you 3 quick things so the demo focuses on what actually matters for you.' Total refusal to answer questions usually means they're not really evaluating — they're shopping.

Should I send my discovery questions in advance?

Optional. Sending a 5–7 question agenda email in advance helps the buyer prepare and shows seriousness. Don't send all 27 — that signals interrogation. A short agenda email signals professionalism. Some top reps swear by it; others prefer to keep the questions natural. Test both.

salesdiscovery callsB2B salessales processqualification
Rachel Brennan

About Rachel Brennan

Editor in Chief & Co-Founder

Rachel Brennan is a seasoned business strategist who has spent 15+ years helping founders turn ideas into scalable companies. After earning her MBA from Stanford GSB, she joined McKinsey & Company as a consultant before co-founding two venture-backed startups — one acquired in 2019. She launched EntrepreneurBytes to share the playbooks she wished she had as a first-time founder.

View All Articles →