RevOps
Turn deals, win rate, ACV and cycle length into revenue per day.
- Category
- RevOps
- Signup
- None
- Your data
- Stays in your browser
- Also in
- Claude, via MCP
How do you calculate pipeline velocity?
Pipeline velocity = (qualified opportunities × win rate × average deal value) ÷ sales cycle length in days. The result is the revenue your pipeline produces per day. 120 opportunities at a 25% win rate and $18,000 average deal value, on a 60-day cycle, give $9,000 a day, or about $270,000 a month.
You’re generating about $9,000/day of won revenue. Cutting cycle length is the most under-used lever here, it’s a divisor, so shaving 10 days lifts velocity as much as adding deals or raising ACV.
Velocity = (opportunities × win rate × deal value) ÷ cycle length. Each input is a lever; the cycle length is the one most teams ignore.
About this calculator
Pipeline velocity is the one RevOps formula that turns four separate metrics, deal count, win rate, deal size, cycle length, into a single number: how much revenue your pipeline generates per day. It's useful precisely because it's a ratio, it tells you which lever to pull rather than just how much pipeline you have sitting open.
How to use it
- Enter open opportunities, the count of active deals in your pipeline right now.
- Enter win rate, the share of those opportunities that historically close won.
- Enter average deal value (ACV) for the segment you're modeling.
- Enter sales cycle length in days, the average time from opportunity creation to close.
- Read velocity per day, per month, and per quarter, plus deals won per cycle.
Methodology
Velocity per day is (open opportunities × win rate × average deal value) ÷ sales cycle length, the classic pipeline velocity equation. Per-month and per-quarter figures simply multiply the daily rate by 30 and 90.
Deals won per cycle is opportunities × win rate, a secondary output showing raw deal count independent of dollar value or time.
Because cycle length sits in the denominator, shortening it lifts velocity by the same proportion as growing the numerator, cutting a 60-day cycle to 50 days raises velocity about 20%, the same effect as adding 20% more opportunities or ACV. Most teams under-invest in cycle-length work relative to lead generation, even though it moves the same number.
This is a rate calculation, not a forecast, it assumes the win rate, ACV and cycle length you enter are representative of the pipeline going forward, not just a historical average that may already be shifting.
Pipeline (sales) velocity formula
Velocity per day = (Open opportunities × Win rate × Average deal value) ÷ Sales cycle length (days) Velocity per month ≈ Velocity per day × 30 Velocity per quarter ≈ Velocity per day × 90 Deals won per cycle = Open opportunities × Win rate
- Open opportunities
- Qualified, active opportunities in the pipeline that have passed your opportunity stage gate.
- Win rate
- Closed-won deals ÷ all closed opportunities (won plus lost) over a recent period, for the same segment.
- Average deal value
- Average first-year value of won deals (ACV for SaaS), in your reporting currency.
- Sales cycle length
- Average days from opportunity creation to close, measured on closed deals.
This is the same equation Salesforce and HubSpot publish as sales velocity; "pipeline velocity" and "sales velocity" are used interchangeably. Because the opportunity count is a snapshot of open deals, the result is a steady-state rate: it assumes new opportunities replace closed ones at the same pace. If pipeline creation is falling, today's velocity overstates next quarter. Cutting the cycle by a given share raises velocity by slightly more than the same share: a 10% shorter cycle lifts velocity by 11.1% (1 ÷ 0.9), while a 10% higher win rate lifts it by exactly 10%. HubSpot recommends measuring over at least a quarter and up to a year to smooth out seasonality.
Worked example: an Indian B2B software company
A Pune B2B software company has 80 qualified open opportunities. Its win rate on closed opportunities over the last two quarters is 20%, average first-year deal value is ₹6 lakh, and deals take 90 days from opportunity creation to close.
- Numerator = 80 × 0.20 × ₹6,00,000 = ₹96,00,000
- Velocity per day = ₹96,00,000 ÷ 90 = ₹1,06,667
- Velocity per month ≈ ₹1,06,667 × 30 = ₹32 lakh; per quarter ≈ ₹96 lakh
- Deals won per cycle = 80 × 0.20 = 16
- Lever check: cutting the cycle to 75 days gives ₹96,00,000 ÷ 75 = ₹1,28,000 a day, a 20% lift
- Lever check: raising win rate to 24% at 90 days gives 80 × 0.24 × ₹6,00,000 ÷ 90 = ₹1,28,000 a day, the same 20% lift
The pipeline produces about ₹32 lakh a month of won revenue. A 15-day shorter cycle and a four-point win-rate gain are worth the same amount, so the team can choose whichever is cheaper to achieve. If the quarterly target is ₹1.2 crore, the gap is about ₹24 lakh a quarter, which at current rates needs roughly 20 more open opportunities (₹24 lakh ÷ (0.20 × ₹6 lakh)).
Reference points from Gong customer data (2025)
| Metric | Figure |
|---|---|
| Days to close a $100K deal | About 70 days on average |
| Win rate, opportunity to closed, enterprise customers | About 25% |
| Open opportunities per enterprise rep | About 54 on average |
What is a good pipeline velocity?
There is no universal good velocity, because it is measured in your currency and scales with team size. A good velocity is one that, multiplied by the days in the period, covers your target. Use it in three ways:
- Against target: velocity per quarter ÷ quarterly new-revenue target. Below 100% means the current pipeline cannot deliver the plan, however hard reps work.
- Against itself over time: track it monthly per segment. A fall shows up here before it shows up in closed revenue, because cycle and win rate move first.
- By lever: compare each input with your own history. Gong data reported by SaaStr puts enterprise win rates around 25% and $100K deals at about 70 days, which is a reference point, not a target.
A decision rule: fix the input furthest below its own historical level first, since it usually has the most room to recover. The pipeline velocity guide covers how to measure each lever, the sales cycle length forecaster checks cycle assumptions, and the sales pipeline leak evaluator finds where deals drop out.
Pipeline velocity in India vs the US
Indian B2B cycles often include steps after the commercial decision: vendor registration, purchase order release and GST invoicing. Measure cycle to signed purchase order or contract, not to verbal approval, or velocity will look better than cash received. Deal values in rupees are lower, so Indian teams usually need more opportunities per rep to reach the same velocity, and lead qualification discipline matters more. Opportunities from WhatsApp, IndiaMART or phone enquiries are often logged inconsistently, which distorts the opportunity count; a HubSpot consultant in India or a RevOps audit usually starts by fixing stage definitions so the inputs are trustworthy.
US SaaS teams typically run velocity by segment (SMB, mid-market, enterprise), as HubSpot recommends, because deal values and cycles differ several-fold between them. Larger US deals involve more stakeholders and procurement review, so cycle length is often the input that drifts first. Gong figures reported by SaaStr show $100K deals averaging about 70 days; if your deals of that size take much longer, compare stage-by-stage durations to find where time is lost.
Common pipeline velocity mistakes
- Counting every open deal, including stale ones with no activity for months, which inflates the opportunity count.
- Calculating win rate as won ÷ all opportunities created, including ones still open, which understates it, or won ÷ won plus lost late-stage deals only, which overstates it.
- Measuring cycle length on open deals instead of closed deals.
- Blending SMB and enterprise deals into one velocity number so neither segment can be managed.
- Using list-price deal value when most deals close at a discount.
- Treating velocity as a forecast without checking that new pipeline is being created at the same rate deals are closing.
Sources
- How to Supercharge Your Sales Velocity for Quicker Wins, Salesforce. Accessed 2026-10-17.
- Sales Velocity: What It Is & How to Measure It, HubSpot. Accessed 2026-10-17.
- Gong: $100k Deals Take About 70 Days to Close, SaaStr (reporting Gong, The State of Revenue 2025). Accessed 2026-10-17.
Go deeper
FAQ
Whichever one moves fastest relative to its current value. Since all four inputs multiply or divide linearly into velocity, a 10% improvement in any one produces roughly the same 10% lift, so the fastest win is the input you can realistically move furthest, and cycle length is usually the most under-worked of the four.
Yes, if enterprise and SMB deals differ meaningfully in win rate, ACV or cycle length, blending them into one velocity number can hide which segment is actually improving or degrading. Run the calculator separately per segment where volumes justify it.
It reflects throughput, not profitability, a team could raise velocity by discounting to close faster at lower ACV, which the formula would show as flat or improved even though margin fell. Read velocity alongside margin, not as a standalone health metric.
In most usage they are the same metric with the same formula: opportunities × win rate × deal value ÷ cycle length. Some teams use "pipeline velocity" for the speed deals move between stages and "sales velocity" for revenue per day; say which you mean in reports.
Either works as long as you read the output in the same unit. In days, the result is revenue per day; in months, revenue per month. This calculator uses days and multiplies by 30 and 90 for monthly and quarterly figures.
As a sense check, yes: velocity per quarter shows what the current pipeline can produce if conditions hold. It is not a deal-by-deal forecast, so use it alongside stage-weighted pipeline and rep commits, and investigate when the methods disagree.
Only deals that have met your qualification criteria, for example a confirmed need, budget range and a next meeting. Including unqualified leads raises the count but lowers the win rate, and the mismatch makes the lever analysis misleading.
Slipped deals stay open longer, which lengthens the measured cycle, and they tend to close at a lower rate. Both effects reduce velocity, so track how many deals move their close date each month alongside the formula.
Numbers looking off?
If the model says one thing and the pipeline says another, that gap is usually where the revenue is. A 30-minute call finds it.
It starts with a 30-minute call. Pick a time below.