The best launch-day message tells a specific person what changed, why it helps, and what they can do next. These templates give you starting language for email, X, LinkedIn, direct messages, and communities. Replace every bracketed placeholder, cut anything you cannot honestly claim, and send only to people for whom the product is relevant. A short personal note beats a polished blast sent to strangers.

Key takeaways

  • Choose one audience and one action for each message.
  • Show the product doing something real, not a list of adjectives.
  • Ask for honest feedback or a visit, not votes where platform rules forbid that.
  • Use a different opening for users, peers, and communities.
  • Follow up with what you learned, not another copy of the announcement.

Before sending anything, run the launch readiness checklist. Test the destination URL, signup, main action, and mobile page. The launch guide covers the sequence around these messages.

How to use these templates

Replace the bracketed fields with real details and remove any sentence that does not fit. Do not leave [specific result] in an email or insert a made-up metric because it makes the note sound more impressive. If the product is in beta, say so. If a feature is not available yet, do not write as though it is. Read the message aloud once; founders often hear awkward marketing language more easily than they spot it on the screen.

Set one primary link per message, usually the product page or the launch discussion. If you are using several platforms, do not ask the same person to perform an action on all of them at once. The free Launch Post Kit can help adapt copy to channel lengths, but you should still check platform rules and make the final wording your own.

1. Pre-launch teaser email to your list

Send this only to people who already opted in. It creates context without pretending there is a surprise reveal if you have discussed the product publicly for months.

Subject: [Product] opens on [date]

Hi [first name],

On [date], we're opening [product] to [specific audience].
It helps with [one concrete job] by [simple explanation of how].

If that sounds useful, you can see [demo or preview link] now.
I'll send the public launch link when it is live. Reply if there is
one thing you want me to show or explain before then.

[Your name]

Customize the audience and job before choosing a subject line. If there is no useful preview, remove that sentence rather than sending a broken or private link. A teaser should make the next email expected, not manufacture urgency.

2. Launch-day email to your list

Send this after the product and launch page are genuinely public. Point people to the product first if trying it is your main goal; point to the discussion if you want feedback there.

Subject: [Product] is live: [clear benefit]

Hi [first name],

[Product] is live. It helps [audience] [complete a specific task]
without [friction you actually remove].

You can try it here: [product URL]
Our launch discussion is here: [platform URL, if relevant]

The part I'd especially like feedback on is [one question].
If you try it, hit reply and tell me where you got stuck.

Thanks for following the build,
[Your name]

Do not bury the action under a long founder biography. Include pricing or access limits if they affect whether someone can try the product. Remove the second link if it divides attention.

3. Short X post

Use one sentence for the audience, one for the task, and a working link. A screenshot can help if it shows the actual result.

We built [product] for [audience] who need to [job].

It lets you [specific action] and get [real output].

It's live today: [URL]
I'd love to hear what feels unclear after a first try.

Avoid stacking unrelated hashtags or claiming to be the “best” without evidence. If you have a launch thread, link to the thread only when discussion is the point. Otherwise link to the product.

4. X thread opener

Use a thread when the problem needs a little explanation. The opener should stand alone if nobody reads the remaining posts.

We kept seeing [specific problem] when [audience] tried to [task].

Today we launched [product], a [plain category] that [main action].
Here's the problem we focused on, what we built, and what still needs work.

Try it: [URL]

Follow with a real example, a screenshot, and one honest limitation. Do not use a thread to repeat ten versions of the same product claim.

5. LinkedIn post

LinkedIn readers may need business context before a feature list. Write like you are explaining the launch to a former colleague, not presenting a keynote.

After talking with [type of users], one problem kept coming up:
[specific task and why it was difficult].

We built [product] so [audience] can [concrete action].
The first version does [two important things]. It does not yet [limit].

It's public today: [URL]
If this is part of your work, what would you need to see before trying it?

The limitation line can make the post more credible when it is relevant. Do not reveal private customer details or imply users endorsed the product if they only answered research questions.

6. Direct message to a friend or existing user

Send individually, not as a copied mass DM. Choose someone who knows you or has asked about the problem. Never make their support feel like a debt.

Hey [name], [product] is live today. You mentioned [specific problem]
when we spoke, so I thought you might want to see it: [URL]

No need to promote it. If you have ten minutes to try [specific task],
I'd value your honest reaction, especially where the flow feels slow.

If you link to a platform launch, ask them to read and comment only if they have something genuine to say. Product Hunt's official launch guidance says not to ask directly for upvotes. Show HN also forbids recruiting friends for votes or comments.

