Show HN reply through the comment window
Stay in the Show HN thread and answer substantive comments while the post is live instead of treating the front-page spike like a finished launch.
Why this can grow a startup
The thread is part of the product surface. In a Show HN retrospective, the founder said they replied to almost every one of 74 comments because anyone who took time to comment deserved an answer. The same post produced nearly 25,000 page views, 2,670 downloads, and multiple collaboration leads. Another founder in the same thread said their front-page run sent 18,000 visitors on day one and led to valuable feedback. The practical lesson is that the traffic spike and the discussion spike are the same event. If the founder disappears, a large part of the value disappears with them.
Source-backed example
A founder who trended on Show HN said they replied to almost every one of 74 comments; the post drove 24,997 page views, 2,670 downloads, and follow-up conversations with founders and engineers.
Source-reported evidence
Source: Hacker News: Show HN: Retrospective on having my “Show HN” on the front-page
24,997 page views, 2,670 downloads, and 74 comments in three days; the founder said they replied to almost every comment.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 31, 2026
When to use it
Use this when Hacker News, Communities, Lifecycle is relevant to show hn, community management, launch follow-up and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Follow Hacker News community guidelines: do not solicit votes, comments, or submissions; share a useful working demo and an original explanation.
- Record a baseline for: Qualified Show HN visitors who complete the intended first product action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Build creator and community systems around real incentives, trust, and repeat participation.