Startup Email Examples: From Waitlist to Winback

Sent immediately after a user joins the waitlist. Confirms the action and sets expectations.

Hi {{first_name}},

You are on the waitlist for {{ProductName}}.

Access invites will go out in {{rough_eta}}. Until then, the only emails sent here will be product updates that affect launch timing.

Useful preview: {{optional_preview_link}}

{{Sender name}}

Confirms what the user just did, names the product, gives a soft ETA, and avoids any marketing pretense. The job is to not lose trust before you have earned it.

Plain text. One sentence per paragraph. Sign it from a real person. Mention what they will hear about and roughly when.

Skip the long backstory, the founder vision essay, the unsolicited social-proof links. They opted in for a wait, not a pitch.

Sent to a slice of the waitlist when private access opens.

Hi {{first_name}},

Your {{ProductName}} access is ready: {{access_link}}

Start with {{first_action}}. It should take about {{time_estimate}}.

If anything breaks, reply with the rough steps that led there.

{{Sender name}}

Treats the invite as the event, not the marketing copy around it. One link to claim, a single sentence on what to do first, and a way to reply if anything is broken.

A button, a deadline (gentle), a one-line note that you want feedback. The reader is doing you a favor by trying it.

A multi-step welcome flow before the user has logged in. Save the deeper onboarding for after they have done something.

Sent on launch day to the broader waitlist or full subscriber list.

Hi {{first_name}},

{{ProductName}} is live: {{product_url}}

The short version: {{one_sentence_value_prop}}.

Launch notes: {{launch_story_url}}

If the product is useful, a comment on {{community_link}} helps other builders find it.

{{Sender name}}

Short, declarative, links to one thing. The reader wakes up to a clear answer to "what happened." Pair it with a Product Hunt or HN link as the secondary action.

Two sentences max in the lede. Hero link to the product. Secondary link to the launch story (Product Hunt, blog, HN) for people who want to participate.

A wall of feature copy. The launch email is a doorway, not a pitch deck.

Sent immediately after self-serve signup. The most-read email a startup will ever send.

Hi {{first_name}},

Welcome to {{ProductName}}.

The fastest path to {{first_outcome}} is here: {{first_action_link}}

Estimated time: {{time_estimate}}.

Replies go to a monitored inbox if anything looks broken.

{{Sender name}}

Names one next action, says how long it takes, and invites a reply. Puts ownership of activation on the reader without making them feel pressured.

One next action. One time estimate. One reply invitation. A signed-from-founder line for the first 1,000 signups.

Listing every feature. Multiple CTAs. A drip schedule that starts firing before the user has even logged in.

Behavior-triggered when a user signed up but has not hit a key milestone after 24 to 72 hours.

Hi {{first_name}},

{{ProductName}} is one step from {{aha_moment}}.

The remaining step is {{missing_step}}: {{deep_link}}

If the step is unclear, reply with the blocker.

{{Sender name}}

Specific to the action they did not complete. Not a generic comeback send. Names the unlocked outcome, not the missing button.

Reference the actual step they got stuck on. Offer one path forward. Offer a reply if it is broken.

A generic "any questions?" send to your entire signup list. Behavior-triggered means triggered by behavior.

Sent to active users when a meaningful feature ships.

Hi {{first_name}},

{{Feature}} is now live in {{ProductName}}.

It helps with {{specific_use_case}}.

Try it here: {{deep_link}}

Release note: {{release_note_link}}

{{Sender name}}

Plain subject line, one paragraph on the use case, one screenshot, one CTA. Treats the user as someone who already knows the product.

Lead with the user problem the feature solves. Skip the feature name as the lead.

Sending feature emails for changes the user will not notice. Save announcements for moments that change behavior.

Sent 3 days and 1 day before a trial expires.

Hi {{first_name}},

Your {{ProductName}} trial ends on {{trial_end_date}}.

So far, {{usage_summary}}.

To keep access: {{billing_link}}

Need more evaluation time? Request an extension here: {{extension_link}}

{{Sender name}}

Tells the user what will happen, what they need to do, and gives them a clean way to extend or convert. Honesty wins here.

A clear date. A summary of what they have done in the trial (use the actual product data). Two CTAs: convert or extend.

Surprise expirations. Fake countdown urgency. Hidden cancellation flows.

Transactional, sent when a card declines on renewal.

Hi {{first_name}},

The latest charge for {{ProductName}} did not go through.

Reason from the payment processor: {{decline_reason}}

Update billing details here: {{billing_portal_link}}

Access remains active until {{grace_period_date}}.

{{Sender name}}

Direct, calm, action-oriented. Tells the user what happened, what is at stake, what to do, and how long they have. Subject line matches the body.

The reason from the gateway, the date access ends if not fixed, a single billing-portal link. Keep it from looking like a phishing email.

Marketing language. Apologies that imply your fault. CTAs to upgrade.

Sent to a user that churned 30 to 90 days ago, ideally after a meaningful product change.

Hi {{first_name}},

Since your {{ProductName}} account went inactive, three relevant things changed:

1. {{change_one}}
2. {{change_two}}
3. {{change_three}}

If those solve the original blocker, reactivate here: {{reactivation_link}}

If not, no action needed.

{{Sender name}}

Acknowledges they left without guilt-tripping. Names what is new that addresses the reason they likely left. Offers a path back without a discount that signals desperation.

2 to 4 specific changes since they left. A reactivation link that does not require re-onboarding. A reply invitation if their reason for leaving has not been addressed.

A discount in the subject line. A long comeback message. A reactivation flow that asks them to re-enter everything.