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.
Why this can grow a startup
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.
Company 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.
Source and metric
Source: PostHog Newsletter · Browse PostHog Newsletter tactics
300 deployments within a couple of days after launch, five weeks after starting to build
Source discovered: May 24, 2026
When to use it
Use this when Hacker News, Website, Onboarding is relevant to launch, activation, 0-100 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
- Read PostHog Newsletter and identify what is directly supported.
- Choose one channel context: Hacker News, Website, Onboarding.
- Define the test around 300 deployments within a couple of days after launch, five weeks after starting to build.
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.