agentleFS
coleschaffercoleschaffer/copywritingskills-rmbc/skills/post-purchase-sequence/SKILL.md

post-purchase-sequence

Skill32 starsChanged 8 months agoMITView on GitHub

Generate a 4-5 email post-purchase sequence that reduces buyer's remorse, increases product usage, generates reviews, and sets up the next purchase using RMBC principles.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 8 are distinctive, and 5 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.

  • 5

    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:

    No selling in emails 1-4. The cross-sell in email 5 must feel earned by the value delivered in 1-4.

    line 67
  3. Distinctive:

    Check that the sequence addresses:

    line 72
  4. Distinctive:

    If any stage is missing, revise.

    line 79
  5. Distinctive:

    Check-in email must feel genuine — not a scripted "How are you?" that leads to a pitch

    line 123
  6. Distinctive:

    No selling in emails 1-4 — pure value delivery, support, and relationship building

    line 126
  7. Distinctive:

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

    line 130
  8. Distinctive:

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

    line 131
  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 133
  10. Very specific:

    Run /email-retention-sequences for subscription products needing ongoing retention

    line 138
  11. Very specific:

    Run /upsell-sequence-writer for higher-ticket ascension after this sequence

    line 139
  12. Very specific:

    Run /email-promo for standalone promotions to existing customers

    line 140
  13. Very specific:

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

    line 141

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

post-purchase-sequence

Purpose

Generate a post-purchase email sequence (4-5 emails) that maximizes customer lifetime value by guiding buyers from order confirmation through product mastery to repeat purchase. The post-purchase window is the most underleveraged moment in email marketing — the buyer just trusted you with their money and attention is at peak. This sequence reduces refund rates, increases product usage (which drives results, which drives reviews), generates social proof, and primes the next sale. RMBC applies as value delivery architecture: Research identifies usage barriers, Mechanism explains how to get results, Brief structures the onboarding arc, Copy executes with support and warmth.

Inputs

InputRequiredDescription
product_nameYesName and core promise of the purchased product
target_audienceYesWho the buyer is — demographics, goals, experience level
usage_instructionsYesKey steps to use the product effectively — the "how to get results" guide
complementary_productsYes1-3 products that pair with the purchase for cross-sell in final email
sequence_lengthNoNumber of emails: 4 or 5 (default: 5)
review_platformNoWhere to leave reviews — Amazon, Trustpilot, website, Google (default: website)
delivery_timelineNoExpected shipping/delivery window (default: 3-5 business days)

Execution Protocol

Step 1 — Load Framework Context

Read rmbc-context/SKILL.md to load RMBC framework definitions. Post-purchase sequences flip RMBC from persuasion to fulfillment — the sale is made, now the framework ensures the product delivers on its promise. Mechanism explains HOW to get results. Proof is generated (reviews), not deployed.

Step 2 — Map the Post-Purchase Arc

EmailTimingRoleFocus
1 — ConfirmationDay 0Validate the purchase, set expectationsOrder details, delivery timeline, what to expect, immediate quick win
2 — Usage TipsDay 3-5Teach them how to get resultsTop 3 usage tips, common mistakes to avoid, "do this first" action
3 — Results Check-InDay 10-14Ask how it's going, provide supportCheck on their experience, offer help, deepen engagement
4 — Review RequestDay 21-30Ask for a review at peak satisfactionSpecific review prompt, make it easy (direct link), show gratitude
5 — Cross-SellDay 30-45Introduce complementary product"Based on your purchase, you might also like..." — value-first bridge

For 4-email sequences: combine emails 3+4 (check-in + review request in one email).

Step 3 — Calibrate Tone by Phase

PhaseEmailsToneWhat to Avoid
Onboarding1-2Supportive, excited, educationalSelling anything — they just bought
Engagement3Curious, caring, helpfulPushy follow-up — this is a check-in, not a sales call
Proof Generation4Grateful, specific, easyGeneric "leave a review" — give them a prompt
Ascension5Helpful, relevant, low-pressureHard sell — frame as "customers who bought X also loved Y"

Step 4 — Write Each Email

For each email, produce:

  • Subject line (under 50 characters, warm and non-promotional)
  • Preview text (40-90 characters, complements subject)
  • Body copy following the email's role from the arc
  • CTA appropriate to the email's purpose (value action, not purchase — until email 5)

Rules:

  • Email 1: Confirm the order, reduce anxiety, deliver one immediate value piece (tip, guide, video).
  • Email 2: Practical and actionable — numbered tips, common mistakes, "do this first" guidance.
  • Email 3: Genuine check-in — ask how it's going, offer support channels, provide advanced tips.
  • Email 4: Make the review request specific — "What result have you noticed?" not "Leave a review."
  • Email 5: Cross-sell as recommendation — "Customers who got results with X found that Y accelerated..." — not a cold pitch.
  • No selling in emails 1-4. The cross-sell in email 5 must feel earned by the value delivered in 1-4.
  • Tone throughout: peer-to-peer, supportive. Never "Dear Valued Customer."

Step 5 — Validate Post-Purchase Coverage

Check that the sequence addresses:

  1. Buyer's remorse prevention (email 1 — immediate value + confirmation)
  2. Product usage education (email 2 — they know HOW to succeed)
  3. Engagement deepening (email 3 — they feel supported, not abandoned)
  4. Social proof generation (email 4 — review captured at peak satisfaction)
  5. Revenue expansion (email 5 — cross-sell at natural timing)

If any stage is missing, revise.

Output Format

## Post-Purchase Sequence: [Product Name]

**Sequence Length:** [4-5] emails
**Send Schedule:** Day 0, 3, 14, 25, 35
**Audience:** [target audience summary]
**Review Platform:** [where to leave reviews]

---

### Email 1: Order Confirmation — Day 0

**Subject:** [subject line]
**Preview:** [preview text]

[Full email body — confirmation, expectations, immediate value]

[CTA — value action: read the guide, watch the video, do step 1]

---

### Email 2: [Role Label] — Day [X]

[...continue for each email...]

---

## Post-Purchase Strategy Notes

- **Buyer's remorse window:** Day 0-3 — Emails 1-2 address this
- **Peak satisfaction timing:** Day [X] — Review request timed here
- **Cross-sell bridge:** [how email 5 connects the original purchase to the recommendation]
- **Support escalation:** Email 3 offers [support channel] for customers with issues
- **Success metrics:** [refund rate reduction, review count, cross-sell conversion, repeat purchase rate]

Quality Criteria

  • Email 1 must confirm the order AND deliver immediate value — not just a receipt
  • Usage tips in email 2 must be specific and actionable — numbered steps, not vague advice
  • Check-in email must feel genuine — not a scripted "How are you?" that leads to a pitch
  • Review request must include a specific prompt — "What's the first result you noticed?" not "Leave a review"
  • Cross-sell must connect logically to the original purchase — not a random product push
  • No selling in emails 1-4 — pure value delivery, support, and relationship building
  • Tone must be warm and supportive throughout — these people trusted you with money
  • Review link must go directly to the review form — minimize friction
  • 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 /email-retention-sequences for subscription products needing ongoing retention
  • Run /upsell-sequence-writer for higher-ticket ascension after this sequence
  • Run /email-promo for standalone promotions to existing customers
  • Run /mechanism-ideation to explain how the product works (feeds email 2)
  • 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.