Why Your Discovery Questions are Missing Hidden Objections (& How to Fix Them)

Surface-level discovery questions get surface-level answers. And surface-level answers can kill deals you thought were already won.

I learned this the hard way on a $30k ARR deal that stalled for 4 weeks with no visible reason. Stakeholders were aligned, demos landed, champion was on board, and still nothing moved. 

The blocker turned out to be a bad experience with an agency the company had worked with years before. They weren’t like AiSDR in model or approach, but it was close enough to make leadership hesitate.

I never would have found it with the question I asked.

The question that let the real objection hide

During discovery, I asked: “Have you tried or entertained projects like AiSDR before?”

It’s technically accurate, but effectively useless. The question anchors the prospect to your product category. If their bad experience was with an agency, an internal project, or a different type of tool, the honest answer is still “no”. 

Even if the emotional residue is very much “yes.”

My product champion didn’t know about the agency history at the time. But leadership did, and it was why they were dragging their feet on a deal they’d already said yes to.

The discovery questions worth upgrading

Here are 3 common discovery questions that invite clean answers to messy situations, along with the versions that surface hidden context.

Question 1: Have you tried anything like this before?

The problem: “Like this” means your category. Prospects mentally narrow to direct comparisons and miss adjacent experiences that still shape how they feel about buying.

The upgrade: “Have you ever tried anything similar to what we do, such as tools, agencies, internal projects? How did it go?”

This casts a wider net. It catches the failed agency engagement, the internal pilot that went nowhere, or the tool a previous manager championed that nobody used. Such experiences create fear that doesn’t go away just because your product is different.

Question 2: Do you have a budget for this?

The problem: A yes/no question gets a yes/no answer. It doesn’t tell you whether the budget was fought for, whether it’s contingent on approval, or whether a previous spend in this area ended badly and made the CFO skeptical.

The upgrade: “How does your team typically evaluate and approve spend in this area? Has anything like this gone through before?”

The second sentence is the one that matters. It opens up the conversation around past budget decisions. Even the ones that left a bad taste.

Question 3: Is leadership aligned?

The problem: Your champion will almost always say yes. They want to believe it’s true, and they want to look capable in front of you.

The upgrade: “What would make leadership hesitate on this, even if they’re positive right now?”

This reframes the question around risk rather than current sentiment. Champions who’ve been burned by internal blockers before will give you real answers here. It also positions you as someone thinking about their success, not just closing the deal.

What to do when a deal stalls anyway

Even with better discovery, deals stall. When they do, a direct email often does more than another follow-up call.

The email above closed my $30k deal, and it’s got 4 components:

• Acknowledge the pattern – Name the slipped dates without blame. “I know we’ve talked about a start date a few times and it hasn’t happened.”
• Set a boundary – Be honest that you can’t keep the account active without a clear commitment. This isn’t pressure. It’s respect for both sides’ time.
• Flag any fit issues – Surface any genuine limitations like a missing integration or a mismatch in use case. This shows you’re thinking about their outcome and not just trying to close a deal.
• Leave the door open – Make it clear the relationship isn’t over. You just need a real signal to continue.

There’s no need to offer a discount or manufacture urgency out of thin air. The willingness to walk has to be genuine, or the prospect will feel it.

In my case, the email gave my champion something concrete to take to leadership: “We might actually lose this.” 

That’s the message they needed to hear internally, and I couldn’t deliver it myself. The champion did it for me.

Result

Hidden objections don’t surface because you ask the right question once. They surface because you ask questions that make it safe to tell the truth about past experiences, internal politics, and fears that leadership hasn’t voiced out loud.

Upgrading your discovery questions helps you capture adjacent context in addition to direct comparisons. Treat your champion as a partner who’s fighting battles you’ll never see. And when a deal goes quiet, a direct email built around honesty about fit will do more than another “just checking in.”

The close rate matters less than the quality of information you gather before you try to close.