Knowledge Library · Reviews

Powered by Pulse — Value Added. The #1 source of truth in revenue operations. Find the bottleneck. Fix the pipeline. Win the quarter.

How do you coach reps to remove dead deals from the pipeline?

Curated byKory White · Fractional CRO · Maryland

How do you coach reps to remove dead deals from the pipeline?

📖 2,324 words🗓️ Published Sep 8, 2026

Direct Answer

You coach reps to remove dead deals from the pipeline by pairing a mandatory diagnostic ("what did the buyer *do*, not say, in the last 14 days?") with a low-shame, scheduled ritual — never a one-off purge. Coach the sunk-cost attachment directly, install a 14/21-day re-engage/close-lost rule, and make weekly pruning as routine as forecasting. For a RevOps leader, the win isn't fewer deals — it's a pipeline number people can actually trust.

The Two Ways to Get Dead Deals Out of the Pipeline

There are really only two structural approaches to removing dead deals, and most sales orgs pick one by accident instead of by design. Understanding both — and their failure modes — is what separates a manager who coaches pruning from one who just nags about it.

Option A: Manager-Led Coaching Cadence. This is a recurring, human-run review — typically weekly in the 1:1 — where the manager and rep walk the board together, apply a disqualification standard, and jointly decide what gets re-staged, re-engaged, or closed-lost. The manager owns the diagnostic questions ("what did the buyer *do* in the last 14 days?"), models the language for closing gracefully, and coaches the emotional resistance in real time. This is a coaching intervention, not an admin task — its entire value is in the conversation, not the data cleanup. It works because it addresses the *will* problem directly: reps hoard dead deals because closing them feels like failure, and only a human can reframe that in the moment.

How do you coach reps to remove dead deals from the pipeline — figure 1

Option B: System-Enforced Auto-Aging Rules. This is a CRM-automated approach: a workflow rule flags or auto-moves any deal with no logged activity in a defined window (commonly 14, 21, or 30 days), pinging the rep, then escalating to the manager, then — in the most aggressive configurations — auto-closing the deal as "stale, no action" if the rep doesn't respond. Tools like Salesforce flow builder, HubSpot workflows, or a RevOps-built script in the data warehouse can enforce this without a human ever having the conversation. It works because it removes the rep's discretion entirely: there's no negotiation with a system rule the way there is with a manager's judgment call.

In practice, the strongest programs run both, sequenced deliberately. System rules (Option B) act as the tripwire — they surface which deals are stale so nobody has to manually sort a 200-row pipeline by eye. But the actual behavior change — the rep learning to self-prune before the system flags them — only happens through Option A's coaching layer. A pure system-only approach breeds resentment and workarounds (reps logging a fake "touched base" note every 13 days to dodge the flag). A pure coaching-only approach without automation doesn't scale past a handful of reps and depends entirely on the manager remembering to run the review every week.

How do you coach reps to remove dead deals from the pipeline — figure 2

The trade-off comes down to trust versus scale. Manager-led coaching builds the underlying skill and changes how a rep thinks about their own forecast — but it's slow, inconsistent across managers, and vanishes the moment a manager gets busy. System-enforced rules scale instantly across every rep and territory and never forget to run — but on their own they train reps to game the metric instead of actually reassessing the deal. The right call depends on team size, CRM maturity, and how much you can trust reps to self-report honestly once the stakes (comp, forecast credibility) are attached to the number.

How to Decide Between Them

The decision isn't binary — it's a sequencing question. Small teams (under 8 reps) with a hands-on manager should lean almost entirely on Option A first, because the manager can realistically review every rep's board weekly and the coaching relationship is strong enough to carry the behavior change. Larger teams (15+ reps, multiple managers) need Option B's automation as scaffolding, because inconsistent manager cadence becomes the single biggest failure point at scale — some managers run tight weekly reviews, others let three weeks slip, and the pipeline data quality diverges by team.

How do you coach reps to remove dead deals from the pipeline — figure 3

