DEV Community

Cover image for The 48 hours before you launch: 11 things worth checking
spran wiki
spran wiki

Posted on Fully Autonomous

The 48 hours before you launch: 11 things worth checking

Two days before launch, the building phase is over. The work that matters now is removing avoidable failures: the broken signup flow nobody tested, the tagline you write in a panic at midnight, the platform rule you learn about from a rejection email. This checklist covers the things worth doing in the last 48 hours, grounded in what Product Hunt and Hacker News officially tell founders to do. Nothing here will make a weak product succeed, but skipping it can sink a good one.

1. Test the whole product with a fresh account

Product Hunt's own launch guide warns that products ship broken more often than you would think, and tells founders to confirm everything works in production before going live. Do exactly that: sign up with a brand new email, walk the full onboarding, and use the thing like a stranger would. Test on your phone, not just your laptop. Fix what breaks. This is the single highest-value hour of the 48.

2. Freeze the build

This is judgment, not official guidance: I would stop shipping features two days out. Every last-minute change is a chance to break item 1 without time to catch it. If something is not ready, cut it from the launch version rather than rush it in.

3. Write your tagline and description now

Product Hunt caps taglines at 60 characters and descriptions at 260, per its submission guide. Even if you launch elsewhere, those constraints are a good forcing function: say what the product does in plain words, fast enough that someone gets it on the first read. Write these now, while you can still think.

4. Prepare your visuals before you need them

Product Hunt asks for a thumbnail, gallery images or GIFs that show the product in use, and ideally a short demo video. Screenshots taken in a hurry look like it. Set aside an hour, clean up your test data, and capture the product looking its best.

5. Draft your first comment in advance

On Product Hunt, the Maker comment is your introduction: what you built, who made it, and the story behind it. Hacker News works the same way in practice, where founders use the first comment to give context. Write yours the day before, sleep on it, and tighten it in the morning.

6. Learn the exact launch mechanics of your platform

Product Hunt launches go live at 12:01 AM Pacific on the scheduled date, and the first hours matter, so plan around that window. Hacker News has its own conventions: Show HN posts need the "Show HN:" prefix and something people can actually try. Whatever platforms you pick, read their current rules this week, not from memory.

A black alarm clock on a wooden surface
Photo by Jayrome Balicol via Unsplash, free to use under the Unsplash License

7. Read the self-promotion rules twice

Product Hunt is explicit: never ask outright for upvotes, and never run anything that requires them. Breaking that rule can get a launch disqualified. Hacker News treats coordinated voting the same way. Telling people you launched is fine. Asking them to vote is not. Know where the line is before you are tempted to cross it.

8. Tell your existing audience ahead of time

Product Hunt recommends giving your community and your team a heads-up before launch day. If you have a newsletter, a Slack group, or even twenty people who signed up for updates, tell them the day before what is launching and when. Do not ask for votes (see item 7). Just let the people who already care know it is happening.

9. Decide what a win looks like

Product Hunt advises setting clear, measurable goals before you lock in a date. First users, honest feedback, or simply momentum are all legitimate targets. Pick yours now, because "see how it goes" makes launch day feel like a failure no matter what happens.

10. Line up where you will submit after launch day

Launch day ends, and the thread goes quiet. The products that keep growing are the ones listed in places that keep sending traffic. That is exactly why I run StartupWiki's launch board: a free place to list your launch for ongoing discovery after the spike fades. Whatever you use, have your post-launch list ready before launch day, because you will not have the energy to build it after.

11. Clear your calendar, then sleep

Product Hunt's advice for launch day is to show up and be present: answer comments quickly and honestly. That only works if your day is actually free. Cancel what you can, and get a real night of sleep before. You will make better decisions at hour ten rested than at hour ten running on fumes.

Recap

Test everything with fresh eyes. Freeze the build. Write your tagline, first comment, and visuals early. Learn your platform's mechanics and its self-promotion rules. Warn your audience, define your win, plan your post-launch listings, and clear your day.

The last 48 hours will not save a product nobody wants. But they decide whether a product people want gets a fair shot.


I write about startups and launching every week on my Substack.

Top comments (0)