What question can you ask during a deal review that forces the rep to quantify the value they brought to the customer in 2027?

The two options compared

There are really two distinct questions a deal-review leader can reach for, and they surface different failure modes, so it helps to hold them side by side before picking one.

Option A — the Financial Delta question: "What specific metric did the customer improve, and by how much, compared to their baseline before you were involved?" This is the sharper, more confrontational version. It puts the rep on the spot to produce one clean before/after number — a support-ticket count, a cycle time, a conversion rate, a cost line — and to say plainly how much of that change is attributable to what they brought to the account. It is fast to ask and fast to fail: a rep either has the number or they don't, and there's nowhere to hide behind a story about the relationship.

Option B — the Stakeholder ROI Map question: "Which of the different buyers on this account did you quantify value for, and what did each one specifically care about?" This is the broader, more diagnostic version. Instead of demanding one number, it asks the rep to prove they've done the value work across the whole buying group — the economic buyer, the technical evaluator, the day-to-day user — because a single quantified metric for one champion is not the same as an organization-wide business case. It surfaces political gaps (whom the rep hasn't talked to) as much as analytical gaps (what the rep hasn't measured).

In practice these aren't mutually exclusive — Option A is the atomic unit, Option B is the aggregate check that the atomic unit has been repeated enough times across the account. But a deal-review leader has to decide which one to lead with in the room, because leading with both at once turns the review into an interrogation instead of a coaching moment. The choice depends on where the deal actually is and what kind of quantify problem you suspect the rep has: a measurement problem (they have no number at all) calls for Option A first; a coverage problem (they have a number from one champion but nobody else) calls for Option B first.

A third, lighter-weight variant worth naming here because reps reach for it instinctively and it should be rejected outright: "How did you help the customer?" This is not a real option in a 2027 deal review — it invites a narrative answer with no number in it, and it should be treated as a non-answer that triggers a follow-up with either Option A or Option B, never accepted as a stopping point.

How to decide between them (mermaid)

Use the rep's opening answer to route the review, rather than deciding in advance which question to lead with. If the rep volunteers a number unprompted, you're checking its quality. If they don't, you're diagnosing which gap — measurement or coverage — is actually the problem.

The routing logic matters more than the labels: a rep who cannot answer Option A should never be allowed to skip straight to Option B, because a stakeholder map built on unverified numbers is just as thin as no map at all. Conversely, a rep who nails Option A for one champion but has never spoken to the economic buyer should be pushed into Option B immediately — the deal review's job at that point is to expose the coverage gap before procurement does.

Concrete numbers behind each option

Numbers make the difference between coaching and theater, so the deal-review leader should be listening for specific ranges, not just the presence of a number.

For Option A, a credible answer names three things together: a metric, a percentage or absolute swing, and a measurement window. Reasonable, defensible ranges to listen for:

• A 10-15% improvement on an operational metric (ticket volume, cycle time, error rate) is plausible and common for a well-adopted tool; treat anything under 10% as marginal and worth probing on whether the customer would even notice it.
• A 15-30% improvement is the range where the rep should be able to point to a specific before/after pair of numbers (e.g., "4.2 hours per case down to 2.9 hours"), not just a percentage in isolation.
• Anything claimed above 40% should trigger extra scrutiny — it's not impossible, but it usually means either the baseline was unusually broken, the measurement window is too short to be reliable, or the number is inflated. Ask what the baseline actually was in absolute terms before accepting the percentage.
• The measurement window matters as much as the percentage: a 20% lift measured over two weeks is weaker evidence than a 12% lift measured over two full quarters. Push for at least one full business cycle of data before treating a number as load-bearing.

For Option B, the useful concrete signal is not a single percentage but a count: how many distinct stakeholders does the rep have a quantified number for, and how many total stakeholders are actually on the account. A deal where the rep can quantify value for one out of five or six real buyers is a deal with a coverage ratio under 20% — treat that as a red flag regardless of how good that one number is. A deal where the rep has quantified numbers for at least half the buying group, even if each number is smaller and less dramatic than a single flashy metric, is structurally healthier and more likely to survive procurement, because no single stakeholder's doubt can sink the whole business case.

Dollar-figure framing helps too, especially with economic buyers: translate the operational percentage into a cost or revenue number wherever possible. A 15% reduction in case-handling time is abstract; "roughly $40,000-$60,000 a year in reclaimed labor cost at their current headcount and average loaded salary" is something a CFO can actually weigh against price. If the rep hasn't done that translation, that's a coaching gap worth naming directly in the review rather than letting it slide to the next stage.

Implementation details and sequencing (mermaid)

Neither question is a one-time ask — the answer should be re-verified and refreshed as the deal moves through stages, because the number a rep had at first discovery is rarely the number that survives to close. Build the sequencing into your normal deal-review cadence rather than treating it as a special exercise.

Sequence it like this in practice: at the first deal review after discovery, ask Option A and accept a rough, unverified number — the point at this stage is to confirm the rep is even oriented toward quantification, not to demand perfection. By the mid-cycle review, that same number needs a second, independent source (a call recording, a report the customer shared, a second stakeholder's confirmation) rather than resting on the rep's own paraphrase of what the champion said once. At the stakeholder-review checkpoint, switch to Option B and count how many buyers now have a number attached to their name; if the count hasn't grown since discovery, that's a sign the rep is coasting on one relationship instead of multi-threading the account. At the pre-close review, the operational number should have a dollar figure attached that the economic buyer has actually seen and not disputed — silence is not the same as agreement, so ask the rep directly whether the buyer pushed back on the math. After close, the loop closes itself: whatever number closed the deal becomes the number customer success is responsible for tracking, and a gap between the promised delta and the realized delta should feed back into how the rep calibrates the next account's claims, not get quietly dropped.

The sequencing also protects the deal-review process itself from becoming repetitive theater. Asking the identical question in the identical way at every single review trains reps to prepare a canned answer rather than to do fresh work. Rotating which piece of the sequence you probe — sometimes the source of the baseline, sometimes the stakeholder count, sometimes the dollar translation — keeps the accountability real instead of performative.

Related questions

How do you coach a rep to quantify the cost of the prospect's problem before they've even bought anything?

Ask the rep to price the status quo in the same units they'll later use to price the solution — hours lost, tickets unresolved, revenue leaked per month — so the later "value delivered" number has something concrete to compare against.

What do you do when the customer refuses to share exact numbers for the metric you're asking about?

Push for a range instead of a hard number — "15-20% fewer tickets" is still quantifiable. A rep who can't get even a range hasn't built enough trust with the account yet.

How do you tell the difference between a vanity metric and a metric that actually matters to the customer's business?

Ask what the metric changes downstream — does higher adoption reduce churn, cut onboarding hours, or lower support cost? If the rep can't trace it to a dollar or a headcount effect, it's probably vanity.

What's a reasonable way to verify a rep's claimed metric without demanding an audit?

Ask for the source in one sentence — a report screenshot, a call clip, a named stakeholder who confirmed it — and treat "I just remember them saying it" as an unverified claim, not a verified one.

FAQ

What question forces a rep to quantify the value they brought to a customer? "What specific metric did the customer improve, what was it before, what is it now, and how much of that change would you attribute to what you brought them?" A rep who can answer all four parts has a real value story; a rep who can only answer one or two does not.

Why is a before-and-after number better than a general description of the relationship?

A number is falsifiable and comparable across deals; a description of the relationship isn't. Asking the rep to quantify the outcome turns the deal review from a mood check into an evidence check, and it's the evidence — not the rapport — that survives procurement.

What if the rep says the customer hasn't measured anything formally? Then the coaching task is to help the rep set up a lightweight measurement with the customer going forward, and to be honest in the review that today's answer is a hypothesis, not a result. Don't let an unmeasured guess get recorded as a verified metric.

How many stakeholders' worth of quantified value should a healthy deal have by the time it nears close? There's no single magic count, but a deal where only one buyer has a quantified number attached to them is thinner than it looks. Aim for at least half of the actively engaged buying group having some specific, even modest, metric tied to their name.

Should this question be asked the same way every single deal review? No — rotate which part of the sequence you probe (the source of the baseline, the stakeholder coverage, the dollar translation) so reps do fresh analytical work each time instead of reciting a memorized answer.

What's the biggest mistake a deal-review leader makes with this question? Accepting a percentage with no baseline. "40% better" means nothing without knowing 40% of what, measured against what, and over what period — always ask for the actual before-and-after numbers, not just the ratio between them.

Sources

• Gartner — Sales
• Harvard Business Review — Sales
• McKinsey — Growth, Marketing & Sales
• Forrester
• Gong — Blog
• HubSpot Blog — Sales
• Salesforce — Resources
• Winning by Design

Related on PULSE

• How do you coach a rep to quantify the cost of the prospect's problem?
• How do you phrase a question that helps a rep recognize they are using too much jargon instead of customer language?
• Top 10 questions to help a rep build stronger customer relationships
• How do you coach reps to tell better customer stories?
• What question do you ask when a prospect objects on price but hasn't identified any specific value yet?
• How do you coach a rep to expand a deal's scope and value?