The other deciding factor is how much emotional resistance you're seeing. If reps openly admit deals are dead but won't act ("I know it's probably gone, but..."), that's a *will* problem — pure coaching, no automation needed, because a system flag won't change how someone feels about their number. If reps genuinely can't distinguish a stalled deal from a dead one, that's a *skill* gap — automation actually helps here, because the system's objective 14/21-day rule gives them the missing framework. If a rep's pipeline goes nearly empty the moment you prune it, stop pruning and pivot to a *system/territory* diagnosis — that's a demand problem, not a discipline problem, and no amount of coaching or automation fixes an empty top of funnel.

Concrete Numbers Behind Each Option

Manager-led coaching cadences that actually stick share a specific rhythm: a 15-30 minute segment inside the existing weekly 1:1, reviewing the three to five oldest open deals by stage age rather than the whole board (reviewing everything every week burns out both parties within a month). The disqualification window that shows up most consistently across RevOps playbooks is 14 days with no buyer action triggers a re-engagement email; 21 days with no reply triggers close-lost. Teams that use a looser 30-day window tend to carry 20-30% more dead weight in pipeline because deals get three extra weeks to decay before anyone questions them.

How do you coach reps to remove dead deals from the pipeline — figure 4

On the target state: a healthy pipeline should have fewer than 20% of open deals older than 90 days relative to your average sales cycle length. If average cycle is 45 days, any deal sitting past 90 days (2x cycle) with no recent activity is almost certainly dead weight, not a "long deal." Slipped-deal rate — the percentage of deals whose close date moved right in a given month — is the other number worth tracking; anything consistently above 30-40% of the active pipeline slipping monthly is a strong signal of hoarding rather than genuinely long cycles.

System-enforced rules carry their own numbers. Auto-flag thresholds in CRM workflows are typically set at 14 days (warning to rep), 21 days (escalation to manager), 30 days (forced re-stage or auto-close-lost if no response). Pipeline coverage ratio is the number this all rolls up into: a forecast built on a bloated, zombie-filled pipeline might show 4x coverage that's really closer to 2x once dead deals are stripped out — and RevOps leaders who've cleaned up a pipeline this way report the "real" coverage number is often 30-50% lower than the pre-cleanup figure. That's not bad news; it's the first accurate number leadership has seen in months, and it's what actually justifies headcount or territory changes instead of an inflated fiction.

How do you coach reps to remove dead deals from the pipeline — figure 5

Incentive-side numbers matter too: tying a small 5-10% of quarterly variable comp to a pipeline-quality score (deal-age distribution, contact freshness, close-lost velocity) is enough to shift behavior without turning pruning into a punishment. Go much above that and reps start gaming the metric instead of genuinely reassessing deals.

Implementation Details and Sequencing

Roll this out as a 30/60/90-day build rather than flipping a switch, and put the system automation in place *before* asking reps to change behavior, so the coaching conversation has real data to point to instead of a manager's gut feeling.

How do you coach reps to remove dead deals from the pipeline — figure 6

Days 1-30 — Manager-led, system-assisted. Turn on the CRM aging flags (14/21-day thresholds) so stale deals surface automatically, but keep the actual close-lost decision manual and manager-co-piloted. Every Monday review, walk the three oldest flagged deals together, model the breakup-email language, and code the close-lost reason live so the rep watches how it's done without shame attached.

Days 31-60 — Rep-led, manager-audited. The rep now prunes their own board before the 1:1 using the same system flags as the trigger, then presents what they cut and why. The manager's job shifts from doing the pruning to auditing for honesty — specifically watching for reps who slip close dates right instead of admitting a deal is dead, since that's the most common workaround once pruning has real stakes attached.

How do you coach reps to remove dead deals from the pipeline — figure 7

Days 61-90 — Self-sustaining, spot-checked. Pruning becomes the rep's own standing habit, driven by the same automated flags, with the manager checking in monthly rather than weekly and only re-engaging directly if stage age or slip rate spikes again.

Sequencing this way — automation first, coaching layered on top, then fading the manager's hands-on involvement — avoids the two most common failure modes: a system-only rollout that trains reps to game the flags, and a coaching-only rollout that collapses the moment the manager gets pulled into something else for a few weeks. It also gives RevOps a clean, auditable trail: every close-lost has a coded reason, every flag has a resolution, and the pipeline number leadership sees each Monday is one they can actually act on.

