How To Launch on Hacker News in 2026: The 5-Lever System

How to launch on Hacker News when the rest of the front page is on fire

How to launch on Hacker News in 2026 is a different problem than it was in 2018. The front page now refreshes inside hours under the weight of a global audience reading from every timezone, the moderation bar is tighter on coordinated voting and on superlative-heavy titles, and the founder accounts that hit the front page in the past 90 days share a tight pattern that reads less like luck and more like a checklist. We have run 11 Show HN launches across FORKOFF clients in the past 12 months, audited 30 more from the public archive, and the same five levers separated the runs that crossed 200 points from the runs that died at 4 points. This guide is the operating system, in the order you need to execute it.

The mistake almost every first-time launcher makes is treating the submit click as the launch. The submit click is the middle of the launch. The first lever fires two hours before submit, the last lever fires 24 hours after submit, and the post itself is the four-hour window in between where you are reading every comment as it arrives and replying inside three minutes. If you cannot block four uninterrupted hours, do not launch that day. Reschedule. The cohort that compounds on Hacker News is the cohort that respects the time the post needs. Mark Pear's dev-tool launch breakdown covers the same window from a single-tool perspective and arrives at the same conclusion: the founder is the operator of the launch, not the audience of it.

1. Title craft: the lever that fires two hours before submit

Lever one is the title and it is the most under-respected variable in every launch we audit. The Hacker News title field is the entire pitch. There is no thumbnail, no preview text on most clients, and no second chance once the post is live. We rewrite the title at least eight times before submit, then sleep on it, then rewrite three more times the morning of. The pattern that wins is concrete plus modest plus unexpected. Show HN: We replaced our 14-stage SQL pipeline with a 90-line agent beats Show HN: The fastest data pipeline you can build with AI on every variant we have shipped. The first reads like a sentence a real engineer would write to a friend. The second reads like a marketing team approved it.

The Hacker News audience flags superlative titles inside minutes. Words like fastest, biggest, best, revolutionary, game-changing trigger immediate downvotes from senior accounts and almost guarantee a flag from the user@ycombinator.com mods inside the first hour. The Y Combinator Launch HN instructions spell out the modest-language rule in writing and the same rule applies to Show HN even though the curated process is different. Modest, specific, and a little bit unexpected is the mark you are aiming at. If the title makes a reader pause for half a second before clicking, you have it. If the title sounds like every other AI startup tagline, rewrite it.

2. Submit hour: how to launch on hacker news at the right minute

Lever two is the submit hour. The Show HN front page rotates inside hours and the algorithm gives the heaviest weight to the first 90 minutes after submission, so the question is not which day but which minute. The window that consistently wins for technical launches is 06:00 to 08:00 Pacific Time on a Tuesday or Wednesday. The reasoning is mechanical: 06:00 PT is 09:00 ET (East Coast engineers reading first thing), 14:00 GMT (Europe mid-afternoon engineers checking HN), and 19:00 IST (Indian engineers winding down). The post catches three timezone cohorts inside the same first 90 minutes that decide its fate.

Friday and weekend submits leak the early window into a low-engagement day, then the post drifts off the new page before Monday's high-engagement window opens. Monday is fine but harder because Tuesday-launchers who scheduled poorly catch the same window and you are competing for the same first-90-minutes attention. Tuesday and Wednesday are the cleanest. The Lucas Costa post-mortem of his own Show HN run reaches the same time-of-day conclusion from a different dataset, which is one of the few places the conventional advice is actually tight.

3. The prep-vote cohort: how to clear the front-page gate in 90 minutes

Lever three is the prep-vote cohort and this is the lever where most launches go quietly wrong. The mechanic that decides front-page placement is roughly 30 organic votes accumulated in the first 90 minutes after submission. Organic is doing the load-bearing work in that sentence. Organic means people who follow your work, who already use your product, or who would have voted regardless of whether the post was yours. It does not mean a Slack channel of friends instructed to vote at 06:05 PT on a Tuesday. The HN moderation team can detect coordinated voting patterns inside the first hour from account age, account activity, and IP clustering, and the penalty is permanent: the post gets buried, the submitting account gets penalty-flagged, and re-launching with a different account is detectable too.

The right way to build a prep-vote cohort is the slow way. Spend the 30 days before launch posting your build progress on the founder-voice X surface we covered in the AI startup marketing stack, replying in r/programming and r/MachineLearning where appropriate, and joining one or two Slack or Discord communities you actually use. By launch morning you will have 200 to 500 builders who recognize your name and click the link because they want to see what you finally shipped. Of those, 30 to 50 will upvote inside the first 90 minutes and you will clear the front-page gate without ever asking anyone to do anything.

4. Founder reply cadence: the lever that holds the front page

