Stats
Actions
Tags
From rmbc-skills
Generate post-purchase email upsell sequences (3-5 emails) that ascend customers from initial purchase to higher-ticket offers using RMBC-structured persuasion.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rmbc-skills:upsell-sequence-writersonnetThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate a post-purchase email sequence (3-5 emails) that ascends customers from their initial purchase to a higher-ticket complementary offer. These emails deploy after the buyer has already said yes — trust is established, the product is in hand (or arriving), and the window for ascension is open. Each email must deliver genuine value before bridging to the upsell. The sequence arc moves from...
Generate a post-purchase email sequence (3-5 emails) that ascends customers from their initial purchase to a higher-ticket complementary offer. These emails deploy after the buyer has already said yes — trust is established, the product is in hand (or arriving), and the window for ascension is open. Each email must deliver genuine value before bridging to the upsell. The sequence arc moves from gratitude through value delivery to the offer, with urgency closing the window. Every email uses RMBC principles compressed into short-form format.
| Input | Required | Description |
|---|---|---|
initial_product | Yes | What the customer already purchased — name, price, core promise |
upsell_product | Yes | The higher-ticket offer — name, price, what it does, how it complements the initial purchase |
upsell_price | Yes | Price of the upsell with any discount framing |
target_audience | Yes | Who the buyer is — demographics, pain points, desires, sophistication level |
sequence_length | No | Number of emails: 3, 4, or 5 (default: 5) |
key_mechanism | No | The upsell product's unique mechanism (output from /mechanism-ideation) |
send_timing | No | Days between emails (default: Day 1, 3, 5, 7, 9) |
Read rmbc-context/SKILL.md to load RMBC framework definitions. Upsell sequences deploy RMBC across multiple touchpoints — Research informs the value content, Mechanism justifies the upsell, Brief structures the sequence arc, Copy executes each email.
Map the emotional journey across the sequence:
| Role | Emotional State | RMBC Focus | |
|---|---|---|---|
| 1 — Thank You | Validate purchase, deliver quick win | Excited, hopeful | Research (reinforce their decision) |
| 2 — Value Delivery | Teach something useful related to their purchase | Engaged, learning | Research → Mechanism tease |
| 3 — Bridge | Connect initial product's limitation to upsell need | Curious, aware of gap | Mechanism reveal |
| 4 — Offer | Present the upsell with full value stack | Desire, trust | Brief → Copy (full pitch) |
| 5 — Urgency Close | Final window, scarcity, guarantee restatement | Fear of missing out | Copy (close) |
For 3-email sequences: combine emails 1+2, 3+4, and keep 5. For 4-email sequences: combine emails 1+2 and keep 3, 4, 5.
For each email, produce:
Rules per email position:
Read all emails in order. Check:
## Upsell Sequence: [Initial Product] → [Upsell Product]
**Sequence Length:** [3-5] emails
**Send Schedule:** [Day 1, Day 3, Day 5, ...]
**Audience:** [target audience summary]
---
### Email 1: [Role Label] — Day [X]
**Subject:** [subject line]
**Preview:** [preview text]
[Full email body]
[CTA or sign-off appropriate to position]
---
### Email 2: [Role Label] — Day [X]
[...continue for each email...]
---
## Sequence Strategy Notes
- **Value-to-pitch ratio:** [X value emails : Y pitch emails]
- **Mechanism reveal timing:** Email [X] — [why this timing]
- **Urgency type:** [deadline | limited quantity | price increase | bonus expiration]
- **Standalone test:** Email [4] works as a standalone pitch: [yes/no + why]
First 1-2 emails must deliver genuine value — no selling, no "by the way" pitches
Each email must have a clear single purpose aligned to its arc position
Subject lines must be under 50 characters and work on mobile
The bridge email (3) must make the upsell feel like a logical next step, not a random offer
Offer email (4) must work as a standalone pitch if read in isolation
Urgency in final email must be real — name the specific deadline, quantity, or trigger
Sequence must feel like a relationship, not a drip campaign of pitches
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)
/mechanism-ideation for the upsell product's mechanism/upsell-script for the immediate post-purchase OTO page (before this sequence)/email-promo for standalone promotional emails outside a sequence/hook-battery for subject line inspiration/rmbc-copy-auditGenerated using RMBC framework by Stefan Georgi. Learn more: copyaccelerator.com/join
npx claudepluginhub coleschaffer/copywritingskills-rmbcGenerate a 5-7 email welcome sequence for new subscribers or buyers — arc from first impression through value delivery to first offer using RMBC principles.
Generates a 5-7 email drip sequence for affiliate marketing, warming cold subscribers to buyers with a Welcome-Value-Sell pattern. Includes subject lines, body copy, and CTAs.
Designs email automation sequences with timing, subject lines, copy, and conditional logic for welcome series, nurture, re-engagement, abandoned cart, post-purchase, review requests, and custom campaigns triggered by subscriber actions.