AIViral logoAIViral
← Back to blog

Sales Discovery Questions That Uncover Real Buying Intent

Seller asking a buyer a discovery question

The best sales discovery questions are open-ended and follow a simple arc. They cover the prospect’s situation, then the pain, then its business impact, then urgency, then who decides. Ask them in that order, listen more than you talk, and end the call with a concrete next step. This guide gives you the questions, a call structure to hang them on, a SaaS-specific set and a checklist for before, during and after the call.

Aiviral
Meet Buyers Ready to Talk
Aiviral uses AI-driven outreach and performance marketing to generate B2B leads who actively request meetings or pricing.
Explore Aiviral lead generation

TL;DR

  • A discovery call is the first real conversation after a prospect shows interest. Its job is to learn goals, pain, decision process and fit, not to pitch.
  • Use open “what” and “how” questions. Avoid yes-or-no questions, which end the conversation instead of opening it.
  • Move through five layers: situation, pain, impact, critical event (urgency) and decision. Pain alone is not enough to qualify a deal.
  • Treat your questions as a menu, not a script. Follow the buyer’s answers and summarize before you close.
  • End every call with a mutual-fit judgment and one specific next action.

Table of Contents

What a discovery call is for

A discovery call is an early sales conversation that happens after a prospect has shown interest. Salesforce describes it as the moment to determine product fit and uncover what motivates the buyer. Zendesk frames it the same way: assess fit and learn needs and goals before any product pitch.

In practice you leave the call with answers to a short list of things. HubSpot’s 2026 guide lists them as goals, pain points, decision process, budget, timeline and overall fit. If you cannot answer those after thirty minutes, the questions were too shallow or the buyer was not ready to talk.

One point is easy to miss. A call that leads to a polite “send me something” and nothing else is not a successful discovery call. It is a call where the seller talked, the buyer stayed vague and nobody learned anything that moves a deal. Good questions are how you prevent that.

A call framework to hang your questions on

Questions work better when they have a place to live. Several teams publish their own structures, and they agree more than they differ.

Framework How it divides the call Best for
PostHog’s discovery handbook Opening and situation (about 5 to 7 minutes), a relevant demo (about 15 to 20), closing and next steps (about 3 to 10) Product-led SaaS with a demo built in
Revenue.io’s call plan Minutes 0 to 3 purpose, 3 to 15 workflow, problem and consequence, 15 to 23 stakeholders and evaluation, 23 to 27 summary, 27 to 30 next action or acknowledged no-fit A 30-minute call with no demo
SPICED from Winning by Design Situation, Pain, Impact, Critical Event, Decision Keeping notes and CRM fields consistent
HubSpot’s GPCT model Goals, Plans, Challenges, Timeline Qualifying when BANT feels too rigid

You do not need to pick a winner. A practical blend: use a time plan like the 30-minute one for pacing, and SPICED as the checklist of what you must have learned by the end.

The SPICED authors make one argument worth keeping. Pain by itself is not enough. A seller should connect the situation and pain to measurable impact, a critical event and the decision path. A prospect who admits a process is annoying but has no deadline and no owner is still a long way from a deal.

Opening questions that set the frame

The first three minutes decide whether the buyer treats this as a conversation or an interrogation. State the purpose, check the time and agree on what a good outcome looks like. For example:

  • “Thanks for making time. Do we still have the full thirty minutes?”
  • “My goal is to understand how you handle this today and whether it makes sense for us to keep talking. Does that work?”
  • “What made you take this meeting?”
  • “What prompted you to look at solutions in this space now?”

That last pair matters most. The answer tells you the trigger, and the trigger usually tells you the urgency. A prospect who answers with a specific event (a missed quarter, a new hire, a failed tool) is in a different place from one who says they are just exploring.

Situation questions: how things work today

Situation questions map the current state. They should be short, factual and few. Prepare them from research on the account so you do not waste the buyer’s time asking what a website already says.

  1. How does your team handle [the process] today?
  2. Which tools or vendors are involved right now?
  3. Who on your team touches this process, and how often?
  4. What have you tried before to improve it?
  5. What are your main priorities this quarter or this year?

PostHog’s guidance recommends “what” and “how” questions and prompts such as “tell me” or “describe” to understand the prospect’s current state. That wording invites a story instead of a one-word answer. Zendesk adds that you should avoid yes-or-no questions and explore goals, roadblocks, stakes, decision-makers, prior software and budget.

Pain questions: where it breaks