Lever four is founder reply cadence and across our 11-launch audit it is the single highest-impact variable in the entire system. A Show HN that hits the front page typically draws 40 to 120 comments in the first six hours, and the founder who replies personally to every top-ten comment inside three minutes of arrival keeps the post in motion. The audience reads the founder's replies as a separate signal from the submission itself. Concrete numbers, an honest concession when a critique lands, a follow-up commit pushed during the thread, all of those move the post up.

Templated replies, marketing-team voice, and silence move the post down. The pattern across the launches that died at 4 points is almost always the same: founder submits at 06:00 PT, comments start landing at 06:25 PT, founder is in a meeting at 06:45 PT, first reply lands at 09:30 PT and reads like a press release. Block the first six hours after submit. Cancel meetings. Tell your team you are unreachable. The same playbook we documented for the X launch protocol applies here: the founder is the operator of the launch and the cost of breaking that pattern is measured in points lost, not in time saved.

5. Counter-skeptic tone: the lever that survives the second-day audit

Lever five is the tone you bring to the skeptics, and on Hacker News every successful Show HN draws skeptics. The senior accounts that read the new page first will leave critical comments in the first hour. Some are signal. Some are pattern-matching to last week's overhyped launch. The founder who treats both kinds the same way wins, and the founder who gets defensive on the pattern-matched critique loses 30 to 80 points inside two hours. The right tone is concrete and slightly amused. Yes, the SQL approach works for sub-1M-row datasets and we have benchmarks at the README link. The agent stack starts winning past 10M rows because of X. Happy to share the benchmark notebook beats every defensive variant of the same content.

The dev.to Hacker News launch guide from Daniel Farrell makes the same point in different words. The skeptics are the audit, not the enemy. The Show HN that survives day two is the one where the comment thread reads like a working engineering conversation. The Show HN that does not survive is the one where the founder went into PR mode at the first critique. We have run engagements where the founder needed coaching through the first three hours of the thread and the post still cleared 250 points because the underlying voice held. The voice is the lever. Everything else is mechanics.

Verification checklist for show hn front page strategy

Run this checklist 24 hours before launch. Title is one sentence, modest, concrete, and does not contain any superlative word. Submit hour is calendar-blocked at 06:00 to 08:00 PT on a Tuesday or Wednesday. Prep-vote cohort is identified by name, has been warmed via 30 days of founder-voice posting, and you can list 50 specific people who will see the post inside the first hour. Founder reply window is calendar-blocked from submit-time through submit-plus-six-hours with no meetings. The first three counter-skeptic replies are pre-drafted in a doc you can paste into the thread. The same prep discipline shows up in the founder-led content marketing audit, where the highest-trust posts are the ones that were drafted and rewritten before the founder hit publish.

Common pitfalls we see and refuse on FORKOFF engagements. The founder is travelling and tries to launch from a hotel wifi without a backup laptop, the post gets one early reply, then the wifi drops for 40 minutes, the thread is cold by the time the founder is back and the post dies at 28 points. The founder writes the title in marketing-team voice because the marketing team made them feel like they had to, the post is flagged inside 22 minutes. The founder coordinates a vote ring through a Slack of 18 friends, all 18 vote inside a 9-minute window from similar IPs, the post is buried by HN moderation inside 70 minutes and the founder loses the launch slot for 90 days. The same trust-recovery protocol from the AI product trust recovery playbook applies after a botched launch: name the failure inside 72 hours, ship the next launch with the gap closed, and the cohort comes back. Each of these is recoverable on the next launch but recovers slowly. Better to read the checklist twice and not have to recover.

Where the show hn launch fits in the broader founder distribution stack

The Show HN spike is one surface in a stack of seven we run with founder-growth clients, and it is the single highest-leverage one-day distribution event a technical founder gets. It does not work in isolation. The founders who treat HN as the only launch surface burn one strong asset on a 12-hour spike and have nothing to compound. The founders who sequence HN as the spike inside a stack that also runs founder-voice X, an open-source cookbook, hackathon presence, and developer podcasts, get the spike and the trailing distribution at the same time. We mapped the full sequence in the AI startup marketing stack and the order matters: HN is surface four, after the founder-voice and cookbook surfaces have already calibrated the voice the launch depends on.

If you have not yet shipped surface one or two, do not launch on Hacker News this week. The spike will not have anywhere to land, the people who upvote will not be people who care, and the trailing distribution will be effectively zero. Spend 30 days on founder-voice posts and a working repo, then come back to this checklist and run the launch. The launches that compound do the prep work first. The launches that flame out skip the prep and try to recover during the 4-hour window where there is no time to recover. We covered the same prep-then-spike pattern in the AI DevRel playbook and the principle holds across every distribution surface a technical founder runs.