Runbook8 min read

The 48-Hour Product Hunt Pre-Launch Runbook

A tactical 48-hour countdown for launching on Product Hunt. What to do on Day 2, Day 1, launch morning, launch hour, and after. Built for solo founders who are about to hit the button.

Published April 12, 2026

Key takeaways

  • The 48 hours before a Product Hunt launch is when most preventable mistakes happen.
  • This runbook covers the operational tasks, not the marketing strategy. Marketing is a separate conversation.
  • Ninety percent of launch-day problems are caused by the same issues: broken OG images, missing policies, no launch hunter lined up, wrong time zone.
  • Most of this can be done in a focused weekend if you haven't started yet.

You're launching on Product Hunt in 48 hours. This is the point where most indie builders panic, break things while trying to fix things, and ship something half-ready. Here's the runbook that stops that from happening.

This isn't the marketing strategy post. This isn't the "how to actually win Product Hunt" post. This is the operational checklist for what must be true at each point in the 48-hour countdown. Run it top to bottom.

T-48 hours (two days out)

The goal today is to finish anything operational that could go wrong on launch day. Marketing preparation is a bonus.

1. Freeze features

No new features. No refactors. No "just one more thing." You're in bug-fix-only mode from this point. New code is how launch day gets broken.

2. Final scan of your public site

Run through the checklist items that matter in every launch:

  • Privacy policy, terms, refund policy all live and linked in the footer
  • OG image loads correctly on Twitter, LinkedIn, and Slack (use opengraph.xyz)
  • Custom domain, SSL working, no certificate warnings
  • Analytics installed and receiving data
  • No leftover noindex tags (read how to find a hidden noindex tag)
  • Contact email live and monitored

If any of these fail, fix them today, not tomorrow.

3. Prepare your Product Hunt post assets

  • Thumbnail: 240x240, crisp, not a generic icon
  • Gallery images: at least 2, up to 6, under 3MB each, showing actual UI
  • Tagline: one short sentence, no more than 60 characters
  • Description: the full pitch, 260 characters max
  • Maker comment: a draft of what you'll post as the first comment on your own launch
  • First comment: a draft of the "why I built this" follow-up

4. Line up your launch hunter (if using one)

If someone else is hunting your product, confirm with them today. Send them the final post draft, make sure they have the assets, and make sure they know the exact launch time. Don't assume they remember.

5. Prep your network

Draft the DM or email you'll send to friends, early users, and your audience the morning of launch. Don't send it yet. Just draft it.

Tip: Product Hunt penalizes mass brand-new-account voting. If you message people, tell them to only vote from accounts they already use. New accounts created just to upvote you get ignored by the algorithm.

T-24 hours (launch day minus one)

The goal today is to put the final touches on and sleep early.

6. Verify launch time zone

Product Hunt days start at 12:01 AM Pacific. That's 3:01 AM Eastern, 8:01 AM UTC, 1:31 PM India Standard Time. If you want the full day, schedule your post for 12:01 AM Pacific, not 12:01 AM in your local time zone.

7. Schedule the post

Use Product Hunt's own scheduling tool in the Ship dashboard. Enter all the assets, the tagline, the description, the topics. Set it to go live at 12:01 AM PT.

Do NOT publish immediately. Schedule it. Then screenshot the scheduled post as evidence it's set up correctly.

8. Write your maker comment

The first comment under your own launch is your second chance to make an impression. Write something personal: why you built this, who it's for, what you learned, what feedback you're looking for. Three to five paragraphs. Not salesy. Save it as a draft in your notes app.

9. Check your server or hosting plan

If you expect traffic, verify you're on a plan that can handle a spike. Serverless platforms (Vercel, Netlify, Cloudflare) scale automatically. Traditional VPS servers may need a bump. Check your database too. Postgres connection pools crash launches.

10. Test signup and purchase flow one more time

Create a new account in incognito mode. Go through signup end-to-end. If you have payments, make a real purchase with a test card and verify the receipt arrives. If any step breaks, fix it tonight.

11. Go to bed early

You're going to be active at odd hours tomorrow. Get real sleep.

Launch morning (T-0 to T+3 hours)

12. Verify the post went live

