Pipeline velocity calculator and the sales velocity formula, with worked numbers

A pipeline velocity calculator returns revenue per day: qualified opportunities times win rate times average deal size, divided by sales cycle length in days. With 80 qualified opportunities, a 25% win rate, a $40,000 average deal and a 90-day cycle, velocity is $8,888.89 a day, or $800,000 over 90 days. Run it per segment, because a blended number hides which lever is moving.

What is pipeline velocity and how do you calculate it

Pipeline velocity is the dollars of revenue your pipeline produces per day. SalesHive describes sales velocity as the rate at which open pipeline converts into closed revenue, expressed as a dollar figure per day. The formula, as Revspire writes it: qualified opportunities × win rate × average deal size ÷ average sales cycle length in days.

Pipeline velocity = (qualified opportunities × win rate × average deal size) ÷ sales cycle length in days

Sales velocity and pipeline velocity are two names for the same calculation. Pick one name, write it into your metric definitions, and calculate it the same way every quarter.

The four inputs, defined so they can be audited

• Qualified opportunities: the count of open deals that meet your entry criteria, usually your sales qualified lead (SQL) or stage-one opportunity definition.
• Win rate: SalesHive defines it as closed-won deals divided by deals that reached a terminal state (closed-won plus closed-lost). Leave in-progress deals out of the denominator.
• Average deal size: closed-won revenue divided by closed-won deal count, using one definition of contract value throughout.
• Sales cycle length: the average number of days from opportunity creation to close, counted across both won and lost deals.

For the forward-looking version, Revspire's guidance is to take the opportunity count from the pipeline as it stands today and pull the other three inputs from closed deals in the same segment over recent quarters.

A worked example

The mid-market math is (150 x $40,000 x 0.28) / 75 = $22,400 per day. The enterprise math is (35 x $180,000 x 0.24) / 130 = $11,631 per day. Multiply by 90 and the mid-market motion yields $2,016,000 over a 90-day quarter. Enterprise deals are larger, yet that motion produces fewer dollars per day.

How the calculator works

The calculator takes the same four inputs. Enter your open qualified opportunity count, your win rate as a percentage, your average closed-won deal size in dollars, and your average cycle length in days. It returns one figure: revenue per day.

Run it once per segment rather than once for the company. We think a blended number hides which lever is moving. To check whether your inputs are in a plausible range, compare them against our win rate benchmarks and sales cycle length benchmarks. The short definition lives in the pipeline velocity glossary entry.

Where each input comes from in your CRM

Each of the four inputs has a home in your customer relationship management (CRM) system. The work is pulling each one with the same date window and the same filters, so the formula multiplies like with like.

Pulling each input

For win rate and cycle length, Revspire advises: "use cohorts (opportunities created in the same period) rather than whatever happened to close". In practice, set the report's date filter to created date, not close date.

For deal value, divide won revenue by won deals, with one definition of value, either annual contract value or first-year value, throughout. The same guide suggests reporting the median next to the mean.

If your CRM stamps creation before qualification, use the date the deal entered your first qualified stage.

Grouping by team and filtering by pipeline

HubSpot's sales reports show how these filters usually look. Its Date range by filter uses a stated date property, its Group by option segments the records based on their owners or their owners' teams, and a Pipeline filter filters the records based on their deal pipeline. Its average deal size report shows the average deal amount per deal owner or team.

Run all four inputs with the same pipeline filter and the same team grouping. A renewals pipeline mixed into new business will distort all four inputs at once, in our reading.

Pipeline number versus stage timing

The four inputs produce a pipeline-level rate. Stage timing is a separate, deal-level measure: Revspire describes it as days in each stage and total days to close. A deal stuck in one stage shows up first in deal velocity, then in stage velocity, and only later in pipeline velocity. Keep a days-in-stage report next to the velocity calculation, and check cycle inputs against sales cycle length benchmarks.

Worked example of a pipeline velocity calculation

The inputs are illustrative: a single segment with 80 qualified opportunities open today, a 25% win rate, a $40,000 average deal and a 90-day cycle.

The steps, in order

1. Multiply opportunities by win rate: 80 x 0.25 = 20 deals expected to close.
2. Multiply expected deals by average deal size: 20 x $40,000 = $800,000 in expected won revenue.
3. Divide by cycle length in days: $800,000 / 90 = $8,888.89 a day.
4. Multiply the daily figure by 30 to get the 30-day view: $266,667.

The order of the first three steps does not change the answer, because the formula is all multiplication with one division. Keeping this order makes the middle numbers readable. Most people can sanity-check 20 deals and $800,000 against their forecast in a few seconds.

Reading $8,889 a day

The daily figure is the rate at which today's qualified pipeline turns into won revenue. It is a pace, not a booking. No single day will show $8,889 landing in the CRM; deals close in lumps.

