Back to GrowthDex
Growth idea action plan

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.

rare tacticfree budget

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.

Company 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 and metric

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.

Source discovered: May 31, 2026

Hacker NewsCommunitiesContentshow hnlaunch copytechnical audiencemessage clarity
GrowthDex operator note

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.

Founder checklist

  1. Read Markepear: How GlassFlow got to the top of Hacker News and identify what is directly supported.
  2. Choose one channel context: Hacker News, Communities, Content.
  3. Define the test around GlassFlow reached #1 on Show HN and stayed there for over 12 hours after the post was rewritten with more technical depth and context..
  4. Set an owner, evidence window, and stop condition before launch.

Explore the context

Advisory bridge

Apply this with an operator

Build creator and community systems around real incentives, trust, and repeat participation.

Work with Ian