The Pivot That Created a Billion-Dollar Company
Slack was not built as a workplace communication platform. It was built by a team that was trying to build a massively multiplayer online game called Glitch, which launched in 2011 and shut down in 2012 after failing to attract the audience required for the game to be commercially viable. During the development of Glitch, the team had built an internal communication tool to coordinate their distributed development work — a tool they had come to depend on so completely that when the game failed, the tool seemed potentially more valuable than the game it had been built to support.
The pivot decision that Stewart Butterfield and his co-founders made after Glitch’s failure — to develop and commercialise the internal communication tool rather than starting a new project from scratch — is now studied as one of the most successful pivots in startup history. The tool had been validated by the team’s own intensive use, had been refined through the specific requirements of coordinating distributed technical work, and had demonstrated the key product characteristics that would make Slack successful: the ability to organise conversations by topic in persistent channels, the integration with other tools through a simple API, and the search capability that made historical context accessible without digging through email.
The Product-Led Growth Engine
Slack’s growth from zero to a hundred million dollars in annual recurring revenue in fewer than three years was driven primarily by a product experience that users wanted to share with their colleagues and organisations. The product-led growth mechanic that made this possible: Slack was only useful when multiple people were using it simultaneously, creating the natural internal viral loop in which every new user had an incentive to invite additional users to join the same workspace. The product that generates natural internal sharing is the product that grows within organisations without a sales team.
The Slack free tier design that most powerfully drove adoption: the limitation of free tier access to the ten thousand most recent messages, rather than a time-based restriction or a feature-based restriction. The team that adopted Slack and found it genuinely valuable would eventually approach the message history limit and face the choice between paying to preserve their conversation history or losing access to the knowledge accumulated in their previous discussions. This limitation was both fair (the team had genuine value from the free tier) and commercially effective (the limitation was felt most acutely by the teams that had become most dependent on Slack — precisely the teams most willing to pay).
Enterprise Expansion: From Viral Adoption to Commercial Scale
The enterprise sales motion that Slack built after establishing viral adoption across thousands of small teams and departments: the product-led sales approach in which the commercial team identified the organisations with the highest concentration of Slack usage across multiple teams, approached those organisations about formalising and expanding the relationship through an enterprise contract, and used the existing product adoption as both proof of value and leverage in the commercial negotiation. The enterprise buyer who was asked to pay for a tool that their employees were already using and already dependent on was in a very different negotiating position than the enterprise buyer being asked to evaluate a new tool without existing adoption.
The enterprise contract negotiation dynamic that most determined Slack’s enterprise pricing power: the switching cost that accumulated as teams integrated Slack with their other tools, stored years of conversation history in their Slack workspace, and built workflows around Slack’s specific functionality. The organisation that had been using Slack for three years, had ten thousand employees whose institutional knowledge lived in Slack channels, and had dozens of workflow integrations built on Slack’s API was not making a cost-benefit decision about Slack versus an alternative — it was making a decision about whether the cost and disruption of switching was worth the savings.
The Microsoft Teams Challenge
The competitive threat that most tested Slack’s market position: Microsoft’s 2017 launch of Teams, a workplace communication platform bundled into Office 365 at no additional cost for the hundreds of millions of organisations that were already paying for Microsoft’s productivity suite. The competitive dynamic was unprecedented: Slack was being asked to compete against a product that its target customers were receiving for free as part of software they were already buying.
The Slack competitive response that most clearly revealed the strength and the limits of the product-led growth model: the significant investment in product differentiation, developer ecosystem development, and enterprise feature parity that attempted to maintain the product quality advantage that had driven Slack’s adoption. The product-quality argument was genuine — Slack’s product had specific advantages in user experience, integration depth, and channel organisation that Teams did not immediately match. But the free-bundled competitor argument was ultimately more powerful in large enterprise accounts where IT purchasing decisions and Microsoft relationship management frequently determined the platform choice regardless of product-quality comparison.
The Salesforce Acquisition and Its Lessons
Salesforce’s 2021 acquisition of Slack for 27.7 billion dollars represented one of the largest acquisitions in enterprise software history and reflected Salesforce’s strategic assessment that workplace communication was becoming the central platform through which all enterprise software would be accessed and used. The acquisition thesis: as work became increasingly digital and increasingly distributed, the platform where workers spent the most time would become the platform with the most influence over adjacent software purchasing decisions.
The Slack case study’s most transferable lesson for founders and product builders: the product that is built to solve a genuine internal problem and that its builders use intensively and improve through their own use has a product authenticity that market-research-driven product development rarely produces. Slack was built by people who needed it, refined through the specific pressures of their own work, and commercialised only after the team’s intensive use had proven the product’s value in the most demanding context available — their own. The authenticity of the product experience that this genesis produced was visible to early users and was the foundation of the trust that made Slack’s viral growth possible.