Discovery Call Script and Questions: A Structure That Wins Deals

The discovery call is where most deals are won or quietly lost. Not because of the pitch — there usually is not one yet — but because of what you learn, what the prospect realises while explaining their problem aloud, and whether they leave feeling understood. A good discovery call makes the rest of the sales process shorter. A poor one produces a proposal nobody reads.

This guide gives you a structure you can use tomorrow: a call outline, the questions worth asking, how to handle the objections that reliably appear, what to do in the minutes after you hang up, and how to review calls so the whole team improves. It is a framework, not a script to read word for word — the difference matters, and we will come back to it.

Key takeaways

What a discovery call is for

A discovery call has four jobs, and a pitch is not one of them.

• Understand the situation. What is happening, what have they tried, and why now.
• Establish the stakes. What the problem costs in money, time or risk, in the prospect’s own words.
• Map the decision. Who else is involved, what the process is, and what a good outcome looks like to each of them.
• Decide together whether to continue. Sometimes the right outcome is “this is not a fit”, and finding that out in thirty minutes is a good result.

That last point is the one most often missed. Salespeople who treat every call as something to be won tend to push unsuitable prospects through the pipeline, where they stall, churn or complain. A call that ends with an honest “we are probably not the right choice for you” costs you half an hour and earns a referral.

Before the call: ten minutes of preparation

The prospect’s patience for being asked things you could have looked up is short. Preparation is what lets you spend the call on questions only they can answer.

• Read the record. What did they fill in on the form? Which page did they come from? Have they spoken to anyone here before? Asking someone to repeat what they already wrote is a poor start.
• Look at the company. Size, what they sell, recent news, who they appear to compete with. Two minutes is enough.
• Write down your goal for the call. One sentence: what must be true when you hang up for this call to count as a success?
• Open the outline. Have your question list in front of you, not in your head.

The call structure

A thirty-minute discovery call has a rhythm. The proportions below are approximate, but the order matters: context first, then problem, then impact, then decision, then next step.

1. Opening and agenda

Greet them, confirm how long you have, and state what you would like to do. This takes under a minute and changes the tone, because it gives the prospect an active role.

2. Situation

Start broad and let them talk. You are building a picture, not interrogating.

• “Tell me about the business and what you do day to day.”
• “What prompted you to get in touch now?”
• “How are you handling this at the moment?”
• “What have you tried already, and what happened?”

The second question is the most valuable. “Why now” reveals urgency, the trigger event and often the real problem, which is frequently not the one in the form.

3. Problem and impact

This is the heart of the call. Move from what is wrong to what it costs.

• “What is the biggest obstacle to getting that result?”
• “How long has this been a problem?”
• “What does it cost you when it goes wrong — in time, money or lost customers?”
• “What happens if nothing changes in the next six months?”
• “If this were solved, what would be different?”

Listen for specific numbers and let the prospect do the arithmetic. “We lose about two jobs a week because we call back too late” is worth ten times any benefit you could list. Repeat their words back accurately; they will often add detail once they hear it said back.

4. Decision and timing

Prospects who skip this section produce the deals that stall at “I need to run it by someone”. Ask plainly and without apology.

• “Who else will be involved in a decision like this?”
• “What would you need to see to feel confident?”
• “Have you set a budget, or is that still being worked out?”
• “When would you like this solved by, and what is driving that date?”
• “Are you looking at other options?”

Do not leave budget until the proposal. A prospect who cannot discuss it in outline is either not the buyer or not ready, and you would rather know now.

5. Fit and next step

Summarise what you heard in a few sentences — this is the moment to prove you listened — then say plainly whether you think you can help. If yes, propose a specific next step with a date: a demo, a proposal review, a call with the other decision-maker. If no, say so and suggest an alternative.

“I will send some information” is not a next step. “I will send the proposal tomorrow, and we will walk through it Thursday at two with Dana joining” is.

Script or structure?

People argue about this as though it were binary. It is not. A script in the sense of fixed wording to be read aloud tends to make calls worse: the rep listens for the next line instead of to the answer, and prospects notice. A structure — an agreed order, a bank of good questions, prepared responses to common objections — makes calls better, because the rep’s attention is free for the person on the line.

Treat what is written down as a talk track: an objective, an opening, a list of questions to draw from, key points to land, and a few considered responses to objections. Use it as a map rather than a teleprompter. Different calls deserve different tracks — a first discovery call, a qualification call, a follow-up and a closing call have different goals — so keep a small library rather than one document that tries to cover everything.

Handling the objections that always appear

Objections are information. The skill is to understand them before answering, because the stated objection is often not the real one.

The pattern across all of these is the same: acknowledge, ask a question, listen. If you find yourself arguing, you have stopped diagnosing.

After the call: the ten minutes that decide the outcome

What happens in the minutes after you hang up determines whether the call produces a deal or fades. Three things matter.

Record the outcome immediately

Log what happened while it is fresh: the outcome of the call, the prospect’s own words about the problem and its cost, the people involved, the timeline and the agreed next step. A short, consistent set of outcomes — connected, voicemail, no answer, callback requested, not interested — makes pipeline reporting meaningful, because “we spoke” stops being a catch-all.

Send a follow-up within hours

A short summary email that repeats what you heard, confirms the next step and its date, and attaches anything you promised. It shows you listened, gives the prospect something to forward and keeps momentum while the conversation is still current.

