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.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, 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 (../../tools/REGISTRY.md). Key email tools:

---

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: For in-app onboarding (email supports this)
• copywriting: For landing pages emails link to
• ab-testing: For testing email elements
• popups: For email capture popups
• revops: For lifecycle stages that trigger email sequences

---

Supporting file: evals/evals.json

{
  "skill_name": "emails",
  "evals": [
    {
      "id": 1,
      "prompt": "Create a welcome email sequence for new users who sign up for our project management tool's free trial. The trial is 14 days. We want to get them to their aha moment (creating their first project and inviting a team member).",
      "expected_output": "Should check for product-marketing.md first. Should create a welcome sequence (5-7 emails) following the core principles: one email one job, value before ask. Should map each email to a specific goal in the 14-day trial journey. Should include timing/delays between emails. Each email should follow the email copy structure: hook → context → value → CTA → sign-off. Should include subject lines following the subject line strategy. Should align sequence with the aha moment (first project + team invite). Output should follow the structured format with sequence overview and per-email specs.",
      "assertions": [
        "Checks for product-marketing.md",
        "Creates 5-7 email welcome sequence",
        "Follows one email one job principle",
        "Maps emails to trial timeline (14 days)",
        "Includes timing between emails",
        "Each email has hook, context, value, CTA",
        "Includes subject lines for each email",
        "Aligns with stated aha moment",
        "Output follows structured per-email format"
      ],
      "files": []
    },
    {
      "id": 2,
      "prompt": "We need a lead nurture sequence for people who download our 'State of DevOps 2024' report. Goal is to get them to book a demo of our CI/CD platform.",
      "expected_output": "Should create a lead nurture sequence (6-8 emails). Should follow value before ask — first emails should provide related value, not immediately push for demo. Should map the sequence from awareness (report download) through consideration (related content, case studies) to decision (demo request). Should include timing between emails. Each email should have clear subject line, hook, single CTA. Should gradually increase commitment asks across the sequence.",
      "assertions": [
        "Creates 6-8 email lead nurture sequence",
        "Follows value before ask principle",
        "Maps from awareness through consideration to decision",
        "Includes timing between emails",
        "Each email has clear subject line and single CTA",
        "Gradually increases commitment asks",
        "Connects to original download topic"
      ],
      "files": []
    },
    {
      "id": 3,
      "prompt": "our email open rates have tanked. used to be 35% now we're at 18%. what's going on and how do we fix our subject lines?",
      "expected_output": "Should trigger on casual phrasing. Should diagnose potential causes of declining open rates: sender reputation, list hygiene, subject line quality, sending frequency, deliverability issues. Should apply the subject line strategy from the skill: test curiosity vs benefit vs urgency patterns, personalization, optimal length. Should recommend a re-engagement campaign to clean the list. Should provide specific subject line formulas and examples. Should suggest testing framework for subject lines.",
      "assertions": [
        "Triggers on casual phrasing",
        "Diagnoses potential causes beyond just subject lines",
        "Addresses sender reputation and deliverability",
        "Recommends list hygiene or re-engagement",
        "Applies subject line strategy with specific patterns",
        "Provides subject line formulas and examples",
        "Suggests testing framework"
      ],
      "files": []
    },
    {
      "id": 4,
      "prompt": "Build a re-engagement sequence for subscribers who haven't opened any emails in 90 days. We have about 5,000 inactive subscribers.",
      "expected_output": "Should create a re-engagement sequence (3-4 emails). Should follow the re-engagement pattern: first email acknowledges absence and offers value, middle emails escalate with compelling reasons to re-engage, final email is a clear 'last chance' before removal. Should recommend aggressive subject lines to break through. Should include a sunset policy (remove non-responders after sequence completes). Should address the impact on deliverability of keeping inactive subscribers.",
      "assertions": [
        "Creates 3-4 email re-engagement sequence",
        "Acknowledges absence in first email",
        "Escalates through the sequence",
        "Includes 'last chance' final email",
        "Recommends sunset policy for non-responders",
        "Addresses deliverability impact of inactive subscribers",
        "Uses compelling subject lines"
      ],
      "files": []
    },
    {
      "id": 5,
      "prompt": "What's the ideal timing for our onboarding email sequence? We send the first email immediately after signup, but we're not sure about the rest.",
      "expected_output": "Should provide timing guidance for onboarding sequences. Should reference the timing and delays framework: immediate first email (welcome/confirmation), then suggest data-driven timing based on user behavior triggers vs fixed time delays. Should recommend behavior-triggered emails when possible (user completed action → next email) with time-based fallbacks. Should provide typical timing patterns for SaaS onboarding (day 0, day 1, day 3, day 5, day 7, etc.). Should note that optimal timing depends on product complexity and trial length.",
      "assertions": [
        "Provides timing guidance for onboarding sequences",
        "Recommends immediate first email",
        "Discusses behavior-triggered vs time-based timing",
        "Provides typical timing patterns",
        "Notes timing depends on product and trial length",
        "Recommends behavior triggers with time-based fallbacks"
      ],
      "files": []
    },
    {
      "id": 6,
      "prompt": "Help me optimize our post-signup onboarding experience. Users sign up but 60% never complete setup.",
      "expected_output": "Should recognize this is an in-app onboarding optimization task, not an email sequence task. Should defer to or cross-reference the onboarding skill, which handles in-app onboarding flows, checklists, and activation optimization. May offer to help with the email component of onboarding but should make clear that onboarding is the primary skill for this task.",
      "assertions": [
        "Recognizes this as in-app onboarding optimization",
        "References or defers to onboarding skill",
        "Does not attempt full onboarding redesign using email patterns",
        "May offer email component support"
      ],
      "files": []
    }
  ]
}

---

Supporting file: references/copy-guidelines.md

Email Copy Guidelines

Contents

• Structure
• Formatting
• Tone
• Length
• CTA Buttons vs. Links
• Personalization (merge fields, dynamic content, triggered emails)
• Segmentation Strategies (by behavior, by stage, by profile)
• Testing and Optimization (what to test, how to test, metrics to track)

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
• Match your brand but lean friendly
• Read it out loud—does it sound human?

Length

• Shorter is usually better
• 50-125 words for transactional
• 150-300 words for educational
• 300-500 words for story-driven
• If it's long, it better be good

CTA Buttons vs. Links

• Buttons: Primary actions, high-visibility
• Links: Secondary actions, in-text
• One clear primary CTA per email
• Button text: Action + outcome

---

Personalization

Merge Fields

• First name (fallback to "there" or "friend")
• Company name (B2B)
• Relevant data (usage, plan, etc.)

Dynamic Content

• Based on segment
• Based on behavior
• Based on stage

