The coverage number on a HubSpot dashboard is almost never the number you think you are looking at. The default report divides all open pipeline by the quarterly target, which counts deals nobody has touched in two months, deals a rep dragged into negotiation before the buyer agreed on anything, and the same logo sitting in the pipeline three times under three owners. Every one of those inflates coverage without adding a dollar of expected revenue.
This page is the HubSpot build: which deals to exclude and how to exclude them with properties rather than by hand, how to segment the target by sales motion, and how to wire the whole thing into a dashboard that holds up in a forecast call.
Updated September 2026. This version hands the general coverage question to the page that owns it, removes several internal figures the earlier version published without measurement, and focuses on the HubSpot build.
The target: one divided by your win rate, by segment
Coverage is the inverse of the win rate you actually convert at, so 3x is only right for a team closing a third of its pipeline. Clari's guidance puts enterprise teams converting between 15% and 25% at 4x to 7x coverage, and high velocity teams closing more than half their qualified deals a long way below that (Clari).
Where the 3x rule came from, why nobody can cite a source for it, and what the current published win rate benchmarks are is covered in full on the pipeline coverage ratio page. The short version for this build: do not inherit a number, derive it, and derive it per segment rather than for the company.
The formula that actually works
The right way to set coverage is one divided by your historical win rate, with a buffer for forecast slippage.
Required coverage = (1 / win rate) x slip factor
Slip factor is your hedge for deals that push out of the quarter, and it is not a benchmark you can borrow. Compute it from your own history: take the share of deals forecast to close in a quarter that actually closed in that quarter, and invert it. If 89% closed in period and 11% slipped, your slip factor is 1.12.
So a team with a 22% win rate and 15% slip needs coverage of:
(1 / 0.22) x 1.15 = 5.2x
That is the floor, not the ceiling. If you are running heads-down on hitting plan, build to 5.5x and run a clean forecast. If you are entering a new segment or building a fresh territory, push to 6x because your conversion data is unreliable.
If you are already inside a quarter and the number on the dashboard is below this, you do not have a forecast problem. You have a sourcing problem and you have less time to fix it than you think.
Why your reported number is probably wrong
The bigger problem in most CRMs is not the formula. It is the pipeline you are dividing.
In the portals we audit, the reported pipeline shrinks once the noise comes out. We are not going to put a percentage on that, because we have never measured it across a defined sample and a number invented for effect is exactly what this page is arguing against. Measure it in your own portal instead, with the four-step query at the end of this page.
Here is what is in there that should not be:
Stale deals that should be closed-lost. Deals with no activity in 60 days are not pipeline. They are wishful thinking, and they are usually the single largest block of counted-but-dead value in a portal.
Deals at the wrong stage. Reps move deals to "Negotiation" because their manager asked for a forecast update, not because the buyer agreed on price. Stages must be milestone-based and verifiable, otherwise the entire funnel is fiction.
Unqualified opportunities counted as pipeline. I have seen teams put MQLs and SQLs in the pipeline number to make coverage look better. If the deal has not been qualified by a real conversation, it is not pipeline.
Duplicates and zombie accounts. When a CRM has been running for three years without governance, you find the same logo as five different deals with five different owners. They cannot all close.
The fix is not a one-time cleanup. It is a weekly hygiene cadence and a stage definition document everybody signs off on. If you want the deeper version of this, I covered it in the pipeline ghost deals post and the HubSpot deal stages post.
Coverage is a ratio. The denominator is real. The numerator is half a lie at most companies.
Before you debate whether 3x or 5x is right, run the audit. If a meaningful share of your open pipeline has not had activity in 60 days, fix that first. The ratio will tell you something useful afterwards. Right now it is telling you a story about CRM hygiene, not pipeline health.
Segmenting coverage so the math is honest
A single coverage target across a sales org is the second mistake. The first is using 3x. The second is averaging.
Every meaningful sales motion has a different conversion rate, and a single blended target will overstate coverage in the easy segment and understate it in the hard one. You will hire badly, forecast badly, and fire reps for the wrong reason.
Here is how I segment for most B2B SaaS teams:
If you have a hybrid motion, run the math by segment, then calculate a weighted blended target. Do not roll up to a single number for the whole company unless you also report by segment.
The failure mode is easy to see once you write it out. An SMB segment at 4.2x and an enterprise segment at 2.8x blend to 3.5x, which reads as comfortably above target. The enterprise segment is roughly half covered against the target its own win rate demands, and the only thing standing between that and a missed quarter is an SMB deal pulling forward. Without a segment breakdown, that fragility is invisible in the number the board sees.
What to track besides coverage
Coverage on its own is a snapshot. To run a quarter you need three more numbers next to it.
Pipeline velocity. How fast deals are moving through stages compared to a quarter ago. Coverage can look fine while velocity is collapsing. The deals are sitting, not moving, and the cliff is two weeks away.
Stage conversion rates by quarter. Look at how the percentage of deals that move from each stage to the next has changed. If "demo to proposal" used to be 60% and is now 40%, that is your problem. The pipeline at the top is fine. The middle is where things are dying.
Pipeline aging. What share of your open pipeline has been open longer than one full sales cycle. In a 90-day cycle business, anything past 90 days is half dead. Whatever that share is in your portal, your real coverage is smaller than the dashboard claims by roughly the same amount, so measure it rather than assuming a benchmark.
Sourced pipeline by channel. If outbound is dropping from 35% of new pipeline to 18% over two quarters, your coverage will collapse next quarter even if it looks fine today. Coverage is a lagging indicator. Sourcing trends are the leading one.
How to build this in HubSpot
The reporting most teams set up looks at total open pipeline divided by quarterly target. That is the wrong number to put on a dashboard.
Here is how I build it in HubSpot for a Series A or B portal:
1. Build a "real pipeline" calculated property. A boolean that flags a deal as real pipeline only if it has had activity in the last 30 days, is past the qualification stage, and has a close date in the current or next quarter. Use this to filter your coverage report.
2. Create a segment property. A custom property on the deal record for segment (SMB, mid-market, enterprise, new territory). Auto-populate it based on the company's employee count and ARR fit, with a manual override for edge cases.
3. Build a "win rate by segment" report. Last four quarters of closed deals, grouped by segment, with closed-won divided by closed-won plus closed-lost. This is the input to your target.
4. Build a coverage dashboard. One tile per segment, plus a blended view. Each tile shows current coverage, target coverage, and the gap in dollars and deal count. Alert thresholds at 90% and 80% of target.
5. Set up automation for stage hygiene. Workflow that pings the deal owner if a deal has had no activity in 21 days and reassigns it to the manager if there is no activity at 45 days. Stale deals destroy the denominator.
The whole setup takes about a day if you have already cleaned up your stages and another two if you have not. If your portal has 200 workflows and 30 deal stages, you have a hygiene project to do first. I covered the workflow side in the HubSpot workflows post and the stage architecture in the deal stages post.
For teams running Clay or n8n for enrichment, you can also feed the win-rate calculation an external signal: deals that match your highest-LTV ICP segments get a separate coverage track. That is more useful for account-based motions than a single blended number.
The three mistakes that break the report
Reporting on dollar value instead of weighted value. A $2M deal at "demo scheduled" is not $2M of pipeline. It is $2M times your own historical conversion from that stage to closed won, which in most portals is a small fraction. Pull the rate from your own closed deals rather than borrowing one, then weight the column before you divide.
Reporting on a single point in time. Coverage on the first day of the quarter is a different metric than coverage in week nine, because by week nine much of the target is already booked and much of the pipeline already resolved. Look at the trend, and compare the pipeline still in play against the revenue still to close rather than against the original target.
Treating renewal pipeline as new pipeline. Renewal motions convert at a far higher rate than new business, where the published 2025 benchmark average is 19% (Ebsta and Pavilion). Blend them and coverage looks healthy because the renewals are carrying the math. Track them apart.
What to do when the clean number looks bad
If the audit leaves you at 2.4x against a 5x target, you have roughly half the pipeline the math requires, and there is no sourcing plan that closes that gap inside the same quarter. The honest move is to say so early and reset expectations while there is still a quarter left to fix.
The mistake in this situation is letting hope carry the forecast. "We will pull more deals in" and "we have a few wildcards" buy one more quarter and cost two. One real conversation in month one is much cheaper than two missed quarters and a CFO who stops trusting the dashboard.
The fix is a quarter or two of discipline: clean the pipeline, segment the targets, get sourcing back to where it needs to be, and rebuild the forecast from measured numbers.
Share of B2B sellers who missed quota in 2025, up from 69% the year before, across 655,000 opportunities and $48B of pipeline (Ebsta and Pavilion, 2025 GTM Benchmarks). A coverage number that reads healthy in that market deserves a second look.
A practical first step for next Monday
If you do nothing else, run this query in your CRM this week:
- List every open deal where the close date is this quarter or next.
- Filter to deals with no activity in the last 30 days.
- Add up the dollar value.
- Divide by your reported pipeline.
Whatever percentage comes back is the share of your reported coverage that is decoration. The fix is not more sourcing. The fix is hygiene first, then sourcing.
After that, calculate your win rate by segment from the last four quarters of closed deals. Compare it to the assumed win rate baked into your coverage target. If they do not match, that is your work for the rest of the quarter.
In our experience the audit always finds a gap between the dashboard and reality. The useful question is how big it is in your portal and how fast it can be closed, and both of those are measurable in an afternoon.
Want a second pair of eyes on your pipeline math?
Book a free 30-minute audit and we will show you the three coverage gaps we would fix first in your HubSpot portal.
Book an audit →FAQ
What is a healthy pipeline coverage ratio for B2B SaaS?
It depends on your win rate. The formula is one divided by your historical win rate, multiplied by a slip factor measured from your own in-period close history. A team converting between 18% and 25% lands somewhere between 4x and 5.5x before slip. The 3x rule only works at a 33% win rate, well above the 19% average in the 2025 Ebsta and Pavilion benchmark. The full account of where 3x came from is on the pipeline coverage ratio page.
How is pipeline coverage different from pipeline velocity?
Coverage is a snapshot of how much pipeline you have versus your target. Velocity is how fast deals are moving through the funnel. You can have great coverage and terrible velocity at the same time. The pipeline is sitting still and will not close in time. Both numbers are needed for an honest forecast.
Should I include unqualified leads in pipeline coverage?
No. Pipeline coverage only works as a metric when the numerator is qualified, recently active deals with an in-period close date. Including MQLs, SQLs, or deals nobody has touched in two months inflates the ratio and buys false confidence. Measure the share in your own portal with the four-step query above rather than assuming a benchmark.
How often should I review pipeline coverage?
Weekly, with a deeper review at the start of each month. Coverage at the start of the quarter is misleading because the early-quarter number is heavily influenced by what got pushed out of the prior quarter. Look at the trend over four to six weeks, not a single point in time.
Do I need different coverage targets for SMB and enterprise?
Yes. Win rates move with deal size: the 2025 Ebsta and Pavilion benchmark reports roughly 35% to 45% on deals under $50,000 and 15% to 25% above $100,000 (Pavilion). Inverted, that is a target near 2x to 3x for a small-deal motion and 4x to 7x for enterprise, which matches Clari's published range. A single blended target hides the risk in whichever segment is harder to close, because the easy segment carries the average.