Blog
Guide

How to Coach Quantified Impact on Discovery Calls

The number one behavior gap we see: reps confirm the problem but do not tie it to a dollar figure.

C
Coachvyne Team··6 min read
How to Coach Quantified Impact on Discovery Calls

Pull a set of your closed-lost calls from the last two quarters and look for one specific moment: the point where the rep could have asked "what does that cost you" or "how much time does your team spend on that" and didn't. In our annotation work, that missed moment appears in roughly two-thirds of closed-lost discovery calls. It rarely appears in closed-won calls at the same stage.

The gap between problem acknowledgment and quantified impact is one of the most consequential coaching opportunities in B2B SaaS sales — and one of the least specifically coached. Managers tell reps to "understand the business case" or "make sure you know the ROI story," but those instructions are too abstract to produce a behavior change on the next call. What actually changes behavior is drilling the precise moment and the precise question that extracts quantified impact from the buyer's own mouth.

Why the number needs to come from the prospect, not the rep

There's an important mechanics question here that most coaching glosses over: who generates the number? A rep who calculates "so based on what you've told me, that's probably a $200K annual impact" and the prospect says "yeah, roughly" has not achieved quantified impact as a coaching behavior. The prospect hasn't done the work of connecting their operational reality to a dollar figure. They've approved the rep's estimate.

The behavioral standard is that the prospect should either generate the number themselves or confirm a number they've already worked out internally. The psychological mechanism matters: a prospect who says "we figure we're losing about $300K a year to this problem" has done the analysis and owns the conclusion. A prospect who says "sure, your number sounds about right" has outsourced the analysis to the rep and will not carry the same level of conviction into an internal budget conversation.

This is the distinction that makes the difference at the proposal stage. Internal champions who can say "we put the cost at $300K — here's how we calculated it" are far more effective at making the budget case than champions who say "the vendor told us it was around $300K." Finance and procurement reviewers push back on vendor-generated ROI estimates. They're much more reluctant to push back on numbers the champion's own team developed.

The three categories of quantifiable impact

Reps and managers often think about quantified impact narrowly — revenue impact or direct cost savings. But in B2B SaaS discovery, there are at least three distinct categories of quantifiable impact, and each requires different probing language:

Direct cost impact

This is the easiest to quantify and the most familiar: costs associated with the current state that would be reduced or eliminated. "How much does your team spend on manual reconciliation each month, in hours and at what burdened cost per hour?" The bridge to dollars is direct. Where reps struggle is with the follow-up: "And is that a number your CFO or budget holder is already aware of?" If the answer is no, that's an implication that hasn't landed internally yet, and the champion will struggle to make the case without that calculation.

Revenue impact

Opportunity cost or direct revenue risk is harder to quantify but creates stronger urgency. For a ramp-time problem, the question isn't just "what does ramp time cost you in OTE" but "what does ramp time cost you in missed ARR from deals that didn't close because the rep wasn't ready?" That second number is typically 3–5x the OTE cost, and prospects are often surprised when they calculate it because they've been thinking about the cost in terms of salary, not in terms of pipeline. The coaching prompt: "If your ramp time were 2 months shorter, how many additional deals would each rep have closed last year? What's that worth at your average ACV?"

Time and capacity impact

For problems where the cost is primarily in manager or team time — coaching overhead, manual reporting, rework — quantifying in time and then converting to cost produces strong urgency. "How many hours per week does your head of enablement spend on building coaching materials that could be automated? At a $150K loaded cost, that's about $75 per hour — what would 10 hours a week worth be, annualized?" The conversion step is one the prospect often needs help with, but the underlying hours number should come from them.

The probing sequence that works

Here's a four-step sequence that consistently produces prospect-owned quantified impact:

  1. Surface the activity: "How much time does your team currently spend on [problem process] per week?"
  2. Confirm the scope: "Is that across the whole team, or is that per person?"
  3. Bridge to cost: "What's the rough loaded cost for that kind of work — are we talking $100K a year, $200K?" (Offer a range to make it easier for them to anchor.)
  4. Lock the number: "So you're looking at something in the [X] range — is that a figure your leadership is already tracking?"

The last question is diagnostic: if leadership is already tracking the cost, the champion has fuel for the internal conversation. If leadership isn't tracking it, the champion now has something to bring to them — and the rep has created a trigger for the next follow-up ("I'll send you the calculation framework so you can run this by your CRO before our next call").

Common failure modes in quantified impact probing

The most common failure is bailing on the quantification because the prospect says "I don't know the exact number." Reps who hear "I don't know" treat it as a signal to move on. The correct response is a range anchor: "That's fine — is it closer to $50K or $500K? We don't need precision, just order of magnitude." Almost every prospect can answer that question, and once they've committed to a range, they're in the quantification conversation rather than outside it.

The second failure mode is quantifying a metric the prospect doesn't care about. If the VP Sales cares about win rate and deal cycle length, and the rep quantifies the cost in terms of call recording storage and transcription time, the number lands flat. The quantification has to be connected to a metric the prospect is already accountable for. The diagnostic question at the start of the quantification sequence: "Of the things we've discussed, what's the one your leadership team is most focused on improving this year?" Then quantify in the units of that metric.

What this looks like in a coaching session

The most effective coaching drill for quantified impact is what we call the "cost calculator" exercise. Pull a call where the rep identified a problem but didn't quantify it. Find the exact moment — usually identifiable by the rep saying "that sounds like a real challenge" or "I can see how that would be frustrating" and then moving to a product capability. Pause. Ask the rep: "What question at this exact moment would have gotten them to a dollar figure?" Then role-play the next 90 seconds, with the manager playing the prospect and the rep trying the probing sequence.

This drill rarely takes more than 15 minutes and produces a muscle memory response that shows up in the next live discovery call. The goal is not to get reps to always walk away with a precise ROI figure — many deals don't need that level of specificity. The goal is to ensure every rep has the habit of attempting quantification and the probing sequence to make it feel natural to the prospect rather than like an interrogation.

See these behaviors scored on your team's calls

Book a 30-minute demo. Bring a recent discovery call — we'll score it live.

Get a Demo