Revenue Leakage: Where It Hides in HubSpot and How to Stop It

Revenue leakage is revenue that a company has already earned the right to, through a signed contract, an existing customer relationship, an advanced sales conversation, or a qualified inbound interest, and which is not collected or converted because a process step failed to fire — not because the customer said no. It is a distinct category from three things it is routinely confused with, and the confusion is expensive because it leads finance and sales leadership to solve the wrong problem.

In portal after portal, leakage concentrates in seven recurring places. Each has a distinct HubSpot signature, a distinct owner, and a distinct fix — which is why a single "clean up the pipeline" initiative rarely works. You have to work each leak point on its own terms.

1. Stalled open deals. Deals sitting in a mid-funnel dealstage for far longer than your historical median time-in-stage, with hs_lastmodifieddate moving (someone touched a field) but hs_last_sales_activity_timestamp static (no one actually spoke to the buyer). These are deals that look alive in a pipeline report and are functionally dead.
2. Unmanaged renewals and rebookings. Renewal deals with a closedate inside the next 60–90 days and no logged next step, or worse, no renewal deal created at all despite an active contract. These are the highest-value, fastest-to-recover leak in almost every portal we've examined, because the relationship is warm and the decision is comparatively low-friction.
3. Dormant relationships. Contacts and companies in an active lifecyclestage (customer, opportunity) with no engagement — no email opens, no meetings, no notes_last_contacted update — for 90-plus days. The relationship exists on paper but has gone cold operationally.
4. Unrevisited lost deals. Deals marked closedlost (hs_is_closed = true, hs_is_closed_won = false) where the loss reason was timing, budget or "went quiet" rather than a competitive loss or a hard product gap — and which have not been reapproached in the 6–18 months since. Timing objections resolve; nobody goes back to check.
5. Unquoted line items and expired quotes. Deals where a quote was generated but never sent, or sent and never followed up before its expiration date, leaving genuine buying intent to evaporate on an administrative technicality rather than a commercial decision.
6. Ownership handover gaps. Deals and accounts where hubspot_owner_id was reassigned — through territory changes, promotions or attrition — and the new owner has not logged a first touch within a reasonable window. The account doesn't churn dramatically; it just slowly stops being worked.
7. Silent process leaks. Inbound leads and form fills that entered the CRM correctly but were never assigned, or were assigned and not contacted within your stated SLA — commonly visible as a gap between createdate and the first logged activity on the associated contact or deal.

Before you can size or prioritise leakage, you need a shared reference table that every stakeholder — sales, RevOps, finance — agrees to use. This is the version we recommend teams adopt as their internal standard.

The single biggest credibility risk in any leakage initiative is presenting one number. Boards and CFOs have seen enough optimistic pipeline forecasts to be instinctively sceptical of any large recovery figure, and they are right to be. The fix is structural: always separate gross exposure from expected recovery, and always show your working.

Consider a B2B software company with $12M in annual revenue, roughly 340 open and recently closed deals in its HubSpot portal, and a customer base of 210 active accounts. Running the seven-category taxonomy against 18 months of deal and engagement history produces the following exposure picture.

Two things are worth noting about this shape, because they recur across portals of similar size. First, renewals and rebookings contribute disproportionately to expected recovery relative to their share of gross exposure, because the recovery rate on a warm renewal is far higher than on a cold, dormant account — which is exactly why renewals should be worked first in any 30-day cycle. Second, the CRM health category doesn't carry a recovery percentage of its own, because its value is realised indirectly: cleaning ownership gaps and stale fields improves the accuracy and recovery rate of every other category, rather than converting to revenue on its own.

For this company, the honest board statement is: "$1.4M sits exposed to leakage across the base; based on our own historical conversion rates, we expect to recover approximately $380,000 of that within the next two quarters if we run a disciplined recovery process, starting with renewals." That is a defensible, specific, falsifiable claim — and it is the kind of number that survives a second and third quarter of scrutiny.