Triggered Emails

• Action-based sends
• More relevant than time-based
• Examples: Feature used, milestone hit, inactivity

---

Segmentation Strategies

By Behavior

• Openers vs. non-openers
• Clickers vs. non-clickers
• Active vs. inactive

By Stage

• Trial vs. paid
• New vs. long-term
• Engaged vs. at-risk

By Profile

• Industry/role (B2B)
• Use case / goal
• Company size

---

Testing and Optimization

What to Test

• Subject lines (highest impact)
• Send times
• Email length
• CTA placement and copy
• Personalization level
• Sequence timing

How to Test

• A/B test one variable at a time
• Sufficient sample size
• Statistical significance
• Document learnings

Metrics to Track

• Open rate (benchmark: 20-40%)
• Click rate (benchmark: 2-5%)
• Unsubscribe rate (keep under 0.5%)
• Conversion rate (specific to sequence goal)
• Revenue per email (if applicable)

---

Supporting file: references/email-types.md

Email Types Reference

A comprehensive guide to lifecycle and campaign emails. Use this as an audit checklist and implementation reference.

Contents

• Onboarding Emails (new users series, new customers series, key onboarding step reminder, new user invite)
• Retention Emails (upgrade to paid, upgrade to higher plan, ask for review, offer support proactively, product usage report, NPS survey, referral program)
• Billing Emails (switch to annual, failed payment recovery, cancellation survey, upcoming renewal reminder)
• Usage Emails (daily/weekly/monthly summary, key event or milestone notifications)
• Win-Back Emails (expired trials, cancelled customers)
• Campaign Emails (monthly roundup/newsletter, seasonal promotions, product updates, industry news roundup, pricing update)
• Email Audit Checklist (onboarding, retention, billing, usage, win-back, campaigns)

Onboarding Emails

New Users Series

Trigger: User signs up (free or trial) Goal: Activate user, drive to aha moment Typical sequence: 5-7 emails over 14 days

• Email 1: Welcome + single next step (immediate)
• Email 2: Quick win / getting started (day 1)
• Email 3: Key feature highlight (day 3)
• Email 4: Success story / social proof (day 5)
• Email 5: Check-in + offer help (day 7)
• Email 6: Advanced tip (day 10)
• Email 7: Upgrade prompt or next milestone (day 14)

Key metrics: Activation rate, feature adoption

---

New Customers Series

Trigger: User converts to paid Goal: Reinforce purchase decision, drive adoption, reduce early churn Typical sequence: 3-5 emails over 14 days

• Email 1: Thank you + what's next (immediate)
• Email 2: Getting full value — setup checklist (day 2)
• Email 3: Pro tips for paid features (day 5)
• Email 4: Success story from similar customer (day 7)
• Email 5: Check-in + introduce support resources (day 14)

Key point: Different from new user series—they've committed. Focus on reinforcement and expansion, not conversion.

---

Key Onboarding Step Reminder

Trigger: User hasn't completed critical setup step after X time Goal: Nudge completion of high-value action Format: Single email or 2-3 email mini-sequence

Example triggers:

• Hasn't connected integration after 48 hours
• Hasn't invited team member after 3 days
• Hasn't completed profile after 24 hours

Copy approach:

• Remind them what they started
• Explain why this step matters
• Make it easy (direct link to complete)
• Offer help if stuck

---

New User Invite

Trigger: Existing user invites teammate Goal: Activate the invited user Recipient: The person being invited

• Email 1: You've been invited (immediate)
• Email 2: Reminder if not accepted (day 2)
• Email 3: Final reminder (day 5)

Copy approach:

• Personalize with inviter's name
• Explain what they're joining
• Single CTA to accept invite
• Social proof optional

---

Retention Emails

Upgrade to Paid

Trigger: Free user shows engagement, or trial ending Goal: Convert free to paid Typical sequence: 3-5 emails

Trigger options:

• Time-based (trial day 10, 12, 14)
• Behavior-based (hit usage limit, used premium feature)
• Engagement-based (highly active free user)

Sequence structure:

• Value summary: What they've accomplished
• Feature comparison: What they're missing
• Social proof: Who else upgraded
• Urgency: Trial ending, limited offer
• Final: Last chance + easy path

---

Upgrade to Higher Plan

Trigger: User approaching plan limits or using features available on higher tier Goal: Upsell to next tier Format: Single email or 2-3 email sequence

Trigger examples:

• 80% of seat limit reached
• 90% of storage/usage limit
• Tried to use higher-tier feature
• Power user behavior patterns

Copy approach:

• Acknowledge their growth (positive framing)
• Show what next tier unlocks
• Quantify value vs. cost
• Easy upgrade path

---

Ask for Review

Trigger: Customer milestone (30/60/90 days, key achievement, support resolution) Goal: Generate social proof on G2, Capterra, app stores Format: Single email

Best timing:

• After positive support interaction
• After achieving measurable result
• After renewal
• NOT after billing issues or bugs

Copy approach:

• Thank them for being a customer
• Mention specific value/milestone if possible
• Explain why reviews matter (help others decide)
• Direct link to review platform
• Keep it short—this is an ask

---

Offer Support Proactively

Trigger: Signs of struggle (drop in usage, failed actions, error encounters) Goal: Save at-risk user, improve experience Format: Single email

Trigger examples:

• Usage dropped significantly week-over-week
• Multiple failed attempts at action
• Viewed help docs repeatedly
• Stuck at same onboarding step

Copy approach:

• Genuine concern tone
• Specific: "I noticed you..." (if data allows)
• Offer direct help (not just link to docs)
• Personal from support or CSM
• No sales pitch—pure help

---

Product Usage Report

Trigger: Time-based (weekly, monthly, quarterly) Goal: Demonstrate value, drive engagement, reduce churn Format: Single email, recurring

What to include:

• Key metrics/activity summary
• Comparison to previous period
• Achievements/milestones
• Suggestions for improvement
• Light CTA to explore more

Examples:

• "You saved X hours this month"
• "Your team completed X projects"
• "You're in the top X% of users"

Key point: Make them feel good and remind them of value delivered.

---

NPS Survey

Trigger: Time-based (quarterly) or event-based (post-milestone) Goal: Measure satisfaction, identify promoters and detractors Format: Single email

Best practices:

• Keep it simple: Just the NPS question initially
• Follow-up form for "why" based on score
• Personal sender (CEO, founder, CSM)
• Tell them how you'll use feedback

Follow-up based on score:

• Promoters (9-10): Thank + ask for review/referral
• Passives (7-8): Ask what would make it a 10
• Detractors (0-6): Personal outreach to understand issues

---

Referral Program

