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.
What this skill does
# 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 `[email protected]` kills credibility. You want `[email protected]` — 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 `[email protected]` 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: `[email protected]` → `[email protected]` 5. Add a catch-all if you want (sends ANY `@yourdomain.com` address to your Gmail) That's it. Emails to `[email protected]` 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 `[email protected]` 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 `[email protected]`, 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 `[email protected]` (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 `[email protected]` 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:[email protected]; 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
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".