TL;DR
Revenue leakage is revenue that was real and in motion, then quietly went missing. In B2B, it rarely starts as an invoice error. It starts as a renewal risk raised on a support call, a champion who left, a deal that went quiet, and no one who could act on it ever heard about it.
Most B2B revenue leaders have had the quarter where pipeline looked healthy, and the close did not, and the CRM could not say where the difference went. Forrester found that 86% of B2B purchases stall during the buying process. Revenue leakage is what that looks like inside your own numbers. This article answers where B2B leaders should watch to stop the revenue leakage.
What Is Revenue Leakage?
Revenue leakage is revenue that was real and in motion, committed, renewable or expandable, and was lost because a signal never reached the person who could act on it in time. It is usually preventable, and it rarely shows up as a billing error on a report.
Most published definitions frame leakage as a quote-to-cash or invoicing problem. That framing is legitimate, and it is also narrow. In a complex B2B sale, the larger share of leakage sits upstream of the invoice, in deals, renewals and expansion conversations.
The practical test is simple. If someone in your company knew something that would have changed the outcome, and the person who owned the account did not know it in time, that is leakage. Not fraud, not pricing model failure. A routing failure.
How Much Revenue Leakage Actually Costs B2B Companies
There is no verified benchmark for leakage as a percentage of B2B software revenue. PwC puts leakage at 1% to 5% of income for telecommunications companies, which is the closest published benchmark; no equivalent figure has been published for B2B software (Optimizing revenue with data & analytics, December 2020).
What can be quantified is the compounding. Forrester’s renewal arithmetic shows that on a $1 million recurring revenue stream, a 90% annual renewal rate loses $344,000 over four years, an 85% rate loses $478,000, and an 80% rate loses more than $600,000 (Four Keys to Increasing Renewal Rates).
McKinsey puts the same point in enterprise-value terms. Top-quartile B2B SaaS companies achieve net revenue retention of 113% while bottom-quartile peers reach 98%, and top-quartile companies held median EV/revenue multiples of 24x versus 5x for bottom-quartile peers across Q1 2019 to Q4 2024 (The net revenue retention advantage, 19 November 2025).
Alfonso Pulido, Senior Partner at McKinsey, and co-authors Begum Erdogan and Jake Berliner write that “it is more critical than ever for software vendors to have regular, outcome-based conversations that remind customers of the benefits of a continuing partnership.”
Fifteen points of NRR is not an invoicing problem. It is an accumulation of small, individually forgivable misses.
10 Hidden Causes of Revenue Leakage
Let’s break down the 10 signs of revenue leakage and how to proactively counter them before the actual loss.
1. Deals that go quiet without anyone noticing
A deal does not usually die on a call. It fades. The last meaningful reply was three weeks ago, the rep has eleven other deals, and the opportunity stays at 60% because nothing has formally changed.
Example: an enterprise deal sat at stage four for six weeks after the buyer’s procurement lead was reassigned. Nobody updated the record because nobody was told.
2. Renewal risk that never reaches the account owner
The clearest renewal warnings usually arrive somewhere other than the renewal conversation. Support sees them, CS sees them, and the person who owns the commercial relationship reads about it after the fact.
Example: a customer raised the same integration failure in three tickets across a quarter. The account owner learned about it during the renewal call itself.
3. Expansion signals buried in support conversations
Expansion intent gets logged as a feature request. A customer describing a new team, a new region or a new workflow is describing budget, but the ticket taxonomy has no field for that.
Example: a user wrote “we’re rolling this out to our Germany team next quarter, will licenses transfer?” That ticket closed as a billing question.
4. Outdated or incomplete CRM records
A CRM records what someone chose to enter. Where entry is inconsistent, downstream forecasting inherits the gap. Gartner research from 2020 puts the cost of poor data quality at least $12.9 million a year on average and finds that 59% of organizations do not measure data quality (Data Quality: Why It Matters and How to Achieve It).
Example: two of the four buying-committee members on a six-figure opportunity were never added as contacts.
5. Verbal commitments that never get logged
Reps hold a private view of a deal that differs from the recorded one. That is not misconduct, it is behavior. Bob Suh, writing in Harvard Business Review, observed that “salespeople commonly withhold information about deals that aren’t going well, they keep two sets of books (one for the CRM system and one for themselves), and cling to unrealistically optimistic beliefs about how a troubled deal is going,” and that “the root causes of most inaccuracies are not faulty algorithms but human behaviors” (Sales Teams Aren’t Great at Forecasting, 19 March 2019).
Example: a verbal agreement to expand by 40 seats at renewal, made on a call, never appeared anywhere a forecast could see it.
6. Pricing and discounting inconsistencies
Discounts compound invisibly across a deal. McKinsey’s pocket price waterfall, published in 2003, showed a global lighting supplier where on-invoice discounts reduced list price by 32.8%, with a further 16.3 percentage points of off-invoice leakage, leaving average pocket price at about half of standard list (The Power of Pricing, 1 February 2003). The mechanism travels even though the figure is two decades old and not a SaaS number.
Example: a renewal repriced off the previous discounted rate rather than list, permanently resetting the baseline.
7. Handoff gaps between sales and customer success
The handoff is where context dies. What the buyer actually bought, what they were promised, and which outcome they will judge you on often do not survive the transition.
Example: an onboarding team optimized for the use case in the order form, not the one the champion described on the last sales call.
8. Contract and billing errors
This is the leakage everyone already writes about: unbilled usage, missed escalators, auto-renewal clauses nobody tracked. It is real, it is measurable, and finance usually owns it. Fix it, then look upstream, because it is rarely the largest share in a B2B sales motion.
Example: an annual contract that auto-renewed month-to-month without the contractual 5% price escalator applied.
9. Champion turnover that goes undetected
Your champion leaves, and the relationship resets to zero without anyone declaring an incident. The account looks green until the renewal conversation with a stranger.
Example: an out-of-office reply that never came back, followed four months later by a renewal routed to a new director who had never heard of your team.
10. Slow signal-to-action time
Sometimes the information exists, reaches someone, and still arrives too late to matter. Gartner found that 45% of sales leaders and sellers have high confidence in their organization’s forecasting accuracy, and 47% believe their organizations have high-quality data (Gartner Says Less Than 50% of Sales Leaders and Sellers Have High Confidence in Forecasting Accuracy, 12 February 2020).
Craig Riley, Senior Principal Analyst in Gartner’s Sales Practice, notes that “heads of sales operations are under constant pressure to produce accurate forecasts to help shape decision making.”
Example: a risk flagged in a Monday internal thread reached the account owner in the Friday pipeline review, eight days before the renewal date.
| Cause | Where it hides | How to catch it |
| Deals going quiet | Calendar gaps, unanswered email threads | Time-since-last-meaningful-contact review |
| Renewal risk unrouted | Support queue, CS threads | Cross-team review of top renewals |
| Expansion buried in support | Ticket text, feature requests | Read tickets from named accounts monthly |
| Outdated CRM records | Contact and stakeholder fields | Buying-group completeness check |
| Unlogged verbal commitments | Call recordings, rep memory | Deal review against recorded calls |
| Pricing inconsistency | Quote and renewal history | Realized price versus list, by account |
| Sales to CS handoff gaps | Onboarding notes | Compare promised outcome to onboarding plan |
| Contract and billing errors | Invoices, contract terms | Finance audit of usage and escalators |
| Champion turnover | Email bounces, job changes | Contact-health check on key accounts |
| Slow signal-to-action | The gap between knowing and acting | Measure days from first mention to owner action |
Read next: how to find revenue leakage hidden in customer conversations
Revenue Leakage vs. Lost Revenue: Are They the Same?
No. Revenue leakage is preventable revenue that is still recoverable if caught in time. Lost revenue is the same opportunity after the window has closed.
The distinction is operational, not semantic. It tells a team what to work on first. A renewal at risk with six weeks left is leakage and deserves attention today. A renewal that lapsed last month is lost revenue and belongs in a post-mortem, not a pipeline review.
More detail in the dedicated piece: revenue leakage vs. lost revenue.
How to Identify Revenue Leakage in Your Business
Start with the channels where the evidence actually lives: sales calls, support tickets, customer success email, internal chat and internal meetings.
The structural problem is that this evidence is unstructured. Mark Beyer, Distinguished VP Analyst at Gartner, states that “unstructured data, such as documents and multimedia files, accounts for 70% to 90% of organizational data” (Gartner Data & Analytics Summit 2026 London: Day 2 Highlights, 12 May 2026). That figure describes enterprise data overall rather than revenue data specifically, but the shape of the problem is the same: the record is structured; the evidence is not.
This is what Revenue AI Signals addresses. It reads across customer-facing conversations, flags contradictions where the record says one thing, and the conversations say another and emails the finding to the person who owns the account, with no new login and no new dashboard. fifthelement.ai defines a signal as “a piece of revenue-relevant intelligence, surfaced from inside your customer-facing organization, that would change what an AE, CSM, or sales leader does, if they knew it in time.” The six categories of revenue AI signals cover the detection patterns in detail.
Two limits worth stating plainly. The system surfaces contradictions; humans resolve them. And no accuracy percentage is published for detection, so treat any vendor quoting one with care. On data handling: SOC 2 (Type II), RBAC/FGAC, audit logs, SSO/SCIM, encryption in transit and at rest, deployed as SaaS, private cloud/VPC or on-prem.
Proof lives on the Revenue Operations & Sales Intelligence page, where a multinational software company reduced CRM upkeep time by 60 percent, per fifthelement.ai’s own data.
Frequently Asked Questions
Q1. What is revenue leakage?
Revenue leakage is revenue that was real and in motion, committed, renewable or expandable, and was lost because a signal never reached the person who could act on it in time. It is usually preventable, and it rarely shows up as a billing error on a report.
Q2. What causes revenue leakage?
Most commonly: deals that go quiet without anyone noticing, renewal risk that never reaches the account owner, expansion intent buried in support conversations, and verbal commitments that never get logged. Billing and contract errors matter too, but in B2B sales motions they are usually the smaller share.
Q3. How do I identify revenue leakage in my business?
Look in the five places the evidence lives: sales calls, support tickets, customer success email, internal chat threads and internal meetings. Pick ten named accounts, read the last quarter of conversation across all five, and count how many findings never reached the account owner.
Q4. How do I prevent revenue leakage?
Three steps. Define what a revenue-relevant finding looks like in your business. Give it a route to a named owner with a deadline. Measure the days between first mention and owner action, because that number is the one that predicts whether leakage becomes loss.
Q5. What’s the difference between revenue leakage and lost revenue?
Revenue leakage is preventable revenue that is still recoverable if caught in time. Lost revenue is the same opportunity after the window has closed. The distinction drives triage: leakage goes on this week’s list, lost revenue goes into the post-mortem. More in the dedicated comparison.
Q6. What are some examples of revenue leakage?
A customer mentioning a Germany rollout in a support ticket that closed as a billing question. A champion whose out-of-office never came back. A verbal commitment to add 40 seats that never reached the forecast. A renewal repriced off a discounted rate rather than list.
Q7. How much revenue do companies typically lose to leakage?
PwC puts leakage at 1% to 5% of income for telecommunications companies, which is the closest published benchmark; no equivalent figure has been published for B2B software. Treat any precise SaaS percentage with suspicion, because the widely circulated ones do not trace to a primary source.
Q8. How does AI help detect revenue leakage?
It reads across calls, tickets, email and internal channels continuously, flags where the record and the conversations disagree, and routes the finding to the account owner by email. No published accuracy figure exists, and humans still resolve the contradiction. See Revenue AI Signals.
