How to Find Budget in Discovery, Without the Question That Kills It

The call is going well. You've uncovered a real problem, the prospect is engaged, and you've earned some trust. Then you ask: "So what's your budget for something like this?"

Pause.

"We're still early in the process." Or worse, they throw out a number so low it poisons the rest of the call. You're not recovering from that anchor. And you're not qualifying the deal either.

Why the Budget Question Backfires

Asking for budget directly triggers a negotiation reflex before you've established value. The buyer thinks: If I give them a number, that's where the price lands.

So they do one of three things:

• Lowball you to anchor the negotiation in their favor
• Stonewall you with "we're still in evaluation mode"
• Give a vague non-answer to keep moving

None of those help you qualify the deal. All three make the next conversation harder.

The question isn't wrong because it's rude. It's wrong because it arrives before the buyer has any reason to trust you with that number. You haven't yet made the case for why it matters, which means they're protecting themselves, not hiding from you.

What You Actually Need to Know

Here's the real thing: you don't need the exact budget figure. You need to know three things:

• Is there real money allocated, or is this exploratory?
• Is their ceiling above or below what you'll propose?
• Who has to approve the spend?

You can learn all three without ever asking "what's your budget." The approaches below do it without triggering the reflex.

Three Moves That Surface Budget Without Asking

Help the buyer quantify what they're already losing before you bring price into it.

When they put a number on the pain, even a rough estimate, you've built the business case before the price conversation starts. A prospect who tells you their current approach costs them $300K in wasted headcount will not blink at a $40K solution. You didn't ask what they could spend. You helped them do the math on what they can't afford to keep doing.

Before: "What's your budget for something like this?" → Buyer anchors low.

After: "If this stays broken, what's the actual cost to the business over the next year?" → Buyer calculates the gap your solution fills.

Instead of asking them to name a number, give them one to react to:

You're not asking them to commit, you're asking them to calibrate. "That's about right" and "that's way too high for us" are both extremely useful. Either way, you've qualified budget without putting the buyer in extraction mode.

If you need a ceiling and the reference approach doesn't land, try framing it as a planning question rather than a qualification:

This reads as service. Most buyers will answer it because it sounds like you're trying to help them, which you are. The ones who still won't engage on budget are typically not far enough along in the process to be qualified, which is itself useful information.

Don't Skip the Approval Question

One of the most underused budget moves in discovery is this:

The answer surfaces budget and authority in the same breath. "I can sign off myself up to $75K" tells you where you stand without a direct number conversation. "I'd need to take it to the CFO and the board" tells you you're in a longer cycle, and that you need to build a champion now, not when the proposal lands.

Budget and approval are inseparable. The approval question gets you both.

The Mindset Shift

Budget doesn't sit in a spreadsheet waiting for you to ask about it. It lives in the buyer's running calculation of what this problem is actually worth solving, and that's a number you can help them build.

Stop asking what they can spend. Start helping them understand what they're losing by not solving this. When the cost of inaction is clear, budget tends to appear.