Time in Stage
How long opportunities remain in each pipeline stage. The diagnostic that localises where deals actually stall.
What it reveals
Where deals actually slow down. Aggregate cycle length says a deal took ninety days; time in stage says seventy of them were spent waiting for a security review, which is a specific and fixable finding.
Reading it properly
Use the median per stage. The distribution is right-skewed and the mean describes no typical deal.
Split won and lost. A stage where lost deals sit far longer than won ones is where deals go to die, and the difference is the signal.
Report the share of opportunities exceeding twice the median for their stage. That set is your at-risk pipeline and it is more useful than any coverage figure.
Compare across segments before concluding. Enterprise stages legitimately run longer, and a blended median hides both.
The data-entry distortion
What to do with a slow stage
Check whether the exit criterion is stated and checkable. Stages that lack one accumulate records because nobody knows when to advance them.
Check whether the wait is external — procurement, legal, security — in which case the fix is starting that step earlier rather than pushing harder.
Check whether the stage represents work by someone outside the deal team, which makes it a handoff and subject to the same silent-failure problem.
Prerequisite
This measure requires stage-change history. Many systems store only the current value by default, and history cannot be reconstructed after the fact — so if it is not being captured, enabling it is the first action, and the measure becomes available a quarter later.
RELATED TERMS
Pipeline Velocity
A composite of the four variables determining how fast pipeline converts to revenue: number of opportunities, average deal size, win rate, and sales cycle length.
Sales Cycle Length
The elapsed time from an opportunity's creation to its close. The time dimension underneath capacity planning and forecasting.
Stage-to-Stage Conversion
The proportion of opportunities moving from each stage to the next. The most localised view of where pipeline dies.
COMMON QUESTIONS
- How do you measure time in stage?
- Elapsed days between stage entry and exit, per opportunity, summarised as a median per stage. It requires stage-change history — if your system only stores the current stage, this cannot be computed retroactively.
- What does a long time in stage mean?
- Either the stage genuinely takes that long, or the exit criterion is unclear so nobody knows when to advance. Comparing won and lost deals in the same stage usually separates the two.
- Why do some opportunities show under an hour in a stage?
- Because someone advanced several stages in one sitting to bring the record up to date. A material share of sub-hour transitions means the stage model is recording data entry rather than process.
- Should time in stage be a target?
- No. It is trivially improved by advancing records faster, which is data entry rather than progress. Use it as a diagnostic and pair it with the outcome of the deals concerned.
FURTHER READING
Learn how to apply this: RevOps 101: Revenue Operations Foundations
Definitions are the vocabulary. The courses are where you learn to operate it, with the interactive audit tools.
See the course