Claim and evidence
Design the shortest path from a new user entering the product to that user inviting the next one.
No dated example yet. Treat this tactic as a hypothesis.
Anecdotal
Practitioner experience without published numbers.
Working · 2026-11 Principle is old (page undated, likely 2007) and still standard in funnel design.
What the numbers show
attrition to assume when asking for a username and password (Andrew Chen's rule of thumb)
andrewchen.comWhy it works
Every extra step (like registration) loses a large share of people, so a tight loop beats a long tour. Chen advises tightening the loop before adding on-ramps.
How to run it
- List steps from landing to first invite
- Delay registration where possible
- Test removing each step
- Add onboarding on-ramps only after the loop works
Before / after
Generalised wireframe of the pattern, not a copy of any company's screen.
Ways to run it
Design options to test, not promised results.
- Option ADelay registration
Let invited people get value first and ask for an account only when they need to save or share.
- Option BRemove one step per test
Map every step from landing to first invite and test dropping them one at a time.
- Option CLoop before on-ramps
Tighten the core loop first; add tours and onboarding on-ramps only once it works.
Timeline
- 12007 first documented: Andrew Chen
- 22026-11 status checked: Working
Dated examples
No dated example yet. Treat this tactic as a hypothesis.
Does it still work?
Principle is old (page undated, likely 2007) and still standard in funnel design. source
Risks
- Page undated
- No data on the page
Sources
- andrewchen.com
“Assume up to 80% to 90% attrition if you are asking them to register for a username/password, for example.”
✓ quote checked word-for-word on the page
Change log
- 2026-11-20 — harvest v0.1 (referral-loops)