← Back to playbooks

Email launch workflow

Waitlist follow-up email playbook for SaaS founders

Use this after visitors join from templates, playbooks, Product Hunt, Show HN, pricing pages, or paid-pack previews and the next validation step is a reply, objection, or paid-intent signal.

Audience

Founders with SEO, launch, or paid-pack waitlist signups who need replies before checkout

Validation metric

Reply rate, paid-pack preview clicks, objection quality, source-aware signup segments, and requests for the next launch email asset.

Launch steps

  1. Segment subscribers by the page, source, or offer that triggered the signup instead of sending one generic blast.
  2. Open with the exact asset they cared about so the email feels like a continuation of the page they joined from.
  3. Deliver one useful teardown, prompt, or diagnostic question before asking for a reply.
  4. Ask one reply-friendly question that reveals urgency, objection, or desired paid-pack format.
  5. Route commercial-intent readers to the most relevant paid-pack preview or launch email sequence template.
  6. Use replies and paid-pack clicks to decide whether Creem checkout is justified before building delivery features.

Pitfalls to avoid

  • Do not send a generic newsletter welcome email when the signup source already tells you the reader's intent.
  • Do not ask for a call before giving the reader a useful diagnostic or example.
  • Do not mix three CTAs in one email; reply intent, paid-pack clicks, and digest interest should stay measurable.

Paid-pack validation

Turn this workflow into a show hn pack

Preview the $19 show hn pack hypothesis for this workflow. Every click and signup helps separate real monetization intent from generic newsletter interest.

Preview the $19 show hn pack

Keep the swipe file growing

Get weekly SaaS launch hooks

One email with fresh teardown notes, swipe-file patterns, and launch workflow examples for founders writing better landing pages, tweets, and Show HN posts.

No product spam. The first signal is whether founders want more reusable launch examples.