Sales Cycle Length: Benchmarks, Analysis, and How to Shorten Your Close Time

Sales cycle length is the number of days from a qualified opportunity to a closed-won deal. Report it as the median of the deals won in a period. The median B2B SaaS cycle is 84 days (optif.ai), but your forecast needs your own number. Split it by deal size, and keep new business and expansion apart. Updated October 2026: the formula choices, a worked example, and checked benchmarks.

Sales cycle length is the metric most likely to wreck your forecast. Not because teams do not track it, but because they track an average and assume it applies to every deal in the pipeline. It does not.

Medians are dangerous too when the distribution is wide. In the same study, SMB deals under $15,000 typically close in 14 to 30 days and enterprise deals over $100,000 take 90 to 180 days or more. A single number for the two describes neither.

Sales cycles have lengthened 22% since 2022 (optif.ai). Not every dataset agrees on the last year: Ebsta's 2025 benchmark found new-business cycles 9% shorter than in 2024 (Ebsta and Pavilion, 2025). Different samples, different methods. The lesson is the same either way. Cycle length moves, and a team that plans around an old cycle time is forecasting with a bad assumption. That is one reason 87% of enterprises missed their revenue targets in 2025 (Clari Labs, 2026) and why so many sales forecasts land late rather than wrong.

This guide covers the formula and the choices that change it. Then the benchmarks by deal size and motion, where cycles break down, and five ways to shorten them without hurting deal quality.

What Is Sales Cycle Length?

Sales cycle length is the number of days from opportunity creation to closed-won. It is what you divide by in the pipeline velocity formula, and one of the biggest inputs in your revenue model.

Per deal: close date minus the date the opportunity was created. The result is the cycle in days. For the team: the median of that figure across all deals won in the period.

The definition sounds simple, but two decisions change the number dramatically:

When does the clock start? Some teams start at first contact. Others start at opportunity creation. Others start at the first qualified meeting. Starting at first contact mixes marketing's time into the selling cycle. If the question is which campaigns sourced a deal and how long they took to pay off, that is revenue attribution, a separate measure. Pick one start point, be consistent, and compare apples to apples. What counts as an opportunity? If every inbound lead gets an opportunity created, your average cycle will be shorter (lots of quick wins mixed in). If only qualified, discovery-completed leads get an opportunity, the average will be longer but more meaningful.

My recommendation: start the clock at opportunity creation, defined as the point where a deal has been qualified and enters your active pipeline. This gives you a cycle length that measures the selling process, not the marketing-to-sales handoff.

The five choices that change the number

Most published guides give one formula: total days to close divided by deals closed. That is a mean, and it hides five decisions. Make them on purpose and write them down.

Renewals deserve their own rule. In ORM's models, new business timing is a function of when the opportunity last changed stages. Renewal timing is a function of the renewal date, with closes spread across roughly 30 days before and after it. Blend the two and the number describes neither motion.

A worked example you can check

Ten deals closed last quarter. Seven were won and three were lost. All numbers below are illustrative.

- Won deals, days from creation to close: 0, 21, 35, 48, 62, 75, 190 - Lost deals, days from creation to close: 30, 120, 210

The math: the seven won deals add up to 431 days, so the mean is 431 / 7 = 61.6 and the median is the fourth deal, 48. Drop the zero-day deal and the mean is 431 / 6 = 71.8, with a median of (48 + 62) / 2 = 55. Add the three lost deals (360 days) and the mean is 791 / 10 = 79.1, while the median stays at 55.

Same ten deals, answers from 48 to 79 days. Three things to notice:

1. One slow deal moves the mean. The 190-day deal puts the mean 13.6 days above the median. The median is the better description of a typical deal. 2. Same-day deals are a data problem, not fast selling. When stage criteria are loosely enforced, reps keep deals in a desk drawer and only create the opportunity once it is effectively won. One ORM customer had 20% of its opportunities created and closed-won on the same day. Those zero-day records drag the cycle down and make the selling process look faster than it is. Find them and model them separately. 3. Won-only measures survivors. Deals still open are invisible in a close-period view, and those are often the slow ones. Use a creation cohort to see them, as in how to calculate sales cycle length for open deals.

A first-meeting clock would shift every figure again. If your opportunities are created about two weeks after the first meeting, a first-meeting start adds roughly 14 days to each deal.

