Overdue follow-ups: over a third of open deals to under 5%

The challenge

The team had been on Pipedrive for two years and liked the visual pipeline, but the deal board had quietly become decorative. Reps moved a deal to the next stage when they remembered to, activities were logged after the fact if at all, and on any given day roughly a third of open deals had no scheduled next step or one that was already overdue. Sales leadership found out a deal had gone cold when a prospect emailed asking if the company had lost interest. Pipedrive is built around activity-based selling, the idea that a healthy pipeline is one where every open deal has a defined next action with a date attached, and that reps who complete their activities on schedule close more of their pipeline than reps who don't. The team knew this in theory. In practice, activity types had been left at the Pipedrive defaults, nothing enforced that a deal needed a next activity before it could sit in a stage, and the overdue-activities view existed but nobody was accountable for clearing it. A rep with fifteen overdue calls saw the same dashboard as a rep with zero, and neither felt any different day to day. The compounding problem was that the sales motion itself was outbound and volume-dependent. Reps were expected to run sequences across a large number of leads, and any gap in follow-up discipline didn't show up as one missed deal, it showed up as a slow leak across the whole book. A lead that didn't get a day-3 follow-up call rarely generated a complaint; it just went quiet and got mentally written off, and nobody could say afterward whether it was a bad lead or a dropped one. Manager 1:1s were spent scrolling a rep's board looking for gaps, which is slow, inconsistent between managers, and easy for a rep to talk their way around in the moment. There was also a data-quality angle underneath the activity problem. Deal stages were being used inconsistently, partly because reps had never been given a shared definition of what belonged in each one, so a manager reviewing the pipeline couldn't always tell whether a stage reflected the deal's real status or just where the rep had last dragged it. Fixing the activity gap without fixing the stage definitions would have produced a team that completed activities on schedule but still couldn't forecast reliably, so the two were scoped together. The team had tried to solve this once before by asking reps to "be more disciplined," which produced a brief improvement that faded within a few weeks once the reminder emails stopped feeling new. That result is common and it points at the actual fix: a system that makes the next action visible and overdue activities impossible to ignore outperforms a policy that depends on reps remembering on their own, especially on a team running high lead volume where memory is the first thing to fail under load.

The approach

1. 01

   Pipeline and stage audit

   Reviewed every open deal against its stage and its activity history to see where the board and reality had diverged. This surfaced two patterns: deals sitting in a stage well past the typical time for that stage, and deals with no activity logged in over two weeks despite being marked open. Both became the baseline the team would be measured against after the rebuild, not just an anecdotal starting point.

2. 02

   Stage definitions, in writing

   Ran a working session with the sales manager and two senior reps to agree what each pipeline stage actually means, in terms a manager could verify from the record rather than take on trust. A deal only belongs in "Qualified" if a specific set of facts is on the record, not because a rep feels good about the call. Writing this down first meant the activity rules that followed were enforcing an agreed standard, not one person's opinion imposed on the team.

3. 03

   Activity types rebuilt around the real sales motion

   Replaced Pipedrive's default activity types with ones that matched how this team actually sells — first-touch call, discovery call, demo, proposal follow-up, contract chase — instead of the generic "call, meeting, task" set most accounts never customize. Specific activity types make the pipeline legible at a glance; a manager scanning the board can tell what stage of the conversation a deal is in without opening it.

4. 04

   Mandatory next-activity rule

   Configured Pipedrive so a deal cannot be saved without a scheduled next activity attached. This is the single change that did the most work: it closes the exact gap that let a deal sit with no next step in the first place, and it moved the requirement out of a manager's memory and into the tool itself.

5. 05

   Rotting-deal thresholds per stage

   Set stage-specific rotting-deal alerts so a deal flagged as stalled after three days in early stages and after ten in late-stage negotiation, matching how urgent a gap actually is at each point in the cycle. A generic one-size threshold either nags reps constantly in stages that naturally move slowly or misses real problems in stages that should move fast, so the thresholds were tuned per stage rather than applied uniformly.

6. 06

   Overdue-activity view as a daily habit, not a dashboard

   Built the overdue-activities filter into the view every rep opens Pipedrive to by default, so clearing it becomes the first thing a rep does rather than a report a manager pulls occasionally. A number nobody has to go looking for gets acted on; a number buried three clicks deep gets ignored.

7. 07

   Manager dashboard by rep, not just by pipeline

   Built a reporting view showing overdue activities and rotting deals broken out by rep, so a 1:1 could start from actual numbers instead of a manager scrolling a board hunting for gaps. This also let the manager see patterns across the team — for example, if overdue activities clustered around a specific stage, that pointed at a process problem rather than an individual one.

8. 08

   Lead routing from web forms and chat

   The company generated inbound leads through website forms and a chat widget in addition to outbound, and those had been landing in a shared inbox before manual assignment, which added a lag before the first activity could even be logged. Routing was set up so an inbound lead creates a person, an organization, and a deal with a first-activity due date automatically, removing the gap between lead arrival and the mandatory-next-activity rule taking effect.

