How to Write a Product Hunt Launch Post (With Templates)

Quick summary

• A launch post is a few short fields: URL, name, tagline, description, images and a maker comment. Each field has one job, so do not repeat yourself.
• Start from one plain sentence about who the product is for and what it does. Build every other field from that sentence.
• The tagline says what it does. The description adds one proof point. The maker comment tells the story and asks a real question.
• Write all the copy a week early and test it on someone who has never seen your product.
• Ask people for honest feedback, not upvotes. Vote fishing can hurt you.
• The post only sends people somewhere. Make sure your landing page is ready for them.

What goes into a Product Hunt launch post

Before you write, know the parts. According to Appcues, a post needs four text fields:

• URL. Product Hunt recommends the main URL of your website.
• Title. This is your product name.
• Tagline. A short, marketing-friendly line about what the product does.
• Description. Appcues lists a limit of 260 characters. Limits can change, so check the editor when you build your page.

Then you add images or video, and you write a maker comment. That is the first comment under your post, written by you. Product Hunt's own guide gives it a clear instruction: write like a person, not a press release.

Most guides stop at a list of fields. The harder part is deciding what to put in each one. The next sections give you a method for that.

Start with one plain sentence

Open a blank note. Fill in this sentence:

[Product] helps [specific person] do [specific job] without [the pain they have today].

Here is a made-up example. The product is called InvoiceNest.

InvoiceNest helps freelancers get paid on time without chasing clients by hand.

This sentence is ugly on purpose. It is not your tagline. It is the raw material. Every field in your post should come from it:

• The tagline is a shorter, cleaner version.
• The description adds how it works and one proof point.
• The maker comment explains why you built it.
• The first image shows the job being done.

If you cannot fill in the sentence, the problem is not your copy. The problem is that the product is not clear yet. Fix that first. Browsing launches in your category helps here. Appcues suggests spending time on Product Hunt before you launch, so you can see which tone and content fit your topic.

Write the tagline and description

The tagline

A tagline has one job: a stranger scrolling a list should know what you do in two seconds. Use these rules:

1. Name the job, not the category. Say what the user gets done.
2. Use words your customer would use. Skip invented terms.
3. Cut adjectives. If the line still works without a word, remove it.
4. Say it out loud. If you stumble, simplify.

Here are three versions for the same product.

Write five versions. Pick the one a friend understands fastest. Do not pick the one you like most.

The description

The description is not a second tagline. Use it to add the two things the tagline cannot carry: how it works and one reason to believe you. A simple order:

1. One sentence: what it does and for whom.
2. One sentence: how it works in plain steps.
3. One short line: an offer, a limit, or a proof point.

Example:

InvoiceNest sends polite payment reminders for freelancers, so you stop chasing clients by hand. Connect your invoices, pick a tone, and it follows up on a schedule. Free for your first 20 invoices.

That is about 200 characters, which fits under the 260 limit Appcues lists. If you have no real proof point yet, such as a number of users, do not invent one. An honest offer or a clear limit works better than a vague claim.

Write the maker comment

The maker comment is where most founders write too much or too little. Product Hunt's guide says to write like a person, not a press release. Here is a structure that does that in about 150 to 250 words:

1. Hello and who you are. One line. No résumé.
2. The problem you hit. A real moment, not a market size.
3. What you built. Two or three sentences, matching your tagline.
4. What is rough. Name one thing that is not done yet. People trust you more when you do.
5. One specific question. Ask something people can answer in a sentence.
6. The offer. If you have one, state it clearly.

Here is the middle of a made-up comment:

I invoice about ten clients a month and I hated sending the awkward second email. So I built InvoiceNest to send it for me, in a tone I pick. The reminders work. The part I am least sure about is the templates. Which tone would you want as the default: friendly or firm?

The closing question matters. A question gives people an easy way to start a conversation. Product Hunt says the goal of launch day is real conversation and useful feedback, not a vote count.

Avoid these in your maker comment:

• Starting with a list of features.
• Words like innovative or cutting-edge that say nothing.
• Asking for upvotes (more on that below).
• A wall of text with no line breaks.

Images, video and the offer

Your copy gets read second. Your images get seen first. Appcues looked at highly rated posts and noted that many have animated thumbnails, an incentive such as a free trial, and detailed, relatable comments from the makers. You do not need all three, but they show where attention goes.

A practical image plan:

• Thumbnail. It will be tiny. Test it at small size. If you cannot tell what it is, redo it.
• First gallery image. Show the finished result, not a login screen. Put your tagline on it in plain text.
• Second and third images. One screenshot per step of how it works.
• Short demo. Keep it to the one job in your sentence. A short clip of the real product beats a long tour.
• Use real screenshots. Mockups with made-up data feel thin. Use realistic sample data instead.

Then add an offer if it makes sense for your business. A free tier, extended trial or launch discount gives people a reason to try it today. Write it in one line and use the same line in your description and maker comment, so people see it every place they look.

