Product Hunt launch checklist for solo developers

Product Hunt is the one directory almost every solo developer has heard of, and the one where a rushed submission costs the most, because the launch day is a fixed moment and everyone you know will look at the page. This checklist is written for the person who builds, markets and launches alone, with no team to review the copy at midnight. It is based on our own submission of seomap.dev, documented in the public Product Hunt field guide, plus the representation briefing that ships in the LaunchRepo repository. Where a number appears, it is what the form showed on the observed date — Product Hunt changes its forms, so recheck before you paste anything final.

One expectation up front: the checklist gets you to a scheduled launch with honest copy and real images. It does not promise upvotes, a homepage position or traffic. Nobody can, and the tactics that claim to are the ones the platform rules forbid.

Before you touch the form

• Search first. Look for your product name and domain on the public site and in “My Products” while signed in. An older draft or a listing someone else created is a duplicate waiting to happen. The tracker states article explains why we record already_listed separately.
• Decide who the maker is. Product Hunt launches are maker-led. Set up a personal profile with a real name or the nickname you actually use, a photo and a one-line bio. If your company account and your personal account are different things, decide now which one will be attached.
• Run the representation briefing. The repository’s PR-BRIEFING.md asks three questions before any personal fact reaches a public listing: individual, company or both; which name, nickname and affiliation may appear; and what must never be said about you. Then it drafts a one-line maker bio, a one-sentence launch intro and a one-sentence “why I built this” and shows them to you verbatim for correction. Approve, correct, save. As a solo developer you are the only reviewer, which is exactly why it helps to look at the three sentences on their own instead of inside a form.
• Write down the product facts, not the wishes. Audience, the problem, what exists today, pricing as it is, launch stage. A trial with limited credits is not a free plan. Planned features stay out of the description.

Copy: the limits we observed

On the observed date, the submission form allowed a 60-character tagline and a 500-character description. Both are shorter than most people’s first draft, and both are where the honest version of your product has to fit.

• Tagline ≤ 60 characters. One benefit, in plain words. Count it — “AI-powered” and a product-name repeat eat a third of the budget for nothing.
• Description ≤ 500 characters. Who it is for, what it does, what it costs. No customer counts, revenue, awards or integrations you cannot point to.
• Prepare variants. The LaunchRepo copy workshop produces copy.md with versions for different field limits, so the 60-character tagline for Product Hunt and the different limit on the next directory come from the same approved facts instead of being rewritten at the last minute.
• Recheck the limits on the day. They were 60 and 500 when we looked; treat that as a data point, not a rule.

Assets: real, current, yours

• Logo in the requested size, on a background that survives a dark card.
• Gallery images from the actual product. Screenshots of what a user sees this week, not a mockup of the redesign. If the product has a video, add it; if it does not, do not fake a thumbnail.
• Product URL that resolves and matches the name and domain on your maker profile.
• Category that a stranger would pick for you. The form uses native selects; verify the value actually selected after scrolling, because in the observed run the selection could silently differ from what appeared highlighted.

Pricing and the honesty checks

Product Hunt asks how the product is priced. A paid product with a trial should be represented as paid with a trial, not as “free”. This sounds obvious until a launch page says “free” and the first comment asks why the signup wants a card.

Two things the field guide is explicit about, and the repository’s AGENTS.md repeats for every directory:

• No upvote solicitation. Do not ask friends, communities or customers to upvote; do not buy engagement; do not run a “support us on Product Hunt” campaign that reads as a vote request. Tell people you launched and let them decide. This is a platform rule, and the tracker treats manufactured votes or comments the same way it treats invented testimonials: forbidden.
• No invented testimonials. Quotes go on the page only if a real person said them and agreed to be quoted.

The launch date: deliberate, not immediate

The single most useful thing a solo developer can do on Product Hunt is to choose the date instead of clicking “launch now” because the form is finally filled in.

• Set your earliest launch date. In LaunchRepo this lives in product.json as earliest_launch_date; the tracker refuses to record a platform as scheduled before that date. If your website, pricing page or onboarding is not ready, that date is later than today.
• Choose a day you can be online. A solo launch means you answer comments yourself. Pick a day with no client deadline, not a day you will be travelling.
• Confirm the time zone. The observed workflow showed a date and a time zone on confirmation. Record both. A launch scheduled at “00:01” is a different day in Pacific time than in Berlin.
• Do not count a saved draft as scheduled. The field guide makes this distinction on purpose: a draft is work saved; scheduled is the account confirming a date. Only the second one belongs in your tracker as scheduled, and it still says nothing about whether the page will be featured or where it will appear.

What “scheduled” means, and what it does not

In our own run, the Product Hunt workflow reached a scheduled launch. That confirms a date. It does not confirm publication, homepage placement or any visibility. On launch day, the guide’s outcome step is to open the public product page and inspect it before recording live — because live in the LaunchRepo tracker requires a verified public URL and your explicit confirmation, not a calendar entry.

This matters more on Product Hunt than on most directories, because the gap between “I scheduled it” and “people can see it” is exactly the gap solo developers tend to announce across. Announce on the day, from the public page.

Launch day for one person

• Open the public page first thing. Check the tagline, the images and the maker attribution rendered as intended.
• Post the approved launch intro — the one sentence from the representation briefing — where you normally talk about your work. No vote request.
• Answer every comment yourself, in your own words. It is the one place where being a single maker is an advantage.
• Record the outcome honestly. Live with the public URL if the page is public; scheduled with a note if it is not yet; whatever actually happened if something went wrong. The status tracking guide covers the edge cases.

After the day

Product Hunt is one directory in a catalog of 346. The playbooks in the repository treat it like the others: search first, verify identity, prepare copy within the limits, confirm nothing costs money, submit only within your authorisation, record what you observed. A solo developer who has done that once for Product Hunt has already done the hard part for the next platform — the facts, the copy variants and the assets are reusable, and the walkthrough with Claude Code shows how an agent runs the rest of the list from the same files.

If you are picking which directories come next, best startup directories 2026 groups the catalog by category, and the indie hackers page describes the setup for a one-person launch. The repository itself — playbooks, product template, tracker, local dashboard — is bought once on the pricing page.

Sources: the public Product Hunt field guide (form limits and workflow as observed on 2026-09-13), PR-BRIEFING.md, ONBOARDING.md, AGENTS.md and RUNBOOK.md in the LaunchRepo repository. No upvote, ranking or traffic figures are given because none were measured, and none are promised.