How to Run a Discovery Call (Questions + Template)

A buyer says, "We need better visibility across our deals." The tempting response is to open the deck and explain your dashboard. Stay with the buyer's sentence instead: "Where does visibility break down today?"

Their answer may uncover a forecasting problem. It may also reveal that managers do not trust CRM updates. Perhaps deals stall after demos or the project has no executive support. You cannot know until you follow the problem far enough.

A strong discovery call gives the buyer space to examine that problem while you work out whether there is a deal worth pursuing.

TL;DR: How to Run a Discovery Call

1. Use the call to decide whether the opportunity deserves a next step. The buyer should get useful clarity from the conversation too.
2. Leave with evidence about the problem, business impact, timing, budget, decision path, concerns, and the next commitment.
3. Follow a loose sequence: agree on the purpose, understand the current situation, examine impact, qualify the buying process, then recap what you heard.
4. Prepare a small set of questions, then listen to the answers and ask follow-ups. A long question list turns the call into an interview.

What Is a Discovery Call?

A discovery call is an early sales conversation where a rep and buyer work out whether there is a meaningful problem and enough mutual interest to continue.

The rep needs more than a statement of interest. "We want to improve sales performance" says little about what happens inside the team or how much the problem costs. It also leaves the approval path unclear. Discovery turns that broad interest into evidence.

The buyer should gain something as well. A good rep helps them describe the problem with more precision and connect it to an outcome the business cares about. They can then decide whether solving it now deserves attention.

Discovery can happen on the first scheduled call or across several conversations. A straightforward purchase may need 30 minutes. A complex B2B deal often requires separate conversations with users and budget owners. Technical reviewers may need their own session. The job stays the same: learn enough to agree on a sensible next step.

What You Need to Learn Before the Call Ends

You do not need every possible fact. You need enough evidence to judge the opportunity and protect the buyer from an irrelevant follow-up.

A rep rarely learns these in neat order. Budget may surface while the buyer describes a failed project. A hidden stakeholder may appear when you discuss timing. Keep the sequence loose and follow what the buyer gives you.

How to Run a Discovery Call From Prep to Next Step

1. Prepare a point of view

Read the account notes and the person's role. Check any context from the meeting request, then form one or two hypotheses about the problem they may have.

For a VP of Sales, you might expect inconsistent discovery across the team. The hypothesis only gives you a place to start. Prepare a question that tests it:

> "Where do deals tend to lose momentum after the first conversation?"

Bring one relevant customer example or product detail in case it helps. Twenty prepared questions will compete with your ability to listen.

2. Agree on the purpose

Open with a short agenda and give the buyer room to change it.

> "We have 30 minutes. I would like to understand what prompted the conversation and how you handle it today. Then we can decide whether there is a useful next step. Is there anything you want to make sure we cover?"

That sentence sets a destination without pretending you know the route.

3. Understand the current situation

Start with how the buyer works today. Broad claims become useful once they attach to a real process.

If the buyer says managers lack deal visibility, ask where managers look now and how often the information is wrong. Then ask when the gap last caused a problem. A recent example will tell you more than a general opinion.

4. Follow the problem into its impact

The first problem a buyer names is often one layer above the business consequence. "Reps forget questions" may lead to poor qualification. That can lead to late-stage losses and unreliable forecasts.

Use short follow-ups:

> "What happens when that gets missed?"

> "Can you give me a recent example?"

> "Who else feels the effect?"

The difficult part is noticing which thread deserves another question while the call keeps moving. A real-time AI sales assistant can identify buying signals as they appear and prompt the rep when budget, timing, or another important area is still unclear. The rep still decides what fits the conversation.

5. Establish why the problem matters now

A painful problem can sit untouched for years. Ask what changed and whether a deadline exists. Find out what happens if the buyer leaves the current process in place.

Urgency does not need to sound dramatic. A new manager or missed target can be enough. An expiring contract may create a different deadline. If nothing makes the issue timely, record that rather than inventing pressure.

6. Discuss budget and the decision process

Budget questions feel awkward when they arrive without context. Once the buyer has described the impact and desired change, ask how the company would fund a solution.

