Indiecity

Guide · 17 Aug 2026 · 15 min

How to launch on Product Hunt without making it the whole plan

Field guide

Launch day is short. The follow-up list is the real work.

Product Hunt is an afternoon. The day resets. The feed moves on. You get a burst of strangers, a rank that feels like a grade, and then silence unless you do the next work yourself.

In 2026 the trap is still treating launch day like a premiere. You polish screenshots for weeks. You schedule the post. You refresh the board. Then you call the launch the plan. It is not. Indiecity is for one person or a team under twenty. You need paying customers, not a badge.

Run Product Hunt as one day inside a longer week. Prepare the page. Work the thread while it is live. Follow up when the afternoon ends.

What Product Hunt is in 2026

Hundreds of products can launch on the same day. Only a thin slice gets real homepage time. In March 2026, JustOneDev wrote on Indie Hackers after both Erla and Voicr were featured. His point was blunt: Product Hunt hand-picks around fifteen apps each day. Featured means you stay visible. Everything else fights noise.

That pick is editorial, not a pure vote race. Product Hunt’s featuring guidelines say they look for useful, novel, high craft, and creative work. You do not need to win every category. Standing out in one or two is often enough. They only feature live products. Waitlists without access, templates, courses, and pure services sit outside what they want on the homepage. Engagement helps. They also say engagement is not everything.

Votes are filtered too. Product Hunt’s own note on fair voting describes automated detection, community reports, and removal of votes that look non-genuine. New accounts and coordinated blasts are a bad bet. Organic comments and real use matter more than a purchased spike.

Two 2026 launches, two different lessons

JustOneDev’s write-up is useful for the page itself. He launched both apps on weekends, away from big company weekdays. He scheduled the page days ahead. He shipped clear previews and a short demo. He filled the first comment, tags, and built-with fields so the page looked finished. That is the work of getting a chance at featured. It is not the work of building a business.

Indie Hackers · u/JustOneDev

I launched 2 apps on Product Hunt and both were featured

March 2026. Both Erla and Voicr featured. His checklist: weekends, mass-market clarity, scheduled page, polished assets, fill every field.

In June 2026, Subhrajyoti Basu wrote about launching RadiusHQ. He started the day near the bottom of the board. He spent the day replying to other makers, asking for feedback, and pulling attention by hand. He finished around #20. The useful part of that thread is not the climb. The comments keep saying the same thing: without an audience, you show up cold. The conversations around the page matter more than the page alone.

Indie Hackers · u/Subhrajyoti Basu

I recently launched on Product Hunt and went from #94 to #20

June 2026. Manual outreach on launch day. Commenters push the same point: follow-up and real conversations beat chasing rank.

A few real conversations beat a pile of drive-by upvotes. The follow-up after launch day is where most of the learning lives. Subhrajyoti’s own take after the climb was honest. If you are not a big name, a mid-board finish may still produce no clients. Rank is not a list of buyers.

Do not make the launch the product

Builders still reverse the order. Four months of features. One day of hope. Then zero. A polished Product Hunt page does not fix that. You still have to talk to people who have the problem, before the day and after it.

You can't wait for users to come to you. You have to go out and get them.

Product Hunt does not replace that line. It gives you a room full of people who like new tools. You still go get them after the room empties. Pieter Levels’s 2026 point still holds: building got cheap. Attention did not. A launch day is one free way to be seen for a few hours. It is not an audience you own.

What to have before you schedule the day

Ship a product someone can use the same day. Put a price on the page if you sell. Set up payment. Write one sentence a stranger understands in five seconds. Prepare the gallery, a short demo, and a first maker comment that says who it is for and what changes for them. Schedule the launch so you are not scrambling at midnight Pacific.

