Pipeline Velocity Calculator
The formula
What the pipeline velocity tells you
Expected dollars flowing through the pipeline per day — one number that combines volume, size, skill and speed into a throughput rate.
Calculation: Velocity = (opportunities × deal size × win rate) ÷ cycle days. Enter your inputs and every substitution is shown below the result.
Reading the result
Velocity turns forecasting into arithmetic: 30 days of forward revenue is roughly the month’s expected close. Use the four levers individually when diagnosing change.
Rules of thumb: Track direction over levels — the number is company-specific by construction
Limitations and best practice
The formula assumes open opportunities are evenly aged; a pipeline stuffed with stalled deals produces flattering velocity that never closes. Segment by stage or age-bucket.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
Which lever should I pull first?
Does velocity replace coverage?
Source & methodology
Pipeline-velocity formula popularised by Steli Efti (Close.io).
Pipeline Velocity explained: formula, worked example and honest limits
This page was written for one job: turning your own inputs into a defensible figure, with the working shown. Searchers land on a Pipeline Velocity page for three reasons — to plan, to compare options, and to check that somebody else’s arithmetic is honest. This tool serves all three, and everything after the calculator explains the model instead of hiding it.
It helps to separate the mechanics from the interpretation. The mechanics are fixed: Velocity = (opportunities × deal size × win rate) ÷ cycle days. Anyone, anywhere, entering the same inputs will get the same $9,920.00. The interpretation is where experience counts: whether $9,920.00 is good, normal or alarming depends on comparisons covered below, and that is the part most articles about Pipeline Velocity never explain.
Like most useful measures, Pipeline Velocity is a summary, and summaries hide as much as they reveal. The companion outputs and the input table are here to reopen what the headline compressed.
What makes a calculation page trustworthy is that its copy is derived from its own arithmetic: here daily pipeline velocity = $9,920.00, recomputed every time a field changes, and the sensitivity section ranks the inputs that move the result — Sales cycle first, at ≈11.1 % of the headline for a ten-percent error either way in that input. Read the sections in order and you will be able to reproduce every figure by hand.
Every input in Pipeline Velocity, and what it does to the answer
Here is the complete model this tool runs — Velocity = (opportunities × deal size × win rate) ÷ cycle days — with each input explained below. If a competitor’s page gives you a different answer from the same inputs, this is the text that settles which of you is right.
Open opportunities (example value 62) is a measured number in the unit named by the label; the formula does not convert for you. This input feeds the formula directly; a defensible figure here is worth more than false precision anywhere else.
Average deal size ($) (example value 32,000) is a quantity rather than a category — precision here is cheap and worth having. Measure twice and use the unit the label asks for — length terms often scale the result geometrically.
Win rate (%) (example value 28) is a plain measured quantity — the unit shown in the label is the unit the formula expects. Rates are the most mis-transcribed input on any page like this; copy it from the document rather than retyping from memory.
Sales cycle (days) (example value 56) is a measured number in the unit named by the label; the formula does not convert for you. If the period is partial, decide whether you mean elapsed or planned time and keep that meaning across every field.
Pipeline Velocity on the example inputs: the complete substitution
Abstract formulas are hard to trust, so here is the complete substitution using the default inputs, written the way an examiner would want it. Starting figures: Open opportunities, Average deal size ($), Win rate (%), Sales cycle (days). The endpoint of that chain is $9,920.00 of daily pipeline velocity, sitting in the “≈ $297,600 of expected revenue per month at the current pipeline” band.
- Velocity = (62 × $32,000 × 28%) ÷ 56 days = $9,920/day
- Each input moves the number proportionally — the cycle lever costs nothing to pull
Velocity per month — $297,600. Read next to the headline, this is the figure that shows the shape of the trade-off.
Velocity if cycle drops to 50 days — $11,110. If your inputs change, this is usually the first companion figure to move.
Velocity if win rate rises 5 points — $11,691. This is the number experienced users quote when the headline alone would mislead.
Keep this worked example open while you enter your own figures: matching the shape of the substitution is the fastest way to spot a unit or convention mistake.
The Pipeline Velocity corridor: your result across a realistic band
Read this table as the practical error bar on the headline figure. It answers the question people actually have after seeing a single number: how wrong could this be if the main input is off by ten or twenty percent?
| Sales cycle setting | Daily pipeline velocity |
|---|---|
| 80 % of the example value | $12,400.00 |
| 90 % of the example value | $11,022.22 |
| example inputs | $9,920.00 |
| 110 % of the example value | $9,018.18 |
| 120 % of the example value | $8,266.67 |
That spread — $8,266.67 at the low end, $12,400.00 at the high — is what a careful read of Pipeline Velocity looks like: a band you can state out loud, with the reason for each edge. Reproduce it in the form above by editing Sales cycle alone; the substitution steps will follow your figures exactly.
Sensitivity: which inputs change Pipeline Velocity the most
Generic advice says “it depends on your inputs”; this section says exactly how much. Each field was perturbed by ±10 % in isolation and the daily pipeline velocity recomputed, so the ranking below is measured rather than asserted. Read it as a map of where Pipeline Velocity is fragile — drawn for the example inputs, which is the map you want when deciding what to measure carefully.
- Sales cycle +10 % → Pipeline Velocity = $9,018.18 · −10 % → $11,022.22 (the daily pipeline velocity shifts ≈11.1 %)
- Win rate: ten percent up gives $10,912.00, ten percent down gives $8,928.00 — ≈10.0 % of the daily pipeline velocity either way
- Open opportunities: ten percent up gives $10,912.00, ten percent down gives $8,928.00 — ≈10.0 % of the daily pipeline velocity either way
- Nudge Average deal size by ±10 % and Pipeline Velocity lands between $8,928.00 and $10,912.00 (sensitivity ≈10.0 %)
Sales cycle is the dominant lever here: ten percent either way moves the result by about 11.1 %, from $9,018.18 to $11,022.22. That is where a careless figure does the most damage, so check it against a source, and treat Win rate as the second priority (≈10.0 % per ten percent). The remaining fields can sit at safe defaults without materially changing the answer — knowing which is which is what separates a careful calculation from an anxious one.
Reading the result: bands, zones and thresholds
A number on its own is trivia; a number against a range is intelligence. The verdict attached to the default calculation — “≈ $297,600 of expected revenue per month at the current pipeline” — is one band on a ladder your own figure may sit somewhere else on. The sensitivity list shows how far a modest input error moves you along that ladder: for Sales cycle, ±10 % covers $9,018.18 to $11,022.22. The practical reading rules: compare against your own history before comparing against other people; treat band boundaries as zones, not walls — one point on the wrong side of a threshold rarely changes a real outcome; and when a companion output contradicts the headline, believe the pair.
Where Pipeline Velocity sits next to similar measures: this tool answers “how much is the Pipeline Velocity”, while the related calculators answer “what do I do about it”. Reading the result alone tends to over-weight a single snapshot; pairing it with the companion tools above turns the number into a decision.
The errors that quietly break a Pipeline Velocity figure
The formula assumes open opportunities are evenly aged; a pipeline stuffed with stalled deals produces flattering velocity that never closes. Segment by stage or age-bucket. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Copying a single headline number without checking the companion outputs. The tool reports Velocity per month, Velocity if cycle drops to 50 days and Velocity if win rate rises 5 points alongside the main result precisely because Pipeline Velocity in isolation misleads — the secondary columns are where outliers and trade-offs show up.
Attention is also misallocated between fields. Having measured this engine, we can say where it belongs: Sales cycle first, everything else second.
A final trap is presentation: reporting Pipeline Velocity to more decimal places than the inputs support. The tool prints what the arithmetic gives; you should quote only what your least precise field justifies.
Pipeline Velocity verification checklist
- Re-run the calculation with a ±10 % stress on the two most sensitive inputs.
- Confirm the example values are plausible for your own situation before replacing them.
- Re-verify Sales cycle against a source document — ten percent of error there moves the headline by ≈11.1 %.
- Compare the result with one independent method or published benchmark.
- Record the date and the inputs alongside the number so future-you knows what was assumed.
- Repeat the ±10 % test on the inputs that matter and see whether the decision — not just the number — still holds.
A routine for decision-grade Pipeline Velocity
The tool does the arithmetic; the routine below is what makes the arithmetic trustworthy. Five steps, a minute total — and afterwards you will know not just what the number is, but which assumption produced it.
Step 1 — collect, then type. Everything this tool asks for is listed above (open opportunities, average deal size ($), win rate (%), sales cycle (days)). Pull each figure from something you can point at — paperwork, a dashboard, a label — before touching a field. Guesswork at the input stage cannot be repaired at the interpretation stage. The fastest sanity test is to guess the answer first and see how far the calculation disagrees.
Step 2 — baseline before exploration. Get one defensible Daily pipeline velocity on screen before you start nudging numbers. Without a baseline, every variation looks interesting and none of them means anything. Write the figure down before moving on; memory flatters whichever number you saw last.
Step 3 — change one input at a time. Nudge a single field by ten percent, watch the headline and its companions move, then undo it. Two or three fields will dominate — the sensitivity table above already ranks them for this engine. If the verdict changes with a ten-percent nudge, report the nudge alongside the number.
Step 4 — stress before you commit. A decision that survives a ten-percent squeeze on its two biggest inputs needs no luck to be sound. One that does not survive is a decision about hope, not about arithmetic. When two sources disagree, it is almost never the arithmetic that differs.
Step 5 — save the story with the figure. A number without its inputs and its date is unusable within a quarter. Record $9,920.00, the assumptions behind it, and today’s date; your future self will be auditing a stranger’s arithmetic. When two sources disagree, it is almost never the arithmetic that differs.
From calculation to decision: where Pipeline Velocity earns its keep
Most Sales & Revenue disagreements are arithmetic disagreements in disguise. When Daily pipeline velocity of $9,920.00 sits on the table with its working shown, the conversation stops being about who sounds more confident and starts being about which input is wrong. Compare the calculation to the rough guess you arrived with, and ask why they differ.
The audience for this page is people who need one trustworthy number before their next decision. In professional Sales & Revenue practice the pattern is always the same — screen with Pipeline Velocity, then invest slow analysis only in whatever survives the screen. The fastest sanity test is to guess the answer first and see how far the calculation disagrees.
There is a personal-administration use people overlook: periodic self-checking. Pipeline Velocity quietly drifts as life changes — rates move, bodies change, costs compound — and re-running it a few times a year catches drift while correction is still cheap. Say the answer out loud before you save it; if it sounds wrong, the model did not change, your understanding did.
The questions that come up most about Pipeline Velocity
What affects Pipeline Velocity the most?
The short answer: Sales cycle. The longer answer is the sensitivity table on this page, where every numeric input was probed by ten percent and the daily pipeline velocity recalculated — Sales cycle moved it furthest, by roughly 11.1 % ($9,018.18 to $11,022.22).
Which matters more: win rate or sales cycle?
For Pipeline Velocity, Sales cycle wins the head-to-head (≈11.1 % against ≈10.0 % per ten-percent change). Knowing which input dominates is the difference between careful work and merely slow work.
What is a typical Pipeline Velocity?
On the worked example above Pipeline Velocity comes out at $9,920.00. Treat that as one point on a distribution rather than a norm: the bands, the companion outputs and the sensitivity ranking tell you how wide the plausible range really is.
How do I calculate Pipeline Velocity by hand?
Use the stated model — Velocity = (opportunities × deal size × win rate) ÷ cycle days — and substitute in the order the tool prints (it starts from Velocity = (62 × $32,000 × 28%) ÷ 56 days = $9,920/day). On the example inputs the hand route lands on $9,920.00, exactly what the calculator shows. A spreadsheet reproduces it in two or three cells; doing it once by hand is what makes the automated answer trustworthy.
What happens to Pipeline Velocity if sales cycle changes by 10 %?
On these inputs a ±10 % change in sales cycle takes Pipeline Velocity to $9,018.18 against the $9,920.00 example — around 11.1 % of the headline. The same test on every other field is in the sensitivity section.
Is the Pipeline Velocity result of $9,920.00 good or bad?
Neither, on its own — the label “≈ $297,600 of expected revenue per month at the current pipeline” is the band this figure falls in for the example inputs, and your own inputs will place you elsewhere on the same ladder. Judge the number against your history and your alternatives, and remember that a ten-percent error in Sales cycle alone moves it by ≈11.1 %.
How do I calculate Pipeline Velocity manually?
Write down the inputs, then follow the printed steps in order — Velocity = (opportunities × deal size × win rate) ÷ cycle days. A spreadsheet replicates it with two or three cells. The manual route is worth doing once to build intuition; after that the calculator saves time and eliminates transcription slips.
Can Pipeline Velocity be negative or empty?
Yes, and that is informative rather than broken: a negative Pipeline Velocity usually means the inputs encode an outflow or a shortfall, and the verdict band above labels exactly that situation instead of hiding it.
Which lever should I pull first?
Cycle length — it is the only denominator and shortening it does not require new spend. Next: win rate via qualification; volume and size last, since both consume budget.
Does velocity replace coverage?
No — coverage says whether the pool is big enough; velocity says how fast it drains into closed revenue. Mature teams run both on a weekly view.
Does this Pipeline Velocity tool store my numbers?
No. The entire calculation runs in your browser session; nothing entered above is transmitted or saved, which is the correct behaviour for sensitive Business & Entrepreneurship figures and the reason you can re-run this page as often as you like.
What the labels on this page mean
- Velocity per month
- $297,600 on the example inputs — a companion figure printed beside the headline of Pipeline Velocity so that no result is read in isolation.
- Velocity if cycle drops to 50 days
- $11,110 on the example inputs — a companion figure printed beside the headline of Pipeline Velocity so that no result is read in isolation.
- Velocity if win rate rises 5 points
- $11,691 for the Pipeline Velocity worked case; it sits next to the main result because it carries context the headline leaves out.
- Daily pipeline velocity
- The primary output of this tool: $9,920.00 for the default inputs, computed exactly from Velocity = (opportunities × deal size × win rate) ÷ cycle days.
- Worked example
- Every substitution in order, from the example inputs to $9,920.00 — the audit trail for the headline figure.
- Verdict band
- The interpretation attached to a result (“≈ $297,600 of expected revenue per month at the current pipeline” on these inputs), which turns a bare number into a position on a scale.
- Sensitivity (±10 %)
- How far the Pipeline Velocity moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Methodology, sources and limits
The model is published arithmetic implemented exactly as written: Velocity = (opportunities × deal size × win rate) ÷ cycle days. Source of record: Pipeline-velocity formula popularised by Steli Efti (Close.io). Where a professional version of this calculation differs, it differs in inputs and jurisdiction-specific coefficients, not in the algebra — which is why re-checking your inputs beats hunting for a second calculator.
This page is an estimation aid, not professional advice. The design rule is simple: two people entering identical figures must get identical answers. What that buys you is reproducibility — two people, two browsers, the same arithmetic, and a printed trail from inputs to result that either of them can audit.
What to do with your Pipeline Velocity next
Re-run the calculation with your own figures, stress the two most sensitive inputs by ±10 %, and only then act on the result.
The audience here is people who need one trustworthy number before their next decision. Everything you need to defend the result — formula, substitution, sensitivity, source — is printed above, so the only remaining variable is the honesty of your inputs.