Email examples
Real email examples organized by moment. Every example includes a subject line, why it works, what to copy, and what to avoid.
Startup Email Examples: From Waitlist to Winback
Nine email types every startup sends, with what to copy and what to avoid.
Onboarding Email Examples (And Why Each One Exists)
Eight onboarding emails plotted on the activation path, with subject lines, why they work, and what to skip.
Product Launch Email Examples (By Launch Type)
Launch emails for waitlist openings, beta invites, public launches, feature releases, and re-launches.
Welcome Email Examples (By Signup Context)
Eight welcome emails grouped by how the user signed up. Subject lines, what to copy, and what to skip.
B2B Email Marketing Examples (For Startups)
Eight B2B emails covering BDR sequences, account-based nudges, lifecycle, and renewal. Startup-scale examples, not enterprise playbooks.
SaaS Email Marketing Examples
Eight emails SaaS startups send: trial, activation, expansion, churn save, billing, and product updates.
Product Update Email Examples for SaaS
SaaS product update examples for feature releases, workflow changes, security updates, billing changes, and expansion moments.
Customer Winback Email Examples
Winback email examples for inactive users, cancelled accounts, price objections, and dormant product teams.
Agent Email Workflow Examples
Workflow examples for inbound routing, outbound replies, approval gates, and agent retry loops.
Inbound Email Agent Examples
Inbound email agent examples for support triage, lead capture, invoice parsing, and mailbox safety.
Retention Email Examples
Retention email examples for usage drops, missed value, milestones, expiring benefits, and renewal risk.
Onboarding Email Sequence Examples
Three full sequences plotted across the activation timeline. Triggers, timing, and what to drop if you must.
Lifecycle Email Marketing Examples
Eight lifecycle emails covering activation, retention, expansion, and winback, each with the trigger noted.
reading this as developers picking email infrastructure
The question here is which one a backend engineer would rather operate. That means SDK depth in the language already in use, whether a retry can safely be replayed, how much the event log tells you when a customer says the email never arrived, and whether the pricing curve stays sane as volume grows.
Applied to these email examples, that means weighing developer experience, SDK breadth, idempotency keys, and operating track record ahead of the rest, against password resets, receipts, and magic links shipped from application code.