The HubSpot Revenue Audit: A Definitive Method

A HubSpot revenue audit is a structured review of every deal, contact, and company record in a portal, undertaken specifically to answer one question: where is revenue that the business is entitled to, or has already earned the right to pursue, sitting unaddressed? It is not a data-quality audit, though data integrity is one of its six areas. It is not a forecast review, though open pipeline is one of its six areas. And it is not a CRM adoption audit, though follow-up discipline overlaps with adoption.

The distinction matters because each of those adjacent exercises answers a narrower question. A forecast review asks whether the quarter will land, using the subset of deals reps have already flagged as commit or best-case in their pipeline meetings. A CRM audit asks whether the system is being used correctly — are fields populated, are stages consistent, is data clean. A revenue audit asks a wider, more commercially blunt question: across the entire history in this portal, including deals nobody is thinking about right now, what is recoverable?

That reframing is deliberate. Deals that stalled eight months ago and were never formally closed lost. Contracts that renewed automatically without anyone checking usage or expansion potential. Customers who went quiet eleven months ago after a champion left, with no one flagged to re-engage them. None of these show up in a forecast call, a QBR deck, or a pipeline review — because by definition, they've fallen out of anyone's active attention. A revenue audit exists to surface exactly that category of exposure: real, dollar-denominated, and currently invisible.

In our experience the request to run a revenue audit tends to come from one of four situations, each with a slightly different emphasis.

A comprehensive audit covers six distinct areas. Each has its own diagnostic questions, its own HubSpot properties, and its own typical failure modes.

• Open pipeline credibility. Which open deals haven't had a stage change or logged activity in 60, 90, or 120+ days, and are they still realistically alive?
• Renewals and rebookings. Which contracts are approaching or have passed their renewal date with no linked renewal deal, task, or recent contact?
• Dormant relationships. Which customers or high-value contacts have had no logged engagement in six months or more, despite an active or recently active lifecyclestage?
• Win-back opportunities. Which closed-lost deals, especially those lost to "no decision" or budget rather than to a named competitor, are worth a second approach?
• CRM data integrity. How many duplicate contacts or companies exist, how many deals are missing amount or closedate, and how consistently is dealstage used across the team?
• Follow-up discipline. How many contacts or deals have exceeded your internal SLA for a follow-up touch after their last inbound signal?

The rest of this guide walks through each of these in the audit method below, with the specific properties and view filters to use for each.

The method below is designed to be executed inside HubSpot itself, using saved views and property filters, so that it is reproducible by anyone on the team and re-runnable on a schedule without rebuilding it from scratch each time.

1. Fix the audit window and confirm access. Default to a 24-month lookback (36 months if your typical contract term exceeds 12 months). Confirm you have reporting access across deals, contacts, companies, and engagements for the whole portal, not filtered to your own owned records.
2. Build the stalled-pipeline view. Filter deals where hs_is_closed is false, and hs_lastmodifieddate is older than 90 days, grouped by dealstage and hubspot_owner_id. Cross-reference against amount to rank by dollar exposure, not deal count.
3. Build the renewals view. For subscription or contract businesses, filter closed-won deals or active company records where a renewal or expiration date property is within 60 days forward or has already passed, with no associated open renewal deal. If you don't track a dedicated renewal date property, approximate using closedate plus contract term.
4. Build the dormancy view. Filter contacts and companies where lifecyclestage is customer or opportunity, and both hs_last_sales_activity_timestamp and notes_last_contacted exceed 180 days, excluding records with an open support ticket that would explain the quiet.
5. Build the win-back view. Filter deals where dealstage is closed-lost, closedate falls within the lookback window, and the closed-lost reason property excludes "competitor selected" — no-decision and budget-related losses convert back at meaningfully higher rates than competitive losses.
6. Build the data integrity view. Run HubSpot's duplicate management tooling for contacts and companies, and build a separate view for deals missing amount, missing closedate, or sitting in a dealstage that has not been used by the rest of the team in the past 90 days (a sign of an abandoned or legacy pipeline stage).
7. Build the follow-up discipline view. Filter contacts with a recent form submission, meeting request, or inbound email where notes_last_contacted is either blank or older than your SLA (commonly 48 or 72 hours for inbound-qualified leads).
8. Export, reconcile, and de-duplicate across views. A single account can appear in both the dormancy and renewals views; decide a hierarchy so it's only counted once in the total exposure figure, with a note on which categories it also touches.
9. Size each finding conservatively. See the sizing method in the next section — do not sum face-value deal amounts uncritically.
10. Package findings by owner and category, not as one long list. A rep or CS manager needs their fifteen relevant records, not a 400-row spreadsheet covering the whole portal.

