Product Hunt launch course: plan, launch and follow up

A Product Hunt launch is one day on a public leaderboard, watched by makers, early adopters, investors and journalists. That makes it great for some goals and the wrong tool for others, so start by naming yours.

Goals a launch serves well.

• First users and feedback: people on Product Hunt like trying new tools and saying what they think.
• Social proof: a launch page, reviews and a day badge you can show on your site.
• A deadline for your team: a date that forces you to finish onboarding, copy and visuals.
• Visibility with early adopters: people who tell others about tools they like.

Goals it serves poorly. Long sales cycles with a handful of enterprise buyers, or products nobody can try yet. If people cannot sign up or see a demo on launch day, wait.

Write your launch goal as one number you control. "Fifty conversations with new users in the launch week" or "two hundred sign-ups from the launch page". A ranking is a nice result, but it depends on who else launches that day.

Check the basics. Can a stranger understand the product in ten seconds from your homepage? Does sign-up take under a minute? Is there a way to collect feedback?

Common mistake. Launching because "everyone does". A launch without a goal ends with a busy day and no lasting result.

The Catchwisdom Product Hunt Launch Playbook puts pre-launch preparation early in its curriculum, before any launch-day tactics. The community you meet before launch is the community that shows up on the day.

Set up your maker presence. Complete your Product Hunt profile with a real photo, a headline that says what you build and links to your site and social profiles. People check the maker before they try the product.

Participate for a few weeks. Browse new launches, try tools in your category and leave thoughtful comments: what you liked, one question, one suggestion. Makers remember people who gave useful feedback, and some will return the favour by trying your product.

Study your category. Look at recent launches similar to yours. Note their taglines, first images and the first comment from the maker. Which ones started real conversations?

Warm up your own audience. Tell your newsletter, community and social followers that a launch is coming and what you will ask of them: try the product, share honest feedback, leave a review if they like it.

Collect launch-day helpers. A short list of friends, customers and fellow makers who will try the product and comment on the day.

Common mistake. Creating an account the week of launch. A profile with no history looks like a stranger asking for attention.

Your launch card on the homepage has a few seconds to earn a click. Product Hunt's own preparing-for-launch guide says the tagline is typically the main element that drives someone to click.

Name (40 characters max). Simply the name of the product, as the launch kit on GitHub puts it.

Tagline (60 characters max). Say what the product does, concisely and descriptively. Product Hunt's guide asks for no gimmicks or over-the-top language. Write ten options and pick the clearest.

• Weak: "The future of productivity is here".
• Strong: "Turn meeting notes into tasks in Slack".

Thumbnail and gallery. The thumbnail is your logo on the card; the gallery tells the story. Lead with the image that shows the main result, then the key screens, then social proof. Keep text on images large enough for a phone.

Demo video. Short and concrete: the problem, the product solving it, the result.

The maker's first comment. Introduce yourself, explain why you built it, what is special and what feedback you want. End with a question that invites replies. It sets the tone for the whole thread.

Description. Expand the tagline: who it is for, the top three features and any launch offer for the community.

Common mistake. A clever tagline nobody understands. Clear beats clever on a busy homepage.

One of the most common questions in Product Hunt's Launch Guide is "Do I need a hunter?". The official answer is no: Product Hunt encourages makers to hunt their own products and says there is no discernible advantage to using a third-party hunter.

What this means for you. You can post your product yourself, as the maker, and spend the energy you would have spent finding a hunter on preparation.

When a known person still helps. Someone respected in your niche can help in other ways: trying the product early, giving feedback on your tagline and gallery, and telling their audience about your launch on the day. That help is about people, not about who clicks "Submit".

Add your team as makers. Everyone who built the product can be listed as a maker, so they can reply in the thread with their own profile.

Schedule the launch. Prepare the post in advance and schedule it for your chosen day, so launch morning is about people, not forms.

Prepare your replies. Write answers to the five questions you expect most: pricing, integrations, privacy, roadmap and how you differ from the best-known alternative. Having them ready lets you answer fast and well.

