# Outbound Sequence Pause-or-Kill Decision Framework

> A structured decision framework that tells you exactly when to pause an outbound sequence and when to kill it permanently, using concrete, countable criteria instead of gut feel. Includes two decision trees, scoring thresholds, and a midpoint triage card to force an active call before wasted effort compounds.

Free framework for sales reps. Topic: [Prospecting & Outbound Strategy](https://www.peerlab.ai/library/topic/prospecting-outbound-strategy/). Published by PeerLab in the [Sales Enablement Resource Library](https://www.peerlab.ai/library/). Source: https://www.peerlab.ai/library/outbound-sequence-pause-or-kill-decision-framework/

## How to use it

Run the midpoint triage card at touch 4 of a 7-touch sequence (or the equivalent halfway point of yours). Score the account against the five pause signals and five kill signals, then follow the corresponding decision tree to its outcome. Review killed sequences once a quarter to confirm the disqualification logic is still sound.

## What's inside

- Five concrete pause signals with countable criteria (touches, days, trigger type)
- Five concrete kill signals covering ICP failure, hard nos, and gone-dark thresholds
- Pause decision tree with four named outcomes and next-action instructions
- Kill decision tree with three named outcomes and CRM disposal instructions
- Midpoint triage card (one page, fill-in format) for touch 4 of 7 or equivalent
- Named failure modes for each path so reps recognise when they are rationalising
- Thresholds table: days elapsed and touch counts that trigger each category
- "When NOT to use this framework" cautions for edge-case accounts
- Glossary of four terms used consistently across both trees

## What This Is For

You finish touch 4 of 7. Zero response. The question is not "should I keep going?" The question is "am I wasting touches on a dead account, or is this just bad timing?"

This framework forces a binary, defensible decision at that midpoint. Pause means you exit the sequence intentionally and re-enter later under defined conditions. Kill means you remove the prospect from active sequencing permanently and log why.

Neither is failure. Continuing without a decision is.

---

## Glossary

**Sequence:** any structured outbound cadence with a fixed number of planned touches.
**Pause:** a deliberate, temporary exit with a defined re-entry trigger.
**Kill:** permanent removal from active sequencing. The record stays in the CRM; the sequence does not restart without a qualifying event.
**Gone dark:** no response of any kind (open, click, reply, voicemail pickup) across all channels for a defined number of days.

---

## When to Run This Framework

Run it at the midpoint of every sequence. For a 7-touch sequence, that is after touch 4. For a 6-touch sequence, after touch 3. If you are inside a sequence that has no defined end point, run it at day 21 regardless of touch count.

You can also run it at any point if you receive new account-level intelligence that changes the picture.

---

## The Five Pause Signals

Score one point for each signal present. A score of 3 or more = pause the sequence now.

| # | Signal | Countable Criterion |
|---|--------|-------------------|
| P1 | Timing conflict confirmed | Prospect or gatekeeper has stated a specific future window: budget cycle, contract renewal, returning from leave, project end date |
| P2 | Partial positive engagement | At least one open or click registered but no reply, OR a voicemail was listened to and not returned, within the last 14 days |
| P3 | Known internal disruption | Verifiable event: leadership change, acquisition, redundancy programme, or reorg announced in the last 30 days |
| P4 | Trigger event pending | A product launch, funding round, regulatory deadline, or hiring spike is scheduled or signalled within 60 days |
| P5 | Low touch count with no negative signal | Fewer than 4 touches completed AND no hard no received AND no ICP disqualification found |

**Failure mode for pause:** Using P5 as an excuse to avoid a kill decision. If you score only P5 and nothing else, that is not a pause signal. That is an incomplete sequence. Keep going.

---

## The Five Kill Signals

Score one point for each signal present. A score of 1 or more = kill the sequence now. These are not weighted. Any single kill signal is sufficient.

| # | Signal | Countable Criterion |
|---|--------|-------------------|
| K1 | Hard no received | Any explicit instruction not to contact: "remove me", "not interested, do not follow up", "we have a supplier", "legal has flagged this" |
| K2 | ICP disqualification confirmed | Account-level research has established the prospect falls outside your ICP on a hard criterion: company size, geography, industry, tech stack dependency, or regulatory bar |
| K3 | Contact no longer at the company | LinkedIn, company website, or direct confirmation shows the prospect has left and no replacement contact exists |
| K4 | Gone dark past threshold | Zero engagement (no opens, no clicks, no pickups, no replies) across all channels for 28+ days AND 6+ touches completed |
| K5 | Duplicate or wrong account | The account is already in an active sequence owned by another rep, or the contact is a duplicate of a live opportunity in the pipeline |

**Failure mode for kill:** Refusing to log K4 because "they might just be busy." At 6 touches and 28 days of silence, you have done your job. The account is not interested right now. Kill it, log it, move on.

---

## Pause Decision Tree

```
Start: Pause score is 3 or more
        |
        v
Is there a specific re-entry date or trigger? (P1 or P4 present)
        |
       YES --> Set a CRM task for that date. Exit sequence. Label: PAUSED - DATED TRIGGER.
        |
        NO
        |
        v
Is there any positive engagement signal? (P2 present)
        |
       YES --> Send one final "value" touch NOW (not a follow-up, a new angle).
              Wait 10 days. If no reply, re-evaluate. If still silent, kill at K4 criteria.
              Label: PAUSED - ENGAGEMENT SIGNAL.
        |
        NO
        |
        v
Is there a verifiable internal disruption? (P3 present)
        |
       YES --> Set a CRM task for 45 days. No contact in that window. Label: PAUSED - DISRUPTION.
        |
        NO
        |
        v
Only P5 is present? Return to sequence. This is not a pause. Complete remaining touches.
```

---

## Kill Decision Tree

```
Start: Kill score is 1 or more
        |
        v
Is K1 present (hard no)?
        |
       YES --> Log "Do Not Contact" in CRM. Remove from all sequences immediately.
              Notify your manager if the contact was senior (Director level or above).
              Label: KILLED - HARD NO.
        |
        NO
        |
        v
Is K2 present (ICP disqualification)?
        |
       YES --> Log disqualification reason with specific evidence (source, date).
              Flag the account for data hygiene review.
              Label: KILLED - ICP FAIL.
        |
        NO
        |
        v
Is K3, K4, or K5 present?
        |
       YES --> Log reason with specific evidence. Remove from active sequence.
              K3: add a task to find the replacement contact in 30 days.
              K4: set a 90-day "re-evaluate" task. Market conditions may change.
              K5: transfer ownership or merge the record immediately.
              Label: KILLED - [K3 / K4 / K5].
```

---

## Midpoint Triage Card

Fill this in at the midpoint of every sequence. Keep it in the CRM note or your call prep sheet.

---

**Prospect:** [Name, Title, Company]
**Sequence name:** [Name or ID]
**Current touch:** [X] of [Y]
**Days since touch 1:** [Number]
**Date of triage:** [Date]

**Pause score (circle all that apply):**
P1 / P2 / P3 / P4 / P5
Total pause score: __ / 5

**Kill score (circle all that apply):**
K1 / K2 / K3 / K4 / K5
Total kill score: __ / 5

**Decision:**
- Kill score 1 or more: KILL. Complete the kill tree above. Stop here.
- Pause score 3 or more: PAUSE. Complete the pause tree above. Stop here.
- Neither threshold met: CONTINUE. Complete remaining touches before next triage.

**Evidence logged (mandatory for any KILL or PAUSE decision):**
[One sentence describing the specific signal and its source]

**Next action and date:**
[Task set in CRM: Yes / No]

---

## When NOT to Use This Framework

**Strategic accounts under active stakeholder mapping.** If a sales engineer, CSM, or senior leader is running a parallel track into the same account, do not unilaterally kill the sequence. Align first.

**Accounts in a live RFP or tender process.** Sequence logic does not apply when there is a formal procurement cycle running. Manage those contacts through your opportunity record, not a cadence.

**Reactivation sequences for churned customers.** The ICP and gone-dark criteria above are calibrated for cold outbound. Former customers have different thresholds and warrant a separate decision framework.

---

## Quick Reference: Thresholds at a Glance

| Decision | Minimum touches | Minimum days | Signal requirement |
|----------|----------------|-------------|-------------------|
| Pause | Any | Any | 3+ pause signals |
| Kill (K4 only) | 6+ | 28+ | Zero engagement across all channels |
| Kill (K1-K3, K5) | Any | Any | 1 signal sufficient |
| Continue | Fewer than midpoint | Any | Fewer than 3 pause signals, zero kill signals |
