Prospects Lie on Discovery Calls

Over 80% of discovery calls have the same flaw. The rep finds the pain and moves on without asking what it’s actually costing. That’s from Gong’s analysis of 519,291 sales conversations.

But there’s a problem underneath the problem. Even when reps do ask the follow-up, they still get bad answers. Not because they phrased it wrong. Because the prospect isn’t telling the truth in the first place.

Prospects don’t lie on discovery calls because they’re dishonest. They lie because the format of the call makes honesty uncomfortable. You ask “what’s your biggest challenge right now?” and they say “scaling efficiently.” You ask “what does that mean in practice?” and they say “we’re looking at a few options.” You ask “what would make this a priority?” and they say “we’d need to see ROI first.”

Meanwhile, they’re sitting on a $400,000 operational problem they haven’t fully articulated to themselves, let alone to a salesperson they’ve known for eight minutes.

67% of B2B buyers consider discovery the most important step in the entire sales process. The gap between what that should imply and what most discovery calls actually produce is enormous. Here’s what I’ve learned across hundreds of outbound programs at Momentum Nexus: when the call is structured to make lying easy and honesty uncomfortable, prospects lie. Change the structure, and the truth comes out. Here’s the framework we use.

Why Prospects Default to False Answers on Discovery Calls

Only 32% of B2B buyers consider sales reps a valuable resource in 2025. That number has dropped consistently over the last several years, and the reason isn’t hard to trace. Decades of overpromising, underdelivering, and treating discovery as a pitch setup have trained buyers to protect themselves.

Three psychological mechanisms produce false answers on discovery calls.

Reactance. When buyers sense they’re being steered toward a conclusion, they pull back. Psychological reactance is the brain’s response to perceived pressure: when someone feels their options are being constrained, they resist, even when the suggestion might be in their interest. Discovery calls that move from “what’s your challenge?” straight toward “let me show you what we do about that” trigger this response. The prospect senses the structure, switches into defense mode, and their answers get vague. Their real situation stays hidden.

The embarrassment shortcut. When a prospect doesn’t see why the conversation matters, they prefer a small lie over the vulnerability of admitting “I don’t think this applies to us” or “I’m not sure how this would help.” Saying “we’re just evaluating options” or “budget is tight right now” is cleaner. It ends the call without confrontation. This isn’t dishonesty. It’s self-protection in the absence of trust.

Status protection. Admitting a real, expensive, embarrassing problem to a salesperson is uncomfortable. Executives especially find it hard to say “our pipeline is broken and we have no idea why” to someone they met twelve minutes ago. Instead, they describe the version of their situation they’re comfortable sharing: controlled, considered, already being managed. The actual problem stays several layers below the surface.

None of these are fixable with better closing technique or more aggressive follow-through. You fix them by redesigning the call so that honesty feels safe and deflection doesn’t come up as an option.

The 5 Lies Prospects Tell on Discovery Calls (and What They Actually Mean)

After reviewing hundreds of early-stage outbound programs with clients, I’ve cataloged the five lies that show up consistently on discovery calls. Each one has a real translation underneath.

The Lie	What It Actually Means
”We’re not ready to buy.”	You triggered defenses before the prospect understood why this conversation mattered.
”We don’t have budget for this.”	The pain isn’t expensive enough yet to justify reprioritizing.
”We’re just evaluating options.”	We’re interested but not ready for a conversation that feels like a sales process.
”We’re managing it internally.”	We have a manual, inconsistent, or under-resourced internal solution and we’re nervous about change.
”This isn’t the right time.”	I don’t have a reason to make this the right time.

Lie 1: “We’re not ready to buy.”

This almost never means “we’ve thought carefully about timing and decided against moving forward.” It means the prospect heard something that felt like a sales pitch before they felt a reason to engage. The trigger is usually a rep who moved toward “let me tell you about our platform” before establishing shared understanding of the prospect’s current situation.

The fix is not to push back on the objection. Going back to situation mapping before the objection came up, and asking a question the prospect hasn’t been asked before, is what opens things back up.

