Sales & marketing
Sales Velocity Formula: Check the Units and Test One Assumption
A common sales velocity formula is opportunities × average deal value × win rate ÷ sales-cycle length. With cycle length in days and deal value in dollars, the resulting indicator is dollars per day. This invented exercise uses supplied planning inputs; the output is not a promise of daily revenue or cash collections.
Define the four inputs on a consistent basis
Supplied practice inputs: 40 eligible opportunities; average deal value $6,000; assumed win rate 25%; average sales-cycle length 30 days. Treat these as a consistent hypothetical set for one segment. The exercise does not estimate the inputs from real customer records.
Salesforce presents this four-variable velocity formula. When calculating it elsewhere, check the opportunity population and how the win rate, deal value and cycle duration were measured. Mixing unrelated segments can create a precise-looking result without a coherent basis.
Calculate the indicator and inspect its units
A unit-labeled calculation
Use 25%=0.25, not 25.
Numerator=40×$6,000×0.25=$60,000.
Velocity indicator=$60,000÷30 days=$2,000 per day.
The $60,000 is the formula’s weighted amount under the assumptions. It is not confirmed orders; the $2,000/day indicator does not mean exactly $2,000 will arrive each day.
Change one input at a time
ScenarioA changes only win rate to 30%. The indicator becomes 40×$6,000×0.30÷30=$2,400 per day,20% above the base result. The win-rate assumption rises 5 percentage points, which is a 20% relative increase from 25%.
ScenarioB restores the 25% base win rate and changes only cycle length to 24 days. The result becomes $60,000÷24=$2,500 per day,25% above the base. A20% shorter denominator does not imply only a 20% higher quotient. These are sensitivity calculations, not independently achievable improvements.
Distinguish a combined scenario from a measured effect
If both changes were assumed together, the result would be 40×$6,000×0.30÷24=$3,000 per day. That 50% increase follows from the chosen arithmetic. The fixture does not prove that a team can increase win rate while shortening cycles, or that the inputs would remain independent.
To interpret a real change, investigate whether opportunity qualification or measurement changed. Removing slow opportunities from a report can lower the observed cycle without making the underlying work faster. Keep definitions consistent before comparing indicators.
Catch denominator and population errors
A zero cycle length makes the division undefined. A cycle measured in weeks produces dollars per week unless converted explicitly. Likewise, a 25% win rate from all closed opportunities may not apply to a narrowly filtered open-opportunity set without justification.
Practice explanation: “Under the supplied consistent inputs, the indicator is $2,000/day. Changing only the cycle assumption to 24 days gives $2,500/day. Neither amount is a confirmed revenue schedule.” This communicates the calculation and the limit together.
Questions, answered
Does a higher velocity guarantee more revenue?
No. The indicator depends on its inputs and assumptions. It does not guarantee timing or outcomes for individual opportunities.
Can I use 25 as the win rate?
Use 0.25 for 25% in this multiplication. Using 25 would inflate the result 100 times.
Sources and examples
ResumizeAI team. Examples are fictional teaching material, not customer results. Replace sample details with your own facts.
Your experience. A complete resume.
Build in Resumize with ATS-friendly templates, guided editing and a live preview. Start free, then upgrade when you need more.
Free account required. Free-plan PDF exports include a watermark.