2026-04-05

Discovery Call Script

the playbook · word-for-word scripts · frameworks · templates

Enterprise Sales Discovery SaaS MBA Interns Call Scripts

Discovery is where enterprise deals are won or lost. Not at the demo. Not at the pricing call. Not at the negotiation. Right here — in the 30-minute conversation where you either understand the prospect’s world deeply enough to help them, or you don’t.

Most salespeople treat discovery as a checkbox — a few surface-level questions before they jump into a product demo. That’s why most salespeople lose. The best enterprise reps spend 70% of the call listening, ask questions that make the prospect think, and leave the call with the prospect more convinced than before — not because of a pitch, but because they felt understood.

Who this is for: MBA interns doing enterprise SaaS sales for the first time. AEs who want to sharpen their discovery. Sales leaders building a repeatable discovery framework for their team.

Part I

Foundations

Before you pick up the phone, you need to understand why discovery matters more than any other part of the sales process, what to research before every call, and the structural framework that keeps you in control of the conversation.

01 Why Discovery Matters

Here is the uncomfortable truth about enterprise sales: 80% of deals are won or lost at discovery, not at the demo. The demo just reveals whether you did good discovery. If you understood their pain, their process, their priorities, and their politics, the demo writes itself. If you didn’t, no amount of feature dazzle will save you.

Three things separate great discovery from mediocre discovery:

The 70/30 Listening Ratio

On a 30-minute discovery call, you should be talking for roughly 9 minutes. The prospect should be talking for 21 minutes. That’s the 70/30 rule. Most reps invert this — they talk for 20+ minutes and wonder why the prospect says “looks interesting, send me some info” at the end.

Metric	Bad Discovery	Great Discovery
Talk ratio	Rep talks 60-70%	Prospect talks 70%+
Questions asked	3-5 surface questions	12-20 layered questions
Prospect reaction	“Sounds interesting, send info”	“That’s a great question. Let me think…“
Rep knowledge after	Knows what they do, vaguely	Can explain their problem to their boss better than they can
Next step	“I’ll follow up next week”	Calendar invite sent during the call

What Great Discovery Actually Sounds Like

BAD DISCOVERY

“So tell me about your company.”

“What tools do you use?”

“What’s your budget?”

“Want to see a demo?”

Total questions: 4. Total insight: zero. The prospect feels interrogated and bored.

GREAT DISCOVERY

“I saw you’re hiring 3 data engineers — is the analytics layer becoming a bottleneck?”

“When a report is wrong, what happens downstream? Who feels it first?”

“You mentioned it takes 2 weeks to onboard a new data source. What does that cost you in terms of decisions that get delayed?”

“If you solved this, what would your VP say at the next board meeting?”

Total questions: 4. Total insight: enormous. The prospect feels understood and starts selling themselves on the solution.

Why the good version works: Each question builds on the last. The first is research-based (shows preparation). The second goes to consequences (not just symptoms). The third quantifies the pain in business terms (cost, time). The fourth connects to stakeholders and politics. The prospect is doing the work of convincing themselves.

Insight: The best discovery calls end with the prospect saying: “I’ve never thought about it that way before.” That means you asked questions they haven’t been asked. That’s when you stop being a vendor and start being an advisor.

02 Pre-Call Research

You should spend 10-15 minutes researching before every discovery call. Not 2 minutes. Not 30 minutes. Ten to fifteen. Enough to be genuinely informed. Not so much that you’re burning hours you could spend on other prospects.

The Research Checklist

Source	What to Look For	Time
LinkedIn (person)	Role tenure, career path, recent posts, mutual connections, what they comment on. Did they just start? (New leaders buy.) Are they posting about a problem you solve?	3 min
LinkedIn (company)	Headcount growth, recent hires by department, open roles. Hiring = investing. What departments are growing fastest?	2 min
Company blog / newsroom	Product launches, partnerships, fundraising, leadership changes. Any recent trigger event.	2 min
Job postings	What roles are open? Job descriptions reveal priorities, tech stack, and pain points. “Must have experience with X” = they’re struggling with X.	2 min
G2 / Capterra / TrustRadius	Reviews of their product (if B2B SaaS). Reveals what their customers complain about. Also: reviews of tools they use — reveals their pain.	2 min
Tech stack (BuiltWith, Wappalyzer)	What tools are they running? This tells you their maturity, budget level, and potential integration points.	1 min
Funding / financials	Crunchbase for funding stage. Public companies: earnings calls, 10-K. Funding stage tells you budget reality and growth pressure.	1 min

The Pre-Call Notepad

Before every call, write down these five things on a sticky note or doc. Have it on screen during the call:

Pre-Call Research Notes · Fill this out before every call

1. Trigger / why now: ``

2. Hypothesis: ``

3. Relevant proof point: ``

4. 3 questions I must ask: ``

5. Desired next step: ``

Why write a hypothesis: A hypothesis gives you something to test during the call. Instead of asking random questions, you’re validating or invalidating a specific theory. “I think they’re struggling with data pipeline reliability because they just hired 3 data engineers and their G2 reviews mention ‘reporting delays.’” Now your questions have direction. You’re a doctor with a preliminary diagnosis, not a doctor asking “so, what hurts?”

The 10-minute rule: If you can’t find enough to fill out the pre-call notepad in 10 minutes, the prospect may not be qualified. Qualified enterprise prospects leave digital breadcrumbs — job postings, blog posts, funding announcements, LinkedIn activity. If there’s nothing to find, ask yourself: is this the right account?

03 The Call Structure — 6-Phase Framework

