The Discovery Call Script Top B2B Reps Use Right Now

Discovery Calls Die Before the First Real Question

One rep went back through 34 recorded calls. On calls where he invested 25 to 30 minutes in pure discovery before touching the product, his close rate hovered near 40%. On calls where he led with the product early, he closed maybe 6 deals total across the entire batch.

A completely different business outcome from the same leads, the same product, and the same rep.

Sequence is the difference.

Discovery call advice online is still stuck on generic frameworks like BANT and SPIN, generic question lists, and tips like "build rapport" and "ask open-ended questions." None of that is wrong. None of it is specific enough to change what you do tomorrow morning.

This article is different. What follows is a word-for-word discovery call script built from what practitioners are doing right now, why the first 5 minutes determine 80% of your outcome, and the pre-call move that separates reps closing at 30% from reps closing at 55%.

The Number That Should Change How You Prep

Top-performing sales reps ask 39% more questions during discovery calls than their peers, and they hold discovery calls that run 76% longer. These are benchmarks worth taking seriously. Reps who hit quota ask more questions and run longer calls than reps who miss it.

Meanwhile, discovery calls under 20 minutes show 42% lower advancement rates compared to calls in the 41 to 50 minute range. If your average discovery is wrapping up at 18 minutes, you are leaving deals on the table by default.

The sweet spot for question volume is 11 to 14 questions. Fewer than 11 and you have not covered enough ground. More than 14 and you start losing the conversational thread. The goal is focused depth, not a checkbox audit.

Here is the other number worth knowing before you open the script: Databox research puts the conversion rate from discovery calls to closed deals at 10 to 30% across B2B. That range is enormous. The difference between 10% and 30% is almost entirely execution on the call itself. This script is designed to push you toward the top of that range.

The Pre-Call Email

Before we get into the call itself, there is a move that changes the quality of every discovery conversation you have - and almost no one does it.

Send a short email 24 to 48 hours before the call. Not a reminder. Not a calendar confirmation. A priming question.

The format looks like this:

"Thanks for booking. Before our call, I want to make the most of your time. We'll be covering [topic A], [topic B], and [topic C]. Quick question before we connect: [specific question tied to their situation]? Even a quick answer helps me tailor the conversation."

What happens next is the point. About half of prospects ignore it. The other half respond and tell you exactly what is on their mind before you ever dial. Either outcome advances the deal.

If they respond, you walk into the call already knowing their biggest concern. You can open with it directly instead of fishing for it with generic openers. You look prepared. You sound like someone worth talking to.

If they do not respond, you have still done something important. You have set an agenda. They know the call has a purpose. They show up ready to engage rather than waiting to see what you are going to pitch them.

This tactic is especially powerful in cold outreach contexts. One operator who runs personalized cold email campaigns reported that pre-call priming emails - sent after a meeting was booked - dramatically increased the quality of the first few minutes. The prospect arrived oriented, not guarded.

The specific question matters. Generic questions like "what are your goals?" get ignored. Specific questions like "what's the one thing that would need to be true for this to be worth your time?" or "what have you already tried that hasn't fixed this?" get answered. Make it feel like you already know something about their situation, because you should.

The Opening Line That Went From 30% to 55%

The single highest-leverage moment in any discovery call is the first 60 seconds. I've seen this documented from multiple angles: discovery calls die in the first 5 minutes, and the cause is almost always the same. The rep starts talking about themselves or their product before establishing why the prospect showed up.

One rep documented a close rate jump from 30% to 55% after changing only his opening line. The old opener was a product overview. The new one was this:

"Before we start, I want to make sure we use your time well. Can you tell me what you were hoping to get out of this call specifically?"

That question does three things at once.

First, it signals that you are not there to pitch. You are there to listen. That lowers the prospect's guard immediately.

Second, it forces them to articulate their expectation out loud. People who have to say what they want from a call are more engaged in that call. They have invested something.

Third, and most importantly, it tells you immediately what kind of buyer you are talking to. You can sort the answer into three buckets on the spot.

