Average Sales Cycle Calculator

The average sales cycle is the mean number of calendar days between the moment an opportunity starts, ideally the date it was qualified, and the date it was won. It is calculated on won deals only. Sales managers, revenue operations teams and founders use it to set realistic close dates, plan how early pipeline must be created to land in a period, and spot where deals slow down. It describes how long past wins took; it does not predict when a given open deal will close.

For each won deal, the calculator counts the calendar days between the start date and the won date. It adds these durations and divides by the number of won deals to get the average. It also sorts the durations to show the median (the middle value, half the deals faster and half slower) and the shortest and longest cycles.

Every row must use the same start milestone. The qualified date is the default and recommended, because it measures the selling effort on genuine opportunities; the created date is available as an explicit switch but includes time spent before qualification, which varies with how quickly records are cleaned up. A won date earlier than the start date is rejected, and at least one deal is required: with no won deal there is no cycle to measure.

What each term means

Start milestone

Which CRM date the cycle is measured from. Keep the same milestone when you compare periods.

Where to find it: Choose which CRM date marks the start of the cycle: the qualified date (default) or the created date. Use the same choice for every deal and every period you compare.

Opportunity start date

Chosen start milestone, preferably date qualified.

Where to find it: For each won deal, the date it reached the chosen milestone, as stored in the CRM (often a stage history field such as the date it entered your qualified stage).

Won close date

Date when a won deal was finalized.

Where to find it: For each deal, the date it was marked closed-won in the CRM. List only won deals from the same segment and period, for example all deals won last quarter by the mid-market team.

Days to win

Calendar days between the start milestone and the won date of one deal.

Average sales cycle

Mean elapsed days from the start milestone to the won date.

Hypothetical example: a team won three deals that took 20, 40 and 60 days from qualification to signature.

1. Average sales cycle(20 days + 40 days + 60 days) ÷ 3 = 40 days

Average sales cycle = 40 days

Average = (20 + 40 + 60) ÷ 3 = 120 ÷ 3 = 40 days, and the median is also 40 days, with a shortest cycle of 20 and a longest of 60. If the third deal had instead taken 120 days, the average would jump to (20 + 40 + 120) ÷ 3 = 60 days while the median stayed at 40: a sign that one long deal, not the typical deal, is driving the average.

Hypothetical numbers, used to show the calculation. Not real company data.

Use the sales cycle to set realistic expected close dates when new opportunities are created. If won deals typically take 40 days from qualification, an opportunity qualified today and dated to close next week deserves a question.

It also tells you how far ahead pipeline must be generated. If the median cycle is three months, opportunities created in the last month of a quarter will mostly land in the next one, which matters for coverage and forecasting.

Track it per segment and after process changes, such as a new approval step, a pricing change or a free trial. A change in the cycle is often the first visible effect of such decisions.

A long cycle is not automatically a problem. Enterprise purchases often involve several departments, security and legal reviews, procurement rules and budget calendars. A cycle of several months can be the natural pace of that buying process, and pushing it too hard can cost trust or margin. The useful question is whether the cycle is longer than it needs to be for that segment, not whether it is long in absolute terms.

To answer it, split the total into stages. Using the CRM stage history, measure how many days won deals spend in each stage, for example qualification to proposal, proposal to negotiation, negotiation to signature. The stage where time accumulates, or where its spread is widest, is usually where the bottleneck sits: waiting for a technical evaluation, a pricing approval or a contract review.

Then look at what happens there. Some delays come from the buyer and can only be anticipated, such as a budget committee date; others come from your own process, such as proposal turnaround or internal discount approvals, and can be shortened directly. Compare the median rather than the average when you do this, because a few exceptional deals can dominate the totals.

A shorter cycle means won deals closed faster from the chosen milestone. It is desirable when it comes from less waiting and smoother decisions, less so when it comes from smaller deals or heavier discounting, so read it alongside average deal size.

When the average is much higher than the median, a few long deals are pulling it up; the median better describes a typical deal, and the long deals deserve to be studied individually.

Practical levers

• Measure time per stage and work first on the stage where deals wait longest.
• Agree on a mutual plan with the buyer: decision steps, people involved and target dates.
• Reduce internal delays such as proposal preparation, discount approvals and contract drafting.
• Qualify the buying process early (who signs, which reviews, which budget) to avoid surprises late in the cycle.

Common mistakes

• Mixing deals measured from the created date with deals measured from the qualified date.
• Including lost or open deals, which have no won date.
• Relying on the average alone when one or two deals are far longer than the rest.
• Mixing enterprise and small-business deals in one figure.
• Comparing cycles across periods after the definition of a stage has changed in the CRM.

Scenario comparison

The conservative case adds 10 days to every deal’s cycle and the optimistic case removes 10 days (never going below zero). With the example deals, the average would become 50 or 30 days. These are illustrative shifts, not predictions.

Use the comparison to judge consequences rather than the number itself: what a 10-day change would mean for your close dates, for the pipeline you need to create in advance, and for sales velocity.

Only won deals are measured. Lost deals and deals still open, some of which may have been running for a long time, are not included, so the figure describes how long successful deals took, not how long every opportunity lasts.

Selecting deals by won date favours recently closed fast deals in short periods; longer windows give a fairer picture of slow deals.

Durations are calendar days, including weekends and holidays, and depend on how reliably start and won dates are recorded in the CRM.