playbook
Fix My Retention
Diagnosed root cause of the at-risk relationship + a 30-day save plan with specific touchpoints, decisions, and an explicit save/let-go recommendation
The client has gone quiet.
How it runs
- vault-preflight → verify client context completeness and flag blocking gaps before proceeding
- client-health-tracker → aggregate NPS/CSAT/feedback/deal-activity signals into a current health snapshot
- retention-check → run structured client check-in framework against the snapshot to surface root cause hypotheses
- issue-triage → classify each surfaced issue by severity and SLA — separate "fix-now" from "watch" from "let-go-trigger"
- Review root-cause diagnosis — confirm or correct the hypothesis based on owner's lived context
- consultative-selling → frame the save conversation using the appropriate methodology (Gap Selling for diagnosed issues; Challenger for re-framing relationship value; SPICED for situation-pain-impact-critical-decision)
- Decision — save or let go? Based on diagnosis, owner makes the explicit go/no-go call. Save means committing to the 30-day plan; let-go means transitioning the client gracefully
- Review proposed save-plan financial commitments (discounts, credits, scope changes) before pdf-report drafts the document — terms-review gate
- Approve plan and assign owners — convert each save-plan action to a TaskNote with a specific owner and date
What it needs
- Client name and `client-id`
- What changed (specific signals: late payment, missed meetings, NPS drop, escalation, executive turnover)
- Last positive milestone date
- Contract renewal date (or rolling)
- Stakes — revenue at risk, strategic importance, reference value
What you get
- Client Health Report — root-cause diagnosis with evidence
- 30-Day Save Plan — specific touchpoints, asks, and decisions
- Save/Let-Go Recommendation — explicit go/no-go with rationale
- Followup TaskNotes for each save-plan action
