Sales Velocity: Formula, Four Levers, and How to Track It

Callia Peterson

Summarize this article with your favorite LLM
Table of contents

Summarize article with your LLM

Sales velocity is the amount of revenue your open pipeline produces per day. The formula is open qualified opportunities multiplied by average won deal value and win rate, divided by sales cycle length in days.

Teams raise it by moving one of four levers: more qualified opportunities, larger deals, a higher win rate, or a shorter cycle.

Revenue is a lagging number. By the time a quarter misses, the cause sits months in the past: a thin pipeline, deals that grew smaller, a win rate that slipped, or a cycle that stretched. Leaders see the miss and ask why, and the CRM offers a dozen charts that each answer a different question.

Sales velocity compresses the pipeline's performance into one rate and, more usefully, splits that rate into four parts that a team can inspect and change.

Many teams calculate velocity once, as a slide in a quarterly review, and never use it again. A single calculation tells you where you are.

A tracked velocity tells you what changed. If velocity fell from last quarter, the four inputs show whether the cause was fewer opportunities, smaller deals, a lower win rate, or slower progress.

Each cause has a different owner and a different fix. Marketing and prospecting affect opportunity volume. Pricing and packaging affect deal value. Qualification and selling skill affect win rate. Process, stakeholder access, and deal hygiene affect cycle length.

The metric has traps. Popular guides use the formula with loose definitions, and loose definitions produce numbers that look precise and mean little.

A team that counts new opportunities in place of open opportunities, or that measures cycle length only on won deals, gets a velocity that overstates its performance.

Enterprise teams face a further problem. Deals take months, involve several stakeholders, and depend on signals that live outside the CRM, so the inputs themselves are hard to trust.

This guide explains sales velocity from first principles. It defines the metric, gives the formula and the exact definition of each input, and walks through a worked example with the arithmetic shown.

The guide is written for sales leaders, revenue operations teams, and analysts who need a reliable velocity number and a way to act on it.

It does not give industry benchmark values, because velocity depends on deal size, market, and motion. It shows how to build your own baseline.

What Is Sales Velocity?

Sales velocity is the rate at which a sales pipeline converts into revenue, expressed as revenue per day.

It answers a practical question: given the deals open today, how much revenue should the pipeline produce each day?

The metric combines four variables.

  • Opportunities. The count of open, qualified deals in the pipeline.

  • Deal value. The average value of a won deal.

  • Win rate. The share of closed deals that were won.

  • Sales cycle length. The average number of days from creation to close.

Velocity as stock and flow

Opportunities are a stock: the number of open deals at one point in time. Cycle length is a duration. Dividing a stock of deals by a duration of days gives a rate of deals closing per day.

This is why the first input must be the open pipeline and not the number of opportunities created in a month. A monthly flow divided by a number of days produces a figure with no clear meaning.

Sales velocity vs related metrics

Metric

What it measures

How it differs from velocity

Sales velocity

Revenue per day from the open pipeline

Combines four drivers into one rate

Pipeline coverage

Pipeline value divided by quota

Shows size, not speed or quality

Win rate

Share of closed deals that were won

One input to velocity

Sales cycle length

Days from creation to close

One input to velocity

Quota attainment

Closed revenue against target

A lagging outcome, not a diagnostic

Forecast accuracy

Closeness of forecast to actual

Measures prediction quality, not pace

Velocity pairs well with pipeline and forecast measures. For related ground, see how to calculate the pipeline needed to hit a revenue target and how to measure revenue forecast accuracy.

The Sales Velocity Formula

Sales velocity = (open qualified opportunities x average won deal value x win rate) / sales cycle length. The output is revenue per day.

The numerator estimates the revenue your open pipeline should produce: the number of deals, times their typical value, times the share you expect to win. The denominator spreads that revenue across the typical time a deal takes to close.

Input definitions that keep the number honest

Input

Use this

Not this

Opportunities

Open, qualified opportunities on the day you measure

Leads, or opportunities created this month

Average deal value

Average value of won deals, using first contract value

Customer lifetime value, or the average of open deals

Win rate

Won deals divided by all closed deals (won and lost) over the same period

Won deals divided by every opportunity ever created

Sales cycle length

Average days from creation to close, for won and lost deals

Won deals only

Merlin5's guide to the B2B sales velocity formula makes the same point about these definitions: the open pipeline, not new opportunities, belongs in the first input, and cycle length should include lost deals.

Read their B2B sales velocity formula walkthrough for a worked example in a different currency and the spreadsheet formulas.

