# Repeat-usage gate before big launch

> Hold the bigger public launch until strangers can self-serve and a small group keeps coming back without your help.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/repeat-usage-gate-before-big-launch/
- Source: [newsletter.posthog.com](https://newsletter.posthog.com/p/how-we-got-our-first-1000-users)
- GrowthDex source hub: [PostHog Newsletter](/sources/posthog-newsletter-newsletter-posthog-com/)
- Last checked: May 24, 2026
- Rarity: rare
- Budget: free
- Channels: Hacker News, Website, Onboarding
- Stages: launch, activation, 0-100
- Key metric: 300 deployments within a couple of days after launch, five weeks after starting to build

## Why this can grow

A launch spike is only valuable if people who arrive can use the product and feel enough pull to return. Repeat usage is a stronger readiness signal than raw signup volume because it shows the product survives first contact. Waiting for that signal makes the launch smaller in ego terms and much stronger in compounding terms.

## 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. For activation, the useful question is not whether users liked the page. It is whether they got to the first meaningful win faster. 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 repeat-usage gate before big launch can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Hacker News and Website channel.
3. Use the evidence from newsletter.posthog.com 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

PostHog waited to launch on Hacker News until users could sign up and use the product without help and strangers were already finding it useful; the launch then drove 300 deployments within a couple of days, five weeks after building started.

## Adjacent tactics in the same lane

- [Founder 30-second reply SLA for early users](/growth-ideas/founder-30-second-reply-sla-for-early-users/) - same source, 1 shared channel, 2 shared stages
- [Founder-calendar pricing page for first sales](/growth-ideas/founder-calendar-pricing-page-for-first-sales/) - same source, 1 shared channel, 1 shared stage
- [Public handbook trust surface](/growth-ideas/public-handbook-trust-surface/) - same source, 1 shared channel, 1 shared stage
- [Manual chat onboarding before self-serve](/growth-ideas/manual-chat-onboarding-before-self-serve/) - same source, 1 shared channel, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [Trust often shows up before scale does](/blog/trust-often-shows-up-before-scale-does/) - brand trust, early traction, operator-led distribution

## Advisory

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