Rotting deals are a process problem before they are a pipeline problem. Pipedrive helps when the team uses rotting settings to surface neglected deals early enough that follow-up can restart before the opportunity is lost.
Pipedrive’s “rotting deals” feature is one of the most practically useful – and most ignored – tools in the platform. When a deal hasn’t been updated or had activity logged within a configurable time period, Pipedrive displays a decay indicator (red timer icon) on the deal card in the pipeline view. The intent is to prevent what is the single most common cause of lost deals: not the prospect going cold, but the sales rep going cold – failing to follow up while the prospect was still interested. Understanding what rotting deals are, how to configure the feature correctly, and how to build a cadence that prevents pipeline decay is the difference between a Pipedrive implementation that recovers deals and one where the indicator becomes invisible wallpaper.
That works best when the team treats the rotten list as a management queue, not a punishment list. The point is to recover stalled revenue, not to create more admin work.
What Rotting Deals Mean in Pipedrive
| Rotting Indicator | What It Means | Default Threshold | Recommended Configuration |
|---|---|---|---|
| Red clock icon on deal card | No activity has been logged on this deal within the rotting period | 7 days (varies by stage) | Set per-stage based on your sales cycle length |
| Deal card shading (darker) | Extended period with no activity | Varies | Configure visual threshold to match follow-up urgency |
| Rotten deals filter | Filter pipeline view to show only rotten deals | N/A | Use this filter at the start of every week |
The rotting threshold is configurable per pipeline stage in Pipedrive – one of the feature’s most underused capabilities. Early-stage deals where prospects expect quick responses (Prospecting, Initial Contact) might have a 3-day rotting threshold. Later-stage deals in legal review might not rot until 14 days. Configuring different rotting thresholds by stage reflects the reality that follow-up urgency changes as deals progress.
Configuring Rotting Deals in Pipedrive
To configure rotting: navigate to Settings ? Pipeline ? [Select Pipeline] ? Edit. For each stage, you can enable rotting and set the number of days after which a deal is considered rotten. The “activity” that resets the rotten timer includes: logged calls, emails, meetings, tasks marked as done, and deal property updates. Moving a deal to a new stage also resets the timer.
Recommended configuration by stage type:
- Prospecting / Initial Outreach: 3 days – these contacts go cold fastest
- Discovery / Qualification: 5 days – active conversation; frequent contact expected
- Proposal Sent: 4 days – proposal follow-up is critical to conversion
- Negotiation / Verbal Agreement: 7 days – buyer timelines longer; but don’t let it go quiet
- Contract / Legal Review: 14 days – external process; but check in weekly
Building a Weekly Rotten Deal Review Process
A weekly rotten deal review is the single highest-ROI pipeline management habit for Pipedrive users. The process: every Monday morning, filter the pipeline view to “Rotten deals only.” Review every rotten deal and make one of three decisions: (1) log a planned follow-up activity and move the deal off the rotten list, (2) mark the deal as closed lost if there’s no realistic path forward, or (3) move the deal to a dormant stage or disqualify it from the active pipeline.
The goal of this review is to ensure that every rotten deal has a specific action associated with it by end of Monday. A rotten deal with a logged follow-up task is no longer abandoned – it’s scheduled. Rotten deals that sit unaddressed for two weeks are almost certainly dead; clearing them from the pipeline improves both forecast accuracy and the visibility of genuinely active deals.
Preventing Deals from Rotting: The Follow-Up Activity System
The most effective rotten deal prevention system is a simple rule: every deal must have an open scheduled activity at all times. When you complete a call or meeting, before you close it as done, create the next scheduled activity on the same deal. Never log an activity completed without immediately scheduling the next one. In Pipedrive, this takes 30 seconds – select “Schedule an activity” when marking the current activity as done.
Pipedrive’s Autopilot feature (available on higher plans) can send automated reminder emails or create automatic follow-up tasks when deals go rotten – useful for high-volume pipelines where manual monitoring is impractical. Configure Autopilot to create a task assigned to the deal owner when a deal reaches the rotting threshold: “Task: Follow up with [contact] re: [deal name] – deal has been inactive for [X] days.”
“All my deals are rotten and I don’t know where to start”
A pipeline full of rotten deals is a diagnostic that the pipeline isn’t being maintained as an active working tool. This typically indicates one of three things: the deals were entered but never actively worked (wishlist deals that padded pipeline), the rep was too busy with delivery or other work to maintain sales activity, or the rotting thresholds are too short and legitimate in-progress deals are being flagged prematurely. Fix: start with the most recent rotten deals (deals that became rotten in the last 7 days) and triage them first – these are most likely to be recoverable. For deals that have been rotten for more than 30 days with no activity, batch-close them as lost unless you have a specific reason to believe they’re still viable. A pipeline with 15 genuinely active deals is more useful than a pipeline with 80 deals of mixed quality and age.
“Reps are logging fake activities to keep deals off the rotten list”
Gaming the rotten deal timer by logging placeholder activities (“Sent email” with no actual email sent, “Made call” when no call was made) is a sign that the rotting indicator has become a compliance metric rather than a pipeline health tool. Fix: change the management conversation away from “your deal went rotten” to “what happened with this deal?” In a pipeline review, the question shouldn’t be whether the deal is rotten – it should be what the last meaningful conversation with the prospect was, what the next agreed step is, and what the buyer said. A rep who logged five fake activities will struggle to answer these questions; a rep who had five real interactions will not. Focus pipeline reviews on deal conversation quality, not activity volume.
Sources
Pipedrive, Rotting Deals Feature and Pipeline Configuration Documentation (2026)
Pipedrive Academy, Pipeline Management and Follow-Up Best Practices (2026)
Pipedrive Community, Rotting Deals Configuration and Workflow Tips (2025)
Pipedrive, Autopilot and Automated Pipeline Management (2025)
The strongest implementation is the one that produces a clear next step for the rep. If the data is telling the team what happened but not what to do next, the tracking is still incomplete.
Advanced Strategies and Common Pitfalls in Pipedrive Rotting Deals
Step-by-Step Fix: Build Your Foundation Before Scaling
Successful implementation of pipedrive rotting deals follows a consistent pattern: start with a clearly defined use case for a single team, measure the baseline, implement incrementally, and scale only after achieving measurable results in the pilot. Avoid configuring everything simultaneously. A phased approach with 30-day review cycles catches configuration errors before they spread.
Measuring Success: KPIs and Review Cadence
Establish three to five quantifiable success metrics before launch: adoption rate, data completeness score, and process efficiency measured as time saved per rep per week. Review these metrics monthly and tie configuration decisions to data rather than opinion.
What are the key benefits of Pipedrive Rotting Deals?
The primary benefits include improved operational efficiency, better data visibility for management decision-making, and more consistent customer-facing processes. Organisations that implement structured approaches report average productivity improvements of 20 to 35 percent, though results vary based on implementation quality and user adoption levels.
How long does implementation typically take?
Simple configurations for small teams can be live in two to four weeks. Mid-complexity implementations for 20 to 100 users typically take 60 to 90 days. Enterprise-scale projects with custom integrations and data migrations usually require four to nine months from kickoff to full production deployment.
What is the most common reason implementations fail?
Implementations fail most often due to insufficient user adoption rather than technical problems. Systems are configured correctly but teams revert to old habits because training was insufficient, workflows were not simplified, or leadership did not reinforce usage. Executive sponsorship and simplicity of design are the two highest-leverage success factors.
How do you calculate ROI from this type of investment?
Calculate ROI by comparing costs against measurable gains: hours saved per week multiplied by average hourly cost, pipeline increase attributable to improved process, and reduction in revenue lost to poor follow-up. Most organisations targeting a 12-month positive ROI need to demonstrate at least three dollars in measurable value for every one dollar of cost.
Common Problems and Fixes
Common Implementation Challenges to Anticipate
Organisations working on pipedrive rotting deals frequently encounter three recurring obstacles: inadequate stakeholder alignment during planning, underestimated data migration complexity, and insufficient end-user training budget. Addressing all three before go-live dramatically improves adoption rates and time-to-value. Build a project team with representatives from sales, marketing, and IT rather than delegating entirely to one function.