Lifecycle email for signups you already have

Thousands of people signed up and nobody ever emailed them. Lifecycle email is the mail you send those people so they activate, finish setup, come back, or return after they left.

Updated September 3, 20262 min read

What to send, and to whom

If you are not already getting signups, this is not the work. Lifecycle email starts after someone creates an account. You write based on what they did in the product, or the step they never finished. A newsletter is a calendar. Cold outbound is people who never signed up. This is neither.

Stores usually mean cart and browse abandon. Products with a signup have a different loop: people who never finished setup, people who used it and went quiet, and people who cancelled. Same idea (mail timed to state), different events.

Four jobs that cover a signup list

Almost all of the money sitting in a signup list is one of these four. Pick the job from the row you have, not from a funnel diagram.

Four jobs for signups you already have: signed up never activated, onboarding until activation, used it then quiet, and left after trial ended or cancelled.

They signed up and never came back. Name the step they stopped on (invite, first project, calendar, snippet). Send the same day or next morning. Ramp the audience. Keep a holdout so you can tell whether the mail caused activation.

They started setup and stalled. That is an onboarding email sequence: a few notes from signup until they activate, then stop. Onboarding email examples are paste-ready subjects and bodies.

They used it, then went quiet, but the account is still open. That is retention, not win-back. One note about the next useful step.

They left. Trial expired, cancelled, or the account closed after a quiet stretch. Win-back email names the workspace they had or something that shipped. Not a coupon.

How to run it without wrecking the list

  • Segment on behavior (signup, last incomplete step, last event, cancel reason), not on “day 3” alone.
  • One job and one link per email, in the founder’s voice.
  • Start small. Expand what beats a holdout.
  • Opens do not count. Compare activation or paid against people who got nothing.
  • When a version wins, promote it to an always-on automation.
  • Onboarding, campaigns, and win-back share one frequency count per person. Do not stack three programs on the same inbox.
  • Password resets and receipts can use the same sending domain. That is useful. It is not this job.

FAQ

When should the first email go out?

Same day or next morning after signup, if they have not activated. Name the step they stopped on. A welcome that lists features is not that email.

How do I know it worked?

Hold out a slice of the same audience and compare activation or paid conversion. Opens do not tell you whether the product got used.

Is this the same as ecommerce lifecycle email?

No. Cart and browse abandon are a different event model. This page is for products people create an account for.

Will this send without asking?

It should not. Draft the mail, show it, and wait for approval on any large audience.

Get started

Put Ranla to work this week.

Connect product events and your sending domain. Ranla runs transactional and lifecycle mail from your domain, and shows you where users are dropping off.

Start free