Read it per quarter by multiplying by the days in the period. Over 90 days the pipeline produces $800,000, which is the same figure as step 2. That match is expected: when the period you look at equals the cycle length, velocity times the period returns the full expected value of the open pipeline.

Some definitions express cycle length in months rather than days. HubSpot's version lists the cycle input as "measured in months." Using 3 months instead of 90 days gives $800,000 / 3, or about $266,667 a month, which lines up with the 30-day row. The unit of the denominator sets the unit of the result, so label it on every report.

Checks before you share the number

• Run it per segment. HubSpot advises to separate small, mid-market, and enterprise pipelines and run the equation for each one. A blended figure hides which segment moved.
• Use a long enough window. Measure win rate and cycle on deals closed over the last two to four quarters, so one lumpy month does not swing the result.
• Compare the 90-day output with your quota and your pipeline coverage. In our reading, a gap between the two points to which input to work on first, and the pipeline coverage calculator runs that comparison.

Which lever raises sales velocity fastest

Our sensitivity method is simple. Start from the base plan in the worked example, move one lever by 10% in its favorable direction, hold the other three still and recompute. Then move all four together.

Moving each lever 10% from the $8,889 base adds 10.0% for opportunities, win rate and deal size, 11.1% for a shorter cycle, and 47.9% when all four move together.

The three multipliers behave identically. Each sits in the numerator, so a 10% gain in any one of them is a 10% gain in velocity.

The cycle is different because it sits in the denominator. Cutting 90 days to 81 divides the same $800,000 of expected won revenue by 0.9 of the old length, and 1 / 0.9 is about 1.111. That is the extra 1.1 points. The gap widens as the cut gets deeper. SalesHive works through a case where a 10-day reduction on a 42-day cycle produces roughly a 31% lift, because 42 / 32 is about 1.31.

Combined moves compound: 1.1 x 1.1 x 1.1 / 0.9 is about 1.479, which matches the SalesHive figure that 10% in each of the four levers produces roughly a 48% lift.

Math versus effort

The arithmetic says the levers are close to equal at 10%. What separates them is how much work each 10% costs and what it breaks on the way.

The side effects are real. SalesHive notes that stuffing the pipeline with low-intent meetings lowers win rate and stretches cycle length. It describes win rate as a sales execution problem, driven by ICP fit, competitive positioning, and deal coaching, where ICP means ideal customer profile. It says deal size moves through better packaging, multi-threading into bigger buying committees, and targeting higher-tier accounts, and that it rarely moves through discounting, which compresses deal size and velocity at the same time.

In our reading, the practical order is this. Run the 10% test on your own base. Then pick the lever where a 10% move costs the least effort without damaging the others. For a demand team that is often opportunity quality, not raw count. Check that choice against win rate benchmarks and sales cycle length benchmarks before you commit a number to the plan.

Should you calculate velocity by segment

A blended velocity number assumes one sales motion. Most B2B companies run two or three, each with its own deal size and cycle, and averaging them produces a figure no team can sell against. ORM Technologies puts it directly: averaging segments creates a figure "that describes no real motion in the company."

The blended calculation reports $61,107 per day, while the three segments built from the same deals add to $47,610.

The blended row runs high

Here is ORM's three-segment example, with a typical cycle range by deal size from Domestique alongside each segment.

Segment figures come from ORM. Cycle ranges come from Domestique, where small business deals run 30 to 60 days, mid-market deals average 60 to 120 days, and enterprise deals take 6 to 12 months.

Both bottom rows use the same deals. The blended version reports $61,107 per day while the segments add to $47,610, and across a 90-day quarter that gap is roughly $1.2 million of capacity that does not exist. Check the arithmetic: $13,497 a day times 90 days is $1,214,730.

In our reading, the cause is the denominator. Short-cycle segments dominate the blended cycle because they contribute the most opportunity records, while large deals dominate the blended deal value. The blend pairs enterprise dollars with small business speed.

The blend hides mix shifts

ORM shows a second failure: move 20 opportunities from small business to enterprise and the blended number barely moves, while the revenue timeline stretches by months. Segment velocity shows the change in the quarter it happens.

A working setup

1. Define segments by deal size, using your own thresholds. ORM's $18,000 small business deal sits above Domestique's $10,000 line, so labels vary by company.
2. Split only where the volume supports it. ORM's threshold is a stable win rate, usually 30 or more closed deals per period.
3. Run the formula once per segment, then report the sum of segments, never the blended row.
4. Compare each segment's cycle with its typical range in sales cycle length benchmarks, and each segment against its own prior quarter.

In our reading, a lower enterprise figure per day is expected, not a problem. The useful question is which of the four inputs moved within that segment since last quarter.

What is a good sales velocity