9. 09

   Email sync and templated first-touch

   Connected each rep's inbox through Pipedrive's email sync so outbound emails and replies attach to the right deal automatically, and built a small set of first-touch templates for the most common lead sources. The templates were a minor piece of the work but they removed a common excuse for a delayed first activity — a rep staring at a blank email instead of sending a known-good opener.

10. 10

    Duplicate and stale-lead cleanup

    Ran a one-time cleanup merging duplicate persons and organizations, created mostly by the same prospect submitting more than one form over time, and archived deals that had been genuinely dead for months but were still counted as open pipeline. A pipeline padded with dead deals makes every completion-rate number look worse than the live pipeline actually is, and it hides how much of a rep's book needs real attention.

11. 11

    Automation for the predictable follow-ups

    Set up Pipedrive automations for the mechanical parts of follow-up that don't need a human decision — a reminder email at day 3 if a lead hasn't replied, a task created automatically when a proposal is marked sent, an alert to the manager when a deal crosses its rotting threshold. Automating the predictable steps freed reps to spend their judgment on the calls and emails that actually need it, instead of on remembering that a task exists.

12. 12

    Mobile activity logging

    A meaningful share of this team's calls happened from a phone between meetings, and activities logged well after the fact are the ones most likely to be inaccurate or skipped entirely. Reps were set up and trained on logging a completed call and scheduling the next one directly from the Pipedrive mobile app in the moment, rather than trying to reconstruct the day's calls from memory back at a desk.

13. 13

    Testing against a live rep's book before rollout

    Piloted the new stage rules and activity requirements with one rep for a week before rolling out team-wide, specifically to catch rules that were technically correct but impractical in a real day — for instance an early version of the rotting threshold flagged deals as stalled too aggressively in a stage that genuinely involves a multi-week procurement wait. Adjusting before the full rollout meant the team's first impression of the new system was that it worked, not that it needed fixing.

14. 14

    Rollout and reason-based training

    Trained the full team on the new stage definitions and activity rules, explaining the reasoning behind each one rather than presenting them as a compliance requirement — reps adopt a rule faster when they understand what it protects them from, in this case a pipeline that quietly looked worse in a forecast review than it needed to. Reps who had built informal tracking habits of their own were asked how the new system compared, and a few of their suggestions were folded into the final activity types.

15. 15

    Post-rollout tuning

    Treated the first month after go-live as a tuning period. The team reviewed which rotting thresholds were generating alerts reps consistently disagreed with, adjusted two stage thresholds that had been set too tight, and retired one activity type that had turned out to duplicate another. Data quality and rule quality both settle after a few real weeks of use, not on day one, and treating the rollout date as a finish line rather than a checkpoint is a common way this kind of project quietly regresses.

The result

Within about six weeks of rollout, the share of open deals sitting with an overdue activity fell from roughly 38% to under 5%, and it has stayed there because the mandatory-next-activity rule makes the old state hard to recreate by accident. The mechanism was simpler than the number suggests. Reps were not undisciplined; they were working in a system that let a deal exist without a next step, so some deals inevitably drifted once a rep's attention moved elsewhere. Once the tool itself required a next activity before a deal could be saved, that specific failure mode became structurally difficult rather than a matter of willpower. The rotting-deal thresholds and the default overdue view did the rest, turning a stalled deal from something a manager might notice in a 1:1 into something a rep saw the moment they opened their own board. A secondary effect mattered nearly as much as the headline number. Because stage definitions were now written down and enforced by activity requirements, the pipeline became something the sales manager could forecast from directly, rather than mentally discounting because everyone knew some deals were further behind than their stage suggested. Manager 1:1s shifted from an audit of the board to a conversation about specific rotting deals and what each one actually needed, which is a more useful use of a weekly meeting. It is worth being honest about what this project did not fix. It did not improve close rates on its own, and it did not make a genuinely weak lead source stronger; those depend on messaging, targeting, and the product, none of which activity discipline touches directly. What it did was make sure that every real opportunity in the pipeline got a fair, timely attempt, instead of losing a share of them to simple neglect. For an outbound-heavy team, that is a meaningful chunk of otherwise-recoverable pipeline, but it is a floor being raised, not a ceiling. The most transferable lesson from this pattern is that activity-based selling only works when the activity requirement is enforced by the tool rather than requested of the team. Asking reps to be more disciplined produces a short-lived improvement; making the undisciplined state structurally awkward to reach produces a lasting one. The second most transferable lesson is that the rotting-deal thresholds have to match the real rhythm of each stage — a threshold copied uniformly across a pipeline either nags reps in slow-moving stages or misses real problems in fast-moving ones, and either failure mode teaches the team to stop trusting the alerts.

Delivered within aibrevo's typical Pipedrive implementation timeline — see the Pipedrive implementation page for the full range.