What the Top Product Hunt Launches Did Before Launch Day

What did the top Product Hunt launches do before launch day?

The sources read for this page show a pattern of early audience building, account preparation and day-of planning, but they do not show a dated record for any specific launch. What they offer is one detailed prescription and a set of public launch-day posts and emails.

• The one detailed plan starts the clock about 30 days out: tell your community, get supporters onto Product Hunt accounts early, and engage active users and other makers.
• Public launch emails and maker comments show teams that already had a list, a community, an earlier product or helpers. That earlier work is inferred, not recorded.
• The same guide puts average preparation for launches that do well at 50 to 120 hours.
• The main figures come from a practitioner who sells launch help, and the examples come from vendors, so treat both as interested sources.
• Not documented anywhere in the evidence: the calendar of any named launch, with dates, ranks and results.

The strategy for this page asked for a pre-launch timeline reconstruction. What follows reconstructs the timeline the sources prescribe and marks which steps are visible in public posts. It does not claim to be the actual history of any launch.

What evidence does this page rest on?

It rests on three pages read on 27 October 2026, each from a party with something to sell. The table sets out what each contains and where it is weak.

The Lenny's Newsletter guide is by the person behind Social Growth Labs, an agency the newsletter says has helped more than 60 startups reach first place and over 100 reach the top three. Those counts are the newsletter's statement about the agency, and this page could not check them. The newsletter also says Product Hunt's CEO reviewed the guide and added tips.

The text of the guide supplied for this page was trimmed. Its later sections, on the ranking algorithm, four asset types, and comments and reviews, appear only as headings, so nothing below says anything about them.

Product Hunt publishes its own preparation pages, How to Launch: Preparation and Preparing for launch. They appeared in the search results for this topic but their text was not part of the evidence supplied, so this page cites no fact from them. Read them before you act on anything here.

What does a pre-launch timeline look like when the sources are combined?

Combined, the preparation runs from a go or no-go decision at least a month out to a staffed launch day, and only some of its steps are visible in public. The table shows each step where its source places it.

How it was built: we took every pre-launch instruction in the guide, then added the preparation implied by the public posts and emails in the other two sources, and placed each step by the timing its source gives. Where a source gives no timing, the row says “Before launch”. No row is dated to a real launch.

Read the table in two layers. The prescribed rows are one practitioner's method, not observations of what successful launches did. The rows drawn from public examples are observations of launch-day content, from which the earlier work is our inference.

Why do the sources start the clock about 30 days before launch?

The guide gives two reasons for starting about 30 days out: supporters need time to set up Product Hunt accounts, and outreach works better when it is not a surprise. It compares an unannounced launch to throwing a party and telling no one until the day.

On accounts, the guide says Product Hunt's community and algorithm value engagement from long-standing members more than from newcomers. If supporters create brand-new accounts on launch day to vote, the guide says their votes are likely to be removed. That is the guide's reading of the algorithm, and Product Hunt's own pages are where to check how votes are treated.

On relationships, the guide advises engaging active Product Hunt users with a following, especially those who fit your ideal customer. Its example is a product popular with product managers, where you would find those people on the site and connect on LinkedIn. It also says to support other makers with real comments in the weeks before, because makers who launched recently reply far more often than makers who last posted two years ago.

The guide quotes Product Hunt's CEO adding that founders often launch too late in their product's life and should launch early and often. That concerns when to launch the product, not when to start outreach, so it does not change the 30-day figure.

Our reading: the 30-day figure is a practitioner's rule of thumb. No source tests 30 days against 14 or 60, so treat it as a sensible default and not a threshold.

How many hours does the preparation take?

The guide says startups that do well invest 50 to 120 hours on average, which is about 11.7 to 28 hours a week across a 30-day warm-up. It adds that some startups reach first place with very little time, but that the odds improve with more.

The hours depend, per the guide, on the product's stage, your experience with the site and whether your users are B2B or B2C. The table shows the arithmetic: 30 days is 30 divided by 7, or about 4.29 weeks.

The 10-hour figure is the agency's own statement about its clients, so it is an advertisement for the service as much as a measurement. Taken at face value, it is 20% of the 50-hour low end (10 divided by 50) and 8.3% of the 120-hour high end (10 divided by 120).

The guide also gives one cost figure for assets: a professionally made product teaser can take about four weeks and cost up to $10,000. It frames this as the high-polish end, so the figure marks a ceiling, not a requirement.

What goal should you set before launch day?

Set a business goal first, such as website visits, signups or trial-to-paid conversion, because the guide says those are what drive growth and ranking is only the visible scoreboard. The guide offers a template for choosing the metrics, which this page did not read.

The guide also reports outcome figures, which help you set a realistic number. All of them are the guide's, none is dated, and none came from a sample we can inspect.

One derived figure puts the Twinr result in proportion. Its 1,000 launch-day signups equal about 6.7 days of its later rate of 150 a day (1,000 divided by 150), so on the guide's account the launch was a strong day, and the slower run rate that followed mattered too.

The guide says B2C products usually see more signups than B2B because the market is wider. If you sell B2B, a figure in the 50 to 300 range is the guide's benchmark for a good launch, not a failure.

What do public launch posts reveal about the work done before?

Maker comments reveal preparation through what they mention: an earlier product, an existing community, helpers who are thanked, a launch-only offer and a roadmap. LaunchPedia collects taglines, descriptions and maker comments and says they come from top-three launches. This page cannot confirm the rank, date or results of any of them.

The table reads four of those comments for pre-launch signals. We left out each company's claims about its own results, since those are not Kanso's to repeat and the page gives no way to verify them.

The pattern across all four is the same: the launch drew on something that already existed. An inference like this can be wrong, because a thank-you can be written the same day and an offer can be set in an afternoon. The posts show what was ready on the day, not how long it took.

