The Budget Question: How to Ask 'What's Your Budget?' Without Sounding Like You're Fishing

14 October 2026·5 min read

Quick answer: "What's your budget?" asked flatly feels like you're trying to charge whatever someone's willing to pay. The honest answer gets easier when you reframe the question around scope and priorities instead of a bare number — ask what they're trying to achieve and let them volunteer the range, or offer your own range first so they're not guessing in the dark. Three different phrasings suit three different sales moments, and only one of them reliably gets an honest answer. 🚀

Nobody loves asking the budget question, and almost everyone's been burned by asking it badly. 💖 Ask it too bluntly and people clam up, assuming you're about to quote to the ceiling of whatever number they give you. Don't ask it at all, and you end up scoping a beautiful, detailed proposal for someone who was only ever going to spend a third of what it costs. There's a middle path, and it's mostly about *how* you ask, not *whether* you ask.

What most businesses get wrong

The blunt version — "so, what's your budget?" — puts the prospect on the back foot immediately, because it feels like the first move in a negotiation rather than a genuine planning question. People respond to that feeling by lowballing, dodging ("just send me your pricing") or going quiet altogether, none of which actually gets you the information you need.

The opposite mistake is avoiding the question entirely out of politeness, and instead spending hours scoping a custom quote blind. That's how service providers end up presenting a beautifully detailed proposal to someone who was never going to afford it — the time lost scoping a mismatched job is often more expensive than the awkwardness of just asking.

Three ways to ask, by sales context

1. The "scope first" version (best for custom quoting work):
"Before I put together options, it helps to know roughly what range you're working with — that way I can show you what's realistic instead of guessing and wasting your time. Even a rough ballpark is fine."

2. The "range offered first" version (best when trust needs building first):
"Projects like this usually land somewhere between $[X] and $[Y] depending on scope. Does that feel like the right ballpark for what you had in mind, or were you thinking bigger or smaller?"

3. The "priorities" version (best for early discovery calls):
"What matters most here — getting it done fast, getting the full-scope version, or keeping it as lean as possible? That'll tell me which direction to put options together in." (Their answer reveals budget indirectly, without ever saying the word.)

A business that quotes custom work: A kitchen renovation company used to ask "what's your budget?" on first calls and got vague answers like "whatever it costs to do it properly" nearly every time. Switching to the range-offered version — "Full renovations here typically run $25k to $60k depending on finishes, does that match what you had in mind?" — gave prospects a frame to react to instead of a blank space to fill, and real numbers started coming back in the very next sentence.

A service provider wasting time scoping unaffordable jobs: A web design freelancer kept building full proposals for every enquiry, only to find out at the end that half the leads had a budget a fraction of the quote. Adding the scope-first version early in the first email — "roughly what range are you working with, even a ballpark helps me not waste your time" — filtered out mismatched leads within the first reply instead of three weeks into a back-and-forth.

An early discovery call with a hesitant prospect: A marketing consultant found that asking about budget directly on a first call made prospects visibly tense up. Switching to the priorities version — "is speed, full scope, or staying lean the priority here?" — got the same information through the side door; someone who says "staying lean" has just told you their budget without either of you saying a number.

How to pick the right version

Match the phrasing to how much trust exists so far. On a cold first touch, lead with priorities — it's the softest entry and still tells you a lot. Once you're mid-conversation and genuinely about to scope something, the range-offered version works best because it removes the prospect's fear of naming a number that's "wrong." And when you're dealing with someone who's already engaged and just needs to commit to a number, the scope-first version is direct enough to get a real answer without feeling like an interrogation. In every version, the tell for honesty is giving the prospect an easy, low-stakes way to answer — a range to react to, a priority to pick, a ballpark instead of an exact figure.

💡 Always explain why you're asking. One sentence — "this just helps me show you realistic options instead of guessing" — turns the question from an interrogation into a courtesy, in every single one of the three versions above.

Mistakes to avoid

Asking the budget question before you've shown any value or understanding of their actual need.
Offering a range so wide it's meaningless ("somewhere between $500 and $50,000").
Treating a low answer as a reason to disengage rather than a reason to offer a smaller, honest scope.
Asking once and never circling back when the scope changes mid-project — budgets need revisiting, not just confirming once.

Frequently asked questions

Isn't it risky to name a price range first — won't that just anchor them low?

It's a fair worry, and the honest nuance is that it can anchor a prospect toward the lower end of your range — but the trade-off is usually worth it, because a prospect who at least engages with a real number is far more useful than one who stays vague forever. If anchoring low is a real concern, start the range slightly higher than your true minimum.

What if someone still won't give a number at all?

Fall back to the priorities version — it gets the same information without ever requiring them to say a dollar figure, which works for people who are genuinely uncomfortable discussing money directly.

Should I ever just skip the budget question and send a flat price list instead?

For simple, standardised services, yes, a price list removes the need for this conversation entirely. The budget question earns its place specifically for custom or variable-scope work, where the final number genuinely depends on what the client chooses.

Keep reading 🤍

Written by

Kate, founder of Chronically Online

I help Gold Coast and Brisbane businesses grow with branding, websites and marketing that actually works.

Work with me ✦