Business

Sales Pipeline Calculator

Size the pipeline a revenue target actually requires, weight it by stage probability, and see why the universal three-times coverage rule is really just a claim about your win rate.

Sales Pipeline Calculator

Results recalculate instantly on every keystroke. Nothing you type is transmitted.

Target And Conversion
$
%
×
Pipeline By Stage
$
$
$
$
$
Pipeline Required
The pipeline value a target genuinely requires, given how often you win
Coverage That Implies
What Your Coverage Ratio Assumes
Reconciling The Two
Raw Pipeline You Hold
Probability-Weighted Pipeline
Weighted As A Share Of Raw
Gap To Target
Raw Pipeline Needed At This Mix
Coverage You Actually Hold
How To Read This

What this result does not account for

  • Stage weightings are conventional defaults, not your own historical conversion rates.
  • Does not account for sales cycle length, which determines when pipeline must exist.
  • Treats all opportunities as equally likely within a stage.
Zero-Server Execution Updated 11 Aug 2026 Reviewed by Imran S. Qureshi, CFA IEEE-754 Double Precision

In short: A $1,600,000 target at a 50.00% win rate requires $3,200,000 of pipeline — 2.00× coverage, not the conventional 3.00×. Applying the three-times rule would demand $4,800,000, over-building by $1,600,000.

Formula

Pipeline required = Target ÷ Win rate
Required coverage = 1 ÷ Win rate
Weighted pipeline = Σ (Stage value × Stage probability)

Coverage is not an independent safety factor. It is the reciprocal of the win rate, which means every coverage rule of thumb is a hidden assumption about conversion.

Worked Example

  1. Divide the target by the win rate. $1,600,000 ÷ 50.00% is $3,200,000 of pipeline required. This is the only calculation that matters, and it needs no rule of thumb.
  2. Convert that to coverage. $3,200,000 against a $1,600,000 target is 2.00× — which is simply 1 ÷ 50.00%.
  3. Test the conventional rule. A 3.00× rule implies a 33.33% win rate. At 50% it demands $4,800,000 and over-builds by $1,600,000.
  4. Weight the pipeline you hold. $3,000,000 of raw pipeline weights to $1,154,000 — only 38.47% survives, because most of it sits in early stages.
  5. Read the real gap. Weighted pipeline is $446,000 short of target, and reaching it at this stage mix would need $4,159,445.41 of raw pipeline.

Three-times coverage is the most repeated rule in sales management and it is almost never examined. Required pipeline is target divided by win rate, so coverage is the reciprocal of the win rate and nothing more: 3× is correct only at a 33.33% win rate. This company wins 50% of what it quotes, so its correct coverage is 2.00×, and applying the conventional rule would demand $4,800,000 against a genuine requirement of $3,200,000. That surplus is not free insurance — it is $1,600,000 of opportunities that sales teams must source, qualify and maintain in a system, consuming exactly the selling time the target actually needs. The rule is worse than useless when the win rate is known, and the win rate is always knowable.

Strengths & Limits Of This Model

Where this engine is strong

  • Computes the requirement from the win rate rather than from a rule of thumb.
  • Exposes the win rate that any coverage assumption implicitly claims.
  • Reports weighted and raw pipeline separately with the ratio between them.

Where it stops

  • Cannot model deal aging, which is often more predictive than stage.
  • A single win rate cannot represent multiple products or segments.

Risk & accuracy notice. Coverage rules inherited without examination are the most common cause of both missed targets and wasted selling effort. A rule that is wrong in the conservative direction is not safe — it consumes the capacity that would otherwise have been spent closing.

Practical Use Cases

Setting a pipeline target for a sales team

Use target divided by win rate, then state the coverage that implies. Never start from a coverage rule and work backwards.

Diagnosing a pipeline that looks large but forecasts poorly

A low weighted-to-raw ratio means deals are stuck early. That is a velocity problem, not a volume one, and adding opportunities will not fix it.

Challenging an inherited coverage assumption

Compute the win rate the rule implies and compare it to reality. Measure the real one with the Quote To Close Calculator.

Working back to lead requirements

Pipeline requirements convert into lead requirements through the funnel. Continue with the Lead Conversion Rate Calculator.

Methodology & Editorial Standards