• Bucket 1: "I'm just exploring options." This is a browsing buyer. Not a close this week, but worth a slower qualification.
• Bucket 2: "Our current solution is breaking and we need something fast." Move with urgency.
• Bucket 3: "My boss told me to take this call." This is the wrong person. You need the boss on the call, not the employee they sent.

Knowing which bucket you are in within the first 90 seconds changes everything about how you run the next 40 minutes. You stop guessing and start responding to what is in front of you.

A closely related opener that works just as well, and surfaces the same three buckets, is this one:

"Before we get into anything - what made you take this call today?"

Both openers share the same structure. They invite honesty before obligation. They put the prospect in charge of the first real answer. And they give you signal that no amount of research can replace.

Phase 1 - Situation Questions That Do Not Waste Anyone's Time

One of the most pointed critiques in practitioner communities about standard discovery is this: buyers arrive at your call having already researched your product, read your pricing page, and maybe looked at two competitors. When your rep spends the first 20 minutes asking questions the buyer already answered on your website, trust evaporates.

Showing up with context is now table stakes. It is not impressive. It is the minimum requirement to be taken seriously. Use the 15 to 20 minutes before every call to research the prospect's company, role, recent news, and any signals that something has changed - a funding round, a leadership hire, a job posting that hints at a new initiative.

Then open situation questions with what you already know, not what you do not.

Compare these two approaches:

Weak: "Can you tell me a bit about your company and what you do?"

Strong: "I saw you recently brought on two new AEs. How long have they been ramping?"

The second question does not just gather information. It shows you did your homework. It opens a thread. And according to practitioners who document the "discovery depth ladder," insight comes 3 levels deep - not at the surface question.

• Level 1: "You just hired two AEs."
• Level 2: "How long is your onboarding process?"
• Level 3: "Have they closed anything yet?"
• Level 4: "What is the hardest part of ramping a new rep for you?"

Level 4 is where deals are made. I watch reps stop at Level 2 every single week. Pull the thread. Do not jump topics. The expertise you show at Level 4 is worth more than any case study you could mention.

Situation questions that get the most useful responses:

• "What's going on in your world that made you decide to talk to me?"
• "What do you like about your current setup?"
• "Walk me through how you're handling this right now."

Notice what is not on this list. "What are your goals?" is absent. It is too broad to produce useful answers. Specific, situational questions produce specific, useful answers.

Phase 2 - Pain and Consequence Questions

I see it constantly - reps find the pain. Fewer reps find the consequence. Deals stall because of it.

A prospect telling you they have a problem is not enough to close a deal. They need to feel the weight of that problem staying unsolved. Moving them from "yes, we have that issue" to "we cannot afford for this to stay the same" is what Phase 2 questions are built to do.

The most effective pain and consequence questions, as documented by practitioners:

• "What happens if nothing changes?"
• "How does this affect you personally?"
• "What would solving this allow you to do that you can't do right now?"
• "Why hasn't this problem been fixed before today?"

That last question is the most underused one in the set. When a prospect has been dealing with a problem for months or years and nobody has solved it, there is always a reason. Maybe previous solutions failed. Maybe internal politics blocked a purchase. Maybe they tried to fix it internally and could not. Whatever the answer, it tells you exactly what objections you will face and what your solution needs to overcome to win the deal.

The "why hasn't this been fixed" question also does something subtle and powerful. It signals that you understand this problem did not appear yesterday. It positions you as someone who has seen this before, which builds credibility before you have said a single word about your product.

Mentioning a specific pain point within the first 2 minutes of a discovery call increases the call's success rate by 25%. That is not a small margin. Open Phase 2 early. Do not wait for the back half of the call to surface the pain. The sooner a prospect is talking about their problem in their own words, the more invested they become in the conversation.

Phase 3 - The Qualification Questions Experienced Reps Use

There is a legitimate debate in sales circles about how to qualify on a discovery call. The old BANT framework - Budget, Authority, Need, Timeline - is still cited everywhere and still misapplied everywhere.

Here is the nuance that gets cut from most frameworks: budget is not binary. One experienced rep with a strong track record made this argument plainly - just because there is no budget today does not mean there will be no budget tomorrow. Disqualifying a deal because a prospect says "we don't have budget" is often a mistake. Budget is fluid. The better question is whether the problem is painful enough that budget will move.

The qualification questions practitioners use:

• "Who has the final say if you decide to move forward?"
• "Is this project funded?" (Use with nuance - see above)
• "How does this project stack rank against other priorities right now?"
• "What is your timeline for making a decision?"
• "What does success look like in 6 months if this works?"
• "If this solves your problem and the numbers make sense, are you ready to move forward this week?"

That last question is a commitment test, not a close. It is used early - within the first 10 minutes in some cases - to separate serious buyers from window shoppers. A prospect who flinches at "are you ready to move forward" in the first 10 minutes is giving you extremely valuable information. You have not wasted 45 minutes on someone who was never going to buy.

The three-question mutual qualification framework that top practitioners use internally before investing full discovery time:

1. What is your timeline? (Reveals serious vs. browsing)
2. What is the cost of not solving this? (Reveals whether they understand the value of a solution)
3. What does success look like in 6 months? (Reveals strategic thinking and whether they are a real decision-maker)

Notice the word "mutual" in that framework. Qualifying each other is a structural change in how the call runs. Both sides are deciding whether it makes sense to go further.

One practitioner described this reframe directly: "Tell them how you work, what it costs, what the commitment looks like - and then ask if that aligns. Flip the power dynamic. Let low-quality prospects disqualify themselves." This approach filters out time-wasters fast and positions every serious conversation as a partnership rather than a pitch.

The Complete Word-for-Word Discovery Call Script

What follows is a full script built from the practitioner data above. It is not a rigid script. It is a sequence of moments with specific language options that work. Use it as a skeleton, not a teleprompter.

Opening (Minutes 0-3)

"Hey [Name], good to connect. Before we dive in - I want to make sure we use your time well today. What were you hoping to get out of this conversation specifically?"

[Listen. Identify bucket: exploring, urgent need, or wrong person. Adjust accordingly.]

If exploring:

"Got it - so you're in research mode. That's totally fine. I'd rather spend this time helping you figure out if there's even a fit than pitching you on something that might not apply. Sound good?"

If urgent:

"Let's make sure we cover what matters most. Tell me more about what's going on."

If wrong person:

"Appreciate you jumping on. Quick question - who else is typically involved when your company evaluates something like this? Would it make sense to loop them in for part of this call or set up a follow-up?"

Situation (Minutes 3-10)

"Before we go any further - I did some research before this call. I noticed [specific thing you found - job posting, news item, LinkedIn signal]. Is that related to what's bringing you here today?"

[Pull the thread. Ask 3 to 4 levels deep on one thread before moving to the next.]

"What's going on in your world that made you decide to take this call?"

"What does your current process look like for handling this?"

"What do you like about how you're doing it now?"

Pain and Consequence (Minutes 10-22)

"Where does this break down today?"

"Why hasn't this been fixed before today?"

"How does this affect you personally - not just the team?"

"What happens if nothing changes over the next 6 months?"

"What would solving this allow you to do that you can't do right now?"

[Pause after each answer. Let them expand. Do not rush to the next question. The silence after a good pain question is worth more than your next question.]

Qualification (Minutes 22-32)

"Who has the final say if you decide to move forward with something?"

"How does this project rank against other things competing for budget and attention right now?"

"What's your timeline for wanting to have a solution in place?"

"If this solves the problem and the numbers work - is there anything that would stop you from moving forward?"

[This last question is Phase 4 territory in disguise. Any answer other than "no" is a real objection. Treat it as such.]

Closing the Call (Minutes 32-45)

"Based on what you've shared, here's what I'm hearing [summarize their situation in their words]. Does that feel accurate?"

"Here's where I think we can help and where we might not be the right fit [be honest about both]. Does that match what you're looking for?"

