Run a Product Hunt launch playbook
You are launching on Product Hunt in 3-4 weeks and your previous attempt got 20 upvotes because you hit publish and hoped. This builds the launch playbook — hunter selection, pre-launch audience warming, launch-day shift schedule, asset checklist — so the launch produces real signal instead of embarrassment.
Product Hunt Launches That Ship Signal, Not Noise
Hitting publish on Product Hunt and hoping is the single most common failure mode — launches that get 20-50 upvotes because no audience was warmed, no first comment was prepared, and no shift schedule existed for launch day. Teams with a 4-week playbook routinely produce 500+ upvote launches because the playbook handles three different axes: discovery (hunter, assets), distribution (audience warming, launch-day amplification), and engagement (replies to every comment within the hour).
How the Run a Product Hunt launch playbook Prompt Works
The prompt sequences work across four weeks. Foundations week (T-4) covers hunter selection and asset prep. Warming weeks (T-3, T-2) build the runway — email segmentation, social teasers, advocate priming — without revealing the launch date. T-1 week locks the launch-day checklist and the shift schedule. Launch day itself runs on the shift model: someone is always on duty to respond to comments within the hour, which is the single highest-leverage action during the PH window.
The execution rules catch the predictable landmines: Product Hunt policy prohibits directly asking for upvotes, which catches many launches that draft "please upvote" email blasts. The rule is to share with personal notes, not solicit votes. First Round Review's writing on launch orchestration and Y Combinator's library on go-to-market both document the same pattern — great launches look simple on launch day because the prep work happened four weeks earlier.
When to Use It
- A Product Hunt launch is planned and the team has no playbook.
- A previous PH launch underperformed and the team wants to run a better one.
- A new product is going to market and PH is part of the channel mix.
- A founding team is planning their first public launch.
- A relaunch of a major product version is scheduled.
Common Pitfalls
- No shift schedule. Comment response time drops after the first hour, and so does ranking. Shift coverage is non-optional.
- Directly soliciting upvotes. Violates Product Hunt policy and looks desperate even when it's not caught.
- Weak first comment. The first comment is the pitch that every voter reads. Prepare it in advance, don't type it on launch morning.
Sources
- First Round Review — on launches and go-to-market
- Y Combinator Library
- How to Get Startup Ideas — Paul Graham
- Stripe Blog — on product launches
Sources
- First Round Review — First Round
- Y Combinator Library — Y Combinator
- How to Get Startup Ideas — Paul Graham
- Stripe Blog — Stripe
Prompt details
Ready to try the prompt?
Open the live prompt detail page for the full workflow.