At 12:05 AM PT, check that your launch post is live on Product Hunt. Sometimes scheduled posts glitch. If something is wrong, fix it immediately (you can still edit the post for a short window).

13. Post your first maker comment

Drop the prepared comment under your own launch within the first 10 minutes. This anchors the thread and gives people something to respond to.

14. Notify your network

Send the DMs, emails, and group messages you drafted. Target people who actively use Product Hunt, not strangers or mass lists. Quality of upvote beats quantity.

15. Post on X, LinkedIn, Indie Hackers

Not as the same copy-paste post. Tailor each one. X post is short and conversational. LinkedIn post is a longer story. Indie Hackers post is about the journey.

16. Monitor comments and reply within 30 minutes

The Product Hunt algorithm rewards engagement on your own launch. Reply to every comment, especially in the first 3 hours. Be thoughtful. Don't just say "thanks!" Offer something substantive.

Launch day (rest of the day)

17. Reply to every comment, every DM

For the full 24 hours. This is the single most important thing you can do for your launch. Volume of engagement matters more than clever marketing.

18. Share milestones

"We just hit #5." "100 upvotes." "Climbed to top 3." Post these moments on X and LinkedIn. Don't overdo it (one per big moment, not one per upvote).

19. Don't pay for upvotes

Product Hunt detects paid voting schemes and penalizes launches that use them. You'll get removed from the daily ranking.

20. Don't ask for votes directly

Saying "please upvote me" on Product Hunt or X is against the rules and hurts you algorithmically. You can say "I'm launching today" and share the link. Let people decide.

21. Monitor your site

Check analytics every couple of hours. If signups are climbing but conversions aren't, look at where people are dropping off. If signups aren't climbing, check that the link works and the page loads.

After launch day

22. Write the launch recap

Two or three days after launch, write a recap post. Numbers, lessons, surprises. These posts get shared and indexed well, and they're the content that fuels your second launch.

23. Email your signups

Every new user who signed up during launch should get a welcome email within 24 hours. Thank them. Ask what brought them in. Point them at the one thing you want them to do next.

24. Archive your assets

Save everything you created for this launch: the OG image, the tagline, the comment drafts, the screenshots. You'll reuse most of it for the next launch.

25. Plan the next launch

One launch is not a growth strategy. Product Hunt, Hacker News Show HN, r/SideProject, Indie Hackers, Betalist, and niche communities are all separate channels. Map which ones you want to hit over the next month.

The common preventable problems

Here's what goes wrong on launch day for solo founders, ranked by frequency:

  1. Broken OG image or link preview looks like spam
  2. Missing refund policy causes Stripe freeze mid-launch
  3. Site is down because of database connection limit
  4. Launch scheduled in wrong time zone, post goes live at 3 PM instead of 12 AM
  5. Privacy policy link broken, customers don't trust the signup
  6. Forgot to set up analytics, so launch day data is lost forever

Every one of these is preventable with a pre-launch check. Run through the SaaS launch checklist or use CalmLaunch to catch these automatically before launch morning.

Common questions

What time should I launch on Product Hunt?

12:01 AM Pacific Time. This gives you the full 24-hour window to climb the rankings. Any later and you're competing with products that already have a lead.

Do I need a launch hunter?

No, not in 2026. Product Hunt removed the hunter advantage years ago. You can hunt your own product. The quality of the launch matters more than who clicked submit.

How many upvotes do I need to make Product of the Day?

It varies. Usually 300-600 upvotes by end of day gets top 5. 700+ gets top 3. These numbers are rough and change based on who else launches that day.

Should I launch on a specific day of the week?

Tuesday, Wednesday, Thursday generally have higher traffic. Avoid Mondays (post-weekend catch-up) and Fridays (lower engagement). Avoid US holidays.

What if nothing happens on launch day?

It happens. Most launches don't go viral. The value is in the structured outreach, the content you create, the people you meet in the comments, and the momentum it builds. A quiet launch is still useful. You just need another one soon.

CalmLaunch checks this for you automatically.

112 launch constants across 8 categories. Adaptive to your project type. Free for 3 projects, no credit card required.

See what I'm missing

Related reading