Once you know the setup, ask where it fails. Revenue.io suggests probing where the process slows or breaks and what workarounds people use. Workarounds are a gold mine, because a spreadsheet someone maintains by hand is evidence that the pain is real enough to cost effort.

Questions to try:

  • Where does this process slow down or break?
  • What workarounds has the team built?
  • Can you walk me through the last time that happened?
  • What have you already tried, and why did it not stick?
  • If you could change one thing, what would it be?

A tip from Edithly’s guide: listen for specifics such as numbers, dates, names and recent examples. When an answer is vague, probe with “Tell me more” or “Can you give me a recent example?” Real pain produces details. Mild irritation produces generalities.

Impact questions: what the problem costs

This is the layer most reps skip. A problem the buyer cannot put a cost on rarely gets budget. Ask about time, revenue, headcount and customer experience, and let the buyer do the math in their own words.

  • What does this cost you in time, revenue or headcount?
  • How does it affect your team’s goals?
  • What happens if it is still unresolved next quarter?
  • Who else feels the impact: customers, other teams, leadership?
  • What would a better outcome look like, and how would you measure it?

The Winning by Design examples ask how a problem affects revenue, cost or customer experience, which keeps impact tied to numbers a finance lead would recognize. Zendesk makes a related point: urgency comes from asking what is at stake if the company does not reach its goal.

Do not supply the number yourself. When the buyer says “it costs us about two days a week,” that figure belongs to them and carries far more weight than any industry statistic you could quote.

Buyer describes time lost to a problem

Urgency questions: why now, and by when

Urgency separates a real opportunity from a pleasant chat. Ask about the critical event, meaning the date, launch, renewal or board meeting that makes the problem time-bound.

  • Is there an event or deadline driving this?
  • What is your timeline for making a change?
  • What happens if you do nothing until next quarter?
  • How will success be defined when you look back in six months?

HubSpot’s GPCT model includes a timeline and also asks whether the current plan can reach the goal at all. That second question is useful: if the existing plan will get them there, the case for change is weak, and you should know that early.

Decision questions: who is involved and how they buy

Many deals stall because the person on the call cannot say yes. Ask about the decision process plainly and without apology.

  • Who else is involved in picking a solution like this?
  • Does finance or IT need to approve it?
  • Who is responsible for the improvement, and who will evaluate the change?
  • How have you evaluated tools like this in the past?
  • What does budget look like for this kind of project?

Revenue.io recommends separating three groups: the people affected as users, the person accountable for the improvement, and those who evaluate a change. Zendesk’s qualification advice is to establish budget and who is involved in choosing the software. If you want a deeper look at how handoffs between marketing and sales go wrong after qualification, our piece on sales accepted leads covers the intake side.

SaaS discovery call questions

Software sales add a few extra angles: use cases, current tools and how the buyer evaluates. PostHog’s handbook offers a good model because it was written for its own sales team. Its example questions cover the trigger for contacting the company, the analytics tools in use today, who uses the data and for what decisions, how the team evaluates tools, and who else should be involved.

Adapted for any SaaS product, that becomes:

  1. What made you reach out to us?
  2. Which tools do you use for this today, and what do you like or dislike about them?
  3. Who uses the output, and what decisions does it feed?
  4. How do you usually evaluate new software, and who joins that process?
  5. Which CRM or core systems does this need to work with?
  6. Do you have the technical resources to implement something like this?
  7. What would make this a clear win in the first ninety days?

The same handbook suggests confirming a few fit criteria before you invest in a demo: the prospect matches your ideal customer profile, has a clear problem you can solve, has the technical resources, and has budget and timeline. Winning by Design’s examples add a simple one, which CRM the team uses today, because integration needs often decide the deal.

If you sell software and want conversations with buyers who already raised their hand, see how we approach hot leads for SaaS and software.

Closing the call: summarize and agree the next step

A strong discovery call ends with a mutual-fit judgment and a concrete next step, such as a demo, trial, quote or follow-up, plus an understood timeline and an agreed channel for follow-up. That is PostHog’s standard, and it is a good one.

A closing sequence that works:

  1. Summarize the priorities you heard in the buyer’s own words.
  2. Ask: “Did I get that right? What did I miss?”
  3. State whether you think there is a fit, and why.
  4. Propose one next step with a date.
  5. Confirm who else should join it.

If there is no fit, say so. Revenue.io’s call plan reserves the final minutes for agreeing the next action or acknowledging no fit. A clean “this is not for you right now” protects your forecast and your reputation.

Discovery call checklist

