Launch HN: How YC Startups Run a Hacker News Launch

Launch HN: How YC Startups Run a Hacker News Launch

Launch HN is a YC-coordinated launch post on Hacker News where Y Combinator startups introduce their product to the HN community through a structured, scheduled post that appears directly on the front page at a pre-arranged time, distinct from the self-serve Show HN format that any HN user can submit.

TL;DR

• Launch HN is available only to current YC startups and is coordinated through your group partner, not self-submitted
• Unlike Show HN, Launch HN posts get guaranteed front-page placement and a dedicated time slot
• The founder first comment is non-negotiable: write it before the post goes live and cover problem, product, why now, differentiation, and a clear ask for feedback
• Prepare your site, analytics, and email capture before the post goes up -- traffic from HN is sharp and fast and you will not have time to fix things mid-spike
• The first 4-6 hours of comment responses determine whether the thread converts casual readers into signups
• Without a pipeline plan, the traffic graph goes flat the next day; set up a retargeting audience and a follow-up sequence before you launch

What Is Launch HN and Who Is It For?

Launch HN is the official launch mechanism that Y Combinator provides to its active batch companies. When a YC startup is ready to go public, the group partner coordinates with HN moderators to schedule a front-page post. The post appears with a "Launch HN" prefix in its title, signaling to the HN audience that this is a YC-backed company introducing itself. Access is gated entirely through YC participation -- outside companies cannot request or buy it. The HN audience skews toward engineers, technical founders, and early adopters, who read for product detail and ask sharp technical questions. For pre-seed and seed-stage founders, this is one of the few launch channels where technical depth is an advantage rather than a liability.

How Is Launch HN Different from Show HN?

Show HN is the community-driven format that any registered HN user can submit. There is no gatekeeper, no scheduling, and no guaranteed placement -- a Show HN post either earns upvotes and rises organically or it sinks. Launch HN by contrast is placed directly on the front page by moderators at a time coordinated with YC, so your post does not compete for position against the morning news cycle in the same way. The audience also reads the two formats differently: a Show HN post signals "I built this, try it," while a Launch HN post signals "YC has vetted this team and is putting them in front of you." For a deeper breakdown of Show HN mechanics without YC backing, see our guide on launching on Hacker News.

How Should You Write the Launch HN Title?

The title format is prescribed: "Launch HN: [Company Name] -- [One-line description]." The one-line description is the hardest part. It must be a concrete, medium-independent description of what your product does -- no superlatives, no market-size claims, no inside-baseball jargon. A title like "Launch HN: Acme -- CRM for construction subcontractors" tells the reader exactly what the company does. "Launch HN: Acme -- Reinventing the $300B field-services industry with AI-powered workflow automation" gets scrolled past. HN readers are allergic to hype and will read inflated titles as a reason to dismiss the post. Get the description under 80 characters and test it on someone outside your company.

What Goes in the Founder'S First Comment?

The moment your Launch HN post appears, HN users scroll to the comments. A blank comment section is a missed opportunity. Have your founder comment drafted, reviewed, and ready to paste within seconds of going live. Structure it in five sections: (1) The problem -- who has it, how acute is it. (2) What you built -- the product, the stack, and what a user experiences in the first 30 seconds. (3) Why now -- what changed in the past 12-18 months that makes this company possible. (4) What is different about your approach -- be honest about competition and specific about your technical or distribution insight. (5) A clear ask -- what feedback you want, what types of users you are seeking, and whether you are open to betas or trials. The tone should be direct, humble, and technically honest. Founders who oversell get torn apart; founders who are too vague get ignored.

What Should You Do to Prepare Your Site Before the Post Goes Live?

HN traffic arrives in a concentrated burst; a Launch HN can send thousands of concurrent visitors within minutes. If your homepage loads in six seconds under normal traffic, it may time out under a HN spike. Before the post goes live: run your site through a load test or check with your hoster about concurrent connection limits. Put your signup flow on a static or heavily cached page. Set up a separate analytics view specifically for Launch HN traffic so you can segment these visitors later. Have an email capture mechanism that works without JavaScript -- some HN readers browse with JS disabled. Brief your team so at least two people are online when the post goes live. The YC startup launch playbook covers broader launch-day team coordination in more detail.

