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.
Portability note: The optional context file (.agents/product-marketing-context.md) and the tools REGISTRY.md referenced below are repo-local conventions, not hard dependencies. If absent, gather the same context via the Task-Specific Questions and proceed — never block on a missing file.
Single-voice craft (do NOT parallelize)
An email sequence is ONE deliverable in ONE coherent brand voice. Do not fan out emails to parallel sub-agents — split voice, broken narrative arc, and inconsistent CTAs are the predictable failure. Write the full sequence yourself, start to finish, so each email's hook builds on the previous email's promise and the voice stays continuous.
Craft upgrades (apply every time):
- Narrative arc, not isolated emails. Map the emotional through-line across the whole sequence before writing email 1 (curiosity → trust → desire → decision). Each subject line should make sense having read the prior email; each open loop opened in one email closes in a later one.
- One voice, calibrated to the reader's awareness stage. Pick the awareness level (unaware → problem-aware → solution-aware → product-aware → most-aware) and hold the same persona, vocabulary, and reading level across all emails. Read every email aloud — if two emails sound like different authors, rewrite.
- Earn each CTA's escalation. The ask should ratchet up only as fast as trust accrues (soft click → reply/engage → low-friction offer → direct buy). Never place a hard-sell CTA before the value/proof emails that justify it.
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:
Sequence Type
- Welcome/onboarding sequence
- Lead nurture sequence
- Re-engagement sequence
- Post-purchase sequence
- Event-based sequence
- Educational sequence
- Sales sequence
Audience Context
- Who are they?
- What triggered them into this sequence?
- What do they already know/believe?
- What's their current relationship with you?
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:
- Welcome + deliver promised value (immediate)
- Quick win (day 1-2)
- Story/Why (day 3-4)
- Social proof (day 5-6)
- Overcome objection (day 7-8)
- Core feature highlight (day 9-11)
- 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:
- Deliver lead magnet + intro (immediate)
- Expand on topic (day 2-3)
- Problem deep-dive (day 4-5)
- Solution framework (day 6-8)
- Case study (day 9-11)
- Differentiation (day 12-14)
- Objection handler (day 15-18)
- 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:
- Check-in (genuine concern)
- Value reminder (what's new)
- Incentive (special offer)
- 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:
- Welcome + first step (immediate)
- Getting started help (day 1)
- Feature highlight (day 2-3)
- Success story (day 4-5)
- Check-in (day 7)
- Advanced tip (day 10-12)
- 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
- Hook: First line grabs attention
- Context: Why this matters to them
- Value: The useful content
- CTA: What to do next
- 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
Output Contract & Verify
You MUST deliver, in this order:
- A Sequence Overview block (name, trigger, goal, length, timing, exit conditions).
- Every email fully written per the "For Each Email" template — subject, preview, full body copy, CTA, segment/conditions. No "[write body here]" placeholders; the sequence ships ready to load into the ESP.
- A Metrics Plan (what to measure + benchmark per stage).
Verify before declaring done (self-check, not vibes):
Evidence & no-hallucination guardrail:
- Do NOT invent product features, customer quotes, case-study numbers, pricing, or testimonials. Use only facts from the context file, the user's brief, or answers to the Task-Specific Questions. Where social proof or a case study is needed but not supplied, insert a clearly marked
[PLACEHOLDER: real customer result needed] and flag it — never fabricate a statistic or quote.
- Stay in scope: produce the email sequence asked for. Don't silently bolt on landing pages, ads, or in-app flows (point to the Related Skills instead).
- Cite the source when a benchmark number is stated (e.g. "industry welcome-series open rate ~50%"); if you can't source it, frame it as a range to test, not a fact.
Task-Specific Questions
- What triggers entry to this sequence?
- What's the primary goal/conversion action?
- What do they already know about you?
- What other emails are they receiving?
- What's your current email performance?
Tool Integrations
For implementation, see the tools registry. Key email tools:
| Tool |
Best For |
MCP |
Guide |
| Customer.io |
Behavior-based automation |
- |
customer-io.md |
| Mailchimp |
SMB email marketing |
✓ |
mailchimp.md |
| Resend |
Developer-friendly transactional |
✓ |
resend.md |
| SendGrid |
Transactional email at scale |
- |
sendgrid.md |
| Kit |
Creator/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
1---2name: mk-email-sequence3description: "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.\" French triggers: \"séquence email,\" \"séquence d'emails,\" \"campagne drip,\" \"emails de bienvenue,\" \"emails de nurturing,\" \"emails de relance,\" \"emails de réengagement,\" \"automatisation email,\" \"emails cycle de vie,\" \"tunnel email,\" \"quels emails envoyer,\" \"cadence email.\" Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro."4metadata:5 source: https://skillmd.com/skills/agentik-os/mk-email-sequence6 version: 1.2.07---89# Email Sequence Design1011You 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.1213> **Portability note:** The optional context file (`.agents/product-marketing-context.md`) and the tools `REGISTRY.md` referenced below are repo-local conventions, not hard dependencies. If absent, gather the same context via the Task-Specific Questions and proceed — never block on a missing file.1415## Single-voice craft (do NOT parallelize)1617An email sequence is ONE deliverable in ONE coherent brand voice. Do **not** fan out emails to parallel sub-agents — split voice, broken narrative arc, and inconsistent CTAs are the predictable failure. Write the full sequence yourself, start to finish, so each email's hook builds on the previous email's promise and the voice stays continuous.1819**Craft upgrades (apply every time):**201. **Narrative arc, not isolated emails.** Map the emotional through-line across the whole sequence before writing email 1 (curiosity → trust → desire → decision). Each subject line should make sense having read the prior email; each open loop opened in one email closes in a later one.212. **One voice, calibrated to the reader's awareness stage.** Pick the awareness level (unaware → problem-aware → solution-aware → product-aware → most-aware) and hold the same persona, vocabulary, and reading level across all emails. Read every email aloud — if two emails sound like different authors, rewrite.223. **Earn each CTA's escalation.** The ask should ratchet up only as fast as trust accrues (soft click → reply/engage → low-friction offer → direct buy). Never place a hard-sell CTA before the value/proof emails that justify it.2324## Initial Assessment2526**Check for product marketing context first:**27If `.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.2829Before creating a sequence, understand:30311. **Sequence Type**32 - Welcome/onboarding sequence33 - Lead nurture sequence34 - Re-engagement sequence35 - Post-purchase sequence36 - Event-based sequence37 - Educational sequence38 - Sales sequence39402. **Audience Context**41 - Who are they?42 - What triggered them into this sequence?43 - What do they already know/believe?44 - What's their current relationship with you?45463. **Goals**47 - Primary conversion goal48 - Relationship-building goals49 - Segmentation goals50 - What defines success?5152---5354## Core Principles5556### 1. One Email, One Job57- Each email has one primary purpose58- One main CTA per email59- Don't try to do everything6061### 2. Value Before Ask62- Lead with usefulness63- Build trust through content64- Earn the right to sell6566### 3. Relevance Over Volume67- Fewer, better emails win68- Segment for relevance69- Quality > frequency7071### 4. Clear Path Forward72- Every email moves them somewhere73- Links should do something useful74- Make next steps obvious7576---7778## Email Sequence Strategy7980### Sequence Length81- Welcome: 3-7 emails82- Lead nurture: 5-10 emails83- Onboarding: 5-10 emails84- Re-engagement: 3-5 emails8586Depends on:87- Sales cycle length88- Product complexity89- Relationship stage9091### Timing/Delays92- Welcome email: Immediately93- Early sequence: 1-2 days apart94- Nurture: 2-4 days apart95- Long-term: Weekly or bi-weekly9697Consider:98- B2B: Avoid weekends99- B2C: Test weekends100- Time zones: Send at local time101102### Subject Line Strategy103- Clear > Clever104- Specific > Vague105- Benefit or curiosity-driven106- 40-60 characters ideal107- Test emoji (they're polarizing)108109**Patterns that work:**110- Question: "Still struggling with X?"111- How-to: "How to [achieve outcome] in [timeframe]"112- Number: "3 ways to [benefit]"113- Direct: "[First name], your [thing] is ready"114- Story tease: "The mistake I made with [topic]"115116### Preview Text117- Extends the subject line118- ~90-140 characters119- Don't repeat subject line120- Complete the thought or add intrigue121122---123124## Sequence Types Overview125126### Welcome Sequence (Post-Signup)127**Length**: 5-7 emails over 12-14 days128**Goal**: Activate, build trust, convert129130Key emails:1311. Welcome + deliver promised value (immediate)1322. Quick win (day 1-2)1333. Story/Why (day 3-4)1344. Social proof (day 5-6)1355. Overcome objection (day 7-8)1366. Core feature highlight (day 9-11)1377. Conversion (day 12-14)138139### Lead Nurture Sequence (Pre-Sale)140**Length**: 6-8 emails over 2-3 weeks141**Goal**: Build trust, demonstrate expertise, convert142143Key emails:1441. Deliver lead magnet + intro (immediate)1452. Expand on topic (day 2-3)1463. Problem deep-dive (day 4-5)1474. Solution framework (day 6-8)1485. Case study (day 9-11)1496. Differentiation (day 12-14)1507. Objection handler (day 15-18)1518. Direct offer (day 19-21)152153### Re-Engagement Sequence154**Length**: 3-4 emails over 2 weeks155**Trigger**: 30-60 days of inactivity156**Goal**: Win back or clean list157158Key emails:1591. Check-in (genuine concern)1602. Value reminder (what's new)1613. Incentive (special offer)1624. Last chance (stay or unsubscribe)163164### Onboarding Sequence (Product Users)165**Length**: 5-7 emails over 14 days166**Goal**: Activate, drive to aha moment, upgrade167**Note**: Coordinate with in-app onboarding—email supports, doesn't duplicate168169Key emails:1701. Welcome + first step (immediate)1712. Getting started help (day 1)1723. Feature highlight (day 2-3)1734. Success story (day 4-5)1745. Check-in (day 7)1756. Advanced tip (day 10-12)1767. Upgrade/expand (day 14+)177178**For detailed templates**: See [references/sequence-templates.md](references/sequence-templates.md)179180---181182## Email Types by Category183184### Onboarding Emails185- New users series186- New customers series187- Key onboarding step reminders188- New user invites189190### Retention Emails191- Upgrade to paid192- Upgrade to higher plan193- Ask for review194- Proactive support offers195- Product usage reports196- NPS survey197- Referral program198199### Billing Emails200- Switch to annual201- Failed payment recovery202- Cancellation survey203- Upcoming renewal reminders204205### Usage Emails206- Daily/weekly/monthly summaries207- Key event notifications208- Milestone celebrations209210### Win-Back Emails211- Expired trials212- Cancelled customers213214### Campaign Emails215- Monthly roundup / newsletter216- Seasonal promotions217- Product updates218- Industry news roundup219- Pricing updates220221**For detailed email type reference**: See [references/email-types.md](references/email-types.md)222223---224225## Email Copy Guidelines226227### Structure2281. **Hook**: First line grabs attention2292. **Context**: Why this matters to them2303. **Value**: The useful content2314. **CTA**: What to do next2325. **Sign-off**: Human, warm close233234### Formatting235- Short paragraphs (1-3 sentences)236- White space between sections237- Bullet points for scanability238- Bold for emphasis (sparingly)239- Mobile-first (most read on phone)240241### Tone242- Conversational, not formal243- First-person (I/we) and second-person (you)244- Active voice245- Read it out loud—does it sound human?246247### Length248- 50-125 words for transactional249- 150-300 words for educational250- 300-500 words for story-driven251252### CTA Guidelines253- Buttons for primary actions254- Links for secondary actions255- One clear primary CTA per email256- Button text: Action + outcome257258**For detailed copy, personalization, and testing guidelines**: See [references/copy-guidelines.md](references/copy-guidelines.md)259260---261262## Output Format263264### Sequence Overview265```266Sequence Name: [Name]267Trigger: [What starts the sequence]268Goal: [Primary conversion goal]269Length: [Number of emails]270Timing: [Delay between emails]271Exit Conditions: [When they leave the sequence]272```273274### For Each Email275```276Email [#]: [Name/Purpose]277Send: [Timing]278Subject: [Subject line]279Preview: [Preview text]280Body: [Full copy]281CTA: [Button text] → [Link destination]282Segment/Conditions: [If applicable]283```284285### Metrics Plan286What to measure and benchmarks287288---289290## Output Contract & Verify291292**You MUST deliver, in this order:**2931. A **Sequence Overview** block (name, trigger, goal, length, timing, exit conditions).2942. **Every email** fully written per the "For Each Email" template — subject, preview, full body copy, CTA, segment/conditions. No "[write body here]" placeholders; the sequence ships ready to load into the ESP.2953. A **Metrics Plan** (what to measure + benchmark per stage).296297**Verify before declaring done (self-check, not vibes):**298- [ ] Email count and delays match the chosen sequence type's recommended range.299- [ ] Each email has exactly ONE primary CTA, and CTAs escalate in step with trust.300- [ ] Subject lines: 40-60 chars, no two near-duplicates, each readable in context of the prior email.301- [ ] Voice is continuous across all emails (read aloud test) and matches the reader's awareness stage.302- [ ] Exit conditions and segmentation are explicit, not implied.303304**Evidence & no-hallucination guardrail:**305- Do NOT invent product features, customer quotes, case-study numbers, pricing, or testimonials. Use only facts from the context file, the user's brief, or answers to the Task-Specific Questions. Where social proof or a case study is needed but not supplied, insert a clearly marked `[PLACEHOLDER: real customer result needed]` and flag it — never fabricate a statistic or quote.306- Stay in scope: produce the email sequence asked for. Don't silently bolt on landing pages, ads, or in-app flows (point to the Related Skills instead).307- Cite the source when a benchmark number is stated (e.g. "industry welcome-series open rate ~50%"); if you can't source it, frame it as a range to test, not a fact.308309---310311## Task-Specific Questions3123131. What triggers entry to this sequence?3142. What's the primary goal/conversion action?3153. What do they already know about you?3164. What other emails are they receiving?3175. What's your current email performance?318319---320321## Tool Integrations322323For implementation, see the [tools registry](../../tools/REGISTRY.md). Key email tools:324325| Tool | Best For | MCP | Guide |326|------|----------|:---:|-------|327| **Customer.io** | Behavior-based automation | - | [customer-io.md](../../tools/integrations/customer-io.md) |328| **Mailchimp** | SMB email marketing | ✓ | [mailchimp.md](../../tools/integrations/mailchimp.md) |329| **Resend** | Developer-friendly transactional | ✓ | [resend.md](../../tools/integrations/resend.md) |330| **SendGrid** | Transactional email at scale | - | [sendgrid.md](../../tools/integrations/sendgrid.md) |331| **Kit** | Creator/newsletter focused | - | [kit.md](../../tools/integrations/kit.md) |332333---334335## Related Skills336337- **lead-magnets**: For planning lead magnets that feed into nurture sequences338- **churn-prevention**: For cancel flows, save offers, and dunning strategy (email supports this)339- **onboarding-cro**: For in-app onboarding (email supports this)340- **copywriting**: For landing pages emails link to341- **ab-test-setup**: For testing email elements342- **popup-cro**: For email capture popups343- **revops**: For lifecycle stages that trigger email sequences