BestPromptFor XYZ Prompts for anything.

Best prompts for a Product Hunt launch

AI prompts for a Product Hunt launch. Write the listing and maker comment. Plan the gallery. Research nearby launches before you go live.

Product Hunt gives you one day and a thin strip of text. Hunters read the tagline, glance at the first frame, then decide whether your comment is worth a reply. The form looks small. Filling it out well still takes a week of prep. These prompts follow the launch in order. First you look at who already shipped nearby. Then you fill the listing, plan the shots, and write the pinned comment in your own voice. When someone asks how you differ from a tool they already use, you have a fair answer ready.

7 prompts

Start here a week out. Nearby launches show which taglines got ignored and which complaints keep coming back.

Act as a researcher reading Product Hunt launches that sit near my product. Goal: Find nearby Product Hunt launches for [PRODUCT NAME] and turn them into a short brief. Context: - What I ship: [ONE LINE] - Category or topics I have in mind: [TOPICS] - Closest products I already know: [NAMES OR NONE] - What I want to learn: [TAGLINES, COMPLAINTS, TOPICS, OR ALL] - Time window (optional): [LAST 2 YEARS, OR LEAVE BLANK] Success criteria: - Use live search. If a page cannot be opened, mark it as UNVERIFIED - 5 nearby launches - Separate facts from guesses - No invented comment quotes Instructions: 1. Search Product Hunt for [TOPICS] and for [NAMES OR NONE]. 2. List 5 nearby launches. For each one include: - Name and URL - Tagline as published - Launch date if shown - Topics if shown - One real comment complaint, quoted short, or NONE FOUND 3. Group repeated complaints into themes. Two to four themes. Each theme needs two source names. 4. List topics that keep appearing. 5. Write 4 implications for the listing. Number them. Each one should point back to a launch or a theme. Output format: Return sections 1-5 in order. Use those numbers as headings.

How to use

  1. Fill [TOPICS] with the category you would launch under, even if it feels crowded.
  2. Add a product you fear in [NAMES OR NONE]. The brief is better when the scary one is in the set.
  3. Save the complaint themes. They feed the competitor prompt later.

Tips

  • Read the comments on the closest launch yourself. The model will miss tone.
  • If every nearby product promised the same outcome, your tagline needs a sharper user.

For best results, give your AI access to:web search

Example output

2. Nearby launches (excerpt)
- MeetAction / [url]
  Tagline: Action items from your standup
  Date: March 2025
  Topics: productivity, meetings
  Complaint: "It invented owners I never named."

3. Themes
- Fake precision: MeetAction, NoteFold
- Setup time: MeetAction, StandupBox

5. Implications
1. Say what the tool refuses to guess. MeetAction comments punish invented owners.
2. Keep the first action at one paste. Setup time is a repeated complaint.

The feed only shows a name, a tagline, and a short description. This prompt fills those fields to the character limits Product Hunt actually uses.

Act as an editor who writes Product Hunt listings that strangers can understand in a few seconds. Goal: Draft the listing fields for [PRODUCT NAME]. Context: - What it does today: [WHAT IS LIVE NOW] - Who it is for: [WHO SHOULD CARE] - Problem it solves: [THE JOB THEY ARE STUCK ON] - Proof I can show: [A RESULT, A NUMBER I REALLY HAVE, OR LEAVE BLANK] - What is still unfinished: [KNOWN GAPS] - Why I built it: [THE MOMENT THAT STARTED THIS, OR LEAVE BLANK] - Words I never use: [HYPE WORDS TO SKIP, OR LEAVE BLANK] - Offer for this launch (optional): [LAUNCH DEAL OR LEAVE BLANK] Success criteria: - A stranger can tell what it does after the tagline - The description stays inside 260 characters - Every claim comes from the context I gave - The first-comment seed talks about why I built it. Product facts stay in the listing fields. Instructions: 1. Write the name field. [PRODUCT NAME] in 40 characters or fewer. If the name already fits, keep it. 2. Write 3 tagline options. Each must be 60 characters or fewer. Print the character count in parentheses after each line. The printed count does not count toward the limit. 3. Pick the strongest tagline and say why in one sentence. 4. Write one description of 260 characters or fewer. Put who it is for and what they get in the first line. Print the character count. 5. Suggest 3 Product Hunt topics. After each topic, add one short reason. 6. Write a first-comment seed of 80 words or fewer. First person. End with one question a visitor can answer. Do not ask for an upvote. Output format: Return sections 1-6 in order. Use those numbers as headings. Style rules: - Short sentences. Everyday words. - Do not write AI-powered or leading. - No em dashes. Use a period. - Do not list three things in one sentence. A plain list of facts, such as language names, is not a marketing list and is fine. - Use spoken connectors. Start some sentences with And or But. So is fine too. - Do not use the contrast pattern that names one thing then says not the other. - Cut any line that could sit on any other product. - If a field marked optional is blank, skip it and say nothing about it. - If any other context field is blank, write UNCLEAR and ask one question. Do not invent a user or a result.

