Skip to the content
LaunchedHere
Sign in Launchyours

The First Hour of Launch Day: A Practical Playbook

Playbook · 8 min read ·

What to do in the first sixty minutes after your launch goes live: checks, first comment, first replies, calm messages to helpers and mistakes to avoid.

Illustration: Chunky stopwatch sticker with the sixty minutes divided into four coloured quarter slices, rounded playful style

The first hour of launch day feels like the longest hour of the year. You have prepared for weeks, the page is about to go live or just has, and your heart is doing something odd. This playbook splits the hour into four quarters, each with a small number of jobs, so you always know what to do next.

It assumes you have already built your page and briefed your helpers. If you have not, the guides on writing a page and the week-long competition cover the groundwork.

Before minute zero

A few things should be settled the night before. If you are in a different time zone from the launch window, check the opening time and set two alarms. Product Hunt's own guidance suggests 12:01 am Pacific Time for prepared makers without constraints, though it also says the best time is when you are ready. Whatever time applies to you, know it exactly, and say which time zone you mean whenever you tell anyone.

Have these open and ready: your page, your product's home page, your analytics, your support inbox, a document with your reply drafts, and a drink.

Minutes 0 to 15: look, check, post

Look. Open your live page in a private window, signed out, as a stranger would. Does it display correctly? Are the images sharp? Is the tagline right?

Check the path. Click the link to your product. Sign up with a throwaway address. Does the journey work? If you find a fault, stay calm, fix it, and only then proceed.

Post your first comment. Product Hunt's preparation guide recommends a maker's first comment and describes what it should contain: who you are, what the product does, who it is for, the story behind it and a request for feedback, not votes. Keep it short, warm and specific. End with one question people can answer easily, for example "What would make this more useful for you?"

Do a quick sanity check on your servers. Open your monitoring or dashboard. If you expect a rush, make sure nothing is close to a limit.

Resist the urge to look at the ranking every thirty seconds. At this stage it means almost nothing.

Minutes 15 to 30: tell your helpers

Now send the message you drafted. Keep it short and personal.

"Hi Sam, we are live! Here is the link. If you have two minutes, I would love your honest reaction: what is clear, what is confusing? Thank you."

Notice what is absent. There is no request for votes. Product Hunt's launch guide says you cannot ask people directly to upvote and should invite them to visit and comment, and Hacker News's guidelines tell users not to solicit upvotes or comments. Following the rule makes your results honest. It also tends to produce better comments, since people who look carefully write better replies than people who click a button.

Send the message to individuals, not a big group. People respond better to being addressed by name. Space the messages over the quarter-hour so replies do not all arrive at once and overwhelm you.

Then post your link in the places where you have a standing, relevant presence: your own social profiles, a newsletter if you have one, a community where you are already a regular. Write each post for that audience. A single carefully written post beats five copies.

Minutes 30 to 45: the first conversations

Comments will begin to arrive. This is the heart of the hour.

Reply fast. A first reply within a few minutes tells the person you are present.

Reply specifically. "Thanks!" is polite. "Thanks, Sam. The export you mention is on the roadmap for next month, and I would love to know which format you need" is useful.

Answer questions with the product. If someone asks whether it can do something, show them. A short screenshot or a clip beats a paragraph.

Thank the critics. If someone says something negative, thank them first, then respond with facts. People reading the thread judge you by how you handle disagreement.

Do not argue. If a comment is hostile or unfair, a short, polite reply is enough. Report abuse through the platform's tools.

Product Hunt's guide notes that comments let makers gather feedback and often lead to networking, partnerships and even funding conversations. The first conversations set the tone, so give them your best attention.

If you have teammates, split the work: one on comments, one on social, one watching the product.

Minutes 45 to 60: take stock

Around the forty-five minute mark, pause and breathe. You are not trying to win the hour. You are laying a foundation.

Check your analytics. Where are visitors coming from? Are people reaching the sign-up? Is anything unexpected, like a lot of drop-offs on one page?

