Stewart Butterfield: The Philosophy Major Who Failed at Two Video Games and Accidentally Invented Slack

In late 2012, a 39-year-old Canadian entrepreneur named Stewart Butterfield sat in a dimly-lit San Francisco conference room and told his team that the online game they had spent four years building was being cancelled. The game was called Glitch. It was ambitious, strange, collaborative, and beautiful. It was also commercially dead. Players loved it. Investors didn’t. Growth was too slow. The money was almost gone.

Butterfield’s team was devastated. Engineers cried. Artists stared at the wall. Some of them had relocated their families across continents to work on Glitch. Butterfield absorbed the blame publicly, apologized to employees in a long all-hands meeting, and promised that everyone would receive extended severance and help finding new jobs.

Then he asked his co-founders a quiet question. During the four years of building Glitch, the team had built an internal chat tool to coordinate their distributed engineering work. The tool had almost nothing to do with the game. It was a simple web app for sending messages, organizing channels, and sharing files between team members spread across three cities. Everyone on the team used it constantly. Everyone loved it. Several employees had mentioned that they would pay for a version of it at their next job.

Butterfield looked at the tool. He looked at the cancelled game. And he said, more or less, the same sentence he had said once before, nearly a decade earlier, when a different failed game had produced a different successful side tool: “I think this could be something.”

The side tool became Slack. Eight years later, Salesforce would buy Slack for $27.7 billion — the largest software acquisition in history at the time. Stewart Butterfield, the philosophy-major-turned-video-game-designer-turned-enterprise-software-founder, would pull off one of the most improbable double pivots in the history of technology.

---

🏕️ Chapter 1: Born in a Commune

Stewart Butterfield was born Dharma Jeremy Butterfield on March 21, 1973, in a log cabin on a hippie commune in Lund, British Columbia, on the west coast of Canada. His parents — who had moved to Canada from the United States to avoid the Vietnam War draft — lived off-grid without electricity or running water for the first five years of his life.

The commune was exactly what it sounds like. Families shared food, built houses by hand, and raised their children collectively. Young Dharma spent his early years learning to name edible plants, collect firewood, and listen to adults discuss Eastern philosophy around campfires. He was raised to believe that his first name was a gift from a spiritual teacher and would one day mean something important.

At age twelve, he decided he wanted a more conventional name. He asked his parents if he could change it. They agreed. He became Stewart. Years later, he would joke that changing his name was the first strategic decision of his life — and a preview of his willingness to abandon things that weren’t working.

After the family left the commune, Stewart attended public schools and showed a precocious aptitude for academics. He loved reading, loved language, and loved arguing about abstract ideas. When it came time for college, he enrolled at the University of Victoria and majored in philosophy. Then, improbably, he was accepted into the highly competitive master’s program in philosophy at the University of Cambridge, where he studied the philosophy of mind — a branch of philosophy obsessed with questions about consciousness, perception, and the nature of experience.

---

🎮 Chapter 2: The First Game

After Cambridge, Butterfield drifted into the internet world. He built websites. He ran a small consulting business. He met a Canadian interaction designer named Caterina Fake, whom he would eventually marry. And in 2002, he and Caterina co-founded a company called Ludicorp with the goal of building a massively multiplayer online game.

The game was called Game Neverending. It was strange, social, and stubbornly non-combat. Players could collect items, build worlds, and chat with each other in real time. It was supposed to be revolutionary. It was also too expensive to build, too slow to grow, and impossible to fund.

By 2004, Ludicorp was nearly bankrupt. But during the development of Game Neverending, the team had built a side tool to let players upload and share photos inside the game. The tool was clean, fast, and unusually well-designed. Caterina started showing it to friends as a standalone product. Friends loved it. The tool was called Flickr.

Butterfield made the decision that would define his career. He killed Game Neverending. He focused the entire team on Flickr. He rebuilt the company around photo sharing. Within a year, Flickr was one of the most popular photo-sharing sites on the internet.

In March 2005, Yahoo acquired Flickr for a reported $25 million — modest by today’s standards but enormous for a small Canadian startup at the time. Butterfield and Fake joined Yahoo. Butterfield stayed for roughly three years and then left in a characteristically dramatic fashion, submitting a resignation letter written entirely in character as an early-20th-century tin magnate named “Farley B. Quilliam-Smythe.” The letter went viral on early tech blogs and became a small legend inside Yahoo.

---

🎲 Chapter 3: Trying the Game Again

Butterfield’s post-Flickr life looked, to outsiders, like the classic successful-exit founder life. He had money. He had fame inside a small circle. He could have done anything. What he chose to do was insane: he tried to build another online game — and this time he would do it right.

In 2009, he co-founded Tiny Speck, a new game studio in Vancouver and later San Francisco. The flagship project was Glitch — a sprawling, whimsical, non-violent online game inspired by early massively multiplayer titles and his own fascination with collaborative play. It was beautifully designed. It had an art style inspired by children’s storybooks. It had no combat, no death, and no leveling system in the traditional sense.

Investors funded it generously. Accel Partners and Andreessen Horowitz led multi-million-dollar rounds. Butterfield hired top designers and engineers. Glitch launched in public beta in September 2011.

