Sales
Sales Cycle Length: Measure Deal Age and Time in Stage
Measure deal age and stage duration without mixing open and closed opportunities, hiding re-entry or inventing missing timestamps.
What you will learn
- Distinguish closed-deal sales cycle length from open-deal age
- Calculate current and cumulative stage time from an event history
- Handle re-entry, pauses and missing timestamps without misleading averages
Sales cycle length measures the elapsed time from a defined sales starting event to a defined closing event. Deal age measures how long an open opportunity has existed. Time in stage measures one part of the journey. Keep those three measures separate before deciding whether a deal is moving slowly.
Choose a start that fits your sales process, such as accepted qualification rather than the first anonymous website visit. State whether the closing event is won, lost or either. The same label can otherwise conceal very different calculations.
How long is a typical sales cycle?
There is no single useful duration for every business. Compare deals with similar customer situations, products and process definitions. A self-serve purchase and a multi-stakeholder enterprise decision do not become comparable because both appear in the same CRM.
Start with your own completed cohorts and show the count, median, range and coverage. Treat an unusually old open deal as a question to investigate, not automatic proof that the salesperson failed. Procurement, unresolved requirements and inaccurate records can produce different kinds of delay.
Use the B2B sales guide for the broader selling process. This lesson focuses on reconstructing elapsed time accurately.
Reconstruct a deal from its stage history
This original fictional history uses elapsed calendar days, midnight boundaries and a November 15 cutoff. The opportunity remains open.
| Event | Date | Completed interval |
|---|---|---|
| Qualified opportunity created | November 1 | Qualification begins |
| Enters evaluation | November 4 | 3 days in qualification |
| Returns to qualification | November 10 | 6 days in evaluation |
| Re-enters evaluation | November 12 | 2 more days in qualification |
| Observation cutoff | November 15 | 3 current days in evaluation |
At the cutoff, deal age is 14 days. The latest ongoing evaluation stay is 3 days. Total observed evaluation time, including the current stay, is 6 + 3 = 9 days. Qualification accounts for 3 + 2 = 5 days. The two stage totals sum to the 14-day age under this example's continuous-history convention.
This is not a closed-deal sales cycle. There is no close timestamp yet. Do not enter an assumed close date merely to make a duration report complete.
Check what your CRM's duration property means
A field named “cumulative time” may not update the way you expect while a record is still in a stage. HubSpot's documented properties, for example, distinguish completed latest and cumulative stays from time in the current stage. Read the actual system definition before treating a stored property as a live clock.
The fictional calculation above explicitly includes the current stay in its observed total. That convention must not be confused with a product field that updates only after exit. Record timezone, clock boundaries and whether calculations use calendar or business time.
Keep pauses and missing history visible
If a customer asks to pause, retain the elapsed interval and record a pause reason. You can produce an additional active-time view if your definitions and evidence support it, but do not silently subtract inconvenient waits from the headline cycle.
When a timestamp is missing, mark the interval unknown. A current stage and an old creation date are not enough to reconstruct every earlier transition. Likewise, re-entry must remain visible: overwriting the original entry date loses information about the path.
Check imports, merged records and reopened opportunities separately. Decide whether a reopened opportunity continues the original process or represents a distinct one, then use that rule consistently.
Use duration to ask a better question
A long evaluation stay could mean a technical test is unfinished, the customer has not agreed success criteria or the stage is stale. Pair the duration with the last confirmed customer action and next accepted step. Avoid automatic follow-up simply because a clock crossed an arbitrary threshold.
The sales forecasting workflow addresses a related but separate job: evaluating likely outcomes. Duration alone is not a close probability.
Copyable AI prompt
Use this with Aurora AI in Finta, Codex, or Claude, sharing authorized opportunity history.
Analyze [stage events with timestamps], [metric definitions] and [cutoff]. Separate closed-deal cycle length, open-deal age, current stage stay and completed or cumulative stage time. Show re-entry, pauses, timezone and missing intervals. Reconcile totals where the history permits. Flag CRM property-definition differences. Propose questions for the deal owner, not a universal duration benchmark or close probability. Do not invent dates, contact customers or change pipeline stages.Make the clock useful
Explore Finta's Sales Pipeline Analyst for the next pipeline review. Bring the history and definitions together so a duration becomes a prompt for useful investigation rather than a misleading score.