Network Effects Strategy

When to Apply

• Product's value increases with more users (network-effect products)
• Marketplace, social, or community products
• When evaluating viral growth potential
• Cold start problems (chicken-and-egg)
• Growth ceiling diagnosis

Core Framework

Atomic Network Definition

The smallest group where the product becomes self-sustaining. Define during onboarding:

"Does your product's value increase as more people use it?"
-> YES:
  "Let's define your Atomic Network — the smallest self-sustaining group.

   Reference thresholds:
   Slack: 3 people + 2,000 messages = 93% long-term retention
   Zoom: 2 people (smallest possible)
   Airbnb: 300 listings + 100 reviewed per city
   Uber: 15-20 concurrent drivers, ETA < 3 min per city
   Tinder: 20,000 users in a single market

   What is the minimum unit for YOUR product?
   How many users in one [team/city/community] make it work?"

Finding the threshold: Plot network size (X) vs engagement metric (Y). Look for the inflection point ("kink") where engagement spikes. Everything before the kink is anti-network-effect territory.

Anti-Peanut-Buttering

"Do NOT spread across segments until atomic network is achieved in the first one. Density > breadth."

Concentrating resources in one segment to achieve critical mass beats thinly spreading across many.

"Zero" Tracking

A "zero" = the product's core value cannot be fulfilled because the network is too sparse:

• No drivers available
• No listings for a search
• AI gives generic recommendation

Track zero rates per segment. Users who get "zeroed" churn AND don't return — the damage persists.

Escape Velocity — 3-Force Decomposition

Once atomic network is established, track three independent growth forces:

Escape Velocity Dashboard:
  Engagement: DAU/MAU 35% | D30 28% | Trend up -> HEALTHY
  Acquisition: Viral factor 0.6 | Amp 2.5x | Trend flat -> NEEDS WORK
  Economic: CAC down, LTV up | Ratio improving -> HEALTHY

  Weakest Force: ACQUISITION
  -> "Engagement strong but users aren't inviting others.
     At viral factor 0.95 you'd get 20x amplification vs 2.5x.
     Focus on referral loop design."

Identify weakest force and concentrate effort — applying TOC constraint logic to network growth.

Growth Ceiling Detection (5 Forces)

Monitor during periodic scans:

Competitive Position Dynamics

T2D3 Benchmark

For SaaS with network effects, from $1M ARR: Triple -> Triple -> Double -> Double -> Double $1M -> $3M -> $9M -> $18M -> $36M -> $72M

Decision Rules

1. Define atomic network first — no growth strategy without knowing the minimum viable network
2. Density before breadth — anti-peanut-buttering rule is non-negotiable
3. Zero rates are critical — track and minimize "zeroed" user experiences
4. Weakest force gets focus — TOC constraint logic applied to the three forces
5. Growth ceilings are early warnings — detect during growth, not after stall
6. Share dynamics are exponential — small leads compound, act fast

Anti-Patterns to Detect