Why each definition matters

  • Open qualified opportunities. Qualification keeps unqualified leads from inflating the count. Define "qualified" once, in writing, and apply it everywhere. See lead qualification process for criteria.

  • Won deal value. Using won deals avoids optimism bias in open deals, which tend to carry placeholder values.

  • Win rate. Dividing by all closed deals avoids the distortion of deals that are still open.

  • Cycle length including lost deals. Lost deals often take as long as won ones. Excluding them makes the cycle look shorter than the pipeline's real pace.

A Worked Example With the Arithmetic Shown

Illustrative example. The figures below are hypothetical and chosen to keep the arithmetic readable. They are not benchmarks.

Input

Value

Open qualified opportunities

80

Average won deal value

$60,000

Win rate

20%

Sales cycle length

120 days

  1. Open pipeline value: 80 x $60,000 = $4,800,000.

  2. Expected won revenue: $4,800,000 x 0.20 = $960,000.

  3. Sales velocity: $960,000 / 120 days = $8,000 per day.

That is about $240,000 per 30 days, or about $2.9 million per year at a steady rate.

A sense check

With 80 open opportunities and a 120 day cycle, roughly two thirds of one opportunity closes per day, so about 20 opportunities close in 30 days.

At a 20% win rate, that is about 4 wins in 30 days. Four wins at $60,000 equals $240,000. The two routes agree because the first input is the open pipeline.

A common spreadsheet error

Enter the win rate as 20% or 0.20. Typing 0.20% makes the spreadsheet read 0.002, which shrinks the result by a factor of 100. Check the unit on every input before trusting the output.

The Four Levers of Sales Velocity

Each lever has a different owner and a different effect, and the sales cycle has a slightly larger effect than the others because it sits in the denominator.

What a 10% improvement is worth

Using the worked example as a baseline of $8,000 per day:

Lever

Change

New value

New velocity per day

Change in velocity

Opportunities

+10%

88

$8,800

+10.0%

Deal value

+10%

$66,000

$8,800

+10.0%

Win rate

+10% (relative)

22%

$8,800

+10.0%

Cycle length

10% shorter

108 days

$8,889

+11.1%

Three levers act in proportion. The cycle acts slightly more strongly, because a 10% reduction in the divisor raises the result by 1 / 0.9, or 11.1%.

Real improvements are rarely equal across levers, so the practical question is which lever your team can move most cheaply.

Lever 1: Opportunities

More qualified opportunities raise velocity when they match the ideal customer profile. Volume without fit adds noise and lowers win rate.

How to improve it:

  1. Tighten the ideal customer profile and target accounts that match it. See ideal customer profile in sales.

  2. Use trigger events and account signals to time outreach. See signal-based prospecting.

  3. Remove stale opportunities from the pipeline so the count reflects real deals.

  4. Track qualified opportunity creation by source and cut sources that do not convert.

Lever 2: Average deal value

Larger won deals raise velocity directly. Deal value depends on packaging, pricing, scope, and who is involved in the decision.

How to improve it:

  1. Engage senior stakeholders earlier in the cycle.

  2. Link the offer to the buyer's stated business outcome and not only to features.

  3. Review discounting practices and approval rules for avoidable value loss.

  4. Plan expansion into existing accounts so deal value grows over time.

Lever 3: Win rate

A higher win rate comes from better qualification, stronger discovery, and fewer deals that stall without a decision.

How to improve it:

  1. Qualify earlier and drop poor-fit deals faster, which raises the win rate and shortens the cycle together.

  2. Map the buying committee and engage every key stakeholder. See buying committee mapping and multi-threading.

  3. Run win and loss reviews on a fixed schedule and feed findings back into qualification.

  4. Watch for deal risk signals such as silent stakeholders and slipped close dates. See deal risk detection with revenue agents.

Lever 4: Sales cycle length

A shorter cycle raises velocity and also frees capacity for new opportunities. Cycles lengthen when stakeholders are missing, justification is unclear, or next steps are vague.

How to improve it:

  1. Define a clear next step and date at the end of every buyer interaction.

  2. Assemble purchase-justification material early so the buyer does not wait on it.

  3. Remove internal handoff delays between roles.

  4. Find the stage where deals wait longest and address that stage first. See sales cycle.

Interactions between levers

Levers move together. Raising the price may lower win rate. Chasing volume may lengthen the cycle as reps spread thin. Pursuing larger deals may extend the cycle. Evaluate each change on velocity as a whole, not on one input in isolation.

