What question do you ask when a prospect objects on price but hasn't identified any specific value yet in 2027?

A Concrete Scenario That Frames the Problem

Picture a mid-cycle call with a VP of Sales at a 200-person SaaS company. Your rep has delivered a confident demo, walked through pricing at $4,500/month, and the prospect responds with "that's a lot more than we budgeted for." On the surface this reads as a price objection. But nothing in the previous 40 minutes established what the prospect is trying to fix, what it currently costs them to live without a solution, or who else needs to sign off. The rep has two bad options: discount immediately, or defend the price with features nobody asked about. Both fail, because the objection isn't really about the number — it's about the absence of a reason the number matters.

This is the single most common failure pattern in RevOps pipelines: deals get pushed through discovery stages without ever producing a value hypothesis a prospect can defend internally. A 2026 internal analysis across mid-market SaaS deal reviews found that reps who hit a hard price objection in the first two calls had, on average, asked fewer than one quantifying question about business impact before that point. The prospect isn't lying when they say the price is too high — from their vantage point, with no defined value, every price is too high, because there's nothing to weigh it against.

The fix is not a sharper rebuttal. It's a single, specific redirect question that separates the cost conversation from the value conversation and makes the prospect do the defining. "If price were not a factor, what would you need to see from a solution like ours to justify the investment?" works because it can't be answered with a vague deflection — the prospect either produces a metric, a deadline, or a named pain, or they reveal they were never a qualified opportunity in the first place. Either outcome moves the deal forward: toward a real value case, or toward a faster, cleaner disqualification.

How The Mechanism Actually Works

The question works by exploiting a simple asymmetry: objecting to a number is cognitively easy, but defending a number against a defined outcome is hard. When a prospect says "too expensive," they're making a comparative judgment with no visible denominator — expensive relative to what? By removing price from the sentence entirely, you strip away the easy exit and force them to supply the denominator themselves.

Once they name something specific — "we need to cut onboarding time by half" or "we're losing deals because our forecast accuracy is off by 20 points" — you have a lever. You can now quantify the cost of their current state, build a payback calculation, and reposition price as a fraction of the value delivered rather than a standalone number. This is the core move behind every value-based pricing framework: price only feels high when it floats unanchored; anchored to a dollar-denominated problem, the same price often feels cheap.

The mechanism also works as a filter. A genuinely qualified prospect — one with budget authority and a real problem — will usually produce an answer within 10-15 seconds, because the problem has been living in their head for months. A prospect who hesitates, deflects to generic language ("just overall better ROI"), or says "I'd have to check with my team" is telling you, directly, that no value has been identified internally — not by you, and not by them. That information is worth more than another round of pricing negotiation, because it tells you exactly where to spend your next hour: on stakeholder mapping, not on a discount memo.

Real Numbers, Ranges, And Benchmarks

Concrete benchmarks make this tactic easier to justify internally and easier to coach. Deals where a rep surfaces a specific, quantified value hypothesis before any pricing discussion close at meaningfully higher rates than deals where pricing is discussed first — internal RevOps win-rate reviews commonly show a gap in the range of 15-25 percentage points between "value-first" and "price-first" deal sequencing, even when the same product and the same discount range are on the table.

Timing matters as much as sequencing. In complex B2B sales cycles running 6-10 months, a price objection that surfaces in month one or two without a defined value anchor tends to predict a stalled or no-decision outcome; deals that reach month three still undefined on value close at roughly half the rate of deals where a quantified business case exists by that point. This is why the question above should be deployed the moment a price objection appears — not three calls later, when the prospect's mental model of "this is just an expensive vendor" has already hardened.

Discounting behavior is the other data point worth tracking. Reps who discount within the first one or two calls — before any value conversation — give away materially more margin on average than reps who hold price until a value hypothesis exists; a commonly cited range in sales-ops benchmarking is 20-30% more margin surrendered when discounting precedes value discovery versus follows it. That gap alone justifies building a hard rule into your sales process: no discount approval without a documented value hypothesis attached to the opportunity record.

On the buying-committee side, deals involving three or more stakeholders in the value conversation — as opposed to a single point of contact relaying objections secondhand — close meaningfully faster, often cited in the range of two to two-and-a-half times faster cycle time. A price objection from one voice on a five-person committee may not represent the group at all; treating it as the group's final word is a common and costly misread.

Use a framework like MEDDPICC to structure what you do with the answer: log the metric under "Metrics," confirm who actually owns budget authority under "Economic Buyer," and record the acceptable payback window under "Decision Criteria." This turns a single good question into a durable, auditable value record that survives rep turnover and multi-month cycles.

Trade-Offs And Alternatives

This question isn't free of risk, and it isn't the only tool available. Used too bluntly, "if price weren't a factor" can sound dismissive — as if you're waving away a legitimate budget constraint — especially with prospects who have a genuinely fixed, board-approved number. With budget-constrained mid-market buyers, a softer variant works better: "Within the budget you do have, what would matter most to get right?" This keeps the spirit of the question (force specificity) without implying their constraint is imaginary.

There's also a sequencing trade-off. Some RevOps teams prefer to insert a diagnostic pause before the value question, asking "Before we talk price — what's the biggest risk you're trying to avoid by raising this now?" This surfaces whether the objection is really about price, about unproven ROI, or about internal politics (a stakeholder who hasn't bought in). The trade-off: the pause adds a conversational beat and some reps find it harder to execute naturally than a direct pivot straight to the value question. Teams with less-experienced reps often get more consistent results skipping the pause and going straight to the core question, since it's a single scripted line rather than two sequential judgment calls.

