Pipeline coverage by segment produces one coverage ratio per segment, each measured against the win rate that segment actually delivers. A single company-wide multiple describes an average customer nobody sells to. Segment coverage describes the books the team works every day.
Each segment sets its own requirement
Required coverage is target divided by win rate. Nothing else determines it.
| Segment | Win rate | Required coverage | Pipeline needed on a $2M segment target |
|---|---|---|---|
| Enterprise | 18% | 5.6x | $11.2M |
| Mid-market | 26% | 3.8x | $7.6M |
| Velocity | 38% | 2.6x | $5.2M |
The company ratio hides the starved segment
Across ORM's customer base, coverage ratios run from 1.4x to 5x, with most companies near 3.5x. That spread exists between companies, and a comparable spread usually exists inside a single company between its segments.
Dollar-weighting causes the concealment. Enterprise deals carry the largest amounts, so the enterprise book dominates the company ratio. A mid-market team running at 2.0x against a 3.8x requirement contributes so few pipeline dollars that the company figure barely moves. Leadership reads a healthy number and the miss arrives anyway, which is one reason the 3x pipeline coverage rule is wrong.
Build the ratio where the win rate is measured
Segment the model at the level your win rate holds up statistically. Deal size band and sales motion separate win rates more sharply than geography or industry, so start there. If a segment produces too few closed deals per quarter to compute a stable rate, roll it into a larger group rather than publishing a ratio built on four data points.
Recompute the rates every quarter. Market conditions move them. A new competitor entering a segment compresses average deal size and pushes win rates down, and the effect compounds as win rates fall, so a few points costs far more coverage in enterprise than in velocity. Coverage requirements set once a year drift away from the business they describe. The metric itself is covered at pipeline coverage, and the segment view feeds straight into sales forecasting.
Frequently Asked Questions
Why does one coverage multiple fail across segments?
Required coverage is set by win rate, and win rates differ by segment. A segment converting at 35% needs about 2.9x. A segment converting at 15% needs about 6.7x. One number applied to both understates the requirement for one and overstates it for the other.
How do you calculate coverage for a single segment?
Divide that segment's target by its own trailing win rate to get required pipeline, then divide the segment's open pipeline by its target to get actual coverage. Compare the two. Use trailing four quarters so the rate reflects current conditions.
What segmentation should a coverage model use?
Whatever level your win rate is measured at reliably. Deal size band and sales motion separate win rates most sharply. Geography and industry usually matter less unless the sales process itself differs.
Can total coverage look healthy while a segment is starved?
Yes, and it is the common case. A large enterprise book carrying most of the pipeline dollars pulls the company ratio up while a mid-market team runs a full turn short. The company number never shows it.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like pipeline coverage by segment into prescriptive action for your team.
Schedule a Demo