Affiliate Disclosure: We may earn a commission if a qualifying affiliate link is added after partner approval, at no extra cost to you. No affiliate links are active in this article at publication. This guide uses public documentation and transparent calculations. See our editorial policy.
Part of our CRM Software Guides for Small Businesses library.
Cost evidence: Before comparing velocity gains with software cost, use our CRM annual-cost dataset for a transparent 5-, 10-, or 20-user seat-cost baseline.
The short answer
One formula combines four sales levers.
Sales velocity = qualified opportunities × average deal value × win rate ÷ average sales cycle length. When cycle length is measured in days, the output is expected pipeline value per day.
Sales teams often review pipeline value, win rate, average deal size, and cycle length as separate numbers. Sales velocity combines them into one rate. That makes it useful for answering a narrow operational question: under the current set of averages, how much expected value moves through this pipeline per unit of time?
The number is not a promise that the same revenue will close every day. It is a normalized indicator. Its value comes from comparing like with like: the same qualification rule, the same market segment, the same deal-value definition, and the same measurement window.
The sales velocity formula
| Variable | Definition | Use this evidence | Avoid |
|---|---|---|---|
| Qualified opportunities | Open or newly created opportunities that passed one documented qualification boundary | CRM stage entry event and required fields | All leads, duplicate records, and dead deals |
| Average deal value | Average value attached to the same opportunity population | Closed-won contract value or consistently defined opportunity value | Mixing annual contract value, lifetime value, and one-time fees |
| Win rate | Closed-won opportunities divided by closed-won plus closed-lost opportunities | Closed records from a sufficiently complete cohort | Dividing wins by every raw lead or ignoring losses still open |
| Sales cycle length | Average days from the chosen qualification event to closed-won | Created or qualified timestamp and closed-won timestamp | Mixing lead-to-close and opportunity-to-close definitions |
HubSpot and Pipedrive both describe the standard equation with these four components. The exact labels may differ by CRM, but the boundaries matter more than the label. If one team begins the clock at first website visit and another begins it at qualified opportunity, their velocity figures are not comparable.
Write the units before calculating
Suppose the inputs are 40 qualified opportunities, a $25,000 average deal value, a 25% win rate, and a 45-day average cycle. Convert 25% to 0.25 before multiplication:
(40 × $25,000 × 0.25) ÷ 45 = $5,555.56 per day.
The numerator is $250,000 of expected value across the measured opportunity population. Dividing by 45 days normalizes that expected value by cycle length. A monthly planning view can multiply the daily value by 30.4375, the average number of days per month, producing approximately $169,097.22. That monthly number is still a normalized rate, not a close-date forecast.
Editorial concept images for planning; they are not vendor-interface screenshots.
Three worked sales velocity examples
Example 1: small B2B SaaS team
The team has 40 qualified opportunities, a $25,000 average first-contract value, a 25% win rate, and a 45-day cycle. Its velocity is $5,555.56 per day. If it reduces the cycle by 10% to 40.5 days while holding the other inputs constant, velocity becomes $6,172.84 per day—an 11.1% increase.
The improvement is greater than 10% because cycle length is the divisor. Dividing by 90% of the original cycle produces 1 ÷ 0.9, or 1.111 times the original velocity. This is useful mathematics, but the operational change is only credible if faster movement does not reduce qualification quality or win rate.
Example 2: marketing agency retainers
An agency has 25 qualified opportunities, a $12,000 average first-year retainer value, a 32% win rate, and a 30-day cycle. Its calculation is (25 × $12,000 × 0.32) ÷ 30, which equals $3,200 per day.
The agency should decide whether “deal value” means signed first-year revenue, monthly recurring revenue, or expected gross profit. Any can support an internal model when used consistently, but changing that definition between months creates an artificial trend. A separate delivery-capacity model is also necessary: sales velocity can rise even when the account team cannot onboard the additional work.
Example 3: enterprise sales motion
An enterprise team has 12 qualified opportunities, a $180,000 average first-contract value, an 18% win rate, and a 120-day cycle. Its velocity is (12 × $180,000 × 0.18) ÷ 120, or $3,240 per day.
Combining this enterprise motion with the 30-day agency motion would hide useful differences. Enterprise deals may require security review, procurement, legal approval, and several stakeholders. Calculate velocity separately by materially different segment, product, region, source, or sales motion before creating a company-wide summary.
| Scenario | Opportunities | Deal value | Win rate | Cycle | Velocity/day |
|---|---|---|---|---|---|
| Small B2B SaaS | 40 | $25,000 | 25% | 45 days | $5,555.56 |
| Marketing agency | 25 | $12,000 | 32% | 30 days | $3,200.00 |
| Enterprise motion | 12 | $180,000 | 18% | 120 days | $3,240.00 |
How the four levers change velocity
The three numerator variables have a direct proportional relationship with velocity. If opportunity count rises by 20% and every other input remains fixed, velocity rises by 20%. The same is true for average deal value or win rate. Cycle reduction behaves differently because it is in the denominator.
| Change | Velocity effect | Operational check |
|---|---|---|
| 20% more qualified opportunities | +20% | Did qualification quality and source mix remain stable? |
| 20% larger average deal value | +20% | Did scope, discounting, and delivery cost change? |
| Win rate from 25% to 30% | +20% | Is this a five-point change, supported by completed cohorts? |
| 10% shorter cycle | +11.1% | Did faster movement damage win rate? |
| 20% shorter cycle | +25% | Were approval or handoff delays actually removed? |
A lever analysis should not assume independence. Adding lower-quality opportunities can reduce win rate. Increasing deal size can lengthen the sales cycle. Rushing the cycle can increase losses. Run a combined scenario only after writing the operational reason each input should move and the counter-metric that could deteriorate.
Use counter-metrics
- When increasing opportunity volume, monitor qualification acceptance, no-show rate, and early-stage loss rate.
- When increasing deal value, monitor discount percentage, delivery margin, procurement time, and expansion assumptions.
- When improving win rate, inspect whether representatives are avoiding difficult but valuable opportunities.
- When shortening cycle length, monitor stage regression, late-stage loss, and customer readiness at handoff.
A defensible measurement method
1. Fix a qualification boundary
Write the event that turns a record into an opportunity. Examples include a completed discovery call with documented need, budget range, decision process, and next step. A subjective stage such as “working” is too weak. The boundary should be observable and usable by every representative.
2. Use completed cohorts for win rate and cycle length
A current open pipeline does not yet reveal its final win rate. Calculate historical win rate from closed-won and closed-lost opportunities using the same qualification rule. Calculate cycle length from opportunities that reached closed-won, while separately reviewing closed-lost age so long-running failures are not invisible.
3. Choose one value definition
For a conventional bookings model, use average first-contract value. A SaaS business may run an additional lifetime-value scenario, but it should label the result clearly and keep it separate. Gross profit can support investment decisions, yet it is not directly comparable with a revenue-based velocity series.
4. Segment materially different motions
Separate self-serve, small-business, mid-market, and enterprise pipelines when they have different qualification, pricing, stakeholders, or cycle mechanics. Also inspect inbound, partner, referral, and outbound sources separately before combining them. A blended average can improve simply because the mix shifted toward easier deals.
5. Calculate on a consistent rolling window
A small team can use a rolling 90-day window and update it monthly. A low-volume enterprise team may need a longer window to reduce volatility. Record the window beside the result. Do not compare a 30-day snapshot with a trailing-year average and describe the difference as performance improvement.
Original review template
Record the calculation like an operating decision
| Record | What to capture | Why it matters |
|---|---|---|
| Definition version | Qualification event, value basis, win-rate denominator, cycle start and end | Prevents silent measurement drift |
| Population | Segment, product, region, source, owner group | Keeps unlike motions separate |
| Window | Start date, end date, cohort completeness | Makes trend comparisons reproducible |
| Four inputs | Value, source report, export date, record count | Provides an audit trail |
| Result and decision | Velocity, target lever, owner, next review date | Turns a dashboard number into an action |
| Counter-metric | Quality, margin, late losses, or handoff readiness | Detects harmful optimization |
Common sales velocity mistakes
Counting every lead as an opportunity
Raw lead volume makes the numerator look large while weakening the meaning of win rate. Use a documented qualified-opportunity boundary and remove duplicates, test records, and administratively open dead deals.
Mixing current opportunities with an unrelated historical win rate
If the open pipeline is enterprise outbound but the win rate comes from small-business inbound, the product of those numbers describes neither motion. Match the historical cohort to the current opportunity population as closely as volume permits.
Treating percentage points as percent change
Moving from a 25% win rate to 30% is a five-percentage-point increase and a 20% relative increase. In the formula, 0.30 ÷ 0.25 equals 1.20, so velocity rises 20% when other inputs remain fixed.
Changing the deal-value basis
Switching from monthly recurring revenue to annual contract value creates a twelvefold jump that has nothing to do with sales performance. Store the value definition alongside every result.
Using velocity as a close-date forecast
The formula does not know whether a specific deal is one day or one hundred days old, which stage it occupies, whether procurement has begun, or when seasonal demand changes. Use opportunity-level forecasting and stage-age analysis for timing. Velocity is best for directional comparison and lever diagnosis.
Optimizing the denominator at any cost
A shorter cycle is not automatically healthier. Representatives can manufacture speed by disqualifying complex deals, skipping discovery, or pushing buyers before they are ready. Pair cycle time with win rate, late-stage loss, deal value, and handoff quality.
How to improve sales velocity without damaging quality
- Remove stale pipeline. Close records with no buyer-confirmed next action and report the cleanup separately from true performance change.
- Find the slowest stage. Compare median and average age by stage, source, and segment. Review exceptions rather than guessing.
- Define exit evidence. A deal advances when a customer milestone occurs, not when a seller completes an activity.
- Analyze losses. Use a controlled loss-reason list and inspect a sample of notes each month.
- Improve one constraint. Assign an owner, operational change, counter-metric, and review date to the chosen lever.
- Recalculate with the same definition. Preserve the baseline and disclose any population or methodology change.
Official sources and verification date
The formula and variable definitions were checked on August 11, 2026 against current explanations from HubSpot and Pipedrive. Zendesk also describes sales velocity and pipeline velocity as commonly interchangeable terms in its sales velocity overview. Product terminology and reporting implementations can change; document the definition used in your own CRM.
Frequently asked questions
What is the sales velocity formula?
Sales velocity equals qualified opportunities multiplied by average deal value and win rate, divided by average sales cycle length.
Is sales velocity the same as pipeline velocity?
The terms are commonly used for the same four-variable calculation, although a company should document its own definition and reporting boundary.
Does sales velocity predict exact revenue?
No. Sales velocity is a normalized planning indicator based on averages, not a timing-aware revenue forecast.
How often should a team calculate sales velocity?
A small team can calculate it monthly on a consistent rolling window and review the four underlying inputs every week.
Put the formula into practice
Calculate and share a pipeline scenario
Editorial note: formula definitions and official sources were reviewed August 11, 2026. The worked scenarios are original examples created for this guide and are not performance benchmarks.