The original problem — the one they were actually solving. There wasn't one. Slack was an internal tool.
Founder background. Stewart Butterfield had already done this once. Flickr emerged from a failed massively-multiplayer game called Game Neverending and sold to Yahoo in 2005. Butterfield then founded Tiny Speck in 2009 with Cal Henderson, Eric Costello and Serguei Mourachov — all Flickr/Yahoo alumni — to build another browser game, Glitch.
The failure. Tiny Speck raised over $15M ($5M Series A, $10.7M Series B) from Accel and Andreessen Horowitz for Glitch. The game launched publicly in September 2011 and shut down in November 2012: too complicated, too slow, built on Flash with no mobile path (TechCrunch, "The Slack origin story," May 2019).
The pivot mechanics. Butterfield returned a substantial portion of the remaining capital to investors — a decision that bought him enormous credibility — and kept a small amount to pursue the internal chat tool the distributed team had built to coordinate between Vancouver, San Francisco and New York. Slack launched publicly at the end of 2013.
Validation and first customers. Slack's beta strategy was deliberately manual. Butterfield asked friendly companies — Rdio, Cozy, and others — to use it, then had the team read every piece of feedback and respond individually. They ran a "preview release" rather than a launch, using scarcity and personal follow-up. Within months of the 2014 public launch: ~60,000 daily users and 15,000 paid seats.
Growth strategy. Per-seat pricing with a "fair billing policy" (you only pay for active users), a free tier with a message-history cap that created natural upgrade pressure, and — most importantly — the fact that adopting Slack is a team decision, so each sale lands multiple seats at once and creates internal lock-in through message history and integrations.
Funding history. ~$1.22B raised in total. Peak private valuation ~$17B. Direct listing on the NYSE in June 2019. Acquired by Salesforce in July 2021 for approximately $27.7 billion.
Why this case is misread. The standard telling is "failure taught them to pivot." Look at what actually transferred:
- A team that had built and scaled Flickr together and had worked together for years.
- Existing investor relationships with Accel and a16z, who backed the pivot because they trusted Butterfield specifically.
- Enough capital left over to fund a new product, plus the goodwill generated by offering to return it.
- A founder who had already successfully pivoted a failed game into an acquisition.
None of that is available to a first-time founder whose game fails. The pivot was possible because of accumulated advantage, and the story is usually told as though the pivot itself was the skill.
Current status (September 2026). A product line inside Salesforce, deeply integrated with Agentforce and Salesforce's AI stack. Butterfield left in early 2023. Slack's competitive position against Microsoft Teams — which Microsoft bundled into Office 365, prompting an EU antitrust complaint from Slack in 2020 that Microsoft eventually settled by unbundling — never recovered.
Lessons that generalize.
- Returning capital when you fail is one of the highest-return reputational acts available to a founder. It is also only possible if you still have capital, which means failing early rather than grinding to zero.
- Watch what your team builds for itself. Internal tools are validated by definition — someone chose to build them under time pressure. That is a genuinely transferable heuristic.
Read the wider evidence
This entry is reproduced from the supplied research, with its inline source links retained. It has not been independently re-reported for this website conversion.
Read the complete chapter, source list, and methodological notes →