Without SourceLoop
UntaggedKayden Floyd
- SourceUnknown
- MediumUnknown
- CampaignUnknown
- Landing pageUnknown
Free tool
Calculate K-factor and project user growth over time. Plug in invites per user, conversion rate, and viral cycle time. See whether your product is truly viral, sub-viral but accretive, or just running on paid acquisition.
K-factor and growth projection
User growth over time
| Metric | Value |
|---|
How it works
Two numbers drive the math. The third (cycle time) drives how fast it compounds.
i = 5 invites/user c = 15% convert K = 0.75 cycle = 7 days
Invites sent per active user (from your invite logs). Conversion rate of those invites (signups / invites). K = i × c.
K above 1 grows exponentially. K below 1 grows linearly toward an asymptote. Cycle time controls how steep either curve climbs.
Growth at K = 0.75
Push i first (one-click invites, address book imports). Optimize c second (better invite copy). Reduce cycle time aggressively.
Concepts explained
K-factor is two numbers (i and c) plus a clock (cycle time). Everything else is decoration.
K-factor
K = invites per user × conversion rate of invites. K > 1 means viral exponential growth. K = 0.5 means each user brings 0.5 new users on average, halving on each cycle.
Viral cycle time
How long it takes a new user to invite the next batch. Shorter cycles compound faster: a K=1.2 product with 7-day cycles grows much faster than the same K with 30-day cycles.
Invites per user (i)
Average number of invitations each user sends. The easier this is (one-click sharing, address book imports), the higher the i. Aggressive invite flows can hit 8-12.
Invite conversion rate (c)
Share of invitations that become new users. Personal connections convert higher (15-30%). Bulk address book imports convert lower (2-8%). The trade-off between i and c is the core viral lever.
Saturation
Real K decays as your audience saturates. Early-stage K=1.5 products often drop to K=0.6 by the time they hit 1M users because their market is maturing. Plan for decay.
Why K isn't everything
K=0.5 is sub-viral but still doubles your effective LTV (every paid customer brings half a free customer). Most successful products run at K=0.3 to 0.7, not K>1. Don't chase virality at the expense of retention.
Best practices
Push i before c
Going from 2 to 5 invites per user is usually easier than going from 10% to 25% conversion. One-click sharing, address book imports, integration with messaging apps.
Reduce cycle time aggressively
Shorter cycles compound harder than higher K. A 7-day-cycle product at K=1.0 grows faster than a 30-day-cycle product at K=1.2.
Don't chase K=1 at the expense of retention
A K=0.5 product with great retention beats a K=1.2 product where users churn in week one. Viral acquisition feeds the bucket; retention keeps it.
Plan for K to halve in 18 months
As your audience saturates, K decays. Today's K = 1.5 will probably be K = 0.6 to 0.8 by year 2. Don't over-rotate the plan to current K.
Measure K cohort by cohort
Old cohorts hide today's K. The new-user K from this month is the only number that predicts next month's growth.
Built by the team behind SourceLoop
Guide
K-factor (or viral coefficient) measures how many new users each existing user brings in through invites or sharing. The formula:
K = i × c
where:
i = average invites sent per user
c = conversion rate of those invites (0 to 1) K = 1 means each user brings exactly one new user. K = 0.5 means half a new user. K = 2 means each user brings two new users. K > 1 is the threshold for sustained exponential growth from virality alone, with no paid acquisition needed.
With viral cycle time T (the time for a new user to invite the next batch), starting users U₀, and time horizon t, the projected total users after N = t / T cycles:
If K = 1: U(t) = U₀ × (1 + N)
If K ≠ 1: U(t) = U₀ × (1 - K^(N+1)) / (1 - K) For K below 1 the formula converges to U₀ / (1 - K) as N grows. So a K = 0.5 product with 1,000 starting users will asymptotically approach 2,000 users from virality alone. The first cycle adds 500, the second adds 250, the third 125, etc. Decaying contribution.
For K above 1 the formula explodes exponentially. K = 1.5 with 7-day cycles takes 1,000 users to ~80,000 in 90 days. K = 2.0 takes them to ~14M. Real-world products almost never sustain K > 1 for long because audiences saturate, but the early-stage windows where K > 1 is the kind of growth that made Hotmail, Dropbox, and Slack famous.
Cycle time controls how quickly K compounds. Two products with the same K = 1.0 but cycle times of 7 days vs 30 days will end up at radically different sizes after a year. The short-cycle product has 52 cycles; the long-cycle product has 12. With K = 1, that's 52x growth vs 12x growth in the same calendar time. Cycle time is often a bigger lever than K-factor for early-stage viral products.
K is rarely constant over time. It tends to start high in the early adopter phase (K = 1.5 to 2.0 is common in the first six months for products that go viral), then decays as the audience saturates, the most-likely-to-invite users have already invited their network, and the invitee pool becomes less and less responsive. Most successful products settle into K = 0.3 to 0.7 for the long run, which is still highly accretive even though it's no longer technically viral. Plan budgets assuming today's K will halve within 18 months.
Your product has 1,000 users. Each user invites 5 others on average. 15% of invites convert to new users. K = 5 × 0.15 = 0.75. Sub-viral. Cycle time is 7 days, so over a 90-day period (~13 cycles), the projection is 1,000 × (1 - 0.75^14) / (1 - 0.75) ≈ 3,930 users. Per-cycle contribution drops rapidly because K is under 1. Bump i to 8 (more aggressive invite flow) and K jumps to 1.2. Same 90 days now project to 1,000 × (1 - 1.2^14) / (1 - 1.2) ≈ 59,000 users. Same i improvement (5 to 8) at lower c (15% to 12%) and K = 8 × 0.12 = 0.96, projection at 90 days is ~10,500. Tiny moves across the K = 1 threshold matter enormously.
FAQ
Enter the average invites each user sends, the conversion rate of those invites, and optionally a starting user base, viral cycle time, and time horizon. The calculator computes K-factor (invites × conversion rate), per-cycle growth multiplier, total users projected at the time horizon, and shows the growth curve. The K verdict tells you whether the product is truly viral, sub-viral but accretive, or essentially flat.
K > 1 is considered truly viral and rare in practice. Most successful consumer products run at K = 0.3 to 0.7, meaning every paid acquisition brings 0.3 to 0.7 free users. K = 0.5 effectively halves your CAC. Hotmail famously hit K > 1 with 'PS: Get your free email at Hotmail' in every outbound. Dropbox sat around K = 0.5 to 0.7 in its hottest growth phase. WhatsApp was sustained K > 1 for years.
Viral coefficient measures organic invite-driven growth: the user invites someone naturally (sharing a feature, sending a doc). Referral programs add a paid incentive ($X off, double-sided rewards). Both can be modeled with K, but referral programs typically have lower i (people don't invite as many) but higher c (incentive boosts conversion), so the net K can be similar or different depending on the design.
Two reasons: audience saturation (the easiest-to-acquire users are gone) and invitee quality (early adopters invite enthusiasts; later users invite people less likely to convert). Early-stage products often see K = 1.5 to 2.0 in the first year, then K decays to 0.5 to 0.8 as they cross 1M users. Plan budget assuming K will halve from your current measurement within 18 months.
Generally, optimize i first. Going from i=2 to i=5 is usually easier than going from c=10% to c=25%. One-click invite buttons, address book imports, integrations with messaging apps all push i. Optimizing c requires changing the invite copy, the landing experience, and the value proposition for the recipient, which is more product work. Both matter, but i is the lower-hanging fruit.
Viral cycle time is how long it takes a new user to invite the next batch. A K=1.2 product with 7-day cycles grows from 1,000 to ~5,200 users in 90 days. Same K with 30-day cycles only reaches ~2,500 in the same period. Cycle time compounds harder than K because growth is exponential in cycles. Reducing cycle time from 30 days to 14 days has a bigger impact than going from K=1.0 to K=1.2.
Yes. No signup, no email gate. We host it because the same teams optimizing for viral growth also need real attribution to know which referral channels actually deliver retained users, which is what SourceLoop does.
Capture and send full attribution data from every signup, lead, booking, and sale to your CRM and ad platforms, so you know exactly what's driving revenue.
Without SourceLoop
UntaggedKayden Floyd
With SourceLoop
Auto-taggedKayden Floyd