Some products grow because their users bring more users. A new sign-up invites colleagues, those colleagues invite others, and the loop turns without a matching rise in ad spend. The K-factor is the number that tells you whether that loop is actually working, and by how much. For a founder watching customer acquisition cost climb, it is one of the few levers that can bend growth and CAC in the right direction at the same time.

What is the K-factor?

The K-factor, borrowed from epidemiology, measures how many new users each existing user generates through referrals. The formula is simple: K = invitations sent per user × conversion rate of those invitations. If the average user sends 5 invites and 20 percent convert, K = 1.0, meaning every user brings exactly one more. Above 1.0, growth is self-sustaining and compounds; below 1.0, referrals amplify other channels but do not run on their own. Most real products sit between 0.2 and 0.7, so even a fraction is valuable.

How to calculate it correctly

The arithmetic is easy; the discipline is in the inputs. Measure invitations per user over a fixed window, not lifetime, and count only invites that actually went out. For conversion, divide accepted sign-ups by invites sent, not by invites delivered, since undelivered invites still cost you reach. A worked case: 1,000 users send 4,000 invites in a month, and 600 become users. Invites per user = 4.0, conversion = 15 percent, so K = 0.6. That single number now tells you a referral program contributes 60 percent as many users as you already had, before any paid channel.

Viral cycle time: the multiplier everyone forgets

K-factor decides whether you grow virally; viral cycle time decides how fast. Cycle time is the average gap between a user joining and their invitees joining. Two products with the same K = 0.7 grow at wildly different speeds if one cycles in 2 days and the other in 20. Halving cycle time can do more for growth than nudging K upward, because the loop simply runs more often. Dropbox shortened its loop by rewarding both inviter and invitee with storage the moment a referral landed, turning a slow loop into a fast one. The compounding is dramatic: at K = 0.5 with a 5-day cycle, an initial 1,000 users grow to roughly 2,000 within two months on referrals alone, but stretch the cycle to 20 days and the same K needs most of a year. Hotmail rode exactly this dynamic in the 1990s, reaching 12 million users in 18 months on almost no ad spend by appending a single referral line to every email.

How to improve your K-factor

Three levers move the number, and they compound.

  • Raise invites per user. Make sharing a natural part of the core action, not a buried button. PayPal famously paid $10 to refer and $10 to join, and grew roughly 7 to 10 percent daily at its peak by making the invite the product.
  • Raise conversion. A warm invite from a colleague converts far better than a cold ad; reduce friction so the invitee reaches value in under 60 seconds. Personalised invites can convert 2 to 3 times better than generic ones.
  • Shorten cycle time. Trigger the invite at the moment of peak value, not days later, and the same K compounds faster.

When the K-factor matters, and when it does not

Virality suits products used in groups or networks: messaging, collaboration tools, marketplaces, anything more useful when a colleague is also on it. It matters far less for solo, single-player software, where a K of 0.1 is normal and not worth chasing. For most B2B SaaS, a realistic goal is a K of 0.3 to 0.5 as a discount on paid acquisition rather than a replacement for it. Treat referral as a CAC reducer, and the economics speak for themselves.

The link to acquisition cost and financing

A healthy K-factor is, in effect, free customers, and it directly lowers blended CAC. That matters beyond marketing: the cheaper and more predictable your acquisition, the more financeable your growth becomes. A company whose referrals cover 40 percent of new users has a CAC payback that funds itself faster, which is exactly the profile that supports non-dilutive financing. Improving K and treating acquisition as a capital expenditure, the idea behind the EBITCAC framework, are two sides of the same coin.

Common mistakes when measuring K

Three errors quietly inflate the number. Counting invites delivered rather than sent hides the reach you actually lost. Measuring over a user's lifetime rather than a fixed 30-day window flatters early adopters and masks decay over time. And blending paid referral incentives into organic K makes a bought number look viral, so track incentivised and organic loops separately. A K of 0.6 that holds without incentives is worth far more than a K of 0.9 propped up by $20 referral bonuses, because only the organic loop keeps running once the budget stops.

Frequently asked questions

What is a good K-factor? Anything above 1.0 is rare and means self-sustaining growth. Most successful products sit between 0.2 and 0.7, where referrals meaningfully discount paid acquisition. For B2B SaaS, 0.3 to 0.5 is a strong, realistic target.

How is the K-factor calculated? K = invitations sent per user × conversion rate of those invitations. If users send 5 invites and 20 percent convert, K = 1.0. Measure both inputs over a fixed window for an accurate figure.

Is a high K-factor enough on its own? No. Viral cycle time, the speed of the loop, matters just as much. A K of 0.7 cycling every 2 days outgrows the same K cycling every 20 days, so optimise both.

Does the K-factor matter for B2B SaaS? Yes, but usually as a CAC reducer rather than a standalone engine. A K of 0.3 to 0.5 can cut blended acquisition cost meaningfully and make growth easier to finance.