Also prepare the list that is not on Product Hunt: thirty names of people who already have the pain, email or DM open, ready to hear from you on launch morning and again the day after. Those names are your real launch. The Product Hunt post is the public version of work you already do by hand.

  • Live product, not a waitlist with no access
  • One-line offer a stranger gets in five seconds
  • Price and a way to pay, if you are selling
  • Gallery, short demo, complete first maker comment
  • Thirty names outside Product Hunt, with a follow-up script ready
  • A spreadsheet with columns: name, source (PH comment, signup, DM), status, next step

If you cannot fill that list, you are not ready for a launch plan. You are ready for customer conversations and a priced ask. Do that first, or launch with no audience by writing people one by one. Schedule Product Hunt later if you still want the afternoon.

Launch day is for conversations

Be present for the full day. Reply to every real comment. Answer objections in public so the next visitor sees the answer. Ask people what they tried last time, not only whether they upvoted. When someone leaves a useful note, write their handle into your sheet before you leave the tab.

First maker comment (post this when you go live)
Built this for [who] who still [pain in their words]. Today you can [outcome] without [old mess]. It is [price / free trial terms]. I am here all day for questions. If this is your problem, tell me what almost stopped you from trying it.
Reply when someone says “looks cool”
Thanks. Curious: when did this problem last hit you, and what did you use? If it is still open, I can show you the one path that removes it in ten minutes.

Tell your thirty names once, in plain language. Do not send “please upvote” as the whole message. Ask them to try the product and tell you what is broken. If they are already on Product Hunt, they will find the post. If they are not, you still want their use and their money more than their vote.

Note to someone you already know
Hey [name]. We are live on Product Hunt today, but I care more about your take than the rank. You deal with [pain]. The product does [outcome] for [price]. Can you try it and tell me what would stop you from paying?

Ignore the board for stretches of the day. Refreshing the rank does not create customers. Conversations do. If you have energy left, join other makers the same way Subhrajyoti did: ask for feedback, not votes. Talk like a human, not a bot farm.

The 48 hours after are the plan

When the day ends, open the sheet. Everyone who commented with a real objection. Everyone who signed up. Everyone who clicked through and stalled. Those people are warmer than a cold list you invent next month.

Day-after note to a commenter
Hey [name]. Thanks for the note on the Product Hunt post about [their point]. I [fixed it / want to understand it better]. If you still have [pain], I can walk you through it this week for [price]. Fifteen minutes. Want a time?
Day-after note to a signup who did not pay
Hey [name]. You tried [product] after the launch. What stopped you from continuing? If it is price, say so. If it is a missing piece, say which one. I am trying to learn from people who showed up, not from the rank.

Then ask for money the same way you would without Product Hunt. Fifteen minutes. One outcome. Price said out loud. Payment while they still care. A launch spike that dies in your inbox is a missed sale, not a platform failure.

The ask after they try it
If this takes [pain] off your week, it is [price]. I can start you today. Want to do that?

Copy the phrases people used in comments into your landing page. That is free research from people who were willing to type in public. Do not ship a rewrite of the whole product because one browser asked for a feature. Fix blockers to payment. Leave the rest.

A two-week plan where PH is one day

  1. Days 1 to 3. Finish the live product, the price, the payment link, and the one-line offer. Write thirty names. Draft the maker comment and the day-after scripts.
  2. Days 4 to 5. Schedule the Product Hunt page. Fill every field. Record a short demo. Tell your thirty names the date, not only “soon.”
  3. Launch day. Reply all day. Log every real conversation. Send the personal notes. Do not buy votes.
  4. Days after launch (48 hours). Message every commenter and signup. Book calls. Take payment when someone is ready.
  5. Rest of week 1. Rewrite the page with their words. Ship only blockers. Ask every paid user for one intro.
  6. Week 2. Back to named outreach outside Product Hunt. Count paying customers. If you have some, keep the follow-up habit. If you have zero after real conversations, change the offer or the buyer. Do not book another launch to avoid that decision.

Keep the columns simple: name, where you met them, replied, booked, paid, phrase they used. Rank does not get a column. Rank is not a customer.

How you know it worked