How to Track Sales Velocity Over Time?

Track velocity on a fixed schedule, with fixed definitions, and break it down by segment, source, rep, and stage. A single total hides the drivers.

Cuts that explain the number

Cut

What it reveals

Typical action

Segment (SMB, mid-market, enterprise)

Which motion produces revenue fastest

Shift resources, adjust targets by segment

Lead or opportunity source

Which channels produce pipeline that closes

Fund the sources that convert

Rep or team

Where coaching helps

Coach on the weakest lever

Pipeline stage

Where deals slow down

Fix the stage with the longest wait

Product or offer

Which offers win

Adjust packaging and focus

Region

Where cycle length and win rate differ

Adjust territory plans

Ranking and sorting by velocity

Teams often want to sort segments, sources, or reps by velocity. Rank only comparable groups, since velocity depends on deal size and cycle length.

A high-value enterprise segment may show lower daily velocity than a fast mid-market segment while producing more revenue per rep.

Pair the ranking with deal count and revenue contribution so the order is not misleading.

Illustrative segment comparison

The figures are hypothetical.

Segment

Opportunities

Average won deal value

Win rate

Cycle length

Velocity per day

Mid-market

120

$25,000

25%

60 days

$12,500

Enterprise

40

$150,000

15%

180 days

$5,000

Arithmetic: mid-market is 120 x $25,000 x 0.25 / 60 = $12,500. Enterprise is 40 x $150,000 x 0.15 / 180 = $5,000.

The mid-market segment produces more revenue per day, and the enterprise segment produces larger deals over a longer cycle. Each needs its own targets, so compare each segment to its own history.

Cadence and baselines

  • Calculate velocity weekly or monthly on the same day, using the same definitions.

  • Keep a baseline for each segment and compare against it, not against an outside average.

  • Review which lever moved, using the four inputs, before explaining the change.

  • Record changes to qualification rules or stage definitions, since they shift the inputs.

For dashboards that bring these views together, see revenue operations dashboards for lead sources, win rate, and quota.

Common Calculation Errors

Most velocity mistakes come from input definitions, not from the formula.

  1. Counting new opportunities instead of open opportunities. The formula needs the open pipeline.

  2. Including unqualified leads. Inflates the count and lowers the win rate over time.

  3. Measuring cycle length on won deals only. Understates the real cycle.

  4. Dividing wins by every opportunity ever created. Distorts win rate with open and stale deals.

  5. Using lifetime value as deal value. Overstates the first deal.

  6. Mixing segments. An average across SMB and enterprise describes neither.

  7. Changing definitions mid-year. Breaks comparison over time.

  8. Entering percentages incorrectly. A misplaced decimal changes the result by a factor of 100.

  9. Using stale CRM data. Deals with outdated stages and close dates distort every input.

  10. Treating velocity as a forecast. It describes pipeline pace, and forecasts require stage-level judgment.

Sales Velocity for Enterprise Deals

Enterprise deals strain the simple formula because cycles run long, deals involve many stakeholders, and the signals that decide outcomes sit outside the CRM.

Where the formula bends

  • Long cycles. A 180 day cycle means the open pipeline reflects decisions made months earlier. Use a rolling window and compare like with like.

  • Small counts. A few large deals make the win rate noisy. Track it over a longer period and note the sample size.

  • Buying committees. A deal may stall because one stakeholder is missing. The CRM shows the stage, and it does not show the missing voice.

  • Multi-year and expansion deals. Define whether deal value is first-year or total contract value, and apply the choice consistently.

  • Stage inflation. Reps may advance deals optimistically. Use evidence-based stage criteria.

The context gap in velocity data

Enterprise revenue teams lose deals when deal-moving signals are scattered outside the CRM, across the warehouse, the inbox, call transcripts, and product data. Rox calls this the context gap. The effect on velocity is direct.

If purchase-justification context is not assembled, the cycle lengthens. If representatives spend hours finding information, they work fewer opportunities. If expansion and renewal opportunities surface late, deal value and opportunity count suffer.

How Revenue Intelligence Supports Velocity Tracking

Revenue intelligence connects deal, activity, and conversation data so that velocity inputs come from one trusted source and the reasons behind a change are visible.

For background, read revenue intelligence and sales pipeline intelligence.

A revenue intelligence approach supports velocity work in four ways.

  1. Consistent inputs. One definition of qualified, won, and closed feeds every report.

  2. Stage-level visibility. Time in stage shows where cycles stretch.

  3. Signal context. Conversation and engagement data explain why a deal stalled.

  4. Early warning. Risk signals surface before a deal slips.

