Sales Cycle Length

What is sales cycle length?

Sales cycle length (also called deal cycle time, average days to close, or opportunity-to-close duration) is the average number of days between opportunity creation in the CRM and the close date — whether won or lost. It measures the speed of the selling process from the point where a qualified prospect enters the pipeline.

Long sales cycles tie up rep capacity, delay revenue recognition, and increase the cost of every deal. A rep working 15 active opportunities with a 90-day average cycle can close roughly 60 deals per year. Reduce the cycle to 75 days and the same rep closes 72 deals — a 20% increase in throughput without adding headcount or pipeline.

For mid-market B2B SaaS ($15K-$75K ACV), healthy sales cycles run 60-90 days. Below 45 days often indicates a transactional, low-ACV motion. Above 120 days signals deal complexity, weak qualification, or a multi-stakeholder process that stalls in procurement.

Sales cycle length is not the same as time to close. Time to close is sometimes measured from first touch (website visit, inbound inquiry) to signed deal, which includes the marketing and qualification stages. Sales cycle length starts at opportunity creation — after the lead has been qualified and accepted into the pipeline.

Why sales cycle length matters for operators

Every extra day in the sales cycle costs money. Rep compensation, CRM overhead, management attention, and opportunity cost of not working other deals — these compound across every open deal in the pipeline.

A company with 8 reps running an average 85-day cycle has approximately $4.2M in pipeline at any given time (assuming $25K average deal value and 25 open deals per rep). If 15% of that pipeline stalls past 120 days, $630K in deals are consuming rep time without progressing. Those deals rarely close — win rates on opportunities that exceed 1.5x the average cycle length drop by 40-60% (CSO Insights, 2025).

Operators who segment cycle length by deal size, source, and stage velocity spot the bottlenecks. If Stage 2 to Stage 3 takes 28 days on average but Stage 3 to Stage 4 takes 6 days, the discovery-to-proposal transition is where deals stall. That is a process problem with a process fix — not a "deals take time" excuse.

A $10M ARR SaaS company that reduced mid-market sales cycle from 84 days to 68 days by improving proposal turnaround and multi-threading closed an additional $1.4M in annual revenue from the same pipeline and team size.

Sales cycle length formula

Average Sales Cycle Length = Sum of Days to Close (all resolved deals) / Number of Resolved Deals

Example:
- Deal 1: Created Jan 8, Closed Feb 22 → 45 days
- Deal 2: Created Jan 15, Closed Apr 2 → 77 days
- Deal 3: Created Jan 22, Closed Mar 18 → 55 days
- Deal 4: Created Feb 1, Closed Mar 29 → 56 days
- Deal 5: Created Feb 5, Closed May 14 → 98 days

Average = (45 + 77 + 55 + 56 + 98) / 5 = 66.2 days

Median is often more useful: 56 days
(The 98-day outlier skews the average upward)

What to include in the calculation:

• Numerator: Days from opportunity creation date to close date. Use calendar days, not business days — the buyer's process does not pause for weekends.
• Denominator: All resolved deals (closed-won and closed-lost). Including lost deals gives you the true cycle — not just the cycle of deals that went well.

Segmented cycle length (more actionable):

Cycle length by deal size:
- Deals < $10K ACV: 32 days average
- Deals $10-50K ACV: 67 days average
- Deals $50-100K ACV: 94 days average
- Deals > $100K ACV: 142 days average

Sales cycle length benchmarks by deal size and motion

How cycle length varies across B2B deal types. Ranges based on industry benchmarks.

Sources: Gartner B2B Sales Benchmark 2025, Pavilion CRO Survey 2025, CSO Insights Sales Optimization Study 2024.

Common mistakes when measuring sales cycle length

1. Using opportunity creation date inconsistently

Some reps create opportunities at first contact. Others create them after the discovery call. If the definition of "opportunity created" varies by rep, cycle length comparisons are meaningless. Define the trigger: a clear stage gate (e.g., "discovery call completed and next step scheduled") that applies to every rep.

2. Excluding lost deals from the calculation

If you only measure cycle length for won deals, you undercount the true time investment. Lost deals consumed rep capacity too. Include all resolved deals (won and lost) for an accurate picture. Track won-deal and lost-deal cycles separately as a secondary analysis.

3. Not segmenting by deal size

A blended 72-day cycle might combine 28-day SMB deals with 140-day enterprise deals. The blended number tells you nothing actionable. Segment by ACV band, source channel, and ICP segment. The segment-level number reveals where the process is slow.

