Individual skill

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.

skills/client-churn-save/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.

1. 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.
2. "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.