How Does Launch HN Compare to Show HN and Product Hunt?

For a more detailed breakdown of Product Hunt mechanics and how to time a PH launch alongside or after a HN launch, read our Product Hunt launch strategy for startups.

How Do You Work the Comment Thread During the First 4-6 Hours?

The HN comment thread is where your launch either gains momentum or stalls. HN users read comments before they click through, and the tone of the top-level comments sets the frame for every visitor who arrives after them. During the first 4-6 hours: answer every question, even the ones you think are naive -- HN readers judge founders by how they handle the weakest question, not the strongest. If someone points out a real limitation, acknowledge it without defensiveness and explain what you are doing about it. Do not argue with criticism; a factual correction delivered neutrally is fine, a heated response is not. Have one founder monitor the thread continuously and a second person handle technical deep-dives. Upvote comments that add signal but do not get drawn into meta-discussions about HN itself or YC.

How Do You Convert a One-Day Traffic Spike into Durable Pipeline?

The most common Launch HN outcome is a sharp traffic spike on day one followed by a near-flat graph on day two. The difference between a spike that decays and a spike that compounds is what you set up beforehand. Segment HN visitors into a distinct cohort in your analytics so you can measure downstream behavior -- signups, activation, retention -- separately from organic and paid channels. HN visitors rarely convert on a first visit, so you need a low-friction way to capture contact information: an email waitlist, a newsletter, or a notification form. Build a retargeting audience from the HN referral traffic -- even a few hundred visitors who made it past your homepage can seed a pipeline if you follow up with a relevant sequence. HN traffic includes investors, potential hires, and customers who may not need you today but will remember you in six months. Write a short follow-up email for everyone who signed up during the spike, telling them what you learned, what you are shipping next, and giving them a reason to stay engaged. The Demo Day marketing timeline runs on a similar dynamic: a concentrated moment of attention that decays fast unless you build the infrastructure to convert it into ongoing relationships. For founders without a dedicated growth hire, marketing partners like Stackmatix that specialize in the venture-backed startup segment can help turn a one-day spike into a repeatable acquisition engine.

Frequently Asked Questions

Do I Need to Be a Current YC Company to Do a Launch HN?

Yes. Launch HN is only available to startups in the active Y Combinator batch, coordinated through your group partner. Alumni no longer in an active batch do not have access. If you are not a YC company, your path to launching on HN is a Show HN post, which any registered user can submit. The mechanics differ substantially -- see our guide on launching on Hacker News for detail on the self-serve route.

How Far in Advance Should I Coordinate My Launch HN with YC?

Coordinate with your group partner at least two weeks before your target date. YC needs lead time to schedule with HN moderation, and you need at least a week to prepare site infrastructure, draft the founder comment, brief your team, and set up analytics. Last-minute Launch HNs happen but are riskier: your site, comment quality, and team readiness all suffer when you compress the timeline.

What If the Comment Thread Goes Negative -- Should I Respond to Every Critical Comment?

You do not need to respond to every comment, but you should respond to every substantive criticism. The HN community rewards founders who engage with honest feedback and punishes those who ignore legitimate concerns. Acknowledge the point, explain your thinking if relevant, and move on. Arguing or getting defensive is the fastest way to turn a mildly critical thread into a hostile one. A simple "you are right, we will fix that" beats a long defense every time.

Can I Link to a Paid Product or Require a Credit Card in the Launch HN Post?

HN's culture is hostile to paywalls and credit-card gates on launch posts. If your product requires payment to try, expect significant pushback. The strongest Launch HNs offer a free trial, a generous free tier, or a sandbox that lets HN readers evaluate without friction. If you must require a credit card, at minimum offer a no-charge trial and make cancellation trivially easy. Be transparent about pricing in your founder comment.

Should I Also Launch on Product Hunt During the Same Week?

Spacing your launches is usually better than stacking them. A Launch HN and a Product Hunt launch in the same 48 hours splits team attention and makes it harder to segment which traffic came from where. A common pattern is Launch HN first, use that traffic to seed retargeting audiences and gather feedback, then run a Product Hunt launch 2-4 weeks later with an improved product and a sharper story. For more on this sequencing, see our Product Hunt launch strategy for startups.