# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/show-hn-backstory-and-technical-difference-up-front/
- Source: [markepear.dev](https://www.markepear.dev/case-studies/glassflow)
- GrowthDex source hub: [Markepear: How GlassFlow got to the top of Hacker News](/sources/markepear-how-glassflow-got-to-the-top-of-hacker-news-markepear-dev/)
- Last checked: 2026-05-31
- Rarity: rare
- Budget: free
- Channels: Hacker News, Communities, Content
- Stages: show hn, launch copy, technical audience, message clarity


## Why this can grow

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.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. I would treat this as earning the right to be in the room, not dropping a campaign into a room. In community-led growth, the first job is to notice what people already care about, then bring a useful proof, tool, teardown, or question that makes the conversation better. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where show hn backstory and technical difference up front can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Hacker News and Communities channel.
3. Use the evidence from markepear.dev to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## 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.

## Adjacent tactics in the same lane

- [Show HN direct language without marketing polish](/growth-ideas/show-hn-direct-language-without-marketing-polish/) - 2 shared channels, 1 shared stage
- [Show HN reply through the comment window](/growth-ideas/show-hn-reply-through-the-comment-window/) - 2 shared channels, 1 shared stage
- [Show HN no booster comments or vote rings](/growth-ideas/show-hn-no-booster-comments-or-vote-rings/) - 2 shared channels, 1 shared stage
- [Staggered multi-platform launch sequence](/growth-ideas/staggered-multi-platform-launch-sequence/) - 2 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The Show HN thread should finish the first technical conversation](/blog/the-show-hn-thread-should-finish-the-first-technical-conversation/) - community-led growth, brand trust, launches

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.