Deal age is the number of days since an opportunity was created. Time in stage is the number of days since it last advanced. The two answer different questions, and pipeline reviews that track only one of them miss half the risk on the board.
The two clocks measure different failures
Age measures exposure. A deal open for 200 days has consumed 200 days of rep attention, sat through multiple forecast cycles, and inflated coverage the whole time. Age says nothing about whether it is progressing.
Time in stage measures momentum. A deal that entered negotiation nine weeks ago and has not moved since is stuck, whether it is 60 days old or 400. That is the signal a manager can act on inside the week.
Enterprise motions make the difference obvious. A 150-day-old deal in a segment that averages 150 days is normal. The same deal sitting 45 days in a stage that usually takes 12 is a problem, and the age number will never show it.
What counts as movement
The definition of activity decides whether time in stage means anything. ORM counts a change in stage, close date, or amount as meaningful activity. Logged calls and emails are weaker evidence, because a rep chasing an unresponsive buyer generates plenty of activity on a deal that is already dead.
That distinction matters given how much stale pipeline is normal. ORM sees more than 10% of pipeline untouched for a full year across customer bases. Records like that pass an activity check built on logged tasks and fail one built on field changes.
Set thresholds by group, not by calendar
A flat 90-day aging rule punishes slow segments and lets fast ones drift. ORM groups each opportunity with a machine learning model and predicts a close-timing curve per group, with curves spanning 1 to 80 weeks, most expectation landing before week 12, and very few groups carrying meaningful expectation past 52 weeks.
Against curves like that, the useful question changes from how old a deal is to how old it is relative to deals that behave like it. A deal past the point where most of its group has resolved is late even at 60 days. ORM also applies a twelve-month rule for most customers as an outer boundary on what stays in open pipeline.
Use both in the review
Run the pipeline review on time in stage and the pipeline cleanup on age. Time in stage surfaces the deals that need an intervention this week. Age, combined with the group curve, surfaces the deals that should leave the board entirely.
Clearing those out changes the math everything else depends on. ORM finds that only about 20% of the pipeline carrying in-quarter close dates on day one of a quarter closes in that quarter, so pipeline coverage built on unpurged records is overstated before the quarter starts. Watch deal slippage alongside both clocks, since a close date pushed to a new quarter is the clearest evidence a deal has stopped moving.
Frequently Asked Questions
Which metric predicts a deal outcome better?
Time in stage, because it measures movement rather than existence. A long enterprise deal progressing steadily is healthy, while a young deal that has not moved in six weeks is already in trouble.
What counts as a deal moving?
ORM treats a change in stage, close date, or amount as meaningful activity. Logged emails and calls are weaker evidence, since a rep can generate activity on a deal the buyer has already abandoned.
What is a reasonable aging threshold?
Set it against comparable deals rather than the calendar. ORM applies a twelve-month rule for most customers as an outer limit, and its close-timing curves run from 1 to 80 weeks by deal group, so what counts as old depends on the group a deal belongs to.
Should aged deals be deleted?
Close them out of open pipeline and keep the record. The history is what trains timing models and loss analysis. What has to stop is an untouched deal continuing to count toward coverage and forecast.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like deal age vs time in stage into prescriptive action for your team.
Schedule a Demo