Nika

Essentials for launching a product

There are a lot of products being hunted, launched, and competing for attention here.

But I still see some makers missing the very basics.

It got me thinking about putting together an "essentials package" of things that, in my opinion, every maker should have in place before deciding to launch their product on this platform.

My Product Hunt launch essentials would include the following (these should be done before launch, btw):

  • a properly filled-out profile

  • a finished landing page for the product (the one beyond PH)

  • a hunter

  • gathering relevant people who will be stated under the launch (e.g. as makers + products/stack used for building)

  • a first comment prepared in advance

  • choosing the right launch day

  • appealing visuals and compelling copy

Is there anything you'd add to this essentials package that I'm missing?

772 views

Add a comment

Replies

Best
Alston Zhuang

Strong list. I’d add one more thing before visuals/copy: a sharp “why now” sentence.

A lot of launches explain what the product does, but not why people should care today.

The best PH launches usually make the timing obvious: new workflow, new platform shift, new pain, or a behavior that suddenly became common.

I’d also prepare 5-10 real discussion angles before launch, not just a first comment. The launch day conversation matters as much as the launch page.

Oleksandr Kotliar

Such a solid baseline, Nika! You’ve covered the core foundation perfectly. If I had to add one thing, it would be setting up basic analytics (like PostHog or Hotjar) on the landing page before launch day. It’s the only way to understand why people leave without converting once the PH traffic hits. Great reminder for all the makers out there! 👏

Mikita Aliaksandrovich

One thing I'd add is collecting feedback before launch, not just preparing for launch. A dozen conversations with real users will usually improve your landing page, onboarding, and messaging more than weeks of internal brainstorming.

Arpita Idalgave

Great checklist. I'd add one more essential item: validate the problem with real users before launch. A polished product and landing page help, but user feedback is what truly determines product-market fit.

Md Khayruzzaman

Big one people underestimate: distribution before launch.

A great product with no warm audience often gets treated worse than an average product with momentum.

I’d add:

  • early supporters lined up before launch day

  • a waitlist/email list

  • founder presence on X/LinkedIn before posting the PH link

  • clear onboarding so visitors instantly “get it”

  • analytics + feedback collection ready from day one


    And last but not the least, the first 2 hours of launch matter way more than most makers realize.

Fabrizio Pfannl

Kill switch is the essential nobody puts on the list. A pre-written paragraph for "this is what we tried, what we learned, what we are sunsetting" saved in a doc on launch day saves panic later. Paul Graham's schlep essay is still the cleanest framing of why founders skip this: https://paulgraham.com/schlep.html

Furkan Topcuoğlu

I'd add reply plan after launch to the list. A lot of teams prepare the first comment but not the next 10 answers they'll need if people ask at pricing, use cases, competitors or roadmap. Launch day is much easier when the team already knows who answers what.

Marcelo Vegas
20+ years building products, learned the hard way:

1. Audience first · I've launched on closed marketplaces (TF/CM) without
   audience and watched products die · now I build pre-launch audience first.

2. Single specific niche beats generic · my admin template "Tailwind 4
   senior dev" niche works · "templates for everyone" doesn't.

3. Honesty in copy converts · "It does X well, doesn't do Y" beats "best
   ever for all use cases."

4. Pre-warm your network · 30 LinkedIn DMs to relevant contacts day-of-launch
   = first 100 upvotes in 1 hour = PH algorithm boost.

Curious what others find · the biggest unforced mistake first-time launchers make?