You're sitting in a pipeline review. A deal you expected to close is marked lost.
You dig into the notes. The rep showed up without a tailored value story. They referenced the wrong use case. They never addressed the CFO's core concern — even though your team had a case study that spoke directly to it. The information existed. It just never made it into the room.
This is not a rep performance problem. This is a preparation problem. And it's costing your organisation more than you think — it's just that nobody has ever put a number on it.
If you're a Sales Enablement leader, this is one of the most frustrating feelings in the role. You built the playbook. You curated the content. You ran the training. And somehow, none of it made it into the moment that mattered most.
The frustration isn't just operational. It's personal. Because you know the gap between what your team could do and what they're actually doing — and you carry that gap quietly, in every review, every quarter.
In the next 30 minutes, using data you already have, you're going to calculate the exact revenue your organisation is losing because of poor sales preparation. Not an estimate. Not a benchmark. Your number — specific to your team size, your average deal value, and your current win rate. That number will make the cost of inaction impossible to ignore, give you a concrete figure for your next budget conversation, and tell you exactly how much ROI a preparation platform needs to deliver to justify itself.
We've seen this exercise produce numbers that range from €800K to €4M in annual lost revenue for mid-market B2B teams. Whatever your number is, it will change how your leadership thinks about this problem.
Why This Problem Never Gets Fixed
You've probably already tried to solve this. Here's why it hasn't worked yet.
Industry benchmarks feel like the obvious starting point. They tell you the average rep wastes X hours per week on admin and preparation. That's useful for understanding the category — but useless for internal advocacy. Your CFO doesn't care about averages. They care about your numbers. A statistic from a vendor's research report will never move a budget conversation the way your own data will.
Gut feeling and anecdote are the next most common approach. Every enablement leader knows the problem is real. But "I think we're losing deals because reps are underprepared" doesn't survive a budget conversation. It needs a number attached to it. Without that number, the problem stays in the "important but not urgent" pile — indefinitely.
Generic ROI calculators seem like the answer until you use one. Most vendor-provided calculators are built to produce impressive outputs that justify their own product. You already know this, which is why you discount them. The framework in this article is different — it uses your own data, your own inputs, and produces a number that belongs to you, not to a vendor.
The most common alternative, though, is simply not doing the calculation at all.
Waiting until the CRM is cleaner, until the win/loss data is more complete, until the quarter is less busy, ...
This is inertia dressed up as strategy.
The real issue isn't any of these individual approaches. It's something more fundamental.
Most organisations think about sales preparation as a rep behaviour problem. They try to solve it with training, coaching, and better content libraries. Those things help sure, but they miss the root cause. The root cause is that preparation has no visible price tag. Nobody knows what a poorly prepared meeting actually costs. Nobody has calculated what it means in euros when a rep shows up without the right story. Because there's no number, there's no urgency. And because there's no urgency, the problem persists quarter after quarter, review after review.
This framework gives preparation a price tag. Once your organisation can see what poor preparation costs in revenue terms, the conversation shifts from "should we invest in this?" to "how fast can we fix it?"
Industry research consistently shows that B2B sales reps spend 30–40% of their time on non-selling activities, including manual research and meeting preparation. For a team of 50 reps, that's the equivalent of 15–20 full-time salespeople who aren't selling.
The 30-Minute Revenue Cost Calculator — Step by Step
Five steps. All using data you already have access to. Here's how to do this in 30 minutes.
Before you start, pull up three things: your CRM or last quarterly sales report, a rough sense of how many meetings your reps run per week, and your average rep quota. That's everything you need.
Step 1 — Anchor Your Baseline (8 minutes)
You can't calculate a cost without a starting point. This step gives you the three numbers everything else is built on.
Open your CRM or last quarter's sales report and find these three figures. Average deal value - total closed revenue divided by number of closed deals over the last 12 months. Current win rate - deals won divided by total deals entered over the same period. Number of active sales reps on your team right now.
This takes 8–10 minutes if your CRM is reasonably clean. If not, use your last quarterly report, the numbers don't need to be perfect, they just need to be directional.
The most common mistake here is using pipeline value instead of average closed deal value. Pipeline inflates the number and makes the calculation feel unrealistic when you present it. Use closed revenue only. It's conservative and defensible.
When you have three numbers written down, you're done with this step. Most enablement leaders have never had these three figures in one place at the same time. That alone is useful.
Step 2 — Quantify the Preparation Gap (7 minutes)
The preparation gap is where revenue leaks. This step makes that leak visible in hours.
Ask yourself (or a sample of three to five reps) three questions:
- How many customer-facing meetings does the average rep have per week?
- How long do they currently spend preparing for each one?
- And what would structured, high-quality preparation actually look like (and how long should it take)?
How many customer-facing meetings does the average rep have per week? How long do they currently spend preparing for each one? And what would structured, high-quality preparation actually look like and how long should it take?
Then run this calculation:
(Current prep time − Ideal prep time) × meetings per week × number of reps × 52 weeks = annual hours lost to inefficient preparation
This takes 5–7 minutes. You're building a directional case, not conducting an audit. An imperfect number that exists is more useful than a perfect number you never calculate.
When you have a total annual hours figure, write it down. Seeing "4,500 hours per year lost to preparation inefficiency" on a page creates a visceral reaction that no industry benchmark ever will. That reaction is what you're after.
Step 3 — Convert Hours to Revenue (5 minutes)
Hours are abstract. Revenue is not.
This step converts the preparation gap into the language your CRO and CFO respond to.
Use these formulas:
- Lost Revenue = Hours Lost × Rep Hourly Revenue Rate
- Rep Hourly Revenue Rate = Annual quota target ÷ 1,750 working hours per year
Take the lost hours figure from Step 2, multiply by the hourly revenue rate, and multiply by your number of reps. The result is the total annual revenue cost of preparation inefficiency across your team.
The mistake to avoid: using fully-loaded rep cost (=salary plus benefits) instead of quota-based revenue rate. The cost-based number tells you what inefficiency costs operationally. The revenue-based number tells you what it costs in lost output. That second number is the one that moves executives.
When you have a euro figure, write it at the top of a blank page in large font. This is the number you're going to take into your next conversation with the CRO.
Step 4 — Calculate the Win Rate Recovery (5 minutes)
The previous steps calculate what you're losing. This step calculates what you'd recover =which is the ROI frame that justifies any solution.
Take your current active pipeline value (the deals in your CRM right now) and apply a conservative win rate improvement of 5–8%, or whatever yours is if you know it.
Recovered Revenue = Active Pipeline × Win Rate Improvement %
Then compare that figure to the cost of any solution you're considering. If recovered revenue significantly exceeds solution cost, the ROI case is self-evident.
Use active pipeline only — not total addressable pipeline. It's more conservative and far more defensible when a Finance leader pushes back.
When you have both numbers, (the cost of the problem and the value of the solution) you have your ROI argument.
If recovered revenue is 3–5x the solution cost, you have a strong case. Most teams find it's 8–15x.
Step 5 — Build the One-Slide Executive Summary (5 minutes)
The calculation is only valuable if you can communicate it clearly. This step turns your four numbers into a single, shareable executive summary.
Create a one-page summary with four elements.
- The problem in one sentence: "Our team is losing an estimated €X per year due to preparation gaps."
- The three supporting numbers: hours lost, revenue cost, win rate impact.
- A benchmark comparison: "Teams that address this recover 6–10% of pipeline within two quarters."
- And a proposed next step: "A structured 90-day pilot would cost €Y and is projected to recover €Z."
The most common mistake is over-engineering this.
One number, clearly stated, with three supporting data points is more persuasive than a dense analytical exhibit. Executives respond to clarity, not comprehensiveness.
When you're done, you have something you could send to your CRO today. Not a proposal. Not a formal business case. A single, clear statement of the problem and the opportunity in a format that invites a conversation rather than demanding a decision.
Common Questions Before You Start
My CRM data isn't clean enough to do this accurately.
You don't need clean data. You need directional data. A rough calculation with conservative inputs is more persuasive than no calculation at all. Use your best estimates and note your assumptions explicitly. That transparency actually builds credibility with executives rather than undermining it. "Based on conservative estimates using last quarter's pipeline data" is a perfectly defensible framing.
My leadership will ask where these benchmarks come from.
Every benchmark in this framework comes from published B2B sales research and documented customer outcomes. The core calculation, however, uses only your own data. That means the number belongs to you, not to a vendor. When leadership asks, you can point to your own CRM as the primary source.
What if the number is lower than I expect?
A smaller number is still a number. And it still tells you something important. If the aggregate figure seems low, run the calculation by segment: by region, by product line, by rep tenure. You'll almost certainly find that the problem is significantly larger in specific pockets than the overall average suggests. That segmentation also tells you where to start.
Your Next Step Takes Two Minutes
Open your CRM. Pull last quarter's closed revenue report.
Write down three numbers:
- Average deal value
- Win rate
- Number of active reps.
That's it. The rest of the calculation takes less than 20 minutes from there.
