Launch Day Hour by Hour: What to Do Before, During and After You Post
Plan a launch day around your own attention, because answering people matters more than posting everywhere. Check the signup path the night before, publish early enough to stay at your desk for the hours that follow, post to one place at a time, and reply to every comment within the hour. Fix only what blocks a new visitor, write down numbers at fixed times, and stop posting when you can no longer answer well.
What is this schedule for?
It is for the day you choose to announce your product in public, whichever places you pick. Some launch sites make the day for you, with a daily ranking that resets at a fixed hour. Others, including a free board like ours, have no day at all, so you pick one. The clock below counts in hours after you publish, so it works in any time zone. Call the moment of publishing hour zero.
The schedule assumes one person and one product. If you have teammates, give each channel to one owner and keep the bug list with a single person. Otherwise replies pile up and nobody fixes anything.
What should be checked the evening before?
Anything that can embarrass you in front of a stranger. Do these in a private browser window with no saved logins, because that is what a new visitor sees.
- Complete the signup path as a brand-new user, on a phone as well as a laptop, and note every moment you hesitated.
- Check that your analytics register a visit, and that a tagged link shows up with its source. A launch with no numbers is only a feeling.
- Open every link in the post and every link on the landing page. A dead link in front of new readers is the cheapest mistake to avoid.
- Write the first comment you will leave under your own post, and keep the reasons for building it short. The maker first comment template has a shape to start from.
- Set an error alert, or at least decide where you will look first if the site slows down, such as your host’s dashboard and logs.
- Prepare three short answers to the questions you expect, such as what it costs, what it does with data and how it differs from the obvious alternative.
What happens in each hour?
| When | What you do | Rule for the hour |
|---|---|---|
| Hour -1 | Test signup once more, open your inbox and your analytics side by side | If anything fails, do not publish; fix it, then move the day |
| Hour 0 | Publish in your main place and leave your first comment immediately | Choose the place where your likely users already are, not the biggest one |
| Hours 1 and 2 | Reply to every comment. Watch the first visitors in your analytics and, if you can, a session recording | Answer questions before praise; a question is a person deciding |
| Hour 3 | Write down visits, sign-ups and the first-action count. Read every piece of feedback in one pass | Pick the one problem seen more than once, not the loudest |
| Hours 4 to 6 | Post to a second place with its own wording, only if the first is going well and the product still works | One new place at a time, never several in the same hour |
| Hours 7 to 9 | Ship the one fix that blocks a new visitor, if there is one | Anything that is only annoying goes on the list for tomorrow |
| Hours 10 to 12 | Reply again to everything still open, thank the people who helped and share one useful thing you learned | Stop starting new threads when you can no longer answer them properly |
| End of day | Record the numbers, the top three complaints and the source of each sign-up | Do not judge the launch tonight; you are tired and it is early |
The times are a structure, not a promise about how many people will show up. Move the posting hour to fit the place you chose, using the logic in the best day to launch answer. A Show HN, for example, needs you present for the replies, as the Show HN playbook explains.
What if something breaks, or nobody comes?
Three situations come up often, and the first two need opposite responses.
- The site breaks. If new visitors cannot sign up or load the main page, stop posting to new places at once, say plainly in your own thread that you are fixing it, and fix it. Posting more links to a broken page wastes the attention you earned.
- Silence. If the first three hours bring almost nothing, do not delete the post and do not repost it; most places treat that as a violation. Check that the link works and the title says what the product is, then use the time to message the few people who might care, one by one.
- One thread takes off. Stay in it. A busy thread rewards a maker who is present, and the rest of the plan can wait until tomorrow.
What do you write down when the day is over?
Four things, before you sleep: the number of visitors and where each came from, the number who reached your key action, the three complaints you saw most, and one sentence on what you would do differently. That is enough to start tomorrow with a plan. The post-launch checklist picks up from there, and the launch day checklist holds the full list of jobs if you want it on paper.
If you have not yet chosen where to publish, you can launch your product free on this board in a few minutes and use it as the first stop of the clock above. While you wait for replies, the ideas board is a useful place to read what other builders say people want.
Frequently asked questions
What time should I publish my launch?
Publish when you can stay at your desk for the next several hours and when the people you want are awake. Nobody outside a given platform can give you a verified best hour, so use your own analytics and the platform’s recent posts to see when your readers are active, then test one time and compare.
Should I launch on several sites on the same day?
Space them out. Each place needs replies from you, and answering three threads at once means you answer all of them badly. Start with the place where your likely users are, add a second only if the first is going well, and keep the wording different, since each audience reads different things.
What if I find a bug during launch day?
Fix it now only if it blocks a new visitor from reaching the key action. Everything else goes on a list for the next day. A rushed change at the busiest hour can break more than it fixes, so keep fixes small, test them in a private window and deploy once.
How many hours should a launch day last?
Plan for about half a working day of close attention and another few hours of lighter replies, but let the discussion decide. If a thread is active, stay with it. If nothing is happening by the end of the day, write down the numbers and carry on tomorrow rather than staying up to watch an empty page.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.
How do you triage comments while working on the product?
Sort each reply into one of four kinds and handle them in this order: a question about whether the product works, a bug report, a suggestion and praise. A question you can answer in a sentence gets answered at once. A bug report gets a thanks, a note on your list and, if it blocks signup, a fix before anything else. A suggestion gets a thank-you and a question about what they were trying to do, which turns it into evidence. Praise gets a short, genuine reply.
Do not argue with a critic. State a fact if one is missing, say what you will change if they are right, and leave it. Other readers judge you by the tone of your replies more than by the criticism. The answers page on responding to launch comments covers common situations in more detail.