rampstackco/claude-skills / skills/email-sequences
email-sequences
VerifiedDesign and write email campaigns and sequences including onboarding flows, lifecycle campaigns, transactional emails, newsletters, broadcast sends, and launch and announcement emails. Use this skill whenever the user wants to write email copy, plan an email sequence, design an onboarding drip, or set up lifecycle email campaigns. Triggers on email sequence, drip campaign, onboarding email, lifecycle email, welcome email, transactional email, newsletter, email broadcast, launch email, announcement email, nurture sequence, abandoned cart, re-engagement, win-back. Also triggers when planning email automation flows or writing email subject lines for campaigns.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 356 B |
| SKILL.md | skill md | 10.2 KB |
| references/sequence-templates.md | markdown | 8.0 KB |
| references/subject-line-patterns.md | markdown | 7.4 KB |
references/sequence-templates.md
View on GitHub# Sequence Templates
Starter outlines for the 5 standard sequence types. These are scaffolds. Adapt the cadence, voice, and content to the specific brand and audience.
---
## Onboarding sequence (SaaS, 7 emails over 14 days)
### Email 1 - Welcome
**Send:** Immediately on signup
**Subject:** Welcome to [Product]. Here's your first step.
**Body skeleton:**
- One-line welcome
- Restate the outcome they signed up for
- ONE clear next step
- Optional: founder note for early-stage products
### Email 2 - First action tutorial
**Send:** T+1 day
**Subject:** [Specific first task] in 5 minutes
**Body skeleton:**
- Hook: Why this first task matters
- 3 to 5 numbered steps
- Visual or screenshot
- CTA back to the product
### Email 3 - Build on first
**Send:** T+3 days
**Subject:** Now that [first task done], try [second task]
**Body skeleton:**
- Acknowledge progress (works even if user hasn't done first task; it primes them)
- Introduce next capability
- Show what it unlocks
- CTA
### Email 4 - Use case spotlight
**Send:** T+5 days
**Subject:** How [persona] uses [Product] to [outcome]
**Body skeleton:**
- Specific persona description
- Their workflow with the product
- Specific result
- "Try this approach" CTA
### Email 5 - Common questions
**Send:** T+7 days
**Subject:** Quick answers to questions new users ask
**Body skeleton:**
- 3 to 5 FAQs with brief answers
- Links to fuller help docs
- CTA: open help center or chat with support
### Email 6 - Re-engagement check
**Send:** T+10 days (only if user is dormant)
**Subject:** Need a hand getting started?
**Body skeleton:**
- Acknowledge they may be busy
- Offer a 10-minute call or specific resource
- One simple action they can take in <2 minutes
### Email 7 - Hand-off to ongoing comms
**Send:** T+14 days
**Subject:** You're set up. Here's what to expect from us.
**Body skeleton:**
- Confirm onboarding complete
- Set expectations for future emails (frequency, content type)
- Offer preferences center
- Light next-step CTA
---
## Lifecycle (triggered, individual emails)
### Anniversary (annual)
**Subject:** Hard to believe - it's been a year
**Body:** Celebrate the milestone, surface specific achievements ("You shipped X projects this year"), suggest next-level use case.
### Plan upgrade nudge
**Subject:** You're hitting your [Plan] limits
**Body:** Specific data showing usage approaching limits, value of next tier, painless upgrade path.
### Inactivity check (30 days dormant)
**Subject:** We haven't seen you for a bit
**Body:** Light touch, restate value, surface a recent improvement, easy way to come back.
### Power user celebration (Y key actions)
**Subject:** You've crossed [Y] [actions]. Nice.
**Body:** Acknowledge the milestone, share advanced tips, invite to community or beta.
### Feature announcement (when relevant feature ships)
**Subject:** New: [feature]
**Body:** What it does, why we built it, how to start using it. Brief.
---
## Sales nurture (B2B, 9 emails over 28 days)
### Email 1 - Deliver the asset
**Send:** Immediately on opt-in
**Subject:** Your [asset name]
**Body:** Direct download link, brief intro to what's inside.
### Email 2 - Educational angle
**Send:** T+2 days
**Subject:** [Specific question the audience asks]
**Body:** Useful content piece tied to their problem. No pitch.
### Email 3 - Educational angle (different facet)
**Send:** T+4 days
**Subject:** [Adjacent question]
**Body:** Different angle on the same problem space.
### Email 4 - Customer story
**Send:** T+7 days
**Subject:** How [Customer] [achieved specific outcome]
**Body:** Specific company, specific outcome, specific approach. Their story, with brand as supporting role.
### Email 5 - Objection handling
**Send:** T+10 days
**Subject:** "I'm not sure [common objection]"
**Body:** Address the most common reason this audience hesitates. Honest, non-defensive.
### Email 6 - Demo invitation
**Send:** T+14 days
**Subject:** Want to see [Product] in action?
**Body:** 20-minute personalized demo offer. Specific outcome the demo will show.
### Email 7 - Strong proof + soft pitch
**Send:** T+18 days
**Subject:** [Specific result] in [specific time]
**Body:** Strongest case study, direct invitation to start a trial or call.
### Email 8 - Urgency
**Send:** T+21 days
**Subject:** [Deadline or limited offer]
**Body:** Clear offer with deadline. Real urgency only - manufactured urgency damages trust.
### Email 9 - Goodbye
**Send:** T+28 days
**Subject:** Last note from us
**Body:** Acknowledge the silence. Offer one last resource or chance to opt back in. Then suppress or move to long-term nurture list.
---
## Transactional templates
### Order confirmation
**Subject:** Your order #[number] is confirmed
**Body:**
- Order summary (items, totals, shipping address)
- Estimated delivery
- Order tracking link
- Support contact
Keep marketing minimal. People are looking for specific info.
### Password reset
**Subject:** Reset your password
**Body:**
- Brief acknowledgment of the request
- Reset link (with expiration time stated)
- "Did not request this?" instruction
- Support contact
No marketing in transactional. Keep it clean.
### Email verification
**Subject:** Verify your email
**Body:**
- One-line ask
- Big verify button
- "If you did not sign up..." opt-out
- Expiration time
### Abandoned cart
**Subject:** You left these in your cart
**Body:**
- Items left in cart with images
- Quick-resume link
- Optional: incentive (free shipping, small discount)
- Support contact
Send 1 email at T+1 hour, optional second at T+24 hours, NO third email (annoyance penalty exceeds recovery).
---
## Win-back (5 emails over 20 days)
### Email 1 - We miss you
**Subject:** Hey, it's been a while
**Body:** Acknowledge the lapse, brief reminder of what's possible, soft re-engage CTA.
### Email 2 - What's new
**Subject:** A few things have changed since you were last here
**Body:** Updates, new features, recent improvements. Specific.
### Email 3 - Specific incentive
**Subject:** Come back: [specific offer]
**Body:** Concrete incentive (discount, bonus, free month). Deadline.
### Email 4 - Last chance
**Subject:** Last call: [offer ends X]
**Body:** Final reminder of the offer. Clear deadline.
### Email 5 - Sunset
**Subject:** We'll miss you
**Body:** Acknowledge they're not coming back, confirm we're stepping down sends, leave the door open.
After this email: suppress from active sends. Optional: move to a quarterly "big news only" list.
---
## Cadence rules across all sequence types
- **Default time of day:** 8 to 10 AM in the recipient's timezone for non-time-sensitive sends.
- **Avoid send fatigue:** Cap at 2 emails per week from the same brand to the same person across all programs.
- **Respect engagement:** If a user has opened zero of the last 5 emails, throttle frequency or sunset.
- **Honor unsubscribes immediately:** Same-day, all programs, no exceptions.
- **Test sending:** Send tests to 5+ devices before any sequence goes live.
---
## Subject line patterns that work
- **Specific question:** "Why your churn rate isn't moving"
- **Specific number:** "47% of B2B buyers do this before purchasing"
- **Personal/conversational:** "Quick question about [topic]"
- **Curiosity gap:** "The mistake we see in 80% of pricing pages"
- **Negative framing (sparingly):** "Don't make this mistake on your next launch"
- **Direct value:** "Free template: 90-day onboarding checklist"
Avoid:
- Subject lines that look like spam (all caps, multiple exclamations)
- Misleading subject lines (mentions in subject that aren't in body)
- Tricks ("Re:" or "Fwd:" on cold sends)
- Subject lines longer than 50 characters where avoidable
---
## Metrics to track per sequence
| Metric | Target benchmark (rough) |
|---|---|
| Open rate | 20 to 35% (varies wildly by industry) |
| Click-through rate | 2 to 5% |
| Conversion to goal | Sequence-specific |
| Unsubscribe rate per email | <0.5% |
| Spam complaint rate | <0.1% |
| Reply rate (for cold/B2B) | 1 to 3% |
Below benchmark: investigate the weakest emails in the sequence first. Above: capture what worked and apply to other sequences.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |