A Product Hunt launch is a concentrated week of explanation. Your page, image, first comment, supporters, and follow-up replies all need to tell the same story: who the product helps, what it changes, and why now is a good time to try it.
This is an editorial seven-day preparation plan. For platform requirements, use the official Product Hunt launch guide. It recommends asking people to visit and comment, rather than directly requesting upvotes. Check that guidance again before launch because platform rules can change.
Day 7: Write the one-sentence promise
| When | Deliverable |
|---|---|
| 7 days before | One-sentence promise |
| 6 days before | Screenshot and working demo |
| 5 days before | FAQ and maker introduction |
| 4–2 days before | Relevant invitations and rehearsal |
| Launch day | Replies and issue log |
| Following week | Review useful actions and feedback |
Use a plain sentence with an audience, a job, and an outcome. A daily planning tool for solo consultants who want to protect deep work is easier to remember than an AI-powered productivity revolution. Put the sentence at the center of the page, image, and first comment.
Open the IndieNew Tools directory and study how tools are described in a small card. If the value is hard to understand at card size, shorten the copy before you add more claims.
Day 6: Build the proof set
Prepare one product image that shows the result, a short demo or GIF, and a page where visitors can reach the first success quickly. Remove setup steps that do not teach you anything. A visitor should be able to tell what happened after one minute.
- Use a consistent name and promise everywhere.
- Show the real interface or output, not a generic stock scene.
- Test the link on a phone and a fresh browser session.
Day 5: Prepare the launch conversation
Write answers for the questions you hope to receive: who is it for, what did you build first, what is different, and what should a new user do? Ask a few early users to describe the moment the product became useful. Their words often make better replies than polished brand language.
Practical guideline: The launch day is a conversation with a time limit. Prepare useful answers in advance so you can spend the live window listening instead of searching for adjectives.
Days 4–2: Invite the right people
Send personal notes to people who have a reason to care. Tell them what the product does, who it is for, and what kind of feedback would help. Avoid asking for empty support; a thoughtful comment or a test from the right user is more valuable than a pile of clicks.
Keep a small launch resource list in your own notes with the tools that helped you build, explain, and support the product. The IndieNew Tools directory can help you find candidates for a specific gap.
Day 1: Launch, reply, and watch
Reply to questions with specifics. If someone asks about pricing, link to your own product’s current pricing page. If someone asks whether the product works for a different workflow, explain what you have tested and what you have not. Keep a simple note of the questions that repeat.
Do not make major product changes in the middle of the launch unless something is broken. Capture the signal first. After the page settles, review the path from visit to first success and fix the most expensive hesitation.
Days +1 to +7: Turn attention into learning
A launch spike is useful when it changes your next decision. Compare the promise people repeated with the feature they actually used. Follow up with the users who completed the core action and ask what they expected next. Keep the answers close to the roadmap.
When the product page is ready for ongoing discovery, submit it to IndieNew. A directory listing gives the product another shelf, while your launch notes give you the evidence to keep improving the shelf copy.
Key Takeaways
- Center every launch asset on one audience, job, and outcome.
- Prepare proof and answers before launch day.
- Invite relevant people and ask for useful feedback.
- Use the post-launch week to turn attention into product decisions.
When your launch story is clear, share it through the IndieNew submission page.