Trigger: Customer milestone, promoter NPS score, or campaign Goal: Generate referrals Format: Single email or periodic reminders

Good timing:

• After positive NPS response
• After customer achieves result
• After renewal
• Seasonal campaigns

Copy approach:

• Remind them of their success
• Explain the referral offer clearly
• Make sharing easy (unique link)
• Show what's in it for them AND referee

---

Billing Emails

Switch to Annual

Trigger: Monthly subscriber at renewal time or campaign Goal: Convert monthly to annual (improve LTV, reduce churn) Format: Single email or 2-email sequence

Value proposition:

• Calculate exact savings
• Additional benefits (if any)
• Lock in current price messaging
• Easy one-click switch

Best timing:

• Around monthly renewal date
• End of year / new year
• After 3-6 months of loyalty
• Price increase announcement (lock in old rate)

---

Failed Payment Recovery

Trigger: Payment fails Goal: Recover revenue, retain customer Typical sequence: 3-4 emails over 7-14 days

Sequence structure:

• Email 1 (Day 0): Friendly notice, update payment link
• Email 2 (Day 3): Reminder, service may be interrupted
• Email 3 (Day 7): Urgent, account will be suspended
• Email 4 (Day 10-14): Final notice, what they'll lose

Copy approach:

• Assume it's an accident (card expired, etc.)
• Clear, direct, no guilt
• Single CTA to update payment
• Explain what happens if not resolved

Key metrics: Recovery rate, time to recovery

---

Cancellation Survey

Trigger: User cancels subscription Goal: Learn why, opportunity to save Format: Single email (immediate)

Options:

• In-app survey at cancellation (better completion)
• Follow-up email if they skip in-app
• Personal outreach for high-value accounts

Questions to ask:

• Primary reason for cancelling
• What could we have done better
• Would anything change your mind
• Can we help with transition

Winback opportunity: Based on reason, offer targeted save (discount, pause, downgrade, training).

---

Upcoming Renewal Reminder

Trigger: X days before renewal (14 or 30 days typical) Goal: No surprise charges, opportunity to expand Format: Single email

What to include:

• Renewal date and amount
• What's included in renewal
• How to update payment/plan
• Changes to pricing/features (if any)
• Optional: Upsell opportunity

Required for: Annual subscriptions, high-value contracts

---

Usage Emails

Daily/Weekly/Monthly Summary

Trigger: Time-based Goal: Drive engagement, demonstrate value Format: Single email, recurring

Content by frequency:

• Daily: Notifications, quick stats (for high-engagement products)
• Weekly: Activity summary, highlights, suggestions
• Monthly: Comprehensive report, achievements, ROI if calculable

Structure:

• Key metrics at a glance
• Notable achievements
• Activity breakdown
• Suggestions / what to try next
• CTA to dive deeper

Personalization: Must be relevant to their actual usage. Empty reports are worse than no report.

---

Key Event or Milestone Notifications

Trigger: Specific achievement or event Goal: Celebrate, drive continued engagement Format: Single email per event

Milestone examples:

• First [action] completed
• 10th/100th [thing] created
• Goal achieved
• Team collaboration milestone
• Usage streak

Copy approach:

• Celebration tone
• Specific achievement
• Context (compared to others, compared to before)
• What's next / next milestone

---

Win-Back Emails

Expired Trials

Trigger: Trial ended without conversion Goal: Convert or re-engage Typical sequence: 3-4 emails over 30 days

Sequence structure:

• Email 1 (Day 1 post-expiry): Trial ended, here's what you're missing
• Email 2 (Day 7): What held you back? (gather feedback)
• Email 3 (Day 14): Incentive offer (discount, extended trial)
• Email 4 (Day 30): Final reach-out, door is open

Segmentation: Different approach based on trial engagement level:

• High engagement: Focus on removing friction to convert
• Low engagement: Offer fresh start, more onboarding help
• No engagement: Ask what happened, offer demo/call

---

Cancelled Customers

Trigger: Time after cancellation (30, 60, 90 days) Goal: Win back churned customers Typical sequence: 2-3 emails spread over 90 days

Sequence structure:

• Email 1 (Day 30): What's new since you left
• Email 2 (Day 60): We've addressed [common reason]
• Email 3 (Day 90): Special offer to return

Copy approach:

• No guilt, no desperation
• Genuine updates and improvements
• Personalize based on cancellation reason if known
• Make return easy

Key point: They're more likely to return if their reason was addressed.

---

Campaign Emails

Monthly Roundup / Newsletter

Trigger: Time-based (monthly) Goal: Engagement, brand presence, content distribution Format: Single email, recurring

Content mix:

• Product updates and tips
• Customer stories
• Educational content
• Company news
• Industry insights

Best practices:

• Consistent send day/time
• Scannable format
• Mix of content types
• One primary CTA focus
• Unsubscribe is okay—keeps list healthy

---

Seasonal Promotions

Trigger: Calendar events (Black Friday, New Year, etc.) Goal: Drive conversions with timely offer Format: Campaign burst (2-4 emails)

Common opportunities:

• New Year (fresh start, annual planning)
• End of fiscal year (budget spending)
• Black Friday / Cyber Monday
• Industry-specific seasons
• Back to school / work

Sequence structure:

• Announcement: Offer reveal
• Reminder: Midway through promotion
• Last chance: Final hours

---

Product Updates

Trigger: New feature release Goal: Adoption, engagement, demonstrate momentum Format: Single email per major release

What to include:

• What's new (clear and simple)
• Why it matters (benefit, not just feature)
• How to use it (direct link)
• Who asked for it (community acknowledgment)

Segmentation: Consider targeting based on relevance:

• Users who would benefit most
• Users who requested feature
• Power users first (for beta feel)

---

Industry News Roundup

Trigger: Time-based (weekly or monthly) Goal: Thought leadership, engagement, brand value Format: Curated newsletter

Content:

• Curated news and links
• Your take / commentary
• What it means for readers
• How your product helps

Best for: B2B products where customers care about industry trends.

---

Pricing Update

Trigger: Price change announcement Goal: Transparent communication, minimize churn Format: Single email (or sequence for major changes)

Timeline:

• Announce 30-60 days before change
• Reminder 14 days before
• Final notice 7 days before

Copy approach:

• Clear, direct, transparent
• Explain the why (value delivered, costs increased)
• Grandfather if possible (lock in old rate)
• Give options (annual lock-in, downgrade)

Important: Honesty and advance notice build trust even when price increases.

---

Email Audit Checklist

Use this to audit your current email program:

Onboarding

• New users series
• New customers series
• Key onboarding step reminders
• New user invite sequence

Retention

