How many emails should a product launch sequence have?

Six jobs, about two weeks, and a stop rule.

Why is one announcement email not enough?

Most B2B launches get one email. It goes out on launch day, a fraction of the list reads it, and the team moves on. The problem is not the email. It is the assumption that one message, on one day, reaches the people who would care. Many of them are travelling, in a quarter close, or simply not thinking about your category that morning. A second email three days later is not a repeat. It is a second chance to be read, with a different angle.

The other reason is that one email has to do every job at once: announce, explain, prove and ask. That makes it long and vague. A sequence splits those jobs across several short emails, each one easy to read in under a minute. This is the same logic behind any B2B email campaign: one message, one job, one clear next step.

What are the six jobs of a launch sequence?

The number of emails follows from the number of jobs. Six jobs need six emails. If one of the jobs does not apply (a feature so simple it needs no proof, for example), drop that email rather than pad it.

1. Announce. What is new, who it is for, one link.
2. Explain the problem. The situation the reader is in today, in their words, before the product appears.
3. Show it. A short walkthrough: one screenshot or a 60-second recording, one use case.
4. Prove it. A customer example, a before and after, or a live demo invitation.
5. Last call. The deadline, if there is one: launch pricing, a webinar date, limited onboarding slots. If there is no real deadline, do not invent one.
6. Follow up with the quiet ones. A short, plain email to people who did not act, asking what would make it relevant.

The day-by-day plan

Here is the plan for a full product launch to an existing list. Subject lines are examples, written for a fictional scheduling product sold to operations teams. The full copy for each email is on the launch sequence template page.

Two things to notice. The gaps grow slightly toward the end, so the last call and the follow-up do not land back to back. And the audience shrinks with every email, because the stop rule below removes people who act. The only people who see all six are the ones who never responded.

Who should get which email?

A launch list is really three lists. Treat them differently from email two onward.

Customers already know the problem, so the "explain the problem" email reads as condescending to them. Skip it. Quiet subscribers are the risky group: sending six emails to people who stopped reading months ago is how a launch turns into a spam complaint spike. Give them one email, and if they do not respond, move them into a re-engagement sequence instead of the launch.

What changes for a feature, a product, or a pricing change?

The six-job plan is the full version. Most launches are smaller. Match the number of emails to how much the reader has to understand and how much the change affects them.

Pricing changes are the one case where the sequence should start before the change, not on the day. People need time to read, ask questions and adjust budgets. The tone is explanatory, the ask is small ("reply if you have questions"), and the last email is a confirmation, not a push.

When should the sequence stop for someone?

The stop rule is the part most teams skip, and it is what makes a six-email sequence feel reasonable rather than pushy. Define one or two actions that mean "this person has done what we asked", and remove them from the rest of the sequence the moment they do it. For a launch that usually means booked a demo, started a trial, upgraded, or replied.

Every mainstream email platform can do this, under different names. HubSpot calls it a workflow goal: its help documentation says a contact who meets the goal criteria is unenrolled from the workflow automatically, before the next action runs. Kit (formerly ConvertKit) uses an event step in a visual automation: when a purchase event fires, the subscriber is pulled out of the sales sequence and gets no more of its emails. Mailchimp, ActiveCampaign and Customer.io have equivalents. These are vendor descriptions of their own features, not independent findings, but the behaviour is standard.

Suppression goes one step further. Before the sequence starts, exclude people who should never be in it: anyone in an active sales conversation (the rep should tell them, not a campaign), anyone who unsubscribed from marketing, and anyone who bounced. Google's sender guidelines ask bulk senders to automatically unsubscribe recipients with multiple bounced messages, and to consider unsubscribing people who do not open or read at all. A launch is not the moment to test that advice.

In practice the stop rule removes a meaningful share of the list by email three, which is exactly what you want. The people still receiving email five are the ones who have not decided, and a clear deadline is useful to them, not annoying.

What should you measure?

Measure the actions you defined in the stop rule: replies, demos booked, trials started, upgrades. Those are the only numbers that tell you whether the launch worked. Clicks are a useful early signal. Opens are not.

Opens mislead for a structural reason. Apple's Mail Privacy Protection, on by default in Apple Mail, downloads remote content in the background and hides the reader's IP address, with the stated aim of preventing senders from learning about the reader's mail activity. That means a tracking pixel can load whether or not a person read the email. Google's guidelines point the same way: the reputation numbers it asks you to watch are spam rate and complaints, not opens. Track replies and bookings per email, and read the sequence as a whole rather than judging each email on its own.

After the launch, compare the three segments. If customers upgraded but prospects did not book, the product email worked and the proof email did not. That is the kind of finding you can act on next time. A launch is different from an event invitation sequence, where the deadline is fixed by the calendar, but the measurement logic is the same: count the action, not the open.

Before you send email one: a checklist

Run through this once, the day before launch. Most launch mistakes are list and setup mistakes, not copy mistakes.

If you are unsure whether what you are planning is a launch sequence, a nurture sequence or a newsletter issue, the comparison of the three email formats draws the line. A launch is a campaign: a fixed set of emails, a chosen segment, a start date and a stop rule.

Need help with this? See how Sawa handles launch and nurture campaigns, or book an intro call.