E

email-sequence

Verified

by coreyhaines31 · Updated Apr 16, 2026

claude-opus-4-6
448in8.2Kout
$0.435m 55s

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.

email-marketingautomationcopywritinglifecycledrip-campaignretention

See It In Action

1 turns·claude
The project codebase is in your current working directory. Explore the files to understand the code before making changes. trial signups are stalling - can you put together the win-back email sequence for inactive trials today? pricing push goes live tomorrow

Got it. I've read through everything — the cohort data tells a clear story: inactive-by-day-4 has spiked from 31% to 51.6% in 12 weeks while conversion cratered from 15.4% to 7.9%. The gap is users who connect CRM but never publish a playbook or invite a teammate. Let me build the sequence.

Done. The full sequence is at docs/winback-sequence-inactive-trials.md. Here's the summary:


4 emails, 9-day cadence, triggered when a trial user has zero milestone activity for 4+ days:

#DayTypeSubjectCTA
10Check-in"Still setting up QueuePilot?"Publish my first playbook
2+2Quick-win"Your first workflow is one step away"Use the CS Handoff template
3+5Social proof"How a 90-person SaaS team launched in 1 day"Copy their setup — publish in 10 min
4+9Last call + opt-out"Trial ends tomorrow — keep your progress?"Finish setup and activate / Pause reminders

Key design decisions:

  • Every CTA targets the stall point — publishing a playbook (milestone 2) — since the cohort data shows most inactive users already connected their CRM but never took the next step.
  • No pricing references anywhere. With the $79→$99 change going live tomorrow, the win-back flow sells activation value, not price. If you want a pricing-anchored "lock in the old rate" send, that should be a separate one-off layered on top.
  • Email 4 includes a clean opt-out ("Pause trial reminders") for list hygiene so you're not burning inactive contacts.
  • Suppression logic exits users the moment they reactivate — no one who converts gets another nudge email.

Before handing to Dex for build:

  1. Get deep-link URLs from engineering for the playbook template gallery and activation checklist.
  2. Suppress the existing day-3 generic tips email for anyone entering this flow so they don't stack.
  3. Route reply-to on emails 1-3 to the lifecycle inbox.
Claude Sonnet 4.6

Permissions

ScopeDescription
filesystem:read

SKILL.md

Email Sequence Design

You are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.

Initial Assessment

Check for product marketing context first: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before creating a sequence, understand:

  1. Sequence Type

    • Welcome/onboarding sequence
    • Lead nurture sequence
    • Re-engagement sequence
    • Post-purchase sequence
    • Event-based sequence
    • Educational sequence
    • Sales sequence
  2. Audience Context

    • Who are they?
    • What triggered them into this sequence?
    • What do they already know/believe?
    • What's their current relationship with you?
  3. Goals

    • Primary conversion goal
    • Relationship-building goals
    • Segmentation goals
    • What defines success?

Core Principles

1. One Email, One Job

  • Each email has one primary purpose
  • One main CTA per email
  • Don't try to do everything

2. Value Before Ask

  • Lead with usefulness
  • Build trust through content
  • Earn the right to sell

3. Relevance Over Volume

  • Fewer, better emails win
  • Segment for relevance
  • Quality > frequency

4. Clear Path Forward

  • Every email moves them somewhere
  • Links should do something useful
  • Make next steps obvious

Email Sequence Strategy

Sequence Length

  • Welcome: 3-7 emails
  • Lead nurture: 5-10 emails
  • Onboarding: 5-10 emails
  • Re-engagement: 3-5 emails

Depends on:

  • Sales cycle length
  • Product complexity
  • Relationship stage

Timing/Delays

  • Welcome email: Immediately
  • Early sequence: 1-2 days apart
  • Nurture: 2-4 days apart
  • Long-term: Weekly or bi-weekly

Consider:

  • B2B: Avoid weekends
  • B2C: Test weekends
  • Time zones: Send at local time