In a CRM report. Add a formula field on the opportunity: close date minus created date. In Salesforce that is `CloseDate - DATEVALUE(CreatedDate)`. If your clock starts at a qualified date, put that custom date field in place of the created date. Report builders usually summarize with an average, so check for a median option or export the column.

How long is too long? In ORM's models, every opportunity is grouped by a machine learning model and each group gets its own curve for how long it takes to close. The curves run from 1 to 80 weeks. Most of the expected wins land before week 12, and very few groups carry any expectation past week 52. That is why we use a 12-month rule for most customers: no meaningful change in 12 months, and the deal is no longer real pipeline. More on the curves in how long deals actually take to close, by group.

Why the number has been moving in 2026 is covered below. The short version: buyers are delaying decisions, not declining them.

What Are Sales Cycle Length Benchmarks by Industry?

There is no trustworthy cross-industry table. Deal size and buying motion explain more of the difference than the industry label, so those are the cuts worth benchmarking against.

Average Sales Cycle by Deal Size

The median B2B SaaS sales cycle is 84 days across 939 companies studied by optif.ai, but deal size moves it far more than any blended number shows:

Source: optif.ai. The ranges are the 25th to 75th percentile, and the stage timings behind them come from won deals. Cycles have lengthened 22% since 2022, and the same study ties much of that to bigger buying committees and heavier security review. Larger deals feel it most, because they carry the biggest committees and the most procurement.

Average Sales Cycle by Industry

Published industry averages conflict with each other and rarely explain how they were measured. One puts healthcare near 125 days while another says six to 12 months. We do not reproduce numbers we cannot trace to a method.

What holds across industries is the driver. Regulated sectors such as financial services and healthcare technology add security, compliance and procurement review, and that review lands in the second half of the deal. Deal size and committee size explain more of the difference than the industry label does.

The benchmark that matters is your own trailing four quarters, tracked by segment and by deal size.

Why Sales Cycles Are Getting Longer

Three structural forces are driving the lengthening.

1. Buying Committees Have Expanded

The typical B2B buying decision now involves 13 internal stakeholders and nine outside influencers (Forrester, 2026). Sellers feel it. Ebsta found reps engage eight stakeholders on a new deal and five on an expansion deal (Ebsta and Pavilion, 2025). More people means more calendars, more needs to meet, more internal decks, and more chances for someone to slow things down.

The impact compounds. Each added stakeholder does not add a fixed number of days. The champion has to align every one of them before the deal moves, so the delay shows up inside every stage, not as one extra step at the end.

2. Budget Scrutiny Has Intensified

Post-2022 budget discipline has not relaxed. CFOs still require several levels of approval for new software purchases. This is where pipeline coverage ratio becomes critical for planning. ROI justification that used to be a nice-to-have is now a gate. Deals that used to close on a VP's discretionary budget now need SVP or C-level sign-off.

That work happens in procurement, legal, security review, and finance. The sales team often cannot see it. The deal "goes quiet" for weeks, and the rep thinks it is stalling when it is moving through internal approval.

3. Buyers Have More Information and More Options

Buyers now do much of their evaluation before they talk to sales. They arrive with competitive comparisons, peer reviews and pricing estimates. This is sometimes cited as a reason cycles should be shorter. The buyer has already done the research.

In practice, it makes cycles longer. Informed buyers have more questions, more specific requirements, and more comparison points. They compare more vendors at once. The evaluation is more thorough, which is good for deal quality but extends the timeline.

What Is the Average Sales Cycle, and How Much Has It Moved?

The median B2B SaaS sales cycle runs 84 days. That figure is a median across sectors and it hides an enormous spread, so it is a starting reference rather than a target.

The movement matters more than the level. Across a study of 939 companies, sales cycles have lengthened 22 percent since 2022. A team whose process has not changed at all is closing later than it did three years ago, which shows up as a forecast miss rather than as a cycle problem, because nothing in the pipeline report says the clock moved.

Note the mix of statistics: optif.ai reports a median, Ebsta an average. An average sits above the median when a few deals run long, so the 91-day and 84-day figures are not a contradiction. They are different measures on different samples.

Averages by industry vary widely enough that the cross-sector number should not drive a quota or a coverage rule. Segment your own history by motion, by product, and by deal size before comparing to anything published.

When cycles stretch mid-year, deals planned for one quarter land in the next, and some slide into next year. That is the moment for a full-year reforecast rather than a quiet hope that Q4 makes it up.

What Is Actually Driving Longer Cycles in 2026?