Three of the four carry an offer for the day's visitors. That is a count from four posts we chose to read, so it says nothing about how common offers are across top launches.

What did Layers, Canny and Polywork email their lists?

Each sent a launch-day email asking readers to support the launch page, and Loops describes how each one framed the ask. Loops gives no send times, dates or results, so the table records content only.

What can be observed: three companies emailed a list on launch day, and each email centred on one button or link. What can only be inferred: those lists were built before launch day, since a mailing list is hard to assemble on the morning of a launch. That second point is our assumption and no source states it.

The detail that matters for planning is that two of the three gave readers who would never visit Product Hunt something to do. Canny invited replies and Polywork added a feature announcement, so the email still earned its place for the people who did not vote.

How does the launch-day plan shape what you prepare?

The guide's plan has three pushes at 12:01 am, 7 am and 2 pm Pacific Time, so the pre-launch work includes writing the emails and posts for each push and finding people to cover them. It argues that the algorithm favors a steady stream of engagement and that votes should be spread across time zones.

For a team in India, the 12:01 am Pacific start falls in the middle of the day. The conversion below is our arithmetic, using UTC-7 for Pacific daylight time, UTC-8 for Pacific standard time and UTC+5:30 for India.

The guide also suggests up to 10 email sends across the day, split by time zone where possible, with the whole network and local influencers involved. For replies, it recommends two or three team members on standby, answering in two-hour batches.

The day of the week is a pre-launch decision too, and the guide ties it to your goal. The table gives the guide's three groups, with no sample or date attached to its claims about competition and traffic.

One more tip, credited in the guide to Product Hunt's CEO: embed a live upvote counter on your own page on launch day, and leave the badge up afterwards.

Is the pre-launch work worth it for your product?

It is worth it only when the product, the audience and your hours fit, and the guide's author says the agency talks about 70% of the founders who ask for help out of launching because they are not ready. That is the strongest hint in the sources that readiness should be checked before any outreach begins.

The guide adds that hundreds of startups launch each week with no impact, for reasons it lists as weak preparation, audience mismatch and too much competition on the chosen day. It also says paid advertising is often a more efficient way to test messaging or build sustained signups.

Questions in the Reddit threads listed in the research show founders asking whether a launch paid off and what the site adds. None of the sources here answers that with data, so the table below is a decision aid, not a forecast.

If you answer no to two or more, the cheaper step is to hold the launch and fix the gaps. That threshold is our judgment, chosen because the guide treats readiness as the first filter.

Should you pay a launch agency to run the pre-launch work?

The sources cannot settle it, because the only agency figure comes from an agency. It says clients spend about 10 hours on preparation against 50 to 120 in-house, which is a claim about its own service.

Choosing an agency is a worry that recurs in the community threads in the research, and the sources do not help with it. Our suggestions, which are analysis and not documented practice, are to ask for named and dated results you can check on the launch pages themselves, to ask who contacts whom and from which accounts, and to ask what happens when votes are removed.

The same caution applies to this page. Its main source is an agency guide, and the examples come from vendors, which is why the table of sources states each interest.

What is documented and what is analysis?

Documented facts are what a named source states, and analysis is what Kanso concludes from them. The two lists keep them apart.

• Documented by the guide: the 30-day warm-up, early account creation, outreach to active users, the three pushes, the day-of-week groups, the 50 to 120 hour average and the outcome figures.
• Documented by the guide: its agency says 70% of enquiring founders are not ready, and says its clients spend about 10 hours.
• Documented by Loops: the content and framing of the Layers, Canny and Polywork emails.
• Documented by LaunchPedia: the text of the maker comments for MakerBox Bundle, Product Video Examples, BetterLegal Assistant and Blink.

• Analysis: the weekly hour figures (11.7, 28.0 and 2.3), the 20% and 8.3% ratios and the 6.7 days of Twinr signups.
• Analysis: the IST conversion of the three pushes.
• Analysis: that the launch emails and posts imply an earlier list, community, helpers and offers.
• Analysis: the readiness check and its two-no threshold, and the questions to put to an agency.

How would you build a real, dated timeline for a launch you admire?

Choose a launch, collect only dated public traces from before its launch day, and sort them into observed and inferred. That is the data this page could not supply, and it is what separates a timeline of one launch from a prescription.

1. Pick the launch and write down the rule for what counts as pre-launch, such as everything dated before launch day.
2. Read the launch page for its date and final position, not a retelling of it.
3. Collect each dated trace: the maker's posts, snapshots of the product's pages in a web archive where one exists, and any emails you can find.
4. Record how many days before launch each trace falls, and keep your reading of it in its own column.
5. Repeat for several launches before generalising, and state the number and the date of the check beside every result. One launch is a case study, not a pattern.

Until someone publishes that comparison across several launches with its dates, the claims on this page remain one practitioner's method plus a thin set of public examples.

Where do you go after launch day?

The sources treat launch day as the start of a longer tail, since the guide points to a lasting backlink from a high-authority domain and to Twinr's 150 signups a day afterwards. What to do with that traction is a distribution question, and Kanso has pieces on neighbouring channels.

• For a launch on another site, read the Show HN teardown of titles, first comments and timing.
• To decide whether to post, comment or stay out on that site, read Hacker News for B2B founders.
• For the calendar that sits around a launch, read the 25-week plan for launching a B2B SaaS in India and the US.
• For follow-up conversations after launch, read how to promote a startup on Reddit without getting banned.

Product Hunt launch examples: frequently asked questions

Sources

• How to successfully launch on Product Hunt (when it's right for your startup), Lenny's Newsletter
• Product Hunt Content Examples, LaunchPedia
• Product Hunt Launch Email Examples, Loops