Lifecycle email for signups you already have

Lifecycle email is email you send after someone creates an account, based on what they have done since. The trigger is always something that actually happened: they signed up, they stopped partway through setup, they used a particular feature, they cancelled, or their trial ended. The goal is to get them using the product. Whether they open the email is not the goal.

Most articles about “lifecycle marketing” are written for online stores. They describe a journey that starts before anyone has bought anything, and they lean on abandoned carts, reminders to reorder, and discount codes to bring people back. That works well for stores. It is the wrong model for a product people sign up for, because your customers have accounts and leave a trail of activity inside the product you can write from instead.

One caveat before you start. If almost nobody is signing up yet, this is not where your time should go. Lifecycle email does not bring you new users. It gets more out of the ones you already paid to acquire.

Nearly every worthwhile email you can send to your existing signups falls into one of four jobs. Which one applies to a given person depends on where they actually stopped, not on how many days it has been since they signed up.

Do not collapse all four into a single sequence that fires on day 1, day 3, and day 7 and finishes with “we miss you.” People can tell when an email went out on a timer rather than because of something they did, and they stop reading the ones that follow.

Start with whichever group has the most people in it who have never paid you anything.

For most self-serve products that is the people who signed up, never activated, and never got a single email. They already showed interest by creating an account, and then nobody followed up. One specific email about the step they stopped on will do more than a general welcome tour.

If none of these groups has ever been emailed, work through them in this order:

1. People who signed up and never activated
2. People who are part-way through setup and stalled
3. People who went quiet but still have an open account
4. People who have already left

That order is a default, not a rule. If nearly everyone who signs up activates but a lot of people cancel later, start with the people who cancelled. The four jobs stay the same either way. Only the order you tackle them in changes.

• Who to send it to: People who created an account, never got far enough to see the product work, and have not had an email from you recently.
• When to send it: The same day they sign up, or the next morning, if they have not activated by then. Wait much longer and you are writing a “getting started” email to someone who has already forgotten they signed up.
• What to say: Name the specific step they stopped on, whether that is inviting a teammate, creating a first project, pasting a snippet, or connecting a calendar. Give them one link that picks up from that step. A welcome email listing every feature is not an activation email. For more on the product side of this, see Activation for PLG SaaS.
• When to skip it: When an onboarding automation already covers this moment, in which case fix that automation rather than stacking a campaign on top of it. Also skip it when you have nothing specific to name, or when complaint rates are already climbing.
• What this is not: One-time passcodes, account verification, or password resets. It is also not new-hire onboarding for employees.

A sequence that fires on a fixed schedule assumes everyone who signs up moves at the same pace. They do not. Some people finish setup in ten minutes and others take three weeks.

Build your audiences from what you already know about what each person did:

• When they signed up, and whether they have activated since
• The last setup step they started but did not finish
• The last thing they did in the product, such as using a feature, sending an invite, or creating a project
• Which plan they are on, or whether they are still in a trial
• Whether they cancelled or let a trial end

Some triggers are too blunt to use on their own. “Everyone on day 3,” “anyone who has not opened an email in 90 days,” and “the whole list” tell you nothing about whether this particular person needs this particular email.

Plan tier is useful for adjusting the message, since a free user and a paying user need different next steps, but behavior should decide who gets the email at all. A good test: if you cannot name the event that put someone into a segment, that segment is not ready to send to.

Feed this from your analytics tool, such as PostHog, Amplitude, or Mixpanel, or from your own product events. The audience needs to update on its own as people activate or leave. If you export a list once and mail it a week later, you will email people asking them to do something they have already done.

• Give every email one job and one main link, and write it the way a person would actually write it.
• Start with a small audience, see what happens, and only expand the versions that beat a holdout.
• Count every program against the same limit per person. Onboarding, campaigns, retention nudges, and win-back all land in the same inbox, so three programs running at once means three emails, not one.
• Skip the send when you emailed that person in the last week, when an automation already covers the same moment, when you have nothing specific to say, or when complaint rates are climbing.
• Write the email, look at it properly, and get it approved before it goes to a large audience.
• Password resets and receipts can share the same sending setup and suppression list, which is convenient, but they are a different job. Lifecycle email is the activation, onboarding, retention, and win-back work.

Pick one outcome that means the product actually got used. Depending on what you sell, that might be activation, a specific first action, an upgrade to a paid plan, or someone returning after they left.

Then hold back a random slice of that same audience and send them nothing at all. Compare the two groups on the outcome you picked. The gap between them is what the email caused, which is not the same as how many people in the mailed group converted.

Open rates cannot answer this question. Someone can open an email and never touch the product again.

If a version does no better than the holdout, stop sending it. If it wins, turn it into an always-on automation so everyone who reaches the same moment later gets it too, and get that approved before it goes live. Otherwise you rebuild the same campaign by hand every quarter.

These four examples use a made-up company called Acme. Each one is from Alex at Acme to a user named Maya Chen, and there is one for each of the four jobs. None of them offer a discount.

• You do not have meaningful signup volume yet. Getting more people to sign up is the bigger problem.
• You run an online store and need abandoned cart, browse abandon, or reorder reminders. Those run on a different set of events.
• You are looking for new-hire onboarding emails for employees. That is a different kind of onboarding.
• You need one-time passcodes, account verification, or password resets. Those are transactional emails, triggered by a single request rather than by a pattern of behavior.
• You are choosing a transactional email API. Worth doing, but that is a question about infrastructure, not about what to send.
• You want one sequence that every signup gets forever, no matter what they do. That is the thing this guide argues against.