How do you coach reps to remove dead deals from the pipeline — figure 8

FAQ

How do I know if a deal is truly dead versus just slow? Apply the last-buyer-action test, not the rep's optimism. No real action — a reply, a meeting, a shared document — in 14 days makes it stalled; in 21 days, dead. A genuinely slow deal still has a mutual action plan and a live champion.

Won't removing dead deals hurt our pipeline coverage ratio? It corrects a false one. A coverage ratio inflated by dead deals is a number that feels safe but lies to leadership. Real 2x coverage beats fictional 4x, because accurate coverage drives honest territory and headcount decisions instead of getting the help cut off later.

A rep is emotionally attached to a deal they admit is dead — what do I say? Name the sunk cost directly: the work already done doesn't come back whether the deal stays open or not. Ask if a brand-new rep inheriting it today, with zero history, would call it live. Then close it together as a shared, low-shame act.

How often should the pipeline actually get pruned? Weekly, inside the existing 1:1, sorted by stage age and last action. Monthly reviews let zombies multiply and the forecast drift; daily reviews create churn without added benefit. Weekly is the sustainable middle.

What if pruning leaves a rep with almost no pipeline? That's diagnostic, not a discipline failure. An empty pipeline after honest pruning points to a system or territory problem — thin lead flow or a starved outbound cadence — not a rep who needs more coaching on cutting deals.

Can automation replace the coaching conversation entirely? No. Automated flags surface *which* deals are stale, but only a manager can reframe the emotional attachment that makes a rep resist closing one. Use automation as the tripwire and coaching as the behavior change.

Sources

flowchart TD S["How do you coach reps to remove dead d"] S --> N0["The Two Ways to Get Dead Deals Out of "] N0 --> N1["How to Decide Between Them"] N1 --> N2["Concrete Numbers Behind Each Option"] N2 --> N3["Implementation Details and Sequencing"]

flowchart LR C["How do you coach reps to remove dead d"] C --> H0["The Two Ways to Get Dead Deals Out of "] C --> H1["How to Decide Between Them"] C --> H2["Concrete Numbers Behind Each Option"] C --> H3["Implementation Details and Sequencing"]

Related on PULSE

[What question would you ask during a pipeline review to force a rep to prioritize deals based on probability, not hope?](/knowledge/cg0902)
[How do you coach reps to commit deals they can actually close?](/knowledge/cg0104)
[How do you coach a solutions consultant to qualify deals earlier?](/knowledge/cg0220)
[How do you coach a mid-market rep stepping up from SMB deals?](/knowledge/cg0212)
[How do you coach a rep to stop discounting to win deals?](/knowledge/cg0083)
[How do you coach a rep to qualify out bad-fit deals early?](/knowledge/cg0055)

Download:

## Direct Answer

You coach reps to **remove** dead **deals** from the **pipeline** by pairing a mandatory diagnostic ("what did the buyer *do*, not say, in the last 14 days?") with a low-shame, scheduled ritual — never a one-off purge. **Coach** the sunk-cost attachment directly, install a 14/21-day re-engage/close-lost rule, and make weekly pruning as routine as forecasting. For a **RevOps** leader, the win isn't fewer deals — it's a pipeline number people can actually trust.

## The Two Ways to Get Dead Deals Out of the Pipeline

```mermaid
flowchart TD
  S["How do you coach reps to remove dead d"]
  S --> N0["The Two Ways to Get Dead Deals Out of "]
  N0 --> N1["How to Decide Between Them"]
  N1 --> N2["Concrete Numbers Behind Each Option"]
  N2 --> N3["Implementation Details and Sequencing"]
```


There are really only two structural approaches to removing dead deals, and most sales orgs pick one by accident instead of by design. Understanding both — and their failure modes — is what separates a manager who coaches pruning from one who just nags about it.

**Option A: Manager-Led Coaching Cadence.** This is a recurring, human-run review — typically weekly in the 1:1 — where the manager and rep walk the board together, apply a disqualification standard, and jointly decide what gets re-staged, re-engaged, or closed-lost. The manager owns the diagnostic questions ("what did the buyer *do* in the last 14 days?"), models the language for closing gracefully, and coaches the emotional resistance in real time. This is a coaching intervention, not an admin task — its entire value is in the conversation, not the data cleanup. It works because it addresses the *will* problem directly: reps hoard dead deals because closing them feels like failure, and only a human can reframe that in the moment.

