Sales Velocity
Sales Velocity is the master equation that aggregates pipeline volume, conversion rate, deal size, and cycle length into a single revenue-per-day output. The formula: Sales Velocity = (Number of Opportunities ร Average Win Rate ร Average Deal Size) รท Average Sales Cycle Length (in days). If you have 200 opportunities, 25% win rate, $40K average deal, and 90-day cycle, you generate $40K ร 200 ร 0.25 รท 90 = $22,222 per day. KnowMBA POV: sales velocity is the master equation because every other sales metric is just a lever on one of the four inputs. Doubling any input doubles velocity; halving any input halves it. Sales leaders who don't know their velocity number can't diagnose where to focus.
The Trap
The trap is optimizing one input in isolation. Adding more opportunities is the easiest move (more SDRs, more spend) but if those opportunities lower win rate or extend cycle length, velocity goes down. Increasing deal size by moving up-market sounds great but if it crashes win rate from 25% to 8%, velocity drops 60%. The four levers interact โ usually negatively. Pulling on one without measuring the others is how teams celebrate 'pipeline growth' while velocity stagnates. Conversely, leaders who fixate on cycle length compression often achieve it by under-qualifying deals โ win rate then drops and total revenue stays flat.
What to Do
Calculate sales velocity monthly and decompose changes by lever. When velocity moves, identify which input drove it: more opportunities? Higher win rate? Bigger deals? Faster cycle? Then ask whether the change is durable or transient. Set quarterly velocity improvement targets at the lever level: e.g., 'win rate from 22% to 26%' rather than 'velocity up 18%.' Use a balanced scorecard: each lever has a target, with the explicit constraint that no lever target can be hit at the expense of another lever's target.
Formula
In Practice
Atlassian (the PLG poster child) demonstrates the inversion of the sales velocity equation. Their initial product-led motion drove enormous opportunity volume (millions of free users) with effectively zero sales cycle on small expansion (self-serve credit card upgrades), small deal sizes ($10-$1K), but at high win rates (~70% for product-qualified expansion). The math: massive volume ร short cycle compensated for small deal sizes. As they moved up-market, they kept the high-velocity self-serve motion AND added an enterprise sales overlay with longer cycles, larger deals, and lower win rates. Two parallel velocity equations, both optimized on different levers, contributed to their growth from $30M to $4B+ ARR.
Pro Tips
- 01
Plot your sales velocity over 12 months as a line chart, with the four input variables as separate lines below it. Most teams discover their 'pipeline growth' was offset by win rate erosion or cycle extension โ the velocity line has been flat for a year.
- 02
Velocity per rep is more useful than total velocity. If team velocity grew 30% but you doubled headcount, per-rep velocity dropped 35%. You're hiring through a problem, not solving it.
- 03
Cycle length compression is the highest-leverage move when product-market fit is strong. Cutting cycle from 120 days to 90 days raises velocity 33% with no change to other inputs. Most cycle compression comes from faster sales-side handoffs, not faster customer decisions.
Myth vs Reality
Myth
โMore pipeline always increases sales velocityโ
Reality
Only if win rate and cycle length hold. Expanding pipeline by lowering qualification standards typically reduces win rate proportionally โ net velocity is flat. The 'pipeline coverage' metric must be paired with 'win rate maintenance' to be meaningful.
Myth
โBigger deals are betterโ
Reality
Bigger deals usually have lower win rates and longer cycles โ both kill velocity. Moving up-market only improves velocity if the deal size increase exceeds the combined drag of win rate decline and cycle extension. Run the math; don't assume.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge โ answer the challenge or try the live scenario.
Knowledge Check
Challenge coming soon for this concept.
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets โ not absolutes.
Sales Cycle Length (B2B SaaS)
Median sales cycle by motion, B2B SaaSPLG / Self-Serve
1-14 days
SMB Sales-Assisted
15-45 days
Mid-Market
60-120 days
Enterprise
150-365+ days
Source: Salesforce State of Sales 2024, Bridge Group SaaS AE Survey
Opportunity-to-Close Win Rate
B2B SaaS, qualified opportunities (Stage 2+)Elite
> 35%
Healthy
25-35%
Average
15-25%
Low
< 15%
Source: HubSpot State of Sales 2024
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Atlassian
2002-2024
Atlassian built two parallel sales velocity equations that powered growth from $30M to $4B+ in revenue. The product-led self-serve motion optimized one velocity equation: massive opportunity volume (millions of free users), short effective cycles (credit card self-serve), high win rates on product-qualified expansion (~70%), and small deal sizes ($10-$1K range). The enterprise overlay added a second equation: smaller opportunity volume, longer cycles (90-180 days), lower win rates (~25%), but much larger deal sizes ($100K-$1M+). Both motions optimized different inputs to the velocity equation. Critically, Atlassian was famous for having no traditional outbound sales for over a decade, demonstrating that high-velocity, self-serve motions can scale to billion-dollar revenue when one of the four levers is dramatically optimized.
Self-Serve Opportunity Volume
Millions of free users
Self-Serve Cycle
Effectively zero days
Self-Serve Win Rate (PQL โ paid)
~70%
Sales Headcount Through 2014
Near-zero outbound for >10 years
Revenue Outcome
$30M โ $4B+ ARR
Sales velocity isn't 'more pipeline' โ it's the ratio of four levers. When one lever is dramatically optimized (Atlassian's near-zero cycle from self-serve), even small deal sizes can compound to billions in revenue.
Decision scenario
The Velocity Decomposition Decision
You're VP Sales. Your team's velocity has been flat for 4 quarters at $18K/day despite increasing pipeline by 50%. The board wants a plan. The four levers: 280 opportunities (was 187), 18% win rate (was 26%), $42K deal size (was $40K), 105-day cycle (was 90 days).
Daily Velocity
$18K (flat 4 quarters)
Pipeline Growth
+50%
Win Rate
26% โ 18% (down 8pts)
Cycle Length
90 โ 105 days (+17%)
Deal Size
$40K โ $42K (+5%)
Decision 1
The math is clear: pipeline grew 50% but win rate dropped 31% and cycle extended 17%. The new pipeline is lower quality. The CRO wants to add 6 more SDRs to push pipeline higher. You suspect that doubles down on the wrong lever.
Add 6 more SDRs as the CRO suggests โ pipeline volume is the safest growth leverReveal
Cut SDR pipeline targets by 30%, raise qualification standards, invest in cycle compression (faster contract/legal turnaround). Restore win rate first, then grow pipeline carefully.โ OptimalReveal
Related concepts
Keep connecting.
The concepts that orbit this one โ each one sharpens the others.
Beyond the concept
Turn Sales Velocity into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h ยท No retainer required
Turn Sales Velocity into a live operating decision.
Use Sales Velocity as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.