The Cold Start Problem
Andrew Chen
My take
Network effects sound inevitable when we study companies after they have already reached scale. The Cold Start Problem focuses on the less glamorous period when a product has too few people to deliver the value it promises. I found the atomic network especially useful because it turns a huge ambition into a local operating problem: identify the smallest group that can become self-sustaining, make the experience valuable for its hardest-to-acquire members, and learn how to repeat that unit. The book also shows why growth can’t run on acquisition alone. Density, trust, participation, and retention decide whether each new member strengthens the network or makes it harder to use.
Core insight 1: Start with the hard side
Every network has a group whose participation creates disproportionate value for everyone else. In a marketplace it may be sellers or drivers. In a content product it may be creators. If that group has weak incentives or a poor experience, adding the easier side only produces more unmet demand.
The answer is by building a product that solves an important need for the hard side.
The hard side deserves more than a larger acquisition budget. Its members need a reason to join before the network is established and a reason to keep contributing after other options appear.
How to practice: Name the group that makes the experience valuable for everyone else. Interview five members about what they need before joining, what makes early participation worthwhile, and what would make them leave.
Core insight 2: Build one atomic network before chasing scale
A broad launch can create impressive registration numbers while leaving every user inside a sparse experience. An atomic network is small enough to fill deliberately and complete enough to provide real value. Geography, profession, school, interest, or use case can create the initial boundary.
Cofounder Nate Blecharczyk is highly quantitative and had determined that 300 listings, with 100 reviewed listings, was the magic number to see growth take off in a market.
That advantage appears after a group becomes active enough to generate invitations, content, matches, or transactions. The first goal is density, followed by replication.
How to practice: Define the smallest bounded network that could work on its own. Set a concrete threshold for supply, demand, and repeat activity, then focus the launch on crossing those thresholds in one place.
Core insight 3: The product and the network must reinforce each other
Useful software can attract an initial audience, but the network has to increase the value of returning. At the same time, social activity can’t rescue a weak product. The experience needs a useful individual action and a reason that action improves when other people participate.
It’s easy to think of Zoom’s simplicity as a competitive advantage, but this kind of simplicity is actually hard to implement in practice. Customers request endless features while competitors emerge with a longer list of functionality. Yet I observe that it’s a distinctive quality of networked products that they often do one thing well.
This distinction prevents a team from labeling every social feature a network effect. The effect becomes meaningful when the network changes the value or defensibility of the product.
How to practice: Write the product’s value for one person using it alone, then write what becomes more valuable with ten, one hundred, and one thousand relevant participants. Measure the behaviour that connects those stages.
Core insight 4: Early weakness can hide a strong trajectory
New networked products often look narrow, manual, or unserious because their first community is small and specific. That appearance can hide the mechanism that matters: each participant makes the experience more useful or more attractive to the next one.
New products often disrupt markets by starting on the low end, providing “good enough” functionality, and growing from there into the medium, and eventually into the core market of the incumbents.
The right early question is whether a small group cares enough to return and contribute. A tiny network with strong internal activity has more potential than a broad audience that never interacts.
How to practice: Review your early metrics at the level of one community instead of the full user base. Look for repeat interactions, successful matches, contributions, and invitations inside that group.
Core insight 5: Software is only half of the system
Networked products are shaped by the people inside them, including their incentives, norms, status, trust, and behaviour. Product design can guide those forces, but it can’t treat them as predictable interface components.
The term “network effect” has almost become a cliché. It’s a punch line to difficult questions, like “What if your competition comes after you?” Network effects. “Why will this keep growing as quickly as it has?” Network effects. “Why fund this instead of company X?” Network effects. Every startup claims to have it, and it’s become a standard explanation for why successful companies break out.
The people form the other half. As the network grows, the team has to manage quality, participation, discovery, and safety with the same care it gives features and infrastructure.
How to practice: Add a network-health review beside the product review. Track who creates value, who receives it, where participation becomes uneven, and which behaviours improve or damage the experience.
The Cold Start Problem turns network effects from a slogan into a sequence of operating challenges. Start with a dense and useful atomic network, protect the people who create its value, and expand only when the first unit can sustain itself.
Other reminders
Getting an email notification that says your boss just shared a folder with you is a lot more compelling than a marketing message.
Yet because of the dynamics of market saturation, a product’s growth tends to slow down and not speed up. There’s no way around maintaining a high growth rate besides continuing to innovate.
Enjoyed this? You'll like Open Loops.
Every Thursday, I share what I’m learning about growth, work, and the long game. Join 3K+ readers.
You might also like