Every discovery call follows the same 6-phase structure. The phases are sequential but flexible — you’ll loop back and forth. The time allocations are guidelines, not rigid rules. But if you’re spending 15 minutes on the opening, something is wrong.

Phase	Name	Time	Purpose	Your Role
1	Opening	2 min	Set the agenda. Build rapport. Earn permission to ask questions.	Leading
2	Situation	5 min	Understand their current state. Tools, team, process.	Asking
3	Pain	10 min	Uncover problems, frustrations, gaps. Quantify in $/time/risk.	Probing
4	Impact	5 min	Connect pain to business outcomes. Make it strategic, not tactical.	Elevating
5	Process	5 min	Understand how they buy. Timeline, stakeholders, budget.	Mapping
6	Next Steps	3 min	Lock in a specific commitment. Calendar invite on the call.	Closing

The flow: Situation questions establish context. Pain questions reveal problems. Impact questions make problems urgent. Process questions reveal how to navigate the deal. This sequence is intentional — you can’t ask about pain without understanding the situation, and you can’t ask about impact without understanding the pain. Skipping phases is the #1 discovery mistake.

Part II

The Script

Word-for-word scripts for every phase of the discovery call. These are not meant to be read robotically — they’re starting points. Internalise the structure, then make it your own. But when you’re starting out, it’s better to sound a little scripted than to wing it and miss critical information.

04 Phase 1: Opening (2 Minutes)

The opening has three jobs: (1) build rapport, (2) set the agenda, (3) earn permission to ask questions. Do not skip the agenda-setting. It gives you control of the call and tells the prospect you’re a professional who respects their time.

The Standard Opening Script

Script · Phase 1: Opening · 2 minutes

The Agenda-Setting Open

“Thanks for taking the time, ``. I appreciate it — I know your calendar is packed.

Before we jump in, let me share what I was thinking for the next 30 minutes, and you can tell me if it makes sense.

I’ve done some research on — I'd love to share a couple of things I noticed and get your reaction. Then I have a handful of questions to understand how your team handles today. And if it makes sense at the end, we can talk about whether there’s a fit and what a next step would look like.

Sound fair?”

Why this works: “Sound fair?” is a micro-commitment. When they say “yes,” they’ve agreed to let you lead the call. You’ve also set expectations — they know you’ll ask questions (so they won’t be surprised), and you’ve signaled there’s an out (“if it makes sense”). This reduces pressure and builds trust. The phrase “I’ve done some research” signals competence immediately.

Opening Variations by Persona

VP Engineering / CTO

“Thanks for the time, Priya. I know engineers hate sales calls — so I’ll be respectful of the 30 minutes.

I’ve been looking at your team’s setup — saw the GitHub org, the job postings for platform engineers, and your talk at ``. I have a hypothesis about a challenge you might be facing, and I’d love to test it with you. Then a few questions about your current stack. And if there’s something here, we can figure out a next step. Does that work?”

VP Sales / CRO

“James, thanks for jumping on. I know you’re in the middle of quarter-end — I’ll keep this tight.

I’ve been following ``’s growth — the AE hiring spree tells me you’re scaling fast. I’d love to understand how your team is running today, what’s working, and where the friction is. Then we can figure out if there’s anything we can help with. Cool?”

CFO / VP Finance

“Rachel, thanks for making the time. I know finance leaders don’t usually enjoy vendor calls, so I’ll be direct and efficient.

I looked at 's recent and had a few hypotheses about where financial operations might be under pressure. I’d love to ask a few questions, share what we’ve seen at similar-stage companies, and see if there’s a conversation worth having. Fair enough?”

CMO / VP Marketing

“Alex, thanks for hopping on. I’ve been digging into ``’s marketing — your content game is strong, and the SEO footprint has grown a lot in the last two quarters.

I’d love to understand what’s driving that, where the team is feeling stretched, and whether some of the patterns we’re seeing at other high-growth marketing teams are relevant for you. Work for you?”

The compliment rule: In every opening, reference something specific you genuinely respect about their work. Not fake flattery — a real observation. “Your content game is strong” only works if it’s true. Enterprise buyers have finely tuned BS detectors. One authentic compliment builds more rapport than five minutes of small talk about the weather.

05 Phase 2: Situation Questions (5 Minutes)

Situation questions establish the baseline. You’re mapping their current reality — what tools they use, how their team is structured, what their processes look like. These are the “what” questions. They’re necessary but not sufficient. Don’t spend too long here — situation questions are where mediocre reps get stuck.

The Transition

“Great. Let me start with a few context questions so I’m not making assumptions. Can you walk me through how your team currently handles ``?”

Why “walk me through”: This phrase is magic. It’s open-ended, non-threatening, and invites them to tell a story rather than give a one-word answer. “What tool do you use?” gets you “Salesforce.” “Walk me through how a deal moves from qualified to closed” gets you a 3-minute explanation with 10 insights embedded in it.

Situation Questions by Category

Current Tools & Stack

“Walk me through your current stack for ``. What are the core tools?”
“How long has that setup been in place?”
“Was that a deliberate choice, or did it kind of evolve over time?”
“If you could wave a magic wand and change one thing about the current setup, what would it be?”

Team Structure

“How is the team structured? How many people touch ``?”
“Has the team grown recently, or is it staying flat?”
“Who owns this area day-to-day? Is there one person, or is it shared?”

Process & Workflow

“Walk me through a typical `` from start to finish.”
“How much of that is manual vs automated?”
“What does the handoff look like between and?”

Recent Changes

“What’s changed in the last 6-12 months? New leadership, new tools, new strategy?”
“I noticed you recently ``. How has that changed priorities?”
“Is the current approach scaling with you, or is it starting to crack?”

