Most B2B SaaS leadership teams can point to a number that feels wrong. Pipeline coverage that never converts at the rate the forecast implies. A renewal that should have closed and did not. A demo request that sat in a queue for four days before anyone called the prospect. Each of these is a symptom. A revenue leakage audit is the discipline of tracing the symptom back to a specific record, a specific owner, and a specific breakdown, rather than accepting the general sense that something is wrong.
The temptation is to skip straight to a tool purchase or a new dashboard. That usually treats the wrong layer of the problem. Before you touch a system, you need a list of records that prove where revenue actually stopped moving. This checklist walks through that process end to end, from inbound lead routing to renewal forecasting, and gives you a way to size the dollars at risk without overstating what you find.
None of these figures tells you what is happening inside your own CRM. They set the stakes. If most of your revenue depends on renewals and a meaningful share of buyer attention is won or lost in a narrow window, then a routing delay or an unowned renewal is not a minor process gap. It is a direct hit to the number the board expects.
Set a scope before you start. Pick a recent 90-day period and follow a sample of leads, opportunities, and customers from first touch through to renewal, using the same reporting window across every system you check. Keep a working sheet with the record ID, the expected next step, the actual event, the owner, the timestamp, and the evidence behind each entry. If a field is missing or a status is unclear, label it unknown. Do not count it as a confirmed loss. That single discipline separates a credible audit from a spreadsheet of assumptions.
Where revenue actually stops moving
Revenue leakage rarely announces itself. It shows up as a series of small, individually defensible decisions: a lead that waited one extra day, a deal that stayed in "negotiation" past its close date, a customer success handoff that depended on someone remembering to forward an email. Each check below targets one of these handoff points and tells you what to pull, what to look for, and which team should be in the room when you review it.
Inbound lead routing
Take every demo request in the period. Compare submission time with the time the record got an owner and the time of first real outreach. Break out records that never got an owner, landed in the wrong territory, or were assigned to a rep who was inactive. Determine whether the delay traces back to form mapping, lifecycle stage rules, assignment logic, or a stalled integration queue. In HubSpot, lead properties such as owner-assigned date and time-to-first-touch depend on the object and workflow your team has configured, so confirm the definition before you trust the report (HubSpot lead properties documentation).
This is GTM operations territory. Routing logic, form mapping, and lifecycle rules live in the systems that team owns.
Marketing-to-sales handoff
Count leads marked qualified by marketing, then inspect whether sales accepted them, rejected them with a documented reason, or never touched them at all. Pull the actual record history rather than relying on a funnel chart, which will smooth over exactly the gaps you are trying to find. A high volume of qualified leads with no next event usually means one of three things: the two teams define "qualified" differently, required fields are missing at handoff, or the automation that should trigger the handoff has failed silently.
Opportunity progression
List open deals with overdue close dates, no scheduled buyer meeting, no recent buyer activity, or an unusually long time in stage. Review a sample with the deal owner directly. Some of these are active negotiations that are simply under-documented in the CRM. Others are no longer viable and are inflating the forecast. Separate the two before you estimate anything. Compare the stage history against your documented sales process. If deals can advance without a clear exit criterion at each stage, the forecast will keep hiding exactly where buyers stall.
Closed-won to onboarding
For a sample of new customers, compare the signed date, the customer success owner assignment, the kickoff date, and the first value milestone. Note missing handoff fields, unclear implementation scope, and deals that were sold with terms customer success never received. A clean close in the CRM tells you the deal was won. It does not tell you whether the customer was actually set up to renew.
Renewal and expansion
Build a list of every account renewing in the next two quarters. For each one, check the contract end date, the renewal owner, current product usage or health signal, the renewal opportunity record, and the date of the last customer conversation. Flag accounts with missing owners and accounts marked healthy despite no recent evidence supporting that status. Reconcile the CRM renewal forecast against billing and contract records before calling any discrepancy a confirmed leak.
A framework for sizing what a leak actually costs
Once you have a list of suspected leaks, the next mistake is treating every flagged record as lost revenue. A stalled opportunity might still close. A delayed lead might have converted anyway. The goal of sizing is to produce a defensible range, with the assumptions shown next to the number, not a single figure that implies more precision than the data supports.
For lead delays, compare the affected group against a similar group that received timely follow-up, and use the difference in conversion rate rather than assuming every delayed lead was lost.
Apply the same logic across the other checks, using different inputs for each:
- Renewals: use contract value, the specific documented risk signal, and a realistic retention probability rather than treating every unowned renewal as a certain loss.
- Stale opportunities: report pipeline at risk as a separate line from expected revenue. Do not fold a soft forecast number into a hard exposure figure.
- Onboarding delays: measure the gap between signed date and first value milestone against your fastest cohort, then estimate the churn or expansion risk attributable to that gap.
One discipline matters more than any formula: never add overlapping estimates from the same account twice. If an account shows up in both the stale-opportunity list and the at-risk renewal list, decide which exposure category owns it before it goes into a total.
Running the audit in practice
Who owns each part of the workflow
A leakage audit crosses team boundaries by design. Assigning the wrong owner to a finding is one of the fastest ways to stall the fix. Use this as a rough map of where each check tends to land, understanding that the exact split depends on how your revenue org is structured.
Lead routing, form mapping, lifecycle stage definitions, and the marketing-to-sales handoff trigger. These are system and workflow issues more often than they are people issues, and they are frequently the fastest to repair once diagnosed. See GTM Operations.
Opportunity stage discipline, exit criteria, deal amount accuracy, and forecast hygiene. This is where a healthy-looking pipeline and an honest pipeline diverge. See Sales Operations.
Onboarding handoff, activation milestones, renewal ownership, and health signal accuracy. Leakage here is often the most expensive because it compounds against contract value already booked. See CS Operations.
Reporting reconciliation across CRM, billing, and finance, and the definitions that keep every team looking at the same number. See Revenue Intelligence.
How this reads in the boardroom
The same finding lands differently depending on how it is framed. These three cards show the same underlying data problem told three ways, so you can see the difference between a status update, a risk narrative, and an action plan.
"Pipeline coverage is at 3.2x for the quarter, in line with target. Marketing qualified lead volume is up 14 percent quarter over quarter." This is accurate and says nothing about whether the leads are being worked or whether the pipeline behind the coverage number will actually close.
"Of the 80 qualified leads generated last quarter, 22 sat unassigned for more than 48 hours, and this group converted to opportunity at roughly two-thirds the rate of leads that were worked on time. We estimate $30,000 to $50,000 in delayed-lead exposure this quarter, based on a comparison against timely-response leads, not a confirmed loss." This version names the mechanism, shows the range, and states the assumption.
"We are fixing lead routing this month, resetting the assignment rule and adding an alert for unassigned records past four hours. We will recheck time-to-first-touch in 30 days against this quarter's baseline and report the delta at the next review." This is what a board or an investor actually wants to hear after the risk has been named.
Where leakage connects across the revenue engine
Leakage checks are often run in isolation, one team looking at its own funnel stage. The pattern worth watching for is when the same account shows up in more than one check: a lead that was delayed at routing, went through a weak qualification handoff, sat as a stale opportunity, and is now an at-risk renewal with no clear health signal. That account is not four separate problems. It is one account that never got a consistent owner across its lifecycle, and it is the clearest signal that the issue is structural rather than a one-off mistake.
This is the point at which a checklist stops being sufficient on its own. A full audit examines GTM operations, sales operations, customer success operations, and revenue intelligence together, across the same accounts, using HubSpot or Salesforce as the system of record. VANDFORT's GTM Audit is built for exactly this: a structured review of where revenue stalls across the full customer lifecycle, with a deliverable that names specific records and specific fixes rather than general recommendations. You can review the scope and current offer on the audit page, or see how the engagement runs on the How We Work page.
Common questions
What is the difference between revenue leakage and churn?
Churn is revenue lost from customers who leave or reduce spend. Revenue leakage is a broader diagnostic label for revenue that fails to convert, is billed incorrectly, or is not retained as expected. Define each suspected leak against your own records so the same lost dollar is not counted twice across categories.
Can this audit be run inside HubSpot or Salesforce alone?
Yes, as a starting point. The CRM's lead, opportunity, and activity history will surface most routing and pipeline issues. A CRM-only review can show an overdue handoff clearly, but it will often miss what happened after the sale, which is why customer success and billing records need to enter the picture for renewal and onboarding checks.
How often should this be repeated?
Monitor assignment failures and overdue handoffs on a rolling basis so live cases get fixed quickly. Repeat the broader audit when a funnel metric shifts, a team changes its process, or you migrate systems. Keep the definitions and reporting window consistent between runs so the before-and-after comparison actually means something. For a lighter, recurring check, VANDFORT's GTM Health Score is designed as the faster version of this diagnostic.