A dollars-per-day figure only means something next to your own history. The formula multiplies opportunity count by deal size, so a company with ten times the open deals posts ten times the velocity at identical efficiency. Even the vendors who publish the formula say so: pipeline velocity itself varies significantly with the nature and size of the company.

The useful outside comparisons are for the inputs, where a ratio or a day count travels between companies.

Published input ranges

Read its slippage figure as a check on your cycle input: if close dates move often, your measured cycle is shorter than the one buyers are living.

Your own trend is the benchmark

Three rules keep the trend honest:

1. Hold definitions fixed. If you change what counts as a qualified opportunity, restart the series rather than splice it.
2. Read the inputs before the output. A flat velocity can hide a rising deal size offset by a longer cycle.
3. Compare like periods. Set a quarter against the same quarter last year when your business has seasonal buying.

A good velocity, in our reading, is one that rises over time while each input stays inside a range you can defend against the published figures above. The pipeline velocity glossary entry covers the definitions the template assumes.

Mistakes that distort the velocity number

Most bad velocity numbers come from inputs, not arithmetic. The formula multiplies whatever you feed it, so one loose definition moves the whole result. These are the traps we see most, with the fix for each.

Cycle length on survivors only

ORM Technologies states the problem directly: measuring cycle only across closed deals "excludes every opportunity still open past the average, which pulls the number down and inflates velocity." Sources split on the cure. SalesHive counts cycle "across both won and lost deals to get a true picture," while ORM keeps won-only for cycle length and says to "track time to loss separately." We think either works if the choice is written down and a creation cohort sits beside it, so open deals stay visible.

Watch for zero-day records too. ORM reports one customer that "had 20% of its opportunities created and closed-won on the same day." Pull those out before you compute the median.

Unqualified opportunities and inflated deal values

SalesHive notes that unqualified deals reduce velocity "by dragging down win rate and inflating cycle length." Tie the opportunity count to your sales qualified lead definition. Deal value has the same trap: in ORM's example, a pipeline average of $80,000 against closed-won deals averaging $40,000 doubles reported velocity. Use closed-won averages only.

Mismatched windows

ORM gives the rule: "Every input has to come from the same segment and the same time window." A practical check: put the start and end date of each input in the report header. If the four rows show different dates, the number is not ready to share.

Average where a median belongs

In ORM's worked set, a single 190-day deal puts the mean 13.6 days above the median. Report the median, then split it by deal size, since the same source warns that "Medians are dangerous too when the distribution is wide." Compare your splits against our sales cycle length benchmarks.

How pipeline velocity differs from pipeline coverage and how to act on both

Coverage and velocity answer different questions. SalesHive puts it plainly: "Raw pipeline coverage tells you how much is in play. Velocity tells you how fast it is actually turning into money." Pipeline coverage is a ratio of open pipeline to target. Velocity is dollars per day.

The same source notes that two teams with identical coverage can have wildly different velocity. Here is a worked case. Both teams hold $1.2M of pipeline against a $400K quarterly target, so both sit at 3x coverage.

The 90-day row multiplies velocity by days in the window. That is a simplification, since real deals close in lumps, but it shows the direction. A coverage report would rate these teams the same. Velocity tells you Team A needs either a shorter cycle or more pipeline created earlier. Check the coverage side with the pipeline coverage calculator and the velocity side with the method from earlier sections.

In forecasting, we use coverage to ask whether enough pipeline exists and velocity to ask whether it lands inside the period. A quarter needs both answers.

A monthly routine you can copy

1. Pull inputs by segment. Opportunities, average deal size, win rate and cycle length for each motion, same window, same definitions as last month.
2. Compute velocity per segment.
3. Compare to last period. Record the percent change in velocity and in each of the four inputs.
4. Find the weakest lever. Pick the input with the largest adverse change. Small moves matter: SalesHive notes a 3 to 5 point drop in win rate can represent a large revenue gap across a full pipeline.
5. Assign one owner and a date to report back.

Ownership follows who moves each input. Per SalesHive, the opportunities lever is the one an outbound SDR function directly controls, deal size and win rate are mostly closed by AEs and the product, and cycle length is a shared effort across sales, marketing and procurement. For a shared lever, we name one person anyway, so the follow-up has an owner.

On Monday, add a velocity column next to the coverage column in your demand gen dashboard, one row per segment. Then name the first owner for whichever segment shows the lowest velocity this month.

What this page does not cover

This page covers the velocity formula, its four inputs, segment math and a monthly review routine. It does not cover building a full revenue forecast, setting quotas or measuring deal-level stage timing in detail. It is not financial advice.

Related on Take the Market: Pipeline coverage calculator: the ratio you need from your own win rate and slippage; Demand generation calculator: reverse funnel math from a revenue target to visitors, leads, MQLs, SQLs and opportuniti; B2B marketing budget allocation calculator: split demand gen spend by pipeline per dollar.

Where the defaults come from