Quick answer
Pipeline velocity is the revenue a sales pipeline is expected to generate per day: qualified opportunities × average deal value × win rate, divided by the sales cycle length in days. Improving any one of the four inputs raises it.
Formula: (opportunities × average deal value × win rate) ÷ sales cycle length (days)
What is pipeline velocity?
Pipeline velocity is the amount of revenue your sales pipeline is expected to generate per unit of time, usually per day. It combines four numbers: how many qualified opportunities you have, how much each is worth, how often you win, and how long a deal takes. Many sources use sales velocity for the same metric, and the formula is the same.
Pipeline velocity does not tell you how much you will sell this quarter. It tells you how fast value moves through the funnel at today's rates, and, more usefully, which of the four inputs is worth improving first.
The formula
Pipeline velocity = (opportunities × average deal value × win rate) ÷ sales cycle length
| Variable | Definition | Unit | Where it comes from |
|---|---|---|---|
| Opportunities | Qualified deals in the pipeline during the period | Count | CRM, filtered by qualification stage |
| Average deal value | Average revenue per won deal | Currency | Closed-won deals |
| Win rate | Won deals ÷ all closed deals (won plus lost) | Percent | CRM closed deals |
| Sales cycle length | Average days from a deal entering the pipeline to closing | Days | CRM timestamps |
The result is revenue per day when the cycle is in days. Multiply by the days in a period to project it: Salesforce's own example, 150 opportunities at $1,000 with a 25% win rate and a 30-day cycle, gives $1,250 per day, or $112,500 over a 90-day quarter. (Its text prints the win rate as 0.25%, but the arithmetic only works with 25%.) Pipedrive's guide shows a second case: 20 deals at $5,000 with a 40% win rate and a 60-day cycle give (20 × 5,000 × 0.40) ÷ 60 = $667 per day.
There is no universal good number. Velocity depends on deal size and industry, so compare your own figure month over month and by segment, not against someone else's. A rise in the number is only good news if the inputs behind it are real: check that win rate and cycle were measured the same way both months.
A short rule for the first input: an opportunity is qualified when the buyer has a budget, a need and a decision date you have confirmed, whatever your team calls the stage. Write the definition down and count only deals at or past that stage, in every period.
A worked four-variable example
Sample data: a B2B software team has 40 qualified opportunities, an average won deal of $12,000, a 22% win rate and a 60-day cycle.
(40 × $12,000 × 0.22) ÷ 60 = $105,600 ÷ 60 = $1,760 per day
Over a 90-day quarter that is $158,400 of expected revenue. Now improve each input by roughly 10%, one at a time:
| Change | New inputs | Velocity per day | Change vs $1,760 |
|---|---|---|---|
| More opportunities (+10%) | 44 | $1,936 | +10.0% |
| Higher deal value (+10%) | $13,200 | $1,936 | +10.0% |
| Higher win rate (+10%) | 24.2% | $1,936 | +10.0% |
| Shorter cycle (−10%) | 54 days | $1,956 | +11.1% |
| Shorter cycle (−25%) | 45 days | $2,347 | +33.3% |
The first three inputs multiply, so a 10% gain in any one gives a 10% gain in velocity. The cycle length divides, so cutting it is slightly better than the same percentage on a multiplier, and cutting it by a quarter is worth a third. The practical question is which lever is cheapest for you: a 10% shorter cycle may need only faster contract review; 10% more opportunities may need more spend.
Why you should calculate by segment
Averages across very different deals give misleading answers. Sample data: 30 small deals and 10 large deals.
| Segment | Opportunities | Avg deal value | Win rate | Cycle | Velocity per day |
|---|---|---|---|---|---|
| Small business | 30 | $4,000 | 30% | 30 days | $1,200 |
| Enterprise | 10 | $60,000 | 15% | 120 days | $750 |
| Sum of segments | 40 | $1,950 |
Now pool the same 40 deals with simple averages: average deal value $18,000, win rate 26.25%, cycle 52.5 days. The formula gives (40 × 18,000 × 0.2625) ÷ 52.5 = $3,600 per day, 85% higher than the true $1,950. The simple averages weight a handful of large deals as if they were as common and as quick to close as the small ones, so the pooled result describes no real group of deals. Compute each segment, then add the results.
How to improve each input
- Opportunities. Count only qualified ones. Adding unqualified leads raises the count but lowers the win rate and lengthens the cycle, so velocity can fall. Define "qualified" in writing.
- Average deal value. Look at pricing, packaging, multi-year terms and add-ons. Watch that bigger deals do not stretch the cycle by more than they add in value: a deal 30% larger that takes 40% longer lowers velocity.
- Win rate. Review lost deals by stage and reason. A rate that falls only in one stage points to a process problem there.
- Cycle length. Find the slowest stage with stage-to-stage timestamps. Typical delays are procurement, legal and waiting for the buyer's reply, and each has its own fix.
Change one input at a time over a full cycle, or you will not know what moved the number. For more on timing, see the B2B sales cycle guide, and for stage-by-stage conversion, the SaaS sales funnel.
Common mistakes
- Mixing definitions. Use the same stage for "opportunity", and the same calculation for win rate (won ÷ won plus lost) every period.
- Using a stale cycle length. Measure from the stage you count as an opportunity, over deals closed in the period.
- Ignoring deal slippage. Open deals that sit for months are still in the opportunity count. Cap the age or review them.
- Comparing teams with different mixes. Compare within a segment, as above.
- Treating it as a forecast. Velocity is a rate at today's inputs, not a commitment.
What TapCub covers around pipeline velocity
Suppose your opportunity count is flat and you want to know whether the top of the funnel is the problem.
- TapCub is not a CRM. It does not hold opportunities, deal values, win rates or sales cycles, and does not score leads, so it cannot calculate pipeline velocity itself.
- Measure what feeds the first variable. In Web analytics › Goals, define a goal such as a demo-request page view or event, then read conversions by channel in Web analytics › Sources. This shows which channels produce the demo requests that become opportunities.
- Know who they are. Call
tapcub.loginon login so people appear in All-platform analytics › Users › People, with a time-line of what they did before they asked for a demo. - Carry the source into your CRM. Use the channel and UTM data you see in TapCub to tag leads at creation, so win rate and cycle can later be sliced by source in your CRM.
- Check the speed of the first reply. If you use TapCub's live chat, Live chat › Reports shows first response time, one input to how fast a deal starts moving.
Sources
- Salesforce, Sales velocity: what it is and how to calculate it.
- Pipedrive, What is sales velocity and how do you boost it?.
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Product Experience Specialist
Explores usability, user journeys, and feature adoption through practical examples of onboarding and everyday product use.