> "If we find an approach that fits, has the team set aside budget for it?"

> "Who would need to be comfortable with the investment?"

Then map the decision. Learn who will use the product and who can stop the purchase. Confirm who gives final approval and what reviews happen before signature. A verbal yes from one person does not tell you whether procurement or security can still block the deal. The final approver may have concerns of their own.

7. Invite the concern they have not raised

Buyers often keep a concern to themselves because the rep is moving fast or because they expect a sales answer. Make room for it.

> "What would make this hard to introduce inside the team?"

> "What concern would you want resolved before taking this further?"

Listen without preparing your defence. If an objection appears, clarify it before answering. Our guide to handling sales objections covers that conversation in more detail.

8. Recap and earn the next step

Use the buyer's words:

> "You are trying to reduce the time managers spend chasing call notes, and the bigger concern is that weak discovery reaches the forecast too late. You want a change in place before the next hiring round. Have I understood that correctly?"

Correct anything you missed. Then suggest a next step tied to the decision process, with a date and the right people involved.

> "It sounds useful to test this with two reps and review the calls with your sales manager. Shall we book that session for next Thursday and include her?"

"I will send something over" leaves both sides guessing. A useful next step has an owner and a reason. Later in the deal, the right closing technique still depends on the evidence you gathered here.

Sales Discovery Questions, Grouped by What You Need to Learn

Use these discovery call questions as options. They are grouped around the sales evidence you need. Choose the ones that fit the answer in front of you, then follow the thread instead of reading down the page.

Current situation

1. "Walk me through how the team handles this today."
2. "Where does that process tend to break?"
3. "Can you give me a recent example?"
4. "How often does that happen?"

Problem and impact

1. "What happens when the problem shows up?"
2. "How does it affect revenue or your team's time?"
3. "Which number would improve if you fixed it?"
4. "Who feels the effect most?"

Desired outcome

1. "What would you want to change first?"
2. "How would you know the change worked?"
3. "What would that result make possible for you?"
4. "Which part matters most to the people approving this?"

Timing

1. "What prompted you to look at this now?"
2. "Is there a date you are working toward?"
3. "What happens if the current approach stays in place for another quarter?"
4. "Which event could change the timeline?"

Budget and resources

1. "Has the team set aside budget for this?"
2. "Where would the money come from?"
3. "How will the company judge whether the investment is worthwhile?"
4. "Which approval does a purchase at this level need?"

Stakeholders and decision process

1. "Who else needs to be involved in the decision?"
2. "Who will use the solution day to day?"
3. "What happens inside the company after this call?"
4. "Who can approve the final purchase?"

Previous attempts and alternatives

1. "What have you tried already?"
2. "What worked well enough to keep?"
3. "Why did the previous approach fall short?"
4. "Which other options are you considering?"

Objections and hidden concerns

1. "What part of this change would be hardest for the team?"
2. "Which concern have we not covered?"
3. "What could stall the project after this call?"
4. "Based on what you have heard, is there a reason you would stop here?"

The last question gives the buyer permission to say no. That answer is more useful than a polite follow-up that never turns into a decision.

A Discovery Call Script You Can Adapt

Use this discovery call script for sequencing. Change the words to sound like yourself.

Opening

> "Thanks for making the time. We have 30 minutes. I would like to understand what prompted the conversation and how you handle it today. If there is a fit, we can agree on a useful next step. What would you like to make sure we cover?"

Reason for the call

> "What was happening when you decided to book this?"

Follow with:

> "Can you give me a recent example?"

Current process

> "Walk me through what happens today, starting when the issue first appears."

Follow with:

> "Where does the process tend to break?"

Impact

> "What does that create for the business?"

If the answer stays vague:

> "You mentioned managers spend a lot of time on it. Roughly how much time did it take last week?"

Desired change and timing

> "If you fixed this, what would be different for the team?"

> "Is there a date when you need that change in place?"

Budget and decision

> "If the approach fits, how would the company fund it?"

> "Who else would need to assess the solution before you decide?"

Concerns

> "What could make this difficult to adopt?"

If the buyer hesitates:

