agentleFS
coleschaffercoleschaffer/copywritingskills-rmbc/skills/email-retention-sequences/SKILL.md

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

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
  1. Very specific:

    Read rmbc-context/SKILL.md to load RMBC framework definitions.

    line 30
  2. Distinctive:

    Every email must give them a reason to USE the product — not just read the email.

    line 69
  3. Distinctive:

    Check that the sequence addresses:

    line 74
  4. Distinctive:

    If any stage is missing, revise.

    line 80
  5. Distinctive:

    No selling in emails 1-6 — pure value delivery and relationship building

    line 121
  6. Distinctive:

    Every email must include a specific action the customer can take with the product

    line 122
  7. Distinctive:

    Specificity gate: Every claim in the copy must include a number, name, or timeframe — no "get results" or "improve your business"

    line 129
  8. Distinctive:

    Mechanism quantification: When referencing the mechanism, include at least one specific data point (number, timeframe, study reference)

    line 130
  9. Distinctive:

    Proof diversity: Use at least 2 different proof types (testimonial, statistical, authority, case study) — do not rely on a single proof mode

    line 132
  10. Very specific:

    Run /upsell-sequence-writer AFTER retention sequence (ascend only after value is delivered)

    line 137
  11. Very specific:

    Run /email-promo for promotional emails to retained customers

    line 138
  12. Very specific:

    Run /mechanism-ideation to explain how the product works (feeds email 3)

    line 139

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

InputRequiredDescription
product_nameYesThe product the customer owns — name and core promise
target_audienceYesWho the customer is — demographics, goals, experience level
key_benefitsYesTop 3-5 benefits the product delivers when used correctly
subscription_modelYesOne of: one-time (prevent refunds, encourage repeat purchase) or subscription (prevent cancellation)
sequence_lengthNoNumber of emails: 5, 6, or 7 (default: 7)
churn_triggersNoKnown reasons customers leave — objections, confusion points, competitor pull
send_timingNoDays 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

EmailRoleEmotional NeedFocus
1 — Welcome/OnboardSet expectations, quick winExcited but unsureShow them step 1 — reduce overwhelm
2 — Quick WinDeliver the fastest visible resultNeeds early proof it worksOne specific action → one specific result
3 — Deeper ValueTeach an advanced use case or hidden featureCurious, engagedMechanism: HOW the product works behind the scenes
4 — Social ProofShow other customers' winsNeeds validationStories of people like them succeeding
5 — Objection PreemptAddress the #1 reason people quitDoubt creeping inName the objection, resolve it directly
6 — Milestone CheckCelebrate progress, survey for feedbackWants acknowledgment"You've been with us X days — here's what you've achieved"
7 — Renewal/AdvocacyReinforce commitment, invite community or referralLoyal, ready to advocateSubscription: 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:

  1. Early overwhelm (emails 1-2)
  2. "Is this working?" doubt (emails 3-4)
  3. Active cancellation consideration (email 5)
  4. 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-writer AFTER retention sequence (ascend only after value is delivered)
  • Run /email-promo for promotional emails to retained customers
  • Run /mechanism-ideation to 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.