How Rox approaches it?

Rox is warehouse-native. Its context graph is built from the full data warehouse and unifies internal and external signals into a single system of context.

Rox assigns one dedicated revenue agent to each account, and the agent retains account context, monitors signals continuously, and acts from rep-set intent.

That design supports revenue orchestration: coordinating who acts, when, and on what information across the account lifecycle, so that velocity inputs reflect the whole account and not only CRM fields.

Human oversight

AI-generated outputs are informational and should be reviewed by authorized personnel before action. Features described as automated operate within user-defined parameters and require initial configuration and ongoing oversight.

Review the definitions that feed velocity, sample the deals behind a change, and keep a person responsible for conclusions that affect targets or compensation.

See how Rox unifies deal-moving signals into one system of context: Explore Rox's revenue agent capabilities.

A Worked Walkthrough: Diagnosing a Drop in Velocity

Scenario. A team's velocity fell from the prior quarter, and leadership wants to know why. The figures below are hypothetical.

Input

Prior quarter

Current quarter

Open qualified opportunities

80

78

Average won deal value

$60,000

$59,000

Win rate

20%

19%

Sales cycle length

120 days

144 days

Velocity per day

$8,000

$6,072

Arithmetic: current velocity is 78 x $59,000 = $4,602,000 of open pipeline. Multiplied by a 0.19 win rate, that is $874,380 of expected won revenue.

Divided by 144 days, velocity is about $6,072 per day, down about 24% from $8,000.

  1. Find the biggest mover. Opportunities fell 2.5%, deal value fell 1.7%, win rate fell 5% (relative), and cycle length rose 20%.

  2. Isolate the cycle. The cycle explains most of the drop, since it moved the most.

  3. Locate the stage. Time-in-stage data shows deals waiting at the legal and security review stage.

  4. Check the cause. Reviews show missing security documentation at several accounts.

  5. Act. The team prepares standard security material earlier in the cycle.

  6. Re-measure. The team tracks cycle length and velocity the following quarter against the same baseline.

This structure is a template to adapt, and it does not promise any outcome. Use your own data.

Conclusion

Sales velocity turns a pipeline into a rate and then splits that rate into four parts a team can act on. The formula is simple: open qualified opportunities times average won deal value times win rate, divided by sales cycle length.

The value of the metric depends on definitions. Use open qualified opportunities, won deal value, a win rate based on all closed deals, and a cycle length that includes lost deals.

Tracking matters more than a single calculation. Compare velocity over time, by segment, source, rep, and stage, and read the four inputs to see which lever moved before explaining the change.

A shorter cycle has a slightly larger effect than an equal gain in the other levers, and levers interact, so judge changes on velocity as a whole.

Enterprise teams need extra care. Long cycles, small counts, buying committees, and signals that live outside the CRM make the inputs harder to trust. Closing the context gap by unifying warehouse, inbox, call transcript, and product data gives velocity a firmer base.

Rox's warehouse-native system of context and account-dedicated agents support that base, with people reviewing the definitions and the conclusions. To start, write down your four input definitions, calculate velocity by segment for the last two quarters, and identify the lever that moved most.

Talk to the Rox team about building a single system of context for your revenue data: Visit Rox.

Frequently Asked Questions

What is sales velocity?

Sales velocity is the revenue your open pipeline produces per day. It combines open qualified opportunities, average won deal value, win rate, and sales cycle length into one rate.

What is the sales velocity formula?

Sales velocity = (open qualified opportunities x average won deal value x win rate) / sales cycle length in days. The result is revenue per day.

How do you calculate sales velocity step by step?

Multiply the number of open qualified opportunities by the average won deal value. Multiply that by the win rate. Divide the result by the average sales cycle length in days. Check that the win rate is entered as a percentage and not as a tiny decimal.

What counts as an opportunity in the formula?

Use open, qualified opportunities on the day you measure. Do not use leads, and do not use opportunities created during the month, since the formula divides a stock of deals by a number of days.

How should I calculate win rate for sales velocity?

Divide won deals by all closed deals, both won and lost, over the same period. Do not divide by every opportunity ever created, since open and stale deals distort the result.

Should cycle length include lost deals?

Yes. Lost deals often take as long as won ones, and excluding them makes the cycle look shorter than the pipeline's real pace.

How do you improve sales velocity?

