Aged Pipeline vs Stale Pipeline

What is the difference between aged pipeline and stale pipeline?

Aged pipeline is measured from the creation date. Stale pipeline is measured from the last meaningful change. They sound like synonyms and they diagnose completely different problems.

A deal created nine months ago that has moved through four stages, had its amount revised twice, and has a close date the rep updated last week is aged. It is also fine. Enterprise deals take a long time and length alone is not a defect.

A deal created six weeks ago that has not changed since the day it was entered is stale. It is younger and it is far more likely to be dead. The clock that matters is the one measuring silence.

How do you measure each one?

Age uses creation date. Staleness uses last modified date on the fields that indicate progress. The definition of meaningful change decides whether staleness measures anything. Use a change in stage, a change in close date, or a change in amount. Those three fields move when a deal actually progresses.

Resist using logged activity counts. Email sync and calendar integrations generate volume automatically, and a rep who copies a nurture list into a sequence produces activity on twenty dead deals without advancing any of them. Activity is easy to fake. A stage change is not.

Why does stale pipeline distort the forecast?

Because every stale dollar counts at full value in coverage and weighted pipeline calculations. The models have no way to know the deal stopped moving.

Across ORM customers, more than 10 percent of open pipeline has typically gone untouched for twelve months. That is a straight overstatement of readiness. A team reporting 4x coverage with a tenth of it frozen is really operating closer to 3.6x, and the deals that remain are not evenly distributed across segments.

There is a sharper number behind the same problem. Of the pipeline carrying in-quarter close dates on the first day of a quarter, roughly 20 percent closes in that quarter. Four fifths of the visible in-period value does not land. Stale opportunities are a large share of that gap, because a deal nobody has touched keeps its close date only until someone remembers to push it.

What makes a deal go quiet?

The earliest slippage signal is the absence of a signal. No stage change, no close date change, no amount change, no reply. Sellers recognize this pattern instinctively. A buyer who stops returning email and stops picking up the phone has usually made a decision the rep has not been told about.

The second signal is more concrete. When a rep moves a close date, the deal becomes less likely to close at all, even when it is sitting in commit. One push is a data point. Two pushes on the same opportunity is a pattern, and a pattern of pushes is the strongest predictor available that the deal will end as a no-decision. That mechanism is covered in more depth under deal slippage.

Both signals are invisible in an age report. A deal can push its close date four times and stay young.

How old is too old?

Twelve months is the rule ORM applies for most of its customers, and it is a defensible default. The reason is empirical rather than arbitrary.

When opportunities are grouped by machine learning and each group gets a predicted close-timing curve, those curves span roughly one week to eighty weeks. Most of the expectation concentrates before week twelve. Very few groups carry meaningful expectation past week fifty-two. A deal open beyond a year is outside the range where nearly every group of comparable opportunities has already resolved.

That does not mean deleting the record. It means the deal needs an explicit exception with a named reason, an owner, and a review date, or it comes out of the pipeline. Silence should not be enough to keep a dollar in the coverage ratio.

Set the threshold per segment. A pipeline selling six-figure platform deals into regulated buyers has a different curve from one selling seats to mid-market teams, and applying a single company-wide cutoff will purge legitimate deals in one segment while leaving zombies in another.

How should you run the cleanup?

Scrub on a fixed cadence, before the quarter starts, and make the outcome binary. A monthly review that produces "keep watching" on every record accomplishes nothing.

Each stale opportunity gets one of three outcomes. It is requalified with a new close date and a documented next step. It is closed with an honest reason code. Or it is moved to a nurture status outside the pipeline where it stops counting toward coverage.

Report the results as a share of dollars rather than a count. Ten stale small deals are a hygiene annoyance. Two stale seven-figure deals are a forecast problem, and a count-based report treats them the same.

Which metric belongs on the dashboard?

Both, and in that order: stale first, aged second. Staleness is the actionable one because every stale deal has a specific person who can resolve it this week.

Aging belongs next to it as context rather than as an alarm. Track median days open by segment and compare it against your own history. When median age rises while win rate holds, cycles are extending and your capacity plan is about to be wrong. When median age rises and win rate falls at the same time, the market moved.

Neither metric should be read in isolation from pipeline coverage. A coverage ratio computed on unscrubbed pipeline is the single most reassuring number on a bad dashboard. Clean the denominator of silence first, then decide whether the ratio means anything.