Metrics & Measurement

“How do you measure success for `` today? What are the key metrics?”
“Where are you tracking vs where you want to be on those metrics?”
“Who sees those numbers? Just your team, or does leadership have visibility?”

The 5-minute rule: Spend no more than 5 minutes on situation questions. If you’re at minute 8 and still asking about their tech stack, you’re in trouble. The goal is to get enough context to ask smart pain questions — not to create a complete org chart. You can always fill in details later.

06 Phase 3: Pain Questions (10 Minutes)

This is the most important phase of the entire call. This is where deals are made. Pain questions go deeper than situation questions — they uncover what’s broken, what’s frustrating, what’s costing them money or time, and why they haven’t fixed it yet. Your job is to make the pain vivid and quantifiable.

The Transition

“That’s really helpful context. Let me dig into a couple of areas. You mentioned `` — can you tell me more about that?”

Why you reference what they said: Parroting back their own words shows you’re listening. It also gives you permission to go deeper. They opened the door — you’re just walking through it. Never introduce a pain topic from nowhere. Always anchor it to something they mentioned.

The Pain Question Framework

Great pain questions follow a four-layer model: Surface → Consequence → Quantification → Emotion. Each layer goes deeper.

Layer	What You’re Asking	Example
Surface	What’s the problem?	“What happens when a data pipeline breaks?”
Consequence	What’s the downstream effect?	“When that breaks, what happens to the reports that depend on it?”
Quantification	How big is the problem in numbers?	“How often does that happen? What does it cost in engineering hours per month?”
Emotion	How does it feel? Who feels it?	“How does the team react when that happens? Is it a fire drill every time?”

20+ Pain Questions, Word for Word

Uncovering the Problem

“What’s the biggest challenge your team faces with `` right now?”
“What breaks most often?”
“Where do things slow down or get stuck?”
“If you had to pick the one thing that frustrates your team the most about the current setup, what would it be?”
“Is there anything that works fine today but you know won’t scale?”

Going to Consequences

“When `` happens, what’s the downstream effect?”
“Who else feels it when that breaks? Just your team, or does it ripple out?”
“What happens to the business when `` is delayed by a day? A week?”
“You mentioned `` — how does that affect your team’s ability to hit their goals?”
“What do people do as a workaround when the system breaks? Manual spreadsheets? Slack messages? Heroic all-nighters?”

Quantifying the Pain

“How often does this happen? Once a month? Once a week?”
“When it happens, how long does it take to fix?”
“If you add up the engineering hours spent on ``, what’s the monthly cost?”
“Have you ever tried to put a dollar number on this? What would you estimate?”
“How many people are pulled in when `` happens? What’s their hourly cost?”

Why you must quantify: “Our pipelines break sometimes” is a vague problem. “$45K/month in wasted engineering time because two senior engineers spend 15 hours each fixing broken pipelines every week” is a business case. The prospect won’t remember your features. They will remember the number they said out loud on your call. That number becomes the anchor for the entire deal.

Getting to Emotion and Urgency

“How long has this been a problem?”
“What have you tried so far to fix it?”
“Why didn’t that work?”
“What happens if you don’t solve this in the next 6 months? What gets worse?”
“Is this something your leadership team talks about, or is it more of a team-level frustration?”
“On a scale of 1-10, how urgent is this compared to everything else on your plate?”
“If this doesn’t get solved, what’s the risk to the business? To your team? To you personally?”