• Upgrade to paid sequence
• Upgrade to higher plan triggers
• Ask for review (timed properly)
• Proactive support outreach
• Product usage reports
• NPS survey
• Referral program emails

Billing

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

Usage

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

Win-Back

• Expired trial sequence
• Cancelled customer sequence

Campaigns

• Monthly roundup / newsletter
• Seasonal promotion calendar
• Product update announcements
• Pricing update communications

---

Supporting file: references/sequence-templates.md

Email Sequence Templates

Detailed templates for common email sequences.

Contents

• Welcome Sequence (Post-Signup)
• Lead Nurture Sequence (Pre-Sale)
• Re-Engagement Sequence
• Onboarding Sequence (Product Users)

Welcome Sequence (Post-Signup)

Email 1: Welcome (Immediate)

• Subject: Welcome to [Product] — here's your first step
• Deliver what was promised (lead magnet, access, etc.)
• Single next action
• Set expectations for future emails

Email 2: Quick Win (Day 1-2)

• Subject: Get your first [result] in 10 minutes
• Enable small success
• Build confidence
• Link to helpful resource

Email 3: Story/Why (Day 3-4)

• Subject: Why we built [Product]
• Origin story or mission
• Connect emotionally
• Show you understand their problem

Email 4: Social Proof (Day 5-6)

• Subject: How [Customer] achieved [Result]
• Case study or testimonial
• Relatable to their situation
• Soft CTA to explore

Email 5: Overcome Objection (Day 7-8)

• Subject: "I don't have time for X" — sound familiar?
• Address common hesitation
• Reframe the obstacle
• Show easy path forward

Email 6: Core Feature (Day 9-11)

• Subject: Have you tried [Feature] yet?
• Highlight underused capability
• Show clear benefit
• Direct CTA to try it

Email 7: Conversion (Day 12-14)

• Subject: Ready to [upgrade/buy/commit]?
• Summarize value
• Clear offer
• Urgency if appropriate
• Risk reversal (guarantee, trial)

---

Lead Nurture Sequence (Pre-Sale)

Email 1: Deliver + Introduce (Immediate)

• Deliver the lead magnet
• Brief intro to who you are
• Preview what's coming

Email 2: Expand on Topic (Day 2-3)

• Related insight to lead magnet
• Establish expertise
• Light CTA to content

Email 3: Problem Deep-Dive (Day 4-5)

• Articulate their problem deeply
• Show you understand
• Hint at solution

Email 4: Solution Framework (Day 6-8)

• Your approach/methodology
• Educational, not salesy
• Builds toward your product

Email 5: Case Study (Day 9-11)

• Real results from real customer
• Specific and relatable
• Soft CTA

Email 6: Differentiation (Day 12-14)

• Why your approach is different
• Address alternatives
• Build preference

Email 7: Objection Handler (Day 15-18)

• Common concern addressed
• FAQ or myth-busting
• Reduce friction

Email 8: Direct Offer (Day 19-21)

• Clear pitch
• Strong value proposition
• Specific CTA
• Urgency if available

---

Re-Engagement Sequence

Email 1: Check-In (Day 30-60 of inactivity)

• Subject: Is everything okay, [Name]?
• Genuine concern
• Ask what happened
• Easy win to re-engage

Email 2: Value Reminder (Day 2-3 after)

• Subject: Remember when you [achieved X]?
• Remind of past value
• What's new since they left
• Quick CTA

Email 3: Incentive (Day 5-7 after)

• Subject: We miss you — here's something special
• Offer if appropriate
• Limited time
• Clear CTA

Email 4: Last Chance (Day 10-14 after)

• Subject: Should we stop emailing you?
• Honest and direct
• One-click to stay or go
• Clean the list if no response

---

Onboarding Sequence (Product Users)

Coordinate with in-app onboarding. Email supports, doesn't duplicate.

Email 1: Welcome + First Step (Immediate)

• Confirm signup
• One critical action
• Link directly to that action

Email 2: Getting Started Help (Day 1)

• If they haven't completed step 1
• Quick tip or video
• Support option

Email 3: Feature Highlight (Day 2-3)

• Key feature they should know
• Specific use case
• In-app link

Email 4: Success Story (Day 4-5)

• Customer who succeeded
• Relatable journey
• Motivational

Email 5: Check-In (Day 7)

• How's it going?
• Ask for feedback
• Offer help

Email 6: Advanced Tip (Day 10-12)

• Power feature
• For engaged users
• Level-up content

Email 7: Upgrade/Expand (Day 14+)

• For trial users: conversion push
• For free users: upgrade prompt
• For paid: expansion opportunity

---

Supporting file: tools/REGISTRY.md

Marketing Tools Registry

Quick reference for AI agents to discover tool capabilities and integration methods.

How to Use This Registry

1. Find tools by category - Browse sections below for tools in each domain
2. Check integration methods - See what APIs, MCPs, CLIs, or SDKs are available
3. Read integration guides - Detailed setup and common operations in integrations/

---

Tool Index

---

By Category

Analytics

Track user behavior, measure conversions, and analyze marketing performance.

Agent recommendation: Start with GA4 if using Google ecosystem. Use Mixpanel or Amplitude for deeper product analytics. Plausible for privacy-focused sites.

SEO

Search engine optimization tools for keyword research, rank tracking, and site audits.

Agent recommendation: Google Search Console is essential (free). Add Semrush or Ahrefs for competitive research. DataForSEO for programmatic SERP data. Keywords Everywhere for quick keyword lookups. RankParse for agent workflows where per-call cost matters — backlinks, domain authority, and tech stack at a fraction of enterprise pricing.

CRM

Customer relationship management and sales tools.

Agent recommendation: HubSpot for startups/SMBs. Close for high-velocity inside sales. Salesforce for enterprise.

Payments

Payment processing and subscription management.

Agent recommendation: Stripe is the default for SaaS. Paddle for built-in tax compliance.

Referral & Affiliate

Tools for referral programs, affiliate tracking, and partner management.

Agent recommendation: Rewardful or Tolt for Stripe-based SaaS. PartnerStack for enterprise partner programs. Dub.co for link attribution.

Email

Email marketing, transactional email, and automation platforms.

Agent recommendation: Resend for transactional (dev-friendly). Sequenzy for lifecycle email, sequences, and agent-driven email marketing. Postmark for deliverability. Customer.io for advanced automation. Kit for creators. Beehiiv for newsletters. Klaviyo for e-commerce email/SMS. ActiveCampaign for email + CRM combo.

SMS / Messaging

SMS and MMS marketing platforms and programmable messaging APIs.

