email

Use this skill when the user needs to create email sequences, design onboarding drips, write welcome emails, set up behavioral triggers, improve email engagement, or set up professional branded email. Also use when the user mentions 'drip campaign,' 'welcome email,' 'trial expiry email,' 'email automation,' 'lifecycle emails,' 'branded email,' 'business email,' 'email forwarding,' 'DMARC,' 'SPF,' 'DKIM,' 'hello@ email,' or 'professional email.' Covers branded email setup, email security, lifecycle email programs, subject line formulas, and drip campaign design.

157 stars

Best use case

email is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use this skill when the user needs to create email sequences, design onboarding drips, write welcome emails, set up behavioral triggers, improve email engagement, or set up professional branded email. Also use when the user mentions 'drip campaign,' 'welcome email,' 'trial expiry email,' 'email automation,' 'lifecycle emails,' 'branded email,' 'business email,' 'email forwarding,' 'DMARC,' 'SPF,' 'DKIM,' 'hello@ email,' or 'professional email.' Covers branded email setup, email security, lifecycle email programs, subject line formulas, and drip campaign design.

Teams using email should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/email/SKILL.md --create-dirs "https://raw.githubusercontent.com/whawkinsiv/solo-founder-superpowers/main/skills/email/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/email/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How email Compares

Feature / AgentemailStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Use this skill when the user needs to create email sequences, design onboarding drips, write welcome emails, set up behavioral triggers, improve email engagement, or set up professional branded email. Also use when the user mentions 'drip campaign,' 'welcome email,' 'trial expiry email,' 'email automation,' 'lifecycle emails,' 'branded email,' 'business email,' 'email forwarding,' 'DMARC,' 'SPF,' 'DKIM,' 'hello@ email,' or 'professional email.' Covers branded email setup, email security, lifecycle email programs, subject line formulas, and drip campaign design.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Email & Lifecycle Marketing

Email is the highest-ROI channel in SaaS — when done right. This skill helps you design email sequences that drive activation, retention, and revenue with specific copy you can paste into your email tool.

> **If `ABOUT-ME.md` and/or `MY-ICP.md` exist in the project root**, read them before writing emails. The "from" voice should match ABOUT-ME.md Communication Style — emails should sound like the founder, not a marketing department. The content should speak to MY-ICP.md — their pain, their goals, their language.

## Core Principles

- Every email must answer: "Why should I care about this right now?"
- Behavioral triggers > time-based drips. React to what users DO, not how long they've been around.
- One email, one goal, one CTA. Multiple CTAs = no CTA.
- Subject lines determine whether your email is read. Body copy determines whether it's acted on.
- Unsubscribes are better than spam complaints. Make it easy to leave.

---

## Part 1: Professional Branded Email (Do This First)

Before you send a single marketing email, you need a professional email address. Sending from `yourname@gmail.com` kills credibility. You want `hello@yourdomain.com` — and you can set this up for free in under 30 minutes.

### The Free Setup (Cloudflare + Gmail)

This is the 80/20 approach. You get a branded email address without paying for Google Workspace or managing an email server.

**What you need:**
- A free Gmail account (you probably already have one)
- Your domain on Cloudflare (free plan works — if your domain is elsewhere, transfer DNS to Cloudflare)

**Step 1: Set up Cloudflare Email Routing (receiving mail)**

Cloudflare Email Routing forwards `hello@yourdomain.com` to your personal Gmail — for free.

1. Go to Cloudflare dashboard > your domain > Email > Email Routing
2. Click "Get started" and add a destination address (your Gmail)
3. Verify your Gmail address when Cloudflare sends the confirmation
4. Create a route: `hello@yourdomain.com` → `yourpersonal@gmail.com`
5. Add a catch-all if you want (sends ANY `@yourdomain.com` address to your Gmail)

That's it. Emails to `hello@yourdomain.com` now arrive in your Gmail inbox.

**Step 2: Send AS your branded address from Gmail**

Receiving is only half the equation. You also want to reply FROM `hello@yourdomain.com` so recipients see your branded address, not your personal Gmail.

