In short: Pipeline velocity combines qualified opportunity volume, average deal value, win rate, and sales-cycle length into a directional rate. It is useful for finding which part of the sales system changed. It is not a revenue forecast or proof that marketing caused the change. Define the opportunity cohort and time basis first, then review the four inputs alongside stage movement, losses, and realized revenue.
Teams often respond to a slow quarter by asking for more leads or a shorter sales cycle. A single pipeline metric cannot tell them which response will help. A velocity calculation can organize the discussion, but only when its inputs refer to comparable opportunities and the team can trace changes back to the underlying deals.
1. Decide what the metric should help you decide
A common sales-velocity formula is:
Qualified opportunities × average deal value × win rate ÷ average sales-cycle length
Salesforce describes these four inputs as a way to estimate the pace at which revenue moves through a pipeline. The result is often expressed as currency per day. Treat it as a model based on the definitions you select, not as a universal accounting measure.
Keep it distinct from two nearby metrics:
- Pipeline coverage compares the open pipeline with a target. It describes how much potential value is available relative to a goal.
- A sales forecast estimates what may close in a future period, using stages, probabilities, manager judgment, and other evidence.
- Pipeline velocity combines volume, value, win rate, and time into one directional rate. It can help explain a change, but it does not identify its cause by itself.
Use velocity when the decision is about diagnosing the sales system: whether qualified volume, deal value, conversion, or cycle time is changing. Use a forecast to plan a period, and use booked, invoiced, or collected results when reporting realized economics.
2. Lock the definitions before calculating
The formula is simple; the data choices are not. Write down what counts as an opportunity, which date starts the cycle, what counts as a win, how deal value is measured, and which records belong in the calculation.
For example, a team might define an opportunity as a CRM record that has passed a documented qualification gate. Another team may use a later stage. Either can be useful if the definition is stable and the team applies it consistently. The revenue data dictionary guide can help document the record grain, stage criteria, field owner, and source.
Choose one time basis for each input. Do not combine the number of open opportunities on the last day of a quarter with a win rate from a different market and a cycle length calculated only from last month’s wins without labeling the mismatch. If the business has meaningfully different segments, calculate them separately, such as new-logo versus expansion deals or enterprise versus mid-market.
Also decide whether the cycle begins at first qualified opportunity, first meeting, or another CRM milestone. Changing that start point can change the measured cycle without any change in how buyers actually decide. Record changes to stage definitions and fields so a process change does not look like a sudden performance improvement.
3. Build a comparable cohort and calculate the rate
A practical starting point is a cohort of opportunities that entered the same qualified stage during a defined period. Calculate the outcomes for that cohort after enough time has passed for it to mature. If you use a point-in-time pipeline snapshot instead, label it clearly and do not present it as the result of a closed cohort.
Consider this example:
- 20 qualified opportunities in the defined cohort
- $25,000 average deal value, using one consistent amount basis
- 25% win rate for the same segment and comparable cohort
- 100 average cycle days under the team’s chosen start and end rules
The calculation is 20 × $25,000 × 0.25 ÷ 100 = $1,250 per day. That is a modeled rate based on those inputs. It does not mean the company collected $1,250 each day or will close that amount in the next 24 hours.
Use the formula as a comparison only when the cohort, currency, opportunity definition, and time window are comparable. If the B2B cycle is longer than the reporting window, show the cohort’s maturity and keep open opportunities visible as open. Avoid treating an immature cohort’s current win rate as its final conversion rate.
4. Keep the four inputs visible
Always show the inputs next to the calculated rate. A rising velocity can result from more qualified opportunities, larger deal values, a higher win rate, or a shorter cycle. Those changes have different commercial meanings.
- More opportunities may reflect broader sourcing, or looser qualification.
- A larger average value may reflect a stronger segment, or a few unusually large deals.
- A higher win rate may reflect better fit, or a narrower set of opportunities being entered.
- A shorter cycle may reflect less buyer friction, or deals being closed out earlier as lost.
Break the number down by relevant segments and inspect stage-to-stage conversion, time in each stage, close-date changes, and loss reasons. HubSpot’s sales analytics documentation, for example, describes reports for deal stage conversion, time in stage, deal velocity, and sales velocity. These views help you see movement behind an aggregate rate; they do not make different CRM definitions automatically comparable.
Do not use only won deals to claim that cycle time improved if slow, open, or lost opportunities disappeared from the calculation. Define how closed-won, closed-lost, and still-open records are handled, and keep that rule stable between periods.
5. Compare periods without hiding timing effects
Set a clear as-of date and compare periods with similar opportunity maturity. The pipeline as-of date guide explains why reports taken at different points in a CRM update cycle can disagree. The guide to separating processing delays from sales-cycle maturity covers the difference between a late-arriving update and a genuinely long buying process.
For a useful review, preserve the same rules across the periods being compared:
- Use the same qualification and stage definitions.
- Compare like-for-like segments and currency.
- Show the age and maturity of each opportunity cohort.
- Include stage movement, losses, and pushed close dates.
- Explain changes to CRM fields, pipelines, or reporting filters.
If sample sizes are small or cycles are long, show the components and direction of change instead of presenting a precise-looking daily figure. Keep the assumptions visible so a decision maker can distinguish a real shift from timing noise.
6. Connect velocity to marketing and realized revenue carefully
Marketing can influence qualified opportunity volume, deal fit, and the information buyers receive. Sales execution, pricing, product availability, procurement, and delivery capacity also affect wins, deal size, and cycle time. A single velocity number cannot assign credit among those causes.
Compare opportunity cohorts with documented source and influence fields, and report where those definitions are uncertain. The guide to forecasting marketing-sourced pipeline without calling it revenue explains how to keep pipeline contribution separate from booked results. For realized economics, use the bookings, invoices, and cash reconciliation method.
Pipeline-velocity worksheet
- Decision this metric should inform: ______
- Opportunity entry stage and qualification criteria: ______
- Cohort period or snapshot date: ______
- Deal-value field and currency basis: ______
- Win-rate numerator and denominator: ______
- Sales-cycle start and end events: ______
- Treatment of open and lost opportunities: ______
- Segments reported separately: ______
- Stage conversion, aging, and close-date movement: ______
- Realized outcome used for follow-up: ______
Pipeline velocity is most useful as a prompt to inspect the system behind the number. Keep its inputs visible, compare mature and comparable cohorts, and use customer and cash outcomes to judge whether a change created better business results.
If your pipeline report moves but the underlying opportunity records tell a different story, request a marketing diagnostic to review the stage definitions, cohort logic, and reporting path.
Sources and scope
- Salesforce: What Is Sales Velocity? — the four-input formula and a common interpretation of its result.
- HubSpot Knowledge Base: Create sales reports in the sales analytics suite — available sales reports for stage conversion, time in stage, deal velocity, and sales velocity.
- Salesforce Help: Pipeline Forecasting Best Practices — opportunity-level details, stage-to-forecast mapping, and regular forecast review.
The formula is a diagnostic model, not an industry-standard accounting definition or a guarantee of future revenue. Confirm your CRM’s field definitions and reporting behavior before comparing teams or changing targets. Accessed October 9, 2026.
How did this article land?
Choose one reaction. You can change it anytime.