Discovery Call Questions: 16 Only the Prospect Can Answer

If you could have Googled the answer, don't ask it on the call. Discovery time is for the questions only this person can answer. A discovery call has maybe 30 minutes, and every minute spent asking about company size, tech stack, or org structure, things you could have researched beforehand, is a minute stolen from the questions that actually matter: how the prospect feels about their current process, what the problem is costing them, and what "solved" looks like in their terms. Those answers do not exist in any database. This guide is a bank of 16 discovery call questions organized by the section of the call they belong to, current state, problem and impact, desired outcome, decision process, and timeline, each chosen because only the prospect can answer it. Filter your own question list through the same test before every call.

Discovery call questions are the questions a salesperson asks during a discovery call to understand a prospect's situation, problem, its impact, decision process, and desired outcome. The most valuable ones ask about things only the prospect can know, their experience, priorities, internal dynamics, and definition of success, rather than facts the seller could have found through prior research.

The filter: what to research vs what to ask

Before a discovery call, research everything that is knowable without the prospect: company size, funding, tech stack, org chart, recent news, likely stakeholders. Walk in already knowing these. Then use the call exclusively for questions whose answers live only in the prospect's head.

The test for each question on your list: could a well-prepared rep have found this answer through research. If yes, cut it. Asking "how many people are on your sales team" when the answer is on LinkedIn signals you did not prepare and wastes time you do not have. This connects to the diagnose-don't-pitch discipline: the call is for understanding, and understanding comes from questions only the prospect can answer.

Current state questions

These establish how the prospect handles the relevant area today, in their words.

1. "Walk me through how your team handles [the relevant process] today, step by step." The step-by-step framing surfaces friction points a summary would hide.
2. "What made you take a call about this now, rather than six months ago or six months from now?" Reveals the trigger, which is often the real driver of the whole evaluation.
3. "Who on your team touches this process, and where does it tend to get stuck?" Maps the people and the bottleneck at once.
4. "What have you already tried to fix this, and what happened?" Tells you what solutions are burned and what the prospect learned from them.

Problem and impact questions

The core of the call. These get the prospect to articulate the cost of the problem themselves, in the style of SPIN's implication questions.

1. "What does that [specific friction they mentioned] cost you, in time or money, over a quarter?" Forces a concrete number, which makes the problem real.
2. "How does this affect the people doing the work day to day?" Surfaces frustration, morale, and turnover risk that a pure cost question misses.
3. "Is this getting better or worse as the team grows?" Reveals urgency and trajectory, which a snapshot question does not.
4. "If nothing changes here in the next year, what happens?" Makes the prospect state the consequence of inaction, which is what creates urgency.
5. "What is the hardest part of this to explain to someone outside your team?" Often uncovers the most acute pain, the part that is hard to articulate.

Desired outcome questions

These define what "solved" means to the prospect, which you will tailor your later product conversation to.

1. "If this were working the way you want, what would be different?" Their words for success, which should shape everything you present later.
2. "What would need to be true for you to consider this a win in six months?" Ties success to a concrete, measurable state.
3. "Who else would notice if this got fixed, and what would they say?" Identifies additional stakeholders and how they measure the outcome.

Decision process questions

These map how a purchase actually gets made here.

1. "If you decided to move forward, walk me through what happens next inside your company." Reveals the buying committee, procurement, and legal steps in the prospect's own description.
2. "Whose budget would this come out of, and can that person approve it, or does it go higher?" Identifies the economic buyer, who is often not your contact.
3. "Has your team bought something like this before? How did that go?" Tells you what the process looks like and whether there is organizational scar tissue.

Timeline questions

1. "Is there a specific event, deadline, or business goal driving the timing on this?" A timeline with no anchor event is usually soft, and this question surfaces whether there is a real one.

If the answer to question 16 is vague, the deal's timeline is aspirational, which changes how you forecast it regardless of how enthusiastic the prospect sounds.

The Answer-You-Already-Know Filter

The Answer-You-Already-Know Filter: before asking any discovery question, filter out the ones whose answers you could have found through research, company size, tech stack, org structure. Asking those wastes limited call time and signals you did not prepare. Reserve the call exclusively for questions only the prospect can answer: how they feel about the current process, what it is costing them, and what "solved" looks like to them.

Run your standard discovery question list through this filter once. Most reps find that a third of their usual questions are research questions in disguise, and cutting them frees up real time for the impact and decision-process questions that actually move a deal. Do the research beforehand, then spend the call on the head, not the database.

"If you could have Googled the answer, don't ask it on the call. Discovery time is for the questions only this person can answer."

Rebuild your discovery question template around the filter, sorting every question into "research beforehand" or "ask on the call," and lead the call with the impact questions since those carry the most weight.

Where InboundLabs fits

The research half of this, everything you should know before the call so you do not waste time asking it, depends on having accurate account and contact data ready.

InboundLabs is a B2B contact database with buyer intent signals layered on firmographic data, so a rep can filter by industry, headcount, region, and title and prepare the account context before a discovery call, keeping the call itself focused on the questions only the prospect can answer. It holds a database of 280M verified B2B contacts with 98% email deliverability on verified contacts, plus verified direct dials, not switchboard numbers. Monthly plans, no annual lock-in, and free to start, no credit card required.

See how InboundLabs finds verified contacts instantly → inboundlabs.app

The bottom line

Discovery call questions are only worth the limited call time if the prospect is the only person who can answer them. Research company size, tech stack, and org structure before the call; use the call for how the prospect experiences the current process, what the problem costs, what "solved" looks like, how a decision actually gets made, and what is driving the timing. Filter your standard question list through the "could I have Googled this" test, cut the research questions, and lead with the impact questions. Prepare the account context ahead of time. Start free at inboundlabs.app.

Frequently Asked Questions

What are the best discovery call questions to ask?

The ones only the prospect can answer: how their team handles the process today step by step, what made them take a call now, what the problem costs them per quarter, how it affects the people doing the work, what "solved" would look like, how a decision gets made internally, and what event is driving the timing.

What discovery questions should you not ask on the call?

Anything you could have found through research: company size, funding, tech stack, org structure, recent news. Asking these wastes limited call time and signals you did not prepare. Know them before you dial, and spend the call on the prospect's experience and priorities instead.

How many questions should a discovery call have?

Not a fixed number, but roughly 12 to 18 well-chosen questions spread across current state, problem and impact, desired outcome, decision process, and timeline, with the most call time on problem and impact. The point is depth on the core questions, not volume of questions.

What is the most important type of discovery question?

Impact questions: the ones that get the prospect to articulate what the problem is actually costing them in time, money, missed targets, or team frustration. When a prospect states that cost themselves, the problem becomes urgent in a way it never does when a seller asserts it.

How do you ask about the decision process without sounding pushy?

Frame it around a hypothetical forward step: "If you decided to move forward, walk me through what happens next inside your company." This surfaces the buying committee, budget owner, and procurement steps in the prospect's own words, without implying they lack authority.

What if the prospect's timeline answer is vague?

Treat it as a signal that the deal's timeline is aspirational rather than real. A timeline anchored to a specific event, deadline, or business goal is a genuine opportunity; a timeline with no anchor should be forecast more conservatively regardless of how enthusiastic the prospect sounds.

LSI keywords: discovery call questions, current state, problem impact, desired outcome, decision process, timeline, implication questions, buying committee, economic buyer, research vs ask, qualification, call preparation

Sources

• Attainment: B2B Buying Committees, Why 8-13 Stakeholders Changed Enterprise Sales (checked September 2026)