What it measures
Required pipeline is the amount of eligible open pipeline, unweighted, that you need to cover a remaining sales goal if pipeline converts at your expected value-weighted close rate. It divides the gap still to be booked by the share of pipeline value that historically turns into won deals. Sales leaders, founders and representatives use it when planning a quarter or a territory, to check whether current pipeline is enough and how much new pipeline prospecting must create.
Explain this formula
Divide the remaining revenue goal by the value-weighted close rate expressed as a fraction (25 % counts as 0.25). The result is the unweighted pipeline amount which, multiplied by that rate, would produce exactly the remaining goal. It is a currency amount and is always larger than the goal unless the close rate is 100 %.
If you enter an average deal value, the calculator also divides the required pipeline by it and rounds up to a whole number: the number of opportunities of typical size you would need. Rounding up is deliberate, because 33.3 opportunities in practice means 34.
A close rate of zero gives no finite answer: no amount of pipeline converts into bookings at 0 %. The rate must therefore be greater than zero, and it should be the value-weighted rate — won value divided by the value of won and lost deals — rather than a simple count of deals.
What each term means
- Remaining revenue goal
- Additional booked value needed to reach the period goal.
- Where to find it: The target for the period minus the booked sales already credited, using the same definition as the target (usually booked contract value, excluding taxes). Do not include deals already won.
- Expected value-weighted close rate
- Share of pipeline currency historically converted into won bookings, not merely the count win rate.
- Where to find it: Won value ÷ (won value + lost value) for deals of the same segment, over a recent and comparable period, from a CRM closed-deals report. Enter 25 for 25 %. Use the rate of deals at the stage your pipeline starts counting from.
- Average deal value
- Typical monetary value per won or qualified deal in the defined segment.
- Where to find it: Optional. The average booked value of won deals in the same segment, in the same currency. Leave it empty if you only need the pipeline amount.
- Required unweighted pipeline
- Remaining goal ÷ value-weighted close rate.
- Opportunities needed
- Required pipeline ÷ average deal value, rounded up.
Worked example
Hypothetical example: a team still needs 100,000 of bookings this quarter, converts 25 % of its pipeline value into won deals and has an average deal of 12,000.
- Required unweighted pipeline100,000 ÷ 25% = 400,000
Required unweighted pipeline = 400,000
100,000 ÷ 0.25 = 400,000 of unweighted pipeline required; 400,000 ÷ 12,000 = 33.33, rounded up to 34 opportunities. If the close rate were 20 % instead of 25 %, the requirement would rise to 500,000, or 42 opportunities of the same size (41.67 rounded up). The relationship is not linear: each point of close rate matters more when the rate is low.
Hypothetical numbers, used to show the calculation. Not real company data.
When and why to use it
Use the calculator at the start of a period and at each pipeline review, once you know how much is left to book. Comparing the result with the eligible open pipeline you actually have shows whether the gap is a conversion problem, a pipeline creation problem, or both.
It is also a planning tool for prospecting. Working backwards from required opportunities, the funnel conversion and prospecting activity calculators show how many meetings and first contacts the plan implies, given your own stage rates.
Finally, it makes a target discussion more concrete. If the required pipeline is several times what the team has ever generated in a quarter, the useful conversation is about the goal, the segment or the close rate assumption, not about effort alone.
The hidden assumption behind pipeline coverage
Pipeline coverage targets such as “three times the quota” are a close rate in disguise. Requiring three times the goal assumes that about a third of the pipeline value will turn into bookings. This calculator makes that assumption explicit: you enter the close rate, and the required multiple follows from it (at 25 % the requirement is four times the goal).
That assumption only holds if the rate and the pipeline describe the same thing. A rate measured on deals that reached a late stage does not apply to pipeline that includes early, barely qualified opportunities. A rate calculated by number of deals overstates conversion when large deals are lost more often than small ones; that is why the value-weighted rate is the right input.
Time is the other hidden factor. Required pipeline says how much value must be in play, not when it will close. A deal created this week with a 90-day cycle cannot help a quarter that ends in 30 days. When you compare the result with your open pipeline, count only deals whose expected close dates fall inside the period, and use the revenue forecast calculator to see what that pipeline is likely to produce.
How to read and improve the result
The result is unweighted: compare it with the plain sum of eligible open deal amounts, not with a weighted or forecast figure, otherwise you would apply the close rate twice.
A higher close rate lowers the requirement, and the effect is strongest when the rate is low. The chart shows how steeply the curve rises as the rate falls towards 5 %: at 5 % the requirement is 20 times the goal, at 10 % ten times, at 25 % four times. That is why small errors in a low close rate produce large errors in required pipeline.
If you already have more eligible pipeline than required, the gap is not volume; check timing and deal quality. If you have less, the difference is the new pipeline that must be created and qualified in time to close.
Practical levers
- Measure the close rate by value, by segment and from the same pipeline stage you count from.
- Count only open deals that can realistically close within the period when you compare with the requirement.
- Improve qualification so that pipeline entering the count converts closer to the rate you plan with.
- Start pipeline creation early enough to cover the typical sales cycle before the period ends.
Common mistakes
- Comparing the required unweighted pipeline with a weighted pipeline total.
- Using a count-based win rate when deal sizes vary a lot.
- Including deals that are already won in the remaining goal or in the open pipeline.
- Ignoring time to close, so that late-created pipeline appears to cover the period.
- Applying a late-stage close rate to a pipeline that includes early-stage opportunities.
Scenario comparison
The scenarios move the close rate by ±5 percentage points, the remaining goal by ±10 % (a higher goal is the conservative case) and the average deal value by ±10 %. They are illustrative ranges, not forecasts.
Look first at the close rate scenario: because the rate is in the denominator, its effect is usually the largest, which is a reason to measure it carefully before committing to a pipeline creation plan.
Methodology and limitations
The calculation assumes that pipeline amount multiplied by the close rate predicts realized bookings. In practice amounts change during negotiation and some deals slip to a later period.
It uses one average rate for all deals. A pipeline mixing segments, stages or deal sizes with different conversion should be split and calculated separately.
It gives no information about timing or risk concentration. A requirement covered by one very large deal is much less secure than the same amount spread over many deals.
Frequently asked questions
How do I calculate required pipeline?
Required unweighted pipeline = remaining revenue goal ÷ value-weighted close rate. With 100,000 left to book and a 25 % close rate, you need 400,000 of eligible open pipeline.
How many opportunities do I need?
Divide the required pipeline by your average deal value and round up. In the example, 400,000 ÷ 12,000 = 33.33, so 34 opportunities.
Why use a value-weighted close rate rather than a win rate by count?
Because the requirement is a currency amount. If large deals are lost more often than small ones, the share of deals won is higher than the share of value won, and a count-based rate would understate the pipeline you need.
How does this relate to pipeline coverage?
Coverage is open pipeline divided by the remaining goal. The required coverage is simply 1 ÷ close rate: at 25 %, you need coverage of 4. The pipeline coverage calculator then tells you how much you actually have.
What if my close rate is zero?
Then no finite amount of pipeline can cover the goal, and the calculator does not return a result. Use a rate measured on enough closed deals, or calculate it on a broader but comparable segment.
Does the result tell me when the deals will close?
No. It says how much value must be in play, not when it will be booked. Combine it with your sales cycle and expected close dates to check that the pipeline can close within the period.
Sources
- Salesforce — Sales pipeline
- Salesforce Help — Revenue Insights team metrics (coverage, win rate, cycle)
- HubSpot — Win rate
Last reviewed:
Related calculators
- Sales Pipeline Coverage CalculatorSee how many times your open pipeline covers the revenue still missing from this period’s quota, and how much pipeline you lack if it does not cover it even once.
- Sales Win Rate CalculatorFind out what share of the opportunities that reached a final decision your team actually won, using only closed outcomes from one cohort.
- Average Deal Size CalculatorFind the average value of your won deals, and check with the median whether one large contract is distorting the picture.
- Sales Prospecting Activity CalculatorWork back from the number of deals you want to win to the number of prospects you need to contact, and see how each conversion step multiplies the effort.