Discovery Call Script Templates

Opening

Hi prospect name, thanks for making the time -- I know day can get busy. Before we dive in, I want this to be useful for you, not a pitch.

Set the agenda

Here is what I had in mind: I will ask a few questions about how your team handles area today, share how we have helped companies like similar company, and if it makes sense, we will talk about a next step. If not, that is completely fine.

Confirm and hand over

Does that work for you? And is there anything specific you were hoping to get out of our meeting length together?

Why it works

Opening with their time and their goals, not your product, lowers the guard. Naming the agenda and giving them an easy exit signals you are there to qualify a fit, not to corner them, which makes the honest answers you need in discovery far more likely to come out.

Ask about the current state

Walk me through how your team handles process right now. Who owns it, and what tools are in the mix?

Get specifics

How long has it worked this way? And roughly how many volume are you dealing with in a typical time period?

Understand the trigger

What made you take this call now, as opposed to six months ago or six months from now?

Listen for the gap

When something goes wrong in that process today, how do you usually find out about it?

Why it works

Situation questions map the ground before you prescribe anything. Asking who owns the process, which tools they rely on, and how much volume flows through in a time period gives you the facts to tailor everything that follows. Prospects also relax when the first questions are easy and clearly about them, which builds the trust you will spend later asking about pain and budget.

Surface the pain

You mentioned process is handled manually today. Where does that tend to break down or eat up time?

Quantify the friction

When that happens, what does it cost you -- is it cost type, rework, or something falling through the cracks?

Explore the ripple

Who else feels it when problem happens? Does it reach affected team or your customers?

Test how much it matters

On a scale where ten means you would fix this tomorrow, where does solving problem sit for you right now?

Why it works

Pain questions only work after you have earned them with situation questions. By asking where process breaks, who it touches, and how much it matters, you let the prospect articulate the problem in their own words. People commit to solving problems they said out loud, not ones you told them they have, so your job here is to ask and then stay quiet.

Add up the cost

So if problem is costing roughly cost estimate every time period, what does that add up to over a full year?

Make it concrete

What could your team do with that time or budget back? Where would affected team focus instead?

Picture doing nothing

If nothing changes and you are having this same conversation next year, what does that look like for you?

Anchor the upside

And if this were solved cleanly, what is the one outcome that would make it clearly worth it?

Why it works

Impact questions turn a vague annoyance into a number the prospect cannot unsee. Naming what problem costs per time period, then contrasting it with the cost of doing nothing, builds the urgency that budget decisions require. You are not pressuring them; you are helping them weigh a real trade-off, which is exactly the frame a good buyer wants before they spend.

Open the budget conversation

To point you at the right option and not waste your time, do you have a budget range in mind for solving problem?

Understand the decision

Besides yourself, who else weighs in on a decision like this? I want to make sure decision maker has what they need.

Map the process

What does a yes actually look like inside company -- is there an approval step I should plan around?

Pin the timeline

And when would you want this live? Is there a deadline driving that, or is it more when the fit is right?

Why it works

Budget, authority, and timeline are where soft deals fall apart, so you ask directly but with a reason attached -- to save their time and route them correctly. Framing questions about decision maker and the approval step as help rather than interrogation keeps the tone collaborative while still surfacing whether this deal can actually close and when.

Play it back

Let me make sure I have this right: problem is costing you around cost estimate, it touches affected team, and you would want it solved by deadline. Did I miss anything?

Bridge to the next step

Based on that, the logical next step is next step -- that is where I can show you exactly how this would work for your situation.

Book it now

I have time option one or time option two open this week. Which works better for you?

Confirm and close

Great, I will send a calendar invite and a short agenda so you know exactly what to expect.

Why it works

Summarizing in their words proves you listened and lets them correct the record before you propose anything. Tying the next step directly to the pain they described, then offering two concrete times instead of asking if they are interested, turns a good conversation into a booked meeting rather than a polite dead end that never gets followed up.