Skip to content
Back to Launch & Discoverability

Hard Launch

The full public release — Product Hunt, press, social, email, and all channels simultaneously — after the soft launch has de-risked the product.

Why

The hard launch is the moment your product faces its maximum scrutiny: Product Hunt voters, Hacker News commenters, and press readers all arrive within 24 hours, and first impressions are sticky. A coordinated hard launch concentrates all your marketing energy into one spike that algorithms reward (Product Hunt ranking, HN front page, social virality) — spreading the same energy across two weeks gets 1/10 the reach. The hard launch also creates a forcing function: the team has already fixed the soft-launch bugs and sized the infrastructure, so the public launch is execution rather than discovery. Products that 'just quietly launch' and plan to 'promote it later' almost never get the later promotion — without the deadline of a hard launch, marketing stays perpetually tomorrow.

When

After the soft launch exit criteria are met (top issues fixed, infra sized, NPS > 30). Pick a Tuesday or Wednesday for maximum Product Hunt and press pickup; avoid Fridays and weekends.

How

1. Pick launch day: Tuesday or Wednesday, avoid holidays and major competitor launches; check Product Hunt calendar for light days
2. Prepare all channels in advance: blog post (final), Product Hunt listing (title/tagline/gallery/first-comment), social posts (Twitter/LinkedIn/Reddit), email to waitlist, press pitch (if applicable)
3. T-1 day: final go/no-go, confirm soft-launch issues are fixed, confirm infra is sized for 10x soft-launch peak, schedule all posts
4. T-0 09:00 local: deploy to production, run smoke test, verify all green
5. T+15min: submit to Product Hunt (12:01am PST is ideal but 09:00 local works), post on HN (Show HN), tweet, post LinkedIn, send email
6. T+1h to T+12h: monitor all channels — respond to every PH comment within 15 min, every HN comment within 30 min, every tweet within 10 min
7. T+12h: Product Hunt results check — if top 5, double down on getting upvotes; if not, focus on HN and social
8. T+24h: compile launch report — total signups, PH rank, HN points, social shares, press mentions; compare to targets
9. T+72h: steady-state review — if signups > target and retention healthy, declare hard launch successful

Example

# Hard Launch — ez4code v2.0
Date: Tuesday 2026-10-06  (after soft launch met exit criteria)

## Channels prepared (T-1 day)
- Blog: "EZ4Code v2.0 — from cheatsheets to full lifecycle" (1,200 words)
- Product Hunt: title/tagline/5 gallery images/maker comment
- Twitter: 5-thread + demo GIF
- LinkedIn: 200-word post + demo video
- Email: 2,847 waitlist recipients, subject "EZ4Code v2.0 is live"
- HN: Show HN post

## Timeline
09:00 Deploy + smoke test green
09:15 PH submitted, HN posted, Twitter thread, LinkedIn, email sent
10:00 PH #7, HN #12, 312 signups
12:00 PH #3, HN #4 (front page!), 1,089 signups
18:00 PH #2 (Product of the Day runner-up), 2,400 signups
T+24h: 3,127 signups, PH #2, HN 847 points, 89 social shares

## T+72h steady state
Signups: 3,127 (target 2,000) ✓
D1 retention: 34% (target 30%) ✓
=> HARD LAUNCH SUCCESSFUL

Common Problems

  • ⚠Launching on a Friday or weekend — Product Hunt voting is weekday-heavy, HN traffic drops on weekends, and press don't write on Saturdays; you lose 60% of your potential reach.
  • ⚠Staggering channels across days — Product Hunt on Monday, HN on Wednesday, email on Friday; each channel gets a smaller spike and algorithms see 3 small events instead of 1 big one, killing virality.
  • ⚠Not responding to comments in the first 2 hours — Product Hunt and HN commenters who feel ignored become critics, while engaged commenters become advocates; the first 2 hours set the comment tone.
  • ⚠Hard launching without a soft launch first — the first real users are also the most scrutinizing, so every soft-launch bug becomes a public review; the soft launch exists to prevent this exact scenario.

Best Practices

  • ✓Submit to Product Hunt at 12:01am PST on launch day — this gives the full 24-hour voting window and avoids competing with same-day heavy hitters; check ph.launchcalendar.com for light days.
  • ✓Write the Product Hunt 'maker comment' (first comment by the maker) in advance — it should tell the story of why you built this, not restate the tagline; this comment is what converts visitors to upvoters.
  • ✓Have the entire team (and friendly power users) ready to upvote and comment in the first hour — Product Hunt's algorithm weights early engagement, and a 5-comment head start compounds into a top-5 ranking.
  • ✓Prepare a 'launch day support' rotation so the maker can engage on PH/HN while an engineer handles bug reports and a support lead handles inbox — one person cannot do all three for 12 hours.