jonathimer/devmarketing-skills/developer-email-sequences

Developer Email Sequences

This skill helps you craft email sequences that developers actually read. No spam, no fluff — just useful content delivered at the right frequency.

Before You Start

1. Load your developer audience context:

• Check if .agents/developer-audience-context.md exists
• If not, run the developer-audience-context skill first
• Understanding your developers' tech stack, pain points, and communication preferences is essential for effective email

1. Audit existing emails:

• What emails are you currently sending?
• What are open rates, click rates, unsubscribe rates?
• Any feedback from developers about your emails?

The Developer Email Reality

Developers are ruthless with email:

Golden rule: Every email must provide immediate value or solve a problem.

Email Sequence Types

1. Onboarding Sequence

Goal: Get developers to their first "Hello World" moment.

Timing:

• Email 1: Immediately after signup
• Email 2: 24 hours (if no activation)
• Email 3: 3 days (if no activation)
• Email 4: 7 days (if no activation)
• STOP if they activate

Structure:

Template: Welcome Email

Subject: Your API key is ready
 
Hey [NAME],
 
Your API key: [KEY]
 
Quickstart (2 minutes):
[LINK TO QUICKSTART]
 
That's it. Hit reply if you get stuck.
 
— [SENDER NAME]

Template: First Nudge

Subject: Quick question about your setup
 
Hey [NAME],
 
Noticed you haven't made your first API call yet.
 
Where'd you get stuck?
 
[ ] Didn't have time yet
[ ] Confused about authentication
[ ] Can't find the right SDK
[ ] Something else
 
Just reply — I read every response.
 
— [SENDER NAME]

2. Activation Sequence

Goal: Turn first-time users into regular users.

Trigger: After first successful API call or integration.

Timing:

• Email 1: Immediately after first success
• Email 2: 3 days later
• Email 3: 7 days later
• Email 4: 14 days later

Structure:

3. Changelog / Product Update Emails

Goal: Keep developers informed without overwhelming them.

Frequency: Weekly digest or per-release (never more than 2x/week).

Structure:

Subject: [Product] v2.3 — Faster webhooks, TypeScript 5 support
 
What's new:
 
## Breaking changes (read first)
-Webhook signature algorithm changed (migration guide)
 
## New
-TypeScript 5.0 support
-Batch API for bulk operations
 
## Improved
-Webhook delivery 3x faster
-Better error messages for auth failures
 
## Fixed
-Memory leak in long-running connections
 
Full changelog: [LINK]
 
---
 
Need help upgrading? Reply or join #support in Discord.

Rules:

• Breaking changes ALWAYS at the top
• Code examples for new features
• Link to full changelog, don't dump everything in email
• No marketing fluff — just facts

4. Re-engagement Sequence

Goal: Win back developers who've gone quiet.

Trigger: No activity for 30/60/90 days.

Timing:

• Email 1: Day 30 of inactivity
• Email 2: Day 45
• Email 3: Day 60
• Email 4: Day 90 (sunset warning)

Structure:

Template: Check-in

Subject: Did something break?
 
Hey [NAME],
 
Haven't seen you in a while.
 
Quick check:
 
