Save-Play Sequencer
30/60/90 save sequences anchored on what's actually breaking — not a generic playbook.
Sample output for this workflow will appear here once it is captured.
Run the workflow in Claude, ChatGPT, or Phoenix Playground using the buttons below to see real output.
Overview
Given a customer that just turned Yellow or Red, this workflow proposes a 30/60/90-day save sequence: week-1 executive escalation, week-4 technical recovery plan, week-8 commercial re-anchor. Each step is tied to a specific signal the churn workflow surfaced — so the save plan is anchored on what's actually breaking, not a generic playbook.
Use cases
Save sequences your team can actually run
Your CSMs get a Red on an account and ask 'what do I do?'. This workflow gives them week 1 / week 4 / week 8 specifically: exec call about the disengagement, technical recovery plan tied to the specific competitor add, multi-year renewal with modified terms tied to whitepaper co-authorship. Paste into Salesforce as the next-90-days plan.
Signal-anchored, not generic
A competitor-landed Red gets a technical-recovery play. A champion-churned Red gets a multi-thread play. A financial-stress Red gets a commercial re-anchor. Same workflow, different sequence — driven by which signals actually fired.
View workflow prompt
# Save-Play Sequencer
## Parameters
- `{{domain}}` *(required)* — Customer company domain. Example: `acme.com`
- `{{your_product}}` *(required)* — Your product or category. Example: `HG Insights`
- `{{verdict}}` *(required)* — Churn-risk verdict — Yellow or Red. Example: `Red`
## Purpose
{{domain}} just came back {{verdict}} on a churn-prediction screen for {{your_product}}. Propose a 30/60/90-day save sequence anchored on the specific signals driving the verdict. Each step ties to a named signal — not a generic playbook.
## Process
1. **Re-confirm the driving signals** — call `company_install_time_series` filtered to {{your_product}} (adoption shape), `company_technographic` filtered to {{your_product}}'s category (recent competitor adds), `company_intent` (category trend), and `contact_search` (named-sponsor presence) to identify the top-3 signals that justify the {{verdict}}. Web-search {{domain}} for any major event in the last 90 days that adds context.
2. **Map signals → save play** — for each top signal, pick from these patterns:
- **Adoption decline** → executive escalation in week 1 (open the disengagement honestly with the exec sponsor).
- **Competitor landed** → technical recovery plan in week 4 (head-to-head against the specific competitor, in the customer's geo).
- **Intent decay** → workshop / training cycle in week 4-8 (intent decays when the team forgets you exist).
- **Champion churned** → multi-thread + new-sponsor pitch in week 1-2 (don't wait for the new exec to find you).
- **Financial stress** → commercial re-anchor in week 8 (longer term, modified terms, value-share rather than discount).
3. **Sequence** — week 1 (exec sponsor), week 4 (technical recovery), week 8 (commercial re-anchor). Adjust based on which signals are loudest — a competitor-landed Red leads with technical recovery; a champion-churned Red leads with multi-thread.
## Output Format
- `# 🚑 {{domain}} — {{verdict}} Save Sequence`
- `## Driving signals` — top 3, cite each
- `## Day 1-14 — Executive engagement` — specific action, exec sponsor named (if known), specific message
- `## Day 15-60 — Technical recovery` — specific action tied to the technical signal
- `## Day 61-90 — Commercial re-anchor` — specific term modification or value-share proposal
## Quality Checklist
- Each step cites the signal that drove it
- Exec sponsor named only if `contact_search` returned them (no fabrications)
- Competitor named only if `company_technographic` returned them (no fabrications)
- Sequence is specific, not "have a call about it"
- Cap tool calls at ~10