Hacker News
Hacker News launch for developer SaaS
Hacker News is the strongest launch channel for genuinely interesting developer tools — but the audience is the most skeptical of any launch platform. The first comment thread can torch your launch in 90 seconds if the product feels marketing-heavy. Honest technical depth beats polish every time.
SaaS type: Developer tools, infrastructure, open-source projects, or technical-decision-maker SaaS.
Verified · editorial policy
Channel fit verdict
Channel fit: Strong fit
When NOT to use: If your product is non-technical, design-heavy, or has zero engineering substance, Hacker News is the wrong channel. The audience punishes glossy marketing on undifferentiated products.
Pre-launch build-up
Step 1
Build something genuinely technically interesting (months before)
Hacker News rewards substance. Trying to launch a generic CRUD app with a 'Show HN' will fail. The technical pre-work is the entire game.
Time: Months of product work.
Step 2
Pick the title carefully (1-2 days before)
Hacker News titles are make-or-break. 'Show HN: X — a Y for Z' format. Specific, technical, no marketing language. 'Show HN: A static-site generator written in 200 lines of Zig' beats 'Show HN: The fastest blog tool ever'.
Time: 30 minutes of drafting; iterate.
Step 3
Prepare the first comment (1 day before)
Your own first comment as the founder explains why you built this, what is interesting technically, and what is NOT in the product. Honesty about limitations is the trust unlock.
Time: 1 hour of drafting.
Step 4
Make sure the URL holds 1,000 concurrent visitors (1 day before)
Hacker News traffic spikes are real. Cache headers, CDN, and your hosting need to handle 1k+ concurrent. A site that crashes on launch day is a story Hacker News tells for years.
Time: 2-4 hours of infrastructure prep.
Launch day
Step 1
Post at 7-9am Eastern (Tuesday-Thursday)
Hacker News peak activity is 8am-noon Eastern weekdays. Avoid weekends; lower engagement, less discussion.
Time: First 90 minutes set the trajectory.
Step 2
Post your own first comment within 5 minutes
The 'why I built this, what is here, what is not' comment. Self-disclosure about what is incomplete is the trust mechanism the platform rewards.
Time: 5 minutes.
Step 3
Respond to every technical question for 12 hours
Hacker News commenters technically engage. Answer with detail, link to relevant code, admit when you do not know. The platform rewards thoughtfulness.
Time: 12 sustained hours.
Post-launch (7 days)
Step 1
Day 2 — write the build retrospective
A separate post on your blog covering what the launch revealed about the product. The post often re-appears on Hacker News as a separate submission.
Time: 3-5 hours.
Step 2
Day 3-7 — engage with mentions
Track mentions of your tool in other Hacker News threads, on Twitter, on Lobsters. Each is a follow-up conversation worth having.
Time: 30-60 minutes daily.
Success profile
Front page for 4+ hours, 100-500 upvotes, 50-200 comments, 1,000-10,000 unique visitors, 50-300 email signups. Conversion to paying customers is slower than Twitter or Product Hunt — Hacker News audience is research-then-buy.
Failure profile
Buried in 30 minutes, under 20 upvotes, no comment thread. Usually traceable to a generic title, a marketing-heavy landing page, or a launch from a brand-new account.
Channel-specific mistakes
- Marketing-language titles. 'Revolutionary' and 'game-changing' get downvoted instantly.
- Hiding limitations in the first comment. Hacker News rewards honesty about what is not in the product.
- Defensive responses to critical comments. The audience watches how founders handle criticism; defensiveness loses trust.
- Submitting from a new account with zero karma. Older accounts get more initial visibility.
Niches that fit this channel
Related Brunson terms
Frequently asked
- Can I re-submit if my Show HN gets no traction?
- Once, with a different title, after 60+ days. Frequent re-submission is detectable and penalized.
More launch channels
Pair this with the pre-launch checklist
The pre-launch indie SaaS checklist names the ten things every SaaS must verify before any of the launch channels here can convert.