The instinctive response to a leakage number is to ask reps to "work the base harder." This almost never works, for a structural reason: the leak points are invisible inside a standard deal-by-deal or activity-by-activity view. A rep opening HubSpot each morning sees their assigned open deals, not the dormant account they haven't touched in four months or the renewal quietly approaching in another rep's book after a handover. The information required to catch a leak early simply isn't surfaced by the interface reps use daily.

This is compounded by incentive design. Commission plans reward closed-won revenue on new and active deals; they rarely reward the unglamorous work of re-engaging a dormant account or chasing down an expired quote. Without a structural mechanism — a report, a threshold, an alert, an accountable owner — leakage will always lose out to whatever is visibly urgent in the current pipeline, regardless of how hard any individual rep works.

The fix, correspondingly, is systemic rather than motivational: instrument the seven leak points as standing reports, assign explicit thresholds and owners, and build a weekly ritual that surfaces new leaks before they compound into dormant or lost status. Effort applied inside a system that doesn't surface the problem produces no measurable change in the leakage number quarter over quarter.

A leak-stopping programme needs to be time-boxed, owned and reviewed weekly, or it dissolves into ambient good intentions. The following structure has held up across companies from $5M to $50M in revenue; adjust thresholds to your own sales cycle length, but keep the rhythm.

The difference between catching a leak in-week and discovering it in a quarterly business review is entirely a function of which indicators you track and how often. Lagging indicators — closed-lost revenue, churned ARR, missed quota — tell you what already happened. The following leading indicators, tracked weekly against the same seven categories, tell you what is about to happen.

• Days since last activity, by deal and by account — using hs_last_sales_activity_timestamp rather than hs_lastmodifieddate, which can be misleadingly recent due to automated field updates.
• Renewal-date proximity distribution — the count of renewal deals entering the 90-, 60- and 30-day windows each week, so the pipeline of upcoming renewal risk is visible before any individual renewal is overdue.
• Owner coverage after handover — the percentage of reassigned deals and accounts with a logged first touch within 5 business days.
• Quote-to-send lag — the gap between quote creation and quote being sent, and separately, quote-sent to first follow-up.
• Lead response time against SLA — the gap between createdate on a new inbound contact or deal and its first logged activity, tracked as a distribution, not just an average.
• Lifecyclestage drift — accounts sitting in "customer" with zero engagement events in a rolling 90-day window, which is the earliest visible signal of an emerging dormant relationship.

None of these indicators requires new CRM fields; all of them can be built from properties HubSpot already tracks natively. The discipline is in reviewing them weekly, at a fixed time, with a named owner for each — not in the sophistication of the underlying calculation.

Leakage reporting lives or dies on credibility. A board that catches one inflated or unexplainable number will discount every subsequent figure you present, regardless of accuracy. The following mistakes are the ones we see most often, and each is avoidable.

1. Presenting gross exposure as if it were forecast revenue. This is the single fastest way to lose credibility. Always label exposure as exposure and recovery as recovery, and never let the two numbers appear in the same cell of a table.
2. Using an industry benchmark instead of your own historical conversion rate. A generic "companies typically recover 20% of stalled pipeline" claim, unless it comes from your own closed-deal history, is not defensible under questioning and should not be used.
3. Double-counting a deal across two leak categories. A deal can be both stalled and approaching a renewal date; decide a single primary category per record before summing, or your total exposure figure will be inflated and impossible to reconcile.
4. Reporting a single snapshot instead of a trend. One point-in-time exposure figure invites the question "compared to what?" Track gross exposure and expected recovery monthly so the board sees direction, not just magnitude.
5. Failing to reconcile the recovery figure against actual closed-won revenue and actual renewed contracts. If you claimed $380,000 in expected recovery, the next board update needs to show what actually landed against that figure — silence on reconciliation is read as evasion.
6. Attributing recovery to the programme without isolating it from normal pipeline activity. Some of the deals in your stalled-deal category would have closed anyway. Be conservative and explicit about what you're claiming as incremental versus business-as-usual.