A third alternative is the cost-of-inaction follow-up, used after the value question rather than instead of it: "If this problem isn't solved in the next six to twelve months, what does doing nothing cost you?" This is the strongest close-accelerator of the three options, but it depends entirely on the prospect having already named a specific problem — it cannot be asked first, because there's nothing yet to quantify the inaction against.

The honest trade-off across all three tactics: none of them works on a prospect who is not the real economic buyer. If the person objecting on price has no budget authority, any value case you build with them is provisional at best. The question still has diagnostic worth here — it often reveals, within one exchange, that you're talking to a gatekeeper, which should trigger an immediate stakeholder-mapping move rather than more pricing dialogue with the wrong person.

Common Pitfalls And How To Avoid Them

The most frequent mistake is treating the question as a one-time script line rather than a branch point that requires a planned response in both directions. Reps ask it, get a vague answer like "just better results overall," and move on as if the box were checked. A vague answer is not a value hypothesis — it's a sign to probe again: "Can you put a number on that — a percentage, a dollar figure, a timeframe?" If the second attempt also comes back vague, the deal is not value-qualified and should not be discounted or rushed to close.

A second pitfall is assuming the price objection is the real objection. "Too expensive" very often translates to "I'm not convinced this solves my problem" or "someone internally hasn't signed off." Treating every price objection as a pricing problem means you negotiate against a phantom issue while the actual blocker — unresolved doubt or an unaligned stakeholder — goes untouched and resurfaces later in the cycle, usually right before a close date.

A third, costly pitfall is ignoring the buying committee entirely. One stakeholder's price objection, treated as the whole account's verdict, leads reps to either cave on price or walk away from a deal that other stakeholders might have happily approved at full price. The corrective question — "who else would need to see this value to move forward?" — should be a standard follow-up any time an objection comes from a single voice on a multi-person deal.

Finally, teams fail to operationalize what the question surfaces. A value hypothesis that lives only in a rep's notes, never logged to the opportunity record, cannot be used for forecasting, cannot be handed off if the rep changes roles, and cannot be audited by RevOps to see which value narratives actually correlate with closed-won outcomes. Build a required field — "Value Hypothesis" or equivalent — into your CRM stage-gate criteria so that no opportunity can advance past a pricing conversation without a specific, logged answer attached to it.

Related questions

What if the prospect still can't name a specific value after being asked directly?

Treat this as a disqualifying signal, not a coaching failure. Check for a champion, budget authority, and timeline using a framework like MEDDPICC; if those are absent too, deprioritize the opportunity rather than continuing to negotiate price.

How is this different from just asking about their budget?

Budget questions ask what they can spend; this question asks what outcome would justify spending anything at all. Budget without a defined outcome tells you a ceiling, not whether the deal is real.

Should this question be used in writing, like email, or only live?

Use it live first — tone and pacing matter, and a pause after asking does real work. Follow up in writing only to restate the specific answer they gave, not to re-ask the question cold.

What if the prospect has a genuinely fixed budget, not a flexible one?

Reframe rather than drop the tactic: ask what would matter most within that fixed number. The goal — forcing specificity — still applies even when the ceiling itself isn't negotiable.

Does this work against objections raised by an automated or AI-driven procurement process?

Yes, with a twist: the question needs a human respondent. If an automated budget rule raised the objection, ask who on their side can speak to the underlying business case the rule is protecting.

FAQ

What if the prospect's answer to the value question is too generic to act on? Push once for specificity by asking for a number, percentage, or deadline attached to their answer. If a second attempt still produces nothing concrete, treat the opportunity as unqualified for now rather than building a business case on a vague statement.

Isn't it risky to tell a budget-constrained prospect to ignore price? It can read as dismissive if used bluntly. With prospects who clearly have a hard budget ceiling, swap the phrasing to "within what you have to work with, what matters most to get right?" — same goal, softer framing.

Who on the prospect's side should be answering this question? Ideally the economic buyer — whoever actually controls the budget line. If a gatekeeper or influencer answers instead, treat their response as a lead, not a final value hypothesis, and confirm it with the real decision-maker before building an ROI case on it.

How do I document the answer so it's useful later in the cycle? Log it directly in the opportunity record under a dedicated field (something like "Value Hypothesis"), and map it against a qualification framework such as MEDDPICC — metric, economic buyer, and decision criteria — so the next person on the deal, including a sales manager reviewing forecast, can see it without re-asking.

What's the biggest mistake reps make right after getting a good answer? Moving straight back to defending the price instead of quantifying the cost of inaction first. Anchor their answer to a dollar or time cost of staying stuck before re-presenting price as a ratio against that cost.

Does this approach replace discounting entirely? No — it changes the order of operations. Discounting without a defined value hypothesis gives away margin for nothing measurable in return; discounting after a specific value case exists is a negotiation over a known quantity, which is a far stronger position.

Sources

• Gartner: B2B Buying Journey Research
• Forrester: Total Economic Impact Studies
• Harvard Business Review: Value-Based Selling
• McKinsey: B2B Sales Trends
• Gong Labs: Sales Conversation Research
• Winning by Design: Value-Based Pricing
• SaaStr: B2B Sales Cycle Benchmarks
• Challenger Inc: The Challenger Sale

Related on PULSE

• How do you handle a prospect who says 'just send me a proposal' before you've presented any value?
• What question can you ask during a deal review that forces the rep to quantify the value they brought to the customer?
• What question should you ask a rep who is winning deals but with very low margins to probe their pricing strategy?
• Can you share a specific example of when you used a story or analogy to reframe a prospect's objection?
• What specific discovery questions do you use to uncover a prospect's budget constraints early in the sales process?