Cycle length has been the biggest culprit in 2026. Across the B2B SaaS companies ORM works with, buyers are delaying decisions, and two causes account for most of it.

Uncertainty about AI. Buyers do not know what an AI-enabled version of their workflow will look like. Rather than committing to a known solution, they wait to see whether AI solves the problem a different way. One thing we heard again and again: the prospect knew the problem, knew a solution existed, and wanted to give its own team more time to see what it could build with AI first. That hesitation does not show up as a lost deal. It shows up as a deal that keeps moving. Macro pressure. Broad economic pressure hit the back half of Q1 and the front half of Q2. Uncertainty rose, and decisions slipped again.

Both produce the same signature: pipeline holds, deal count holds, and revenue arrives late. Fewer deals get decided. They are not won and not lost. Days in stage creep up, days to close rise, and velocity slows while coverage still looks fine. The good news: in Q3 we saw more deals decided in the first few weeks of the quarter than in comparable periods of Q1 or Q2.

How to tell which problem you have. The symptom pattern separates them cleanly: The third row is the one teams misdiagnose most often. The pipeline is not the problem, so generating more of it does not help. What helps is forcing decisions, because a no today is better than a no three months from now, then finding out why buyers hesitate and answering it in the pitch.

Where Do Sales Cycles Break Down?

The overall cycle length number hides the breakdown by stage. And the stage breakdown is where you find the fix.

Measure your own median time in each stage from your closed-won deals, then look for the stages where deals pile up:

Run it on your last 50 closed-won deals. Cycle time usually concentrates in one or two stages, and those are where compression pays off. For open deals, time since the last stage change says more than total age. A deal that moved into Proposal yesterday is in better shape than one that has sat there for two months.

Then compare cycle length by outcome. Deals that win tend to follow a predictable timeline. Deals that lose often stall in the solution or proposal stage. Watch two signals in particular. A rep pushing a close date is the best single sign of a slip, and a deal that moves from one quarter to the next is less likely to close, even in commit. Earlier still is silence: no activity, no changing data and no notes.

How Do You Shorten a Sales Cycle?

Shorten the stages where deals wait, not the ones where buyers do real work. Bring decision makers in early, confirm budget and timeline by the second call, and have the business case and security package ready before anyone asks.

Tactic 1: Multi-Thread by Stage 2

Multi-threading means engaging multiple stakeholders in the buying committee early in the process, before the deal reaches the stages where committee alignment becomes the bottleneck.

Multi-threading helps win rates, and it also shortens cycles. Get the economic buyer, the technical lead, and the champion engaged by Stage 2. Then the internal alignment that stalls later stages has already started. Ebsta found win rates rose 55% when decision makers took part in the first two stages (Ebsta and Pavilion, 2025). That is a relative lift.

The process: after every discovery call, ask "who else needs to be involved in this decision?" Then schedule a meeting with each of those stakeholders within 10 days. Do not wait for the champion to bring them in. They will not. They are busy, and scheduling internal meetings is not their priority.

Tactic 2: Front-Load Discovery

Most teams run discovery as a single call focused on pain points. That leaves decision discovery, the questions about budget, timeline, buying committee, and decision process, for later in the cycle. This is backwards.

By the end of call two, you should know:

- Budget range. Not the exact number, but whether the deal is in the right ballpark. - Timeline. When the prospect needs a solution in place and what is driving that date. - Decision process. How many steps, how many approvals, and who signs. - Competition. Who else they are evaluating and where they are in the process.

When all four are confirmed by Stage 2, you know whether the deal is real. You can plan around the buyer's real timeline instead of your own guess. Slow qualification costs you. Ebsta found that when the qualification stage runs 50% longer than average, the deal is 120% more likely to slip (Ebsta, 2024).

Tactic 3: Quantify the Business Case Early

Budget committees approve business cases, not product demos. A deal that reaches the proposal stage without a quantified ROI justification will stall at procurement while the champion scrambles to build one internally.

Build the business case during the solution stage, not after. Work with the champion to quantify:

- Cost of the current state. What is the problem costing in revenue, time, or risk? - Value of the proposed solution. Quantify the improvement in the same units. - Payback period. How many months until the investment recovers its cost?

Picture the champion walking into the approval meeting with a business case that says "this pays for itself in 4 months." That is a different talk than "this looks like a good tool."

Tactic 4: Pre-Build Legal and Security Packages

