Pipeline aging surfaces deal risk that coverage ratios miss
Pipeline aging is the measurement of how long open opportunities have been sitting, and it catches deal stagnation before standard coverage metrics give you a false sense of security. A team that reports strong coverage but holds that coverage primarily in deals that have not advanced in two months is in a weaker position than the coverage number suggests.Coverage tells you how much pipeline exists relative to quota. Aging tells you how much of that pipeline is still alive.
Two ways to measure pipeline age
Total age counts days since the opportunity was created. It is simple to calculate and useful for identifying deals open far longer than a typical sales cycle. Any opportunity older than two full sales cycles deserves attention. Time in stage counts days the opportunity has been in its current stage. This is a more precise signal because different stages carry different expected durations. A deal in initial discovery taking 30 days may be normal. The same deal in contract review for 30 days is a problem.| Measurement | What it detects | Limitation |
|---|---|---|
| Total age | Deals that have survived multiple cycles without closing | Blunt; long enterprise deals can legitimately be old |
| Time in stage | Stage-specific stagnation | Requires stage history data to calculate accurately |
| Age relative to stage benchmark | Deals deviating from your historical norm | Requires baseline data by stage and segment |
Pipeline aging as a forecasting input
A quarter-end forecast built on pipeline that is heavily weighted toward aged deals carries hidden risk. If your historical data shows that deals over 90 days old close at materially lower rates than deals created in the current quarter, those aged deals should carry a haircut in any honest weighted forecast.
The aging distribution also informs pipeline creation urgency. If a large share of your pipeline entered the quarter already aged, you need more new pipeline creation to compensate for the lower expected close rate on the existing base.
Running an aging review
In a pipeline review cadence, the aging view should sit alongside the standard stage-and-value view. Use it to identify which deals need immediate action, which should be put on nurture holds, and which should be marked closed-lost to clean up coverage optics. See zombie-deals for the specific case of opportunities that have been open so long they serve more as coverage decoration than real revenue potential, and time-in-stage for the stage-level measurement that makes aging analysis precise.
Frequently Asked Questions
What is pipeline aging and why does it matter?
Pipeline aging measures how long individual opportunities have been open, either since creation or within their current stage. Standard pipeline coverage metrics show volume and value but not velocity. A large pipeline composed primarily of old, stalled deals overstates realistic revenue potential and obscures the actual capacity shortfall the team is facing.
How do you build a pipeline aging report?
The core report segments open opportunities into age buckets (for example, 0 to 30 days, 31 to 60 days, 61 to 90 days, and 90 days plus) and shows count and total value by bucket and by stage. The more actionable version adds stage-specific thresholds: a deal sitting in Proposal for 45 days when your average close from that stage is 20 days is a flag; a deal in Discovery for 15 days may not be. Threshold-based aging tied to historical stage benchmarks is more precise than raw age.
What should you do with aged pipeline?
Aged opportunities require individual diagnosis, not bulk action. The right response for each deal depends on why it stalled: champion departure requires re-threading, budget freeze may warrant a nurture hold, no next step scheduled is a coaching issue. The pipeline aging report is a prioritization tool that tells you where to spend inspection time, not an automatic cleanup script.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like pipeline aging into prescriptive action for your team.
Schedule a Demo