Set the next action

Create the task, with a due date, for the thing you committed to. The most common cause of a stalled deal is a follow-up that existed only in someone’s intentions.

Reviewing calls so the team gets better

The fastest way to improve discovery is to listen to real calls, and most teams never do because there is no time. Make it small enough to happen.

• Record calls where you are permitted to. Laws on recording and consent differ by location, so tell people at the start and follow the rules that apply to you and to them.
• Review a handful a week, not everything. Two calls each, picked at random, is enough to find patterns.
• Measure talk ratio. Who spoke for how long. If the rep talks for most of a discovery call, that is the finding.
• Look for the questions that unlocked something. The best ones are worth adding to the shared outline.
• Track the objections. If “too expensive” appears in half your lost calls, the problem is upstream of the call.
• Coach on one thing at a time. A list of ten improvements produces none.

Summaries generated by AI can make this faster by pulling out key points, action items, objections raised and questions asked from a recording. Treat them as a starting point to check against the call, not as a record of what was said — they are good at structure and occasionally wrong about detail.

Mistakes that quietly cost deals

• Pitching too early. Once you start describing your product, the prospect stops describing their problem.
• Asking only closed questions. “Do you have a budget?” gets a yes; “How are you thinking about budget?” gets an answer.
• Filling silence. A pause after a good question is the prospect thinking. Count to five before speaking.
• Skipping the cost of the problem. Without it, price is the only thing left to discuss.
• Ending without a dated next step. Hope is not a process.
• Never saying no. Qualifying out unsuitable prospects protects your close rate and your reputation.

How Scalry handles this

Scalry includes a calling module alongside the CRM, so the call, the contact and the follow-up are in one place rather than three. You can keep a library of call scripts by type — discovery, qualification, follow-up, demo, objection handling, closing — each with an objective, an opening, a list of questions, talking points, objection responses and a closing. Reps call from the browser, and each call can be logged against the contact with an outcome from a configurable list of dispositions.

Calls can be recorded where you are allowed to, and Scalry can produce an AI summary of a recording with key points, action items, questions asked and objections raised, along with a sentiment reading and a quality score. For outbound days there is a call queue with priorities, so a rep works through a list of contacts without hunting for the next one.

Because everything is attached to the contact, the next step you agreed on the call can be created as a task straight away, and anyone picking up the account sees what was actually said. As with the structure above, the tooling removes admin; it does not conduct the conversation for you. The listening is still yours.

Questions to ask before you commit

Whichever way you are leaning, these are the questions that change the answer. Work through them against your own numbers rather than anyone's feature matrix — including this one.

• Do our reps share an outline, or does each call depend on the person?
• What proportion of the call does the prospect speak? Listen to three recent calls and note it.
• Do we learn the cost of the problem, in the prospect’s words?
• Do we know the decision process before we send a proposal?
• Does every call end with a dated next step?
• How consistently are outcomes recorded? If “spoke” is the only category, pipeline reports cannot be trusted.

If you cannot answer the first three, you are not ready to choose between Scalry and your current discovery process yet — you are still deciding what you need, which is a cheaper problem to solve first.

A first-week plan

Day 1: write the outline

Take the structure above and write your own version: an opening, six to eight questions across situation, problem, impact and decision, and responses to the three objections you hear most. One page.

Days 2–3: run it on live calls

Use it on your next five calls and change nothing yet. Note which questions produced real answers and which fell flat.

Day 4: define the outcomes

Agree a short list of call outcomes the whole team uses, and a rule that every call is logged within ten minutes.

Day 5: review two calls

Listen to two calls and measure talk ratio. Pick the one improvement that would help most and focus on it next week.

Frequently asked questions

What is a discovery call?

A discovery call is an early conversation in the sales process where you learn about the prospect's situation, the problem they want solved, what it costs them, who is involved in the decision and what timeline they are working to. The goal is to diagnose and decide whether there is a fit, not to pitch.

What questions should I ask on a discovery call?

Cover five areas: their situation and why they got in touch now, the biggest obstacle, what the problem costs in time or money, who else is involved in the decision and what budget and timeline exist. Open questions that start with how, what and why produce better answers than yes-or-no questions.

How long should a discovery call be?

Twenty to thirty minutes suits most situations, with the majority of the time spent on the problem and its impact. Longer calls are justified for complex, high-value sales, but the structure stays the same.

Should I use a script for discovery calls?

Use a structure rather than a word-for-word script. A fixed order of topics, a bank of good questions and prepared responses to common objections keep calls consistent, whereas reading lines aloud makes you listen for your next line instead of the prospect's answer.

How do I handle the objection that it is too expensive?

First find out what it is being compared with, then return to the cost of the problem the prospect described earlier. Price objections usually mean the value has not been established, or the budget is not there — and you want to know which before you respond.

What should I do after a discovery call?

Log the outcome and the prospect's own words straight away, send a short follow-up email summarising what you heard and the agreed next step, and create a dated task for anything you committed to. Most stalled deals stall because the follow-up existed only as an intention.

Is it legal to record sales calls?

It depends on where you and the other person are. Some places require consent from everyone on the call, others from one party. Tell people at the start of the call that it is being recorded and check the rules that apply to you, particularly for calls across state or national borders.