![How do you coach reps to remove dead deals from the pipeline — figure 1](/assets/qa/cg0106-b1.jpg)



**Option B: System-Enforced Auto-Aging Rules.** This is a CRM-automated approach: a workflow rule flags or auto-moves any deal with no logged activity in a defined window (commonly 14, 21, or 30 days), pinging the rep, then escalating to the manager, then — in the most aggressive configurations — auto-closing the deal as "stale, no action" if the rep doesn't respond. Tools like Salesforce flow builder, HubSpot workflows, or a **RevOps**-built script in the data warehouse can enforce this without a human ever having the conversation. It works because it removes the rep's discretion entirely: there's no negotiation with a system rule the way there is with a manager's judgment call.

In practice, the strongest programs run **both**, sequenced deliberately. System rules (Option B) act as the tripwire — they surface which deals are stale so nobody has to manually sort a 200-row pipeline by eye. But the actual behavior change — the rep learning to self-prune before the system flags them — only happens through Option A's coaching layer. A pure system-only approach breeds resentment and workarounds (reps logging a fake "touched base" note every 13 days to dodge the flag). A pure coaching-only approach without automation doesn't scale past a handful of reps and depends entirely on the manager remembering to run the review every week.

![How do you coach reps to remove dead deals from the pipeline — figure 2](/assets/qa/cg0106-b2.jpg)



The trade-off comes down to trust versus scale. Manager-led coaching builds the underlying skill and changes how a rep thinks about their own forecast — but it's slow, inconsistent across managers, and vanishes the moment a manager gets busy. System-enforced rules scale instantly across every rep and territory and never forget to run — but on their own they train reps to game the metric instead of actually reassessing the deal. The right call depends on team size, CRM maturity, and how much you can trust reps to self-report honestly once the stakes (comp, forecast credibility) are attached to the number.

## How to Decide Between Them

```mermaid
flowchart LR
  C["How do you coach reps to remove dead d"]
  C --> H0["The Two Ways to Get Dead Deals Out of "]
  C --> H1["How to Decide Between Them"]
  C --> H2["Concrete Numbers Behind Each Option"]
  C --> H3["Implementation Details and Sequencing"]
```


The decision isn't binary — it's a sequencing question. Small teams (under 8 reps) with a hands-on manager should lean almost entirely on Option A first, because the manager can realistically review every rep's board weekly and the coaching relationship is strong enough to carry the behavior change. Larger teams (15+ reps, multiple managers) need Option B's automation as scaffolding, because inconsistent manager cadence becomes the single biggest failure point at scale — some managers run tight weekly reviews, others let three weeks slip, and the pipeline data quality diverges by team.

![How do you coach reps to remove dead deals from the pipeline — figure 3](/assets/qa/cg0106-b3.jpg)



The other deciding factor is how much emotional resistance you're seeing. If reps openly admit deals are dead but won't act ("I know it's probably gone, but..."), that's a *will* problem — pure coaching, no automation needed, because a system flag won't change how someone feels about their number. If reps genuinely can't distinguish a stalled deal from a dead one, that's a *skill* gap — automation actually helps here, because the system's objective 14/21-day rule gives them the missing framework. If a rep's pipeline goes nearly empty the moment you prune it, stop pruning and pivot to a *system/territory* diagnosis — that's a demand problem, not a discipline problem, and no amount of coaching or automation fixes an empty top of funnel.

## Concrete Numbers Behind Each Option

Manager-led coaching cadences that actually stick share a specific rhythm: a 15-30 minute segment inside the existing weekly 1:1, reviewing the **three to five oldest** open deals by stage age rather than the whole board (reviewing everything every week burns out both parties within a month). The disqualification window that shows up most consistently across RevOps playbooks is **14 days with no buyer action triggers a re-engagement email; 21 days with no reply triggers close-lost.** Teams that use a looser 30-day window tend to carry 20-30% more dead weight in pipeline because deals get three extra weeks to decay before anyone questions them.

