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.
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.
Source-reported evidence
Source: PostHog Newsletter · Browse PostHog Newsletter tactics
300 deployments within a couple of days after launch, five weeks after starting to build
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
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.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Follow Hacker News community guidelines: do not solicit votes, comments, or submissions; share a useful working demo and an original explanation.
- Record a baseline for: Share of target users completing the product's first-value action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.
SOURCE HUB
More tactics from PostHog Newsletter
Explore related GrowthDex examples and evidence connected to PostHog Newsletter.
Open PostHog Newsletter source hub