What Is a Sales Cycle?: Stages, duration drivers, and common sources of delay and rework

A slow sales cycle is not actionable until the team can say what clock is running, what buyer evidence advances a deal, and where the same work is being repeated. The operating job is to define that clock, compare like-for-like deal cohorts, and separate necessary approval time from preventable waiting and rework.

The unit is one prospective deal moving from a declared start event—such as qualification or opportunity creation—to a declared outcome, usually closed-won or closed-lost. Salesforce describes the sales cycle as a sequence of stages that moves a prospect toward becoming a customer. One organization may describe a broad cycle from customer research through signature; another may start its measured clock only when a qualified opportunity is created. Both can be useful, but their durations are not comparable until the start event, end event, and included outcomes are explicit.

Calculate sales cycle length from one declared clock#

For a closed-won cohort, the basic calculation is:

Average won sales cycle length = Σ (closed-won date − defined cycle start date) ÷ number of closed-won deals in the cohort

Salesforce Canada’s sales-cycle-length guide expresses the same arithmetic as total days taken to close divided by the number of closed deals. The calculation is simple; the data contract around it is not. State whether the clock begins at first contact, qualification, opportunity creation, or another recorded event. State whether “close” means a signed agreement, a CRM status change, payment, or something else.

Here is an illustrative example, not real company data. Three closed-won opportunities took 18, 27, and 45 days from the team’s declared opportunity-start event to closed-won.

Average won sales cycle length = (18 + 27 + 45) ÷ 3 = 30 days

That result describes those three wins under that boundary. It says nothing about open deals, time spent on losses, or opportunities that never received a clean outcome. Keep separate views for time to win and time to loss or no decision. Also inspect the median and the distribution: an average can be arithmetically correct while concealing a fast transactional motion and a slow enterprise motion in the same total.

Sales cycle, process, pipeline, funnel, and buyer journey are different views#

These terms often appear in the same meeting, but they answer different questions:

Salesforce distinguishes the cycle’s stages from the process used to execute them, and its pipeline guide defines the pipeline as a live view of active deals. Salesforce Canada’s pipeline-and-funnel introduction describes the funnel as the prospect path that narrows as some records do not advance. Gartner’s public buying-journey summary adds an important limit: buyers may revisit problem definition, requirements, validation, and consensus work even while a CRM presents a neat linear sequence.

There is no universal set of sales-cycle stages#

Salesforce presents one common seven-part sequence: customer research, prospecting, qualification and discovery, presentation or demo, proposal, negotiation, and close. Some teams start the measured clock only after the first two. Some separate security review from commercial negotiation. A low-touch product may collapse evaluation and purchase into one session.

The useful design test is not whether a CRM contains seven columns. It is whether each stage makes a distinct, inspectable claim about the deal. A practical B2B model might look like this:

This model separates seller activity from buyer progress. “Proposal sent” is an activity. “The required reviewers received an agreed scope and scheduled a decision review” is evidence of a state. The second statement tells another operator what is true, what remains uncertain, and what should happen next.

How long should a sales cycle be?#

There is no context-free target. Duration changes with the clock boundary, contract value, product and implementation complexity, number of participants, required proof, approval path, and urgency. A short cycle may reflect a low-risk self-service purchase. It can also reflect skipped discovery that creates a poor-fit customer. A long cycle may contain avoidable inactivity, or it may contain necessary security, legal, technical, and consensus work.

Norwest’s 2025 B2B Sales & Marketing Benchmark Report offers a bounded reference point. Its survey, fielded in August 2025, covered 177 sales and marketing leaders from North American and Israeli VC- and PE-backed B2B companies. Respondents reported average cycles of about two to three months for deals below $25,000 in annual contract value and about nine to twelve months for deals above $500,000.

Those figures are reference points, not goals. They are self-reported and come from a particular financing and geographic sample. The report does not make every respondent’s start event, outcome rule, product complexity, or segment mix identical. Comparing a local 70-day figure with the report is useful only after asking whether the units and deal types are genuinely similar.

For operating decisions, compare like with like:

• New business separately from renewals and expansions.
• Similar contract-value and customer-size bands.
• Inbound, outbound, partner, and product-led entry paths when their clocks differ materially.
• Won duration separately from lost and no-decision duration.
• Mature cohorts separately from deals still open at the reporting cutoff.

Then inspect both the whole-cycle distribution and time in stage. A stable overall average can hide a new bottleneck if faster early work offsets a slower approval stage.

Duration has structural drivers and operating drivers#

Structural drivers are properties of the purchase. They are not automatically defects:

• Economic exposure: Higher-value or harder-to-reverse decisions usually require more scrutiny. Norwest’s ACV pattern is consistent with that relationship in its sample.
• Solution and implementation complexity: More requirements, integrations, services, or change-management work create more questions to resolve.
• Stakeholder topology: Users, technical evaluators, finance, executives, procurement, legal, and security may join at different times and use different criteria.
• Approval architecture: Budget timing, risk classification, vendor onboarding, contracting, and compliance can impose real dependencies.
• Existing trust and urgency: A known supplier solving a funded, time-sensitive problem starts from a different position than an unfamiliar supplier addressing a loosely prioritized issue.

Operating drivers come from how the deal is run: qualification quality, stage definitions, handoffs, ownership, information consistency, next-step discipline, and when predictable review work begins. These are the places where a team can reduce waste without pretending that every buyer task should disappear.

Salesforce’s sales-cycle guidance names product complexity, price, stakeholder count, company size, relationships, and market conditions as duration factors. It also describes procurement and legal involvement in enterprise negotiation. McKinsey’s B2B journey cases show the same issue from an operating perspective: multiple stakeholders, fragmented departments, technical inputs, risk assessment, and compliance work can lengthen a journey.

Delay and rework are different failure modes#

Delay is elapsed time without meaningful progress: waiting for an owner, an approval, a meeting, a missing input, or a decision that has no committed date. Rework is effort repeated because a requirement, stakeholder, scope boundary, approval condition, or decision criterion was incomplete or discovered too late. Rework creates delay, but a delay can occur without anyone repeating work.

McKinsey explicitly identifies rework as a source of significant delay in B2B journeys and points to internal controls, auditing, and compliance requirements as recurring causes in its cases. It also describes two useful controls: move predictable review work earlier, and align the responsible teams on specifications and ownership before handoffs. These are case-derived practices, not promises of a universal cycle reduction.

Common patterns include:

Gong adds one correlational signal about next steps. Its analysis covered recorded meetings associated with 28,833 closed deals. The fastest-closing group spent 53% more time discussing next steps during the first meeting than the slow-cycle group, while the same pattern did not appear for time spent on that topic in later calls.

The useful lesson is narrower than “talk longer.” A real next step has a purpose, owner, expected output, and date that both sides recognize. A placeholder follow-up can satisfy a CRM task while leaving the buying work undefined.

Review a sales cycle as a small operating contract#

A dashboard cannot repair an ambiguous cycle definition. Write the contract first, then instrument it in the CRM:

This contract gives a sales manager something more useful than “deals are slow.” It can show whether a segment genuinely requires more buyer work, a specific stage is waiting on an external dependency, or the team repeatedly creates its own delay by advancing without evidence.

Do not optimize for the shortest possible number in isolation. Preserve the buyer work that reduces risk and improves fit; remove ambiguous boundaries, missing owners, late predictable reviews, and repeated artifacts. A healthy cycle is not merely fast. It makes necessary work visible and preventable rework difficult to hide.