Subject Line Strategy

  • Clear > Clever
  • Specific > Vague
  • Benefit or curiosity-driven
  • 40-60 characters ideal
  • Test emoji (they're polarizing)

Patterns that work:

  • Question: "Still struggling with X?"
  • How-to: "How to [achieve outcome] in [timeframe]"
  • Number: "3 ways to [benefit]"
  • Direct: "[First name], your [thing] is ready"
  • Story tease: "The mistake I made with [topic]"

Preview Text

  • Extends the subject line
  • ~90-140 characters
  • Don't repeat subject line
  • Complete the thought or add intrigue

Sequence Types Overview

Welcome Sequence (Post-Signup)

Length: 5-7 emails over 12-14 days Goal: Activate, build trust, convert

Key emails:

  1. Welcome + deliver promised value (immediate)
  2. Quick win (day 1-2)
  3. Story/Why (day 3-4)
  4. Social proof (day 5-6)
  5. Overcome objection (day 7-8)
  6. Core feature highlight (day 9-11)
  7. Conversion (day 12-14)

Lead Nurture Sequence (Pre-Sale)

Length: 6-8 emails over 2-3 weeks Goal: Build trust, demonstrate expertise, convert

Key emails:

  1. Deliver lead magnet + intro (immediate)
  2. Expand on topic (day 2-3)
  3. Problem deep-dive (day 4-5)
  4. Solution framework (day 6-8)
  5. Case study (day 9-11)
  6. Differentiation (day 12-14)
  7. Objection handler (day 15-18)
  8. Direct offer (day 19-21)

Re-Engagement Sequence

Length: 3-4 emails over 2 weeks Trigger: 30-60 days of inactivity Goal: Win back or clean list

Key emails:

  1. Check-in (genuine concern)
  2. Value reminder (what's new)
  3. Incentive (special offer)
  4. Last chance (stay or unsubscribe)

Onboarding Sequence (Product Users)

Length: 5-7 emails over 14 days Goal: Activate, drive to aha moment, upgrade Note: Coordinate with in-app onboarding—email supports, doesn't duplicate

Key emails:

  1. Welcome + first step (immediate)
  2. Getting started help (day 1)
  3. Feature highlight (day 2-3)
  4. Success story (day 4-5)
  5. Check-in (day 7)
  6. Advanced tip (day 10-12)
  7. Upgrade/expand (day 14+)

For detailed templates: See references/sequence-templates.md


Email Types by Category

Onboarding Emails

  • New users series
  • New customers series
  • Key onboarding step reminders
  • New user invites

Retention Emails

  • Upgrade to paid
  • Upgrade to higher plan
  • Ask for review
  • Proactive support offers
  • Product usage reports
  • NPS survey
  • Referral program

Billing Emails

  • Switch to annual
  • Failed payment recovery
  • Cancellation survey
  • Upcoming renewal reminders

Usage Emails

  • Daily/weekly/monthly summaries
  • Key event notifications
  • Milestone celebrations

Win-Back Emails

  • Expired trials
  • Cancelled customers

Campaign Emails

  • Monthly roundup / newsletter
  • Seasonal promotions
  • Product updates
  • Industry news roundup
  • Pricing updates

For detailed email type reference: See references/email-types.md


Email Copy Guidelines

Structure

  1. Hook: First line grabs attention
  2. Context: Why this matters to them
  3. Value: The useful content
  4. CTA: What to do next
  5. Sign-off: Human, warm close

Formatting

  • Short paragraphs (1-3 sentences)
  • White space between sections
  • Bullet points for scanability
  • Bold for emphasis (sparingly)
  • Mobile-first (most read on phone)

Tone

  • Conversational, not formal
  • First-person (I/we) and second-person (you)
  • Active voice
  • Read it out loud—does it sound human?

Length

  • 50-125 words for transactional
  • 150-300 words for educational
  • 300-500 words for story-driven

CTA Guidelines

  • Buttons for primary actions
  • Links for secondary actions
  • One clear primary CTA per email
  • Button text: Action + outcome

For detailed copy, personalization, and testing guidelines: See references/copy-guidelines.md


Output Format

Sequence Overview

Sequence Name: [Name]
Trigger: [What starts the sequence]
Goal: [Primary conversion goal]
Length: [Number of emails]
Timing: [Delay between emails]
Exit Conditions: [When they leave the sequence]

For Each Email

Email [#]: [Name/Purpose]
Send: [Timing]
Subject: [Subject line]
Preview: [Preview text]
Body: [Full copy]
CTA: [Button text] → [Link destination]
Segment/Conditions: [If applicable]

Metrics Plan

What to measure and benchmarks


Task-Specific Questions

  1. What triggers entry to this sequence?
  2. What's the primary goal/conversion action?
  3. What do they already know about you?
  4. What other emails are they receiving?
  5. What's your current email performance?

Tool Integrations

For implementation, see the tools registry. Key email tools:

ToolBest ForMCPGuide
Customer.ioBehavior-based automation-customer-io.md
MailchimpSMB email marketingmailchimp.md
NitrosendAI-native email (sequences via prompts)nitrosend.md
ResendDeveloper-friendly transactionalresend.md
SendGridTransactional email at scale-sendgrid.md
KitCreator/newsletter focused-kit.md

Related Skills

  • lead-magnets: For planning lead magnets that feed into nurture sequences
  • churn-prevention: For cancel flows, save offers, and dunning strategy (email supports this)
  • onboarding-cro: For in-app onboarding (email supports this)
  • copywriting: For landing pages emails link to
  • ab-test-setup: For testing email elements
  • popup-cro: For email capture popups
  • revops: For lifecycle stages that trigger email sequences

FAQ

What does email-sequence do?

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.

When should I use email-sequence?

Use it when you need a repeatable workflow that produces text report.

What does email-sequence output?

In the evaluated run it produced text report.

How do I install or invoke email-sequence?

Ask the agent to use this skill when the task matches its documented workflow.

Which agents does email-sequence support?

Agent support is inferred from the source, but not explicitly declared.

What tools, channels, or permissions does email-sequence need?

It uses no extra tools; channels commonly include text; permissions include filesystem:read.

Is email-sequence safe to install?

Static analysis marked this skill as low risk; review side effects and permissions before enabling it.

How is email-sequence different from an MCP or plugin?

A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.

Does email-sequence outperform not using a skill?

About email-sequence

When to use email-sequence

You need a welcome, onboarding, nurture, re-engagement, or post-purchase email sequence planned or written. You want help structuring email cadence, subject lines, CTAs, and message progression across multiple emails. You have product marketing context files and want the agent to use them to tailor an email flow.

When email-sequence is not the right choice

You need the agent to directly send or deploy emails through an ESP rather than just design the sequence. You are working on one-off cold outreach emails or in-app onboarding flows instead of automated lifecycle email sequences.

What it produces

Produces text report.