Discovery Call Script Library for New Reps

Use these scripts as your floor for the first 90 days, not your ceiling. Once you've run 20+ discovery calls and you're getting through them faster than the script allows, you've earned the right to improvise. Until then — run the script.

The Universal Discovery Structure

Every discovery call below follows the same five-part skeleton. Learn this skeleton, not just the words:

1. Open (2 min) — set the frame, get permission to lead
2. Context (3–5 min) — understand their world before you ask about problems
3. Situation → Problem → Impact → Need-payoff (15–20 min) — the core of the call
4. Qualify (5 min) — budget, timeline, decision process, competition
5. Close the call (3 min) — recap, next step, calendar action before you hang up

---

Script 1: SMB / Transactional Discovery (single decision-maker, 20–30 min call)

Open:

"Thanks for making time, [Name]. Here's what I'd like to do in the next 20 minutes — I want to understand what's going on for you right now with [problem area], ask a few questions about how your team handles it today, and then I'll tell you honestly whether we're a fit. If we're not, I'll say so. Sound good?"

Context:

"Before we get into it — tell me a bit about your role and how your day-to-day actually runs. I don't want to assume anything."

(Listen. Take notes. Don't pitch yet.)

Situation questions:

• "Walk me through how you handle [process] today, start to finish."
• "How long has it worked that way?"
• "Who else touches this besides you?"

Problem questions:

• "What's the part of that process that's most annoying, or takes the most time?"
• "Has anything about it gotten worse recently, or has it just always been this way?"

Impact questions:

• "If that stayed exactly the way it is for another 12 months, what does that cost you — time, money, or something else?"
• "Who notices when it goes wrong — just you, or does it show up somewhere else in the business?"

Need-payoff questions:

• "If that part just… worked, what would you do with the time/money that freed up?"
• "What would 'solved' actually look like for you?"

Qualify:

"A few practical questions so I don't waste your time. Is there budget already set aside for this, or would this be a new line item? Who else, if anyone, would need to sign off? And is there a date this needs to be sorted by, or is it open-ended?"

Close:

"Here's what I heard: [one-sentence recap of their problem and impact]. Based on that, I think it's worth a follow-up where I show you specifically how we'd solve [the exact thing they said]. Does Thursday at 2 or Friday at 10 work better?"

(Book it live, on the call. Do not say "I'll follow up to schedule.")

---

Script 2: Mid-Market Discovery (2–3 stakeholders, 30–45 min)

Open:

"Thanks everyone for joining. Quick intros — [Name], you're in [role], and [Name], [role] — did I get that right? Here's the plan: I want to hear from each of you about how [problem area] shows up in your part of the business, because I've found it usually looks different depending on where you sit. Then I'll ask some process questions, and we'll figure out together whether a next step makes sense."

Context (ask each stakeholder in turn):

"[Name], from where you sit, what does this look like day to day?"

(Deliberately go around the room/call — don't let one person answer for everyone.)

Situation questions:

• "How do decisions about [problem area] get made today — is it one team, or does it cross departments?"
• "What tools or process are you using for this right now?"

Problem questions:

• "Where does that process break down, or where do people get frustrated with it?"
• "Is this a top-3 priority for the team this quarter, or is it more of a 'someday' fix?"

Impact questions:

• "Whose numbers get hit when this doesn't work well — yours, [other stakeholder]'s, or does it roll up further?"
• "Has this come up in a leadership conversation, or is it still a below-the-radar issue?"

Need-payoff questions:

• "If you fixed this, what changes for each of your teams specifically?"
• "Is there a number attached to that — time saved, revenue, cost avoided?"

Qualify:

"Help me understand your buying process — is this a decision the two/three of you can make, or does it need to go further up? Is there a budget cycle this needs to align with? And are you looking at anyone else for this?"

Close:

"Here's what I'm hearing across the group: [recap, naming each person's specific angle]. The logical next step is [a scoped demo / a technical deep-dive / a business-case session] with [the right next stakeholder]. Who should own pulling that together, and what does the next two weeks look like on your calendars?"

---

Script 3: Enterprise Discovery (multi-stakeholder, longer cycle, 45–60 min)

Open:

"Thank you all for the time — I know enterprise calendars are hard to align. My goal today isn't to sell you anything. It's to understand your current state well enough that if we move forward, we're solving the right problem, not a generic one. I'll ask a lot of questions. Feel free to disagree with each other in front of me — that's useful information, not an awkward moment."

Context:

"Before problems — give me the lay of the land. How is [function] organized today? Who owns what?"

Situation questions:

• "Walk me through your current stack/process for this end to end."
• "Where did this initiative originate — is it top-down from leadership, or bottom-up from the team?"
• "Has anyone tried to solve this before? What happened?"

Problem questions:

• "What's not working with the current approach — is it a capability gap, a cost problem, or an adoption problem?"
• "Is this problem contained to one team, or does it show up in other parts of the org too?"

Impact questions:

• "How does this map to a company-level metric or OKR this year?"
• "If this doesn't get solved, what happens at the exec level — does someone above you feel it?"
• "Is there a cost of doing nothing you can put a number on?"

Need-payoff questions:

• "If we solved this exactly as you'd want, what does that unlock strategically, not just operationally?"
• "Who becomes a hero internally if this goes well?"

Qualify (be direct — enterprise punishes vagueness):

"Let's map the buying process honestly. Who are all the people who need to say yes — including security, procurement, and legal? Is there budget allocated, or does this require a business case to create budget? What's driving the timeline — is there an event forcing a decision, or is this evaluate-when-ready?"

Close:

"Here's my understanding of where you are: [recap]. Given the number of stakeholders involved, I'd suggest we build a shared plan — who needs to see what, and by when — rather than me guessing at your process. Can we put 20 minutes on the calendar specifically to map that out with [economic buyer / champion]?"

---

Script 4: Inbound Demo-Request Discovery (they came to you, 20–30 min)

They already raised a hand — do not skip discovery just because they asked for a demo. An undiagnosed demo is a wasted demo.

Open:

"Thanks for booking time — I saw you requested a demo. Before I show you anything, I want 10 minutes to understand what prompted you to reach out, so that when I do show you the product, I'm only showing you the parts that matter to your situation. Fair?"

Situation/Problem questions:

• "What were you doing right before you decided to look for a solution like this?"
• "Is this the first tool you're evaluating, or have you already looked at others?"
• "What's the specific trigger — did something break, or is this proactive planning?"

Impact questions:

• "Who asked you to look into this — was it your idea, or did it come from above?"
• "What happens if you don't solve this in the next quarter?"

Qualify:

"So I tailor the demo right — how many people would actually use this day to day? And is there a rough budget range already in mind, or is this exploratory?"

Close (transition into the demo):

"Great — based on what you've told me, I'm going to focus the demo on [X, Y, Z] and skip the rest, since that's what's actually relevant to you. After the demo, let's leave 5 minutes to talk about what a next step would look like if it's a fit."

---

Script 5: Outbound Cold-to-Discovery Bridge (they took your cold call/email, first real conversation)

Open:

"Thanks for taking the call — I know I reached out cold, so I'll keep this focused. The reason I called specifically is [one-sentence, researched reason specific to their company/role — never generic]. Does that resonate at all, or am I off base?"

(If off base — ask what IS on their mind instead. Don't force your angle.)

Bridge into situation questions:

• "Since I've got you — how are you handling [problem area] today?"
• "Is this something that's on your radar as a priority, or did I just get lucky with timing?"

From here, drop into the Problem → Impact → Need-payoff flow from Script 1.

Close:

"I don't want to oversell a 15-minute cold call into something bigger than it is. Based on what you've said, it sounds like [worth / not worth] a proper conversation. If it's worth it — can we get 30 minutes on the calendar where I come prepared with [specific thing relevant to them]?"

---

Universal Question Bank (Reference)

Situation (understand current state):

• "How do you handle X today?"
• "Who's involved in that process?"
• "What tools/systems are in play?"

Problem (surface the pain):

• "What's the hardest part of that?"
• "What's changed recently that's made this harder?"
• "What have you already tried?"

Impact (make the pain costly):

• "What does that cost you — in time, money, risk, or reputation?"
• "Who else feels this besides you?"
• "What happens if this is still true in 6 months?"

Need-payoff (let them sell themselves):

• "If that were solved, what would that mean for you/the team?"
• "What would you do with the time/money that frees up?"

5 Rules for Every Discovery Call

1. Never pitch before minute 15. If you're describing your product before you've asked five questions, you're freelancing.
2. Never accept the first answer as the real answer. "Why does that matter?" is your most-used follow-up.
3. Never let one person on a multi-stakeholder call answer for everyone. Name-call the quiet ones in.
4. Never end a call without a calendared next step. "I'll follow up" is not a next step.
5. Never skip qualify questions because the conversation felt good. Rapport is not the same as a real deal.

End-of-Call Recap Script (use verbatim, every call)

"Before we go, let me play back what I heard, so you can correct me if I got anything wrong: [1-sentence situation] + [1-sentence problem] + [1-sentence impact]. Does that sound right? ... Great — so the next step is [X], and I'll send a calendar invite for [specific date/time] before we hang up."