Browser-local calculator · Account-free
Sales Velocity Calculator: Baseline, Scenario, and Sensitivity
Calculate sales velocity from aligned opportunity, value, win-rate, and cycle inputs; compare a scenario and inspect sensitivity.
- Method owner
- Anastasiia Krynytska
- Reviewed
- 10 Sep 2026
- Reading
- 9 min read
Practical answer
What this resource does
The calculator returns the arithmetic throughput rate implied by one declared input set. It is not a forecast, grade, or causal recommendation.
- No lead gate. Open, calculate, or download directly.
- Visible method. Definitions, formulas, ownership, and invalid states stay inspectable.
- Human authority. The asset supports a decision; it never owns one.
Browser-local tool · v1
Calculate sales velocity
Inputs stay in memory, are never submitted, and clear on refresh.Sales velocity estimates how much revenue moves through a defined sales population per unit of time. The calculator uses four inputs—eligible opportunities, average deal value, win rate, and average sales-cycle length—and makes the population, period, units, formula, and assumptions visible. It runs entirely in the browser, without an account, cookies, LocalStorage, or server-side storage of entered values.
The result is not a forecast and not a grade. It is a rate implied by the declared inputs. Use it to inspect the relationship between volume, value, conversion, and time; compare aligned populations; and test scenarios. Do not present it as realized revenue, cash collection, or proof that changing one input will cause the calculated outcome.
Salesforce explains the standard sales-velocity formula, while its pipeline-review guidance illustrates why forward-looking actions and exit criteria belong in the surrounding operating process. This implementation adds a strict input contract, baseline-versus-scenario comparison, sensitivity ranking, validation states, and explicit boundaries with pipeline coverage and forecast.
01 / Method
Formula and units
Sales velocity = opportunities × average deal value × win rate ÷ average sales-cycle length.If opportunity count is a count, average deal value is dollars per opportunity, win rate is a decimal, and cycle length is days, the output is dollars per day. The same formula can produce euros per week or another valid rate when all units are declared and aligned. The calculator never performs currency conversion.
Example: 50 eligible opportunities × $20,000 average deal value × 25% win rate ÷ 80 days equals $3,125 per day. This does not mean exactly $3,125 will close every day. It describes the throughput implied by a simplified, steady input set.
02 / Method
Define the eligible population
Opportunity count must refer to a declared population, not every CRM record with a value. Specify segment, team, opportunity type, creation or close cohort, stage boundary, geography, currency, and observation window. Exclude duplicates, tests, and records outside the chosen motion according to a documented rule.
A snapshot count and a cohort count are not automatically comparable. A snapshot reports eligible open opportunities at an as-of time. A cohort reports opportunities entering under a defined condition during a period. Choose the model that matches the question and use the same approach across all four inputs.
The calculator requests a population label and observation dates alongside the number. If users omit this context, arithmetic can still be shown, but the result carries an alignment warning.
03 / Method
Average deal value
Average deal value is the arithmetic mean value for the relevant population:
Average deal value = total comparable deal value ÷ number of comparable deals.Declare whether value means annual contract value, total contract value, recurring revenue, gross revenue, or another measure. Do not combine these in one average. Decide how to treat multi-currency records, services, usage estimates, renewals, expansions, downsells, refunds, and outliers.
The mean can be unstable when a few large deals dominate. The result panel therefore requests deal count and can display an optional median or concentration note, though the velocity formula continues to use the declared average. Segmenting the population may be more informative than adjusting away inconvenient records.
04 / Method
Win rate
Win rate = won opportunities ÷ eligible decided opportunities.The numerator and denominator must share the same cohort and outcome rule. “Decided” commonly means won plus lost; open opportunities are not included until resolved, unless a different method is declared. Record how no-decision, duplicate, disqualified, abandoned, and reopened opportunities are treated.
Win rate must be greater than or equal to 0% and less than or equal to 100%. Entering 25 means 25%, and the interface visibly converts it to 0.25 in the formula. A very small number of decided opportunities creates a fragile estimate; the calculator flags low counts without inventing a confidence interval.
Do not mix an enterprise win rate with a blended opportunity count or an opportunity-stage win rate with a lead-stage population. Review the broader Sales KPI guide when selecting the denominator.
05 / Method
Average sales-cycle length
Average sales-cycle length = sum of elapsed time from declared start to declared end ÷ eligible won deals.Define start and end events. Start might be qualified opportunity creation, accepted opportunity, or another durable event. End might be closed won, contract signature, or payment. The calculator cannot reconcile inconsistent event definitions.
Calendar days and business days are different units. Choose one. Decide how pauses, reopened deals, backfilled dates, mergers, and missing timestamps are handled. Cycle length must be greater than zero. A zero-day result may be valid for a specific transactional workflow, but it cannot be used as a denominator in this formula; use a smaller time unit or a different throughput metric.
Average cycle length based only on won deals can produce survivorship effects. Long-running open opportunities and lost deals may represent material capacity. Use stage aging, time-to-loss, and open-duration distributions as companion measures.
06 / Method
Baseline mode
Baseline mode accepts one aligned input set and returns:
- implied sales velocity in selected currency per selected time unit;
- the substituted formula;
- implied won value in the input population (
opportunities × average deal value × win rate); - declared cycle length;
- population and period labels;
- warnings and missing assumptions;
- a copyable text summary.
The interface displays full input precision and rounds only the visible result. It does not map the number to “poor,” “average,” or “excellent.” There is no universal sales-velocity benchmark that applies across segments, currencies, revenue definitions, stages, and sales motions.
07 / Method
Scenario mode
Scenario mode places a second input set beside the baseline. It reports absolute and percentage change in each driver and in calculated velocity. A percentage change is unavailable when the baseline value is zero. The comparison remains descriptive.
For example, a manager may model 50 opportunities, $20,000 average value, 25% win rate, and 80 days against a scenario of 50 opportunities, $20,000, 30%, and 75 days. Baseline velocity is $3,125/day. Scenario velocity is $4,000/day, an arithmetic increase of $875/day or 28%.
That 28% is not a predicted improvement. The scenario changes two assumptions and does not establish that coaching, tooling, pricing, or process will achieve them. The result should be used to set a testable operating hypothesis and measurement plan.
08 / Method
Sensitivity analysis
The sensitivity panel answers: if each input changes independently by a user-selected relative amount, how much does the calculated result change? For the three multiplicative numerator inputs, a 10% relative increase produces a 10% velocity increase, holding everything else constant. For cycle length, a 10% decrease produces an 11.11% velocity increase because the input is in the denominator.
The interface computes one-at-a-time alternatives and ranks the absolute numerical effect. It does not recommend which lever to pursue. Feasibility, causality, cost, risk, and interaction matter. Increasing opportunity volume may lower fit or win rate; increasing price may affect conversion and cycle; shortening cycles may change deal mix. The simple formula does not model these interactions.
Use sensitivity to identify which assumption deserves better evidence, not to claim that the easiest spreadsheet change is the best strategy.
09 / Method
Sales velocity versus adjacent metrics
Pipeline coverage compares eligible pipeline value with a target. Luck My Sales defines its house version as MEDDPICC-qualified pipeline divided by the aligned target. Coverage is a stock-to-target relationship; velocity is a throughput rate.
Weighted pipeline sums opportunity value multiplied by declared probabilities. It describes a probability-weighted stock and depends on model calibration. It is not sales velocity.
Forecast estimates an expected outcome for a future period under a declared method. A forecast may use pipeline state, seller judgment, historical behavior, timing, and other features. Velocity alone is not a forecast.
Quota attainment is actual credited revenue divided by assigned quota for the same period. It is an outcome ratio, not a throughput driver.
Sales cycle is one input to velocity and should also be examined as a distribution. Reducing the mean by excluding long or lost deals does not improve the process.
Use the weekly pipeline review workbook to inspect coverage, movement, qualification evidence, and actions. Use the calculator when the specific question is how the four declared inputs relate arithmetically.
10 / Method
Data extraction protocol
For a reproducible baseline, save the source system, query or export logic, as-of timestamp, field mapping, filters, exclusions, currency rule, and row count. Keep stable opportunity IDs so aggregates can be reconciled. Do not paste confidential opportunity data into the calculator; it only needs aggregate inputs.
Check for duplicates, missing close outcomes, zero or negative values, mixed currencies, inconsistent stage histories, backfilled timestamps, and test records. Report the count and value affected by exclusions. If data quality is insufficient, label the result provisional rather than filling gaps with estimates that look observed.
Compare periods only after checking mix. A faster velocity may result from smaller deals, a different segment, a backlog release, seasonal timing, or changed opportunity definitions. Preserve the prior metric contract when possible; when it changes, restate history or mark the discontinuity.
11 / Method
Worked examples
All examples are illustrative.
Aligned baseline: 80 eligible opportunities, €15,000 average deal value, 20% win rate, and a 60-calendar-day average cycle.
80 × €15,000 × 0.20 ÷ 60 = €4,000 per calendar day.Implied won value in the population is €240,000. The rate is meaningful only within the declared population and steady simplification.
Same result, different system: 40 opportunities × €30,000 × 20% ÷ 60 also equals €4,000/day. The identical velocity conceals different concentration and capacity risk. The second population may be more exposed to a small number of outcomes.
Invalid denominator: cycle length 0 returns Unavailable: cycle length must be greater than zero. The calculator does not display infinity.
Mixed units: monthly opportunity volume combined with a historical cycle in business days can still be used if opportunity count is a population rather than a monthly rate, but the interface asks the user to confirm the population logic. Currency and time labels remain visible in the output.
12 / Method
Validation and test vectors
Production behavior will be verified against these deterministic cases:
- 10 opportunities × 100 value × 20% ÷ 20 days → 10 currency units/day.
- 0 opportunities × 100 × 20% ÷ 20 → 0/day, with population warning.
- 10 × 0 × 20% ÷ 20 → 0/day, with value-scope warning.
- 10 × 100 × 0% ÷ 20 → 0/day.
- 10 × 100 × 100% ÷ 20 → 50/day.
- Cycle 0, negative count, negative value, or win rate above 100% → validation error; no velocity.
- Required blank input → unavailable, not zero.
- Baseline 0 and positive scenario → absolute delta shown, percentage delta unavailable.
- Baseline and scenario with different currency or time units → comparison blocked until aligned.
Non-finite numbers, pasted symbols, decimal separators, and very large values receive explicit parsing or range messages. The calculation uses numeric values, not formatted strings.
13 / Method
Frequently asked questions
Is higher sales velocity always better?
No. It can be associated with favorable throughput, but it can also reflect a changed population, smaller deals, weak qualification, premature closes, or data errors. Inspect the drivers and companion outcomes.
Should opportunity count include open deals?
It may, depending on the metric contract. Use one declared eligible population and derive the other inputs from a compatible population. Do not combine a current open snapshot with unrelated historical averages without labeling the approximation.
Can I compare two teams?
Yes, after aligning currency, opportunity definition, stage boundary, value basis, win-rate cohort, cycle events, and time unit. Otherwise the comparison is arithmetic over different systems.
Does the calculator predict revenue?
No. It returns the rate implied by inputs. Forecasting requires a separate method and uncertainty treatment.
Are inputs retained?
No. Version 1 is browser-local and uses no server storage, cookies, LocalStorage, or lead gate for entered values.
Method owner: Anastasiia Krynytska, RevOps Architecture Lead. Reviewed 10 September 2026. Results are analytical estimates, not revenue guarantees or financial advice.
Method & privacy note
Inspect before you act
- The complete approved editorial text is published on this page, not hidden behind the download or interface.
- Calculator inputs stay in browser memory; workbook contents stay wherever the user saves them.
- Unknown, unavailable, contradicted, and not applicable remain distinct states.
- Corrections: corrections@aiinsales.org.