Hand-pick a few demanding teams in a tight community and get them using the product hard, because concentrated density exposes flaws and creates pull broad launches cannot.
Slack
Slack is a team communication platform that organizes work into channels and connects to the tools teams already use. It grew out of Tiny Speck, the studio behind the failed online game Glitch, when founder Stewart Butterfield turned the team's internal chat tool into a product in 2013. Its two stories run in sequence: first win a narrow, tech-forward set of teams willing to try something new, then let the fact that Slack gets better with every colleague added pull entire companies in.
Beachhead: begging a handful of tech-forward friends to try it
The problem. Slack launched into a category, workplace communication, where every team already had email, IRC, and IM, so nobody was actively shopping for a replacement. A messaging tool is also worthless in an empty room: a broad public launch would have scattered a few curious individuals across thousands of teams, none reaching the density needed to feel useful. Butterfield needed real teams using it hard enough to expose what was broken.
The approach. Rather than court all communication users, Tiny Speck hand-picked a beachhead of six to ten companies chosen because they were friends first, very tech-forward, and eager to try new products. These included Cozy, a rental-management software startup whose board Butterfield sat on, and the music service Rdio. As Butterfield put it, "We begged and cajoled our friends at other companies to try it out and give us feedback."
How it solved it. The narrow, high-need segment gave Slack concentrated, honest usage instead of thin curiosity: by May 2013, roughly 45 companies were on it, enough to refine the product before any public exposure. When Slack opened its "preview release" in August 2013 (deliberately avoiding the word "beta" so nobody assumed it was buggy), 8,000 people requested invitations on the first day, and 15,000 within two weeks. The beachhead had turned a dead-start category into a launch with a running head of demand.
Network Effect: the product that got better with every colleague added
The problem. A single person on Slack has almost nothing: on February 1, 2014, Slack counted just 14 daily active users. The tool's entire value depends on the people you work with also being there to talk, share files, and coordinate in channels, so the challenge was getting whole teams active rather than isolated individuals who would drift back to email.
The approach. Slack leaned into within-company network effects by making adoption spread naturally across a workspace: channels, shared files, and integrations meant each new member and each new conversation made the tool more useful for everyone already inside. Rather than sell top-down, Slack let one team pull in the next. Rdio was the clearest proof: it started with a small group of front-end developers, "then it spread to the whole engineering group and then to all 120 people in the company."
How it solved it. That compounding value showed up as extreme stickiness once a team crossed a usage threshold. Butterfield found that any team that had exchanged 2,000 messages had genuinely tried Slack, and "after 2,000 messages, 93% of those customers are still using Slack today." The mechanic scaled: Slack grew from those 14 daily users in early 2014 to roughly 1.1 million monthly active users by 2015, as activating entire teams, not individuals, became the engine of growth.