· product-managers Editorial · Career · 7 min read
Product Growth Loop Viral Coefficient Analysis
How PMs model growth loops and viral coefficients to find where a product actually compounds.
“Growth loop” has become one of those PM interview terms that gets thrown around with far more confidence than precision. Candidates say “we need to build a viral loop” the way people say “let’s leverage synergies” — as a gesture toward sophistication rather than an actual model. This article is about the actual model: what a growth loop is structurally, how to compute a viral coefficient correctly, and why most products that claim virality don’t have any.
Growth Loops vs. the Funnel Mental Model
The traditional acquisition funnel — awareness, consideration, conversion, retention — treats growth as a pipeline you pour more people into. A growth loop treats growth as a compounding system where existing output becomes new input. The distinction matters because it changes what a PM optimizes.
In a funnel model, growth is a function of spend: more ad budget, more top-of-funnel traffic, more conversions downstream. In a loop model, growth is a function of a coefficient: each unit of existing usage produces some fraction of a new unit, and if that fraction exceeds a threshold, growth compounds without additional spend.
A canonical example is a file-sharing product where User A uploads a document and sends a link to User B, who needs an account to view it and, in viewing it, is exposed to the product and eventually uploads their own documents, sending links to Users C and D. The loop closes when the new users become new senders. A funnel model would track “signups from shared links” as a channel. A loop model tracks the multiplier itself: how many new users does each existing user generate, and over what time period.
Anatomy of a Growth Loop
Every growth loop, viral or otherwise, has four components a PM should be able to name explicitly for their own product:
- The trigger — what causes an existing user to take an action that reaches other people (uploading, inviting, sharing, publishing).
- The action — the specific behavior that produces outward reach (a link sent, a post published, an email invite fired).
- The exposure — what happens when a new person encounters that output (they see a shared document, land on a public profile page, receive an invite email).
- The conversion — what fraction of exposed people become new users who eventually trigger the loop themselves.
Weak growth loop designs usually fail at step 3 or 4, not step 1 or 2. Teams obsess over making sharing easier (step 2) while the actual bottleneck is that exposed non-users see a login wall with no preview of value (step 3), or the onboarding flow doesn’t get new users to their own first “trigger” moment fast enough (step 4).
Computing the Viral Coefficient Correctly
The viral coefficient, commonly denoted k, is the number of new users each existing user generates through the loop. The basic formula:
k = i × c
Where i is the average number of invites (or shares, or exposures) sent per user, and c is the conversion rate of those invites into new active users.
If k is greater than 1, the loop is mathematically viral: each user replaces themselves plus more, and the user base grows without additional acquisition spend, at least in theory. If k is less than 1, the loop still adds value — it’s a real acquisition channel — but it will not compound on its own and needs to be paired with paid or other acquisition.
The mistake most PMs make is computing k once, at launch, with enthusiastic early adopters, and treating it as a fixed product property. In practice, k decays as the addressable network saturates (there are only so many new people your existing users know) and as invite fatigue sets in. A serious growth loop analysis tracks k over cohort time, not as a single snapshot number, and multiplies it against the cycle time — how long it takes one loop iteration to complete — because a k of 1.2 with a 30-day cycle time compounds far slower than a k of 1.1 with a 3-day cycle time.
Comparison: Loop Types and Their Realistic k Ranges
| Loop type | Example | Typical k range | Primary lever |
|---|---|---|---|
| Content/SEO loop | User-generated content indexed by search, drawing new visitors | 0.05–0.3 | Content volume × search visibility |
| Collaboration loop | Shared documents requiring recipient signup to view/edit | 0.3–0.9 | Collaboration frequency in existing workflows |
| Social/referral loop | Direct invites with an incentive (credits, discounts) | 0.1–0.5 | Incentive structure, invite friction |
| Network-effect loop | Product requires counterpart to function (marketplaces, communication tools) | 0.4–1.2+ | Two-sided liquidity, not just invite volume |
| Paid acquisition (not a loop) | Ad spend driving signups | N/A (k=0 by definition) | Budget, targeting, creative |
True k > 1 loops are rare outside of specific network-effect or communication products; most successful growth strategies combine a sub-1 loop with paid or organic acquisition rather than chasing pure virality, which is a healthier target for most PMs than the mythical self-sustaining viral product.
Common Analytical Mistakes
Confusing referral programs with growth loops. A referral program with a cash incentive is a paid acquisition channel wearing a growth-loop costume. If the loop stops the moment the incentive budget runs out, it was never compounding — it was subsidized.
Measuring invites sent instead of loop closures. Counting how many invite emails went out says nothing about growth. The number that matters is how many of those recipients became active users who themselves triggered the loop. Optimizing for invite volume without tracking closure rate produces vanity metrics.
Ignoring cycle time. As noted above, a slow loop with a good k can be economically worse than a fast loop with a mediocre k, because the compounding effect is time-bound, not just coefficient-bound. Any growth loop analysis presented without a cycle-time component is incomplete.
Treating the loop as static. k decays. A PM presenting a static viral coefficient as a permanent growth engine, without a plan for what happens as the addressable network saturates, is presenting a launch metric, not a strategy.
Interview Framing
Growth loop and viral coefficient questions show up frequently in growth PM and generalist PM interviews at consumer and marketplace companies. A strong answer names the trigger-action-exposure-conversion structure explicitly, computes or estimates a realistic k rather than assuming k > 1, and discusses decay and cycle time rather than presenting virality as a permanent state. Weak answers describe “making it easy to share” without any structural model of where the loop actually closes.
For a broader walkthrough of growth and analytical PM interview scenarios, including how to structure a growth loop answer under time pressure, see the Product Manager Interview Prep Guide.
FAQ
Is a viral coefficient above 1 required for a growth loop to be worth building? No. Most valuable growth loops have k below 1 and function as a durable, low-cost acquisition channel rather than a self-sustaining engine. A k of 0.3 that costs nothing in paid spend and compounds slowly over months can be more valuable than a one-time viral spike that decays to zero.
How do you measure a growth loop’s viral coefficient without dedicated analytics infrastructure? At minimum you need to track, per cohort, how many outbound actions (invites, shares, links) each user generates and what fraction of exposed recipients convert to activated users within a defined window. This can be built from event logs and a spreadsheet before investing in a full growth analytics stack — the model matters more than the tooling at first.
What’s the difference between a growth loop and a network effect? A growth loop is a mechanism describing how existing usage generates new usage. A network effect is a property describing how the product gets more valuable as more people use it. They often coexist — a network-effect product frequently also has a strong growth loop — but a product can have a growth loop without a true network effect, and vice versa. Conflating the two leads teams to assume virality where only a value-scaling relationship exists.