7. Community post

Read the community rules first. Some groups welcome maker updates; others only allow product links in a weekly thread. If the venue does not allow self-promotion, do not use this template there.

I built [product] because [specific problem I encountered].

It currently helps [audience] [complete task]. Here is a working
example or demo: [URL]

One decision I'm uncertain about is [real design or product question].
If you try it, I'd appreciate direct feedback on that part. I made
the product and will be here to answer questions.

This works only when the question is real and the product is accessible. Replace the community post with a normal contribution if you do not yet have something members can try.

8. Note to an integration partner

Use this only where the partner relationship actually exists. A cold pitch pretending to be an existing collaborator damages trust.

Hi [name],

We launched [product] today. The [integration or shared workflow] we
discussed is now available at [URL].

It lets a [shared user type] move from [starting point] to [outcome].
I wrote a short setup note here: [documentation URL].

Would you review the integration description for accuracy? If it looks
right, I'm happy to provide a short paragraph your team can share.

[Your name]

Give the partner a reason to care and a small, specific ask. Do not request a backlink before they have confirmed that the integration or description is useful.

9. Reply to a launch comment

Public replies are part of the product experience. Thank the person, answer the actual question, and avoid pasting the same CTA under every comment.

Thanks, [name]. You're right that [restate their point accurately].

Right now [what the product does or does not do]. We chose that because
[short reason], but [trade-off] is real.

If you try [specific part], tell me whether [focused question].
I'll update this thread if we change the approach.

If you do not know the answer, say that you need to check and return with the result. A concrete follow-up builds more trust than an instant evasive answer.

10. Thank-you note to supporters

Send this to people who chose to help. It should not be another request for public engagement.

Hi [name],

Thanks for taking time to look at [product] today. Your note about
[specific observation] helped us spot [what we learned].

We're working on [next action] and I'll let you know when it changes.
If you run into another issue, you can reply here.

[Your name]

Specificity matters. If you have not actually acted on feedback yet, say what you are investigating instead of claiming a fix is underway.

11. Post-launch recap

Send this after you have something to report beyond a leaderboard position. It can be a short email, social post, or update to existing users.

One week after launching [product], here is what we learned.

People used it most for [observed use case]. The repeated question was
[question], so we changed [real improvement or next investigation].
We also found [honest limitation].

If you are [target audience], you can try the current version here:
[URL]. Tell us what still gets in your way.

Only include observations you actually recorded. A public rank or upvote count can be mentioned with context, but it is not a substitute for product learning. For a broader distribution plan after day one, see the launch platforms guide.

What should you avoid sending?

  • A mass DM that pretends to be personal.
  • A request to “upvote us” where the platform prohibits it.
  • A vote ring or exchange with people who have not tried the product.
  • A claim of limited availability that is not true.
  • A broad promise about SEO, traffic, or customer results.
  • The same long paragraph copied into communities with different rules.

LaunchAF's ranking policy puts paid launches above free launches on the current weekly board, with votes ordering products within each group. That does not mean you should ask strangers for performative votes. Invite people who might use the product to inspect it and comment honestly. If you submit to LaunchAF, check the current free badge and review conditions before writing that your listing is live.

Frequently asked questions

When should I send a launch email?

Send the announcement once the product page and main action work. If a launch platform reviews submissions, wait until your listing is actually public before linking to it. Your own email schedule can be fixed even if a directory queue cannot.

Should I ask friends to upvote?

Follow the platform's rules. Product Hunt says not to ask directly for upvotes, and Show HN forbids recruiting votes or comments. A personal request for honest product feedback is safer and more useful than trying to inflate a score.

How long should a launch post be?

Long enough to say who it helps, what it does, and where to try it. A short X post and a community build story need different lengths. Cut claims that do not help a reader decide whether the product is relevant.

Can I reuse the same copy everywhere?

Reuse verified facts and links, but change the opening and question for each audience. A customer email should help someone try the product; a developer community may want a working example and a design trade-off.

What if the launch is quiet?

Do not manufacture activity. Check whether the link worked, whether visitors understood the first screen, and whether anyone completed the main action. Follow up with relevant people who opted in and use what you learn to improve the next message.

The bottom line

Edit the bracketed fields until each message sounds like something you would send to one real person. Test the links, respect each platform's rules, and answer the replies. The strongest launch template is the one that makes it easy for the right reader to try the product and tell you the truth.