Move one of four levers: add qualified opportunities that fit your ideal customer profile, raise average won deal value, improve win rate through better qualification and stakeholder coverage, or shorten the sales cycle by fixing the stage where deals wait longest. Judge each change on velocity as a whole.

Which lever has the biggest effect on sales velocity?

Equal percentage gains in opportunities, deal value, and win rate each raise velocity by the same percentage. A 10% shorter cycle raises velocity by about 11.1%. In practice, the largest gain comes from the lever your team can move most cheaply.

What is a good sales velocity?

It depends on deal size, segment, and motion, so a generic figure misleads. Build a baseline from your own history and compare each segment against its own past results.

How do you track sales velocity by segment?

Calculate velocity separately for each segment, source, rep, or stage using the same definitions and schedule. Compare each group to its own baseline, and pair rankings with deal count and revenue contribution.

Why is enterprise sales velocity harder to measure?

Enterprise cycles are long, deal counts are small, buying committees are large, and key signals sit outside the CRM. Use a rolling window, define deal value consistently, apply evidence-based stage criteria, and unify signals from the warehouse, inbox, call transcripts, and product data.

Is sales velocity the same as a sales forecast?

No. Velocity describes the pace at which the current pipeline converts into revenue. A forecast predicts outcomes using stage-level judgment, history, and risk. Use velocity to diagnose and forecast accuracy measures to check predictions.

How does revenue intelligence help with sales velocity?

Revenue intelligence connects deal, activity, and conversation data, so velocity inputs follow one set of definitions and the causes of a change are visible through time in stage and signal context. People should review the inputs and conclusions before acting.

How often should I recalculate sales velocity?

Weekly or monthly, on the same day, with the same definitions. Record any change to qualification rules or stage definitions, since those shift the inputs.

Summarize this article with your favorite LLM

Rox is committed to the privacy and security of its users. Customer data processed through the Rox platform is encrypted in transit and at rest using AES-256 encryption and is never used to train generalized machine learning models. Rox maintains SOC 2 Type II compliance and undergoes independent third-party security audits on an annual basis. All AI-generated outputs, including but not limited to prospect recommendations, message drafts, meeting summaries, and pipeline scoring, are provided for informational purposes and should be reviewed by authorized personnel before any action is taken. Performance metrics referenced on this website, including pipeline generation figures, response rates, and revenue impact, reflect results reported by individual customers under specific configurations and may not be representative of all deployments. Actual results will vary based on factors including but not limited to data quality, CRM configuration, outreach volume, market conditions, and target audience. Rox does not guarantee specific revenue outcomes. The Rox platform integrates with third-party services including Salesforce, HubSpot, Gmail, Microsoft Outlook, Slack, and others; availability and functionality of third-party integrations are subject to the respective providers' terms of service and may change without notice. Features described as "autopilot," "autonomous," or "automated" operate within user-defined parameters and require initial configuration and ongoing oversight. Rox, the Rox logo, and "Revenue on Autopilot" are trademarks of Rox Data Corp. All other trademarks are the property of their respective owners. Service availability is subject to the terms outlined in your enterprise agreement. For questions regarding data processing, compliance certifications, or platform capabilities, contact security@rox.com.

Rox is committed to the privacy and security of its users. Customer data processed through the Rox platform is encrypted in transit and at rest using AES-256 encryption and is never used to train generalized machine learning models. Rox maintains SOC 2 Type II compliance and undergoes independent third-party security audits on an annual basis. All AI-generated outputs, including but not limited to prospect recommendations, message drafts, meeting summaries, and pipeline scoring, are provided for informational purposes and should be reviewed by authorized personnel before any action is taken. Performance metrics referenced on this website, including pipeline generation figures, response rates, and revenue impact, reflect results reported by individual customers under specific configurations and may not be representative of all deployments. Actual results will vary based on factors including but not limited to data quality, CRM configuration, outreach volume, market conditions, and target audience. Rox does not guarantee specific revenue outcomes. The Rox platform integrates with third-party services including Salesforce, HubSpot, Gmail, Microsoft Outlook, Slack, and others; availability and functionality of third-party integrations are subject to the respective providers' terms of service and may change without notice. Features described as "autopilot," "autonomous," or "automated" operate within user-defined parameters and require initial configuration and ongoing oversight. Rox, the Rox logo, and "Revenue on Autopilot" are trademarks of Rox Data Corp. All other trademarks are the property of their respective owners. Service availability is subject to the terms outlined in your enterprise agreement. For questions regarding data processing, compliance certifications, or platform capabilities, contact security@rox.com.