Average Deal Cycle Length: How to Forecast Revenue Without Guessing

In shortAverage deal cycle length is the mean number of days between first contact and signed deal — calculated from your closed-won history, not estimated. Once you have the real number, you can build a 30/60/90-day revenue forecast that holds, because you know when today's open deals will realistically close.

Most revenue forecasts are fiction. Not because the numbers are wrong — because the timing is.

You look at your open pipeline, count up the deal values, and tell yourself (or your client, or your team) “we should close €X this month.” Then the month ends and half of those deals are still sitting in “negotiation,” exactly where they were on day one.

The problem isn’t your closing rate. It’s that you never anchored your forecast to time. You’ve been forecasting amounts without forecasting when.

Average deal cycle length fixes that. It’s the one number that transforms a wishlist of open deals into a timeline — and a timeline into a real revenue forecast.

Here’s how to calculate it, use it, and build a 30/60/90-day forecast that doesn’t embarrass you at end of month.

What is average deal cycle length and why haven’t you calculated it yet?

Average deal cycle length is the mean number of days between first contact with a prospect and the moment they sign or pay. That’s it. No weighted probability, no gut feel, no “it feels like 3 weeks.”

You calculate it from your closed-won deals only. Not your pipeline. Not your lost deals. The deals you actually closed.

Example: you closed 8 deals last quarter. The cycle lengths in days were 12, 18, 22, 35, 41, 45, 52, 67. Add them up (292), divide by 8 — your average deal cycle is 36.5 days. Every deal you enter in your pipeline today should, on average, close in about 37 days.

So why haven’t most closers calculated this? A few reasons.

First, the data isn’t clean. If you’re running your pipeline in a spreadsheet, you probably never logged the exact date a lead entered. You have the close date, maybe. The entry date? Buried in an email thread.

Second, most CRM dashboards show you the metrics managers care about — total pipeline value, number of deals, stage distribution. Deal cycle length as a standalone number, cut by lead source or offer tier, rarely surfaces unless you go looking for it.

Third, closers tend to think in deals, not in time. “I have 12 open deals” feels more concrete than “my oldest open deal is 58 days in and my average cycle is 37.” But the second sentence is the one that tells you whether that deal is about to close or about to die.

How to pull your average cycle length from your CRM (or your Excel)

If you’re using a CRM that logs entry dates and close dates, this is straightforward. Filter to closed-won deals for the last 3-6 months, export the two date columns, calculate the difference in days for each row, average the column. Done in 10 minutes.

If you’re still tracking deals on Excel — and plenty of closers are — you need at least two columns populated: date of first contact (or the date you created the row) and date closed. If you have those, =AVERAGE(DATEDIF(B2:B50, C2:C50, "D")) gets you there.

The honest version: if your spreadsheet doesn’t have a consistent entry date, your first step isn’t calculating cycle length. Your first step is deciding to log it going forward. Start today. In 60 days you’ll have enough data to work with.

A few things to track alongside the raw average:

• Median, not just mean. One 120-day enterprise deal in a batch of 30-day deals will inflate your average badly. The median tells you what typical looks like.
• Min and max. Your fastest deals tell you what’s possible when everything aligns. Your slowest tell you where the friction lives.
• Standard deviation if you want to get serious. A tight spread means your forecast is reliable. A wide spread means cycle length depends heavily on factors you haven’t isolated yet.

If you’re using Fennec, your pipeline already logs entry dates on every deal card. The stats dashboard surfaces deal velocity by stage — which means you can see where the 37 days are actually going, not just that they exist.

How to build a 30/60/90-day revenue forecast that holds

Once you have your average cycle length, the forecast logic is simple: date of pipeline entry + average cycle = expected close date.

Walk through your open pipeline. For each deal, find the date it entered. Add your average cycle. That’s your realistic close estimate.

A deal that entered 32 days ago, with an average cycle of 37 days, should close within the next 5 days — this month. A deal that entered 5 days ago won’t close this month no matter how bullish you feel. Put it in the 30-day bucket, maybe 60.

Now bucket your open pipeline:

• Closes this month (0-30 days remaining): deals where entry date + average cycle falls within the current month
• Next month (31-60 days): deals that should close next cycle
• 60-90 day range: your building pipeline, not this quarter’s cash

