Pipeline value answers "how much could close." Sales velocity answers "how much will close, how soon." The four inputs are the only levers that move it, which is why every revenue team eventually tracks them separately.
Sales velocity is the rate at which a sales team generates revenue. The formula is the number of qualified opportunities multiplied by average deal size multiplied by win rate, then divided by sales cycle length in days. The result is revenue per day, which forecasts how fast money actually flows out of the pipeline instead of how big the pipeline looks on paper.
The six things to understand about sales velocity before building a dashboard or arguing about one in a revenue review.
Sales velocity equals the number of qualified opportunities multiplied by average deal size multiplied by win rate, divided by the sales cycle length in days. The output is a dollar amount per day. It is the only revenue metric that combines volume, value, conversion, and speed in a single number.
A big pipeline looks healthy until you ask how fast it converts. Sales velocity measures the rate of revenue production, not the stockpile. Two teams with identical pipeline value can have very different velocities, and the one with higher velocity hits plan while the other misses, every time.
Those four inputs are the only things that move sales velocity. Every improvement initiative, every enablement program, every hire eventually shows up in one of them. Framing the number as four levers instead of one metric is what turns sales velocity from a KPI into an operating system.
SMB teams run high opportunity counts and short cycles with modest deal sizes. Enterprise teams run low opportunity counts and long cycles with large deal sizes. The absolute velocity numbers differ by orders of magnitude. Compare velocity against your own prior quarters, not against a published average that mixes segments.
Three errors break velocity math: using closed-won revenue in the formula instead of qualified opportunity count, averaging across segments so trends disappear, and mixing time windows (opportunities from this quarter, win rate from last year). Each one makes the headline number look fine while hiding the diagnosis.
Opportunity count, deal size, win rate, and cycle length are all native CRM metrics. A CRM that stores stage history, close dates, amounts, and outcomes computes velocity in one query. Teams rebuilding it in a spreadsheet lose a quarter to data cleanup every time an exec asks the question.
The sales velocity equation is simple arithmetic, but the inputs are where every team quietly disagrees. The formula is the number of qualified opportunities multiplied by the average deal size multiplied by the win rate, then divided by the average sales cycle length in days. The output is revenue per day. Each input needs a written definition that stays consistent across quarters, or the number drifts and the trend becomes unreadable. The point of sales velocity is to compare one period to the next, which only works if the measurement rules do not change.
Count the qualified opportunities created or active in the measurement window. Raw leads do not belong in this input; a lead becomes an opportunity when a rep has confirmed fit and interest. Using lead count inflates the number and makes velocity rise even when nothing is actually closing faster.
Pull the average contract value on deals that have actually closed-won in the period. Open deals carry hopeful amounts that reps have not committed to. Using open-deal amounts in the velocity formula produces an aspirational number, not a measurable one. Measure deal size on outcomes, not forecasts.
The same win rate you use everywhere else: closed-won divided by the sum of closed-won plus closed-lost in the window. If no-decision deals get hidden in an "unqualified" bucket, win rate inflates and velocity follows. Count no-decision as a loss so the velocity number reflects real conversion.
Average the days between opportunity creation and the closed-won date, using closed-won deals only. Mixing in closed-lost cycle times blends two different motions. If deals get reopened, use the final close date, not the first attempt. Round to whole days so the trend reads clearly month over month.
The result of the formula is revenue per day, which is a rate, not a total. Multiplying it by the number of days in a quarter gives the quarterly run rate. Reporting velocity as a daily figure makes period comparisons honest, since quarters have different numbers of selling days.
Write each input definition down. Apply it to every quarter, every segment, every rep. If a definition has to change, change it going forward and keep the old series for comparison. Nothing erodes trust in sales velocity faster than retroactive re-definitions that make last quarter suddenly look better.
Because the formula has four inputs, there are exactly four ways to raise sales velocity. Every revenue initiative, every piece of enablement, every hire eventually shows up in one of them. Framing improvements as levers instead of as projects forces honesty: before you start the work, pick the lever you believe it will move, and after the quarter, check whether that lever actually moved. The teams that do this get out of the "we tried a lot of things and the number went up" problem and into "we moved deal size by eight percent and velocity followed."
More qualified opportunities raises velocity proportionally. The levers are outbound capacity, inbound demand generation, partner referrals, and tightening lead qualification so fewer good opportunities get dropped. Chasing raw lead volume without qualification does not move velocity; it inflates the top line while cycle length and win rate quietly degrade.
Average deal size is moved by selling to larger segments, bundling more products, or expanding scope within accounts. Pricing changes also move it, but take longer to appear in the average because they only affect new deals. A ten percent lift in deal size produces a ten percent lift in velocity, holding everything else constant.
Win rate rises when discovery qualifies out bad-fit deals early and when the team hunts in the segments where it already wins. Deal reviews on open opportunities catch stalled deals before the close call. Loss analysis on closed-lost deals surfaces patterns that let the team avoid losing the same way twice.
Cycle length drops when the process between stages is instrumented. Automated proposal generation, electronic signature, pre-filled security questionnaires, and routing rules that get the right stakeholder on the call all compress days out of the cycle. Every day saved raises velocity, because the denominator shrinks.
A five percent lift in each of the four inputs produces roughly a twenty-two percent lift in velocity, because they multiply. One lever moved hard is usually less valuable than four levers moved a little, and much more expensive to achieve. Spread the effort across all four inputs for the best compound return.
Moving upmarket for larger deals usually lengthens the cycle and lowers the win rate. Tightening discovery raises win rate but can shrink opportunity count. Velocity captures the net effect of these tradeoffs in one number, which is the whole point. A lever that improves one input while cratering another produces no net gain.
There is no universal good number for sales velocity because the inputs vary so much by segment. SMB teams typically run high opportunity counts, short cycles under forty-five days, win rates of twenty to thirty percent, and smaller deal sizes. Enterprise teams run fewer opportunities, cycles of six to twelve months, win rates of ten to twenty percent, and large deal sizes. The absolute velocity numbers can differ by an order of magnitude between the two, and comparing them directly reads as a diagnosis problem, not a performance problem. The right benchmark is your own trend line over the last four to eight quarters, segmented the same way every time.
SMB sales teams usually see opportunity counts in the hundreds per quarter, cycles under forty-five days, win rates of twenty to thirty percent, and modest average deal sizes. Velocity is sensitive to opportunity count and cycle length. The highest leverage is usually in top-of-funnel supply and in automation that compresses the cycle.
Mid-market cycles land between sixty and one hundred twenty days, win rates between fifteen and twenty-five percent, and deal sizes several multiples of SMB. Velocity in mid-market is sensitive to all four levers in roughly equal weight, which is why mid-market teams tend to run the most structured deal reviews.
Enterprise cycles run six to twelve months or longer, win rates of ten to twenty percent, and deal sizes an order of magnitude above mid-market. Velocity is dominated by deal size and cycle length. Small percentage improvements in cycle length produce the largest absolute velocity gains, because the denominator is so large.
Deals with existing customers close faster, at higher win rates, and often with better deal sizes. Expansion velocity routinely runs two to four times new-logo velocity. Blending them into one headline number flatters new-logo acquisition and hides whether top-of-funnel is actually producing.
Inbound deals close faster and at higher win rates because the prospect already raised a hand. Outbound deals carry longer cycles and lower win rates but often larger deal sizes and better ICP fit. The two motions should be measured separately, because the levers that move one may not move the other.
A velocity trend rising fifteen percent quarter over quarter is a healthier signal than a flat industry-leading number. The absolute figure depends on segment, product, and competition. The trend reflects execution changes you actually control. Report both, but drive decisions off the trend.
Most sales velocity dashboards lie, usually by accident. The errors cluster around three themes: using closed-won revenue instead of qualified opportunity count in the formula, failing to segment so blended inputs hide real movement, and mismatching the time periods of the inputs so opportunities from this quarter get divided by last year is cycle length. Fixing these does not require new software. It requires a short written definition, segmented reporting, and the discipline to apply the rules the same way every quarter.
The most common mistake is multiplying closed-won revenue by win rate and dividing by cycle length. That double-counts outcomes: closed-won revenue already reflects win rate. The input is qualified opportunity count, which measures pipeline supply before conversion. Mixing the two produces a number that moves without any underlying execution change.
A team that sells SMB, mid-market, and enterprise together will see a blended velocity that reflects none of the three. Deal mix shifts between quarters change the headline number without any real execution improvement. Report velocity by segment, every time, and only roll up for leadership summaries.
Opportunity count from this quarter divided by win rate from the last twelve months produces a number that is neither current nor historical. Match the measurement windows for all four inputs. If velocity is quarterly, every input is quarterly, every time. Different windows is the sneakiest form of velocity error because the math looks correct.
Raw leads are not qualified opportunities. Counting them inflates the input, which inflates velocity, which hides a conversion problem downstream. Define qualified opportunity explicitly (fit confirmed, interest confirmed, next step scheduled) and only count those. Lead-to-opportunity ratio is a separate upstream metric.
Average deal size should be computed from closed-won deals. Open deals carry rep-entered amounts that have not been committed to by the customer and that reps tend to inflate. Using open-deal amounts in the velocity formula produces an aspirational velocity, not a measurable one.
Deals that stalled or ghosted eventually close somehow. If they land in an "unqualified" or "disqualified" bucket outside the win rate denominator, velocity inflates. Count no-decision as a loss, then track the no-decision ratio separately as a leading indicator of discovery quality.
The reason sales velocity shows up as a CRM metric and not a spreadsheet metric is that a CRM stores the four inputs natively. Opportunities are records with a created date and a qualification stage. Deal size is the amount field on closed-won deals. Win rate is a one-line query over the outcome field. Cycle length is the difference between the created date and the closed-won date. A CRM that stores stage history and outcomes correctly computes velocity in one query, segmented however the team wants to slice it. Teams rebuilding velocity in a spreadsheet lose a quarter to data cleanup every time leadership asks the question, and the number drifts the moment one rep updates a deal differently from another.
A CRM filters opportunities by qualification stage, created date range, segment, source, and owner in a single query. Rebuilding this in a spreadsheet means exporting raw deal data, filtering by hand, and recomputing every time. The CRM version refreshes automatically and stays consistent across every dashboard that uses it.
The amount field on each deal, averaged over closed-won deals in the window, segmented however leadership asks. A CRM computes this in milliseconds. The spreadsheet version requires exporting the deal list, filtering out losses, and manually averaging, which is why most spreadsheet velocity dashboards quietly use blended data.
Win rate is closed-won divided by closed-won plus closed-lost, pulled from the outcome field on each deal. A CRM that captures no-decision as a loss reason reports an honest win rate out of the box. Teams that bury no-decision in a separate bucket get inflated win rates and inflated velocity.
The gap between opportunity created and closed-won, averaged across the segment. A CRM with stage history stores every stage transition timestamp, so cycle length can also be decomposed into days per stage. That decomposition is where cycle-shortening work gets targeted, instead of applied vaguely to the whole motion.
A CRM that computes all four inputs natively renders a velocity dashboard sliced by segment, source, rep, and quarter in one place. Leadership checks the number without a sales-ops rebuild every Friday. The team argues about the number only when it moves, not about whether the measurement is correct.
Without a CRM, velocity gets built in a quarterly spreadsheet that pulls data from three sources, filtered by hand, with definitions that drift between quarters. The number is often technically correct, but nobody trusts it enough to act on. The real cost is not the spreadsheet time, it is the quarterly re-litigation of what the number means.
Strkr derives opportunity count, deal size, win rate, and cycle length natively, so the velocity number ties back to the deals your team is actually working. Segment, source, rep, and cohort views come out of the same dataset instead of three different exports.
Sales velocity equals the number of qualified opportunities multiplied by the average deal size multiplied by the win rate, divided by the average sales cycle length in days. The result is revenue per day. Multiplying by the number of selling days in a quarter gives the quarterly run rate for the team.
Pipeline value is the total dollar amount of open opportunities. Sales velocity measures how fast that pipeline turns into revenue. Two teams with the same pipeline value can have very different velocities, because velocity reflects win rate and cycle length in addition to volume and deal size.
There is no universal benchmark because the inputs vary so much by segment. SMB velocity is driven by volume and short cycles, enterprise velocity by deal size and long cycles, and the absolute numbers can differ by an order of magnitude. The right comparison is your own trend over the last four to eight quarters, segmented the same way every time.
The formula has four inputs, so there are four levers: raise qualified opportunity count, raise average deal size, raise win rate, or shorten the sales cycle. The fastest gains usually come from tighter discovery (which raises win rate) and from automating friction between stages (which shortens the cycle). Small gains in each of the four compound into a larger total lift.
No. The input is qualified opportunity count, not revenue. Using closed-won revenue double-counts outcomes, because win rate is already in the formula. The purpose of velocity is to measure how fast opportunities convert into revenue, so the opportunity count is the right numerator ingredient.
Monthly for operational diagnosis, quarterly for strategic trend reading. The quarter is the right window for most B2B sales motions because enough deals have closed to see signal above noise. Weekly velocity is usually too noisy to act on, outside of very high-volume transactional sales teams.
Pipeline coverage tells you whether you have enough open deals to hit a target. Sales velocity tells you how fast those deals will convert. A pipeline with high coverage and low velocity can still miss a quarter if the cycles stretch. Velocity is the better forward-looking signal because it captures speed in addition to volume.
A CRM that stores opportunity records with qualification stage, amount, created date, closed-won date, and outcome is the minimum. All four inputs for the velocity formula come out of that same dataset in one query. Measuring velocity in a spreadsheet is possible but fragile: the data drifts, the definitions shift, and the number stops being trusted inside two quarters.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
