Product launch email: the six-block template that gets read

A product launch email is one message to people who already signed up, and it has one job: get them to one page. Six blocks do that job — subject, one-sentence change, one proof, one action, one reason now, one sign-off. Everything else is decoration or a reason the send gets flagged.

This chapter is the template we use when a launch day arrives and the list is small. It covers the copy, the send checks, and the three places the email normally fails. It does not cover the landing page it points to; that is a separate page with its own chapter, linked below.

What a product launch email has to do

A launch email is not a stranger-facing ad. The reader already gave you an address, which means the hard part is recognition, not persuasion: they need to see, in the first two lines, that the thing they signed up for now exists. Treat it as a status update with a door in it.

That framing changes the copy. You do not need to explain the category. You need to say what shipped, what it now makes possible, and where to click. The message that tries to do introductory marketing to an audience that already opted in reads like a newsletter that forgot its own history.

The table is the whole argument. If a block is missing, the email still sends and still looks finished. That is why this failure mode survives: nothing breaks, the click rate just sits near zero and everyone blames the subject line.

The six-block product launch email template

Copy this and fill the brackets. Six blocks, in this order. The whole message should fit on one phone screen before the first scroll; if it does not, cut the paragraph that explains the roadmap.

Subject: [Product] is live: [the one thing it does]
Preview: [What changed for the reader, 6-10 words]

Hi [first name],

[Product] is live today. [One sentence: what it does that the old version did not.]

[One proof: a number, a date, or a named capability the reader can verify.]

[One link: "See what is new" -> the page that shows the change]

[Why now: first 100 accounts, a launch price, or nothing at all.]

[Your name]
[Reply-to address a human reads]

The bracketed reason-now line is optional. If there is no real reason to open today, delete the line instead of inventing a deadline. A countdown that resets is the fastest way to teach a list to ignore the next email.

Two things in that template are non-negotiable. One link, because two links split the click and make the result unreadable. A real reply-to address, because the first launch email reliably produces replies that are worth more than the click count.

Which subject line survives a crowded inbox

A launch subject line works when it names the change, not the excitement. "Billing exports are live" beats "You are going to love this" because the reader can decide from the subject alone whether it matters. The excitement version asks them to open the email to find out what happened.

1. Put the product or the feature in the first three words.
2. Use the reader's noun, not the internal codename.
3. Keep it under about 45 characters so the phone does not cut the useful half.
4. Never start with "Re:" or "Fwd:" unless it is a real reply. Google's sender guidelines name this as a misleading header.
5. Write the preview line as a second sentence, not an echo.

The 45-character figure is a layout rule, not a law, and it depends on the device and the sender name. What is not negotiable is that the subject and preview together must answer "what changed" without opening. If they only answer "something happened", the email is working against itself.

Five checks before you press send

These are delivery checks, not copy checks. They belong to whoever owns the sending domain, and they should be run once per campaign rather than once per launch.

1. Authenticate the domain. Google's Email sender guidelines, checked on 2026-10-31, require every sender to Gmail to set up SPF or DKIM, and require DMARC plus one-click unsubscribe from senders above 5,000 messages a day. The rules took effect on 2024-02-01. Source: Gmail's Email sender guidelines.
2. Send to a seed list first. Two addresses on different providers. Confirm the link resolves, the images load, and the plain-text part is not empty.
3. Check the unsubscribe path. It has to work without a login, and it has to be visible in the body, not only in the footer fine print.
4. Read the spam-rate number. Google's guidance asks senders to stay under 0.10% and warns that 0.30% or higher is a problem. If the previous campaign was near that line, fix the list before adding a launch blast.
5. Send at the hour you can watch it. A launch email that lands at 2 a.m. and breaks its link is discovered by a customer, not by you.

None of this improves the writing. It only decides whether the writing gets a chance to be read. A perfect launch email from an unauthenticated domain is a spam-folder entry with good grammar.

What goes wrong

Three failure modes show up again and again, and each one is cheap to catch before the send.

• Sending the same message to the whole list, including people who unsubscribed from product news but stayed on the blog list. Segmentation is the difference between a launch and a complaint.
• Writing the email as if the reader has been following the build. They have not. The first line has to stand alone.
• Promising a capability that is still behind a waitlist. If the button leads to a "coming soon" page, the next launch email gets read as noise.
• Writing the email after the product page is final. The email should describe what the page actually shows, not what the roadmap says.
• Testing the mobile view before the desktop view. Most of the list will see the phone version first.

What this template cannot tell you

It cannot tell you whether the email will reach the inbox, because placement depends on domain reputation and recipient behaviour that you do not control. It also cannot tell you whether the launch worked: a click is not a signup, and a signup is not revenue. Those are separate measurements with separate windows.

One more limit is worth writing down, because it is the number people reach for first. Google's own documentation says it does not track open rates and that low open rates are not necessarily an accurate indicator of deliverability. So an open-rate chart is a weak judge of this email. Use clicks to the page, and the page's own conversion, as the two numbers that mean something.

A launch email is a door, not a billboard. Its job is to get the right person through it once.

Common questions

How long should a product launch email be?

Short enough that the action is visible without scrolling on a phone. In practice that is under 150 words before the signature, and often under 100 when the product is already familiar to the list.

Should I send a launch email to people who signed up but never opened anything?

Usually not in the first send. A cold segment inside a warm list drags the engagement signal down for everyone. Send to the engaged part first, then decide about the rest with a separate, smaller message.

Is a launch email the same as a press release?

No. A press release is written for journalists and carries a dateline; a launch email is written for people who already opted in and carries one link. If you need the press version, use the release notes guide for the change log and keep the two messages separate.

How many times should I send the same launch email?

Once as the announcement, and at most once as a reminder to people who did not click, with different copy. A third send to the same list is a list-quality decision, not a launch decision.

Where should the email link go?

To the one page that shows the change in context. For a new product that is usually the launch page; for a feature it is the page where the feature lives. The product landing page guide covers what that page needs, and the launch checklist covers the assets around it.

If the email is one step of a larger push, the channel order matters more than the copy. The distribution workflow is where the sequence lives; the email is one door in it, not the whole campaign.