Sum the deal values in each bucket. That’s your cycle-anchored forecast.

Is it perfect? No. But it’s grounded in something real — your own historical closing speed — instead of wishful thinking about deal values. You’ll miss some deals early and close some faster than expected, but your forecast range will be right far more often than a pure pipeline-value approach.

One important adjustment: weight by confidence. A deal that’s been sitting at “proposal sent” for 10 days beyond your average cycle is not a normal deal. Flag it as at-risk and drop it to the next bucket until you get a real signal.

This is where tracking follow-up sequences and pipeline stages pays off — if you can see exactly when a deal went quiet, you can act on it before it dies, and you know not to count it in this month’s close.

How cycle length changes by lead source, offer price, and decision-maker level

Your “average” cycle is a useful baseline, but it hides a lot. Segment it and the picture gets sharper.

Lead source matters. A referral who already trusts you might close in 12 days. A cold Meta lead warming up through a VSL funnel might take 45. If you’re running paid ads and tracking ROAS, the deal cycle length on those leads directly affects your payback period — which affects how aggressively you can scale spend. A 10-day cycle and a 60-day cycle at the same CAC are completely different cash flow stories.

Offer price matters. High-ticket deals involve more stakeholders, more hesitation, more “let me think about it.” Your €500 offer and your €5,000 offer should have separate cycle benchmarks. If you’re forecasting both with the same number, you’re going to be wrong on both.

Decision-maker level matters. A solopreneur decides in one call. A small team lead needs to check with a partner. A mid-size company has a procurement process. Each profile has its own natural cycle. Know which type is in your pipeline this month and weight accordingly.

Practically: once you have 15-20 closed deals per segment, split the average. Log the lead source on every deal (your CRM or Fennec’s pipeline fields make this easy), tag the deal size tier, note the decision-maker type. Three months of clean data and you’ll have segment-specific forecasts that are dramatically more accurate than one aggregate number.

When your cycle is getting longer: early warning signs and what to do

Your average cycle creeping up is one of the first real signals that something in your sales process has broken — before your close rate drops, before revenue dips.

Watch for these signs:

1. More deals spending longer in a single stage. If “proposal sent” used to average 5 days and it’s now averaging 14, something changed. Either your proposals are landing differently, you’re attracting a different buyer profile, or your follow-up cadence has slipped.

2. Your oldest open deals are older than 1.5x your average cycle. Deals that far outside your normal range are almost never going to close on their own. They need a hard conversation or a pipeline cleanup. Leaving them in the forecast inflates your numbers and keeps you from focusing on deals that can actually close.

3. Your win rate holds but cycle length grows. This is the sneaky one. Everything looks fine — you’re still closing the same percentage. But you’re closing them slower. Cash flow suffers. Ad spend payback extends. Hiring decisions that depended on revenue timing get painful.

When cycle length grows, diagnose before you intervene. Pull the data by lead source first. If only one source is getting slower, the problem is upstream — lead quality, ad targeting, or the onboarding of that segment. If it’s across the board, look at your follow-up consistency. The most common reason cycles stretch is simple: the rep stopped following up on schedule after the first “not yet.”

A structured follow-up sequence, logged in your pipeline and triggered by stage changes, closes most of that gap without heroics. If you want to dig into the mechanics of that, the sales follow-up guide covers the exact cadence.

Key takeaways

• Average deal cycle length = mean days from first contact to closed-won, calculated from historical data only, never estimated.
• Use the median alongside the mean — one outlier deal can blow up your average.
• Forecast by time, not just value: entry date + average cycle = realistic close estimate. Bucket open deals into 30/60/90-day windows accordingly.
• Segment your cycle by lead source, price tier, and decision-maker type. One aggregate number hides too much.
• A lengthening cycle is an early warning signal — check stage-level data and follow-up consistency before the close rate drops.
• If your pipeline data isn’t clean enough to run this today, start logging entry dates now. Sixty days of clean data beats years of guessing.

Revenue forecasting doesn’t require a spreadsheet wizard or a BI tool. It requires honest data and one reliable number: how long your deals actually take. Get that right and the rest follows.

Sébastien De Bollivier built Fennec around exactly this premise — every stat in the dashboard exists to help closers make better decisions, not to generate reports no one reads. If you want your pipeline to start doing the forecasting work automatically, try Fennec.