Setting an Auto-Close Rule for Stale Pipeline

An open opportunity that hasn't moved in months still counts toward every coverage calculation, every forecast roll-up, and every quota conversation, even though everyone involved secretly suspects it's dead. That's not harmless optimism; it's a forecasting error that compounds, because leadership makes real decisions, hiring plans, board commitments, based on numbers that include deals with effectively zero chance of closing.

It also has a real opportunity cost. Time a rep spends checking in on a deal that's quietly gone cold is time not spent finding the next one that actually has momentum.

A deal sitting in early discovery for weeks without progress is a very different problem than a deal sitting in final legal review for the same amount of time. The first has probably lost momentum entirely; the second might just be waiting on a slow procurement cycle that's completely normal for a large account. Set a different staleness threshold for each stage, tighter for early stages where inaction usually means real disinterest, looser for late stages where administrative delay is common and doesn't necessarily mean the deal is dead.

Don't auto-close a deal the instant it crosses the threshold. Give the rep a warning, a notification a set number of days before the threshold hits, with a direct prompt: confirm this is still active, push the close date with a reason, or mark it closed now. That grace period turns the policy from something that feels punitive and automatic into a genuine forcing function that gets reps to make an honest call on every deal instead of letting the system quietly do it for them.

A workable stale-deal sequence looks like this:

1. Set a separate staleness threshold for each stage, tighter for early discovery and looser for late-stage legal or procurement review.
2. Send the rep a warning a set number of days before a deal crosses its threshold, so nothing closes by surprise.
3. Ask the rep to choose one response: confirm the deal is still active, push the close date with a stated reason, or close it now.
4. Require a reason code and a short note before the system lets any deal move to closed, so loss reporting stays useful.
5. Review deals closed as went dark or timeline pushed each quarter and reach back out to those with something new to say.

Closing a stale deal should never be a silent status change with no context attached. Require a specific reason code and a short note before the system will let it close: went with a competitor, budget disappeared, went dark with no response, or timeline pushed beyond a reasonable horizon. That data is what makes your loss-reason reporting and your win-loss interview targeting actually useful later, instead of a pile of deals with no record of what happened to them.

A deal that goes dark isn't necessarily gone forever, and closing it for forecast hygiene shouldn't mean forgetting about it. Set a periodic review, quarterly is reasonable, of everything closed as went dark or timeline pushed, and have a rep or marketing reach back out with something genuinely new: a product update, a relevant case study, a change in the prospect's own situation. Some meaningful share of these will actually restart, but only if someone's tracking them separately instead of letting a closed status mean permanently forgotten.

Frame the policy explicitly as forecast hygiene, not as a judgment on a rep's performance, since a stale deal is often the result of a buyer going quiet, not a rep failing to work it. Show reps the aggregate benefit directly: a cleaner pipeline means a coverage ratio leadership actually trusts, which means less pressure to manufacture activity on deals everyone already knows are dead. A policy introduced as punishment gets worked around. One introduced as a shared tool for better forecasting tends to actually get used.

It helps to share the pattern back with the team once you have a quarter of data: how many deals actually got saved by the warning prompt versus how many closed as genuinely dead. Reps who see that the warning step regularly rescues deals that were still alive, not just rubber-stamps ones that were already gone, trust the system more the next time it flags something on their own pipeline.