What question do you ask to uncover the prospect's real budget without being pushy?

Two Ways to Frame the Budget Question

Every RevOps rep eventually chooses between two structurally different ways to open the budget conversation, and the choice matters more than the wording.

Option A: the process-and-range question. This is the question in the Direct Answer above — you ask how funding typically works inside their organization and let them self-select a range rather than a number. It works because it assumes financial planning already exists (true of any serious deal) and it gives the prospect an easy, low-risk way to answer: they describe a mechanism, not a personal disclosure. The upside is low defensiveness — nobody feels interrogated by a question about process. The downside is that it can produce a vague answer ("it depends on the quarter") if you ask it too early, before the prospect has any reason to think concretely about your deal.

Option B: the cost-of-inaction question. Instead of asking about money at all, you ask what it costs the prospect to keep doing nothing: "If this isn't resolved by next quarter, what does that delay actually cost your team — in lost deals, overtime, or missed targets?" This sidesteps budget entirely and instead builds the case for why budget should exist. The upside is that it surfaces urgency and rough financial stakes in the same breath, often producing a number the prospect volunteers unprompted (e.g., "we're bleeding about a rep's worth of productivity a month"). The downside is that it only works once the prospect has already admitted a real problem — asked too early, before pain is established, it reads as a hypothetical they'll wave away.

The two options aren't mutually exclusive; the strongest RevOps qualification sequences use both, in a specific order tied to how far along the conversation already is. Option A works as an opener because it's low-risk and process-oriented. Option B works as a follow-up once the prospect has named a specific pain point, because by then "cost of doing nothing" has a concrete anchor to attach to. Reps who default to only one option tend to either sound naive (asking about cost-of-inaction before any pain is established) or sound transactional (asking about process/range in every single call regardless of context).

A third variant worth naming, because it shows up constantly in enterprise deals: the authority question — "Who on your team would need to sign off if the ROI case were clear?" This isn't really a budget question at all; it's a budget-*access* question. It tells you whether the person you're talking to can move money or can only recommend that someone else move money. Many reps skip this and spend weeks building a business case for a champion who was never going to be able to approve spend, no matter how convinced they were.

How to Decide Which Approach Fits the Deal

The decision tree above is less about picking one question forever and more about sequencing within a single deal. If you're still in an exploratory first call and the prospect hasn't described a concrete problem yet, lead with Option A — it's safe, low-pressure, and gives you a structural read (project budget vs. platform budget) that shapes everything downstream. A "project budget" answer usually signals a faster, more self-contained decision; a "platform renewal" answer usually means you're competing against other line items and need executive sponsorship earlier.

Once the prospect has named a specific, quantifiable pain — a missed quota, a churn spike, a manual process eating hours every week — shift to Option B. At that point the cost-of-inaction question isn't hypothetical anymore; it's asking them to price out something they've already admitted hurts. This is also the moment to check whether you actually know who holds budget authority. If you don't, don't skip straight to a pricing conversation with someone who can only relay information upward — ask the authority question first, then route your cost-of-inaction question to whoever actually controls the funds, either directly or through your champion.

The single biggest sequencing mistake in RevOps qualification is asking Option B before any pain is established. Without an anchor, "what would it cost you to not act" gets a shrug, because the prospect hasn't yet convinced themselves there's a real cost. Sequence discipline — process question first, pain-anchored cost question second, authority question whenever you're unsure who's actually in the room — consistently outperforms leading with either question in isolation.

The Numbers Behind Each Approach

Concrete ranges make both questions land better, and reps should walk in with a sense of where their own deal typically falls before asking either version.

For Option A (process-and-range), a useful benchmark is deal size relative to approval layers. Many organizations set an internal threshold — commonly somewhere between $10,000 and $50,000 annually — under which a single department head can approve spend without finance sign-off. Above that line, expect at least one additional approval step, often a CFO or VP-level review, which typically adds 2-4 weeks to a sales cycle. If your deal size sits comfortably under a prospect's internal threshold, the process-and-range question usually gets a fast, specific answer. If your deal size is likely to sit above it, expect a vaguer initial answer ("we'd need to check") — that's not evasion, it's an accurate description of an approval chain you haven't mapped yet, and it's your cue to ask the authority question next.

For Option B (cost-of-inaction), the numbers that matter are the prospect's own operational costs, not yours. A rep who has already gathered a few data points earlier in the call — team size, average deal size, hours spent on a manual process per week — can prompt a more specific answer. For example, if a prospect has already mentioned a five-person team spending roughly six hours a week on a manual reporting process, the cost-of-inaction question ("what does it cost you to keep doing this manually through year-end?") has something concrete to multiply against, rather than asking the prospect to invent a number from nothing.

