A Product Hunt Launch Checklist From Someone Who Has Done It Seven Times
I have launched seven products on Product Hunt. That is enough launches to know the ritual and enough missed expectations to stop calling it a growth strategy.
The ritual is familiar. Find a hunter. Pick the right day. Wake up early. Ask everyone you know to vote. Refresh the leaderboard until you hate yourself. By midnight, turn the rank into a graphic and call it a launch.
Most of that is optional. Some of it is actively bad advice.
Product Hunt can still be a useful launch surface. It can give a new product a focused day of feedback, a small pile of early users, some social proof, and occasionally a useful connection. It does not manufacture demand for something nobody wanted yesterday. Treat it as a conversion event, not a discovery event, and the preparation gets much simpler.
What do you need before launching on Product Hunt?
You need a real product that a stranger can try, a clear sentence explaining who it is for, and enough support capacity to respond when someone has a question.
Product Hunt's own featuring guidelines say it plainly: featured products must be ready for use or have a clear path to launch. That is a sensible bar. A waitlist can be honest, but a Product Hunt day has very little patience for vaporware disguised as a release.
Before you pick a date, make sure a new visitor can:
- Understand the product from the first screen.
- Complete the core action without needing a personal demo.
- See what happens after they sign up.
- Get help if something breaks.
- Find your pricing, or understand why there is no pricing yet.
You do not need every edge case finished. You do need the happy path to be real. Launching before that point does not create urgency. It creates a day of confused people who will not return.
Do you need a Product Hunt hunter?
No.
Anyone can submit their own product. Product Hunt's preparation guide explicitly says you should not pay a hunter. The old hunter economy persists because it gave people a concrete thing to optimize, and because a recommendation from someone established felt like borrowed credibility.
A thoughtful hunter who genuinely knows the product can still be useful. They may write a sharper introduction and attract their own network. But a hunter is not a distribution workaround. Do not delay a ready launch for weeks trying to borrow an audience from someone who does not know why your product exists.
The thing that does matter is a credible maker profile. Fill it in before launch day. Add the people who built the product. If someone lands on the page and likes what they see, make it obvious that real people are behind it and available to answer.
How far ahead should you prepare for a Product Hunt launch?
Two weeks is enough for a small product. More time helps only if you use it to improve the product and line up real conversations, not if you use it to build a private upvote spreadsheet.
Here is the checklist I would use.
Two weeks before
- Write the one-sentence description without adjectives you cannot prove.
- Collect screenshots that show an outcome, not six versions of the same dashboard.
- Record a short demo if the product is visual or hard to explain. Product Hunt says roughly 53% of Products of the Day since 2021 included a video, which makes it a reasonable thing to test, not a requirement.
- Ask five people who match the customer to use the product before you launch it publicly.
- Fix the places where they get stuck.
One week before
- Prepare the Product Hunt listing: name, tagline, description, gallery, maker profiles, links, and any launch offer.
- Write your maker comment. Explain why the product exists and the constraint it removes. Do not write an origin story that takes six paragraphs to reach the product.
- Make a list of people who have already expressed interest. Tell them the date, but do not make their support feel like a debt.
- Check analytics and error monitoring. You will not get a big enough sample to learn much from vanity numbers, but you should know whether signups work and where traffic came from.
The day before
- Test the signup and checkout flow while logged out.
- Decide who answers product questions and who watches errors.
- Get sleep. A launch day is a long support shift, not a competitive gaming event.
What should you do on Product Hunt launch day?
Show up and talk to people.
Post the maker comment early. Reply to every real question. Ask follow-up questions when someone describes how they would use the product. If somebody says it is not for them, believe them without trying to negotiate them into a user.
The useful measure of the day is not just upvotes. It is whether the conversations teach you something you could not learn from an analytics dashboard. The person who says “I would use this if it exported to X” may be describing a roadmap item, or they may be revealing that you have targeted the wrong workflow. Keep the distinction open.
Product Hunt's launch-day guidance pushes back on the idea that a launch only counts if it reaches number one. That is not humility copy. It is practical. The leaderboard is a scarce ranking surface that changes day to day. Your product's retention is a better signal than where a temporary page placed against unrelated products.
Should you ask people to upvote your Product Hunt launch?
Ask people to look at the product. Let the upvote follow if they think it deserves one.
Do not run a giveaway that rewards upvotes. Product Hunt's promotion guidance allows launch offers but says a contest or giveaway tied to an upvote will be stopped. Even if it were allowed, it would teach you the wrong thing: how many people will click when asked, not whether your product earns attention from someone who sees it fresh.
Cold DMs to strangers are usually worse. They interrupt people who have no reason to care, make the launch feel transactional, and leave you with a lot of low-quality activity that is hard to separate from genuine interest.
Share the launch with people who already know the problem. Send the landing page or the Product Hunt page. Ask for honest feedback. A real comment from a real potential customer is more useful than a handful of ceremonial votes.
What does a successful Product Hunt launch look like?
It depends on the product stage, but it is not a rank by itself.
A successful launch might mean:
- Ten customers who complete the first valuable action.
- Three conversations with the exact people you hoped to reach.
- One partner or journalist who understands the product enough to continue the conversation.
- A clear message that converts better than the one on your homepage.
- Proof that the launch audience is not the audience you need.
That last one hurts and is still useful. I have published Product Hunt launches without clean retained-user data, so I am not going to invent a number that makes seven launches sound like a linear education. What I can say is that a leaderboard result has never solved the distribution problem afterward.
I went through the platform's data and the incentives behind the advice in my honest answer to whether Product Hunt is worth it. The short version is that the platform is best when you bring a clear product and some people already primed to care. It is weakest when you are hoping one day of attention creates the audience you did not build beforehand.
What should you do after a Product Hunt launch?
Follow up before the day turns into a screenshot.
Write down the questions that came up more than once. Email or message the people who opted in, with a concrete next step rather than a generic thank-you. Watch whether launch-day signups finish onboarding in the following week. If you offered a discount, check whether it attracted a customer you want to keep or a collection of people who wanted a deal.
Then publish what you learned. The useful build-in-public version is not “we hit number four today.” It is the specific thing that surprised you: which screenshot made people understand the product, where users got stuck, what nobody cared about, and whether anyone returned after the excitement wore off.
Product Hunt is a day. Distribution is the work you do before and after it. Do not let the neatness of a launch date distract you from the part that has no leaderboard at all.
A solo full-stack developer and product builder with 8 years of experience shipping production software and 2 years as an indie hacker.
alexcloudstar.com