Show HN backstory and technical difference up front
Open a Show HN post with the founder backstory, the exact pain, and what is technically different before the thread has to drag that context out of you.
Why this can grow a startup
Show HN works best when readers can see why the builder cared enough to make the thing and why the solution is meaningfully different from the obvious alternative. Dang's moderator tips explicitly push founders to explain the backstory and what is different, and the GlassFlow case study showed the launch jumped from a vague draft to a #1 Show HN by spelling out the pain, the failed obvious path, the product, and how it worked. That structure gives skeptical technical readers a reason to stay in the thread instead of opening with disbelief.
Source-backed example
When GlassFlow rewrote its Show HN intro around the pain, the failed obvious solution, and the product's technical difference, the post reached #1 on Show HN and stayed there for more than 12 hours.
Source-reported evidence
Source: Markepear: How GlassFlow got to the top of Hacker News
GlassFlow reached #1 on Show HN and stayed there for over 12 hours after the post was rewritten with more technical depth and context.
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, Content is relevant to show hn, launch copy, technical audience 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.