Viral Coefficient
Viral coefficient (K) is the number of new users each existing user generates through invitations. K = i × c, where i is the average number of invitations sent per user and c is the conversion rate of those invitations. K = 1 means each user replaces themselves (linear growth). K > 1 means exponential growth — each cohort generates a larger cohort. K = 0.5 means each user produces half a user, which still meaningfully reduces blended CAC even though it's not 'viral.' Most viable consumer products run with K between 0.15 and 0.6. K > 1 sustained for more than a few months is so rare it's nearly mythological — Dropbox briefly hit ~1.2 with referrals, and that's the canonical example.
The Trap
The trap is treating K as a vanity metric. K = 0.4 with a 5-day cycle time crushes K = 0.9 with a 60-day cycle time over any meaningful horizon. People obsess over the coefficient and ignore cycle time, retention drag, and conversion drop-off. Worse: most reported K-factors include only the first invitation step, ignoring whether invited users go on to invite others (true viral propagation requires K > 1 across multiple generations, not just one).
What to Do
Calculate your real K monthly: i = (total invites sent in period) ÷ (active users in period), c = (signups from invites) ÷ (invites sent). Then track three derivative metrics: cycle time (days from invite sent to invitee signup), generation depth (how many cycles before propagation dies), and quality drift (do invited users invite at the same rate as organic users?). Most teams measure none of these and wonder why their viral loop 'stopped working.'
Formula
In Practice
Dropbox's two-sided referral program is the textbook K-factor case study. Pre-referral, Dropbox spent ~$300 CAC on Google Ads for a $99 product — economically broken. Post-referral (invite a friend, both get 500MB free), they hit a measured K of approximately 1.2 during peak adoption, meaning each user generated 1.2 new users on average. User base went from 100K to 4M in 15 months at near-zero marginal cost. The key wasn't generosity — it was that storage was the exact thing users wanted, the invitation was native to the product (need to share files), and the cycle time was days, not months.
Pro Tips
- 01
K is most useful as a diagnostic, not a goal. The interesting question isn't 'what's our K?' — it's 'why is i so low?' or 'why is c so low?'. Decomposing K into its drivers tells you what to fix; the headline number doesn't.
- 02
Cycle time matters more than K. K = 0.5 with a 7-day cycle = 14% effective compounding/month. K = 0.9 with a 60-day cycle = 1.5% effective/month. The 'weaker' loop is 9x more powerful in practice. Optimize cycle time first.
- 03
K-factor degrades. Day-1 invitees often have a higher K than Day-30 invitees because they self-selected into the product. Track K by cohort generation — if K drops by half each generation, you have a one-shot referral burst, not a sustainable loop.
Myth vs Reality
Myth
“If K > 1, the company will grow forever.”
Reality
K > 1 is mathematically explosive only if invited users invite at the same rate AND retention doesn't collapse AND the addressable market doesn't saturate. Real-world K > 1 always decays because of saturation (everyone who would join, has joined) and quality drift (referred-of-referred users are weaker referrers). Most 'viral' products grow fast for 12-24 months then plateau hard.
Myth
“Viral coefficient is a B2C-only metric.”
Reality
Calendly, DocuSign, Loom, and Zoom all built billion-dollar businesses on B2B viral coefficients above 0.5. The mechanism is different — instead of 'invite a friend,' the product itself forces non-users into contact with it (you can't send a Calendly link without exposing the recipient to Calendly). B2B virality is often more durable because business problems recur.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
Challenge coming soon for this concept.
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets — not absolutes.
Viral Coefficient (K) — Consumer Apps
B2C consumer apps with intentional referral mechanicsExplosive (Rare)
> 1.0
Strong Viral
0.5 - 1.0
Healthy Assist
0.2 - 0.5
Marginal
0.05 - 0.2
Negligible
< 0.05
Source: Andrew Chen / a16z Growth Reports
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Dropbox
2008-2010
Dropbox's two-sided referral program (invite a friend, both get 500MB free) is the canonical viral coefficient case study. Founder Drew Houston measured a K-factor of approximately 1.2 during peak adoption — meaning each user generated 1.2 new users via referrals before churn. The loop succeeded for three structural reasons: (1) storage was an immediate, tangible reward both sides wanted, (2) sharing files was a native product action that naturally exposed others to Dropbox, and (3) cycle time was days. User base grew from 100K to 4M in 15 months with referrals driving the majority of new signups at near-zero marginal CAC.
Peak K-Factor
~1.2
User Growth (15 months)
100K → 4M
Pre-Referral CAC
~$300 per $99 product
Post-Referral Marginal CAC
~$0
K > 1 is achievable when the incentive is the exact thing the product sells, the invitation is native to the product flow, and cycle time is short. Removing any one of these collapses the loop.
PayPal
1999-2001
PayPal achieved one of the most expensive K-factor strategies in startup history: $10 to sign up, $10 for each successful referral. The math was insane on paper — they were paying $20 per user. But the K-factor was estimated above 1.0 in early months and the loop drove growth from a few thousand users to millions within 18 months. PayPal eventually capped and ended the cash incentive once the network effect (eBay sellers needed PayPal because buyers had it) made the artificial K unnecessary.
Cash Incentive
$20 per acquisition
Total Spent on Bounties
~$70M
Daily Growth at Peak
7-10%
Outcome
Sold to eBay for $1.5B
Buying viral coefficient with cash works if (and only if) the network effect can take over before you run out of money. PayPal was a calculated bet that ended in success — most companies that try this run out of cash before the network kicks in.
Decision scenario
The K-Factor Trade-off
You're Head of Growth at a consumer fitness app at 80K MAU. Current K = 0.18 with a 22-day cycle time. You have one quarter to improve viral growth. Two competing initiatives are on the table.
MAU
80K
Current K
0.18
Cycle Time
22 days
Inviter %
12%
Decision 1
Initiative A: Add a $5 cash bounty for each successful referral, projected to lift K from 0.18 to 0.45. Initiative B: Move the invite prompt from the settings page to the post-workout success screen and add SMS-share, projected to lift K from 0.18 to 0.32 AND cut cycle time from 22 days to 6 days.
Launch Initiative A — the higher K (0.45 vs 0.32) will produce more users per cycle and the cash incentive will drive immediate behaviorReveal
Launch Initiative B — moderate K lift but a 4x reduction in cycle time, with no ongoing bounty cost✓ OptimalReveal
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Viral Coefficient into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn Viral Coefficient into a live operating decision.
Use Viral Coefficient as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.