It was not a hit. Player acquisition was slow. Monetization was unclear. Retention was mediocre. Butterfield tried to iterate — he pulled the game from public release, redesigned it, and relaunched it in 2012. The relaunch didn’t fix the underlying problem. By late 2012, Tiny Speck was running out of money.

Butterfield called a meeting and killed the game.

---

💬 Chapter 4: The Chat Tool Nobody Asked For

What Butterfield did next was the move that would make him famous. Instead of shutting down Tiny Speck, he told his remaining investors that the team had built something useful during the Glitch years — a chat tool that coordinated their distributed work. He believed it could be turned into a standalone product. He wanted to try.

The investors were understandably skeptical. They had funded a game studio. Now the founder wanted to pivot to enterprise software — a completely different market with completely different customers. Butterfield argued his case carefully. He pointed out that every startup in the world needed better internal communication. He pointed out that email was terrible and that existing enterprise chat tools like HipChat were ugly, slow, and unloved. He argued that the chat tool his team had built was genuinely delightful to use and could be productized quickly.

The investors agreed. Butterfield kept roughly half of the Glitch team, focused them on the chat tool, and began working on a new product name. They landed on Slack, an acronym — supposedly — for “Searchable Log of All Conversation and Knowledge,” though Butterfield later admitted he had chosen the name partly because it sounded casual and friendly.

Slack launched in a tiny public beta in August 2013 with 8,000 daily active users across about a thousand teams.

---

🚀 Chapter 5: The Fastest-Growing Enterprise Software Ever

Slack’s growth was unprecedented. Within six months, daily active users crossed 100,000. Within a year, they crossed 500,000. Within two years, Slack had over a million daily active users and was being called “the fastest-growing enterprise software company in history” by multiple industry analysts.

The product was almost offensively simple. It was a chat app. It had channels. It had direct messages. It had file sharing. It integrated with other tools. There was nothing in Slack, technically, that didn’t already exist in HipChat or IRC or older enterprise messaging systems. What was different was the experience. Slack felt fast, friendly, responsive, and designed. Users fell in love with it in the way they fell in love with consumer apps — not the way they tolerated business software.

Butterfield and his team had done something unusual in the enterprise software world. They had optimized for delight. They had assumed, correctly, that if they made a tool that employees voluntarily wanted to use, the tool would spread inside organizations without traditional top-down sales.

Slack raised funding at increasingly aggressive valuations. In 2014, it was worth $1.12 billion. In 2015, it was worth $2.8 billion. In 2016, it was worth $3.8 billion. In 2017, it was worth $5.1 billion. Investors could not throw money at the company fast enough.

---

📝 Chapter 6: “We Don’t Sell Saddles Here”

In late 2013, before Slack had even officially launched, Butterfield wrote an internal memo to his team titled “We Don’t Sell Saddles Here.” The memo was later published publicly and became one of the most influential founder documents in the history of SaaS.

The title was a metaphor. Butterfield argued that Slack’s competitors thought they were selling “saddles” — software features like chat, search, and file sharing. Slack was not selling saddles. Slack was selling the experience of riding. It was selling what happened after the software was installed — the transformation of how a team worked together.

The memo was beautifully written, philosophically dense, and strategically precise. It argued that Slack’s entire marketing, design, and product development needed to be oriented around a single question: what does it feel like for a team to actually use this software? If the answer was “delightful and liberating,” Slack would win. If the answer was “functional but tiresome,” Slack would lose.

The memo shaped every decision the company made. It shaped hiring. It shaped feature prioritization. It shaped the marketing copy that Slack used for years. And it eventually escaped into the broader SaaS industry and became required reading for a generation of founders who wanted to build products people genuinely loved.

---

📈 Chapter 7: The Direct Listing

On June 20, 2019, Slack went public on the New York Stock Exchange through a direct listing — one of only a handful of companies to use this unusual IPO mechanism. Spotify had pioneered the approach the year before. Slack followed.

The direct listing meant no new shares were issued and no investment bankers were paid underwriting fees. Existing shareholders simply began trading their stock on the open market. The first trade was at $38.50. By the end of the first day, Slack was worth roughly $19.5 billion.

The IPO made Butterfield a billionaire on paper several times over. It also marked the formal arrival of Slack as a major public technology company. He rang the bell on the floor of the New York Stock Exchange and gave a short, characteristically self-deprecating speech. He thanked his team. He thanked his investors. He did not take a victory lap.

Behind the public celebration, however, was a growing private worry. Microsoft had launched Teams in 2017 as a Slack competitor bundled for free inside Office 365. By 2019, Teams was growing faster than Slack by most metrics — because Microsoft could ship the product to millions of enterprise customers as part of existing subscriptions, bypassing the traditional sales cycle entirely. Slack was winning the product battle. It was losing the distribution war.

---

⚔️ Chapter 8: The Microsoft Teams Attack

Butterfield fought Microsoft publicly. Slack famously bought a full-page ad in The New York Times the day Microsoft Teams launched, congratulating Microsoft sarcastically on entering the enterprise chat market. The ad was clever, funny, and a little defensive. It was also, in retrospect, a preview of how stressful the next four years would be.

