A Launch Announcement Checklist, Item by Item
Checklists · 9 min read ·
Small checks that stop avoidable launch mistakes: accuracy, links, images, accounts, tracking and a plan for replies once your announcement is live.
Every launch has a moment when something small and silly goes wrong. A link points to the staging site. The pricing page still says "coming soon". The share image is the wrong size. None of these is serious, and all of them are avoidable. A checklist does not make you a better founder; it frees your attention for the things only you can do.
This is a checklist built in the order work actually happens. Take what applies, skip what does not, and adapt the rest to your product.
Two weeks out: the foundations
1. Decide the one-sentence description. Write it, then test it on someone outside your field. Everything else in the announcement repeats it.
2. Settle the facts. Product name, spelling, company name, domain, short and long descriptions, categories. Put them in one document and treat it as the source of truth.
3. Choose the destination. Where will people land when they click? A home page, a dedicated launch page or a product page? Pick the one that explains the product fastest. Hacker News's Show HN guidance advises avoiding sign-ups as a barrier to trying something, and a landing page that blocks the product behind a form works against that principle.
4. Check the product itself. Walk through the sign-up and first-use path on a new device, with a new email address. Note every point of friction.
5. Prepare for traffic. Make sure the site can handle a short surge of visitors. Check that your hosting plan, email sending limits and any third-party service limits are comfortable.
6. Set up measurement. Install analytics, create a goal for your key action (sign-up, purchase, download) and decide how you will tag links from each channel. Use lowercase, consistent labels for source, medium and campaign, and write them down in one place so every link follows the same pattern.
One week out: the assets
7. Images. Prepare a logo, a screenshot, and a share image sized for social previews. Check how each looks on a phone.
8. Alt text. Write short descriptive alternative text for each image. It helps people using screen readers and gives search engines context.
9. Short video or animation. Optional, but if you have one, keep it brief and make sure it works with the sound off.
10. Copy variants. Prepare the long version for your listing, a medium version for an email, and a short version for social posts. Keep the facts identical.
11. Titles and descriptions. Google's SEO starter guide says a good title is unique, clear and concise, and a good description is short and includes the most relevant points. Apply that to your launch page.
12. Accounts. Make sure you have login access to every account you will use, and that two-factor sign-in codes are with the right person.
Three days out: the people
13. List who will help. A short list of people you can message on the day: friends, early users, colleagues. Do not ask anyone to vote. Product Hunt's guidance says that direct requests for upvotes violate its guidelines, and the same discipline suits every platform. Ask people to look, try and say what they think.
14. Brief them. Send a note with the link, the one-sentence description, and the time. Make it easy to do the thing you are asking.
15. Decide who answers what. Split the work: one person for product questions, one for support, one for social replies. A small team can still divide the tasks.
16. Draft reply templates. Prepare a few short, honest answers to predictable questions: pricing, roadmap, how it differs from alternatives, data handling.
The day before: the dry run
17. Click every link. From a clean browser profile, with no logged-in sessions, click every link in the announcement. Do it on a phone, too.
18. Test the sign-up end to end. Create a fresh account. Check that the welcome email arrives, that it is not in spam, and that its links work.
19. Read the announcement aloud. Mistakes in rhythm and spelling show up when you hear them.
20. Check dates and time zones. If you state a time, say which time zone. A clean habit is to write times in 24-hour form with the zone beside them, for example 09:00 UK time, and to add the UTC equivalent for anyone abroad.
21. Check legal and policy pages. Terms, privacy policy, contact details. A visitor who is thinking of signing up may look for them.
22. Sleep. Seriously. The next day is long.
On the day: the live checks
23. Publish, then test. After publishing, open the live page as a visitor and click through.
24. Watch the basics. Server health, error logs, email delivery. If something looks off, fix it before looking at social numbers.
25. Reply promptly and honestly. Answer questions with specifics. If you do not know something, say so and say when you will find out.
26. Thank people individually. A short message goes a long way.
27. Note what confuses people. Keep a running list of questions you keep getting. Each is a gap in your copy or your product.
28. Resist over-claiming. If a result is modest, describe it modestly.
The day after: the follow-through
29. Export what you can. Comments, messages, sign-up data, referrer information. Save them while they are fresh.
30. Send a thank-you note. To early supporters and to anyone who gave useful feedback.
31. Fix the top three problems. Not twenty. The three that most people hit.
32. Write down what you learned. Which channel brought the most useful visitors, which message landed, which did not.
Keeping the record
Archive listings stay available long after the announcement day, so the checklist applies to them too: accurate facts, a working link, and clear writing. The article on keeping a listing current covers how to revisit it.
A shorter version for tiny teams
If you are one person with limited time, do these seven:
- Write the one-sentence description.
- Test the sign-up on a clean device.
- Make one good image.
- Set up analytics with a single goal.
- Click every link on a phone.
- Tell five people the time.
- Clear your calendar for the day.
Adapting the checklist to your kind of product
A checklist is a starting point, and the right emphasis changes with what you are launching.
A software product with sign-up. Spend most of your preparation on the first-use path. Most visitors will decide in the first minutes whether to stay, so empty states, sample data and a short guided start repay the time. Check password reset and email confirmation, because launch day is the worst time to discover they fail.
A physical product or shop. Concentrate on stock, shipping information and the order confirmation message. Make sure the quantities you can actually deliver are clear, and that the page says when customers should expect to receive their order. Disappointment about delivery is a far bigger risk than a lukewarm reception.
A service business. Your launch page should make the next step obvious: book a call, request a quote or send a message. Test the booking form and check that notifications reach a real inbox that someone watches during the day.
A content or community product. Seed it before you announce. An empty forum or a blog with one post gives a visitor no reason to return. Have a handful of real entries in place and a clear sense of the next one coming.
A product with a mobile app. Check the store listing, the version a visitor will actually download, and the screens shown in the store. Make sure the website and the store page tell the same story.
Whichever applies, schedule the dry run for the day before and treat any failure as useful news. Finding a broken link on Tuesday is a good outcome; finding it on Wednesday in front of a crowd is not.
Roles on the day, in one paragraph each
If more than one person is involved, name the roles explicitly. The owner of the launch makes the final decision on anything that comes up and is the person who publishes. The responder answers questions on the listing, in comments and by email, using the prepared templates and escalating anything unusual. The watcher keeps an eye on the technical side: uptime, errors, sign-up volume, email delivery. The recorder keeps a simple running note of what happened and when, so you can learn from it afterwards. In a team of two these roles are shared; in a team of one, you are all four, which is a good reason to keep the scope of the day small and the checklist short.
Where this fits with listing
Many founders use the same preparation for a directory listing and for a contest. Do the checks once, then reuse the assets. When you are ready, the submit page starts the entry, the current price for a launch listing is $5. The categories page helps you choose where to appear.
A launch checklist is not bureaucracy. It is a way of taking small, boring risks off the table so that the interesting ones, the ones about your product, are the only ones left.
Questions and answers
- When should I start the checklist?
- Start at least two weeks before you intend to announce, so that anything that needs lead time, such as images, accounts or approvals, is not left to the last day.
- What is the most commonly missed item?
- The link. Teams test the product but forget to click the announcement link from a clean browser, so visitors land on a broken or logged-in page.
- Do I need analytics set up before announcing?
- Yes. Without it you cannot tell which channel sent which visitors, and you cannot repeat what worked.
- Who should check the announcement?
- Someone who did not write it, ideally someone outside your field, since they will notice what an insider skims past.