Skip to content
Back to Launch & Discoverability

Product Hunt Preparation

Everything you build before submit day — the gallery, tagline, maker comment, demo asset, and hunter — so launch day is one-click execution.

Why

Product Hunt rewards preparation with a 3-5x ranking boost, and punishes improvisation with invisibility. The gallery images, the 60-character tagline, the maker's first comment, and the demo GIF are all scored by voters in the first 3 seconds — if any is generic or confusing, the voter scrolls past and never comes back. Preparation also means lining up a hunter (a respected PH user who posts for you), pre-briefing your network to upvote in the first hour, and writing the maker comment that tells the building story. Teams that submit 'when the product is ready' without preparing the listing get 50 upvotes; teams that prepare the listing get 500. The product is the same; the preparation is the difference.

When

2-3 weeks before the target PH launch date. The product must be live and stable (post-soft-launch), and the team must have 2-3 hours on launch day for comment engagement.

How

1. Study the top 10 Product Hunt launches in your category (dev tools) from the last 6 months — screenshot their gallery, tagline, and maker comment; identify the pattern
2. Write a 60-character tagline that states the category + the differentiator: "Cheatsheets → full lifecycle platform for developers" (not "the best tool for devs")
3. Build a 5-image gallery (required): image 1 = hero with product name + tagline, images 2-4 = key features with annotations, image 5 = pricing or social proof; 1270x760 PNG, dark-mode-safe
4. Record a 30-second demo GIF or video showing the core 'aha' moment — voters watch 5 seconds, so the hook is in the first 2 seconds
5. Write the maker comment (500 words): the building story (why this exists), the key feature, the launch offer, a question to invite discussion; save as a draft
6. Line up a hunter: a PH user with >500 followers and a track record of top-5 launches; DM them 2 weeks before, or self-submit if you have >100 followers
7. Pre-brief your network: 20-30 friendly users who will upvote and comment in the first hour; send them the PH link (it goes live at 12:01am PST) and the first-comment draft
8. Submit at 12:01am PST on launch day (or have your hunter submit); post the maker comment immediately, then start the engagement rotation

Example

# Product Hunt Preparation — ez4code v2.0
Target: Tuesday 2026-10-06, 12:01am PST

## Tagline (60 chars)
"Cheatsheets → full lifecycle platform for devs" (52 chars)

## Gallery (5 images, 1270x760)
1. hero-ez4code.png — logo + tagline + 3 feature icons
2. feature-lifecycle.png — 7-stage lifecycle diagram
3. feature-launch.png — /launch page screenshot w/ annotation
4. feature-ai.png — AI coding assistant in action
5. social-proof.png — "12k devs · 47 cheatsheets · 9 locales"

## Demo GIF
ez4code-demo.gif — 28s, shows: signup → pick cheatsheet → AI code → deploy
Hook in first 2s: "from idea to deployed in 4 clicks"

## Maker comment (draft)
"We built EZ4Code because every dev tool is a point solution —
cheatsheets here, deploy there, AI in another tab. v2.0 is one
platform for the whole lifecycle: learn → build → launch → grow.
Launch day: 50% off Pro for PH voters. What's your lifecycle stage?"

## Hunter
@johndoe (4,200 followers, 3 prior Product of the Day) — confirmed

## Pre-briefed network
27 friendly devs, Slack #ph-launch, link + first-comment draft sent

Common Problems

  • ⚠A tagline that describes the product instead of the value — 'AI-powered developer cheatsheet platform' is a description, not a hook; 'Stack Overflow meets Vercel for solo devs' is a hook that positions and intrigues.
  • ⚠Gallery images that are raw screenshots — voters see 50 launches and raw screenshots blur together; annotated images with a headline overlay and brand color stand out and communicate the feature in 2 seconds.
  • ⚠No demo GIF because 'the gallery is enough' — the gallery is static; the GIF shows the product working, which is the single highest converter for software products; a 30-second GIF outperforms 5 images.
  • ⚠Self-submitting with 12 followers — Product Hunt's algorithm weights the hunter's reputation; a no-name submit gets 30 upvotes, the same product with a top hunter gets 300; line up a hunter or build your PH presence first.

Best Practices

  • ✓A/B test the tagline with 5 friendly devs before launch — show them 3 candidates and ask 'which makes you want to click?'; the tagline is the single highest-impact text on the listing.
  • ✓Make gallery image 1 a 'hero' with the product name, tagline, and a visual of the core action — this is the image shown in the PH feed and social cards, so it must work as a 200px thumbnail, not just full-size.
  • ✓Write the maker comment as a story, not a spec — 'I spent 2 years jumping between 7 dev tools and built the thing I wished existed' outperforms 'EZ4Code has 47 cheatsheets, 9 locales, AI coding...'; voters upvote stories.
  • ✓Confirm your hunter 2 weeks before, not 2 days — top hunters book up, and a last-minute self-submit with no hunter is the most common PH launch failure mode.