Growth Is a System (Acquisition–Retention–Monetization)
Change one part of the growth system and you change them all—so fix the true source.
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 3
- Confidence
- —
Growth is a system between acquisition, retention and monetization: change one and you affect them all. The deeper lesson is that when a problem shows up in one area, the solution often lives in a different part of the system. Retention problems are frequently caused by acquiring the wrong people; monetization issues often stem from engagement problems. Teams tend to identify the symptom (low revenue retention, low conversion) and immediately pull levers inside that same area, without stepping back to ask which part of the system is actually creating it. This systems-level thinking — amplified in marketplaces and networks where dynamics compound — is what Balfour says separates great growth people from merely good ones.
Origin
A core Reforge teaching Balfour has written about extensively; framed here as the growth-model / growth-system view of acquisition–retention–monetization.
Core principles
- 01Acquisition, retention and monetization are one interlocked system.
- 02The symptom's location is often not the cause's location.
- 03Wrong-fit acquisition manufactures downstream retention loss.
- 04Systems thinking separates great growth people from good ones.
How to run it
- 1
Locate the symptom
Identify where the problem surfaces — e.g. low revenue retention, low conversion — but treat that only as the symptom.
Watch out Working levers inside the symptom's area is the default trap.
- 2
Trace it to the source
Step back and ask which part of the acquisition–retention–monetization system is actually creating the problem.
Pro tip Retention issues are often an acquisition problem; monetization issues often an engagement problem.
- 3
Act on the real lever
Move the lever in the part of the system that causes the issue, even if that means a different team owns the fix.
Pro tip In marketplaces, every demand conversation is a supply conversation and vice versa.
Watch out System dynamics are amplified in marketplace and network products.
In the wild
An Airbnb guest-retention team found retention was driven by how good the trip was, not by anything they could do as a retention team — so the company shifted resources to trip and host quality (response rate, reviews) instead.
→ The 'retention team' arguably shouldn't exist; the real lever was trip experience.
Early HubSpot's weak renewals traced to salespeople closing the wrong personas/use cases. Rather than add features, HubSpot changed sales comp so reps weren't paid for selling to the wrong customer, which immediately changed behaviour.
→ Retention improved by fixing top-of-funnel acquisition, not the retention surface.
Common mistakes
Fixing the symptom's neighbourhood
Pulling levers only inside the area where the metric drops ignores that the cause usually lives elsewhere in the system.
Is it for you?
Best for
Growth practitioners and product leaders diagnosing stalled metrics.
Not ideal for
Teams wanting a single-lever quick fix without systems analysis.
From the episode
Brian Balfour: 10 lessons on career, growth, and life