"What would a useful next step look like from your side?"

"Are there any reasons not to move forward together if this ends up being a fit?"

That last question comes straight from practitioners who call it their highest-upvoted discovery close. It is disarming because it invites the prospect to surface objections in a low-pressure moment. They tell you what stands between you and a deal. You now have a map.

The Discovery-Into-Demo Mistake Almost Everyone Makes

Here is a discovery call angle that almost no competitor content covers: discovery does not stop when the demo starts.

I watch reps treat discovery and demo as sequential phases. Discovery ends. Demo begins. The problem is that the transition usually kills momentum. The rep finishes discovery, says something like "great, let me show you the product," and then runs a generic tour while asking hollow questions like "does that resonate?"

The better move is to carry 3 to 4 discovery questions into the demo itself. These are questions designed to deepen what you already found in Phase 2, not repeat it. Examples:

• "When you see this feature - what's the first workflow you'd apply it to?"
• "Which part of what I just showed would your team use first?"
• "What would your current setup need to do differently for this to be a real improvement?"

These questions do two things. They keep the prospect mentally active instead of passively watching a screen share. And they surface new information - specifically, what the prospect is imagining doing with your product. That imagination is a buying signal. It tells you they are already in "if I bought this" mode.

The rep who documented this approach specifically called out the empty "does that resonate?" prompt as one of the most common dead zones in B2B demos. Replace it with a real question about a specific behavior or outcome, and the second half of your call becomes part of the discovery, not separate from it.

Why Your Script Is Already Outdated for Half Your Buyers

There is a new problem for anyone running a standard discovery call script right now: your buyer arrived having already done 3 hours of research on your product, your competitors, and your pricing before they ever accepted the meeting.

Buyers use AI to pre-research vendors. They read reviews. They compare feature tables. They know more about your product's limitations than some of your reps do. And then your rep opens with "So tell me about your company" or "What's your biggest challenge right now?" The buyer has already mentally answered those questions and moved on.

The fix is to reset your opening assumption. Do not assume you are starting from zero. Start from what they already know.

Replace generic openers with something like:

"Given what you've already looked at about us - what's your biggest remaining concern?"

Or:

"You've probably already looked at [Competitor A] and [Competitor B]. What made you still want to have this conversation?"

This framing does something competitors' scripts do not. It skips the part of discovery that wastes informed buyers' time. It starts the conversation at the level the buyer is at, not the level the script assumes they are at.

It surfaces the objection immediately. An informed buyer who is still on the call has one of two things happening. Either they have not found a reason to say no yet, which means your job is to help them find reasons to say yes. Or they are comparing you against a competitor and trying to find the tiebreaker. Either scenario is a conversation you want to be having in the first 5 minutes, not the last 5.

What the Data Actually Shows About Talk Ratio

In a discovery call, sales reps who talk less than 46% of the time and let prospects fill 54% or more of the conversation close at higher rates. This is the inverse of cold calling, where reps typically need to lead more of the conversation.

The mechanics behind this matter. When a prospect is talking, they are revealing. When they are revealing, they are also convincing themselves. The most effective discovery calls often feel, to the rep, like they hardly said anything. From the prospect's perspective, it felt like the most useful conversation they had that week - because they got to think out loud about a real problem with someone who seemed to care about the answer.

High-performing reps also use 10% more collaborative language than average performers - words like "we" and "us" instead of "I" and "you." Switching one word changes how the prospect hears the entire conversation. The deal outcome difference is not.

Calling out a specific pain point within the first 2 minutes of the call correlates with a 25% higher success rate. Demonstrating that you already understand what they are dealing with is what drives that number. "I know a lot of companies in your space are dealing with [specific problem] right now. Is that something you're running into?" signals expertise and gives the prospect permission to go deeper immediately.

The Pre-Call Intelligence Workflow That Takes 15 Minutes

Good discovery starts before the call. Here is the 15 to 20 minute pre-call research sequence that top reps run before every discovery conversation.