Microsoft’s bundling advantage was nearly impossible to overcome. Enterprise IT buyers who were already paying for Microsoft Office 365 could turn on Teams for free. They didn’t have to evaluate Slack. They didn’t have to talk to Slack’s sales team. They could simply use what they already had.

By 2020, Teams had more daily active users than Slack. By 2021, Teams had vastly more. Slack’s growth rate slowed. Its stock price, which had peaked after the pandemic-driven remote work boom, began to stagnate. Butterfield and his leadership team started having conversations they had not wanted to have: about whether Slack could survive as an independent company against a competitor with Microsoft’s unfair distribution advantage.

The answer, increasingly, was maybe not. Slack needed scale, distribution, and enterprise trust that it could not build fast enough on its own. Something had to give.

---

💼 Chapter 9: The Salesforce Deal

On December 1, 2020, Salesforce announced it was acquiring Slack for $27.7 billion in cash and stock. At the time, it was the largest software acquisition in history. Butterfield would become an executive vice president at Salesforce and run Slack as a division of the larger company.

The deal was controversial. Some Slack employees felt the company was selling out too early. Some investors wondered whether Salesforce was overpaying for a stagnating asset. Some competitors, notably Microsoft, insisted that the acquisition was proof that Slack had already lost the chat war.

In hindsight, the timing was remarkable. Butterfield sold at nearly the absolute peak of the pandemic SaaS valuation bubble. Within 18 months, nearly every SaaS company on the market would lose 50% to 80% of its peak valuation as the post-pandemic correction gutted growth-at-all-costs business models. If Butterfield had waited, Slack might have been forced to sell for half as much. Or less.

Salesforce’s CEO Marc Benioff framed the deal as the foundation for the next generation of enterprise software — an all-in-one platform for CRM, sales, service, and internal collaboration. Butterfield publicly embraced the vision. Privately, he began preparing for a different kind of transition.

---

🚪 Chapter 10: Leaving Slack

In December 2022, almost exactly two years after the Salesforce acquisition, Butterfield announced he was leaving Slack — and leaving Salesforce. He did not announce a new company. He did not announce a book deal. He did not reinvent himself as a venture capitalist.

He simply said he was tired, that his lock-up obligations were ending, and that he wanted to spend time with his family. He praised the Slack team, thanked Salesforce, and disappeared from the public technology conversation almost entirely.

The departure was classic Butterfield. No drama. No Twitter manifesto. No carefully stage-managed media tour. He had sold the company, completed the integration period in good faith, and then stepped off the stage.

In the months and years that followed, Butterfield would pop up occasionally — an angel investment here, a small podcast appearance there, a quiet advisory role at a small startup. But he made no move to reinvent himself as a public figure. For a founder of his stature, this was remarkable.

---

🧠 Chapter 11: The Philosophy of Work

Stewart Butterfield’s deepest intellectual contribution to the technology industry is not Slack itself. It is his philosophical framing of what software is supposed to do. He has consistently argued that the real purpose of enterprise software is not to add features or automate tasks — it is to change the subjective experience of work.

This framing, borrowed from his philosophy-of-mind background, is unusual in Silicon Valley. Most tech founders think about software in utilitarian terms: does it save time, make money, reduce errors? Butterfield thinks about software in phenomenological terms: does it make the human on the other side of the screen feel calmer, clearer, more connected, more competent?

Slack’s most successful features were designed around this principle. The little custom emoji reactions. The light, playful tone of notification sounds. The subtle loading animations. The carefully chosen typography. None of these things had obvious business justifications. All of them contributed to the experience of using the product — which, Butterfield believed, was the only thing that actually mattered.

This philosophical approach influenced a generation of product designers who came up through Slack or watched it from the outside. It is one of the most under-acknowledged intellectual legacies of the 2010s SaaS era.

---

🌅 Chapter 12: The Ledger

Stewart Butterfield’s career ledger is one of the strangest in technology history. He failed at a video game. He turned the side tool into Flickr and sold it to Yahoo. He failed at another video game. He turned the next side tool into Slack and sold it to Salesforce for $27.7 billion. He was twice rescued by the same strategic insight: the side project is more valuable than the main project.

His personal net worth is estimated at around $1.8 billion. He lives quietly in Vancouver and California with his wife Jen Rubio, the co-founder of the luggage company Away, and their children. He remains on the board of a handful of small companies. He does not tweet often. He does not go on podcast tours. He does not publish AI manifestos.

Slack continues to exist as a division of Salesforce. It continues to serve millions of users. Microsoft Teams continues to dominate by volume. Google Workspace continues to exist. The chat wars of the 2020s are ongoing, and Slack’s long-term position inside Salesforce is still being negotiated.

But the cultural legacy of Slack is harder to dislodge. An entire generation of knowledge workers learned to communicate through channels, emojis, and threads because Stewart Butterfield decided, twice, to ignore the game his investors had funded and build the tool his team actually wanted.

Some founders build empires. Butterfield built two delightful products inside the wreckage of two failed games. That is arguably a rarer, and more instructive, kind of success.