Viral Coefficient & Cycle Time: The K-Factor Math
A K of 0.4 on a 3-day cycle buries a K of 0.7 on a 30-day cycle over a single quarter, and it isn't close. That surprised me the first time I ran the loops out. For years I'd treated the K-factor as the whole scoreboard. The viral coefficient is just invites per user times invite conversion rate (K = i × c), and most teams fixate on crossing K > 1 when the real lever is cycle time. K compounds once per loop, so a modest K that cycles fast wins over any planning horizon you'd actually put in a board deck. Sub-viral K isn't a failure. It's a CAC discount you can put a number on.
The canonical formula, and the input everyone fudges
The definition is boring and consistent everywhere, which is a good sign. As Startups.com puts it, "K = i × c, where i is invitations sent per existing user in a given period and c is the fraction of those invitations that convert to new active users." Above 1, each cohort more than replaces itself and you get self-sustaining exponential growth. Below 1, virality amplifies your paid acquisition without replacing it.
Napkin math to make it concrete. You have 100 users. Each sends 5 invites in the period, so that's 500 invites. Four percent convert, which gives you 20 new users. K = 5 × 0.04 = 0.2. Nothing exotic.
Here's the input everyone fudges: i. Teams measure invites offered — the number of times a share prompt appeared — instead of invites actually sent. That inflates i, which inflates K, which inflates the whole forecast. If your product shows a "refer a friend" button to 500 users and 60 of them actually send something, your i is built on 60, not 500. Measure the send event, not the impression.
The myth that you need K greater than 1
The K > 1 obsession is mostly Dropbox and Hotmail mythology, retold at every growth offsite until it feels like a law of physics. It isn't. MV3 Marketing's benchmark is blunt about it: "A K-factor above 1.0 produces exponential self-sustaining growth; most B2B SaaS operates at 0.15–0.7, where virality meaningfully reduces but doesn't eliminate paid acquisition dependence." Most real products live in that band. Wait for K > 1 before you count viral mechanics as a win and you'll wait forever.
I've made this mistake with real money. On one campaign I got so fixated on pushing i up that I bolted a cash bribe onto the referral flow. Invites went up. Conversion cratered, because the people getting invited could smell the bribe from orbit, and the new "users" churned inside a week. I juiced i and torched c, my K barely moved, and my payback got worse. StartupGrowthTactics frames the healthier view directly: "Even a K-factor of 0.3 or 0.5 significantly amplifies your other growth efforts and reduces overall customer acquisition costs." Sub-viral K is a durable multiplier, not a consolation prize.
Turning K into a CAC discount
Here's where the sub-viral number earns its keep. For any K below 1, the loop converges to a finite multiple. KPI Tree states it plainly: "When K is below 1.0, this converges to: Users = Initial Users × (1 / (1 − K))." Rahul Vohra frames the same math as an amplification factor, writing that he thinks of virality "not as the viral factor v, but as the amplification factor a = 1/(1−v)." Same equation, more useful vocabulary.
Now put a dollar sign on it. You pay a $50 CAC to acquire 1,000 users through paid channels, and your product carries a K of 0.4. The amplification factor is 1 / (1 − 0.4) = 1.67. So those 1,000 paid users pull in another 667, for 1,667 total. Your paid spend didn't change. It was $50,000 either way.
| Input | Value |
|---|---|
| Paid users acquired | 1,000 |
| Paid CAC | $50 |
| Total paid spend | $50,000 |
| K-factor | 0.4 |
| Amplification (1 / (1 − K)) | 1.67× |
| Total users after loop converges | 1,667 |
| Blended CAC ($50,000 / 1,667) | ≈ $30 |
That's a 40% haircut on CAC from a K nobody would brag about. The blended $30, not the raw 0.4, is the number that belongs in front of your CFO. If you're already tracking acquisition cost against payback and lifetime value, this slots straight into your LTV to CAC benchmark work and any unit-economics dashboard you maintain.
Why cycle time quietly dominates K
The amplification math above assumes the loop has run to completion. In real time, it hasn't, and how fast it runs is the part most models skip. Alexander Jarvis puts the mechanism cleanly: "The Viral Coefficient K is raised to the power of t/ct, so reducing ct has a far more powerful effect than increasing K." Cycle time, ct, is how long it takes an average user to complete a loop: receive access, get value, send invites, get those invites converted. Over a fixed horizon you get t / ct loops. K compounds once per loop. So loops matter more than the base.
Napkin math over one quarter, 90 days, deliberately round.
| Scenario | K | Cycle time | Loops in 90 days | Cumulative multiple (approx.) |
|---|---|---|---|---|
| Fast & modest | 0.4 | 3 days | 30 | ≈ 1.67× |
| Slow & strong | 0.7 | 30 days | 3 | ≈ 1.55× |
Read the multiples. The fast-and-modest loop converges close to its full 1.67× ceiling inside the quarter because it gets 30 turns. The slow-and-strong loop, despite a much higher K, only gets three turns and never approaches its own 3.33× ceiling in that window. Give the slow loop a full year and it eventually wins the theoretical race. But nobody plans a quarter around a loop that needs a year to pay off. Fast-and-modest wins the horizon you actually run.
The practical takeaway: instrument time-to-invite and time-to-convert as first-class metrics, not just the K ratio. Shaving a 10-day cycle to 3 days will usually move more growth than grinding your conversion rate up two points. And because cycle-time changes compound the same way a good payback-first budget decision does, it belongs in the same conversation about how fast money comes back.
The segment trap where your average K is lying to you
Here's the failure mode I see most in mature teams. They compute one blended K across the whole user base, feel fine about the 0.35, and move on. That average hides the one loop worth funding and drowns it in the loops that aren't.
The peer-reviewed Wharton/Goethe study by Schmitt, Skiera and Van den Bulte is the cleanest evidence here. They found the value "of a referred customer is at least 16% higher than that of a nonreferred customer with similar demographics and time of acquisition. However, the size of the value differential varies across customer segments; therefore, firms should use a selective approach for their referral programs." That last clause is the whole game. The 16% is an average across segments, and the segments diverge enough that the authors explicitly warn against a blanket program.
Apply that back to K. If enterprise users cycle in 40 days at a K of 0.2 while your prosumer segment cycles in 4 days at a K of 0.5, your blended number smears both into a mush that describes neither. You'd fund the wrong loop. Compute K per loop and per segment, then pour budget into the fast-cycle, high-conversion segment rather than the flattering average that makes every cohort look mediocre and equal. This is the same discipline that keeps cohort retention curves honest: the shape lives in the segments, never in the mean.
Instrumenting K from product data
You can't compute any of this from a spreadsheet of guesses. You need two events fired from inside the product, invite-sent and invite-converted, each carrying a timestamp so you can derive cycle time, and each attributable to a user so you can split by segment. Without those, i and c are estimates, and cycle time doesn't exist at all.
Product analytics tools that capture these events let you derive K and cycle time per cohort directly. Kixo is one example, where you can query invite funnels and cohorts without exporting raw logs. Whatever you use, the requirement is the same: real events, real timestamps, segment-level breakdowns. If you're validating whether a referral tweak actually moved c, treat it like any revenue experiment and hold it to statistical significance before you believe the lift.
What a good viral coefficient actually means
Stop asking "is my K good." It's the wrong question and it produces the K > 1 death march. Ask three better ones.
What's my amplification factor and the CAC discount that falls out of it — the blended $30, not the raw 0.4? How fast is my cycle, given that 30 loops at 0.4 beats 3 loops at 0.7 over a real quarter? And which segment's loop deserves the budget, when the average is hiding your best and worst loops inside one number?
Cycle time beats K. Sub-viral K is a discount you can bank. Averages lie. Build your referral model around those three and you'll defend a smaller, truer number in the board deck instead of a bigger one that falls apart the moment someone asks how you measured i.
FAQ
What is a good viral coefficient for B2B SaaS? Most B2B SaaS sits between 0.15 and 0.7, per MV3 Marketing's benchmark. Anything in that band is normal and useful. It lowers CAC without replacing paid. K > 1 is rare and mostly the exception you've heard about at conferences.
How do you calculate the viral coefficient?
K = i × c, where i is invites actually sent per user in a period and c is the share of those invites that convert to active users. Measure sent invites, not offered ones, or you'll inflate the whole forecast.
Why does cycle time matter more than the K-factor?
Because K compounds once per loop, and cycle time controls how many loops fit in your horizon. K is raised to the power of t / ct, so halving cycle time compounds harder than nudging K up, as Alexander Jarvis lays out.
Does a viral coefficient below 1 still help? Yes. For K below 1, total users converge to Initial × 1 / (1 − K), a finite multiple KPI Tree documents. A K of 0.4 gives you a 1.67× amplification on paid, a real, bankable CAC discount.