Procurement, legal, and security review add weeks to most enterprise deals. Most of that time goes to the same questions every time: SOC 2, data processing terms, SLAs, and insurance.

Build a procurement acceleration package that includes:

- Pre-completed security questionnaire - SOC 2 Type II report (or equivalent) - Standard DPA and data retention policies - Master service agreement template - Reference customer contacts

Send this package proactively at Stage 3, before the prospect asks for it. When procurement has the materials before it requests them, you remove the back-and-forth that stretches the negotiation stage.

Tactic 5: Coach the Champion to Sell Internally

Your champion is selling for you when you are not in the room. If they are not equipped, they are not effective, and the deal stalls.

Champion coaching means providing three things:

1. An internal pitch deck. Not your sales deck. A five-slide summary in the customer's visual format that the champion can present to their leadership. Include the business case, the implementation timeline, and the risk of doing nothing.

2. Objection responses. The three most common internal objections your champion will face, with data-backed responses. "Why not build it ourselves?" "Why this vendor versus X?" "Can we wait until next quarter?"

3. A mutual action plan. A shared timeline with milestones, owners, and dates that keeps both sides accountable. The mutual action plan is the single most effective tool for preventing the "deal goes quiet for three weeks" problem.

Executive engagement compounds the effect. When the champion has a direct sponsor at the executive level who has committed to the timeline, internal blockers get resolved faster. Coaching the champion to get executive sponsorship early is one of the most valuable things a rep can do in a complex deal.

What not to do: buy speed with a discount

Discounting to close faster looks like a shorter cycle. It is not. Pull a deal forward with a discount and the days to win improve a little, but the deal shrinks. What you gain in speed you give back in price. You also shrink next quarter's starting pipeline, which is often built 6 to 12 months ahead. More on that trade in the real cost of pulling deals forward. Ebsta's data points the same way: top performers do not discount, and that helps cut negotiation time by 24% (Ebsta and Pavilion, 2025).

Sales Cycle Length and the Revenue Model

Sales cycle length is the most underappreciated variable in revenue planning. Here is why.

Pipeline velocity = (Opportunities x Average deal size x Win rate) / Sales cycle length in days

Cut your cycle by 20% and change nothing else, and velocity rises 25%. Dividing by 0.8 is the same as multiplying by 1.25. That equals 25% more pipeline, or a 20% win rate lifted to 25%. Velocity math is one place the mean belongs, because total deal days matter there.

The compounding effect is even larger. Shorter cycles mean reps can work more deals per quarter. More deals with the same win rate means more closed revenue. And reps working more active deals stay sharper, which tends to improve win rate over time.

Here is the quarterly impact for one rep (illustrative: $80,000 average deal, 20% win rate, and enough open pipeline that 60 deals reach a decision in a quarter at a 90-day cycle). Cut the cycle 20% and the same pipeline turns over 1.25 times as fast, so 75 deals reach a decision:

The math: 60 x 20% = 12 wins x $80,000 = $960,000. 75 x 20% = 15 wins = $1,200,000. 75 x 22% = 16.5 wins = $1,320,000.

Uneven cycle length is one of the main reasons forecast accuracy suffers. The model assumes one blended cycle, but real deals run from a few weeks to six months or more. So every deal in the forecast carries timing risk. Shrink the range as well as the average, and accuracy improves.

Tracking Sales Cycle Length Weekly

Track these metrics weekly:

1. Median cycle of deals closed this week. Compare to the 90-day rolling average. If it is trending up, cycles are lengthening and your velocity assumptions need adjustment. Compare against the same point in prior quarters too. Deals bunch at quarter end: in ORM's data the third month of a quarter is always the largest and the first month the smallest, so a median read in month one is not comparable to one read in month three.

2. Average age of open opportunities by stage. This is the leading indicator. When deals start spending longer in a stage than the historical norm, they are stalling. Stalled deals close at lower rates and take longer. The sooner you identify them, the sooner you can intervene or remove them.

3. Percentage of pipeline past the 75th percentile cycle for its segment. This is your stale pipeline metric. If, say, 30% of your pipeline has been open longer than 75% of deals that eventually closed, your coverage ratio is overstated.

4. Days since the last meaningful change. We count a change in stage, close date, or amount as meaningful activity. A deal with none of the three in 12 months is out of the pipeline under our rule.

For the full framework on weekly pipeline tracking, see the sales pipeline metrics guide, and our roundup of the best RevOps tools for platforms that automate this tracking.