Use this as a one-page reference. It follows the structure in PostHog’s handbook: research before, natural conversation during, clear follow-up after.

Before the call

  • Research the account: size, industry, tools, recent news.
  • Review how the prospect came to you and what they asked for.
  • Choose five to eight questions from the menu above, not thirty.
  • Prepare the fit criteria you will check against.

During the call

  • Open with purpose, time check and desired outcome.
  • Cover goals, current setup, challenges, decision-makers and timeline.
  • Probe vague answers for a recent example or a number.
  • Take notes in a consistent structure, such as SPICED.
  • Summarize and confirm before proposing anything.

After the call

  • Send a follow-up by email or chat the same day, restating what you heard.
  • Record decision-makers, timeline and impact in your CRM. Our guide to CRM lead management shows how to keep those fields useful.
  • Route the opportunity if another team should own it.
  • Confirm the next step and put it on the calendar.

Keep it a conversation, not an interrogation

The most common failure is not asking bad questions. It is asking good ones in a rigid row. ZoomInfo’s guide warns that jumping from question to question without listening makes discovery feel like an interrogation. Zendesk advises listening roughly as much as you speak and weaving questions in naturally instead of reading them like a robot.

Three habits help:

  • Pause. After an answer, wait a beat. Buyers often add the most useful detail in the silence.
  • Follow the thread. Prepare core questions, but let the last answer decide the next question.
  • Use the 5 W’s as a prompt, not a list. Who is involved, what is happening, when does it matter, where does it break, why now. They are a quick way to notice a gap in your notes, nothing more.

Revenue.io puts the idea well: discovery is a menu of questions followed by the buyer’s answers, not a completed questionnaire.

Our perspective on discovery

We spend our days on the step just before discovery: finding the people who actually want a conversation. That vantage point changes how we think about these questions.

Most discovery calls go badly for a reason that has nothing to do with technique. The prospect never really asked for the meeting. A rep can have a perfect question list and still spend thirty minutes politely convincing someone who was never interested. Discovery works best when the buyer arrives having requested a meeting, pricing or a demo, because the opening question (“what made you take this meeting?”) then has a real answer.

That is why we build around interest first. Our service runs cold email, LinkedIn, social outreach and search ads, checks replies from decision-makers, and has a person review every response before a lead is delivered. Clients pay only for leads who show genuine interest, and a lead that does not meet that standard can be disputed for credit. Your team then spends its time on the questions in this guide instead of on prospecting.

Our advice: invest in your questions, but invest just as much in who sits on the other side of the call. Great discovery with an interested buyer beats great discovery with a lukewarm one every time.

Max

Get discovery calls with buyers who asked for them

If your reps are spending their best questions on prospects who never raised a hand, the fix is upstream. AIViral handles the outreach and the ad spend, then delivers leads who replied asking for a meeting, a call, pricing, info or a demo. You pay per lead, with no setup fees or contracts.

Aiviral

Pricing is published by interest level: Warm leads are $5 to $15 each, Hot leads are $15 to $30 each and On fire leads are $30 to $50 each, one-off per lead. See the details on our pricing section, check how it works, or start at aiviral.com.

FAQ

What are the best sales discovery questions?

The best ones are open-ended and tied to the buyer’s situation. Start with what prompted the conversation and how the process works today. Then ask where it breaks, what it costs, what the deadline is and who else decides. Questions like “What made you take this meeting?” and “What happens if this is unresolved next quarter?” tend to produce the most useful answers.

How many discovery questions should I ask on one call?

Fewer than you think. Pick five to eight core questions and let follow-ups fill the rest. A 30-minute plan such as Revenue.io’s gives about 12 minutes to workflow, problem and consequence, which is enough for a handful of deep questions, not thirty shallow ones.

What is the difference between discovery and qualification?

Discovery is about understanding the buyer’s needs, pain and goals. Qualification is about deciding whether the deal is worth pursuing, based on things like budget, decision process, timeline and fit. In practice they overlap on the same call. Models such as SPICED and HubSpot’s GPCT combine them in one set of questions.

What should a SaaS discovery call cover that other calls do not?

Current tools, integration needs, technical resources and how the team evaluates software. Ask which CRM or core systems the product must work with, who will use it day to day, and who joins the evaluation. These answers shape the demo and surface blockers early.

How do I stop discovery from feeling like an interrogation?

Explain the purpose up front, ask one question at a time and respond to what the buyer actually says. Summarize priorities in their words and confirm them. Use your question list as a menu, not a script.

Sources

← Back to blog