The problem in numbers
Run two filters on your open pipeline today. Deals with no activity scheduled, and deals whose last change is older than thirty days. In accounts we audit, the two lists together typically cover a quarter to a third of open pipeline value. That value sits in the weighted forecast at full stage probability, month after month, while its real probability slides toward zero.
The damage is threefold. The forecast overstates, and leadership plans against air. Reps spread attention across deals that will never close, at the cost of deals that might. And when the stalled deals finally get marked lost, they land in one quarter as a cliff, making a slow leak look like a sudden collapse.
The design
Layer one is the rotting setting itself, per stage, in days. Base the thresholds on evidence: the deal duration view in Insights shows how long won deals historically spent in each stage. Set rotting at roughly one and a half times that dwell time. A typical B2B result: 7 to 14 days in early stages, 14 to 30 in proposal and negotiation stages. Thresholds set by feel end up either invisible or ignored, and both defeat the point.
Layer two is the activity rule that gives rotting teeth: every open deal carries a planned next activity, no exceptions. Pipedrive supports it with the deals without activity filter and with a workflow automation that creates a follow-up task whenever a deal changes stage. Rotting measures silence. The activity rule makes silence rare, so red actually means something. Both layers stand on stage definitions with real exit criteria, which is stages and probabilities territory.
Layer three is the escalation path, because a red deal with no consequence is wallpaper within a month. Week one red: the rep acts, reactivate or lose. Week two red: the deal appears in the pipeline review, and the question is what would move this, asked once. Week three red: the deal gets a decision, a concrete revival plan with a date, or lost with a reason. Lost with a documented reason is a good outcome. It cleans the forecast and feeds the win-loss numbers with truth.
Implementation steps
Start with the cleanup, not the settings. Take the thirty-days-silent filter and decide every deal on it once: real, or lost with a reason. This pass hurts, shrinks the pipeline visibly, and is the moment the forecast becomes honest. Announce the shrink to leadership in advance, because a pipeline that halves overnight needs context.
Then set the thresholds from your duration data, switch rotting on, and build the two supporting pieces: the follow-up automation on stage change, and a rotten deals filter per rep for the weekly review. Finally, put a recurring fifteen minutes into the weekly sales meeting for the escalation pass. The ritual carries the system. Accounts where rotting works all share that one meeting habit, and it doubles as the enforcement end of your response SLAs.
How you measure that it works
Watch three numbers monthly in Insights. The share of open deals currently rotten: healthy accounts run under ten percent. The average age of open deals per stage: it should fall for two or three months after rollout, then stabilise. And the lost-reason distribution: a rising share of no decision and went quiet losses in the first quarter is the system working, flushing old air out of the pipeline. Expect win rates to look better within two quarters, not because selling improved, but because the denominator stopped lying, which also steadies the forecast.
Common failure modes
Red blindness: thresholds so tight that half the pipeline glows, and the team learns to see past it within weeks. Loosen until red is rare enough to mean something. The activity shuffle: reps push the follow-up date forward every Friday, so deals never rot while never moving. Counter it in the review by asking for the buyer's last verifiable action, not the rep's next intention. The parking stage: a nurture or on-hold stage with rotting disabled becomes the graveyard annex. Kill the stage, mark the deals lost with reasons, and let a revival filter handle genuine long shots. And threshold decay: the sales cycle changes, nobody revisits the day counts, and rotting drifts out of tune. Recheck thresholds against duration data twice a year.
Questions
What does deal rotting actually do in Pipedrive?
You set a number of days per stage in the pipeline settings. A deal that sits in that stage longer without progress turns visibly red in the pipeline view. It is a visual flag, not an action. What happens next is your process, which is what this playbook supplies.
How many days should each stage get?
Read your own history first: the deal duration reports in Insights show how long won deals actually spent per stage. Set rotting at roughly one and a half times the typical won-deal dwell time. Early stages usually get 7 to 14 days, later stages 14 to 30.
Is a rotten deal a lost deal?
No, it is an undecided one, and that is the problem. The escalation path exists to force a decision: reactivate with a real next step, or lose it with a reason. Both outcomes beat the third state, which quietly corrupts your forecast for months.
Reps say rotting feels like surveillance. How do we handle that?
Frame it on the deal, not the rep. Rotting measures deal momentum, and stalled deals waste rep time more than anyone's. Teams accept it quickly when the weekly review asks what do you need to move this rather than why is this red.
Should rotting apply to every pipeline?
Every pipeline where time pressure is real, which is most sales pipelines. Long-cycle pipelines still benefit, just with longer thresholds. Skip it only where dwell time is genuinely meaningless, such as a passive partner-referral pipeline that waits on third parties by design.