client-win-back
Skill1 starsChanged 15 days agoMITView on GitHub
Use this skill when the pipeline is thin and the best available list is the clients who already left, or when something has changed at the firm that makes a past engagement worth revisiting. Produces a sorted list of who is worth reaching, what changed since they left, and a message per person that does not pretend the gap never happened. Also use for "reach out to past clients", "win back churned accounts", "who should I re-engage", "we've changed, tell the people who left".
In this repository67 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- morning-paper-outreachSkill
- client-activation-checkinSkill
- client-churn-autopsySkill
- late-payment-chaseSkill
- network-path-mappingSkill
- rate-increase-planSkill
- sales-call-debriefSkill
- weekly-funnel-reviewSkill
- buyer-readSkill
- punch-upSkill
- call-topic-miningSkill
- ceo-exec-assistantSkill
- og-image-from-templateSkill
- weekly-site-and-ad-reportSkill
- icp-reviewSkill
- weekly-content-ideas-from-callsSkill
- client-performance-reviewSkill
- cold-email-sequenceSkill
- email-content-reviewerSkill
- scoring-analysis-and-distributionSkill
- delivery-audit-discovery-callSkill
- directionSkill
- rundownSkill
- source-checkSkill
- work-reviewSkill
- demandbird-exact-time-linkedin-postSkill
- kondo-owed-reply-sweepSkill
- linkedin-export-contact-importSkill
- mail-messages-contact-touchesSkill
- riverside-short-social-scheduleSkill
- youtube-transcript-panel-pullSkill
- email-voice-setupSkill
- upsell-opportunity-briefSkill
- ad-creative-content-strategySkill
- klaviyo-account-auditSkill
- facilitator-notesSkill
- local-prospectingSkill
- weekly-linkedin-postsSkill
- linkedin-watchlist-briefSkill
- pipeline-by-scriptSkill
- pre-session-flash-cardSkill
- write-in-the-owners-voiceSkill
- reddit-gtm-sprintSkill
- process-captureSkill
- sales-call-market-analyzerSkill
- linkedin-shoutout-postSkill
- plain-language-copy-checkSkill
- revenue-goal-funnel-mathSkill
- case-study-buildSkill
- cash-runway-forecastSkill
- client-profitability-readSkill
- client-proposalSkill
- content-briefSkill
- quarter-goal-filterSkill
- win-to-anglesSkill
- activity-incentive-sprintSkill
- candidate-interview-coachSkill
- client-list-stack-pitchSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Check who is still there. Past clients move, and a champion who left for a new company is a new account with a warm path rather than a …
- Very specific: line 31
Write a message per person that names the gap, says what changed, and asks for nothing bigger than a reply.
- Distinctive: line 45
MUST have one nameable thing that changed before contacting anyone.
- Distinctive: line 46
MUST match the change to the reason they left.
- Distinctive: line 47
MUST check whether the contact is still at the company.
- Distinctive: line 48
MUST acknowledge the gap rather than writing as if no time passed.
- Distinctive: line 49
MUST keep the ask small enough that no is easy.
- Distinctive: line 50
MUST record the outcome against the departure reason.
- Distinctive: line 51
NEVER send the same message to people who left for different reasons.
- Distinctive: line 52
NEVER pitch into an unrepaired relationship.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Applies to clients who have stopped working with the firm, when something real has changed. Produces a sorted list and a message each, written to be easy to answer honestly.
The play
- Establish what changed before writing to anyone. A win-back with no new information is a check-in, and a check-in to someone who left is an awkward email. The thing that changed can be the offer, the price, a capability, a person, or a problem in their world, but it has to be nameable in one sentence. The test is in references/what-changed.md.
- List everyone who left, with why. Not the version in the record, the real one: they ran out of budget, the champion left, the work did not land, they took it in house, or the firm let them down. The categories and how to sort them are in references/sorting-the-list.md.
- Sort by whether the reason for leaving is addressed by what changed. A price change speaks to the ones who left on budget and says nothing to the ones who left unhappy with the work. Everything else is a mismatch, and a mismatched win-back reads as a mailshot.
- Check who is still there. Past clients move, and a champion who left for a new company is a new account with a warm path rather than a win-back. Treat that as the better opportunity it is.
- Branch by why they left:
- Budget or a downturn: the cleanest win-back. Lead with what changed about scope or price, name the old engagement plainly.
- Champion left, replacement never engaged: not a win-back, a fresh sale into a warm account. Do not lean on a relationship the new person does not have.
- Took it in house: ask how it is going, honestly, with no pitch. Half the time it is going badly and nobody wants to say so first.
- The work did not land: only reach out if something concrete changed, and acknowledge it directly. Anything else makes it worse.
- The firm let them down: repair before pitch, in a separate conversation, and accept it may not be recoverable.
- They were never a good fit: leave them. A win-back of a bad-fit client is a reheated bad engagement.
- Write a message per person that names the gap, says what changed, and asks for nothing bigger than a reply. The patterns are in references/the-message.md. Pretending the relationship never lapsed is the most common error and the most obvious one.
- Work the list in batches of five to ten, not all at once, so the wording can change based on what comes back.
- Record the outcome against the reason they left. Over two or three rounds, this shows which departure reasons are actually recoverable, which is the thing that makes the next win-back faster.
What good looks like
- First thing I check that most people skip: whether the person is still at that company. A warm message to someone who left eight months ago is wasted, and the move itself was the opportunity.
- The mediocre version: an email to every past client saying the firm has grown and would love to reconnect. No reason to reply, no acknowledgement of the gap, and it teaches the list to ignore the sender.
- I know a message is right when it would be easy for them to reply "no thanks" without feeling rude. That is the test of whether the ask is sized correctly.
- Second test: the message names the specific work the firm did for them, not the firm's general capabilities.
- Red flag: the same message going to people who left for different reasons. That is a campaign, and win-backs do not work as campaigns.
Rules
- MUST have one nameable thing that changed before contacting anyone.
- MUST match the change to the reason they left.
- MUST check whether the contact is still at the company.
- MUST acknowledge the gap rather than writing as if no time passed.
- MUST keep the ask small enough that no is easy.
- MUST record the outcome against the departure reason.
- NEVER send the same message to people who left for different reasons.
- NEVER pitch into an unrepaired relationship. Repair first, separately.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

