What Is a Discovery Call? How to Run One That Moves Deals Forward

A discovery call is a structured conversation where a salesperson learns whether a prospect is a genuine fit — before pitching anything. The goal is not to sell. It's to gather enough information to know if there's a real problem, real budget, and real urgency. If those three exist, the deal moves forward. If they don't, you save both sides time.

What is a discovery call in sales?

A discovery call is a scheduled conversation — typically 20–45 minutes — between a sales rep and a potential buyer, held early in the sales process. Its purpose is diagnosis, not persuasion. The rep is trying to understand the prospect's current situation, the problem they're experiencing, what they've already tried, and whether the timing and budget are real.

The term comes from the idea of "discovering" fit before investing either party's time in a full demo or proposal. In B2B SaaS sales, it's usually the first call after an initial reply to outreach or an inbound lead form — the moment where a lead either becomes a qualified opportunity or gets disqualified.

A well-run discovery call answers four questions: Does this company have the problem we solve? Is that problem painful enough to justify change? Do they have the budget and authority to act? And is the timing right?

Why do discovery calls matter so much in B2B sales?

Discovery calls are where pipeline quality is determined. A rep who skips deep discovery and jumps to demo is essentially guessing that the prospect is qualified. That guess is wrong more often than not — and the cost is a bloated pipeline of deals that never close.

According to Gong's analysis of over one million sales calls, top-performing reps ask an average of 11–14 questions during a discovery call, while average reps ask fewer than 7. But quantity isn't the key variable — it's the nature of the questions. Top reps ask about business impact, consequences, and current workarounds. Average reps ask about features, integrations, and timelines.

Discovery also protects your time. Every hour spent building a proposal for an unqualified prospect is an hour not spent on a deal that could actually close. The fastest way to improve your close rate is to improve what goes into your pipeline — and discovery is the filter.

"The discovery call is where deals are won or lost — not during the demo. If you haven't uncovered real pain by the time you're presenting, you're pitching into a vacuum."

— Chris Orlob, former Head of Sales Intelligence at Gong

How do you run a discovery call step by step?

A discovery call has a predictable structure. Reps who improvise tend to drift into pitching too early. The following sequence keeps the conversation focused on the prospect's reality.

Set the agenda upfront

Open by stating what you plan to cover and asking the prospect to add anything missing. This creates a shared contract for the call and signals that you're organized. Something like: "I'd like to spend the first 15 minutes understanding your situation, then if there's a fit I can show you how we've solved similar problems. Does that work?"

Ask about their current state

Before asking about problems, understand the baseline. What tools are they using today? How is the relevant process currently handled? Who owns it? This context makes every subsequent question more precise and makes the prospect feel heard rather than interrogated.

Identify the gap

What's not working about the current state? This is where the real discovery happens. Good reps don't accept the first answer — they follow up. "What does that cost you?" "How long has that been a problem?" "What have you tried to fix it?" The goal is to understand the gap between where they are and where they need to be.

Qualify on BANT or MEDDIC

Budget, Authority, Need, and Timeline (BANT) are the classic qualification criteria. MEDDIC (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion) is more rigorous and better suited to complex enterprise deals. Either framework works — the point is to cover all four dimensions before leaving the call.

End with a confirmed next step

Never close a discovery call with "I'll send you some information." That's a non-commitment disguised as progress. The call ends with a specific next step — a demo date, an intro to the economic buyer, a follow-up call — agreed on the call, in both calendars.

What questions should you ask on a discovery call?

The best discovery call questions are open-ended, focused on impact, and sequenced to go deeper as the call progresses. Here are the categories that matter most.

Current state questions

• "Walk me through how you currently handle [relevant process]."
• "What tools are you using today to manage [problem area]?"
• "Who on your team is most involved in this day-to-day?"

Pain and impact questions

• "What's the biggest frustration with how things work today?"
• "What does that problem cost you — in time, revenue, or headcount?"
• "If this doesn't get fixed, what happens?"

