Sales Cycle Length

What Sales Cycle Length Measures

Days. From the moment an opportunity becomes qualified to the day it closes — won or lost. A B2B SaaS company with an average cycle of 84 days from SQL to close-won is telling its CFO that pipeline created in March will land in cash in June. Cycle length is the most underused leading indicator in sales. It moves before win rate moves, before pipeline coverage moves, before forecast accuracy starts collapsing.

How Sales Cycle Length Is Calculated

The math is simple. The boundaries are not.

Average Sales Cycle = Σ (Close Date − Opportunity Start Date) / Count of closed deals

The choices that change the answer:

Best practice is to measure SQL-to-close-won by ACV segment, because a $5K transactional deal and a $750K enterprise deal don't belong in the same average. A company reporting "our sales cycle is 62 days" without a segmentation footnote is reporting a number that's true and useless.

A Worked Sales Cycle Example

An AE closes 14 deals in a quarter. Eleven are $20-40K mid-market deals averaging 47 days from SQL to close. Three are $200K+ enterprise deals averaging 184 days. Blended average: 76 days. That number forecasts nothing reliably.

Re-segment it. Mid-market cycle is 47 days, so opps created today close this quarter. Enterprise cycle is 184 days, so opps created today close next year. When the VP Sales sees pipeline coverage of 3.2x for next quarter and feels good, the actual question is — coverage of what cycle length? If half the pipeline is enterprise opportunities created last week, that 3.2x is a fiction. The deals can't physically close in time.

When Sales Orgs Use Sales Cycle Length

VPs of Sales watch cycle length monthly. A 12% expansion in average cycle is the earliest warning that buyers are stalling — usually two quarters before it shows up as missed quota. RevOps uses cycle length to set coverage targets correctly: a 90-day cycle with a 25% win rate needs 4x coverage, but a 180-day cycle needs that pipeline built six months ahead.

CFOs care because cycle length determines cash conversion. Recruiters use cycle length when sizing AE comp — selling a 30-day product at $25K ACV is a different job than selling a 200-day product at $300K ACV, and the comp plans should not look alike. Individual reps care because their personal cycle length, compared to team average, is a coachable signal. Cycles 40% longer than peers usually mean weak discovery or a missing champion.

Common Sales Cycle Length Gaming Patterns

Cycle length gets manipulated three ways. Backdating — moving the opp create date to right before close, so the cycle reports as 14 days instead of 140 and the rep looks like a velocity machine. Late opportunity creation — only logging an opp once a verbal commit exists, hiding the actual prospecting and discovery time. Close-lost cleanup — bulk-closing stalled opps as lost at quarter-end, artificially shortening the average because the truly long deals never resolve in the data.

The cleanest version of cycle length uses opportunity creation date locked at first CRM sync, segments by ACV and motion, and excludes opps that close in under five days (those are renewal-flavored or pre-negotiated and not real cycles). It's a slower, less flattering number — and the one that actually predicts whether the pipeline will close.