Show HN runnable surface before announcement page
Do not use Show HN for a teaser page or waitlist shell; launch only when strangers can actually try the thing you made.
Why this can grow a startup
Hacker News is unusually blunt about the difference between a product and an announcement. When the launch surface can be tried immediately, the thread becomes feedback, bug reports, and proof. When it is only a signup form, the audience has nothing useful to react to. That means the post burns trust without creating the learning loop the room is good at.
Source guidance
The official Show HN guidelines tell makers not to post landing pages or fundraisers and to come back once the work is ready for users to try.
Source-reported evidence
Source: Show HN Guidelines
Show HN is explicitly for something other people can play with, not a signup page
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 27, 2026
When to use it
Use this when Hacker News, Product, Launch is relevant to launch readiness, feedback loops, self-serve 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.