How to use

  1. Fill [WHAT IS LIVE NOW] with what a stranger can click today. Skip the roadmap.
  2. If you have one real number, put it in [A RESULT, A NUMBER I REALLY HAVE, OR LEAVE BLANK]. Leave the field empty if you do not.
  3. After the draft, paste the winning tagline into the maker-comment prompt if you want the full pinned comment.

Tips

  • Count characters in the form before you submit. Chat tools sometimes miscount spaces.
  • If every tagline sounds clever, ask for a dull version that names the user and the outcome.

Example output

1. Name
DeskClear

2. Tagline options
- Turn meeting notes into next actions (41)
- Next actions from messy meeting notes (40)
- Meeting notes that end as a task list (40)

3. Pick
Option 2. It names the mess and the output.

4. Description
DeskClear takes pasted meeting notes and returns three next actions with owners. Built for people who leave a call with a wall of text and no idea who does what. (158)

5. Topics
- Productivity: the job is getting out of a meeting with a plan
- Meetings: the input is notes from a call
- SaaS: it is a small software tool

6. First-comment seed (excerpt)
I kept walking out of calls with two pages of notes and zero owners. I built DeskClear for that Friday feeling. What would you want it to pull out of a messy note first?

The listing is the product. The first comment is you. Pin it in the first minutes so the thread has a human at the top.

Act as a maker writing the first comment on their own Product Hunt launch. Goal: Write a pinned first comment for [PRODUCT NAME]. Context: - Why I built it: [THE MOMENT THAT STARTED THIS] - What is live today: [WHAT A VISITOR CAN TRY] - What is still unfinished: [KNOWN GAPS] - Who I want to hear from: [THE PERSON WHOSE REPLY WOULD HELP] - One thing I want them to try: [A CONCRETE CLICK OR TASK] - Voice: [DRY, WARM, BLUNT, OR PASTE TWO SENTENCES I WROTE] - Tagline already published: [MY TAGLINE, OR LEAVE BLANK] - Optional launch note: [PRICE, DEAL, OR LEAVE BLANK] Success criteria: - 150 to 220 words - First person - A reader knows who I am and what to click - Ends with one question they can answer from their own work - Never asks for an upvote or a hunt Instructions: 1. Open with the moment in [THE MOMENT THAT STARTED THIS]. Two or three sentences. 2. Say what is live in plain words. One short paragraph. 3. Name one gap from [KNOWN GAPS] so the comment still sounds like a work in progress. 4. Point to [A CONCRETE CLICK OR TASK]. 5. Close with one question for [THE PERSON WHOSE REPLY WOULD HELP]. 6. If [PRICE, DEAL, OR LEAVE BLANK] is filled, add one sentence for that. Keep it after the story. Output format: Return the comment ready to paste. Then add a Cuts list with two lines you would delete if it runs long. Style rules: - Sound like a person at a keyboard. - The public tagline already exists. Tell the story behind it. - No em dashes. Use a period. - Do not list three things in one sentence. A plain list of facts, such as language names, is not a marketing list and is fine. - Use spoken connectors. Start some sentences with And or But. So is fine too. - Do not use the contrast pattern that names one thing then says not the other. - Cut any line that could sit on any other product. - Do not quote the tagline back. It already sits above the comment. - If a field marked optional is blank, skip it and say nothing about it. - If any other context field is blank, ask one question before writing.

How to use

  1. Write [THE MOMENT THAT STARTED THIS] as a real scene. A Tuesday standup works. So does a customer email you were tired of answering by hand.
  2. Run it twice if the first draft sounds like a press release. Ask for the drier version.
  3. Paste this at launch. Reply to real comments in your own words.

Tips

  • Post it in the first few minutes so it sits at the top.
  • If people ask how you differ from another tool, use the competitor prompt for that reply.

