Sales Cycle:
Stages, Length, and Fixing Delays

A sales cycle is the sequence of stages used to convert a prospect into a paying customer, as Salesforce defines it. It describes the progress of a sale; sales-cycle length measures the time that progress takes.

Tracking the cycle means recording both where a deal stands and how long it spends there. HubSpot describes sales-cycle management as monitoring the stages, identifying trends, and deciding which steps need improvement.

What are the stages of a sales cycle?#

The following stages appear in Salesforce’s seven-stage model:

Seven stages are a common teaching model, but their names and boundaries differ. HubSpot’s stage list separates connecting from research, gives objections their own stage, and includes follow-up and referrals after closing. Define the stages around the work required for a sale, and state whether the model includes activity after purchase. For a time-to-close report, end the measurement at the completed sale.

How to calculate sales-cycle length#

The average is calculated by adding the durations of completed deals and dividing by the number of those deals, following Salesforce’s sales-cycle-length formula:

Deal duration = Actual close date − Defined start date
Average sales-cycle length = Sum of deal durations ÷ Number of deals measured

For a report on time to a successful sale, use closed-won deals. To analyze time spent on unsuccessful selling attempts, calculate closed-lost duration separately. Make the calculation reproducible by recording:

• Start event: first contact, qualification, or opportunity creation—choose one and retain that definition.
• End event: the recorded completion of the sale.
• Reporting period: the period in which the measured deals closed.
• Time unit: calendar days or working days.
• Population: the deal types and outcomes included.

Check the fields behind a CRM report. HubSpot’s deal-property documentation defines “Days to close” as the interval between record creation and close date; its close-date field can hold an expected date or an actual one. A record-creation date also needs to match the start event selected for the report. Filter for completed outcomes before treating a close-date calculation as actual elapsed selling time.

Report open opportunities separately, using the reporting date minus the defined start date to measure their current age. This is a reporting recommendation based on the distinction among open, won, and lost deal statuses. Open-deal age measures unfinished work and has no actual closing event yet.

What is a good sales-cycle length?#

A useful target depends on what is being sold and how the purchase is decided. Zendesk’s guidance on typical cycle length identifies industry, product complexity, and customer decision-making as factors. An average from a different kind of purchase is therefore a limited comparison.

For a practical baseline, compare the same kind of sale under the same measurement rules. Keep product category, deal size, customer type, and start event visible. Separate new sales from renewals when their workflows differ. These are comparison recommendations; they do not establish a universal number of days in which a sale ought to close.

Report the median alongside the average. NIST’s explanation of mean and median defines the median as the middle of the ordered observations and explains that extreme values affect the mean more strongly. For an even number of observations, the median is the average of the two middle values. Applying that distinction to deal durations, a gap between the mean and median is a reason to examine the longest deals individually.

How to find the stages causing delays#

Total cycle length tells how long the completed sale took. To locate the delay, examine time spent at each stage. Zendesk recommends stage-duration analysis to identify stages that take longer than the historical average and investigate the cause.

For each stage, retain entry and exit dates. HubSpot distinguishes time in the current stage from cumulative time in a stage, with cumulative duration accounting for repeated visits. Include those return visits when investigating rework.

Use a focused review:

1. Compare the stage durations of similar completed deals.
2. Identify the stages with unusually long waits or repeated visits.
3. Read the associated correspondence, requests, and deal notes.
4. Record the unresolved issue and the next action required.

Review lost deals as well as wins. Zendesk recommends recording specific loss reasons so the outcome can inform changes to the selling process.

How to shorten the sales cycle#

Match the change to the issue identified in the stage review. The following actions draw on published sales-cycle guidance; they are recommendations to test, not promises of a particular reduction.

Evaluate a process change with both duration and conversion. Zendesk’s stage-conversion formula divides the number of opportunities that reached the later stage by the number that reached the earlier stage. Use the same group of opportunities for both counts. This measures movement between stages, while cycle length measures elapsed time.

For the review, record which step changed, compare durations under the same definitions, and examine the resulting wins and losses. HubSpot’s approach to sales-cycle management supports reviewing individual stages and adjusting the process according to what those records show.

Sales cycle vs. sales process, pipeline, and funnel#

These terms describe related aspects of selling:

Use cycle dates to measure duration, pipeline stages to review current opportunities, and funnel counts to examine progression toward purchase. Keep those questions distinct when building a report.