![How do you coach reps to remove dead deals from the pipeline — figure 4](/assets/qa/cg0106-b4.jpg)



On the target state: a healthy pipeline should have **fewer than 20% of open deals older than 90 days** relative to your average sales cycle length. If average cycle is 45 days, any deal sitting past 90 days (2x cycle) with no recent activity is almost certainly dead weight, not a "long deal." **Slipped-deal rate** — the percentage of deals whose close date moved right in a given month — is the other number worth tracking; anything consistently above 30-40% of the active pipeline slipping monthly is a strong signal of hoarding rather than genuinely long cycles.

System-enforced rules carry their own numbers. Auto-flag thresholds in CRM workflows are typically set at **14 days (warning to rep), 21 days (escalation to manager), 30 days (forced re-stage or auto-close-lost if no response)**. Pipeline coverage ratio is the number this all rolls up into: a forecast built on a bloated, zombie-filled pipeline might show 4x coverage that's really closer to 2x once dead deals are stripped out — and RevOps leaders who've cleaned up a pipeline this way report the "real" coverage number is often 30-50% lower than the pre-cleanup figure. That's not bad news; it's the first accurate number leadership has seen in months, and it's what actually justifies headcount or territory changes instead of an inflated fiction.

![How do you coach reps to remove dead deals from the pipeline — figure 5](/assets/qa/cg0106-b5.jpg)



Incentive-side numbers matter too: tying a small **5-10% of quarterly variable comp** to a pipeline-quality score (deal-age distribution, contact freshness, close-lost velocity) is enough to shift behavior without turning pruning into a punishment. Go much above that and reps start gaming the metric instead of genuinely reassessing deals.

## Implementation Details and Sequencing

Roll this out as a 30/60/90-day build rather than flipping a switch, and put the system automation in place *before* asking reps to change behavior, so the coaching conversation has real data to point to instead of a manager's gut feeling.

![How do you coach reps to remove dead deals from the pipeline — figure 6](/assets/qa/cg0106-b6.jpg)



**Days 1-30 — Manager-led, system-assisted.** Turn on the CRM aging flags (14/21-day thresholds) so stale deals surface automatically, but keep the actual close-lost decision manual and manager-co-piloted. Every Monday review, walk the three oldest flagged deals together, model the breakup-email language, and code the close-lost reason live so the rep watches how it's done without shame attached.

**Days 31-60 — Rep-led, manager-audited.** The rep now prunes their own board before the 1:1 using the same system flags as the trigger, then presents what they cut and why. The manager's job shifts from doing the pruning to auditing for honesty — specifically watching for reps who slip close dates right instead of admitting a deal is dead, since that's the most common workaround once pruning has real stakes attached.

![How do you coach reps to remove dead deals from the pipeline — figure 7](/assets/qa/cg0106-b7.jpg)



**Days 61-90 — Self-sustaining, spot-checked.** Pruning becomes the rep's own standing habit, driven by the same automated flags, with the manager checking in monthly rather than weekly and only re-engaging directly if stage age or slip rate spikes again.

Sequencing this way — automation first, coaching layered on top, then fading the manager's hands-on involvement — avoids the two most common failure modes: a system-only rollout that trains reps to game the flags, and a coaching-only rollout that collapses the moment the manager gets pulled into something else for a few weeks. It also gives **RevOps** a clean, auditable trail: every close-lost has a coded reason, every flag has a resolution, and the pipeline number leadership sees each Monday is one they can actually act on.

![How do you coach reps to remove dead deals from the pipeline — figure 8](/assets/qa/cg0106-b8.jpg)



## Related questions

### How do you coach reps to commit deals they can actually close?
Use the same last-buyer-action standard in reverse: a deal only earns "commit" status if it has a verified next step and a champion who can say yes, not just optimism.

### What's the difference between a stalled deal and a dead one?
A stalled deal still has a live mutual action plan and a real champion; a dead deal has only the rep's hope and a stage age past your average cycle length.

### How do you set up CRM automation to flag aging deals?
Build a workflow rule keyed on days-since-last-activity (not days-since-created), with escalating triggers at 14, 21, and 30 days, routed first to the rep and then the manager.

