General
Share and discuss tech, products, business, startups, or product recommendations
Start new thread

Essentials for launching a product

by
•

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?

1.1K views

Add a comment

Replies

Best

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: 

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?

That's very helpful Nika, thanks. I'm about to launch here soon and figured it makes sense to understand more about the community.

A small thing I would add is testing the full user journey before launch. Broken links or confusing signup flows can hurt a good launch.

Solid list. The pre-written first comment is the one most people skip, then fumble live.

Two I'd add:

  1. Line up your people before launch day, not on it. A small group who'll show up in the first 2-3 hours beats a big list you ping at noon. Early momentum is most of the game. Give them the day, the time, and exactly what you need ahead of time.

  2. And have somewhere to catch the traffic. Most makers point everyone at the PH page and a landing page, then let them vanish. Put one capture point in the path: email, waitlist, a Discord, anything. The votes fade in 48 hours. The list doesn't.

That's it, really. You've got the basics covered better than most.

One thing I’d add: prepare answers to the 5 questions people will obviously ask. Pricing, data/privacy, who it’s for, what makes it different, and what happens after signup. Launch day moves fast, and crisp answers make the product feel much more trustworthy.

Thank you so much , now i know what was missing previously :)

Hi. can you please xpand on "HOW TO FIND A HUNTER" and on "gathering relevant people who will be stated...". I am planning my launch but I am far from an expert. Thanks.

I would add one more: a clear objection map before launch.

Most launch checklists cover profile, visuals, landing page, first comment, launch day, etc.

But I think makers should also write down the 10 questions people are most likely to ask in the comments.


Things like:

  • what makes this different?

  • who is it actually for?

  • can I try it without paying?

  • what happens if the output is bad?

  • what is the fastest first use case?

If those answers are ready, the comment section becomes much more useful and less reactive.

the unsexy essentials. a working demo URL that does not require signup to understand the value. an actual person tagged as the founder, not the company logo. one screenshot that explains the product without copy. the rest is wrapping paper.

First
Previous
•••
456
Next