email-retention-sequences
Skill32 starsChanged 8 months agoMITView on GitHub
Generate retention/nurture email sequences (5-7 emails) to reduce churn, reinforce purchase decisions, and increase customer lifetime value using RMBC principles.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Zenobia0000/dtc-copywriting-skillsedited, first seen Mar 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- Zenobia0000/dtc-copywriting-skills★ 450% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository41 other files it gives its agents.
- ab-test-planSkill
- ad-angle-generatorSkill
- ad-creative-auditSkill
- advertorial-writerSkill
- bonus-stackSkill
- broadcast-emailSkill
- cart-abandonment-flowSkill
- checkout-abandonmentSkill
- competitor-offer-analysisSkill
- copy-rewriteSkill
- creative-briefSkill
- email-promoSkill
- fb-ad-copySkill
- free-offer-briefSkill
- funnel-architectureSkill
- funnel-auditSkill
- guarantee-writerSkill
- hook-batterySkill
- ingredient-researchSkill
- lander-copySkill
- lead-writerSkill
- mechanism-ideationSkill
- media-buying-briefSkill
- offer-stackSkill
- order-form-croSkill
- pdp-ecomm-templateSkill
- post-purchase-sequenceSkill
- pricing-strategySkill
- reengagement-sequenceSkill
- rmbc-contextSkill
- rmbc-copy-auditSkill
- scarcity-urgencySkill
- soap-opera-sequenceSkill
- thank-you-pageSkill
- ugc-briefSkill
- unified-research-synthesizerSkill
- upsell-scriptSkill
- upsell-sequence-writerSkill
- vsl-scriptSkill
- webinar-registration-copySkill
- welcome-sequenceSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 8 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 30
Read rmbc-context/SKILL.md to load RMBC framework definitions.
- Distinctive: line 69
Every email must give them a reason to USE the product — not just read the email.
- Distinctive: line 74
Check that the sequence addresses:
- Distinctive: line 80
If any stage is missing, revise.
- Distinctive: line 121
No selling in emails 1-6 — pure value delivery and relationship building
- Distinctive: line 122
Every email must include a specific action the customer can take with the product
- Distinctive: line 129
Specificity gate: Every claim in the copy must include a number, name, or timeframe — no "get results" or "improve your business"
- Distinctive: line 130
Mechanism quantification: When referencing the mechanism, include at least one specific data point (number, timeframe, study reference)
- Distinctive: line 132
Proof diversity: Use at least 2 different proof types (testimonial, statistical, authority, case study) — do not rely on a single proof mode
- Very specific: line 137
Run /upsell-sequence-writer AFTER retention sequence (ascend only after value is delivered)
- Very specific: line 138
Run /email-promo for promotional emails to retained customers
- Very specific: line 139
Run /mechanism-ideation to explain how the product works (feeds email 3)
≈ “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
email-retention-sequences
Purpose
Generate a retention email sequence (5-7 emails) for existing customers that reduces churn and increases lifetime value. Unlike upsell sequences, retention emails are NOT about selling the next thing — they're about making the current purchase successful. The sequence reinforces the buying decision, delivers usage value, builds relationship, surfaces wins, and prevents cancellation before it starts. RMBC principles apply differently here: Research drives personalization, Mechanism explains how to get results, Brief structures the nurture arc, Copy executes with warmth over urgency.
Inputs
| Input | Required | Description |
product_name | Yes | The product the customer owns — name and core promise |
target_audience | Yes | Who the customer is — demographics, goals, experience level |
key_benefits | Yes | Top 3-5 benefits the product delivers when used correctly |
subscription_model | Yes | One of: one-time (prevent refunds, encourage repeat purchase) or subscription (prevent cancellation) |
sequence_length | No | Number of emails: 5, 6, or 7 (default: 7) |
churn_triggers | No | Known reasons customers leave — objections, confusion points, competitor pull |
send_timing | No | Days between emails (default: Day 1, 3, 7, 14, 21, 30, 45) |
Execution Protocol
Step 1 — Load Framework Context
Read rmbc-context/SKILL.md to load RMBC framework definitions. Retention sequences invert the typical RMBC sales arc — instead of moving toward a purchase, they reinforce an existing one. Mechanism explains HOW to get results, not WHY to buy.
Step 2 — Map the Retention Arc
| Role | Emotional Need | Focus | |
| 1 — Welcome/Onboard | Set expectations, quick win | Excited but unsure | Show them step 1 — reduce overwhelm |
| 2 — Quick Win | Deliver the fastest visible result | Needs early proof it works | One specific action → one specific result |
| 3 — Deeper Value | Teach an advanced use case or hidden feature | Curious, engaged | Mechanism: HOW the product works behind the scenes |
| 4 — Social Proof | Show other customers' wins | Needs validation | Stories of people like them succeeding |
| 5 — Objection Preempt | Address the #1 reason people quit | Doubt creeping in | Name the objection, resolve it directly |
| 6 — Milestone Check | Celebrate progress, survey for feedback | Wants acknowledgment | "You've been with us X days — here's what you've achieved" |
| 7 — Renewal/Advocacy | Reinforce commitment, invite community or referral | Loyal, ready to advocate | Subscription: renewal framing. One-time: referral or repeat |
For 5-email sequences: combine 2+3 and 5+6. For 6-email sequences: combine 5+6.
Step 3 — Adapt for Subscription vs One-Time
Subscription model adjustments:
- Email 5 must address cancellation directly: "Thinking about canceling? Here's what you'd lose"
- Email 7 frames renewal: "Your next billing cycle starts [date] — here's what's coming"
- Urgency = loss aversion (what they lose), not scarcity
One-time model adjustments:
- Email 5 addresses buyer's remorse: "Was this the right choice? Let's look at the evidence"
- Email 7 frames repeat purchase or referral: "Know someone who needs this?"
- Urgency = results timeline (they need to USE the product to get value)
Step 4 — Write Each Email
For each email, produce:
- Subject line (under 50 characters, warm tone — not salesy)
- Preview text (40-90 characters)
- Body copy following the email's role from the arc
- CTA — always a value action (use the product, read a guide, reply with feedback), never a purchase CTA until email 7
Rules:
- Tone: helpful, warm, peer-to-peer. Not salesy. These people already bought.
- Short paragraphs: 1-3 sentences. Retention emails compete with inbox fatigue.
- Every email must give them a reason to USE the product — not just read the email.
- Personalization cues: reference their purchase, their timeline, their likely stage.
Step 5 — Validate Anti-Churn Coverage
Check that the sequence addresses:
- Early overwhelm (emails 1-2)
- "Is this working?" doubt (emails 3-4)
- Active cancellation consideration (email 5)
- Relationship deepening (emails 6-7)
If any stage is missing, revise.
Output Format
## Retention Sequence: [Product Name]
**Model:** [one-time | subscription]
**Sequence Length:** [5-7] emails
**Send Schedule:** [Day 1, 3, 7, ...]
**Audience:** [target audience summary]
---
### Email 1: [Role Label] — Day [X]
**Subject:** [subject line]
**Preview:** [preview text]
[Full email body]
[Value CTA — action to take with the product]
---
### Email 2: [Role Label] — Day [X]
[...continue for each email...]
---
## Retention Strategy Notes
- **Churn window:** Highest risk at Day [X] — Email [Y] addresses this
- **Key objection handled:** Email [5] — [the specific objection]
- **Subscription/one-time adaptation:** [how email 7 differs by model]
- **Success metric:** [what to measure — open rate, product usage, reply rate, churn rate]Quality Criteria
- No selling in emails 1-6 — pure value delivery and relationship building
- Every email must include a specific action the customer can take with the product
- Subject lines must feel personal and warm — not promotional
- Email 5 must name the actual objection/cancellation reason — not a vague "still happy?"
- Social proof in email 4 must feature customers similar to the target audience
- Sequence must adapt clearly between subscription and one-time models
- Tone must be peer-to-peer throughout — never "Dear Valued Customer"
- Specificity gate: Every claim in the copy must include a number, name, or timeframe — no "get results" or "improve your business"
- Mechanism quantification: When referencing the mechanism, include at least one specific data point (number, timeframe, study reference)
- Audience journey: The copy must reference where the reader IS (what they've tried, what's failing) — not just who they are demographically
- Proof diversity: Use at least 2 different proof types (testimonial, statistical, authority, case study) — do not rely on a single proof mode
- Objection handling: The copy must address at least 2 likely objections with concrete responses (ROI math, proof of similar result, risk reversal)
Related Skills
- Run
/upsell-sequence-writerAFTER retention sequence (ascend only after value is delivered) - Run
/email-promofor promotional emails to retained customers - Run
/mechanism-ideationto explain how the product works (feeds email 3) - Validate with
/rmbc-copy-audit
Attribution
Generated using RMBC framework by Stefan Georgi. Learn more: copyaccelerator.com/join
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.

