How to Write Your First Launch Email (with Template) (2026)

Your waitlist is full. The product is ready. You sit down to write the launch email and freeze, because the launch email is the one email that has to do real work, and most indie founders have never written one. This is the version I now run after watching a dozen launch emails land or die.

I have shipped 7 indie apps over 8 years and ended up building two tools for myself along the way: Spaceport, a SwiftUI starter that gets a paid iOS app live in days, and Lighthouse, the launch toolkit this post is mostly about. The template below is the launch email pattern both products run.

Table of contents

• What the launch email is for
• The shape that works
• The subject line
• The full template
• Mistakes to avoid
• After you hit send
• Frequently asked questions

What the launch email is for

The launch email has one job: get people from your waitlist to your product, today. Not next week. Not when they have time. Today, while the launch is happening and you are online to answer questions.

Everything else (the story arc, the founder photo, the long backstory) is a way of getting in the way of that job. Indie launch emails fail when they try to be company updates.

The shape that works

Three sections. Each one short enough to read on a phone at a traffic light:

• One opening line that names what shipped. No throat clearing. No "hope you are well". No "long time no email". You are not writing to a friend, you are writing to someone who signed up for this exact thing.
• Two short paragraphs. The first names the problem the product solves (a sentence). The second names what the reader can do right now (also a sentence). Skip the feature list.
• One single link as a clear button or bare URL. Not three calls to action, not a navigation menu. One link. Wherever the reader scans, the link is the answer.

Total length: under 150 words. That is not a constraint to decorate around; it is the whole point. People do not read launch emails, they scan them. Make the scan path obvious.

The subject line

The subject line decides whether the email gets opened at all. It should look like an email from a person, not a campaign:

• Lowercase, no emoji, no exclamation marks. Emoji and TitleCase signal "marketing email" even when the body is human. Lowercase signals "personal".
• Name the thing, not the moment. "runwell is live" reads better than "the day you have been waiting for is here". Concrete beats hype, every time.
• Under 40 characters. Most clients truncate past 40 on mobile. The whole subject should be visible in the preview.

Subject lines that consistently work for indie launches:

• runwell is live
• you can use runwell now
• it's ready, here is the link
• runwell, the one you signed up for

The full template

Copy this, swap in your product name, the one-sentence problem, and the one-sentence action. Then send it. Total writing time should be under ten minutes.

That is the whole email. Six short paragraphs, under 110 words, one link, one signature. The reader can scan it in three seconds and get to the link.

Mistakes to avoid

The shape above is shaped by mistakes. Five worth naming:

• The feature list. Five bullets describing what the product does. The reader does not want a feature list, they want to know if it solves the problem they signed up for help with. Save features for the landing page.
• The journey paragraph. "Eighteen months ago I had a question". The waitlist signed up to use the product, not to read the founder origin story. Move the story to a follow-up post if you want to tell it.
• Three calls to action. "Visit the site, follow us on Twitter, join the Discord". Pick one. The launch email has one job; do not split it across three.
• An image header. Image headers get blocked, tank deliverability, and add zero value over plain text. A link with the URL written out lands every time.
• A 5pm Friday send. Most launch emails should go out on Tuesday or Wednesday morning, mid-week, when people are at their desks and can actually try the product. Friday afternoon is where launches die.

After you hit send

The email itself is half the work. The other half is what happens in the next four hours:

• Stay online. Replies will come, and most of them will be small (a typo, a question about pricing, a thank you). Answer them in the first hour. The first hour of responses is where indie founders earn their first ten loyal users.
• Watch the click-through rate, not the open rate. Opens are noisy. Clicks tell you whether the body and the link landed. For a warm waitlist with this template, expect 35-50 percent clicks if the email matched what they signed up for. Less than 20 percent suggests the pitch on the landing page and the email do not match.
• Plan the follow-up. A second email three days later to anyone who did not click. Same body, different subject ("did you miss this?"). The follow-up usually adds another 10-15 percent of the warmed list.

For the full launch checklist this email fits inside, see the pre-launch checklist for an indie SaaS. This email is step 9 of 12.

Frequently asked questions

What if I am raising capital alongside launching?

The launch email and the investor update are two different documents and should never be the same email. The investor cadence runs on its own track; dedicated tools like Funding Banker, a curated investor directory with pitch and outreach tracking, are built for that side. The launch email above is for the waitlist; the investor update is its own message and its own list.

Can I include a video or product demo?

One link. If the most important thing for the reader to do is watch a demo, make the link the demo. If it is to use the product, make the link the product. Do not include both. Choose.

How long should I wait between waitlist signup and launch email?

Six to ten weeks is the sweet spot. Less and people have not had time to share the waitlist; more and the original "what is this" memory fades and your open rate drops noticeably. If people signed up over a year ago, send a "we are about to launch, are you still in?" email first.

Should I segment the launch email by survey answer?

For the first launch, no. Send the same email to everyone. Once you have the open and click data, the second campaign (a week later) can be segmented by which survey answer they gave. For why surveys on the signup form matter, see why answers beat emails.

What sending tool do I use for indie volumes?

For under 5,000 subscribers, any modern indie newsletter tool works. See best newsletter tools for a small list for the lineup. Lighthouse handles the same job in the same dashboard as the waitlist, which is the indie shortcut.

The launch email is small. Six short paragraphs. One link. The simplicity is what makes it work; the templates that try to do more are the ones that do less. Send a small honest email and stay online to answer the replies.

Lighthouse handles the waitlist that fills the list, the newsletter that sends this email, and the feedback page for after you launch, in one place. Free trial, indie pricing. From the same indie dev behind Spaceport, a SwiftUI starter kit for shipping paid iOS apps fast.