Optimized Sales Optimized Marketing Target Accounts For CROs For CFOs For CMOs Blog News Glossary Compare Tools About Schedule a Demo
Pipeline Analytics

How Much Pipeline Do You Need to Hit Quota?

Pete Furseth 5 min read
pipeline coveragequota attainmentsales planning
How Much Pipeline Do You Need to Hit Quota?
Home/ Blog/ How Much Pipeline Do You Need to Hit Quota?

The question usually gets answered with a rule someone heard at a previous company. Three times quota. Four if you are nervous. The rule is portable, which is why it spreads, and it is disconnected from the mechanics of any specific business, which is why it fails.

The number you need is calculable from data you already have. Here is the calculation, along with the three adjustments that separate a working target from a slide.

How much pipeline do you need to hit quota?

Quota divided by your closed-won win rate, adjusted for the share of pipeline that carries a credible in-quarter close date.

Start with the base calculation. A $2M quota against a 25 percent win rate requires $8M of pipeline, or 4x. The same quota against a 15 percent win rate requires $13.3M, or 6.7x. Win rate sets the multiple. Nothing else does at this stage.

This is why a single company-wide coverage number breaks down the moment segments differ. ORM's customers range from 1.4x to 5x coverage, with most sitting around 3.5x, and every one of those figures is defensible for the business it came from.

Put this to work on your numbers
Run your own numbers with the free Percent to Goal Calculator, then see how ORM builds it into a custom model.

Why is a flat 3x rule the wrong starting point?

Coverage is a ratio of two numbers, and the rule only looks at one of them.

A company can carry 4x coverage and miss badly. The pipeline can be low quality, concentrated in the wrong stage, dependent on a few large deals, inflated by stale opportunities, or built on close dates that sellers keep pushing. A company can start with thin coverage and beat the number because it has a strong in-quarter motion.

The rule also hides composition. Coverage without context makes an executive team feel informed while masking the actual risk: the coverage sits in the wrong segment, is owned by the wrong reps, is too old, comes from low-converting sources, or is priced above what those deals close at. That is the core of why the 3x rule fails as a target.

How do you calculate the number from your own data?

Run it per segment, using closed-won win rate rather than stage-weighted probability.

The table below shows the method on illustrative figures. Substitute your own quota and win rate per segment.

SegmentQuotaClosed-won win rateBase pipeline requiredBase coverage
SMB$1,200,00034%$3,530,0002.9x
Mid-market$3,000,00024%$12,500,0004.2x
Enterprise$2,400,00015%$16,000,0006.7x
Total$6,600,00021% blended$32,030,0004.9x
The blended figure at the bottom is the number most teams report. It is also the number that would let enterprise run at 3x for two quarters before anyone noticed. Report the rows, not the total.

Use closed-won rate, meaning deals won divided by deals won plus deals lost plus deals disqualified after qualification. Using a stage-weighted probability instead imports the same optimism that inflated the pipeline in the first place, which is the failure mode behind most weighted pipeline reporting.

What does close-date data change about the math?

Most of the pipeline carrying an in-quarter close date will not close in that quarter, so the base number understates what you need.

ORM's data on this is specific. Of the pipeline holding a close date inside the quarter on the first day of that quarter, roughly 20 percent closes in the quarter. That means 80 percent of the value dated for the period does not land in the period.

Close-timing curves show the same thing from a different angle. ORM groups opportunities with a machine learning model and predicts a close curve per group. Curves run from 1 to 80 weeks. Most groups carry their expectation before week 12, and very few extend past week 52. A deal dated for week 6 of the quarter that belongs to a group peaking at week 18 is dated wrong, and its contribution to coverage is fiction.

Apply the adjustment by discounting pipeline whose close date falls outside its group's expected window, rather than by inflating the multiple across the board.

How do you adjust for deal size inflation?

Reprice open pipeline at the closed-won average for its segment before calculating coverage.

A pipeline with an average opportunity value of $80,000 against closed-won deals averaging $40,000 is carrying a two-times error at the top of the calculation. Coverage computed on the inflated value looks like 4x and behaves like 2x.

The repricing is straightforward. For each segment, compute the ratio of average closed-won value to average open opportunity value over the last four quarters. Multiply open pipeline by that ratio. Compute coverage on the adjusted figure and report both numbers so the gap stays visible.

Most deals close for less than the value carried in the CRM. Planning against the CRM value guarantees a shortfall that nobody can explain at quarter end.

How much of the number can come from in-quarter creation?

Enough that a coverage target measured on day one is answering only part of the question.

A quarter is funded from three places. Carry-over deals already in the pipeline with an expected in-quarter close. In-quarter deals that do not exist yet but will be created, qualified, and closed inside the period. Pull-forward deals from future quarters, usually discounted, which leave a hole behind.

Teams over-trust visible pipeline and under-model the invisible portion. They inspect CRM records closely and barely forecast the in-quarter motion. Sizing that motion lowers the coverage requirement legitimately, because a portion of the quota is being carried by deals that were never supposed to be in the day-one number.

Measure it from history. What share of closed-won revenue in each of the last four quarters came from opportunities created inside that same quarter? Subtract that share of quota before calculating required coverage on the rest.

How do you exclude pipeline that should not count?

Remove anything with no change to stage, close date, or amount in twelve months.

ORM applies a twelve-month rule for most customers and defines meaningful activity as a change to one of those three fields. Logged calls and notes do not qualify. Under that rule, more than 10 percent of pipeline across ORM's customer base fails to clear the bar.

Excluding it changes the ratio, and the changed ratio is the true one. A pipeline reported at 3.8x with 12 percent stale is really 3.3x. The pipeline coverage you manage should be the coverage that can convert.

How often should you recalculate?

Quarterly, because every input in the calculation moves with market conditions.

Win rates drop when buyers cut spending. Deal sizes compress when a competitor enters and creates pricing pressure. Cycle lengths stretch when uncertainty slows decisions. Any of those changes the required multiple without changing anything about how the sales team works.

Recalculating win rate and average deal size each quarter, then rebuilding the coverage requirement from them, takes an hour. Running a stale multiple for a year costs a quarter.

For the short definition, see the glossary entry.

Frequently Asked Questions

How much pipeline do you need to hit quota?

Divide quota by your closed-won win rate for that segment, then adjust for the share of pipeline that carries a credible in-quarter close date. For a 25 percent win rate that starts at 4x, and the close-date adjustment usually pushes the requirement higher.

Is 3x pipeline coverage enough?

It depends on win rate, not on the rule. ORM's customers run anywhere from 1.4x to 5x coverage, with most near 3.5x. A team with a 35 percent win rate can work at under 3x, while a team at 15 percent needs well over 6x to carry the same quota.

Does pipeline coverage need to be measured per rep?

Measure it per segment first and per rep second. A team-level ratio can look healthy while one segment sits at 1.8x and another at 6x, which is the composition problem that a single number is designed to hide.

Should you count all open pipeline toward coverage?

No. Exclude opportunities with no change to stage, close date, or amount in twelve months. ORM typically finds more than 10 percent of a pipeline in that state, and counting it inflates coverage without adding any chance of revenue.

How often should you recalculate the coverage requirement?

Every quarter at minimum, because win rate, deal size, and cycle length all move with market conditions. A coverage target set two years ago is describing a business that no longer exists.

PF
Pete Furseth
ORM Technologies
Pete has built custom revenue forecast models for B2B SaaS companies for over a decade.

See how ORM turns these insights into action

ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.

Schedule a Demo