Step 1 - LinkedIn (3 minutes). Look at the prospect's profile, their recent posts, and their current job description. Note anything that suggests a recent change, a new priority, or a challenge they are publicly talking about. If they have posted about a problem in the last 30 days, you know exactly how to open.

Step 2 - Company signals (5 minutes). Check for any recent news: funding, leadership changes, new product launches, partnerships, or job postings. A company posting aggressively for sales roles is under revenue pressure. A company that recently raised is under growth pressure. These are entry points, not small talk.

Step 3 - Their tech stack (3 minutes). Tools like BuiltWith or similar tech stack scrapers show what the company is already using. If they are running a competitor's tool, you know they are already paying for a solution in your category. They are not starting from scratch. Your job is to be better than what they have, not to convince them the problem exists.

Step 4 - The pre-call question (4 minutes). Write one specific question to send in the pre-call email. Base it on what you found in Steps 1 through 3. Tie it directly to something in their situation. Then send it and forget about it. Half will respond. The other half will at least know you did your homework.

Reps who run this workflow before every discovery call sound fundamentally different from reps who wing it. Better context is what separates them. And better context produces better questions. Deeper answers follow from that.

If you are running outbound and building contact lists to fill your discovery calendar, Try ScraperCity free - it lets you search millions of B2B contacts by title, industry, location, and company size so you are booking discovery calls with the right people before you ever need to run the script.

The Questions Experienced Reps Discard (And Why)

Not all discovery questions are worth asking. Experienced practitioners are equally opinionated about what to drop as about what to keep.

"What's your budget?" - I see this every week - reps asking for a budget number directly, putting the prospect on the defensive and producing a low anchor they will try to hold you to. Better question: "Is this project funded?" followed by probing the priority level. And remember the practitioner critique - budget is fluid. Someone who says "no budget" today can have budget next quarter.

"What keeps you up at night?" - This question became a cliche so thoroughly that buyers have a rehearsed non-answer ready. Replace it with something specific to their role: "What's the one part of your current process that takes the most time and produces the least value?" That version is harder to deflect and more likely to surface a real problem.

"Are you familiar with our product?" - If they booked a call with you, they have some familiarity. This question burns time and can make you look unprepared. Replace it with the informed-buyer assumption: "What have you already seen about us, and what's still unclear?"

"Does that make sense?" - This is the verbal equivalent of "does that resonate?" It is a low-value check-in that does not produce useful information. Replace it with "What's your reaction to that?" or "How does that compare to how you're doing it now?"

How to Close a Discovery Call Without Being Pushy

A discovery call close is a commitment to a next step. And I see this every week - reps letting momentum die in the final 5 minutes of a discovery call.

High-performing reps are 2x more likely to use specific "next steps" language on calls than average performers. Specific ones with a name, a date, and a purpose.

Weak: "I'll send some info over and we can reconnect."

Strong: "I'd like to set up 30 minutes with you and [decision-maker] next week to walk through specifically how this would work for your situation. Does Tuesday or Wednesday work better?"

The second version moves the deal forward. The first version creates a follow-up task with no momentum behind it.

Before you close the call, run a quick mutual summary. Repeat back what you heard in their words. Not a paraphrase - their actual language. If they said "our onboarding is a mess," your summary says "onboarding is a mess." If they said "we're losing deals because our response time is too slow," you reflect that back. Using the prospect's exact words signals you were listening and creates alignment without you having to claim it.

Then ask: "Are there any reasons not to move forward together if this ends up being a fit?"

This question is a soft close that functions as an objection harvest. Whatever they say next is your roadmap for the rest of the deal cycle.

What Separates a 10% Close Rate From a 30% Close Rate

The conversion range from discovery to close is 10 to 30%. Almost nothing about your product determines where you land in that range. Almost everything about your discovery process does.

The reps at 10% are treating discovery like a data collection exercise. They get through the questions, present the product, and wait for the prospect to decide. Deals stall because nobody created urgency, nobody confirmed who makes decisions, and nobody established a specific next step with a date attached.

