Launches and Product Hunt: give the attention somewhere to go

A launchA short period when several distribution actions point toward one release and one main customer action. It includes the page and route after the announcement, the support provided while people arrive and the follow-up afterward. date has a strange ability to make one day feel like a public ruling on whether your product and/or company should exist. You prepare the posts, open Product HuntA technology-product discovery platform where makers can submit products and the community can view, discuss and vote on them. The homepage shows featured products by default, neither a feature nor a rank is guaranteed and Product Hunt doesn't publish how its ranking algorithm works. in seventeen tabs and wonder why you're suddenly invisible online.

Your first launch is your first attempt to put the product in front of people and see what happens next. It might give you a few things: customers (though don't be disheartened if this doesn't happen), specific questions, a broken signup route, one excellent introduction or almost no response. Recording what happened, and understanding why, gives you something to use for the next launch (because yes, you'll absolutely have more than one).

The earlier chapters helped you choose a customer and ways to reach them. A launch brings some of those actions together around one release. The announcement is the visible part; the result depends on what somebody can do after they click.

Decide what you want the launch to do

Choose one main job before you choose the platforms, posts or graphics. You might want to:

• invite a small group to test an early version;
• find your first users or customers;
• hear questions from a defined group;
• start sales conversations;
• grow a waitlist for later access;
• announce that the product is available;
• give partners, journalists or referrers a reason to talk about it; or
• create a permanent page on a relevant marketplace or directory.

Several things may happen, but one should determine your main launch webpage and the main action you want people to take. An early test might ask somebody to use the product and report a problem. A low-cost product might ask them to try or buy it. A high-price business product may ask them to book a conversation, because the price dictates that a customer needs answers before making a larger commitment.

If the marketing page gives equal weight to trying, buying, joining a waitlist and booking a call, the visitor receives a confusing admin puzzle and you'll lose them.

Name the kind of launch as well, because it changes who you invite and how much support you need.

Most first launches will be a private test, a soft public launchA release announced to a limited public audience in one or two relevant places. The founder keeps it small enough to stay close to questions, problems and early use. or a first general releaseThe first time the product is made broadly available through the routes the founder has chosen. “General” describes availability; it doesn't require the founder to announce it everywhere.. The labels set the audience, invitation and support needed for the product you have.

Can somebody get all the way through?

A launch can include rough edges; it still needs an honest statement of what your product will do for the person buying into it, and a route to that product which works well enough for the number of people you're inviting.

Before you announce anything, answer these five questions:

1. Can the intended customer understand what the product helps them do?
2. Can they try it, join, book or buy?
3. Does that route work from the first click to the promised next step?
4. Can you answer questions or fix a problem when people arrive?
5. Will you know where they came from and what they did next?

If the product handles private data, money, health information or important business operations, make sure your reassurance layer is specific and explicit, as well as within your website terms.

Delay the launch, or make it smaller, when the customer is still unclear, the route is broken, the page makes a claim you can't support, or you don't have the capacity to provide customer support. Unresolved legal, privacy, security, customer-permission or safety issues are reasons to stop. So is exhaustion - taking time out is no bad thing.

Pick a few places according to your time

The first distribution route you already chose should usually lead the launch, because that's where you've been learning how to reach the customer. If you're comfortable, confident, and established on other platforms, consider those your announcement places, too.

Ask whether the intended customer spends time there, whether you have a legitimate way to participate or contact people, what material you already have, how much time replies will require and what the place contributes that the others don't. One community and a small email list may be plenty. Seven scheduled posts can create the thrilling sensation of being everywhere while leaving you unable to help anyone.

LinkedIn, email, Reddit, X, specialist communities, partners, marketplaces, directories and Product Hunt are all possible places. Their detailed mechanics belong in the later channel chapters. For this launch, choose only the ones you can explain and support.

When Product Hunt should be a priority

If your product is made for a specific technology audience, especially developers, Product Hunt should be high on the list. Product Hunt describes its community as product enthusiasts, makersProduct Hunt's term for a person who helped create the product being launched. A maker may also submit, comment on and answer questions about the product., technology workers, entrepreneurs, investors and early adopters, so a developer, AI, design or productivity tool may meet people who can understand and try it quickly. That overlap matters more than the prestige of appearing there. (Product Hunt, accessed September 2026)

A backend product may also fit. Developers can understand an API or infrastructure tool through one good example even when there is little interface to admire. The question is whether the right person can grasp the use and take the next step.

Product Hunt rules to check

The following rules come from Product Hunt's official guidance and were checked on September 16, 2026. Recheck the live guide before you launch because platform rules change.

• Use a personal account; company accounts aren't permitted. (How Product Hunt works)
• A new account currently needs to exist for at least one week before it can submit a product. (Before launch)
• You can submit your own product, and Product Hunt encourages it. Paying somebody to hunt your product goes against its guidelines. (Before launch)
• You can currently schedule a launch up to one month ahead. (Preparing for launch)
• Product Hunt says there is no guaranteed best day. A 12:01 a.m. Pacific start provides the full daily cycle, but choose a time when your audience is around, and you can respond. (Preparing for launch)
• The homepage shows featured products by default, and its leaderboard changes throughout the day based on upvotesA Product Hunt community vote for a product. Product Hunt permits founders to share their launch and ask for feedback, but its current rules prohibit asking for upvotes, coordinating votes or rewarding people for voting., comments, time since submission and other factors, so neither a feature nor a rank is guaranteed. Product Hunt doesn't publish how its ranking algorithm works. (How Product Hunt works)
• You may share the launch and ask for feedback, comments or help spreading the word. Don't ask for upvotes, coordinate voting, mass-message people, use bots or reward votes. (Sharing your launch; Community Guidelines)
• A promotion is allowed when it encourages people to use the product and isn't tied to voting. (Sharing your launch)
• A Product Hunt relaunchA later launch that gives people a meaningful reason to reconsider the product, such as a substantial new capability, corrected route or new use. Product Hunt applies its own relaunch rules, which currently usually require a significant update and a six-month gap. normally needs a significant update and a six-month gap. An earlier relaunch requires review and still isn't guaranteed to be featured. (Can I relaunch my product?)

These rules remove several bits of launch folklore. Your time belongs with the product, an honest invitation to use it and the people who arrive, while the celebrity hunterThe person who submits a product to Product Hunt. Founders can submit their own product and don't need to pay or recruit a well-known hunter. and voting platoon can remain safely unemployed.

Prepare the small set of things the launch needs

Keep the preparation small enough to finish:

• One page that explains who the product is for, what it helps them do and what happens next.
• One main objective from your users such as try, join, book, buy, reply or request a conversation.
• One clear demonstration or piece of evidence that supports what your product does.
• A working route through signup, checkout, booking, download or access, tested from beginning to end.
• A reply and support plan for the questions and problems that may arrive.
• Simple tracking that connects a person to the announcement they saw, through a link, referral question or basic record.

The work you collected in the previous chapter may supply the demo or explanation. It gives you something more substantial to say than “we're thrilled to announce,” a sentence that has survived many launches without helping anybody actually understand the product.

Before, during and after

Before the launch, test the full route, prepare the selected material and tell relevant customers or contacts what is happening, encouraging them to support you if they're able. Leave enough space to fix any problems that pop up on the day.

There's no universal runway or magic weekday; work backwards from what has to be ready and choose a time when the audience (and you!) are available.

During the launch, announce the release in the few places you selected, respond to anyone who engages and watch for repeated questions. Repair anything that prevents somebody from understanding or taking action on your product.

Afterward, follow up with intended customers, record where they came from and what they did, and check whether new users began using the part of the product that delivers the result. Your priorities are to respond to the right people, repair the place where they couldn't continue, then record what changed or what you learned.

A small launch isn't a bad thing

Even minimal activity can make a launch worthwhile when it produces a specific learning. “Marketing is hard” changes nothing. “Three developers reached the permissions screen and stopped because the repository access was unclear” gives you something to repair. There is no universal benchmark for Product Hunt traffic, signups, rank or revenue, and a high rank with no product use is still attention without the action you chose.

Like everything in the go-to-market process, you don't know what'll happen on launch day until you're at launch day. I'm a big fan of launching a product multiple times, taking each learning forward to make the next version better.

You can launch again

A later launch may introduce many things: a stronger product, corrected onboarding, a clearer audience, a new customer use case, or a release that gives people a reason to reconsider it. Don't assume that people will remember the last one; living in an attention economy, it's completely plausible that a tweak in messaging or positioning will present yourself to your audience as a brand-new product.

You can keep releasing through your own channels whenever there's a good reason. Product Hunt has separate relaunch rules, which currently require a significant update and usually a six-month gap, so check them before submitting the product there again. (Product Hunt, accessed September 2026)

Example: the first launch for a developer tool

Imagine a tool that alerts a development team when an API change may break one of its integrations. The first launch has one job: recruit a small number of developers who will connect a test repository and report where the warning is unclear.

The founder chooses Product Hunt because the intended user overlaps with its technology audience, a small developer email list and one community where they already participate. The main action is to connect a test repository. Before the launch, the founder tests that route, writes a plain explanation of the access requested, prepares a short demonstration and keeps the audience small enough to answer security questions.

The result fields remain blank until something happens. A connected repo would show product use. A security question would reveal a trust requirement. A comment from somebody who doesn't use the product may still be thoughtful, although its route to the customer is uncertain. A high Product Hunt rank with no connected repositories would show attention without the chosen action.

Your first-launch brief and record

Complete the first-launch brief and record before you prepare ten versions of the announcement. It asks for the release, intended customer, one main job, customer action, readiness checks, announcement places, Product Hunt fit, support plan and blank response fields.

Preparing that brief completes the chapter; launching can wait until you resolve the checks and choose the date. The next chapter covers Reddit, including how to participate without arriving in a community and immediately behaving like a pop-up ad.

Prompt: prepare my first launch

Use this prompt with your distribution decision, product facts and supplied tone of voice. It prepares the launch for your review; it must not publish, schedule, send or submit anything.

I want to prepare a small, credible first launch.

My existing distribution decision
- Intended customer: [specific customer]
- User, buyer and approver: [same person / different people / I don't know]
- First distribution route: [channel or route already chosen]
- Time I can give preparation: [hours or days]
- Time I can protect for replies and support: [hours or days]

The release
- Product or change: [what is ready]
- What it helps the customer do: [plain description]
- Launch type: [private beta / soft public / first general release /
  substantial relaunch / I don't know]
- One main job for this launch: [test / find users or customers / hear
  questions / begin sales conversations / grow a waitlist / announce general
  availability / help partners or referrers share it / create a permanent
  marketplace or directory page]
- One action I want one person to take: [try / join / book / buy / reply /
  request a conversation / another named action]

What is ready
- Page or explanation: [link or text]
- Demonstration or evidence: [link, file or details]
- Signup, payment, booking, download or access route: [steps and test result]
- Onboarding: [what happens after the action]
- Reply and support plan: [who, where and when]
- Tracking: [links, referral question or record]
- Permissions and approvals: [customer, partner or third-party approval]
- Privacy, security, legal or safety checks: [details / not relevant / unknown]
- Product Hunt account and eligibility: [details / not using Product Hunt]
- Current Product Hunt rules supplied from the official guide: [rules and date]

Tone of voice
- Voice description or approved examples: [paste these]
- Words, claims or styles to avoid: [paste these]

Your task
1. Separate the facts I supplied from assumptions and missing information.
2. Confirm or correct the launch type and name its one main job.
3. Check whether the intended customer can understand the product, take the
   chosen action, complete the route and receive help.
4. Flag broken or missing signup, payment, booking, download, access,
   onboarding, support, evidence, permission, privacy, security, legal or
   safety work. Recommend delay or a smaller launch when the problem could
   harm somebody or waste the invited attention.
5. Recommend no more than three announcement places. Use fewer when my time is
   limited. For each one, explain why the customer is there, what it adds and
   how much response time it needs.
6. Prioritize Product Hunt when the product fits a specific technology
   audience, including developers. Apply only the current rules I supplied or
   rules you can verify in Product Hunt's official guide.
7. Reject vote requests, coordinated voting, artificial scarcity, unsupported
   claims and invented customer proof.
8. Choose one approved launch idea, then adapt it for each selected place in
   my supplied tone of voice. Preserve the meaning across every adaptation.
9. Prepare a before, during and after plan that protects time for replies,
   repairs and follow-up.
10. Create blank result fields. Don't predict traffic, votes, signups, rank,
    revenue or sales.
11. Explain what a small but informative response could help me change. A
    learning must name what happened and the next decision it affects.

Rules
- Don't invent a customer, quotation, result, urgency, endorsement, product
  behavior, platform rule or opinion.
- Don't publish, schedule or send anything, create an account, contact
  supporters or submit the product to Product Hunt.
- Don't ask for, coordinate or reward Product Hunt votes.
- Don't turn rank, traffic or comments into proof of demand.
- Don't use a universal launch runway, best day, conversion benchmark or
  revenue benchmark.
- Use American English, plain language and my supplied tone of voice.

Return exactly these headings
## Facts supplied
## Assumptions
## Missing or broken
## Launch type and one main job
## Can somebody get through?
## Announcement places
## Product Hunt check
## Before
## During
## After
## Drafts for approval
## Blank response record
## What a small response could teach me
## Launch, shrink, delay or cancel

Check every draft against your product facts and route before it leaves your notes. A model can organize the launch; it can't decide that a claim became true because the date arrived.

Sources

• Product Hunt. “Launch Guide.” Accessed September 16, 2026.
• Product Hunt. “How Product Hunt works.” Accessed September 16, 2026.
• Product Hunt. “Before launch.” Accessed September 16, 2026.
• Product Hunt. “Preparing for launch.” Accessed September 16, 2026.
• Product Hunt. “Sharing your launch.” Accessed September 16, 2026.
• Product Hunt. “Community Guidelines.” Accessed September 16, 2026.
• Product Hunt. “Can I relaunch my product?” Accessed September 16, 2026.