### Should close-lost reasons be tied to compensation?
No — reward the act of coding a reason honestly, never penalize the closed-lost outcome itself, or reps will hide dead deals instead of surfacing them.

### How does pipeline pruning affect forecast accuracy?
Removing dead deals shrinks the raw pipeline number but tightens forecast-to-actual variance, because the deals left are the ones actually likely to close near their stated date.

## FAQ

**How do I know if a deal is truly dead versus just slow?**
Apply the last-buyer-action test, not the rep's optimism. No real action — a reply, a meeting, a shared document — in 14 days makes it stalled; in 21 days, dead. A genuinely slow deal still has a mutual action plan and a live champion.

**Won't removing dead deals hurt our pipeline coverage ratio?**
It corrects a false one. A coverage ratio inflated by dead deals is a number that feels safe but lies to leadership. Real 2x coverage beats fictional 4x, because accurate coverage drives honest territory and headcount decisions instead of getting the help cut off later.

**A rep is emotionally attached to a deal they admit is dead — what do I say?**
Name the sunk cost directly: the work already done doesn't come back whether the deal stays open or not. Ask if a brand-new rep inheriting it today, with zero history, would call it live. Then close it together as a shared, low-shame act.

**How often should the pipeline actually get pruned?**
Weekly, inside the existing 1:1, sorted by stage age and last action. Monthly reviews let zombies multiply and the forecast drift; daily reviews create churn without added benefit. Weekly is the sustainable middle.

**What if pruning leaves a rep with almost no pipeline?**
That's diagnostic, not a discipline failure. An empty pipeline after honest pruning points to a system or territory problem — thin lead flow or a starved outbound cadence — not a rep who needs more coaching on cutting deals.

**Can automation replace the coaching conversation entirely?**
No. Automated flags surface *which* deals are stale, but only a manager can reframe the emotional attachment that makes a rep resist closing one. Use automation as the tripwire and coaching as the behavior change.

## Sources

- [Gong Labs: What separates top closers from the rest](https://www.gong.io/resources/labs/)
- [HBR: Stop Losing Sales to Customer Indecision](https://hbr.org/2022/05/sell-more-by-overcoming-your-buyers-indecision)
- [RAIN Group: Sales Pipeline Management Best Practices](https://www.rainsalestraining.com/blog/sales-pipeline-management)
- [MEDDIC Academy: The MEDDIC Sales Qualification Methodology](https://meddic.academy/what-is-meddic/)
- [Sales Hacker: How to Clean Up Your Sales Pipeline](https://www.saleshacker.com/sales-pipeline-management/)
- [Sandler: Why Salespeople Hold On to Dead Deals](https://www.sandler.com/blog/)
- [Winning by Design: The SaaS Sales Method on Pipeline Health](https://winningbydesign.com/resources/)
- [Clari: What Is Pipeline Inspection and Why It Matters](https://www.clari.com/blog/)

## Related on PULSE

- [What question would you ask during a pipeline review to force a rep to prioritize deals based on probability, not hope?](/knowledge/cg0902)
- [How do you coach reps to commit deals they can actually close?](/knowledge/cg0104)
- [How do you coach a solutions consultant to qualify deals earlier?](/knowledge/cg0220)
- [How do you coach a mid-market rep stepping up from SMB deals?](/knowledge/cg0212)
- [How do you coach a rep to stop discounting to win deals?](/knowledge/cg0083)
- [How do you coach a rep to qualify out bad-fit deals early?](/knowledge/cg0055)

Was this helpful?

This page will be disappearing soon.

Download the whole page as a PDF to keep — just $1.

⌬ Apply this in PULSE

Pulse CheckScore reps on the metrics that matter

How do you coach reps to remove dead deals from the pipeline?

The Two Ways to Get Dead Deals Out of the Pipeline

How to Decide Between Them

Concrete Numbers Behind Each Option

Implementation Details and Sequencing

Related questions

How do you coach reps to commit deals they can actually close?

What's the difference between a stalled deal and a dead one?

How do you set up CRM automation to flag aging deals?

Should close-lost reasons be tied to compensation?

How does pipeline pruning affect forecast accuracy?

FAQ

Sources

Related on PULSE

Two scores — Gate vs IQ