If your sales cycle feels longer than it used to, you are not imagining it and your team is probably not the problem. Median B2B SaaS sales cycles have moved from 107 days to 134 days — a 25% increase since 2022 — and the lengthening is not evenly distributed. True enterprise deals now take six to eighteen months. Mid-market is hovering around 84 days. Everything below that has held roughly steady.

The cause is structural, not behavioral. Buying committees ballooned from three to five people to eight to twelve. Budget scrutiny moved from a CFO-only concern to a CFO-plus-procurement-plus-security concern. Security reviews that used to apply only to seven-figure deals now happen on deals one tenth that size. None of this is going away in 2026.

That has consequences for how you forecast, how you stage your CRM, and which deals you spend the next quarter on. Most teams are pricing the change into their numbers about two quarters late.

The Three Structural Changes Driving the Lengthening

The lengthening did not arrive in a single shock. It is the cumulative effect of three changes that each look small in isolation and large together.

The committee got bigger. The average B2B purchase now involves 6.8 stakeholders, up from 5.4 in 2020. Each additional stakeholder adds meeting cycles, asynchronous decision time, and a chance for the deal to die because somebody new objects. The committee growth alone accounts for roughly half of the cycle lengthening.

Procurement and security moved downmarket. A $50,000 deal in 2022 closed without a procurement review. The same deal in 2026 often gets one, plus a security questionnaire, plus a vendor risk assessment. Each layer adds two to six weeks to the cycle and was not on the critical path of the historical playbook. Teams that did not redraw the path are missing it on every deal.

Budget scrutiny became continuous. Pre-2022, budget was approved annually and the cycle was about getting line-item approval. Post-2022, budget is reviewed quarterly and existing approvals can be paused. A deal that was budgeted in Q1 can lose its slot in Q2 if the CFO reallocates — which means time-to-close became a deal-killer in a new way.

Why Most Forecasts Have Not Caught Up

The forecasting bug is the most expensive consequence of the lengthening, and it is the one that catches CROs by surprise.

Stage durations in most CRMs reflect 2022 reality. A stage that historically lasted 14 days is now lasting 21. The CRM still uses 14. The forecast pulls the close date forward by a week per stage. By the time the deal hits late-stage, the projected close is two months earlier than the deal is actually going to close. Multiply across 200 open deals and the quarterly forecast is systematically optimistic by 20 to 30%.

Stage conversion is changing too, in the same direction. Longer cycles correlate with lower stage-to-stage conversion, because there are more meetings, more stakeholders, and more chances for the deal to stall. Many forecasts use historical conversion ratios that were built before the lengthening. The double miss — wrong duration plus wrong conversion — is what makes a CRO miss two quarters in a row and then have to over-correct in the third.

Win rates are holding, but the time-to-revenue is wrong. The deals are still closing, mostly — they are just closing in the next quarter instead of this one. The board sees a missed quarter and assumes a sales problem. The actual problem is a forecasting problem on top of a cycle-length problem. The cure is recalculating the math, not replacing the leader.

Where the Lengthening Shows Up by Function

The effects ripple across the org in predictable ways.

Sales Leadership. CROs running 2022 stage definitions get to month two of a quarter, realize the forecast is going to miss, and have no levers left to pull. The teams that recalibrated stage durations in early 2025 saw the miss coming in time to act — usually by pulling deals forward through multi-threading rather than discounting.

Finance. FP&A teams forecasting revenue off the CRM forecast are inheriting the optimism. Most finance teams have started applying a "cycle drift" haircut — typically 10 to 20% — to the sales forecast for planning purposes. The teams that did not are explaining variances to the board after the fact.

Customer Success. Longer pre-sales cycles produce more thoroughly vetted customers, which is good news for retention. CS teams that track new-customer profile against churn report higher first-year retention for customers who came through the longer cycle than for customers who came through the faster 2022 motion. The cycle lengthening, paradoxically, is improving downstream retention.

Revenue Operations. RevOps owns the cycle math. Teams that re-baseline stage durations and conversion ratios quarterly are getting forecasts within 5% of actuals. Teams that re-baseline annually are running 15 to 20% off and not knowing it. The cadence of the recalibration matters as much as the recalibration itself.

What to Do This Quarter

The fix has three parts and is unglamorous on each one.

Recalculate cycle length from the last six months of data. Not the trailing year. The trailing six months — because the change is accelerating and last year's number is already stale. Compare to your CRM's default stage durations. If the gap is more than 15%, retune the stages this quarter.

Re-baseline stage conversion at the same time. Cycle length and conversion ratio are correlated. The same deals that take longer convert at lower rates per stage. Tuning the duration without tuning the conversion produces a forecast that is wrong in a different direction.

Audit your top ten open deals for multi-threading. Deals with three or more engaged contacts close 2.4x faster than single-threaded deals. The single-threaded deals are not deals; they are wishes. Either get a second and third contact engaged this quarter or move them out of the forecast.

Send proposals within 24 hours. Proposals sent the day of a demo close 35% faster than proposals sent a week later. The reason is political — momentum inside the buyer's org decays quickly, and a proposal four days late has to be re-sold internally. The cycle compression here is essentially free if the team is willing to do it.

Move budget into async demo and proposal automation. Most of the cycle is waiting. Async video demos and interactive proposal links shrink the wait windows between meetings. Teams that invested in these tools in 2024 cut median cycle by 8 to 12% without changing anything else.

The Stakes

The lengthening is not going to reverse in 2026 or 2027. The committee size is structurally larger because the cost of bad software decisions is structurally larger — every team has more SaaS, more security exposure, and more procurement scrutiny than they did three years ago. Pricing that reality into the forecast is now table stakes; the teams that did it early are forecasting accurately and the teams that didn't are explaining misses.

The competitive consequence is that the teams who run the longer cycle well — multi-threading early, sending proposals fast, instrumenting stages quarterly — are taking share from teams who are still running the 2022 motion at 2022 speed. The lengthening rewards rigor. It punishes single-threaded optimism.

Two numbers matter for the next twelve months: your actual cycle length over the trailing six months, and your CRM's assumption about the same. If those two numbers disagree by more than 15%, fix it before the board does the math. The deals are still there. The forecast is what changed.