Ask for support without begging for upvotes

A good post still needs people to see it early. Plan this before launch day.

The sources agree on one thing: do not play games. Demand Curve says Product Hunt's algorithm demotes posts that look like they are fishing for votes, for example when many votes come from newly created accounts. Swipe Files lists these as things to avoid: buying upvotes, asking for upvotes on social media, having people create accounts on the day, and making second accounts.

What to do instead:

• Build a small audience first. Both of those guides say Product Hunt works better as a boost for an existing audience than as your first marketing effort.
• Write to people you already know and who already know the product.
• Ask for feedback, not a click. Product Hunt's guide gives an example of a good ask: a specific comment like "we built our whole onboarding on X, and it saved us weeks" is far more useful than "Great tool!"

Here is a short message you can adapt:

Hi Sam, I am launching InvoiceNest on Product Hunt tomorrow. You told me chasing invoices was your least favorite task, so I would love your honest take. If you try it, a comment on what worked or did not would help me more than anything. Link: [your post URL].

Notice what it leaves out. It does not say upvote. It gives a reason the person should care and a specific thing to do.

Pre-launch checklist and common mistakes

Use this list a few days before you go live. For a wider plan, see our SaaS launch checklist, or run your product through the Launch Readiness Grader.

Copy

• The one-sentence version is written and a stranger understands it.
• The tagline names the job and the person.
• The description is under the field limit and adds how it works plus one honest proof or offer.
• The maker comment ends with a specific question.

Visuals

• The thumbnail reads at small size.
• The first image shows the result.
• Every screenshot uses realistic data.

Landing page

• The page you link to matches your tagline. People should not have to hunt for the thing you promised.
• Sign-up works on a phone. Test the full flow yourself.
• The page title and description are set. Our Meta Tag Checker takes a minute.

People

• You have a short list of people who know you and will give honest feedback.
• You have told them the date and time in advance.
• If you have a team, you have agreed who is online and when.

Mistakes to avoid

1. Writing a category, not a job. A line like AI productivity platform tells people nothing.
2. Repeating the tagline in the description. Use the extra space for something new.
3. Launching the day after a big announcement. Swipe Files warns that you will have used up your social capital by then.
4. Treating the post as the finish line. The post sends people to your site. If the site is weak, the launch will not fix it.
5. Testing your own copy only on yourself. You already know what the product does. Show a stranger.

Timing and launch day

Two timing points come up in the guides. Swipe Files suggests scheduling your post for 12:01 AM Pacific Time, and says Tuesday to Friday are better than Mondays and weekends. That is one author's experience, so treat it as a starting point and look at the days your own audience is active.

On launch day, Product Hunt's guide says the most important thing is to be there:

• Reply to every comment you can, close to real time.
• If you have a team, split the day so someone is online, including overnight in your time zone.
• Answer hard questions plainly. Thank people.
• Where it helps, reply with a short demo or a live link instead of a long paragraph.

The leaderboard moves based on upvotes, comments, time since launch and other signals, and Product Hunt does not share the formula. So do not spend the day refreshing your rank. Spend it talking to people.

After the day ends, keep going. Product Hunt says people keep finding your launch for days. Follow up with the people who showed interest, collect the feedback, and compare your results to the goals you set. Write down what worked so your next launch is easier.

Product Hunt is one channel among many. If you are still deciding whether it fits, read is Product Hunt worth it, and compare Product Hunt alternatives and where to launch your startup. To find your first users after launch, see how to get your first 100 users.

Sources

• 4-Step Product Hunt Launch Guide, Appcues
• Build your product page, Product Hunt Help Center
• What to do during and after your launch, Product Hunt Help Center
• In-depth Product Hunt launch guide, Demand Curve
• How to Launch on Product Hunt, Swipe Files

Frequently asked questions

How long should a Product Hunt launch post be?

Keep every field short. The description has a character limit (Appcues lists 260, so check the editor). The maker comment can run a little longer, about 150 to 250 words. Short, clear and specific beats long.

Do I need a hunter to post my product?

No. A hunter is someone who posts on your behalf. Swipe Files says hunters matter less than they once did and suggests thinking of one as influencer marketing. A hunter helps only if they have real overlap with your audience and bring some credibility.

Should I ask people to upvote my launch?

No. Ask for honest feedback and real comments instead. Demand Curve says the algorithm demotes posts that look like they are fishing for votes, and Swipe Files lists asking for upvotes on social media as something to avoid.

What time should I launch?

Swipe Files recommends scheduling for 12:01 AM Pacific Time and favors Tuesday to Friday over Mondays and weekends. Use that as a default. Then adjust to when your own audience is online.

What should I do if the launch does not go well?

Read every comment, note what you learned, and compare results with your goals. Then keep going on other channels. Our guides to best startup directories and free SaaS directories for backlinks are good next steps.