> "It sounds as if there is a concern behind that. Which part gives you pause?"

Recap and next step

> "Let me check that I have this right. [Summarise the current problem in the buyer's words.] It is affecting [business impact], and you want it addressed by [date]. [People involved] will take part in the decision. Did I miss anything?"

> "The next useful step would be [specific action] with [people]. Shall we put that in the calendar for [date]?"

Some buyers will answer several sections at once. Skip questions they have already answered. A script should reduce mental load, not make the conversation sound rehearsed.

Discovery Call Template and Checklist

Copy this discovery call template into your CRM or notes. Write short evidence under each heading. Leave a field blank if you did not learn it.

Before the call

1. Account and role:
2. Reason they booked:
3. Relevant history:
4. Problem hypothesis:
5. Two questions I need answered:
6. Useful proof or company knowledge:

During the call

1. Current process:
2. Specific problem:
3. Recent example:
4. Business impact:
5. Desired outcome:
6. Why now:
7. Target date:
8. Budget source:
9. Users:
10. Decision maker:
11. Other stakeholders:
12. Approval steps:
13. Previous attempts:
14. Alternatives:
15. Stated concern:
16. Concern I should test:

Before ending

1. Buyer recap confirmed:
2. Next action:
3. Owner:
4. Date:
5. People joining:
6. Open question:

After the call

1. Evidence that supports a real opportunity:
2. Evidence that weakens the opportunity:
3. Follow-up promised:
4. CRM fields to update:
5. Coaching point for the next call:

The blank fields are useful. They show what you still need to learn and stop assumptions from turning into CRM facts.

A B2B Discovery Call Example

This fictional example shows how the flow works. The company and people are invented. The numbers are illustrative.

A rep for a sales call assistant is speaking with Elena, the operations director at a 35-person consulting firm.

Elena: "Our client directors spend too much time sorting out notes after calls. We want AI summaries."

Rep: "Walk me through what happens after a client call today."

Elena: "Each director writes their own notes. Some do it straight away. Others leave it until Friday, then the project manager chases them."

Rep: "Can you think of a recent time when that caused a problem?"

Elena: "Last month a client agreed to expand a project, but the action was buried in somebody's notes. We followed up five days later."

Showing the summary feature now would cut the discovery short. The rep stays with the consequence.

Rep: "What did the delay affect?"

Elena: "The client had started talking to another firm. We kept the work, but the partner got involved and was furious."

Rep: "Is the main goal faster notes, or is there something else you need to catch in those calls?"

Elena: "Faster notes help. The bigger issue is consistency. We have eight new consultants starting in October, and the partners cannot review every call."

The timing now has a reason. The rep continues into the buying process.

Rep: "If you found the right approach, how would you fund it, and who would need to approve it?"

Elena: "It would come from our operations budget. I can approve a pilot. The managing partner signs an annual agreement, and IT will review where recordings go."

Rep: "What would IT be most concerned about?"

Elena: "A bot joining client meetings would be a problem. Some clients will not allow it."

Rep: "Understood. Convo runs on the consultant's computer and does not send a bot into the meeting. Rather than cover every detail now, I suggest a short technical review with IT and a pilot with four consultants before the October intake. Would that let you judge the fit?"

Elena: "Yes. Send me two times for next week and I will bring our IT lead."

The rep learned that note-taking was the entry point, while consistency across new hires was the business reason to act. They also surfaced a privacy constraint and an available pilot budget. The rep knows who takes part in an annual decision, so the next meeting has a purpose and the right stakeholder.

Discovery Call Mistakes That Hide Deal Risk

Starting the product tour too soon

A feature can match the first problem the buyer names and still miss the reason they would spend money. Follow the problem into impact before showing how you solve it.

Asking questions without following the answers

Five thoughtful questions with follow-ups beat 30 disconnected prompts. If the buyer says, "The last rollout failed," ask what failed and who remembers it.

Accepting vague pain

"It takes too long" needs a recent example or a number. Vague pain produces vague business cases.

Treating qualification fields as a form

Sales methods such as BANT or MEDDPICC can help a team inspect deals. Buyers do not speak in CRM fields. Ask in the order that fits the conversation and record the evidence afterward.

