Why we count conservatively (and why your audit figure may disappoint you)

A recovery number you can't verify is a marketing number. The figure the Revenue Leak Audit hands you is designed to survive an argument with your own CRM, which means most of what it finds gets thrown out before it's counted.

That design choice has a cost: our findings are smaller than what a less careful count would produce from the same portal. This piece explains exactly where the shrinkage happens, so that when your figure lands, you know what's inside it and what was deliberately left out.

What gets excluded

Companies that no longer exist. Contacts whose emails bounce. Job seekers, students, competitors, and vendors who filled out a form. Deals that were lost for cause; a real no is a no, not a leak. Anything without a plausible live buyer on the other end is out before arithmetic starts.

The exclusion pass is usually the largest cut. In a typical three-year-old portal, somewhere between a third and a half of superficially dormant records fail the plausible-buyer test. A naive count would happily include them, which is how inflated recovery promises get made: the vendor counts ghosts, quotes a number nobody can act on, and the disappointment arrives after the contract is signed instead of before.

Every exclusion is recorded with its reason. If we cut 1,400 records for bounced emails and dead domains, that line appears in the readout, and you can pull the same list in your own portal and check it.

What gets discounted

What survives exclusion doesn't get counted at face value. Recoverable pipeline is discounted by your own worked-lead close rate, pulled from your portal's history rather than an industry benchmark. If your team closes 3% of the leads it actually works, the audit uses 3%. Benchmarks flatter. Your history doesn't.

Deal-stage records get a second discount: recorded amounts are separated from derived ones. A deal your rep valued at $80K counts differently from a contact whose value we'd have to infer from company size, and the readout never mixes the two in one total. Derived value is labeled as derived, every time. The full method, including how leak rate itself is defined and measured, is laid out in the working definition of revenue leakage.

What we admit

Sometimes the figure is small. Teams with disciplined follow-up, clean ownership, and honest close dates exist, and their audits say so. If that's you, the readout will tell you not to hire us, in exactly those words. That's not generosity. A conservative figure you act on is worth more than an impressive one you doubt, and the guarantee only works if the counting is honest.

There's a second admission worth making: conservative counting can't see everything. Relationships that live in a rep's memory, deals conducted over channels the CRM never captured, buyers whose intent revived last week: none of that appears in a backward-looking query set. The audit measures what the portal can prove. The real pile is usually somewhat larger. We'd rather you discover the upside during recovery than the downside after signing.

Why disappointment is the design

Run the alternative. A vendor quotes you an exciting number built on face-value deal amounts and benchmark close rates. You sign. Recovery reality arrives at a third of the quote, trust evaporates, and the whole category of revenue recovery gets filed under snake oil. The inflated number didn't just cost that vendor a client; it poisoned the well for the honest count.

We run the sequence in the other direction. The figure that lands may be smaller than you hoped, but every dollar in it survives three tests: a live buyer exists, your own history says some of them close, and the records behind it are listed by ID for you to check. If the pile clears the audit guarantee threshold of 20 times the monthly fee, recovery is worth discussing. If it doesn't, you got a free, honest look at your portal's hygiene, which is more than most spend on the question. For a sense of what the honest arithmetic produces at typical scale, see what a modest leak rate costs a $10M company.

The practical consequence: when your audit figure lands, it may be smaller than you hoped. Every dollar in it is one your team can actually go get.