Someone explained the problem in their own words. Someone booked time. Someone paid. Someone introduced a peer. Those are the signals. A featured badge, a screenshot of the board, and a week of “congrats” messages are optional side effects.

If the afternoon was quiet, you still have data. The page was unclear, the offer was weak, or the buyers were never on that site. Fix the offer and go where those buyers already talk. Product Hunt is one room. It is not every room.

What to stop doing

  • Treating launch day as the business plan.
  • Building for months with no priced conversations, then hoping PH saves you.
  • Buying upvotes or farming new accounts.
  • Asking only for upvotes instead of tries, objections, and payment.
  • Ignoring commenters the morning after.
  • Relaunching for dopamine when the offer is still untested.
  • Confusing founder applause with a buyer.

Then the week starts

A Product Hunt day can put strangers in front of a clear offer. It cannot replace the notes, the calls, and the ask. Run the afternoon cleanly. Run the follow-up harder. When someone pays and you will put your name on how you got them, send us the story. When the product is real, put it on the map. You can join Indiecity while you do the week. The launch still ends at midnight. The customers come from what you do next.

Until then, schedule the day if you want it. Own the 48 hours after either way.

FAQ

Questions people get stuck on

Should I launch on Product Hunt with zero audience?

You can. Treat it as practice and a feedback room, not a way to skip follow-up. In June 2026, Subhrajyoti Basu launched RadiusHQ without a built audience, climbed from #94 to #20 by talking to people all day, and still said that at #20 you may not get a single client if you are not a known name. Plan the follow-up before you schedule the post.

Is getting featured the only thing that matters?

For homepage traffic, yes: Product Hunt hand-picks a small set of launches each day. JustOneDev wrote in March 2026 that only around fifteen apps get featured. If you are not featured, most visitors never see you. Still, featured traffic is not paying customers. Use the day to collect names and objections, then ask for money after.

When should I launch?

After you have a live product someone can use today, a clear offer, and a way to take payment. Product Hunt’s featuring guidelines say they only feature live products and do not feature waitlists unless people can access the product immediately. For timing, JustOneDev scheduled both featured launches on weekends to avoid stacking against large company launches on weekdays. That is a timing trick, not a customer plan.

What if I get buried?

You still have comments, clicks, and anyone who tried the product. Write every one of them down. Follow up within 48 hours. Rank is a scoreboard for one day. A buried launch with five real conversations beats a high rank you never touch again.

Does a high rank mean I have customers?

No. Rank measures attention from people who browse launches. Customers are people who pay. [Getting your first 10 paying customers without ads](/stories/first-10-paying-customers-without-ads) still means a price, named people, and a direct ask. Product Hunt can put strangers in front of the page. It does not ask them to pay for you.

Should I buy upvotes or use a vote service?

No. Product Hunt says it removes votes it judges non-genuine and watches for unusual patterns. Paid rings and new accounts created for one day get filtered. You waste money and train yourself to chase a number that is not revenue. Spend the energy on people who might buy.

What should I do the day after launch?

Reply to every real comment. Email or message everyone who signed up or left a useful objection. Ask what almost stopped them, fix one thing if it is blocking payment, and ask who else has the same problem. Do not open a new feature branch to celebrate or mourn the rank.

Does this work for B2B?

Product Hunt skews toward products a browser can try in a few minutes. Niche B2B still works if the page is clear and you treat PH as a demo room, not a sales team. Your real buyers are still people you can name in Slack, email, and industry rooms. Use the launch for proof and screenshots. Use the week after for sales conversations.

Can I launch more than once?

Product Hunt allows another launch when there is a significant product iteration. A thin changelog is not enough. Relaunch when something real changed and you again have a follow-up plan. Do not relaunch to re-feel launch day.

How do I know the launch was useful?

People replied with real objections. People booked time. Someone paid, or at least said the price out loud and hesitated for a concrete reason. “Congrats” comments and a badge on the site are not enough. If nothing moves after twenty real follow-ups, change the offer or the buyer. Do not schedule another launch to fix that.

More from the journal