Network-Effect Freemium Boundary
Keep network-building behavior free and charge when users restrict the network
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 97%
Start by identifying the user behavior that increases the platform's value for everyone, then protect that behavior from the paywall. GitHub made public repositories free because each public project attracted developers, exposed useful code, and strengthened the network. It charged when individuals or companies wanted private repositories, a transition that signaled commercial value and a willingness to pay. The mechanism aligns distribution and monetization: free participation grows the ecosystem, while privacy, control, and enterprise use fund the service. Unlike storage or time limits, this boundary does not encourage users to ration beneficial activity. The result is a freemium model in which free users are not merely unconverted customers; they actively improve the product and expand its reach.
Origin
Ben Gilbert and David Rosenthal derived the rule while examining why GitHub's free public repositories and paid private repositories produced unusually strong growth and monetization.
Core principles
- 01Make participation that strengthens the network free
- 02Charge when customers receive private or exclusive value
- 03Align monetization with natural changes in user intent
- 04Avoid limits that encourage customers to reduce valuable usage
- 05Place the paywall where willingness to pay becomes obvious
How to run it
- 1
Map the Network Effect
Identify which user actions create value for other participants, attract new users, or make the platform more useful over time.
Pro tip Look for content, collaboration, reputation, liquidity, or data that becomes more valuable when publicly shared.
Watch out Do not assume all usage creates a network effect merely because users share one platform.
- 2
Protect Growth-Producing Usage
Keep the behavior that strengthens the network free and easy to access. Minimize restrictions that cause users to ration or abandon that activity.
Pro tip Treat active free users as contributors to distribution rather than failed conversions.
Watch out A usage cap can damage growth if customers respond by deleting or withholding valuable contributions.
- 3
Locate the Value Transition
Find the moment when users seek privacy, exclusivity, administrative control, compliance, or commercial deployment. This transition should correspond to substantially greater customer value.
Pro tip Observe changes in intent rather than relying only on raw consumption thresholds.
Watch out Do not place the paywall before users have experienced the network's core value.
- 4
Attach Pricing to the Transition
Charge for the private or controlled mode while preserving the public growth loop. Make the distinction simple enough that customers immediately understand why payment is required.
Pro tip Use packaging language that mirrors the customer's actual job, such as public versus private collaboration.
Watch out Complex tiers can obscure the natural reason to upgrade.
- 5
Validate Both Sides
Measure whether the free tier accelerates acquisition and whether the paid boundary converts customers with strong intent. Adjust the boundary if either growth or monetization weakens.
Pro tip Track network contribution and conversion separately instead of judging the free tier only by direct revenue.
Watch out Optimizing short-term conversion can destroy the free activity that created demand.
In the wild
GitHub allowed anyone to host public repositories for free, making open-source projects and personal code searchable and accessible. When a developer or company wanted to hide a repository and use the platform for proprietary work, GitHub charged for that privacy. Public usage expanded the developer ecosystem, while private usage generated recurring revenue.
→ GitHub achieved rapid adoption while building a substantial subscription business around private and enterprise development.
A design platform could allow creators to publish reusable components publicly for free because every public component improves discovery and attracts more designers. Teams would pay when they need private libraries, controlled access, approval workflows, and proprietary brand assets.
→ Public contributions grow the ecosystem while private collaboration supports monetization.
Common mistakes
Charging for the Growth Loop
Putting the paywall around network-building participation suppresses the activity that makes the product valuable and discoverable.
Using Arbitrary Consumption Caps
Storage or usage limits can encourage customers to delete content or reduce engagement rather than upgrade.
Confusing Popularity With Network Effects
A large user base does not establish a network effect unless one user's participation creates meaningful value for others.
Is it for you?
Best for
It is best for collaborative products whose free users create content, connections, or activity that benefits other users.
Not ideal for
It is not ideal for standalone utilities where one customer's usage creates little or no value for others.
From the transcript
“it's like the perfect place to draw the freemium line.”
“if it requires network effects, it should be freemium. If it's a utility for you personally, it can be time-bound trials.”
“By me using GitHub for free, does it make GitHub better for everyone else? Absolutely.”
From the episode
GitHub