Example output

I used to leave Monday standups with two pages of notes and no owners. By Thursday I could not tell who owed what. I built DeskClear after I missed a follow-up that was sitting in that pile.

Paste a note and it gives you next actions with names. The assign step is still rough. Pricing is a guess.

If you have a messy note from last week, drop it in and see whether the actions feel true.

What would you want it to pull out of a messy note first?

Cuts
- Pricing is a guess.
- The Thursday line.

Someone will name a tool they already pay for. Keep this reply ready so you can answer without picking a fight.

Act as a product writer who answers comparison questions without picking a fight. Goal: Write a fair answer to "How is this different from [COMPETITOR]?" Context: - My product: [PRODUCT NAME AND WHAT IT DOES] - Their product: [COMPETITOR NAME AND WHAT I BELIEVE IT DOES] - Who I am building for: [MY USER] - Overlap I already admit: [SHARED JOBS] - Proof I have: [A FACT I CAN STAND BEHIND, OR LEAVE BLANK] - Where I have not used their product: [GAPS IN MY KNOWLEDGE] - Where this answer will go: [PRODUCT HUNT COMMENT, LANDING PAGE, OR EMAIL] Success criteria: - Name the shared job first - Name one job they are better at - Name one job we are better at - Do not invent a feature - The short reply fits a comment thread Instructions: 1. Restate the shared job in one sentence. 2. Write three labeled lines. Do not repeat the shared job here. - They are stronger when - We are stronger when - I still need to verify 3. Write a comment-length reply (80 to 120 words). Use first person if [WHERE THIS ANSWER WILL GO] is a Product Hunt comment. 4. Write a shorter 2-sentence version for a listing or a bio. 5. List questions I should answer first, based on [GAPS IN MY KNOWLEDGE]. Output format: Return sections 1-5 in order. Use those numbers as headings. Style rules: - Keep the tone even. - If I have not used [COMPETITOR], say that once. - Skip lines that say we are them with extra features. - Short sentences. Everyday words. - No em dashes. Use a period. - Do not list three things in one sentence. A plain list of facts, such as language names, is not a marketing list and is fine. - Use spoken connectors. Start some sentences with And or But. So is fine too. - Do not use the contrast pattern that names one thing then says not the other. - Cut any line that could sit on any other product.

How to use

  1. Fill [SHARED JOBS] even if it stings. The reply gets weaker if you hide the overlap.
  2. If you only know the competitor from their site, say so in [GAPS IN MY KNOWLEDGE].
  3. Paste a real comment under [WHERE THIS ANSWER WILL GO] if you are answering someone.

Tips

  • The line that names when they should stay with the other tool is the one people trust.
  • Update the answer after you actually try their product.

Example output

1. Shared job
Both turn a pile of text into something you can act on.

2. Lines
Shared job: notes to next steps
They are stronger when: you already live in their editor all day
We are stronger when: you want actions from a paste and then you leave
I still need to verify: their assign flow. I have only used the public docs.

3. Comment (excerpt)
I have not used NoteTaker Pro day to day. From their site they look built for people who write and stay in one editor. DeskClear is a paste box for after a call. If you want a home for all of your notes, they are the better pick. If you want three actions and an owner, try us and tell me what it missed.

4. Short
NoteTaker Pro is a home for notes. DeskClear is the five minutes after the meeting.

5. Before you post
Have I clicked their assign feature?

If friends still ask what it does, run the product through ELI5 and steal one line for the tagline.

ELI5: [PASTE TEXT OR TOPIC]

How to use

  1. Replace [PASTE TEXT OR TOPIC] with anything you want explained in simple words.

Tips

  • Best for a first simple explanation before you ask for deeper detail.

Example output

Sourdough starter is like a tiny pet that eats flour and water.

When it is happy and bubbly, it helps bread rise and gives it that tangy bakery smell.

Paste the tagline, the first comment, and the About line. Ask it to poke holes a hunter would notice at midnight.

Red Team: [PASTE TEXT OR IDEA]

How to use

  1. Replace [PASTE TEXT OR IDEA] with a draft, plan, decision, offer, or argument.

Tips

  • Best when you want a direct critique before you act on something.

Example output

The birthday treasure hunt sounds fun, but the clues may be too hard for six-year-olds.

Make each clue point to something visible in the room, and keep one adult ready with hints.

Related collections