Option A — **Use a free SMTP relay** (most reliable):
1. Create a free account on [Resend](https://resend.com) or [Brevo](https://brevo.com) (both have free tiers)
2. Verify your domain in their dashboard (they'll give you DNS records to add in Cloudflare)
3. Get your SMTP credentials from the relay service
4. In Gmail: Settings > Accounts > "Send mail as" > Add another email address
5. Enter `hello@yourdomain.com`, uncheck "Treat as alias"
6. Enter the SMTP server, port, username, and password from your relay service
7. Click the verification link Gmail sends to `hello@yourdomain.com` (which forwards to your Gmail)

Option B — **ImprovMX** ($10/year):
- Handles both forwarding AND SMTP sending in one service
- Simpler setup than Option A if you want to skip the relay configuration
- Free tier available (forwarding only; sending requires paid plan)

**Step 3: Set your branded address as the default**

In Gmail: Settings > Accounts > "Send mail as" > make `hello@yourdomain.com` the default. Now every email you send comes from your branded address.

### Email Security: SPF, DKIM, and DMARC

These three DNS records prevent attackers from spoofing your domain (sending fake emails that look like they come from you). They also dramatically improve deliverability — without them, your emails land in spam.

**Why this matters for founders:**
- Without DMARC, anyone can send emails pretending to be `@yourdomain.com`
- Phishing attacks using your domain destroy trust and can get your domain blacklisted
- Gmail, Outlook, and Yahoo now require SPF and DKIM for bulk senders — even small senders benefit

**What to set up (add these as DNS records in Cloudflare):**

| Record | What It Does | Priority |
|--------|-------------|----------|
| **SPF** | Declares which servers can send email for your domain | Must have |
| **DKIM** | Cryptographically signs your emails to prove they're authentic | Must have |
| **DMARC** | Tells receiving servers what to do with emails that fail SPF/DKIM checks | Must have |

Your email forwarding service (Cloudflare) and SMTP relay (Resend/Brevo) will give you the exact DNS records to add. Follow their setup guides — they walk you through it.

**DMARC record to start with** (add as a TXT record for `_dmarc.yourdomain.com`):

```
v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com; pct=100
```

- `p=quarantine` tells receiving servers to spam-folder emails that fail authentication (use `p=reject` once you're confident everything is configured correctly)
- `rua=mailto:...` sends you aggregate reports about who's sending email from your domain

**Verify your setup:** Use [MXToolbox](https://mxtoolbox.com/SuperTool.aspx) or Google's [Check MX](https://toolbox.googleapps.com/apps/checkmx/) to confirm SPF, DKIM, and DMARC are working.

### When to Upgrade to Google Workspace

The free Cloudflare + Gmail setup works great for solo founders. Consider Google Workspace ($7/user/month) when:

- You're hiring and need multiple `@yourdomain.com` accounts
- You want native Google Calendar invites from your branded address
- You need shared drives or team collaboration features
- You want a cleaner separation between personal and business email

Don't pay for Google Workspace on day one. The free setup is professional enough to close deals, send investor updates, and handle customer support.

### Other 80/20 Email Recommendations

- **Create 3-4 aliases** for free: `hello@`, `support@`, `billing@`, `founder@` — all forwarding to the same Gmail. This looks professional and helps you filter/label incoming mail.
- **Set up Gmail filters** to auto-label emails by which alias received them (e.g., label "Support" for anything to `support@`).
- **Add a professional email signature** with your name, title, product name, and website link. Keep it minimal — no logos, no quotes, no social icons.
- **Use "Canned Responses" (Gmail Templates)** for repetitive replies: support answers, sales follow-ups, investor FAQs.
- **Never send marketing emails from your primary domain** — use a subdomain like `mail.yourdomain.com` to protect your main domain's reputation. Your lifecycle email tool handles this separately.

---

## Part 2: Lifecycle Email Marketing

Once you have professional email set up, here's how to build the automated sequences that drive activation, retention, and revenue.

### Workflow

```
Email Sequence Setup:
- [ ] Choose which sequence you need (welcome, trial expiry, re-engagement, etc.)
- [ ] Write each email (subject, preview text, body, CTA)
- [ ] Define triggers and timing
- [ ] Set up in your email tool
- [ ] Test: send to yourself on mobile
- [ ] Track opens, clicks, and conversions
```

---

### Choosing an Email Tool

| Stage | Tool | Why | Cost |
|-------|------|-----|------|
| Pre-revenue | **Resend** or **Loops** | Modern, developer-friendly, good free tier | Free tier |
| 0-$5K MRR | **Customer.io** or **Loops** | Behavioral triggers, event-based sequences | $0-150/mo |
| $5K+ MRR | **Customer.io** or **Intercom** | Advanced segmentation, in-app + email | $150+/mo |

For most bootstrapped founders: **Loops** (simple, modern) or **Resend** (if you want to code your own templates). Graduate to Customer.io when you need complex behavioral triggers.

---

### Welcome Sequence (Most Important)

Triggered on signup. Goal: get users to their aha moment.

**Tell AI:**
```
Write a 5-email welcome sequence for our SaaS:
- Product: [what it does]
- Aha moment: [the first action where users experience value]
- Signup flow: [what happens after signup — onboarding wizard, empty dashboard, etc.]

Email 1 (send immediately): Welcome + single CTA to start [aha action]. No fluff.
  Subject line under 50 chars. Body under 100 words.

Email 2 (Day 1, if user hasn't activated): Quick win tip — how to get value in 2 minutes.
  Include a specific "here's how" with a link directly to the action.

Email 3 (Day 3, if user hasn't activated): Social proof — brief story of how
  someone like them got results. End with CTA to try it.

Email 4 (Day 5, if user hasn't activated): Address the #1 objection or confusion
  that prevents activation.

Email 5 (Day 7, if user hasn't activated): Personal check-in from founder.
  "Reply to this email — I read every one."

Stop the sequence as soon as the user completes [aha action].
For each email: subject line, preview text, body, CTA button text.
```

---

### Trial Expiry Sequence

Triggered 3 days before trial ends. Goal: convert to paid.

**Tell AI:**
```
Write a 4-email trial expiry sequence:
- Product: [what it does]
- Trial length: [14 days / 30 days]
- What they lose on expiry: [specific features or data access]

Email 1 (Day -3): Remind what they'll lose + easy upgrade CTA.
  Mention specific features they've used during trial.

Email 2 (Day -1): Urgency + "here's everything you've built" —
  show them what's at stake.

Email 3 (Day 0): "Your trial ended." What happens next — is their data safe?
  Clear, calm, not pushy.

Email 4 (Day +3): "We saved your data." Final offer — extended trial
  or discount for annual plan.

For each: subject line, preview text, body, CTA. Keep subject lines under 50 chars.
```

---

### Re-engagement Sequence

Triggered after 14+ days inactive. Goal: bring them back.

**Tell AI:**
```
Write a 3-email re-engagement sequence:
- Product: [what it does]
- Trigger: user hasn't logged in for 14+ days

Email 1 (Day 14): "Here's what's new" — 2-3 improvements since they left + CTA.
  Subject: not "We miss you" (too generic). Something specific about what changed.

Email 2 (Day 21): Value reminder — "Here's what [similar user] accomplished this week."
  Show what they're missing out on.

Email 3 (Day 30): Direct ask — "Is [Product] still useful to you?"
  If not, offer to help. If they're done, let them go gracefully.

For each: subject line, preview text, body, CTA.
```

---

### Subject Line Formulas

- **Curiosity:** "The one thing most [role]s get wrong about [topic]"
- **Specificity:** "3 ways to [outcome] in [Product]"
- **Personal:** "Quick question about your [project name]" (use merge tags)
- **Urgency (honest):** "Your trial ends tomorrow"
- **Value:** "Save 2 hours this week with [feature]"

### Rules

- Under 50 characters for mobile preview
- No ALL CAPS. No excessive punctuation.
- Personalization increases opens 20-30%
- Preview text is the second subject line — don't waste it
- A/B test subject lines on every send if volume allows

---

### Transactional Emails

Receipts, password resets, invitations, notifications:

- Send instantly. Users expect these within seconds.
- Clear subject: "Your receipt from [Product]" or "Reset your password"
- Minimal design. These are utility, not marketing.
- Include a plain-text version.
- Don't sneak marketing into transactional emails — legal risk and trust erosion.

---

### Technical Setup

Before sending anything:

```
- [ ] SPF, DKIM, and DMARC configured (deliverability non-negotiable)
- [ ] Sending from a subdomain (e.g., mail.yourproduct.com) to protect main domain reputation
- [ ] List hygiene: remove hard bounces immediately, soft bounces after 3 fails
- [ ] Plain text fallback for every HTML email
- [ ] Mobile-responsive templates (60%+ of emails opened on mobile)
- [ ] Preference center (let users choose email types, not just unsubscribe from all)
- [ ] Track: opens, clicks, unsubscribes, spam complaints, conversions
```

**Tell AI:**
```
Set up email infrastructure for our app:
- Configure SPF, DKIM, and DMARC for [our domain]
- Set up a sending subdomain: mail.[domain].com
- Create mobile-responsive email templates for:
  1. Transactional (receipt, password reset, invite)
  2. Marketing (sequence emails, announcements)
- Add unsubscribe link and email preference center
- Verify deliverability with a test send
```

---

### Common Mistakes

| Mistake | Fix |
|---------|-----|
| Time-based drips only ("Day 3, Day 5") | Use behavioral triggers: "hasn't completed X" |
| Multiple CTAs in one email | One email, one goal, one button |
| "We miss you" as a subject line | Be specific: "3 new features since you left" |
| No plain-text version | Always include one. Some clients strip HTML. |
| Sending from noreply@ | Use a real address. Let people reply. |
| No tracking | Track opens, clicks, and conversions per email |
| Marketing in transactional emails | Keep them separate. Trust > short-term engagement. |

---

### Related Skills

- **growth** — Activation strategies that email sequences support
- **conversion** — Optimize the full signup-to-paid funnel
- **analytics** — Track email-driven conversions and attribution
- **copywriting** — Write stronger subject lines and email body copy

Related Skills

validate

157
from whawkinsiv/solo-founder-superpowers

Use this skill when the user needs to validate a business idea, test demand before building, run a smoke test, create an MVP experiment, or decide whether an idea is worth pursuing. Covers demand validation, smoke tests, fake-door tests, landing page experiments, and go/no-go decision frameworks for bootstrapped founders.

ux-design

157
from whawkinsiv/solo-founder-superpowers

Use this skill when flows feel clunky, users are confused, navigation needs planning, onboarding needs design, or accessibility needs implementation. Covers information architecture, user flows, interaction patterns, progressive disclosure, and error handling UX.

ui-patterns

157
from whawkinsiv/solo-founder-superpowers

Use this skill when the user needs to build a dashboard, settings page, data table, or any page layout. Also use when choosing component libraries, implementing responsive design, dark mode, or handling UI states (loading, empty, error). Covers component selection, page composition, and responsive implementation.

translate

157
from whawkinsiv/solo-founder-superpowers

Use this skill when the user is a domain expert (lawyer, doctor, contractor, accountant, etc.) who wants to turn their professional knowledge into a software product. Also use when the user says 'I have an idea for my industry,' 'I know this problem exists,' 'I want to build something for [profession],' or is struggling to describe what they want the software to do. Helps identify which professional pain is worth building for, then translates it into requirements AI tools can execute.

test

157
from whawkinsiv/solo-founder-superpowers

Use this skill when the user needs to test features before deployment, create test scenarios, find edge cases, or verify bug fixes. Covers manual testing workflows, cross-browser testing, edge case identification, and testing checklists for non-technical founders.

technical-seo

157
from whawkinsiv/solo-founder-superpowers

Use this skill to implement technical SEO optimizations in code — meta tags, schema markup, Core Web Vitals, crawlability, robots.txt, sitemaps, and GEO (Generative Engine Optimization) for AI search engines. This is the implementation skill — for strategy see seo, for content writing see seo-content, for auditing see seo-audit.

support

157
from whawkinsiv/solo-founder-superpowers

Use this skill when the user needs to create help docs, build a knowledge base, set up self-serve support, or reduce support tickets. Covers documentation strategy, help center structure, support tone, and scaling support without hiring.

social-media

157
from whawkinsiv/solo-founder-superpowers

Use this skill when the user needs to grow a social media presence, create content for Twitter/X, LinkedIn, or other platforms, build a founder brand, or use social media as a distribution channel. Covers platform strategy, content frameworks, posting cadence, and audience building for bootstrapped SaaS founders.

seo

157
from whawkinsiv/solo-founder-superpowers

Use this skill when the user needs to plan SEO content, do keyword research, build a content calendar, map search intent to page types, or create an internal linking strategy. Also use when the user says 'how do I rank higher,' 'what should I write about for SEO,' 'SEO plan,' 'what keywords should I target,' or 'how to get organic traffic.' This is the strategy and planning skill — for writing content see seo-content, for technical implementation see technical-seo, for auditing see seo-audit.

seo-content

157
from whawkinsiv/solo-founder-superpowers

Use this skill when the user needs to write SEO content — blog posts, landing pages, feature pages, comparison pages, how-to guides, or any content meant to rank in search and get cited by AI. Covers content briefs, humanized writing that avoids AI detection, SERP feature targeting, entity optimization, content refresh, and quality self-checks. This is the writing skill — for strategy see seo, for technical implementation see technical-seo, for auditing see seo-audit.

seo-audit

157
from whawkinsiv/solo-founder-superpowers

Audit a codebase for SEO and AI-answer visibility, then produce a prioritized fix-it plan. Use this skill whenever a user says things like "audit my SEO", "check my site for search visibility", "how do I rank better", "optimize for Google", "optimize for AI answers", "SEO review", "GEO audit", "run the SEO agent", or anything about improving organic traffic or search rankings. Also trigger when someone mentions wanting visibility in AI-generated answers (ChatGPT, Gemini, Perplexity, Claude). Works on any web project — static sites, Next.js, Astro, Hugo, WordPress themes, or anything that outputs HTML.

secure

157
from whawkinsiv/solo-founder-superpowers

Use this skill when the user needs to secure their SaaS app, implement authentication, protect user data, secure APIs, or check for vulnerabilities. Also use when the user says 'is my app secure,' 'security check,' 'I'm worried about hackers,' 'how do I protect user data,' or 'security before launch.' Covers OWASP Top 10, auth best practices, data protection, and security checklists for apps built with AI tools.