Sales velocity
Multiply opportunities, win rate and deal value, then divide by sales cycle days.
Revenue per day = opportunities × win rate × average deal value ÷ sales cycle daysMeasure how much revenue your pipeline produces per day, and whether you have enough of it to hit the quarter.
Qualified opportunities currently open in your pipeline.
The share of qualified opportunities you expect to close-won.
Average revenue from a closed-won deal.
Average days from qualified opportunity to close.
The new revenue target used for coverage and gap.
Revenue per day
60 qualified opportunities at a 25% win rate and $20,000 per deal produce $4,000 per day over a 75-day cycle.
Multiply opportunities, win rate and deal value, then divide by sales cycle days.
Revenue per day = opportunities × win rate × average deal value ÷ sales cycle daysMultiply daily velocity by 30 for a month or 90 for a quarter. Compare the quarterly figure with your target.
Monthly velocity = daily velocity × 30; quarterly velocity = daily velocity × 90Pipeline value is open opportunities times deal value. Coverage compares it with the quarterly target.
Coverage = opportunities × deal value ÷ target; pipeline needed = target ÷ win rateSales velocity estimates how much revenue your current qualified pipeline produces per day. It combines opportunity count, win rate, deal value and sales cycle. This calculator also turns the daily figure into monthly and quarterly revenue.
Multiply open qualified opportunities by win rate and average deal value, then divide by sales cycle days. With the defaults, 60 opportunities at 25% and $20,000 over 75 days gives $4,000 per day. Quarterly velocity multiplies that by 90.
Pipeline coverage divides open pipeline value by the revenue target. Three times coverage is a common rule of thumb; the more direct sanity check is one divided by your win rate. At a 25% win rate, that check is four times coverage.
Increase qualified opportunities, win rate or deal value, or shorten the sales cycle. The lever cards compare a 10% relative improvement in each input. In the default scenario, a 10% shorter cycle produces the largest increase because dividing by 0.9 lifts velocity by about 11%.
I build HubSpot systems that keep stages, routing and forecasts trustworthy.