When should a CSM initiate a save play for at-risk accounts?

Question

Pulse RevOps · The Machine · Accepted Answer

## Save Play Timing Strategy

Initiate save plays **90–120 days before renewal date**, not after a churn warning. Pavilion's retention database shows **82% of save plays started in final 60 days fail**; customers who received intervention *after* their stated intent to churn rarely reverse course.

### Timeline Triggers
| Timing | Trigger | Engagement Level |
|--------|---------|------------------|
| **Day 0–30** | Yellow score emerges | CSM monthly QBR + product roadmap check-in |
| **Day 31–60** | Red score confirmed | Executive sponsor intro + technical audit |
| **Day 61–90** | Churn intent stated | Pricing flexibility + multi-stakeholder summit |
| **Day 91+** | Customer non-renewing | Win-back playbook (lower probability) |

### Proactive vs. Reactive Timing
**Proactive** (≥90 days pre-renewal): CSM initiates based on health score or usage data. Success rate **67%** (per OpenView).

**Reactive** (customer says "not renewing"): Success rate **18%**. Once stated, switching is mentally committed.

Empirical data from **SaaStr annual**: Median save play takes **45 days to show traction** (product demo → trial of new feature → internal champion buy-in). Starting at day-60 means resolution arrives *after* renewal decision. Start at day-90 to build case before renewal meeting.

### Save Play Components
1. **Executive alignment call** (week 1): CEO/CRO speaks to sponsor's business goals
2. **Technical audit** (week 2–3): Identify 3–5 optimization wins customer hasn't discovered
3. **Competitive repositioning** (week 3–4): Show differentiation customer may have missed
4. **Pricing discussion** (week 4–5): Only after demonstrating value, not as first move
5. **Stakeholder summit** (week 5–6): Multi-threaded agreement before renewal date

```mermaid
gantt
    title Save Play Timeline (6-Month Contract)
    dateFormat YYYY-MM-DD
    axisFormat %b
    
    Contract Start: 2024-01-01, 180d
    Health Monitoring: 2024-01-01, 150d
    Yellow Alert Window: 2024-05-31, 30d
    Red Alert Triggered: 2024-06-29, 30d
    Active Save Play: 2024-07-29, 42d
    Final Negotiation: 2024-09-09, 21d
    Renewal Deadline: crit, 2024-09-30, 1d
```

TAGS: save-play-timing,customer-retention,renewal-strategy,churn-prevention,saas-sales,playbook-execution

Timing	Trigger	Engagement Level
Day 0–30	Yellow score emerges	CSM monthly QBR + product roadmap check-in
Day 31–60	Red score confirmed	Executive sponsor intro + technical audit
Day 61–90	Churn intent stated	Pricing flexibility + multi-stakeholder summit
Day 91+	Customer non-renewing	Win-back playbook (lower probability)

When should a CSM initiate a save play for at-risk accounts?

Save Play Timing Strategy

Timeline Triggers

Proactive vs. Reactive Timing

Save Play Components

What does the score mean?