Agent recommendation: Klaviyo SMS for ecom already on Klaviyo email. Postscript for Shopify-first depth. Attentive for mid-market+ wanting concierge support. Twilio (or Plivo for lower cost) for custom builds and transactional/auth. AudienceTap when AI creative or on-pack QR opt-in matters.

Advertising

Paid advertising platforms and campaign management.

Agent recommendation: Google Ads for search intent. Meta for demand generation. LinkedIn for B2B.

Automation

Workflow automation and integration platforms.

Agent recommendation: Zapier SDK for agents that need to interact with any app directly. Zaps for always-on automations.

CRO & A/B Testing

Conversion rate optimization, heatmaps, and experimentation.

Agent recommendation: Hotjar for understanding user behavior. Optimizely for running experiments.

Scheduling

Booking and appointment scheduling tools.

Agent recommendation: Calendly for general use. SavvyCal for personalized booking experiences.

Forms & Surveys

Form builders and survey platforms.

Agent recommendation: Typeform for engaging forms and surveys.

Messaging

In-app messaging, chat, and customer communication.

Agent recommendation: Intercom for in-app messaging and customer support.

Social Media

Social media scheduling, management, and analytics.

Agent recommendation: Buffer for scheduling and analytics across social platforms.

Video

Video hosting, creation, and AI generation.

Agent recommendation: HeyGen for AI avatar videos (MCP-enabled). Hyperframes for templated, data-driven video from code. Wistia for hosting and analytics.

Data Enrichment

Company and person data enrichment for sales and marketing.

Agent recommendation: Clearbit for enrichment. Apollo for prospecting and outbound. ZoomInfo for enterprise B2B data with intent signals. Clay for waterfall enrichment across multiple providers.

Email Verification

Pre-outreach email deliverability validation.

Agent recommendation: Truelist for any prospect list before outreach — Apollo/ZoomInfo/Hunter data accuracy is typically 60–80%, validation is non-negotiable to keep sender reputation healthy.

Developer Intent / GitHub

Discovery channel for dev-tool SaaS prospecting via GitHub stargazers, forkers, and watchers.

Agent recommendation: Use github-prospects.js CLI to pull stargazers/forks of 3–5 anchor repos (competitors, category leaders, complementary tools). Filter to users with company field set, then enrich missing emails via Apollo or Hunter, then validate via Truelist before outreach.

Site Scraping (single-target only)

Programmatic page extraction for individual public business sites — not for the platforms hosting prospects (Google Maps, LinkedIn, Yelp, Apollo, etc.).

Agent recommendation: Default to Firecrawl for static-ish pages and structured extraction. Use Browserbase when the site requires JS rendering, form interaction, cookie consent, or auth — and when you want session recordings for debugging. For both: discovery happens on platforms (manual browser); extraction happens on the prospect's own website URL. Don't point either tool at LinkedIn, Google Maps, Yelp, or similar.

Reviews

Review management and social proof platforms.

Agent recommendation: Trustpilot for consumer products. G2 for B2B software.

Push Notifications

Push notification delivery platforms.

Agent recommendation: OneSignal for web and mobile push notifications.

Webinar

Webinar and virtual event platforms.

Agent recommendation: Demio for marketing-focused webinars. Livestorm for full event engagement.

Sales Engagement

Sales engagement and outreach automation platforms.

Agent recommendation: Outreach for enterprise sales teams managing multi-touch sequences at scale.

Product Analytics

Product analytics, feature adoption tracking, and in-app guidance.

Agent recommendation: Pendo for tracking feature adoption and delivering targeted in-app guidance.

Competitive Intelligence

Traffic analytics, competitor benchmarking, and market research.

Agent recommendation: Similarweb for competitor traffic analysis and market benchmarking.

Audience Research

Audience intelligence and behavioral research tools.

Agent recommendation: SparkToro for discovering where your ICP spends time — what they read, watch, listen to, follow, and search for. Essential for customer research, content strategy, and media buying decisions.

Visitor Identification

Website visitor de-anonymization for B2B sales and marketing.

Agent recommendation: RB2B for identifying anonymous B2B website visitors and routing high-intent visitors to outreach tools. Pairs well with Clay for enrichment and Instantly/Lemlist for cold email.

Revenue Intelligence

Sales conversation analytics, call recording, and deal intelligence.

Agent recommendation: Gong for mining sales call transcripts for customer research, competitive intelligence, and coaching insights. Essential for revenue attribution and win/loss analysis.

AI Content

AI-powered content generation and optimization platforms.

Agent recommendation: AirOps for building AI content workflows that generate SEO-optimized content at scale.

AI Search

AI-powered web search APIs built for LLMs and agents. Return structured results with on-demand text, highlights, and summaries.

Agent recommendation: Exa for neural search over the open web — content research, competitor/similar-page discovery, link prospecting, news monitoring, and audience research. Pairs well with seo-audit, content-strategy, and competitor-profiling skills.

Partner Ecosystem

Partner data sharing, co-sell, and ecosystem management.

Agent recommendation: Crossbeam for identifying partner account overlaps and co-sell opportunities. Introw for full partner relationship management — partner pipeline, commissions, tasks, and automated business review prep.

Email Outreach

Cold email outreach and email finding tools for link building and sales prospecting.

Agent recommendation: Hunter for finding emails. Lemlist or Instantly for sending cold email campaigns. Snov for combined finding + outreach.

Data Aggregation

Marketing data pipeline tools that connect multiple platforms for unified reporting.

Agent recommendation: Supermetrics for pulling data from multiple marketing platforms into unified reports. Coupler.io for automated data flows to spreadsheets and BI tools.

Commerce & CMS

E-commerce platforms and content management systems.

Agent recommendation: Shopify for e-commerce. Webflow for marketing sites. WordPress for blogs. For headless CMS: Sanity for developer-flexible content, Contentful for enterprise multi-locale, Strapi for self-hosted/budget-conscious. See headless CMS guide (../skills/content-strategy/references/headless-cms.md) for selection criteria.

---

CLI Tools

Zero-dependency, single-file Node.js CLIs for tools that don't ship their own. See clis/README.md for install instructions and usage.

All CLIs follow a consistent pattern:

• No dependencies — Node 18+ only, uses native fetch
• JSON output — pipe to jq, save to file, or use in scripts
• Env var auth — set {TOOL}_API_KEY and go
• Consistent commands — {tool} <resource> <action> [options]

---

MCP-Enabled Tools

These tools have Model Context Protocol servers available, enabling direct agent interaction:

• ga4 - Google Analytics 4 data access
• stripe - Payment and subscription management
• mailchimp - Email campaign management
• google-ads - Ad campaign management
• resend - Transactional email sending
• zapier - Workflow automation + SDK for 8,000+ app integrations
• zoominfo - B2B contacts and intent data
• clay - Data enrichment and outbound automation
• supermetrics - Cross-platform marketing data
• coupler - Marketing data pipelines
• outreach - Sales engagement sequences
• crossbeam - Partner ecosystem data
• introw - Partner relationship management
• exa - AI-powered web search for LLMs and agents