- Did you run into a problem? (Reply and I'll help)
- Building something else? (Totally fine)
- Found a better solution? (Genuinely curious what)
 
No hard feelings either way — just want to make sure
you're not stuck on something we can fix.
 
— [SENDER NAME]

Template: Sunset Warning

Subject: Pausing your account in 14 days
 
Hey [NAME],
 
Your [PRODUCT] account has been inactive for 90 days.
 
To keep things tidy, we'll pause your account on [DATE].
 
What this means:
- Your API keys will stop working
- Your data stays safe (we don't delete anything)
- You can reactivate anytime by logging in
 
If you're still using [PRODUCT], just log in once to keep
your account active: [LOGIN LINK]
 
No action needed if you've moved on.
 
— [SENDER NAME]

Frequency Guidelines

The unsubscribe test: If a developer would feel relieved to unsubscribe from this email type, you're sending too many.

Technical Content in Emails

Code Snippets

Do:

• Keep snippets under 10 lines
• Use syntax highlighting (if HTML email)
• Test that code actually works
• Include language/framework version

Don't:

• Assume a specific environment
• Include secrets or realistic-looking API keys
• Use outdated syntax

Example: Good code snippet

# Python 3.8+
import yourapi
 
client = yourapi.Client("your-api-key")
result = client.analyze("Hello, world!")
print(result.sentiment)  # "positive"

API Updates

When announcing API changes:

## New endpoint: POST /v2/batch
 
Process up to 100 items in a single request.
 

client.batch([ {"text": "First item"}, {"text": "Second item"}, # ... up to 100 items ])

 
Rate limit: 10 batch requests/minute
Docs: [LINK]

Transactional vs Marketing Emails

Examples:

Gray area: Onboarding emails can be transactional (user signed up) but should still have easy unsubscribe.

Measuring Email Effectiveness

Metrics That Matter

What to Track

1. Onboarding sequence: % who activate within 7 days
2. Changelog emails: Click-through to docs/release notes
3. Re-engagement: % who return to product
4. All emails: Unsubscribe rate by email type

A/B Testing Priorities

1. Subject lines (biggest impact)
2. Send time
3. Email length
4. Plain text vs HTML
5. CTA wording

Unsubscribe Handling

Preference Center

Let developers control what they get:

Email Preferences for [EMAIL]
 
[ ] Product updates (new features, changelog)
[ ] Security alerts (always recommended)
[ ] Community news (events, meetups)
[ ] Tips and tutorials
 
Or: Unsubscribe from all marketing emails
(You'll still receive transactional emails like receipts and security alerts)

Graceful Unsubscribe

When someone unsubscribes, confirm simply:

Subject: You're unsubscribed
 
You've been removed from [EMAIL TYPE] emails.
 
You'll still receive:
- Security alerts
- Payment receipts
- Usage notifications
 
Changed your mind? Update preferences: [LINK]

Re-subscribe Flow

After unsubscribe, don't:

• Send "We miss you" emails
• Ask them to reconsider
• Add them back to other lists

Do:

• Make it easy to re-subscribe from your site
• Remember their preference if they return

Email Templates Library

Account Security

Subject: Action required: Unusual login detected
 
We detected a login from a new location:
 
Location: [CITY, COUNTRY]
Device: [BROWSER/OS]
Time: [TIMESTAMP]
 
If this was you, no action needed.
 
If this wasn't you:
1. Change your password immediately: [LINK]
2. Rotate your API keys: [LINK]
3. Review recent API activity: [LINK]
 
Questions? Reply to this email.
 
— [PRODUCT] Security Team

Usage Alert

Subject: Heads up: You've used 80% of your API quota
 
Your usage this month: [CURRENT] / [LIMIT] requests
 
At your current rate, you'll hit your limit around [DATE].
 
Options:
- Upgrade your plan: [LINK]
- Optimize your usage: [DOCS LINK]
- Wait for reset on [RESET DATE]
 
We'll send another alert at 95%.
 
— [PRODUCT]

Payment Failed

Subject: Payment failed — update your card to avoid interruption
 
We couldn't charge your card ending in [LAST4].
 
Update your payment method: [LINK]
 
We'll retry in 3 days. If unsuccessful, your account will be
downgraded to the free tier on [DATE].
 
Your API will continue working until then.
 
Questions about billing? Reply to this email.
 
— [PRODUCT]

Common Mistakes

Tools

Related Skills

• developer-audience-context — Foundation for knowing what content resonates
• developer-churn — Re-engagement strategies for at-risk users
• changelog-updates — Structuring product updates
• developer-onboarding — Full onboarding strategy beyond just email