The single most common way a revenue audit loses credibility is by summing raw deal amounts without adjustment. A CFO who sees "$2.1M of recoverable pipeline" made up of full-value stalled deals will, correctly, discount it heavily and possibly dismiss the whole exercise. The fix is to apply a conservative, category-specific adjustment to every finding before it goes into a total.

• Open pipeline at risk: apply your historical stage-to-close conversion rate for that specific dealstage, not a flat 50%. A deal stalled in an early-stage bucket with a 12% historical close rate should be sized at 12% of amount, not full value.
• Renewals: size at the historical renewal rate for that customer segment (commonly 80-95% for healthy SaaS books), applied to the contract's annual value, minus any known churn signals (support escalations, usage decline) which should push the estimate down further.
• Dormant relationships: size using an expansion or reactivation rate benchmark from your own closed-won history for similarly dormant accounts that were later re-engaged, not from the account's full potential spend.
• Win-backs: apply your historical win-back conversion rate (typically lower than fresh pipeline, often 8-20%) to the original deal amount, adjusted for how much time has elapsed since the loss.
• Data integrity and follow-up discipline findings: these are usually sized as risk-to-existing-pipeline rather than net-new dollars — for example, the dollar value of deals whose data quality issues make their forecast inclusion unreliable.

The output of this stage should be two numbers for every category: a gross figure (what's technically at stake) and a recoverable estimate (what a conservative, historically grounded conversion rate suggests is realistically achievable). Present both. Boards and CFOs trust ranges with visible methodology far more than a single confident number with none.

There are four broadly available ways to run this audit, and they trade off differently on speed, coverage, and reproducibility.

None of these is universally wrong. A consultant engagement earns its cost when the findings need to feed a broader operating-model redesign. Native reporting is perfectly adequate for a single-category question, like "how many deals are stalled in negotiation." Where an automated scan tends to win is when the ask is exactly the one this guide is built around: a full-portal, defensible, re-runnable answer to "where is the recoverable revenue," delivered fast enough to act on this quarter rather than next.

To make the method concrete, here is a composite worked example based on the pattern we see repeatedly in mid-market B2B SaaS portals with roughly $8M in trailing twelve-month revenue, a team of eleven account executives, and no formal revenue audit in the past eighteen months.

Summing the four dollar-denominated categories gives a recoverable estimate of roughly $1.2M against $8M in trailing revenue — about 15%. That figure sat in the middle of the 8-22% range we noted earlier is typical for a portal of this profile and audit gap. The two non-dollar categories (data integrity, follow-up discipline) aren't summed into the headline figure, but they explain a meaningful share of why the first four categories exist in the first place: 47 SLA-breached leads this quarter alone is a leading indicator that next quarter's dormancy and win-back numbers will grow if the underlying process isn't fixed.

This is the structure worth replicating: a small number of dollar-denominated, conservatively-adjusted category totals, plus a couple of leading-indicator counts that explain the trend rather than inflate the headline.

An audit that ends as a PDF changes nothing. The value is entirely in what happens in the thirty days after it lands. A recovery plan that has held up well in practice looks like this.

A handful of recurring errors are enough to undermine an otherwise well-run audit, either by inflating the headline number past credibility or by making the findings impossible to act on.

• Summing face-value deal amounts without any conversion-rate adjustment, producing a number that collapses under the first skeptical question in a leadership review.
• Double-counting across categories — an account that's both dormant and has an overdue renewal should be resolved to one category with a note, not counted twice in the total.
• Ignoring deal ownership changes, so findings get sent to a hubspot_owner_id no longer at the company, and nobody notices for weeks.
• Treating the audit as a one-off rather than building it as saved, reusable views, which means next quarter's version starts from zero rather than from a comparable baseline.
• Running the audit without involving the reps who own the accounts, producing a list that gets quietly deprioritised because the people expected to act on it had no input into its accuracy.
• Using a single blanket conversion rate across all deal stages or account segments, rather than the stage- and segment-specific rates that make the sizing defensible.

A revenue audit is not a once-a-year event; the categories it covers accumulate continuously, and a portal that goes untouched for twelve months between audits will surface a materially larger — and less recoverable — backlog than one reviewed quarterly.

The practical shortcut most revenue leaders land on is a full six-category audit each quarter, with the pipeline and renewals categories checked monthly in between given how quickly they move. Because the saved views built in the method above are reusable, a quarterly re-run is a few hours of work rather than the days it took to build the first time — and if it's run through an automated scan instead, the marginal cost of re-running it each quarter is close to zero.