The “what have you tried” question (#17): This is one of the most powerful questions in all of sales. It tells you: (a) how serious they are about solving it, (b) what they’ve already evaluated (competitive intel), (c) what didn’t work and why (so you can position differently), and (d) how much budget and effort they’ve already invested in this problem. If they haven’t tried anything, the problem may not be real. If they’ve tried 3 things and none worked, the problem is very real and very urgent.

Quantification Cheat Sheet

When the prospect can’t put a number on their pain, help them calculate it live on the call:

Script · Live Pain Quantification

“Let me try to do some rough math with you — just ballpark, we can refine later.

You said about spend roughly dealing with this. If we assume a fully loaded cost of for an engineer at your level, that's roughly per month.

Does that feel right, or am I off?”

Why you do the math with them: When the prospect arrives at the number themselves (even with your help), it’s their number. It carries 10x more weight in internal conversations than any number you put in a slide deck. “Our vendor says we’ll save $500K” is skeptical. “We calculated on the call that we’re burning $500K/year on this” is a business case.

07 Phase 4: Impact Questions (5 Minutes)

Pain questions uncover the problem. Impact questions connect the problem to business outcomes that matter to executives. This is where you move the conversation from “our team is frustrated” to “this is a strategic issue for the company.” Impact questions also help the prospect sell internally — they give them the language to pitch this to their boss.

The Transition

“So it sounds like is costing you roughly. Let me ask — if you solved this tomorrow, what would change?”

Impact Questions, Word for Word

Script · Phase 4: Impact · 5 minutes

“If you solved this, what would change for your team day-to-day?”
“What would you be able to do that you can’t do now?”
“How would your VP / CEO / board react if you told them you’d fixed this?”
“What would you do with the time or money saved?”
“Would solving this help hit a specific goal or OKR this quarter?”
“Is this the kind of thing that would show up in a board deck if you solved it?”
“If you freed up those ``, what would your team work on instead?”
“How does this connect to the bigger company priorities right now — growth, profitability, product velocity?”
“If you don’t solve this in the next 6-12 months, does the problem get bigger or stay the same?”
“Is there a revenue or customer impact tied to this, even indirectly?”

Why impact questions matter: Pain is necessary but not sufficient. Every company has 50 problems. They’ll only solve the 3-5 that connect to strategic priorities. Impact questions reveal whether this pain is a “nice to fix” or a “must fix.” They also arm your champion with the business case they need to get budget and buy-in from leadership. You’re not just selling to this person — you’re teaching them how to sell internally.

The “board deck” test: If the prospect can’t imagine this problem or its solution showing up in a board deck or leadership review, the deal will stall. Enterprise deals need executive sponsorship. If the pain doesn’t rise to that level, you either need to find bigger pain or find a more senior stakeholder.

08 Phase 5: Process & Timeline (5 Minutes)

This is where you stop being a doctor and start being a navigator. Process questions help you understand how they buy — who’s involved, what the timeline looks like, what the budget situation is, and who has the power to say yes or no. Skip this phase, and you’ll spend months chasing a deal that was never going to close.

The Transition

“This is really helpful. Before we talk about next steps, I want to make sure I understand how your team would approach something like this. Can I ask a few questions about that?”

Process Questions, Word for Word

Script · Phase 5: Process · 5 minutes

Decision Process

“Walk me through how your team would typically make a decision like this. What does that process look like?”
“Who else would need to weigh in before you could move forward?”
“Is there a procurement or security review process?”
“Have you bought a tool in this category before? How did that go?”

Timeline

“What’s your ideal timeline for solving this? Is there a date you’re working toward?”
“Is there anything that could accelerate or delay this — budget cycles, leadership changes, competing projects?”
“If we showed you something compelling, how quickly could you realistically move?”

Budget

“Do you have budget allocated for this, or would this need to be a new line item?”
“Who controls the budget for a decision like this?”
“What’s the range you’d expect to invest in solving this?”

Competition

“Have you looked at other solutions for this? What did you think?”
“Is there an internal solution on the table — like building it yourselves?”
“What would make you choose us vs another option? What matters most?”

Why you ask about competition (#11): Most reps avoid this question because they’re afraid of the answer. That’s backwards. If they’re evaluating competitors, you need to know. It tells you: (a) the deal is real (they’re actively looking), (b) what criteria matter to them, and (c) how to position yourself. Not knowing you’re in a competitive deal is infinitely worse than knowing and adjusting your strategy.

The “build vs buy” trap (#12): In enterprise, your biggest competitor is often not another vendor — it’s the internal engineering team saying “we can build this ourselves.” If you hear this, don’t panic. Ask: “How long would that take? What’s the opportunity cost of those engineers not working on your core product?” The math almost always favours buying, but you need them to see it themselves.

09 Phase 6: Next Steps (3 Minutes)

Never end a discovery call without a specific, calendar-confirmed next step. “I’ll send you some info” is not a next step. “Let me follow up next week” is not a next step. These are euphemisms for “this deal is dead.” A real next step has a date, a time, an agenda, and specific attendees.

The Closing Script

Script · Phase 6: Next Steps · 3 minutes

Closing Strong

“This has been really valuable, ``. Let me quickly summarise what I heard:

1

Based on what you’ve shared, I think there’s a strong fit. Here’s what I’d suggest as a next step:

Could we lock in `` for that? I’ll send a calendar invite right now while we’re on the phone.”

Next Step Options by Situation

Situation	Best Next Step	Script
Strong fit, single stakeholder	Tailored demo	“I’d love to show you exactly how this would work for your team. Can we do a 30-minute demo focused on ``?”
Strong fit, needs others involved	Group demo	“It sounds like `` would need to weigh in. Could we schedule a demo with them? I’ll tailor it to both of your perspectives.”
Technical buyer	Technical deep-dive	“Would it be useful to do a technical deep-dive with your team — architecture, integrations, security? I can bring our solutions engineer.”
Early-stage / exploring	Second discovery	“I want to make sure I really understand your setup before showing you anything. Could we do one more call, maybe with ``, to go deeper on the technical side?”
Needs internal alignment	Executive briefing	“Would it help if I put together a 1-page summary of what we discussed — the problem, the cost, and what a solution could look like? You could share that with `` and we can reconvene.”

What to do when they say “Let me think about it”: Don’t accept this. Politely push back. “Totally understand — these things take time. Just so I can be helpful: what specifically do you need to think through? Is it budget, timing, whether this is a priority, or something else?” This either gets you real information or reveals the deal is dead — both outcomes are better than “I’ll follow up in a week” purgatory.

Script · The “Let Me Think About It” Recovery

Prospect: “This is great. Let me think about it and get back to you.”

You: “Absolutely — I don’t want to rush anything. Just so I can be helpful on my end: what’s the main thing you’d need to think through? Is it whether this is the right priority right now, or more about fit and functionality?”

Prospect: “Probably priority. We have a lot going on this quarter.”

You: “Totally fair. How about this — I’ll send you a short summary of what we discussed. If it makes sense, let’s block 20 minutes two weeks from now to revisit. If something changes before then, we can move it up. And if the timing isn’t right, no hard feelings at all. Sound fair?”

Why you always get a date: A deal without a next meeting is not a deal. It’s a hope. The moment you hang up without a specific commitment, the prospect goes back to their 147 other priorities, and you drop to the bottom of the list. Getting a date — even 2-3 weeks out — keeps momentum alive and gives you a legitimate reason to stay in touch.

Part III

Advanced

The script gets you through a standard discovery call. But real calls are messy — prospects push back, go quiet, or try to end early. This section covers how to handle objections in real-time, read non-verbal signals, debrief effectively, and avoid the mistakes that kill deals.

10 Objection Handling During Discovery

Objections during discovery are different from objections during negotiation. During discovery, objections usually mean one of two things: (1) the prospect doesn’t trust you yet, or (2) you’re asking for something before you’ve earned the right. The response to both is the same: step back, not forward.

“We’re just exploring right now.”

Objection · Low commitment

Prospect: “We’re just exploring right now. We’re not ready to buy anything.”

You: “Totally makes sense — and honestly, I’m not trying to sell you anything today. I just want to understand your situation and share what we’ve seen at similar companies. If there’s a fit, great. If not, I’ll tell you — I’d rather be honest than waste both our time. Fair?”

Then go right back to your discovery questions. Their guard drops.

Why this works: You’ve eliminated the threat. “I’m not trying to sell you anything today” is disarming because it’s the opposite of what they expect. And “I’ll tell you if there’s no fit” positions you as a trusted advisor, not a pushy rep. This reframes the entire dynamic.

“We already have a solution for that.”

Objection · Existing solution

Prospect: “We already have a solution for that. We use [Competitor].”

You: “That makes sense — [Competitor] is solid. How’s it been working for you? Is it covering everything you need, or are there gaps?”

Never trash a competitor. Compliment them, then probe for cracks.

Follow-up probes after they open up:

“What’s working well with [Competitor]?”

“If you could change one thing about it, what would it be?”

“How does your team feel about it day-to-day?”

“Are you using all the features, or just a subset?”

“When did you implement it? Has your team or needs changed since then?”

“Can you just send me some info?”

Objection · Brush-off

Prospect: “This sounds interesting. Can you send me some info?”

You: “Happy to. So I send you something relevant and not a generic brochure — can I ask two quick questions first? That way I can tailor it to your situation.”

Then ask your two most important discovery questions. You’ve bought yourself 5 more minutes.

Why this works: “Send me some info” is usually code for “I want to get off this call.” You can’t fight it head-on. Instead, you agree (reducing resistance) and use it as a bridge to get the information you actually need. Two questions turn a brush-off into a mini-discovery.

“I don’t have budget for this.”

Objection · Budget

Prospect: “This isn’t in our budget right now.”

You: “Completely understand. Budget is always tight. Let me ask it differently — if budget weren’t a constraint, is this a problem you’d want to solve?”

If yes: “Then let’s figure out the cost of the problem first. If we can show that solving this saves or makes more than it costs, budget usually follows. Can I ask a few more questions to understand the impact?”

If no: “That’s fair. Sounds like this isn’t a top priority right now. Would it make sense to reconnect in `` when budgets reset?”

Budget objections are usually priority objections. Solve the priority problem first.

“I need to talk to my team / boss first.”

Objection · Not the decision-maker

Prospect: “I’d need to run this by my VP before doing anything.”

You: “Of course. What do you think they’d want to know? What questions would they ask?”

Then: “Would it be helpful if I joined that conversation? Sometimes it’s easier to answer questions directly rather than playing telephone. Or I could put together a one-pager that addresses their likely concerns — whatever’s more helpful.”

Your goal: either get in the room with the decision-maker, or arm your champion with the right materials.

The objection pattern: Every objection follows the same formula. (1) Acknowledge — validate their concern. (2) Reframe — shift the conversation. (3) Advance — move toward a next step. Never argue with an objection. Never dismiss it. Acknowledge, reframe, advance.

11 Reading the Room

You can’t see body language on a Zoom call (or can barely see it). But there are clear verbal and behavioral signals that tell you whether a discovery call is going well or badly. Learn to read these in real-time so you can adjust.

Signs the Call Is Going Well

Signal	What It Means	What to Do
They ask questions back	They’re engaged and curious. They’re evaluating you, which means they’re taking this seriously.	Answer concisely. Then ask another question. Keep the ball moving.
They share internal details	“Between you and me, the CEO is pushing hard on this.” Trust has been established.	Listen carefully. This is gold. Don’t react with excitement — stay calm and professional.
They mention other stakeholders	“I should loop in our Head of Data on this.” They’re already planning next steps internally.	Immediately suggest a joint call. “Would it be helpful to include them in our next conversation?”
They go over time	They chose to keep talking. That’s a strong buying signal.	Note it. But also be respectful: “I know we’re over time — want to keep going or schedule a follow-up?”
“That’s a great question”	You made them think. They haven’t been asked this before. You’re differentiating yourself.	Pause. Let them think. Don’t fill the silence.
They push back on your framing	Counterintuitively good. It means they’re engaged enough to correct you, which means they care about accuracy.	Thank them. Adjust. “That’s helpful — tell me more about how you see it.”

Signs the Call Is Going Badly

Signal	What It Means	What to Do
One-word answers	They’re disengaged or don’t trust you enough to open up.	Stop asking yes/no questions. Switch to “walk me through” and “tell me about” open-ended prompts.
Checking the time / multitasking	You’ve lost them. You’re not relevant enough.	Call it out gently: “I want to make sure this is useful for you. Is there a specific area you’d like to dig into?”
“Sounds interesting”	This is the kiss of death. It means they’re politely trying to end the conversation.	Challenge gently: “Interesting enough to spend more time on, or interesting in a ‘that’s nice’ way? I’d rather know now.”
“Just send me info”	They want off the call. You haven’t earned enough interest.	Use the “two quick questions” technique from Section 10.
No questions from their side	If they have zero questions, they’re not engaged. Interested people ask questions.	Prompt: “What questions do you have for me?” If still nothing, the deal is cold.
They cut the call short	Something urgent, or you’ve lost them. Either way, you’re not a priority.	Respect it. “Totally understand. Can we lock in 15 minutes later this week to pick up where we left off?”

Insight: When a call is going badly, most reps panic and start pitching. This is the worst possible response. Pitching when someone is disengaged is like talking louder to someone who doesn’t speak your language. Instead, stop and recalibrate. Ask: “I want to make sure I’m asking the right questions. What’s most top of mind for you right now?” Let them redirect. Their redirect tells you what they actually care about.

12 The Discovery Debrief

Within 10 minutes of hanging up, write down everything you learned. Not an hour later. Not tomorrow. Right now. Your memory degrades faster than you think, and the specific language the prospect used matters enormously for the rest of the deal.

The Internal Handoff Note Template

Template · Post-Discovery Debrief

Discovery Notes: —

PROSPECT
Company: Contact:
Call date: Call duration:

PAIN (in their words)
Primary pain: Secondary pain:
How long: What they've tried:
Quantified cost: ``

USE CASE
Primary use case: Current tools:
Team size: Integration needs:

STAKEHOLDERS
Champion: Decision-maker:
Technical evaluator: Blocker:

SUCCESS CRITERIA
What “success” looks like: Metrics they care about:
Timeline for value: ``

RISKS & RED FLAGS
``

COMPETITIVE LANDSCAPE
Evaluating: Build vs buy:
Key differentiator needed: ``

NEXT STEPS
Agreed next step: Date/time:
Attendees: Prep needed:

DEAL SCORE
Fit (1-5): Urgency (1-5):
Authority (1-5): Overall (1-5):

The exact-language rule: When filling in the “Pain” section, use the prospect’s exact words, not your paraphrase. If they said “it’s a dumpster fire every month-end,” write “dumpster fire every month-end.” Those exact words will appear in your follow-up email, your demo narrative, and your business case. When the prospect sees their own language reflected back, they feel heard — and that builds more trust than any feature comparison.

13 Common Mistakes

The top 10 discovery mistakes, ranked by how much damage they do to your deal. Every one of these is something I’ve seen MBA interns do in their first month of enterprise sales. All of them are fixable.

Rank	Mistake	Why It Kills Deals	The Fix
#1	Pitching too early	You launch into features before understanding their problem. The prospect doesn’t see relevance and checks out. The demo becomes a monologue, not a conversation.	No pitching until Phase 4 at the earliest. If you catch yourself describing features, stop and ask a question instead.
#2	Not quantifying pain	“They have a problem” is not a deal. “$480K/year in wasted engineering time” is a deal. Without numbers, the business case doesn’t exist and the deal stalls.	Always do the math live on the call. “Roughly how many hours per week? At what loaded cost?” Make them say the number.
#3	Single-threading	Talking to only one person at the account. If they leave, get busy, or deprioritise, the deal dies. Enterprise deals require 3-5 stakeholders.	Always ask: “Who else would need to be involved?” Get intros to the decision-maker, technical evaluator, and budget holder.
#4	Not asking about competition	You don’t know you’re in a bake-off. You position generically. The competitor who understands the evaluation criteria wins.	“Have you looked at anything else?” is a mandatory question. Ask it every time. No exceptions.
#5	Not confirming next steps	The call ends with “great chat, let’s stay in touch.” There is no next meeting. The deal evaporates within a week.	Send the calendar invite while you’re still on the phone. If they won’t commit to a next step, the deal isn’t real.
#6	Talking too much	The 70/30 rule is inverted. You’re at 70% talk time. The prospect learns nothing new (they already know your product). You learn nothing (because you’re not asking).	Record your calls. Measure talk time. If you’re above 40%, you’re talking too much. Every sentence should either be a question or a brief, targeted response.
#7	Asking surface-level questions only	“What tools do you use?” gives you a list. It doesn’t give you pain, urgency, or business impact. You leave the call knowing their tech stack but nothing else.	Use the 4-layer model: Surface → Consequence → Quantification → Emotion. Every question should go deeper than the last.
#8	Not doing pre-call research	You open with “So tell me about your company.” The prospect’s trust drops to zero. They feel like a number on a list, not a priority.	10-15 minutes of research. Fill out the pre-call notepad. Reference something specific in your opening.
#9	Skipping the agenda	No agenda = no structure = the prospect rambles or you ramble = 30 minutes evaporate with nothing accomplished.	Always set the agenda in the first 90 seconds. “Here’s what I was thinking for the next 30 minutes. Sound fair?”
#10	Treating discovery as a checkbox	You ask 5 surface questions, declare discovery “done,” and rush to demo. The demo doesn’t land because it’s generic. The prospect says “looks interesting” and ghosts.	Discovery isn’t done until you can explain their problem better than they can. If you can’t, you need another call.

Insight: Here is the simplest diagnostic for whether your discovery was good: after the call, can you write a compelling 2-paragraph email to the prospect summarising their problem, the business impact, and why it’s urgent to solve now — without mentioning your product? If you can’t, you didn’t go deep enough.

Part IV

Templates

Complete 30-minute discovery scripts for four different buyer personas, and a one-page cheat sheet you can keep on screen during every call.

14 Discovery by Persona

Different personas care about different things. A VP of Engineering thinks in terms of velocity, reliability, and technical debt. A CFO thinks in terms of cost, efficiency, and margin. Your questions — and the language you use — must adapt. Below are complete 30-minute discovery scripts for four enterprise personas.

Persona A: VP Engineering / CTO

Full Script · 30 minutes · VP Engineering

Discovery: VP Engineering

OPENING (2 min)
“Thanks for the time, . I know engineering leaders hate vendor calls, so I'll be efficient. I've been looking at your team — saw the GitHub activity, the job postings for, and ``. I have a hypothesis about a scaling challenge you might be facing. Mind if I share it and then ask a few questions? And if there’s nothing here, I’ll tell you straight.”

SITUATION (5 min)
“Walk me through your current engineering setup. What’s the core stack?”
“How big is the team? How’s it structured — squads, platform team, SRE?”
“How long has the current architecture been in place?”
“What’s the deployment cadence? How often are you shipping?”
“What’s your CI/CD setup? How long do builds take?”

PAIN (10 min)
“Where are the biggest bottlenecks right now? What slows engineers down?”
“When the build breaks or CI backs up, what happens downstream?”
“How much time does the team spend on operational toil vs building product?”
“You mentioned — how often does that happen? What's the blast radius?" "If you put a number on the engineering hours lost to per month, what would it be?”
“What have you tried to fix this? Build something internal? Evaluate tools?”
“What’s your biggest concern about the next 12 months as the team scales?”

IMPACT (5 min)
“If you solved this, how would it change your team’s velocity?”
“What would your engineers build if they got those hours back?”
“Is this something your CTO / CEO / board is tracking?”
“How does this affect hiring? Is it harder to retain engineers when the tooling is painful?”

PROCESS (5 min)
“How would your team evaluate a tool like this? POC? Technical review?”
“Who else would need to weigh in — security, procurement, your CTO?”
“Is there budget for developer tooling, or would this need a business case?”
“Have you looked at any other solutions for this?”

NEXT STEPS (3 min)
“Based on what you’ve shared, I think there’s a strong fit. Would it make sense to do a technical deep-dive with your platform lead? I can bring our solutions engineer and we can get into architecture, integrations, and security.”

What to listen for with VPs of Engineering: Developer productivity metrics (cycle time, deploy frequency). Build/CI pain. Platform team capacity. Technical debt conversations. “We built it internally and it’s become a maintenance burden.” Anything about engineering retention — top engineers leave when tooling is bad.

Persona B: VP Sales / CRO

Full Script · 30 minutes · VP Sales / CRO

Discovery: VP Sales / CRO

OPENING (2 min)
“James, thanks for hopping on. I can see you’re scaling fast — AE postings, showing up more in the market. Before I take up your time, let me share what I was thinking: I’d love to understand how your sales machine runs today, where the friction is, and whether any of the patterns we see at high-growth SaaS teams are relevant. Sound good?”

SITUATION (5 min)
“Walk me through the sales org. How many reps? SDRs vs AEs? What segments?”
“What’s your sales cycle look like? Average deal size? Win rate?”
“What CRM and sales tools are you running?”
“How do you generate pipeline today? Inbound vs outbound split?”
“What’s the quota structure? Is the team hitting it consistently?”

PAIN (10 min)
“Where’s the biggest leak in the funnel right now?”
“What percentage of pipeline do you lose between demo and close? Why?”
“When a deal stalls, what’s usually the reason?”
“How much time do your reps spend on admin vs selling?”
“What does forecasting accuracy look like? How confident are you in the number?”
“How long does it take to ramp a new AE to full productivity?”
“If you added those `` new AEs tomorrow, would your current process scale?”
“What’s the cost of a missed quarter for your team?”

IMPACT (5 min)
“If you could improve win rate by even 5 points, what’s that worth in annual revenue?”
“What would your CEO say if you hit 90%+ quota attainment across the team?”
“How does sales performance affect the next funding round or board conversation?”

PROCESS (5 min)
“How do you typically evaluate new sales tools? Pilot with a team?”
“Who else would be involved — RevOps, your VP of RevOps, the CRO?”
“Is there budget allocated for sales productivity tools?”
“What else have you looked at?”

NEXT STEPS (3 min)
“I’d love to show you specifically how this would work for your team. Could we do a 30-minute demo with you and your Head of RevOps? I’ll tailor it to your exact funnel and show you the ROI model.”

What to listen for with VPs of Sales: Quota attainment percentages. Ramp time for new hires. Forecasting accuracy (if they say “it’s an art, not a science,” there’s pain). Pipeline coverage ratios. Win rate trends. Rep attrition. Anything about “we’re throwing bodies at the problem” (hiring to fix a process issue).

Persona C: CFO / VP Finance

Full Script · 30 minutes · CFO / VP Finance

Discovery: CFO / VP Finance

OPENING (2 min)
“Rachel, thanks for the time. I know finance leaders value efficiency, so I’ll be direct. I’ve been looking at 's growth trajectory — — and I had a couple of hypotheses about where financial operations might be under pressure. I’d love to test those with you and see if there’s a conversation worth having.”

SITUATION (5 min)
“What does the finance team look like today? How many people?”
“What’s your core finance stack — ERP, billing, expense management?”
“How does month-end close work? How many days does it take?”
“What does your reporting cadence look like for the board?”
“How are you handling revenue recognition today?”

PAIN (10 min)
“What’s the most painful part of month-end close?”
“Where are you still relying on spreadsheets for things that should be automated?”
“How confident is the team in the numbers when you report to the board?”
“What happens when there’s a discrepancy? How long does it take to track down?”
“As the company scales, what’s the first thing that breaks in your financial ops?”
“How much time does your team spend on reconciliation vs strategic analysis?”
“What keeps you up at night from a financial controls perspective?”
“If you had to put a dollar number on the inefficiency — people time, late insights, error correction — what would it be?”

IMPACT (5 min)
“If you could close the books in 3 days instead of ``, what would that enable?”
“How would faster, more accurate reporting change the board conversations?”
“Is financial ops efficiency something the CEO or board has flagged?”
“What would you do with the headcount you’d save if this were automated?”

PROCESS (5 min)
“How does your team evaluate new finance tools? Is there a procurement process?”
“Who else would need to be involved — your controller, IT, the CEO?”
“Is there budget for financial ops improvements, or would this come from a different bucket?”
“What’s your timeline? Are there any triggers — audit season, next funding round?”

NEXT STEPS (3 min)
“I’d love to show you what this looks like for a company at your stage. Could we do a 30-minute walkthrough with you and your controller? I’ll map it directly to your month-end process.”

What to listen for with CFOs: Month-end close duration. Spreadsheet dependency. Board reporting confidence. Audit readiness concerns. “We’re hiring another accountant” (throwing bodies at a process problem). Gross margin conversations. Revenue recognition complexity. Anything about “we need to be IPO-ready” or “the board wants more granularity.”

Persona D: CMO / VP Marketing

Full Script · 30 minutes · CMO / VP Marketing

Discovery: CMO / VP Marketing

OPENING (2 min)
“Alex, thanks for making the time. I’ve been digging into 's marketing —. I’d love to understand what’s driving that, where the team is feeling stretched, and whether some patterns we see at high-growth marketing teams are relevant for you.”

SITUATION (5 min)
“Walk me through the marketing team. How is it structured?”
“What’s your channel mix? Where does most of the pipeline come from?”
“What’s the marketing stack look like — MAP, CMS, analytics, attribution?”
“What’s the current CAC? How does that trend?”
“How do you measure marketing’s contribution to revenue?”

PAIN (10 min)
“Where’s the biggest bottleneck in your funnel right now?”
“What channel is underperforming vs where you want it?”
“How confident are you in your attribution? When the CEO asks ‘what’s working,’ how solid is the answer?”
“Where is the team spending the most time on manual or repetitive work?”
“What’s the handoff between marketing and sales look like? Any friction there?”
“How long does it take to launch a new campaign from idea to live?”
“If you could fix one thing about how marketing runs today, what would it be?”
“What’s the cost of the current inefficiency — in slower growth, wasted spend, or team burnout?”

IMPACT (5 min)
“If you fixed , what would that mean for pipeline this quarter?" "How would better change the conversation with the board?”
“What would you invest the saved budget or time into?”
“Is marketing pipeline generation a board-level metric?”

PROCESS (5 min)
“How does your team typically evaluate new marketing tools?”
“Who else would need to be involved — RevOps, IT, the CRO?”
“Is there budget for this, or would it need to be a new ask?”
“What else have you looked at in this space?”

NEXT STEPS (3 min)
“I’d love to show you what this would look like mapped to your funnel. Can we do a 30-minute demo with you and your Head of Demand Gen? I’ll tailor it to your top 2 channels.”

What to listen for with CMOs: CAC trends (especially if rising). Attribution confidence (low confidence = pain). Marketing-sales alignment friction. “We’re doing a lot but can’t prove what’s working.” Campaign launch speed. Content production bottlenecks. Channel saturation. Anything about “we need to be more efficient with the budget we have.”

15 The One-Page Discovery Cheat Sheet

Print this or keep it on a second screen. This is your in-call companion — everything you need on one page.

DISCOVERY CALL CHEAT SHEET

BEFORE THE CALL (10 min)
• Research: LinkedIn, job posts, blog, G2, tech stack, funding
• Write hypothesis: “I think they struggle with X because Y”
• Prepare: 1 proof point, 3 must-ask questions, desired next step

PHASE 1: OPENING (2 min)
“Thanks for the time. Here’s what I was thinking for the next 30 min…”
• Share research observation • Set agenda • Get permission: “Sound fair?”

PHASE 2: SITUATION (5 min)
“Walk me through how your team currently handles…”
• Current tools • Team structure • Process • Recent changes • Metrics

PHASE 3: PAIN (10 min) — THE KEY PHASE
Go 4 layers deep: Surface → Consequence → Quantification → Emotion
• “What breaks most often?”
• “What happens downstream when that fails?”
• “How many hours/dollars per month does this cost?”
• “What have you tried? Why didn’t it work?”
• “What happens if you don’t fix this in 6 months?”
• DO THE MATH LIVE: hours x people x cost = monthly waste

PHASE 4: IMPACT (5 min)
• “If you solved this, what would change?”
• “How would leadership react?”
• “What would you do with the time/money saved?”
• “Is this a board-level issue?”

PHASE 5: PROCESS (5 min)
• “How would your team make a decision like this?”
• “Who else needs to weigh in?”
• “Is there budget allocated?”
• “What else have you looked at?”
• “What’s your timeline?”

PHASE 6: NEXT STEPS (3 min)
• Summarise their pain in their words
• Propose specific next step (demo, deep-dive, group call)
• SEND CALENDAR INVITE ON THE CALL
• Never end with “I’ll follow up” — always end with a date

RULES
• Listen 70% / Talk 30%
• No pitching until Phase 4
• Use their words, not yours
• Quantify pain in $ or hours
• Write debrief within 10 min of hanging up

The goal is not to pitch. The goal is to understand their world so well that they trust you to help them.

The Discovery Manifesto

Listen more than you talk.       70/30 or you’re doing it wrong
Go four layers deep.           Surface → Consequence → Quantification → Emotion
Quantify everything.          Vague pain = dead deals
Never single-thread.          3+ stakeholders or the deal is fragile
Always get a next step.        Calendar invite on the call
Debrief within 10 min.        Your memory is worse than you think
Use their words.              Mirror language = trust

The best discovery calls end with the prospect saying:
“I’ve never thought about it that way before.”