4. Measuring calendar time without stage velocity

Overall cycle length tells you the deal took 85 days. Stage velocity tells you it spent 34 of those days stuck between Stage 2 and Stage 3 with no activity. Measure time-in-stage alongside total cycle length. The stage where deals stall longest is the bottleneck to fix.

5. Ignoring the "dead zone" past 1.5x average cycle

Deals that exceed 1.5x the average cycle length close at 40-60% lower win rates. A deal at 130 days on a 85-day average cycle is not "still working" — it is probably lost and consuming rep time. Set automatic flags for deals that pass the 1.5x threshold.

How Fairview tracks sales cycle length automatically

Fairview's Pipeline Health Monitor calculates cycle length from CRM opportunity data — segmented by deal size, source channel, rep, and ICP fit. Stage velocity is tracked in parallel, showing exactly where deals spend the most time.

The Operating Dashboard displays cycle length trends alongside win rate and pipeline coverage. When cycle length increases, the Forecast Confidence Engine adjusts the weekly forecast — extending cycle assumptions before the revenue miss appears in closed-won data.

Deals that cross the 1.5x threshold trigger alerts from the Next-Best Action Engine: "4 mid-market deals have exceeded 102 days (1.5x the 68-day segment average). 3 of 4 have had no activity in 18+ days. Recommend pipeline review and resolution."

The Weekly Operating Report includes cycle length by segment as a standard section, with week-over-week trend lines.

→ See how Pipeline Health Monitor works

Sales cycle length vs time to close

Sales cycle length starts when the prospect enters the pipeline as a qualified opportunity. Time to close often starts earlier — at first touch or lead creation. Time to close is always longer than sales cycle length because it includes the marketing and qualification stages. Use sales cycle length for sales process optimization. Use time to close for full-funnel analysis.

FAQ

What is sales cycle length in simple terms?

Sales cycle length is how many days it takes, on average, to close a deal from the moment it enters your pipeline. If an opportunity is created on January 10 and the deal closes on March 20, that deal's cycle length is 69 days. The average across all deals gives you your sales cycle length.

What is a good sales cycle length for B2B SaaS?

It depends on deal size. SMB deals under $10K ACV should close in 14-45 days. Mid-market deals ($10-50K ACV) run 45-90 days. Enterprise deals above $100K ACV take 90-180 days. If your cycle exceeds the upper range for your deal size, the sales process has a bottleneck worth diagnosing.

How do you calculate sales cycle length?

Add up the number of days from opportunity creation to close for all resolved deals in a period, then divide by the number of deals. Include both won and lost deals. Use median instead of average when outliers are present — one 200-day deal skews a 50-deal average more than it should.

What is the difference between sales cycle length and time to close?

Sales cycle length starts when an opportunity is created in the CRM — after qualification. Time to close often starts at first touch or lead creation, which includes marketing and qualification stages. Time to close is always longer. Use cycle length for sales process analysis. Use time to close for full-funnel efficiency measurement.

How often should you measure sales cycle length?

Monthly for trend analysis, segmented by deal size. Quarterly for strategic benchmarking against industry data. If you close fewer than 20 deals per month, use a rolling 90-day window to reduce noise. Track week-over-week stage velocity for real-time process diagnosis rather than waiting for deals to close.

How do you shorten the sales cycle?

Four approaches: improve qualification so only ready-to-buy prospects enter the pipeline (fewer stalled deals), multi-thread into multiple stakeholders early (reduces single-point-of-failure delays), accelerate proposal and legal review with templates and pre-approved terms, and set mutual action plans with buyers that create shared deadlines.

Related terms

• Sales Velocity — Revenue throughput of the pipeline, where cycle length is one of four input variables
• Win Rate — Percentage of opportunities that close, often inversely correlated with cycle length
• Pipeline Coverage Ratio — Pipeline relative to quota, which must account for expected cycle length
• Discovery Call — First sales conversation, where thorough qualification shortens the remaining cycle
• CAC Payback Period — Months to recover acquisition cost, directly affected by how long deals take to close

Fairview is an operating intelligence platform that tracks sales cycle length by segment and stage — alongside win rate, sales velocity, and pipeline coverage. Start your free trial →

Siddharth Gangal is the founder of Fairview. He built stage velocity tracking into the platform after watching operators treat cycle length as a fixed input when it was actually a process metric with identifiable bottlenecks at specific deal stages.