Common mistake. Delaying a launch for weeks while hunting for a hunter. Product Hunt's own answer: look in the mirror.

"Best day to launch on Product Hunt?" is another common question in the official Launch Guide. Its answer: the best day to launch is the day on which you are most prepared. There are pros and cons to every day.

Weigh the trade-off. Weekdays bring more visitors and more competing launches. Weekends bring fewer of both. A small product with a niche audience may get more attention on a quieter day; a product aiming for wide visibility may prefer a busier one.

The time. Product Hunt's day starts at midnight Pacific Time, and the guide says 12:01 am Pacific Time is the best time for makers who are planning ahead and have no other limitations. Launching at the start of the day gives you the full 24 hours.

Plan around your people. Check where your team and your audience are. If you are in Europe, 12:01 am Pacific is morning for you, which makes launch day easier to staff.

Avoid clashes. Check for big industry events, holidays in your main market and major launches you know about.

Block the calendar. The whole team should keep launch day free for replying, sharing updates and fixing anything that breaks.

Common mistake. Picking a date first and preparing after. The guide's answer works in reverse: prepare, then pick the day you are ready.

The Catchwisdom playbook calls this unit engaging the community on launch day. A launch is a conversation that lasts 24 hours, and the maker's job is to lead it.

First hour. Post your first comment as soon as the launch is live. Share the launch link with your team and your launch-day helpers, and tell your audience you are live: what the product does and that you would love their honest feedback.

Reply to every comment. Thank people by name, answer questions fully and ask follow-ups. If someone reports a bug, say when it will be fixed, then come back and say it is done. A thread full of real maker replies shows the product is alive.

Share updates through the day. A short note on social media a few times during the day: what people are asking, a feature request you just shipped, a thank-you to the community.

Watch your goal, not the leaderboard. Track the number you set in Unit 1: sign-ups, conversations or feedback items. A launch that brings fifty real users is a good launch whatever the rank.

Keep the team in rotation. Split the day into shifts so someone fresh is always in the thread.

Common mistake. Posting the launch and going to bed. The comment thread is where visitors decide whether to try the product.

The Catchwisdom curriculum includes post-launch follow-up as its own unit, because the launch day is the start of the value, not the end.

Within 24 hours.

• Thank everyone who commented, by replying in the thread and with a short post on your own channels.
• Add the launch link to your site, ideally with the Product Hunt badge, so new visitors see the social proof.
• Answer any question that is still open.

Within the first week.

• Follow up with new users. Send a welcome email that asks one question: what did they hope the product would do?
• Sort the feedback. Group comments into bugs, feature requests and confusion about the product. Confusion is often the most valuable: it tells you what the tagline and onboarding failed to explain.
• Ship something fast. Fix one requested item and announce it in the launch thread. People who commented see that you listen.

Within the month.

• Ask happy users for a review on your Product Hunt page; reviews keep working long after launch day.
• Write a short launch recap post: what you learned, the numbers you are happy to share and what is next.

Measure against your goal. Compare the result with the number from Unit 1 and note what you would change next time.

Common mistake. Treating launch traffic as a one-day spike and not following up with the people it brought.

You do not have to guess what works. Product Hunt's own Launch Guide has a case studies section, and public data about past launches is available from independent tools.

Read two case studies before your launch. For each, write down three things: how they described the product in the tagline, what the first gallery image showed and how the maker replied in the comments.

Use public launch data for context. PH Launchpad describes its dataset as real data from 233,775+ launches across 271 categories. Use data like this to see how busy your category is and how similar products positioned themselves, not as a prediction of your own result.

Look at your category map. Which categories are crowded and which are quiet? A precise category often puts you in front of people who are actually looking for your kind of tool.

Build your own playbook. After your launch, write a one-page recap: preparation timeline, assets, launch-day schedule, results against your goal and what you would do differently. It makes your next launch, a major update or a new product, much easier.

Plan the next launch. Many teams launch again for big new versions. Note in your recap what would justify a relaunch.

Common mistake. Copying a famous launch line by line. Learn the structure, keep your own voice.