Note the first questions. Write down the three most common. They are the gaps in your page. If it is cheap to fix, fix it now by adding a line to your description or a reply pinned in the comments.

Look at your tech. Errors, slow pages, failed emails. A fault found now costs far less than one found at midday.

Plan the next three hours. Decide who covers what, when you eat, and when you will post an update.

What not to do in the first hour

  • Do not ask for votes. It breaks guidelines and spoils the result.
  • Do not paste the same message everywhere. People notice.
  • Do not argue with commenters.
  • Do not ignore the product. Launch pages draw people; the product needs to hold up.
  • Do not make big changes. A redesign at minute fifty is how outages happen. Only fix clear faults.
  • Do not over-claim. Say what is true, and say what is coming as "planned", not "done".
  • Do not forget to eat.

A sample first comment

To make this concrete, here is the shape of a good first comment, using an imaginary product.

"Hi everyone, I am Alex, and I built Gardenlog with a friend who runs an allotment. We got tired of forgetting which seeds went where. Gardenlog is a simple planner: you sketch your beds, add plants and it tells you when to sow and harvest. It is free to try without an account. We would love to hear which crops you grow and whether the sowing calendar matches your region."

It has a name, a reason, a plain description, a low barrier and a question. It is about eighty words. Nothing in it asks for a vote.

Keeping calm

The hour will produce emotions. Excitement when a good comment lands, panic when a bug appears, disappointment if the page seems quiet. Some techniques help.

  • Breathe and write. If something goes wrong, write down exactly what you see before acting.
  • Know your rollback. If a release breaks something, you should know how to undo it.
  • Lean on your team. Say "I need help with X" early.
  • Remember the length. An hour is a small part of the competition. A quiet start can build, and a loud start can fade.

After the hour

When the hour is up, you will have a sense of how the week will go. Keep the rhythm going: reply, update, share different angles, and keep notes. The article on the week-long competition describes the middle days, and the one on the day after covers what to do when it is over.

On this site

If you plan to launch with us, the submit page starts an entry. The acceptable use page sets out what is and is not allowed, and the leaderboard page shows the standings. A launch entry is currently priced at $5, a free listing can be upgraded to one at the same price, and neither affects voting. The about-founders page names the two founders.

If the first hour goes badly

Sometimes it does. The page shows an old image, the sign-up fails, or a comment points out a mistake in your description. None of this is fatal. What matters is how visibly and quickly you respond.

If the product has a fault, say so in the comments: "We have found a problem with sign-up for some people and are fixing it now. Thanks for your patience." Then fix it and report back. Visitors who see a calm, honest reply are often more impressed than those who never saw a problem.

If the page itself has an error, edit it, and mention the correction if it was substantial. If the traffic is lower than hoped, keep to the plan. Many launches pick up later in the day as other time zones wake up, and the thoughtful replies you post now will still be there when they do.

A one-page version to print

Minute zero: open the page as a stranger. Minute five: test the sign-up. Minute ten: post the first comment. Minute fifteen: message helpers one by one, asking for visits and comments. Minute thirty: reply to every comment. Minute forty-five: check analytics and note the first questions. Minute fifty-five: plan the next three hours. Keep it by your keyboard, and tick things off as you go. The point of a list at that hour is not to be clever. It is to stop you forgetting something simple while your mind is racing.

One line to remember

Check, post, tell, talk, take stock. Do those five in that order, ask nobody for a vote, and you will have started launch day the way good launches start.

Questions and answers

What should I do first when my launch goes live?
Open the live page as a visitor, click every link, then post your first comment. Fix anything broken before you tell anyone to come.
When should I tell my helpers?
Right after your own checks pass. Send a short message with the link and one clear request: visit, try it and comment honestly.
Is midnight Pacific time the best launch moment?
Product Hunt recommends 12:01 am Pacific Time for prepared makers without constraints, but its guidance says the best day is whenever you are ready.
How many replies should I write in the first hour?
Reply to every comment you can, quickly and specifically. Quality matters more than volume.

Sources

Related guides

Support