The blended number describes no one
One pipeline-wide cycle figure hides two facts that matter more than the average itself: how long each tier takes, and how much of the quarter depends on the slow tier. A team can hold a steady blended cycle while its enterprise band quietly stretches, because a rising volume of small fast deals offsets the drift.
Cycle length also drives in-quarter eligibility. Pipeline created 60 days before quarter end is real in a band that closes in 45 days and fictional in a band that closes in 120. Applying one assumption across both puts revenue in the wrong quarter.
Build the bands on closed-won amounts
Band deals by what they closed at, not by what the CRM said they were worth while open. ORM has seen pipelines carrying an $80,000 average deal size against a $40,000 average closed-won deal size. Bands built on open values in that pipeline would place half the deals in a tier they never reached, and the cycle numbers attached to those tiers would be wrong in both directions.
Use three or four bands, each holding enough resolved deals to produce a stable figure. Report a median inside each band alongside the mean, since the tail behaves differently at the top end.
Watch for mix shift
Deal size is not a constant. ORM's account of why forecasts miss includes a new competitor entering the market and creating pricing pressure, with average deal size falling as the result. When that happens, deals move into lower bands and the blended cycle drops even though no individual deal sped up.
That is why the bands need to be reported separately every quarter. A falling blended cycle can mean the motion improved or it can mean the deals got smaller. Only the banded view distinguishes the two.
What the bands change
Banded cycle length changes three operating decisions. Coverage targets stop being one ratio and become a ratio per band with a matching creation deadline. Capacity planning reflects that a rep working the slow band carries fewer concurrent deals per quarter. Deal aging thresholds get set against the band a deal belongs to, so a 100-day enterprise deal reads as normal while a 100-day small deal reads as stalled.
Run those checks before setting a pipeline coverage target, then push the banded cycle assumptions into sales forecasting so timing reflects how each tier actually behaves. Segment win rate the same way, because cycle length and conversion move together across the value curve.
Frequently Asked Questions
Do larger deals always take longer to close?
Larger contracts carry more approval steps, more security and legal review, and more people who can pause the process, so cycle length rises with value in almost every B2B pipeline. The useful work is measuring how much it rises in yours rather than assuming a ratio.
How should the size bands be set?
Build them from closed-won amounts, not from open pipeline amounts. Deals frequently close below the value carried in the CRM, so bands built on open records assign deals to a tier they never actually reached.
How many bands do you need?
Three or four with enough closed deals in each to be stable. Splitting further thins the sample until the cycle number for each band is fitted on noise instead of pattern.
Why does the blended cycle move when no deal moved?
Mix shift. If pricing pressure pushes average deal size down, deals migrate into faster bands and the blended average falls even though every individual band held steady.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like sales cycle length by deal size into prescriptive action for your team.
Schedule a Demo