Avoiding budget or authority

Reps often postpone these questions because they do not want to damage the rapport. Context and tone make them easier. Explain why you are asking, then use plain words.

Solving every objection on the spot

An objection may contain a question or a bad past experience. It can also hide a concern about internal politics. Clarify which one you heard before reaching for an answer.

Treating politeness as commitment

"Send me some information" can mean interest or a graceful exit. Ask which information would help and who will review it. Then confirm what decision follows.

Ending without a dated action

"We will follow up next week" gives neither person a commitment. Book the next action while the context is fresh.

Using the same structure for every deal

A founder buying a small tool may cover discovery and decision in one conversation. A larger deal may need separate user and commercial calls. Give technical reviewers the space they need as well. Keep the information standard consistent while adapting the route.

How to Make Strong Discovery Repeatable Across the Team

A sales leader cannot improve discovery by asking reps to "go deeper." The team needs shared exit criteria and evidence from real calls.

Define what a rep must know before advancing an opportunity. Your sales playbook should show the questions that help and the evidence that counts. It should also set the next step expected at each stage. Managers can then review what the buyer said instead of scoring a rep's confidence.

Call reviews should focus on one or two moments. Find the answer the rep accepted too fast or the concern they missed. Give them a better follow-up to try. An AI sales coach can anchor that feedback to the call and bring the manager's advice back when a similar moment appears later.

Convo supports the same habit during live conversations. It identifies buying signals and shows which parts of discovery remain unclear. It can then suggest a relevant next question before the opportunity passes. The outcome for the rep is a clearer next step. The sales leader gets earlier evidence about deals that may stall.

Frequently Asked Questions

What is a discovery call? A discovery call is an early sales conversation where the rep and buyer assess the problem and its business impact. They also examine the buying process and decide whether a next step makes sense. Both sides should leave with more clarity than they had before the call.

What is the purpose of a discovery call? The purpose is to decide whether there is a problem worth solving and enough mutual interest to continue. The rep also learns what the buyer needs to achieve and what could block the purchase. They identify who will take part in the decision.

How do you structure a discovery call? Start with a shared agenda, then understand the current process and follow the problem into its impact. Cover timing and budget once the context is clear, then map the decision process. End by recapping the buyer's words and agreeing on a dated action.

How long should a discovery call be? Book 30 minutes for a focused first conversation. Use 45 minutes when the product or buying group adds complexity. Several focused calls work better than forcing user needs and commercial terms into one long meeting. A technical review can have its own slot.

What questions should you ask on a discovery call? Ask about the current process, a recent example of the problem, its business impact, the desired change, timing, budget, stakeholders, past attempts, hidden concerns, and the next step. Pick questions that fit the answer in front of you rather than reading a fixed list.

Should you ask about budget on a discovery call? Yes, once the buyer has explained the problem and desired outcome. Ask whether budget exists and where it would come from. Then learn what approval the purchase needs. If the buyer will not discuss an exact amount, find out how the company expects to fund and assess the investment.

What is the difference between a discovery call and a cold call? A cold call creates enough relevance and interest to earn more time. A discovery call uses that time to understand the buyer's situation and assess fit. A short cold call can include a little discovery, but it rarely supports the depth of a scheduled conversation.

Should a discovery call include a product demo? Include a short product view when it helps test a need the buyer has described. Avoid a standard tour before you understand the problem. Complex products often deserve a separate demo shaped around the buyer's use case and attended by the right stakeholders.

How should you end a discovery call? Recap the problem and its impact in the buyer's words, then confirm the buying context. Ask them to correct you. Agree on a next action with an owner, date, purpose, and the people who need to attend.

What are common discovery call mistakes? Common mistakes include presenting too early, accepting vague pain, reading a question list, avoiding budget, missing hidden stakeholders, answering an objection before clarifying it, and ending without a dated action.

Can AI help with discovery calls? Yes. AI can identify buyer signals during the conversation and remind the rep which areas remain unclear. It can suggest a relevant follow-up while the buyer can still answer it. Managers can also use call evidence to coach one specific moment and reinforce that lesson on a later call.