# HN star-window ledger before launch retrospective

> Track GitHub stars at 24 hours, 48 hours, and 7 days after Hacker News before calling the launch a win or a miss.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/hn-star-window-ledger-before-launch-retrospective/
- Source: [arxiv.org](https://arxiv.org/abs/2511.04453)
- GrowthDex source hub: [arXiv: Launch-Day Diffusion: Tracking Hacker News Impact on GitHub Stars for AI Tools](/sources/arxiv-launch-day-diffusion-tracking-hacker-news-impact-on-github-stars-f/)
- Last checked: 2026-06-10T06:39:08.000Z
- Rarity: uncommon
- Budget: free
- Channels: Hacker News, GitHub, Developer Marketing
- Stages: GitHub stars, Hacker News launch, launch measurement, developer proof, one-week tail


## Why this can grow

A Hacker News launch does not finish when the post leaves the front page. The sharper read is the shape of developer proof after the first wave. The Launch-Day Diffusion paper studied 138 AI and LLM repository launches from 2024 to 2025 and found average gains of 121 GitHub stars in 24 hours, 189 in 48 hours, and 289 in a week after HN exposure. That gives founders a useful launch ledger: measure the immediate proof, the second-day carry, and the one-week tail. Ian's practical read: in developer and AI products, that tail is where curiosity starts becoming repository trust, docs links, comparison pages, and later citations.

## 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 hn star-window ledger before launch retrospective can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Hacker News and GitHub channel.
3. Use the evidence from arxiv.org 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

The Launch-Day Diffusion study reports average post-HN GitHub star gains of 121 within 24 hours, 189 within 48 hours, and 289 within one week across 138 AI and LLM repository launches.

## Adjacent tactics in the same lane

- [HN posting-hour test before front-page hope](/growth-ideas/hn-posting-hour-test-before-front-page-hope/) - same source, 2 shared channels
- [HN public API launch tracker before vanity summary](/growth-ideas/hn-public-api-launch-tracker-before-vanity-summary/) - same source, 2 shared channels
- [HN Show label after substance, not before](/growth-ideas/hn-show-label-after-substance-not-before/) - same source, 1 shared channel
- [HN repo ready before community attention](/growth-ideas/hn-repo-ready-before-community-attention/) - 2 shared channels

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The public room should be ready before attention arrives](/blog/the-public-room-should-be-ready-before-attention-arrives/) - community-led growth, launches, brand trust
- [The GitHub repo should be ready before Hacker News arrives](/blog/the-github-repo-should-be-ready-before-hacker-news-arrives/) - Hacker News, GitHub, developer marketing

## Reading path: AI products

- [The public room should be ready before attention arrives](/blog/the-public-room-should-be-ready-before-attention-arrives/) (2026-06-10T07:06:20.000Z)
- [The GitHub repo should be ready before Hacker News arrives](/blog/the-github-repo-should-be-ready-before-hacker-news-arrives/) (2026-06-10T06:39:08.000Z)

## Reading path: developer tools

- [The public room should be ready before attention arrives](/blog/the-public-room-should-be-ready-before-attention-arrives/) (2026-06-10T07:06:20.000Z)
- [The GitHub repo should be ready before Hacker News arrives](/blog/the-github-repo-should-be-ready-before-hacker-news-arrives/) (2026-06-10T06:39:08.000Z)

## Advisory

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