Blog

Why You're Asking: The Question Beneath the Question

Most discovery questions fail because prospects don't know why you're asking. One line changes that entirely.

Published 5 August 2026

You ask a question on a discovery call. The prospect gives you a one-word answer or a non-answer. You move on. Nothing sticks.

The problem isn't the question itself. It's that your prospect doesn't understand why you're asking it. Without that context, they treat it like a box to check, not a genuine conversation.

The Line That Changes Everything

There's one phrase that flips this: "I only ask because" or "The reason I ask is."

Here's how it works in practice:

You notice the prospect manages a distributed team across three time zones. You ask: "How are you currently handling communication across those different regions?"

If that's all you do, you get a surface answer. You've set off their BS detector—this feels like qualification, not conversation.

Instead, add the clarification:

"How are you currently handling communication across those different regions? I only ask because we've seen a lot of teams struggle with two specific things: making sure documentation actually gets read by remote folks, and preventing the synchronous standup from becoming a bottleneck. Have you run into either of those?"

Now the prospect knows you're not fishing randomly. You've shown them you understand the category of problem, and you're genuinely trying to figure out if it applies to them. They relax. They actually think about the question instead of deflecting.

Why This Works

When you ask without context, prospects assume you're running a qualification script. They've heard this from five other vendors this month. They answer defensively or minimally.

When you add the "I only ask because" frame, you're doing three things at once:

First, you're showing relevant experience. You know what tends to happen in situations like theirs. You're not blindfolded.

Second, you're lowering the stakes. You're not trying to trick them into admitting a problem—you're explicitly naming what you've seen before and asking if it resonates. This is collaborative, not adversarial.

Third, you're teaching them something. You've just introduced them to two specific pain points they may not have fully articulated to themselves. Now they have language for what they're experiencing.

What This Looks Like Across Different Situations

Let's say you're calling on a VP of Ops at a mid-market manufacturing company. You've researched them—they just hired two new regional managers.

Cold call version: "How are you managing quality control across your new regions?"

Discovery call with context: "How are you managing quality control across your new regions? I only ask because a lot of ops teams we work with hit a specific wall right after they scale regionally—the playbooks that worked for one site suddenly create inconsistencies when you have to decentralize execution. Are you running into any of that?"

Or you're in a discovery call with a Head of Marketing who's spent the last year on brand refresh and demand gen setup.

Without context: "What does your content strategy look like?"

With context: "What does your content strategy look like right now? I'm asking because we've noticed a lot of marketing teams in your space spend the first year building demand generation, and then the second year they hit this weird gap—they've got the pipeline engine running, but the sales team says the leads aren't getting the follow-up they deserve before they get recycled. Have you seen any of that dynamic?"

In both cases, you're not asking to qualify. You're asking to explore. The prospect feels the difference.

The Second-Order Effect

Once you start doing this, something else happens: you stop asking bad questions.

If you have to justify why you're asking something, weak questions become obvious. "How's business?" doesn't have a justification. "How are your current systems performing?" is too broad to defend with a specific reason.

This forces you to ask questions that actually matter—questions where you can point to a real pattern you've seen or a specific gap you're trying to understand.

The prospect also knows you're being intentional. That changes the entire tone of the call. You're not hoping to stumble onto a problem. You're methodically exploring whether specific challenges apply to them.

How to Build This Into Your Process

The mechanics are simple, but the discipline is real:

Before your next discovery call, for every question you plan to ask, write down the "I only ask because" clause. If you can't write one that's genuine, cut the question.

This takes three minutes. It saves you from asking seven questions where four of them don't matter.

On the call itself, you don't need to read it verbatim. Just make sure the prospect understands why you're asking. Sometimes it's one sentence. Sometimes it's two. The point is clarity, not a script.

If a prospect seems stuck or defensive, the clarification often unfreezes them. You've given them permission to have a real conversation instead of playing an interview game.

Part of our guide to Discovery calls.