The reps at 30% are doing something different. They use the discovery call to make the prospect feel understood. They let silence sit after hard questions. They pull threads 3 and 4 levels deep instead of skimming the surface. Confirming next steps before the call ends - with a specific name, a specific date, and a specific agenda for what comes next - is non-negotiable.

Closed-won deals involve an average of 6.7 sales team members by the time discovery is complete, per Gong data. If you are only talking to one person on your discovery calls, you are missing half the buying committee. The discovery call is also the right time to map the stakeholders - not the proposal stage.

"Who else needs to be involved in a decision like this?" is one of the highest-value questions you can ask. Ask it early. The answer shapes everything that follows.

The Specific Scripts for Common Discovery Call Moments

In discovery calls, I see this every week - reps hitting specific moments and improvising badly. Here are word-for-word options for the most common ones.

When the prospect is vague about pain:

"Can you give me a specific example of when that caused a problem - like a real situation in the last month or two?"

Specificity breaks vagueness. A prospect who gives you a real example has moved from theoretical to engaged.

When the prospect says "we're happy with what we have":

"That's good to hear. What would have to change for you to consider switching? Is there anything your current setup doesn't do that you wish it did?"

This keeps the conversation alive without dismissing their answer. And it often surfaces something the current solution doesn't cover.

When the prospect tries to rush to the product:

"I'll absolutely show you what we do - I want to make sure when we get there, I'm showing you the stuff that applies to your situation. Give me two more minutes here and I'll make the demo a lot more relevant for you."

This reframes patience as a service to the prospect. You are not delaying the demo. You are making it better.

When the prospect says "we don't have budget":

"I appreciate you being upfront about that. If this solved [specific problem they mentioned] - would budget become available, or is it more about timing?"

If the answer is still no, you have information. If they hesitate, you have a live conversation.

When the prospect stalls on next steps:

"What would need to be true for you to be ready to take a next step on this?"

This is a clean way to get the real objection without being confrontational. Whatever they say is the actual barrier. Now you are negotiating that instead of chasing a ghost.

Building Your Own Discovery Call Scorecard

Once you have a script and a sequence, the next step is measuring whether your calls are improving. Tracking the number of booked calls is an activity metric. It tells you how busy you are, not how good you are getting.

The metrics worth tracking after every discovery call:

• Did the prospect reveal a specific, named consequence of their problem? (The cost of it staying unsolved)
• Did you confirm who the final decision-maker is by name?
• Did the call produce a specific next step with a date attached?
• Did you run at least 25 minutes of discovery before showing the product?
• Did the prospect talk more than 50% of the call?

Score yourself on those five questions after every call. A 5-out-of-5 call that did not close is still a well-run discovery. A 2-out-of-5 call that happened to book a demo is a lucky break that will not repeat.

I watch reps track only deal outcomes and wonder why their close rates stall. Outcomes are lagging indicators. Process quality is a leading one.

The Difference Between a Script and a Framework

Scripts are training wheels. Frameworks are the bike.

The script in this article is designed to get you comfortable with the sequence and the language. But the goal is to internalize the underlying logic - why the opener comes before the situation questions, why pain precedes qualification, why the closing question is an objection harvest rather than a hard close - so that you can adapt in real time.

When a prospect gives you an unexpected answer, a script-dependent rep panics. A framework-fluent rep pulls the thread, goes 3 levels deep, and ends up in a better discovery than the script would have produced anyway.

The fastest way to get from script-dependent to framework-fluent is repetition with feedback. Run every discovery call against your scorecard. Review the recordings. Note which questions produced vague answers and replace them. Find the 2 or 3 questions in your current flow that consistently produce the most useful information and anchor the whole script around them.

In one operator's cold email consulting practice, the single biggest improvement in close rates came not from adding more discovery questions but from identifying which 3 questions produced the most useful buyer signals and making sure those questions were always asked, always in the right sequence, and always followed by silence. The rest of the script was flexible. The core 3 were not.

Find your 3. Protect them. Build the rest of the call around giving those 3 questions the room to land.

FAQ