Software Growth

Pipeline coverage

Pipeline coverage is the value of your open sales pipeline divided by the revenue target for the period, showing whether you have enough deals to hit it.

Pipeline coverage tells you how many dollars of open opportunities you have for every dollar you need to close. If you need $100,000 of new business this quarter and you have $300,000 of qualified deals in the pipeline, your coverage is 3x. The ratio is a forecast check, taken early enough that you can still do something about a gap.

For a founder who sells, it answers a simple worry: will I hit the number, or do I need to prospect harder this month? Most deals are lost long before the quarter ends, because the pipeline was thin when it started.

How to calculate pipeline coverage

Use the same unit on both sides, such as new annual recurring revenue, and only count qualified opportunities with a close date inside the period. Early-stage deals that will not close this quarter belong in next quarter's pipeline.

Example: your target is $120,000 of new ARR this quarter. You have 14 open deals worth $360,000 in total, all with expected close dates inside the quarter. Coverage is 360,000 / 120,000 = 3.0x.

Why "3x" is a rule of thumb, not a law

The popular 3x rule only works if you win about one deal in three. The coverage you need is really the inverse of your win rate:

At a 25% win rate you need 4x. At 20% you need 5x. At 50% you need 2x. In our example, a 25% win rate means you need $480,000 of pipeline to expect $120,000 of closed revenue, so $360,000 leaves you $120,000 short, even though 3x looks fine.

Sales consultant Jason Jordan makes this case in a Salesforce article on pipeline coverage. He argues the 3x rule only fits a team with a 33% win rate and a one-year sales cycle, and that a seller who wins 10% of deals needs about 10x while one who wins half needs 2x. He suggests computing coverage from win rate and sales cycle length instead of copying a universal multiplier. The Salesforce piece includes a formula that adjusts for cycle length. See the article for it.

What to watch

  • Quality over quantity. Ten stale deals are not coverage. Remove anything with no activity in the last 30 days.
  • Timing. Pipeline created too late cannot close. If your sales cycle is 60 days, the deals must exist at least 60 days before the period ends. Check coverage at the start of the period and again at midpoint.
  • Stage weighting. Some teams multiply each deal by its stage probability instead. It is more accurate but needs a clean CRM.
  • Deal concentration. One $200,000 deal is a gamble, however good the ratio looks.

Leading indicators

Coverage is a snapshot. If you want to know months ahead whether it will be healthy, watch how many qualified leads you add each month. Jason Lemkin's lead velocity rate measures this, and sales velocity shows how fast the pipeline turns into revenue.

For small SaaS

If you close a handful of deals a month, track coverage in a spreadsheet. List deals, amount, stage and expected close date, then divide. With few deals the win rate is noisy, so use 12 months of history and round up. If your product is fully self-serve, coverage does not apply, and you should watch trial signups and conversion instead.

Sources

Back to the SaaS glossary