Timing numbers matter too. Budget conversations anchored to a specific calendar event — a quarterly business review, a fiscal-year renewal date, an annual planning cycle — close measurably faster than budget conversations left open-ended, because they give the prospect's internal approval process a deadline to organize around. A question like "if we aligned with your Q1 planning cycle, what range would be realistic?" does double duty: it surfaces a number and a deadline in the same breath, and deadlines are what actually move internal approvals, not urgency from your side of the table.

Sequencing the Question Inside the Sales Call

Timing inside the call — and across calls — determines whether either question feels collaborative or extractive. Never lead a first call with a budget question of any kind; lead with discovery questions about the prospect's current process and what's broken about it. The process-and-range question (Option A) belongs late in call one or early in call two, once you've established enough context that asking "how do you typically fund something like this" doesn't feel like a non-sequitur.

The authority question should be asked as soon as you notice ambiguity about who's in the room — don't wait for a "no" from procurement to find out your champion never had signing power. A simple, non-confrontational version: "Once we get to a proposal stage, who else typically needs to weigh in before something like this moves forward?" This is phrased as a process question, which keeps it in the same low-pressure register as Option A, but it functions as a budget-access question.

The cost-of-inaction question (Option B) works best once you've already summarized the prospect's stated pain back to them — "so if I'm hearing you right, this is costing your team roughly six hours a week in manual work" — and then ask what that costs them to keep absorbing. Don't ask it cold; ask it as a direct follow-up to something they already said, so it reads as clarification, not extraction.

Finally, if the number that surfaces is smaller than your standard deal size, don't walk away — propose a scoped or phased version that fits inside the stated range, and ask what the decision timeline would look like if you met those terms. This keeps the prospect engaged, tests whether "no budget" meant "no priority," and frequently expands once the phased version proves value. Throughout this entire sequence, the RevOps discipline is the same: never ask for a number in isolation. Always tie the question to a process, a pain point already named, or a calendar event — that's what keeps the conversation feeling like discovery instead of an audit.

Related questions

How do I ask about budget in a first meeting without seeming presumptuous?

Don't lead with it — ask two or three discovery questions about the prospect's current process first. Save the process-and-range question for late in the call, after the prospect has named a specific issue you can reference.

What if the prospect refuses to discuss budget at all?

Shift to an industry-benchmark framing: ask what range is typical for tools in this category rather than their specific number. Confirmation or correction of a benchmark still gives you usable data.

How do I qualify budget when multiple departments contribute?

Ask directly how cross-department funding gets allocated when several teams share a purchase. The answer reveals both who holds discretionary funds and how much internal friction to expect.

Should I ask the authority question before or after the budget question?

Ask it as soon as you're unsure who else needs to sign off — often before a specific number comes up, since knowing the approval chain shapes how you phrase everything that follows.

FAQ

What if the prospect says "I can't share that information"? Acknowledge it directly, then pivot to a market-reference version: "Totally fair — could you share the range you typically see for tools in this category instead?" That reframes the ask as general market data rather than their specific internal figure, and most prospects will answer a benchmark question even when they won't answer a direct one.

How early is too early to ask a budget question? Before the prospect has described a specific, named problem. A budget question asked before any pain is established has nothing to anchor to and typically produces a vague or deflecting answer, wasting the moment.

What's the difference between asking about budget and asking about authority? A budget question is about the size and structure of available funds. An authority question is about who can actually approve spending that money. Conflating the two means you can spend weeks building a case for someone who was never able to say yes.

How do I handle a budget figure that seems inflated? Ask what it's meant to cover — implementation, training, ongoing support, or software alone. Inflated numbers usually fall apart, or get corrected downward, once you ask for the breakdown.

What if the number that comes back is too small for our solution? Propose a scoped or phased version that fits the stated range, then ask what the decision timeline would look like if those terms were met. This tests whether the constraint is real or just an opening position.

Is it ever appropriate to ask for an exact dollar figure? Rarely, and only late in a cycle once trust is established and the prospect has already discussed a range. Even then, framing it as confirming a number ("so we're planning around roughly X") lands better than asking for one cold.

Sources

• Gartner: The B2B Buying Journey
• Forrester: B2B Sales & Buying Insights
• Gong Labs: Sales Research
• Winning by Design: Sales Methodology & Frameworks
• MEDDICC: The MEDDPICC Sales Qualification Methodology
• HubSpot Sales Blog: B2B Buyer Behavior
• G2: B2B Software Buyer Behavior Report
• TrustRadius: B2B Buying Disconnect Report

Related on PULSE

• [How do you validate that the person you are talking to actually has decision-making authority?](/knowledge/cg0953)
• [What is the first question you ask when a prospect says they have no timeline?](/knowledge/cg0952)
• [How do you handle a situation where the prospect is happy with their current vendor?](/knowledge/cg0951)
• [What is your strategy for re-engaging a lost deal that went dark 60 days ago?](/knowledge/cg0950)
• [How do you ask for a referral without making the client feel pressured?](/knowledge/cg0949)