Product Launch Email Sequence: 5 Emails, Examples and Best Practices
Why a launch needs an email sequence
Social posts and platform listings are rented attention. Your email list is the one audience you can reach directly, on your own schedule. A launch gives you a natural reason to write to that list several times in a short window, and a sequence turns a single announcement into a conversation: tease, announce, remind, show proof, ask for feedback.
This guide gives you the sequence as a table, one short example email per stage that you can adapt, and the practical rules that decide whether those emails arrive and get read. It builds on our product launch checklist, where the email to your list is one line item; here we expand that line into a full plan. For the bigger picture of timing and channels, see our product launch strategy guide.
One note on numbers: the requirements below come from Google, Yahoo, Apple, Mailchimp and the German UWG text, listed under sources. We do not quote open-rate or conversion benchmarks, because they vary too much by list and industry to be useful for your decision.
The five-email launch sequence at a glance
| Timing | Goal | Subject line examples | CTA | |
|---|---|---|---|---|
| 1. Pre-launch teaser | 5 to 7 days before launch | Set the date, build anticipation, ask for a small commitment | "[Product] launches on [date]" / "Something we have been building for [audience]" | Reply with your biggest [problem], or save the date |
| 2. Launch-day announcement | Launch day, once the product is live | Drive the first visits and sign-ups | "[Product] is live" / "You can try [Product] today" | One button: try [Product] |
| 3. Reminder | 1 to 2 days after launch, to people who did not click | Catch people who missed the first email | "In case you missed it: [Product]" / "Quick question about [problem]" | Same link, a different angle |
| 4. Last chance or social proof | 3 to 5 days after launch | Add real proof, close any launch offer | "What early users say about [Product]" / "[Offer] ends [day]" | Try it, or read the first reviews |
| 5. Post-launch feedback and onboarding | 1 to 7 days after a person signs up | Get them to the first useful moment, collect feedback | "Your first step in [Product]" / "What almost stopped you from trying us?" | Complete one action, or reply with an answer |
The timings are starting points, not rules. A tiny list can compress the sequence into a week; a larger list that you have nurtured for months can stretch it. The important part is the order: each email has one job and one call to action.
Email 1: the pre-launch teaser
Send this to your waitlist, newsletter and beta testers about a week before the date. It confirms they will hear from you again and gives you a first sign of who is paying attention. Keep it short and personal, and ask a question you can actually learn from.
Subject: [Product] launches on [date]
Hi [First name],
You joined the waitlist for [Product], so you should hear it from us first: we launch on [date].
[Product] helps [specific person] do [specific thing] without [specific pain]. We built it because [one honest sentence about why].
One question before launch day: what is the most annoying part of [problem] for you today? Just hit reply. I read every answer, and I will use them to decide what to show first.
Thanks for being early,
[Name], [Product]
Email 2: the launch-day announcement
This is the email most founders write, and most write it too long. One purpose, one button. Send it only after you have checked that the sign-up path works on mobile and desktop; our checklist covers that test.
Subject: [Product] is live
Hi [First name],
[Product] is live today. It helps [specific person] do [specific thing] in [short time or few steps].
Here is what you can do right now:
- [Key capability 1]
- [Key capability 2]
- [Key capability 3]
Try [Product] now: [link]
If something does not work or feels confusing, reply to this email. I am online all day and will answer.
[Name]
If you also launch on a discovery platform, you can add one line asking people to leave honest feedback there. Do not ask for votes where the platform forbids it. The guide to launching a startup explains how the email fits with the other channels.
Email 3: the reminder
Most people will not act on the first email. Send a short follow-up one or two days later, ideally only to those who did not click. Mailchimp's guidance points the same way: because emails to Apple Mail users with Mail Privacy Protection appear opened, a resend to non-openers can miss them, so Mailchimp suggests resending to people who did not click.
Subject: Quick question about [problem]
Hi [First name],
Yesterday we launched [Product]. If you are like most people on this list, you are busy, so here is the short version:
[One sentence describing the result a user gets.]
It takes about [time] to set up. Here is the link: [link].
If [Product] is not for you, no hard feelings. Tell me what you were hoping for and I will point you somewhere better if I can.
[Name]
Email 4: social proof or last chance
By now you should have something real to show: a comment from an early user, a screenshot of a result, a first review, a number from your beta. Use only what is true and what the person agreed to share. If you run a launch offer, this is also where you state its end date plainly, without invented urgency.
Subject: What early users say about [Product]
Hi [First name],
In the first [days] since launch, [number] people have tried [Product]. Here is what a few of them told us:
"[Short real quote.]" ([First name], [role])
"[Short real quote.]" ([First name], [role])
If you want to see for yourself, start here: [link]. [Optional: The launch offer of [offer] ends on [date].]
[Name]
Early-user feedback is also the best material for this email, which is why it pays to work closely with your first adopters. Our article on finding and keeping early adopters goes deeper.
Email 5: post-launch onboarding and feedback
This one is different: it goes to people who signed up, not to the whole list, and it is triggered by their behavior, not by the calendar. Send it a day after sign-up, and again a few days later if they have not reached the first useful moment. Ask for one action, then ask one honest question.
Subject: Your first step in [Product]
Hi [First name],
Thanks for signing up for [Product]. The fastest way to see value is to [one specific action]. It takes about [time]: do it here: [link].
And one question, if you have a minute: what almost stopped you from trying us? Reply with a sentence or two. Your answer goes straight to me.
[Name]
Group the replies into themes after a week or two. Three people asking for the same thing is a signal; one loud request is an anecdote. Then tell the people who asked what you changed.
Best practices that apply to every email
Segment, even if only roughly
You do not need a complex setup. Three groups already change the result: people who clicked the launch email, people who did not, and people who signed up. The first group gets a different follow-up than the second, and the third should not receive the launch announcements again at all. Beta testers and personal contacts can get a more personal version of email 1. If your tool allows it, tag each person by how they joined, so you can see which source produces engaged readers.
Write subject lines for people, not for filters
- State the thing: "[Product] is live" beats a clever riddle.
- Keep it short enough to read on a phone, and put the key words first.
- Avoid ALL CAPS, strings of exclamation marks and invented urgency. They read as spam to people and are poor signals for filters.
- Use a real sender name, ideally a person at the company, and a reply-to address that is monitored.
- Test two variants on a larger list; on a small list, pick the clearer one and move on.
Plain text or HTML
For a founder-led launch, a plain-looking email with one link often works well: it looks like a message from a person, loads fast and has fewer ways to fail. A light HTML layout with a logo and a single button is also fine. What matters is the same in both: one purpose, one call to action, readable on a phone, and a working unsubscribe link. If your messages use HTML, Google asks that they follow HTML standards.
Deliverability basics
The best email is worthless if it lands in spam. Since February 2024, Gmail and Yahoo have made authentication and easy unsubscribing a requirement for large senders, and following the same rules is sensible for small ones too.
- SPF and DKIM: Google requires senders of more than 5,000 messages per day to set up SPF and DKIM for their domain. Yahoo requires both from bulk senders and at least one from all senders.
- DMARC: Google requires senders of more than 5,000 messages per day to publish a DMARC record, and says the policy can be set to "none." Yahoo asks bulk senders for a policy of at least p=none, with DMARC passing. For bulk senders, the domain in your From address must align with the SPF or DKIM domain.
- One-click unsubscribe: Google says senders of more than 5,000 messages per day must support one-click unsubscribe for marketing and subscribed messages and include a clearly visible unsubscribe link in the body. Yahoo asks bulk senders for a functioning List-Unsubscribe header and says to honor unsubscribes within two days. Most email platforms handle the header for you; check that yours does.
- Spam complaints: Both providers set a spam-rate limit for all senders: Google asks you to stay below 0.10% in Postmaster Tools and never reach 0.30%; Yahoo says below 0.3%.
- DNS and transport: Sending domains or IPs need valid forward and reverse DNS records, and Google asks for a TLS connection.
Google's stricter bulk rules apply to senders of more than 5,000 messages per day to Gmail accounts, while its basic rules apply to every sender; Yahoo's page does not define a volume for "bulk." Most launch lists are far smaller, but authentication and a visible unsubscribe link cost little and protect your sender reputation. Warm up by sending to your most engaged people first, and remove addresses that bounce.
Consent: who may you email?
Email only people who asked to hear from you. A waitlist form, a newsletter sign-up or a beta registration with a clear note on what they will receive are the cleanest sources. Do not scrape addresses, import purchased lists or add contacts from a business card pile without asking.
In Germany, section 7(2) no. 2 of the UWG treats advertising by electronic mail as an unacceptable nuisance unless the recipient has given prior express consent. Section 7(3) allows a narrow exception for existing customers, and only if all four conditions are met: you received the address in connection with a sale, you use it only for advertising your own similar products, the customer has not objected, and the customer is clearly told at collection and with every use that they can object at any time. Other EU countries and the US have their own rules, and the details depend on your situation. This is general information, not legal advice; check with a lawyer if you are unsure.
Metrics: what to track
Open rates used to be the headline number. They no longer are. Apple states that in the Mail app, Mail Privacy Protection stops senders from using invisible pixels to collect information about the user, and helps users prevent senders from knowing when they open an email. Mailchimp explains the effect: opens are recorded even if the person never read the message, so open rates look inflated, and clicks and purchases are stronger signs of engagement. Treat opens as a rough hint at most.
- Click rate: the share of recipients who clicked a link. Use a tagged link per email so you can see which message brought visits.
- Replies: the strongest signal on a small list. Count them, read them, answer them.
- Conversions: sign-ups or activated users that trace back to the sequence. This is the number that tells you whether the sequence worked.
- Unsubscribes and spam complaints: a spike after one email means the message or audience was wrong. Complaints matter most for deliverability.
- Bounces: remove them promptly; Google advises reducing sending volume if messages start bouncing.
Base automations on clicks or actions instead of opens. For example, send the reminder to people who did not click, not to people who "did not open."
A simple schedule you can copy
- T minus 7 days: teaser to the waitlist, with a question to reply to.
- T minus 1 day: optional "tomorrow" note to the most engaged segment.
- Launch day: announcement, one button, sent once the product is live.
- T plus 1 to 2 days: reminder to non-clickers, from a different angle.
- T plus 3 to 5 days: social proof or last-chance email.
- Day after each sign-up: onboarding email with one action and one question.
- T plus 14 days: short wrap-up to the whole list, with what you learned and what you changed.
Beyond your own list, discovery sites bring slower but steadier traffic. You can browse products on MyStartup24 to see how other makers present theirs; listing is free.
Conclusion
A launch email sequence does not need to be clever. It needs to reach the inbox, say one clear thing per message, and respect the reader's choice to be there. Set up authentication, collect consent honestly, write five short emails with one call to action each, and measure clicks, replies and sign-ups instead of opens. Then use the answers you get to improve the product, because that is what keeps people around after launch day.
Frequently asked questions
How many emails should a product launch sequence have? +
Five is a sensible starting point: a pre-launch teaser, the launch-day announcement, a short reminder, a last-chance or social proof email, and a post-launch feedback email. Small lists can merge the reminder and the social proof email. More emails only help if each one has a different reason to exist.
Should I send launch emails as plain text or HTML? +
For a small founder list, a short plain-looking email with one link usually fits best, because it reads like a message from a person. A light HTML layout with a logo and one button is also fine. Whichever you choose, keep one clear call to action and include a visible unsubscribe link.
Can I email people I met at events or found on LinkedIn about my launch? +
Be careful. In Germany, section 7 of the UWG treats email advertising as an unacceptable nuisance without the recipient's prior express consent, with a narrow exception for existing customers. Collect opt-ins through your own waitlist or sign-up form. This is general information, not legal advice.
Do I need SPF, DKIM and DMARC for a small launch list? +
Yes. Google and Yahoo require SPF or DKIM from every sender, and SPF, DKIM and DMARC from bulk senders (at Google, more than 5,000 messages a day to Gmail accounts). Google says unauthenticated messages might be marked as spam or rejected.
Are open rates still useful? +
Only as a rough signal. Apple Mail Privacy Protection helps users prevent senders from knowing when they open an email, and Mailchimp says it inflates open metrics. Clicks, replies and sign-ups are more reliable measures of whether the sequence works.
When should I send the launch-day email? +
Send it when the product is live and the link works, at a time your audience is likely to read email. Test your own list: if you have time, compare two send times on a previous campaign rather than copying a generic best-time chart.
Sources
- Email sender guidelines — Google Workspace Admin Help
- Sender best practices — Yahoo Sender Hub
- Apple advances its privacy leadership with iOS 15, iPadOS 15, macOS Monterey, and watchOS 8 — Apple Newsroom
- Apple Mail Privacy Protection FAQ — Mailchimp
- Section 7 UWG: Unzumutbare Belästigungen — Gesetze im Internet (German Federal Ministry of Justice)