A thirty-day SMB motion and a one-hundred-eighty-day enterprise motion blended together produce an average that reflects neither. Segment the number, or do not report it.
Sales cycle length is the average number of days from the moment an opportunity is created in the pipeline to the moment it is marked closed-won. It is a measure of selling speed, not deal quality. Longer cycles require more pipeline coverage to hit the same quota, and the number is a core input to sales velocity, capacity planning, and forecast math. The right measurement is always by segment, never aggregate.
The six things to understand about sales cycle length before quoting an average in a revenue review or wiring it into a forecast model.
Sales cycle length is the average number of days between the opportunity creation date and the closed-won date, measured across deals that actually closed-won in the period. Deals still open, deals closed-lost, and deals disqualified are excluded. The output is a single integer in days, segmented by whatever lens the team uses to run the business.
Longer cycles mean more pipeline coverage is needed to hit the same quota, more time per deal from each rep, and a wider forecast window before cash lands. Cycle length is the denominator in sales velocity and a direct input to capacity planning. Every revenue model that ignores it tends to over-promise and under-deliver.
SMB B2B cycles typically run thirty to forty-five days. Mid-market cycles land between sixty and ninety days. Enterprise cycles run ninety to one hundred eighty days, often longer when procurement, security review, and legal are involved. The numbers vary by product category, but the segment ordering is almost universal.
Teams that sell across segments see a blended average that reflects none of them. A quarter heavy on SMB looks like the cycle shortened. A quarter heavy on enterprise looks like it lengthened. Neither is true at the motion level. Report cycle length by segment, every time, and roll up only for leadership summaries.
Cycles shrink when the process between stages is instrumented. Proposal automation, electronic signature, pre-filled security questionnaires, routing rules that get the right stakeholder on the call, and stage-exit criteria that force clean transitions each remove days. Breaking cycle length into days-per-stage is where the targeting work happens.
Opportunity created date, closed-won date, segment, and stage transitions are all native CRM fields. A CRM that stores stage history reports cycle length and days-per-stage in one query. Teams measuring cycle length in a spreadsheet lose data accuracy the first time a deal is reopened or reassigned, and the number stops being trusted inside two quarters.
The sales cycle length calculation is simple subtraction, but the rules around it are where every team quietly disagrees. For each closed-won deal in the measurement window, subtract the opportunity created date from the closed-won date to get the deal cycle in days. Average those deal cycles across the segment to get the segment cycle length. The result is a single integer. The point of the number is period-over-period comparability, which only works if the inclusion rules stay consistent across quarters. Write the rules down once and apply them the same way every time.
Use the closed-won date to decide which deals belong in the quarter. A deal created in Q1 and closed in Q3 belongs in Q3 is cycle length average, not Q1. Grouping by created date instead of closed date delays the signal by a full cycle and makes the trend read incorrectly for every quarter the team is growing.
Only closed-won deals go into the average. Closed-lost deals have a different cycle shape, often shorter because they died early. Open deals have no closed date yet. Mixing in either one blends two different motions and makes the number tell a story that is not true.
If a deal gets reopened and then closed-won later, use the final close date, not the first. The cycle length should reflect how long the customer actually took to decide, including the pause. Teams that use the first close date understate the cycle for every deal that bounced, which is often ten to twenty percent of the pipeline.
An opportunity is created when a rep has confirmed fit, confirmed interest, and scheduled a next step. Different teams start the clock earlier or later. Pick a bar, write it down, and apply it the same way for every rep and every segment. The absolute number matters less than the consistency of the measurement.
Report cycle length as a whole number of days, by segment, by quarter. Decimals in cycle length are false precision; nobody runs a review off a cycle of forty-two point seven days. Round to whole days so the trend reads clearly and the number anchors in the conversation instead of distracting from it.
If the definition changes, change it going forward and keep the old series intact for comparison. Retroactively redefining what counts as created is the fastest way to break trust in cycle length. Nothing in the number should move except underlying execution, or the signal is lost.
There is no universal good number for sales cycle length because the segment, product category, and buyer involvement all drive it. SMB B2B cycles typically run thirty to forty-five days when the buyer is a single owner-operator with budget authority. Mid-market cycles land between sixty and ninety days once a second stakeholder enters the decision. Enterprise cycles run ninety to one hundred eighty days or longer once procurement, security review, legal review, and executive sponsorship get involved. The right benchmark is your own trend over the last four to eight quarters, segmented the same way every time, with the industry ranges as a sanity check rather than a target.
SMB B2B cycles usually land in the thirty to forty-five day range. The buyer is often a single owner-operator or a founder with budget authority and no procurement process. The cycle is dominated by evaluation and buying intent, not by committee. Longer than forty-five days in SMB often signals a qualification problem upstream, not a sales problem.
Mid-market cycles run sixty to ninety days once a second stakeholder enters the decision and basic procurement controls apply. Expect one or two meetings beyond the initial demo, a security questionnaire of moderate depth, and a legal review that is standard but not negotiated line by line.
Enterprise cycles routinely run ninety to one hundred eighty days, with major deals stretching to twelve months. Procurement, security review, legal, finance, and executive sponsorship each add days. The cycle is dominated by internal buyer processes, not by the rep is cadence, which is why enterprise motions reward multi-threading more than aggressive follow-up.
Expansion deals with existing customers routinely close in half the cycle length of new-logo deals or less. The vendor relationship, security review, and legal paper are already in place. Blending new-logo and expansion into one cycle number flatters the overall average and hides whether new-logo motion is actually working.
Inbound deals close faster because the prospect raised a hand and already has budget intent. Outbound deals take longer because the rep is creating demand that did not exist, and the buyer has to pull a project forward. Measure the two motions separately or outbound metrics get buried under inbound averages.
A cycle trend shortening ten percent quarter over quarter is a healthier signal than a flat industry-leading number. The absolute figure is heavily driven by product category and buyer segment. The trend reflects execution changes the team actually controls. Report both, but drive decisions off the trend.
Cycle length drops when the time between stages drops. The first step is to decompose the cycle into days-per-stage, so the team knows where the real time hides. Most teams discover that one or two stages account for sixty to eighty percent of the total cycle, and those stages are usually where process and automation have the lowest coverage. Targeting the longest stage with proposal automation, electronic signature, security pre-work, routing rules, and stage-exit criteria consistently removes days. The compounding effect matters: every day shaved off the cycle raises sales velocity, lowers pipeline coverage requirements, and tightens forecast reliability.
The total cycle length is an average. The useful signal is the days-per-stage breakdown. Stage history data shows exactly where deals pause, which stage transitions require the most elapsed time, and where process gaps live. Teams that skip this step tend to apply cycle-shortening work to the whole motion rather than the stage that actually needs it.
A tighter qualification bar at opportunity creation removes deals that would spend ninety days drifting before closing-lost. Those deals do not contribute to cycle length (closed-lost is excluded), but they consume rep time that could compress real cycles. Discovery that qualifies out bad fit early shortens the real motion.
Proposal automation, electronic signature, pre-filled security questionnaires, and templated contracts each remove days from the back half of the cycle. The gain is biggest in enterprise motions where paper is the dominant time cost, but even SMB cycles shrink when the contract takes an hour instead of a week.
Deals with three or more active contacts close faster than single-threaded deals, and they are less likely to stall when the champion leaves. In mid-market and enterprise, the stall risk from single-threading is often larger than the deal risk from losing to a competitor. Multi-threading is the cheapest cycle-shortening lever in enterprise.
Explicit stage-exit criteria stop deals from lingering in stage because a rep is uncomfortable asking the hard question. If a deal cannot pass the exit criteria, it either goes back a stage or gets disqualified. Both outcomes are cycle-shortening, because they remove the ambiguous middle where cycle length quietly inflates.
Routing rules that match the deal to the right AE, SE, or exec sponsor at the right stage remove the days spent waiting for the right person to join. The cycle length cost of waiting is often one to two weeks per deal. Automation here is cheap and the gain compounds across the pipeline.
Strkr stores opportunity created date, stage history, and closed-won date natively, so cycle length and days-per-stage come out of the same dataset the team is already using. Segment, source, rep, and cohort views come from one query instead of three different exports.
Sales cycle length is the average number of days from the moment an opportunity is created in the pipeline to the moment it is marked closed-won. It measures selling speed, not deal quality, and is a core input to sales velocity, pipeline coverage, and capacity planning. The right measurement is always by segment, never a blended aggregate.
There is no universal number because the segment drives it. SMB B2B cycles typically run thirty to forty-five days. Mid-market cycles land between sixty and ninety days. Enterprise cycles run ninety to one hundred eighty days or longer. The right benchmark is your own trend over the last four to eight quarters, segmented the same way every time.
For each closed-won deal in the period, subtract the opportunity created date from the closed-won date to get the deal cycle in days. Average those deal cycles across the segment to get the cycle length. Only closed-won deals are included; open and closed-lost deals are excluded. Group deals by closed-won date, not created date, so the trend reads correctly.
Cycle length is the denominator in the sales velocity formula and a direct input to capacity planning and pipeline coverage. Longer cycles mean more pipeline is needed to hit the same quota, more time per deal from each rep, and a wider forecast window before cash lands. Every revenue model that ignores it tends to over-promise and under-deliver.
Decompose the cycle into days-per-stage, find the longest stage, and target it. The usual levers are proposal automation, electronic signature, pre-filled security questionnaires, routing rules that get the right stakeholder on the call sooner, multi-threading to three contacts per deal, and explicit stage-exit criteria. A tighter qualification bar at opportunity creation also helps by removing deals that would drift.
No. Only closed-won deals go into the average. Closed-lost deals have a different cycle shape, often shorter because they died early, and mixing them in blends two different motions. Track closed-lost cycle separately as a diagnostic for how fast the team disqualifies bad-fit deals.
Monthly for operational diagnosis, quarterly for strategic trend reading. The quarter is the right window for most B2B motions because enough deals have closed to see signal above noise. Weekly cycle length is usually too noisy to act on, outside of high-volume transactional sales teams running thousands of deals per quarter.
Sales cycle is the sequence of stages a deal passes through from first contact to close, which is a process definition. Sales cycle length is the average time in days to traverse that sequence for deals that closed-won, which is a measurement. One describes the shape, the other quantifies the speed.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