Required pipeline is the revenue target divided by the win rate, and every other formulation is a restatement of that identity. Coverage ratios are the reciprocal of the win rate, which means the conventional three-times rule is an implicit claim that the business wins 33.33% of what it pursues; where the actual win rate differs, the rule either over-builds pipeline, consuming selling time on opportunities the target does not require, or under-builds it and guarantees a miss. The engine therefore computes the requirement directly, states the coverage it implies, and separately reports the win rate that the user's own coverage assumption embeds, so the contradiction is visible rather than inherited. Pipeline held is assessed twice: as a raw total, and probability-weighted using conventional stage weightings of ten percent at discovery, twenty-five at demonstration, fifty at proposal, seventy-five at negotiation and ninety at verbal commitment. The ratio between weighted and raw value is diagnostic in itself, because a low figure indicates a pipeline concentrated in early stages — a timing and velocity problem that adding further opportunities cannot solve within the period. The engine implements the standard published formula for this calculation. Inputs are validated for domain and sign before evaluation, and any undefined case returns an em-dash rather than a spurious value.

Computation runs in IEEE-754 double precision at full internal precision; rounding to two decimal places occurs strictly at the display layer, so no cumulative drift enters the result. All monetary outputs use accounting presentation — grouped thousands, two decimals, negatives in parentheses — so figures can be transcribed directly into a model or working paper. Division-by-zero and out-of-domain inputs return an em-dash rather than a misleading number.

This engine was reconciled against an independent reference implementation and hand-verified for the worked example above before release. Our full five-stage review process is published on the About Us page.

Imran S. Qureshi, CFA Head of Quantitative Modelling · ApexConverter

Corporate finance, unit economics and valuation across growth and mature businesses. Last reviewed: 11 August 2026.

Disclaimer. This calculator is provided for informational and modelling purposes only and does not constitute financial, tax, legal, medical, or engineering advice. Verify all figures with a qualified professional before acting on them.


Sales Pipeline Calculator — 20 Expert FAQs

20 analyst-written answers to the questions practitioners actually ask — optimised for voice and answer-engine retrieval.

How much pipeline do I need?

Target divided by win rate. Here $1,600,000 at 50.00% requires $3,200,000, which is 2.00× coverage.

Is three times coverage the right rule?

Only at a 33.33% win rate. Coverage is the reciprocal of the win rate, so the rule is a hidden assumption about conversion.

What does over-building pipeline cost?

Selling time. Here the 3× rule demands $1,600,000 more than needed, all of which must be sourced, qualified and maintained.

What is weighted pipeline?

Each stage multiplied by its probability. Here $3,000,000 raw weights to $1,154,000, or 38.47%.

What does a low weighted-to-raw ratio mean?

The pipeline is concentrated in early stages. That is a velocity problem, and adding opportunities will not close the gap in time.

Should I use raw or weighted pipeline for forecasting?

Weighted for forecasting, raw for capacity planning. They answer different questions and should not be substituted.

What stage weights should I use?

Ten, twenty-five, fifty, seventy-five and ninety percent are conventional, but the right weights are your own historical conversion by stage.

How does win rate affect required pipeline?

Inversely and powerfully. Doubling the win rate halves the pipeline requirement, which is why win rate work compounds with pipeline work.

Does the sales cycle change the requirement?

Yes. The pipeline must exist far enough in advance to close within the period, so a long cycle requires the pipeline earlier, not larger.

What coverage should I actually hold?

One divided by your win rate, plus a margin for forecast error. Starting from a rule of thumb inverts the logic.

Why is my pipeline large but my forecast weak?

Because value sits in early stages with low probability. Check the weighted-to-raw ratio before adding opportunities.

Should verbal commitments be counted at 100%?

No. Ninety percent is conventional, because verbal commitments do fall through and counting them fully removes all forecast discipline.

How often should pipeline be reviewed?

Weekly for movement, monthly for coverage. Stage aging matters as much as value — deals that stop moving rarely close.

Can I improve coverage without more opportunities?

Yes, by moving existing deals forward. Progressing stage mix raises weighted pipeline without sourcing anything new.

Does a bigger pipeline always mean more revenue?

No. Beyond the requirement, additional pipeline consumes qualification time without improving the outcome.

How do I set pipeline targets for a new team?

Use the closest comparable win rate available, then correct it once real data exists. An inherited coverage rule is the worst starting point.

Is this sales pipeline calculator free to use?

Yes. It is free, requires no account, and has no usage limits. ApexConverter is funded by contextual advertising, never by selling user data.

Is my data sent to a server?

No. The engine runs as Vanilla JavaScript inside your browser under our Zero-Server Client-Side Execution model. Your figures are computed locally and are never transmitted, logged, or stored.

How accurate is this calculator?

It applies the standard closed-form formula in IEEE-754 double precision, rounding only at the display layer. The engine is reconciled against an independent reference implementation before release.

Does it work on mobile?

Yes. The interface is mobile-first with numeric keypad hints and is tested down to a 320-pixel viewport with no horizontal scrolling.

Related Business Engines