Lie 2: “We don’t have budget for this.”

Budget doesn’t exist in a vacuum. Every company funds its highest-priority problems, with or without a formal budget line. When a prospect says “no budget,” they’re telling you one of two things: either the problem you’re addressing doesn’t feel expensive enough to prioritize, or you haven’t helped them quantify the cost in terms they can take to a CFO.

Gong data shows over 80% of discovery calls skip the quantification question entirely. The rep finds the pain, confirms it exists, and assumes the prospect understands the financial impact. They rarely do. Your job is to help them do that math, specifically and in their own terms, before the conversation ever touches pricing.

Lie 3: “We’re just evaluating options.”

This one is real and false at the same time. The prospect is genuinely in an early information-gathering stage. But “we’re evaluating” is also a shield: it keeps the rep from asking anything that feels like a commitment. The response is not to respect the shield and keep the conversation surface-level. It’s to ask the one question that turns evaluation into real discovery: “What would need to be true for you to stop evaluating and start moving?” That question surfaces the critical event. Critical events are the most useful piece of information you can extract from a discovery call, and they almost never emerge without being directly asked for.

Lie 4: “We’re managing it internally.”

This is the most information-rich lie on the list. A prospect who says “we’re handling it in-house” is almost always describing a manual, inconsistent, or under-resourced internal solution. Your job isn’t to argue that your solution is better. It’s to understand what their internal solution currently can’t do, at what cost, with what opportunity loss attached.

The question that dissolves this deflection fastest: “Walk me through what that looks like right now, step by step.” Specificity breaks the shield. Once a prospect starts describing the actual process, they usually talk themselves into the problem before you have to say a word.

Lie 5: “This isn’t the right time.”

Timing is always a reason and rarely a real constraint. Every experienced sales professional knows this. The question is how to surface the critical event that creates genuine urgency. David Sandler built his qualification methodology because he got tired of enthusiastic discovery calls that ended with “let’s revisit in Q3.” His solution was to address timing, budget, and authority explicitly in the first conversation. That felt uncomfortable. It also cut wasted pipeline significantly. The modern version of that discipline lives inside frameworks like SPICED, which treats the critical event as a first-class qualification criterion rather than something you hope emerges naturally.

Why Traditional Discovery Is Designed to Get Lied To

The standard format taught in most sales training programs goes: build rapport, ask about challenges, confirm pain, pitch solution, schedule next steps. It’s logical. It’s also a near-perfect mechanism for producing false answers.

Here’s the problem. Prospects have been on enough discovery calls to recognize the structure. They know “what are your challenges?” leads to “interesting, we help companies with exactly that.” So they give you a challenge that’s real but safe, not the one that’s actually expensive and uncomfortable. They calibrate their answers to the questions they expect to follow.

Gong’s analysis found that top performers ask 39% more questions per call than average reps, with the optimal range sitting at 11 to 14 targeted questions. Average reps ask 6 to 7. But question count isn’t the core variable. Question sequence is.

Neil Rackham’s SPIN selling framework, built on analysis of more than 35,000 sales calls across 23 countries over 12 years, found that implication questions, the ones that help prospects articulate the consequence of their problem rather than just its existence, are simultaneously the most powerful part of discovery and the most consistently skipped. Most reps jump from “you have this problem” straight to “here’s what we do about it.” That leap is where the truth gets left behind.

The 40/60 talk-to-listen ratio matters for the same reason. Reps who talk more than 57% of the call see lower close rates across every segment Gong studied. Deals won show a consistent lean toward the prospect talking more. That’s not about being a better listener as a personal virtue. It’s about creating enough space for the prospect to say something that surprises both of you.

As we covered in our post on how to write a sales sequence that doesn’t sound like a robot, the messages that lead to a discovery call set expectations for what kind of conversation is coming. If your outreach trained the prospect to expect a pitch, they’ll arrive in discovery in defensive mode before you open your mouth.

The Discovery Truth Stack: A 4-Layer Framework

