Growth Framework

The Native Viral Loop
Framework

A method for designing virality into a product on purpose — from the first feature, not bolted on after launch. Four parts: the Philosophy, the Multiplier, the Diagnostics, and the Measure.

The shift this framework asks for

Most teams treat virality as a growth-team experiment — something you A/B test once the product exists. That is backwards. A viral loop is an architecture decision, not a growth hack. You cannot test your way to a loop the product was never built to support.

The Native Viral Loop Framework makes one demand: treat distribution as a product feature, not a marketing line item. Build it in from the first feature — and put every feature after it through the same filter.

The Loop Question

The whole framework collapses into one question you ask of every feature, in every spec, in every meeting:

"When someone uses this feature, who outside the product encounters it — and why would they step in?"

If a feature has a clean answer, you have found a loop worth designing. If it does not, that is not a failure — it is information. Not every feature carries the loop, but every feature must pass through the question. That habit, applied relentlessly, is the difference between a product that markets itself and one that needs to be marketed.

The framework — four parts

Philosophy sets the mindset. The Multiplier sets the target. The Diagnostics turn it into a repeatable decision. The Measure proves it. Work them in order.

01 — Philosophy

Build for the loop

Who the method is for, the two core ideas, and why distribution belongs in the product, not the marketing plan. Start here →

 02 — The Multiplier

Design toward the target

The number you are actually designing for: reach × conversion × speed. Why k-factor without cycle time is vanity. See the principle →
03a — Quick Test

The 60-second filter

Three questions to gut-check any feature or idea on the spot — in a meeting, a ticket, a Slack thread. Run the test →

 03b — Feature Review

The deep audit

Seventeen questions for features that pass the gut-check and deserve a serious viral-design pass before you build. Open the review →
04 — The Measure

K-Factor Calculator

Quantify the Multiplier and project growth cycle by cycle. The proof that turns a design decision into a number you can defend. Open the calculator →

Why design beats luck

Lower acquisition cost
The product carries part of its own distribution. Marketing supports the loop instead of replacing it.
Compounding, not linear
One user brings the next. A designed loop turns every cohort into the seed of the following one.
You can improve it
A deliberate k = 0.4 beats an accidental k = 0.9 — because you can only optimise what you built on purpose.

New to the underlying concepts? Start with the plain-English guide to what a viral loop is and how the viral coefficient works — then come back and apply the method.

Framework FAQ

What is the Native Viral Loop Framework?
A four-part method for designing viral growth into a product on purpose: the Philosophy (treat distribution as a product decision), the Multiplier (design toward reach × conversion × speed), the Diagnostics (the Quick Test and the Feature Review), and the Measure (the K-Factor Calculator).
How is this different from a growth-hacking checklist?
Growth hacks are experiments you run after launch. This framework treats virality as a product-architecture decision made before product-market fit — a filter every new feature passes through, not a tactic bolted on later.
Do I need a k-factor above 1 to benefit?
No. A deliberately designed k-factor of 0.4 beats an accidental 0.9, because you can only improve what you built on purpose. Even a modest loop meaningfully lowers acquisition cost — and you grow the Multiplier from there.
Who is the framework for?
Product managers, founders, designers, and developers who want their product to grow through how people use it — not only through marketing spend. It is built to be applied feature by feature, in real product decisions.
Start with the Philosophy → Run it with your team — the Kit →