client-churn-save
Detect at-risk agency retainer clients early and run the save - a ranked early-warning signal list, the diagnose-before-prescribing save-call procedure with a word-for-word script skeleton, the re-scope-down-not-lose rule, and the 90-day post-loss win-back window. Use when an agency owner says "I think we're about to lose this client", "the client went quiet on us", "they said they're doing a budget review", "our main contact just left", or "we got a cancellation notice". Do NOT use for designing the routine communication rhythm that prevents churn in the first place - use client-comms-cadence instead.
- License 许可
- MIT
- 最近更新
- 2026-10-14
- Stars
- ★ 25
- Forks
- 3
01 前言 Front Matter
- name
- client-churn-save
- description
- Detect at-risk agency retainer clients early and run the save - a ranked early-warning signal list, the diagnose-before-prescribing save-call procedure with a word-for-word script skeleton, the re-scope-down-not-lose rule, and the 90-day post-loss win-back window. Use when an agency owner says "I think we're about to lose this client", "the client went quiet on us", "they said they're doing a budget review", "our main contact just left", or "we got a cancellation notice". Do NOT use for designing the routine communication rhythm that prevents churn in the first place - use client-comms-cadence instead.
03 SKILL.md 正文
Client Churn Save
By the time a client says "we've decided to go another direction," the decision is weeks old and the save rate is near zero. The costly mistake this skill prevents is late detection followed by panic discounting: noticing churn only at the cancellation email, then throwing a price cut at a problem that was never about price. Churn saves are won in the detection window - the four to eight weeks between the first quiet signal and the internal decision - and won by diagnosis, not concessions.
Work the example agency throughout: Northbeam Digital, an 8-person marketing agency with 11 retainer clients averaging $6,500/month and a 62 percent gross margin target. Losing one average client costs $78,000 a year of revenue; at Northbeam's economics, replacing it takes a paid audit, a close, and onboarding - months of pipeline. A save is almost always cheaper than a replacement.
Operating procedure
Step 1: Watch the ranked early-warning signals
These are the escalation triggers from client-comms-cadence, ranked here by severity. The account manager escalates to the owner the same day any of them fires; two simultaneous signals mean the save call happens this week.
- Champion departure - the day-to-day contact leaves or changes roles. Highest risk: the retainer's institutional memory and internal advocate leave together. Treat as an active save even if nothing else looks wrong.
- "Budget review" language - "budget review," "procurement is looking at vendors," "re-evaluating for next year," or a competitor's name in any message. The internal conversation has already started.
- Skipped meetings - the client cancels or no-shows two consecutive standing calls. Disengagement precedes cancellation; nobody churns while actively attending.
- Declining response rates - two consecutive weekly pulses or two monthly reports (agency-monthly-report) with no reply from a client who used to engage.
- Softer tells - shrinking meeting attendance from their side, requests routed to junior staff, out-of-scope asks stopping entirely (they have stopped investing in the relationship).
Step 2: Prepare before the save call
Never walk in blind. Pull the client's margin from retainer-economics-calculator (it sets the concession floor), the last three monthly reports (is this performance-driven or relationship-driven?), the signal timeline, and any known client-side changes. Label speculation as speculation. Decide in advance the walk-away line: the minimum scope-price combination that still clears the 30 percent margin line - saving a client into a below-floor retainer just converts fast churn into slow churn.
Step 3: Run the save call - diagnose before prescribing
The call is a diagnosis, not a pitch. Offering fixes before understanding the real driver signals panic and usually fixes the wrong thing. Get the truth first; 24 hours buys a better prescription than an on-the-spot concession.
Word-for-word skeleton:
OPEN - name it honestly:
"[FILL: name], I asked for this call because I want to check in on the
partnership itself, not the work. I've noticed [FILL: specific observable
signal - e.g. 'we've missed our last two calls and the March report didn't
get a response'], and in my experience that usually means something's
changed on your side. I'd rather hear it straight than guess."
DIAGNOSE - then stop talking:
"What's changed for you since [FILL: last quarter / the last QBR]?"
...listen...
"If you were deciding today whether to renew, what would the hesitation be?"
...listen...
"Is this about the results, the budget, or something about how we work
together?"
...listen. Do not defend. Take notes.
REFLECT - prove you heard it:
"So if I have this right: [FILL: their issue in their words]. Did I get
that right, and is there anything else?"
PRESCRIBE - only now, and only matched to the diagnosis:
If results: "Here's what I'd change in the next 30 days: [FILL: one
concrete delivery change with a measurable checkpoint]."
If budget: "Rather than lose the momentum entirely - what if we
scoped down to [FILL: reduced scope] at $[FILL]/month,
protecting [FILL: the highest-value work], and revisit
in a quarter?"
If relationship: "That's on us. Here's the change: [FILL: staffing or
cadence change], starting this week."
If undiagnosed: "Let me take this back and come to you with a plan by
[FILL: date within 48 hours]."
CLOSE - one commitment, one date:
"Can we agree to [FILL: specific next step] by [FILL: date], and then
decide from there?"
Step 4: Apply the re-scope-down-not-lose rule
When the driver is budget, a smaller retainer beats a churn - every time the reduced scope still clears the 30 percent margin line from retainer-economics-calculator. A client scoped down from $6,500 to $4,000/month keeps $48,000/year of revenue, keeps the relationship warm for re-expansion at a future QBR (agency-qbr-upsell), and keeps the case study alive. Scope down by cutting deliverables, not by discounting the same deliverables - a discount resets the price anchor permanently; a re-scope preserves it. Paper the change with statement-of-work-writer.
Step 5: If lost anyway, run the 90-day win-back window
Exit gracefully: clean 30-60 day handover, assets delivered, no guilt. Then:
- Day 30: one no-ask check-in ("how's the transition going?").
- Day 60-90: the win-back note - one specific, new observation about their business plus a bounded offer (a project, not the old retainer).
- Why 90 days: that is roughly one quarter - long enough for a replacement vendor or in-house team to show its gaps, short enough that the client still knows the numbers the agency delivered. Past 90 days, win-back reverts to cold outreach odds.
Inputs to collect
- The fired signals and their dates (from the client-comms-cadence escalation log).
- Client margin and the concession floor (from retainer-economics-calculator).
- Last three monthly reports and last QBR notes.
- Champion status and any org changes on the client side; label secondhand information as unconfirmed.
Deliverable
A save plan per at-risk client: the signal timeline, the diagnosed driver in the client's own words, the matched prescription with a measurable 30-day checkpoint, the pre-computed re-scope floor, and - if lost - the dated 90-day win-back sequence with owner.
Do NOT
- Do not open with a discount; if the problem was results or relationship, the discount buys one quarter and then the churn happens anyway, at worse margin.
- Do not prescribe on the call before the diagnosis is confirmed back to the client in their words.
- Do not save a client into a below-30-percent-margin retainer - that is the fire-or-fix line from retainer-economics-calculator, and it applies to saves too.
- Do not treat champion departure as neutral news; it is the highest-ranked signal even when the relationship "feels fine."
- Do not burn the exit - a graceful handover is the entry ticket to the 90-day win-back and the referral that often follows a good goodbye.
- Do not let the save call be the first honest conversation; if it is, the real failure was the cadence - fix that with client-comms-cadence for the rest of the book.
Quality bar
- Every at-risk flag cites a specific, dated, observable signal - not "the vibe is off."
- The save call transcript shows diagnosis questions asked and answered before any offer was made.
- Any re-scope clears the 30 percent margin line, computed before the call.
- Lost clients have a calendared day-30 and day-60-90 touch with a named owner.
Escalation and neighbors
Detection lives in client-comms-cadence - this skill fires when its escalation triggers do. Margin floors come from retainer-economics-calculator; re-expansion of a saved-but-reduced client runs through agency-qbr-upsell at a later quarter; re-scope paperwork goes to statement-of-work-writer. If churn language includes legal or payment-dispute threats, this is a contract matter - bring in a lawyer, not a save call.
04 同仓库更多 Skills
有氧运动计划
zone-2-cardio-plan
当有人要求制定稳态有氧训练计划、进行有氧基础训练或达到第二区间、安排轻松或耐力型的每周有氧训练、按心率区间训练,或提高静息心率、最大摄氧量或耐力时,可以使用此方案。该方案构建了一个包含训练计划结构、训练方式选择和进度安排的心率区间有氧训练模块。本方案仅提供一般健身指导,不构成医疗建议。请勿用于设计力量或举重训练计划(请使用力量训练计划)、高强度间歇训练 (HIIT) 或循环训练(请使用体能训练和 HIIT 计划),或灵活性/柔韧性训练(请使用灵活性训练计划)。
youtube-script-writer
Writes retention-engineered long-form YouTube scripts on a hook/body/payoff architecture - a first-30-seconds hook that survives the retention cliff, a beat-sheet body with mini-hooks and bridges, timed pattern interrupts, and a payoff that over-delivers - with B-roll and editing cues marked inline. Use when someone says "script my next video", "my retention graph dies at the start", "tighten this draft", or "outline a video on X". Do NOT use for the 3-second opener of TikTok, Reels, or Shorts - use video-hook-writer instead; do NOT use for spoken voiceover synced to on-screen tutorial actions - use narration-script instead; do NOT use for a sales demo built on a buyer's discovery notes - use demo-script instead; do NOT use to design the thumbnail and title - use thumbnail-concept instead.
win-back-campaign
Designs segmented win-back email sequences for dormant users - dormancy tiers, a three-beat sequence with a single proportional incentive, and a suppression rule - and measures success by re-activation, not opens. Use when someone says "our users went quiet", "design a win-back campaign", "how do I re-engage lapsed customers", "should we email people who haven't logged in for months", or lifecycle messaging has stopped landing with a lapsed segment. Do NOT use for recovering an unfinished checkout - use abandoned-cart-sequence instead. Do NOT use for diagnosing and fixing why active customers cancel - use churn-reduction instead. Do NOT use for building always-on onboarding or nurture flows - use email-drip-builder instead.
wikipedia-style
Writes neutral, verifiable, encyclopedic prose following Wikipedia's core content policies and manual of style - NPOV, inline citations, notability-backed claims, and a strict ban on promotional language. Use when someone asks "write this like a Wikipedia article", "draft a Wikipedia page for this company or person", "make this neutral and encyclopedic", or "why does my article draft keep getting rejected". Do NOT use for persuasive or opinion writing - use op-ed-writer instead; for thesis-driven academic papers, use academic-essay; for verifying claims in existing text, use fact-checker.
whitepapers
Structures and writes authoritative B2B whitepapers - a standalone executive summary, a data-sized problem statement, methodology, evidence-driven findings, recommendations, and a soft call to action - flagging every claim that needs a real citation. Use when a marketer asks "write a whitepaper on this topic", "turn our research into a lead-gen asset", "make this credible enough for executives", or a draft reads like a product pitch instead of analysis. Do NOT use for customer-story-driven proof - use case-study-builder instead; for policy audiences, use policy-brief.
white-space-analysis
Finds unmet market gaps by ranking jobs-to-be-done on importance versus satisfaction, overlaying them against current solutions and workarounds, and validating that each gap is real, winnable, and worth winning. Use when someone asks "where are the gaps in this market", "what's underserved here", "where should we play next", or is hunting for product, feature, or market-entry opportunities. Do NOT use for profiling competitors and building battle cards - use competitive-intelligence instead; for putting a dollar figure on an identified opportunity - use market-sizing instead; for extracting jobs-to-be-done from raw customer interviews - use jtbd-extractor instead.