This is the framework we run at Momentum Nexus when auditing outbound programs. It’s built on four sequential layers, each designed to create conditions where the next layer produces honest answers.

Layer	Time	Goal	Key Output
Situation Mapping	10-15 min	Understand current state with no evaluative framing	Factual description of how things actually work now
Problem Surfacing	10-15 min	Move from presenting problem to actual problem	The real issue behind the first answer
Impact Quantification	10-15 min	Attach a number to the cost of the problem	Dollar figure or missed opportunity the prospect can own
Critical Event Identification	5-10 min	Find what makes this real and time-bound	Specific external driver creating genuine urgency

The structure maps closely to SPICED (Situation, Pain, Impact, Critical Event, Decision), which Winning by Design developed specifically for B2B SaaS recurring revenue contexts. The key difference from SPIN is the explicit treatment of critical events as a first-class qualification criterion, not something you hope emerges organically near the end of the call.

Layer 1: Situation Mapping

The goal here is to understand current state without any evaluative framing. Not “what do you need?” but “walk me through what’s happening right now, step by step.”

This instruction produces more useful information than any open-ended question about challenges. It surfaces actual workflow, actual handoffs, actual friction, rather than the polished version a prospect presents when they’re in their own marketing mode.

Questions at this layer:

• “Walk me through exactly what happens from [trigger event] through to [outcome you care about].”
• “What’s consuming more of your team’s time than it should right now?”
• “Where do things slow down or get complicated?”

The discipline is to stay in describing mode, not solution mode. Any urge to say “we see that a lot, here’s how we handle it” is premature. You haven’t mapped the whole situation yet. Kill that impulse.

Layer 2: Problem Surfacing

Prospects arrive with a presenting problem. The presenting problem is what they’re comfortable articulating. The actual problem is what drives the buying decision.

The move from presenting problem to actual problem requires one technique: keep asking “and what does that lead to?” or “what happens because of that?” until you hit something with a real cost attached. Most reps stop at the first or second answer. That’s the presenting problem layer. The actual problem usually lives two or three levels deeper.

Questions at this layer:

• “When that happens, what does it create downstream?”
• “If that constraint stayed the same for another 12 months, where do things stand?”
• “What have you tried to address this? What happened?”

The last question is particularly useful. A prospect who tried something and it partially worked, or who tried something and abandoned it because of implementation complexity, has a completely different situation than one who hasn’t started. Our breakdown of the diagnostic vs. pitch approach covers this dynamic in depth, but the mechanism is identical in SaaS sales: the “what have you tried?” question surfaces sophisticated prospects and unrealistic ones at the same time.

Layer 3: Impact Quantification

This is where most discovery calls abandon the diagnostic early. Asking “what does this problem cost you?” feels presumptuous. It isn’t. It’s the question that makes your proposal land as an obvious investment rather than a line item to negotiate down.

Gong’s analysis is direct: over 80% of discovery calls reviewed had the same failure. The rep found the pain and moved on. They never asked what the pain was costing.

You can approach this directly or work your way in:

• “If this bottleneck wasn’t there, what would you expect to close over the next six months?”
• “What does running below capacity on [function] cost you per quarter, directionally?”
• “What’s the cost of letting this problem run for another year?”

The answer doesn’t need to be precise. A directional range, “probably $200,000 to $300,000 in recoverable margin,” is enough. That range is what makes your proposal land as a fraction of recovered value rather than a cost to justify.

This is also where prospects usually stop lying. Once they’ve quantified the problem themselves, they have a stake in solving it. The self-discovery effect from SPIN research is real: people are more committed to solutions they arrived at independently than ones presented to them.

Layer 4: Critical Event Identification

A critical event is a real, external, time-bound trigger that creates urgency. Not internal (“we’d like to improve this”) but external (“our board review is in 90 days and we need to show pipeline progress”). Not vague (“soon”) but specific (“we’re onboarding a new VP of Sales in Q3 and need the discovery process documented before they start”).