Priority and urgency questions

• "Where does solving this sit relative to your other priorities this quarter?"
• "Is there a deadline or event driving the urgency?"
• "What happens if you don't have a solution in place by [timeframe]?"

Decision process questions

• "Who else would be involved in evaluating a solution like this?"
• "Have you looked at other options? What did you find?"
• "What does your typical evaluation process look like?"

The last question — asking about other options they've evaluated — is particularly useful when a prospect is already using a competitor's product. At that point, you already know the problem is validated and the budget is real. What you need to discover is their dissatisfaction and switching criteria. If you're targeting prospects this way — reaching out to companies already using a rival tool — Stealery lets you build those lists before you pick up the phone: search a competitor name, filter by company size and location, and you have a list of qualified targets who've already proven the problem exists.

What are the most common discovery call mistakes?

Most discovery call failures follow one of five patterns. Knowing them in advance is the fastest way to avoid them.

Pitching instead of questioning

The most common mistake is treating discovery as a warm-up to the pitch. As soon as a rep hears a relevant pain point, they start explaining how their product solves it. This collapses the discovery — the prospect stops sharing information and starts evaluating. Save the pitch for after you've heard everything.

Accepting surface-level answers

Prospects often give polite, vague answers at first. "We want to improve our process" is not a pain point — it's a placeholder. The rep's job is to go one level deeper every time: "What specifically about the process isn't working?" "When did that become a problem?" "What have you tried?"

Skipping the economic buyer question

Deals die because the person on the discovery call turns out not to be the decision-maker. Ask directly and early: "If we find a good fit here, who else would need to be involved in moving forward?" This is not rude — it's professional.

No agenda, no structure

Calls without an agenda drift. The prospect starts asking questions, the rep starts answering, and 30 minutes later neither side has learned what they needed to. Open every call by stating what you plan to cover and getting agreement.

Weak close

According to Salesloft's sales benchmarking data, calls that end with a specific next step booked during the call have significantly higher conversion rates to closed-won than calls that end with a vague follow-up. Don't leave the call without a date in both calendars.

What is the difference between a discovery call and a demo?

A discovery call is a diagnostic conversation. A demo is a product presentation. These are different conversations with different goals, and conflating them is a common mistake in early-stage sales motions.

In a discovery call, you are asking questions. The prospect is talking most of the time. You are not showing anything — no slides, no screen share (usually), no product. The output is a clearer picture of fit, pain, and urgency.

In a demo, you are presenting. You're showing the product against the specific pain points uncovered in discovery. A demo that hasn't been preceded by a thorough discovery call is essentially a generic product tour — it lands with a fraction of the impact of a demo tailored to what the prospect just told you they care about.

Some sales processes combine them into a single "disco-demo" call, particularly in high-velocity SMB sales where the deal size doesn't justify two separate meetings. This works only if the rep disciplines themselves to complete discovery before switching to demo mode — not after 10 minutes, but after they've genuinely qualified the opportunity.

How do you run a discovery call with a prospect using a competitor?

When you know going into a call that the prospect is an active user of a competing product, the discovery call dynamic changes. The first half of standard discovery — confirming they have the problem — is already answered. You skip to the more interesting questions.

Start with their experience of the current tool: "You're using [Competitor] today — what's working well about it?" This disarms the defensiveness that comes with being cold-called about switching, and it tells you where the bar is set. Then ask what's missing or frustrating. Then ask what prompted them to take your call or reply to your email.

That last question is the most valuable one. If they replied to your outreach despite using a competitor, something has changed — new requirements, a price increase, a product limitation they've hit, a team change. That's your switching trigger, and the rest of the discovery call is built around it.

This approach — targeting companies already using a competitor and running discovery around switching criteria — is one of the highest-conversion strategies in B2B SaaS sales because the problem validation and budget approval are already done. The only question is fit and timing.