To use MCP tools, ensure the appropriate MCP server is configured in your environment.

Composio Integration

Composio (integrations/composio.md) provides managed OAuth and pre-built connectors for 500+ tools via a single MCP server. It adds MCP access to tools that don't have native MCP servers, including HubSpot, Salesforce, Meta Ads, LinkedIn Ads, Google Sheets, Slack, Notion, and more.

• Setup: npx @composio/mcp@latest setup
• Quick start: See tools/composio/README.md (composio/README.md)
• Marketing tool mapping: See tools/composio/marketing-tools.md (composio/marketing-tools.md)

Use Composio when you need MCP access to OAuth-heavy tools. Prefer native MCP servers (GA4, Stripe, Mailchimp, etc.) when available — they have deeper coverage.

Cogny Integration

Cogny (integrations/cogny.md) is a hosted MCP gateway focused on marketing channels — one federated MCP URL with managed OAuth across every channel you've connected. Narrower than Composio (marketing-only) and useful when you want SEO, paid social, and privacy-friendly analytics behind a single MCP login.

• Setup: connect channels at cogny.com (https://cogny.com), then in Claude.ai go to Settings → Connectors → Add custom connector and paste https://app.cogny.com/mcp
• Channels: Search Console, Bing Webmaster, Semrush, LinkedIn Ads, Reddit Ads, TikTok Ads, Plausible, Fathom
• Pricing: Solo plan starts at $9/mo (7-day trial)

Use Cogny when you only need marketing channels and want to avoid running your own OAuth proxy. Prefer native APIs when you need deep, custom control of a single tool.

---

Quick Start by Use Case

Setting up analytics tracking

1. Read ga4.md (integrations/ga4.md) for web analytics
2. Read segment.md (integrations/segment.md) if routing to multiple tools

Launching a referral program

1. Read rewardful.md (integrations/rewardful.md) or tolt.md (integrations/tolt.md) for Stripe-based programs
2. Read dub-co.md (integrations/dub-co.md) for link tracking

Setting up email automation

1. Read customer-io.md (integrations/customer-io.md) for behavior-based automation
2. Read resend.md (integrations/resend.md) for transactional email

Running email outreach for backlinks

1. Read hunter.md (integrations/hunter.md) for finding emails
2. Read lemlist.md (integrations/lemlist.md) or instantly.md (integrations/instantly.md) for sending campaigns

Running paid ads

1. Read google-ads.md (integrations/google-ads.md) for search campaigns
2. Read meta-ads.md (integrations/meta-ads.md) for social campaigns

---

Supporting file: tools/integrations/customer-io.md

Customer.io

Behavior-based messaging platform for email, push, SMS, and in-app.

Capabilities

Authentication

• Track API: Site ID + API Key (Basic auth)
• App API: Bearer token
• Header: Authorization: Basic {base64(site_id:api_key)}

Common Agent Operations

Identify customer

PUT https://track.customer.io/api/v1/customers/{customer_id}

Authorization: Basic {base64(site_id:api_key)}

{
  "email": "user@example.com",
  "created_at": 1705312800,
  "first_name": "John",
  "plan": "pro"
}

Track event

POST https://track.customer.io/api/v1/customers/{customer_id}/events

Authorization: Basic {base64(site_id:api_key)}

{
  "name": "purchase",
  "data": {
    "product": "Pro Plan",
    "amount": 99
  }
}

Track anonymous event

POST https://track.customer.io/api/v1/events

Authorization: Basic {base64(site_id:api_key)}

{
  "name": "page_viewed",
  "data": {
    "page": "/pricing"
  },
  "anonymous_id": "anon_123"
}

Delete customer

DELETE https://track.customer.io/api/v1/customers/{customer_id}

Authorization: Basic {base64(site_id:api_key)}

Get customer (App API)

GET https://api.customer.io/v1/customers/{customer_id}/attributes

Authorization: Bearer {app_api_key}

List campaigns

GET https://api.customer.io/v1/campaigns

Authorization: Bearer {app_api_key}

Get campaign metrics

GET https://api.customer.io/v1/campaigns/{campaign_id}/metrics

Authorization: Bearer {app_api_key}

Trigger broadcast

POST https://api.customer.io/v1/campaigns/{campaign_id}/triggers

Authorization: Bearer {app_api_key}

{
  "emails": ["user@example.com"],
  "data": {
    "coupon_code": "SAVE20"
  }
}

Send transactional email

POST https://api.customer.io/v1/send/email

Authorization: Bearer {app_api_key}

{
  "transactional_message_id": "1",
  "to": "user@example.com",
  "identifiers": {
    "id": "user_123"
  },
  "message_data": {
    "order_id": "ORD-456"
  }
}

JavaScript SDK

// Initialize
_cio.identify({
  id: 'user_123',
  email: 'user@example.com',
  created_at: 1705312800,
  plan: 'pro'
});

// Track event
_cio.track('purchase', {
  product: 'Pro Plan',
  amount: 99
});

// Track page view
_cio.page();

Key Concepts

• People - Customers and leads
• Segments - Dynamic groups based on attributes/behavior
• Campaigns - Automated message sequences
• Broadcasts - One-time sends
• Transactional - Triggered messages

Attribute Types

• Standard: email, created_at, unsubscribed
• Custom: Any key you define
• Computed: Aggregations from events

When to Use

• Behavior-based email automation
• Multi-channel messaging (email, push, SMS)
• Onboarding sequences
• Re-engagement campaigns
• Transactional messages

Rate Limits

• Track API: 100 requests/second
• App API: 10 requests/second

Relevant Skills

• emails
• onboarding
• analytics

---

Supporting file: tools/integrations/kit.md

Kit (formerly ConvertKit)

Email marketing platform for creators and newsletter businesses.

Capabilities

Authentication

• Type: API Key or API Secret
• Parameter: api_key={key} or api_secret={secret} in query/body
• Get key: Settings > Advanced in Kit dashboard

Common Agent Operations

List subscribers

GET https://api.convertkit.com/v3/subscribers?api_secret={api_secret}&page=1

Get subscriber

GET https://api.convertkit.com/v3/subscribers/{subscriber_id}?api_secret={api_secret}

Add subscriber to form

POST https://api.convertkit.com/v3/forms/{form_id}/subscribe

{
  "api_key": "{api_key}",
  "email": "user@example.com",
  "first_name": "John",
  "fields": {
    "company": "Example Inc"
  }
}

Add subscriber to sequence

POST https://api.convertkit.com/v3/sequences/{sequence_id}/subscribe

{
  "api_key": "{api_key}",
  "email": "user@example.com"
}

Tag subscriber

POST https://api.convertkit.com/v3/tags/{tag_id}/subscribe

{
  "api_key": "{api_key}",
  "email": "user@example.com"
}

Remove tag from subscriber

DELETE https://api.convertkit.com/v3/subscribers/{subscriber_id}/tags/{tag_id}?api_secret={api_secret}

Update subscriber

PUT https://api.convertkit.com/v3/subscribers/{subscriber_id}

{
  "api_secret": "{api_secret}",
  "first_name": "Jane",
  "fields": {
    "plan": "pro"
  }
}

Unsubscribe

PUT https://api.convertkit.com/v3/unsubscribe

{
  "api_secret": "{api_secret}",
  "email": "user@example.com"
}

List forms

GET https://api.convertkit.com/v3/forms?api_key={api_key}

List sequences

GET https://api.convertkit.com/v3/sequences?api_key={api_key}

List tags

GET https://api.convertkit.com/v3/tags?api_key={api_key}

Create broadcast

POST https://api.convertkit.com/v3/broadcasts

{
  "api_secret": "{api_secret}",
  "subject": "Newsletter Subject",
  "content": "<p>Email content here</p>",
  "email_layout_template": "default"
}

Key Concepts

• Subscribers - Email contacts
• Forms - Signup forms
• Sequences - Automated email series
• Tags - Subscriber labels
• Broadcasts - One-time sends
• Custom Fields - Subscriber attributes

Subscriber States

• active - Can receive emails
• unsubscribed - Opted out
• bounced - Email bounced
• complained - Marked as spam
• inactive - Cold subscriber

When to Use

• Creator/newsletter businesses
• Simple email automation
• Form-based list building
• Tagging and segmentation
• Course email sequences

Rate Limits

• 120 requests per minute
• Batch endpoints available

Relevant Skills

• emails
• content-strategy

---

Supporting file: tools/integrations/mailchimp.md

Mailchimp

Email marketing platform for campaigns, automation, and audience management.

Capabilities

Authentication

• Type: API Key or OAuth 2.0
• Header: Authorization: Bearer {api_key} or Authorization: apikey {api_key}
• Base URL: https://{dc}.api.mailchimp.com/3.0/ (dc = datacenter from API key)

Common Agent Operations

List audiences (lists)

GET https://{dc}.api.mailchimp.com/3.0/lists

Get audience members

GET https://{dc}.api.mailchimp.com/3.0/lists/{list_id}/members?count=100

Add subscriber

POST https://{dc}.api.mailchimp.com/3.0/lists/{list_id}/members

{
  "email_address": "user@example.com",
  "status": "subscribed",
  "merge_fields": {
    "FNAME": "John",
    "LNAME": "Doe"
  }
}

Update subscriber

PATCH https://{dc}.api.mailchimp.com/3.0/lists/{list_id}/members/{subscriber_hash}

{
  "merge_fields": {
    "FNAME": "Jane"
  },
  "tags": ["customer", "premium"]
}

Get campaigns

GET https://{dc}.api.mailchimp.com/3.0/campaigns?count=20

Get campaign report

GET https://{dc}.api.mailchimp.com/3.0/reports/{campaign_id}

Create campaign

POST https://{dc}.api.mailchimp.com/3.0/campaigns

{
  "type": "regular",
  "recipients": {
    "list_id": "{list_id}"
  },
  "settings": {
    "subject_line": "Your Subject",
    "from_name": "Your Name",
    "reply_to": "reply@example.com"
  }
}

Send campaign

POST https://{dc}.api.mailchimp.com/3.0/campaigns/{campaign_id}/actions/send

List automations

GET https://{dc}.api.mailchimp.com/3.0/automations

Key Metrics

Campaign Report Fields

• emails_sent - Total sent
• opens - Open count
• unique_opens - Unique opens
• open_rate - Open rate
• clicks - Click count
• click_rate - Click rate
• unsubscribes - Unsubscribe count
• bounces - Bounce count

Subscriber Hash

Calculate subscriber hash for updates:

const hash = md5(email.toLowerCase());

Subscriber Statuses

• subscribed - Active subscriber
• unsubscribed - Unsubscribed
• cleaned - Hard bounce
• pending - Awaiting confirmation
• transactional - Transactional only

When to Use

• Managing email lists and subscribers
• Creating and sending email campaigns
• Setting up email automation
• Analyzing campaign performance
• Segmenting audiences
• A/B testing emails

Rate Limits

• 10 concurrent connections
• 10 requests per second
• Batch endpoints for bulk operations

Relevant Skills

• emails
• analytics
• referrals

---

Supporting file: tools/integrations/nitrosend.md

Nitrosend

AI-native email platform that combines transactional and marketing email in one stack, controlled entirely through AI assistants via MCP. No traditional dashboard required — build sequences, campaigns, and automations by prompting.

Capabilities

Authentication

• Type: API Key
• MCP Setup: Add Nitrosend MCP server to your Claude Code / AI assistant config
• BYO Infrastructure: Optionally bring your own SendGrid, Postmark, SES, or Resend keys
• Get access: Sign up at nitrosend.com — free tier includes 8K emails initially, then 500/month

Pricing

Unlimited contacts on all plans — pay per email sent, not per subscriber.

What Makes It Different

• AI-first: Designed to be controlled by Claude, ChatGPT, Codex, Cursor, Gemini, Windsurf — not a human clicking through a dashboard
• Unified transactional + marketing: Single platform for both, on separate infrastructure
• Automatic optimization: Continuously tests subject lines, send times, and content based on engagement
• Auto-configured deliverability: DKIM, SPF, DMARC, and dedicated IP warmup handled automatically
• Migration-friendly: Import from Mailchimp, Klaviyo, ActiveCampaign, HubSpot

Common Agent Operations (via MCP)

Create an email sequence

"Create a 5-email onboarding sequence for new SaaS trial users.
Email 1: Welcome + what to do first (send immediately)
Email 2: Key feature highlight (day 2)
Email 3: Use case / success story (day 4)
Email 4: Check-in + support offer (day 7)
Email 5: Upgrade prompt (day 12)"

Nitrosend builds the sequence, timing, and sends — no manual setup in a dashboard.

Send a transactional email

"Send a password reset email to user@example.com with a reset link valid for 1 hour."

Create a campaign

"Create a re-engagement campaign for subscribers who haven't opened in 90 days.
Subject line variants: [A] 'We miss you', [B] 'Still interested in [topic]?'
Test both, send winner to remaining list after 4 hours."

Check sequence performance

"Show me open rates, click rates, and unsubscribes for the onboarding sequence."

Import a list

"Import this CSV of 2,000 subscribers from our Mailchimp export."

Deliverability Setup

Nitrosend handles this automatically on signup:

• DKIM signing
• SPF record configuration
• DMARC policy
• Dedicated IP provisioning (Pro+)
• IP warmup schedule

For BYO plan users: bring your own SendGrid, Postmark, SES, or Resend account and Nitrosend routes through your infrastructure.

When to Use

• Building email sequences via AI without touching a dashboard
• Teams already using Claude Code or other AI coding tools as their primary workflow
• Combining transactional (password resets, receipts) and marketing (nurture, campaigns) in one place
• Rapid sequence prototyping — describe the sequence, get it built
• Migrating from Mailchimp/Klaviyo and wanting AI control going forward

When to Use Something Else

• Customer.io — if you need complex event-based branching logic and behavioral triggers
• Klaviyo — if you're in e-commerce and need deep Shopify integration
• Resend — if you need transactional-only and prefer a pure API/code approach
• Kit — if you're a creator or newsletter-first

Relevant Skills

• emails
• onboarding
• churn-prevention
• lead-magnets

---

Supporting file: tools/integrations/resend.md

Resend

Developer-friendly transactional email service with modern API.

Capabilities

Authentication

• Type: API Key
• Header: Authorization: Bearer {api_key}
• Get key: API Keys section in Resend dashboard

CLI

Install

npm install -g resend-cli

Setup

resend login
# or set env var: RESEND_API_KEY=re_xxx

Common commands

# Send a test email
resend emails send --from hello@example.com --to user@example.com --subject "Test" --text "Hello"

# List recent emails
resend emails list

# Get email status
resend emails get <email_id>

# List domains
resend domains list

# Add a domain
resend domains create --name example.com

# Verify a domain
resend domains verify <domain_id>

# List API keys
resend api-keys list

# Create an API key
resend api-keys create --name "Production"

Common Agent Operations

Send email

POST https://api.resend.com/emails

{
  "from": "hello@example.com",
  "to": ["user@example.com"],
  "subject": "Welcome!",
  "html": "<h1>Welcome to our app!</h1>"
}

Send with React template

POST https://api.resend.com/emails

{
  "from": "hello@example.com",
  "to": ["user@example.com"],
  "subject": "Welcome!",
  "react": "WelcomeEmail",
  "props": {
    "name": "John"
  }
}

Get email status

GET https://api.resend.com/emails/{email_id}

List emails

GET https://api.resend.com/emails

Send batch emails

POST https://api.resend.com/emails/batch

[
  {
    "from": "hello@example.com",
    "to": ["user1@example.com"],
    "subject": "Welcome User 1"
  },
  {
    "from": "hello@example.com",
    "to": ["user2@example.com"],
    "subject": "Welcome User 2"
  }
]

List domains

GET https://api.resend.com/domains

Verify domain

POST https://api.resend.com/domains/{domain_id}/verify

Node.js SDK

Install

npm install resend

Usage

import { Resend } from 'resend';

const resend = new Resend('re_xxx');

await resend.emails.send({
  from: 'hello@example.com',
  to: 'user@example.com',
  subject: 'Welcome!',
  html: '<h1>Welcome!</h1>'
});

With React Email

import { WelcomeEmail } from './emails/welcome';

await resend.emails.send({
  from: 'hello@example.com',
  to: 'user@example.com',
  subject: 'Welcome!',
  react: WelcomeEmail({ name: 'John' })
});

Email Statuses

• queued - Email queued for delivery
• sent - Email sent to recipient server
• delivered - Email delivered
• opened - Email opened (if tracking enabled)
• clicked - Link clicked (if tracking enabled)
• bounced - Email bounced
• complained - Marked as spam

Webhook Events

When to Use

• Sending transactional emails
• Welcome emails, password resets
• Receipt and notification emails
• Developer-friendly email integration
• React-based email templates
• Quick CLI testing of email flows without writing code

Rate Limits

• Free: 100 emails/day, 3,000/month
• Pro: 100 emails/second
• Higher limits on scale plans

Relevant Skills

• emails
• onboarding

---

Supporting file: tools/integrations/sendgrid.md

SendGrid

Email delivery platform for transactional and marketing emails.

Capabilities

Authentication

• Type: API Key
• Header: Authorization: Bearer {api_key}
• Get key: Settings > API Keys in SendGrid dashboard

Common Agent Operations

Send email

POST https://api.sendgrid.com/v3/mail/send

Authorization: Bearer {api_key}

{
  "personalizations": [{
    "to": [{"email": "user@example.com"}]
  }],
  "from": {"email": "hello@example.com"},
  "subject": "Welcome!",
  "content": [{
    "type": "text/html",
    "value": "<h1>Welcome!</h1>"
  }]
}

Send with template

POST https://api.sendgrid.com/v3/mail/send

{
  "personalizations": [{
    "to": [{"email": "user@example.com"}],
    "dynamic_template_data": {
      "name": "John",
      "order_id": "12345"
    }
  }],
  "from": {"email": "hello@example.com"},
  "template_id": "d-xxx"
}

Add contact to list

PUT https://api.sendgrid.com/v3/marketing/contacts

{
  "list_ids": ["list-id"],
  "contacts": [{
    "email": "user@example.com",
    "first_name": "John",
    "last_name": "Doe"
  }]
}

Search contacts

POST https://api.sendgrid.com/v3/marketing/contacts/search

{
  "query": "email LIKE 'user@%'"
}

Get email statistics

GET https://api.sendgrid.com/v3/stats?start_date=2024-01-01&end_date=2024-01-31

Authorization: Bearer {api_key}

Get bounces

GET https://api.sendgrid.com/v3/suppression/bounces

Authorization: Bearer {api_key}

Get spam reports

GET https://api.sendgrid.com/v3/suppression/spam_reports

Authorization: Bearer {api_key}

Validate email

POST https://api.sendgrid.com/v3/validations/email

{
  "email": "user@example.com"
}

Webhook Events

Node.js SDK

const sgMail = require('@sendgrid/mail');
sgMail.setApiKey('SG.xxx');

await sgMail.send({
  to: 'user@example.com',
  from: 'hello@example.com',
  subject: 'Welcome!',
  html: '<h1>Welcome!</h1>'
});

When to Use

• Transactional email at scale
• Marketing email campaigns
• Email validation
• Deliverability management

Rate Limits

• Free: 100 emails/day
• Paid: Varies by plan (up to millions/month)

Relevant Skills

• emails
• analytics