Deals without a critical event don’t close and don’t die. They drift into “follow up in 60 days” territory and stay there. The ICP qualification work in our post on fixing outbound pipeline leaks covers how to use trigger signals to qualify before the call even happens. The Layer 4 question is the in-call version: finding the trigger that makes this deal real.

Questions at this layer:

• “What would need to happen externally for this to become a priority this quarter?”
• “Is there a specific date or event this needs to be solved before?”
• “What happens to your situation if the current state continues through the end of the year?”

If there’s no critical event, that’s information too. A prospect with no urgency trigger is either not the right contact, not yet ready for a commercial conversation, or needs more problem surfacing before urgency becomes real. Artificially manufacturing urgency without a critical event produces stalled deals and resentful prospects.

Discovery Call Question Rewrites

The difference between a call that produces truth and one that produces deflection often comes down to one or two specific questions. Here’s what the comparison looks like on the most common failure points.

Traditional Question	What It Produces	Better Question	What Changes
”What are your biggest challenges?”	Safe, polished presenting problem	”Walk me through what a typical [process] looks like right now.”	Forces description, not evaluation. Hard to answer with a rehearsed line.
”What’s your goal for this year?”	Aspirational language with no cost attached	”If this problem ran for another year, what does that mean for the business?”	Attaches consequence to current state before any solution talk.
”Do you have budget for this?”	Yes/no deflection or false answer	”How do you typically prioritize investments in this area?”	Surfaces the budget process without triggering the budget shield.
”Who else is involved in this decision?”	Name-dropping without real context	”Walk me through how a decision like this has moved forward in the past.”	Reveals real process, not org chart.
”What’s your timeline?"	"Sometime this quarter” or “we’re not sure yet"	"Is there a specific date or event this needs to be resolved before?”	Forces the prospect to identify a real critical event or admit there isn’t one.

The common thread: effective discovery questions require description rather than evaluation. When you ask for a description, you force specificity. When you ask for evaluation (“what’s your biggest challenge?”), you invite the polished, safe version.

Auditing Your Last 10 Discovery Calls

The fastest way to measure where your discovery is breaking down is a retrospective audit. Pull the last 10 calls where you ran a discovery conversation and rank each against four questions:

1. Did you get a step-by-step description of the prospect’s current situation, or a summary?
2. Did you ask what the problem was costing, in dollars or in specific missed opportunity?
3. Did you leave the call knowing what specific external event would make this a priority?
4. Did the prospect say something that surprised you, something that contradicted their first answer?

If the answer to all four is no across most of those calls, your discovery is running at surface level. You’re getting the presenting problem, and that’s it. The real situation, the one that drives buying decisions, stays hidden.

Sales organizations with a formalized discovery methodology achieve 27% higher win rates and 21% higher quota attainment than those operating without one. For teams in the $50K to $150K Monthly Recurring Revenue range, where every deal is founder-coached and the pipeline is thin enough that one stalled deal matters, the gap between surface-level and structured discovery is the difference between a predictable close rate and one that feels random.

Our 90-day founder-led sales transition playbook covers how to codify discovery once you’ve figured out what good looks like, so the insight doesn’t live only in the founder’s head. But codification only works when there’s a real framework underneath it. Six questions that all produce deflection aren’t a process. They’re a ritual that produces consistent mediocrity.

Discovery Is a Design Problem

Prospects lie on discovery calls because discovery calls are designed to make lying the path of least resistance. The traditional format signals where the conversation is going, which tells prospects how to calibrate their answers. The questions invite evaluation rather than description. The structure rewards moving fast to solution rather than staying in diagnosis.

The fix isn’t a new objection-handling script or better closing lines. It’s rebuilding the call structure so that honesty is the easiest path: slower situation mapping, deeper problem surfacing, explicit impact quantification, and a direct search for the critical event that makes the deal real.

Most of the expensive problems that don’t show up in your pipeline are sitting in plain sight. They’re just never asked about directly enough to appear.

If you want to audit your current discovery process and map where qualified opportunities are getting lost, we run a free growth audit at Momentum Nexus that starts exactly here. Book a free growth audit and we’ll map your specific situation: www.momentumnexus.com.