Why Should Small Organizations Leave Slack?

TL;DR

Small organizations should reduce dependence on Slack when critical communications, integrations, and institutional knowledge cannot be moved safely on short notice. Hack Club said Slack demanded an additional $50,000 within a week and roughly $200,000 annually, with workspace deactivation and message deletion as the alternative. The nonprofit chose Mattermost, arguing that owning its data would reduce vendor lock-in and future migration risk.

Transcript

Slack is extorting us with a 195k a year bill increase. Oh boy. Spending as much as a big company with tens of thousands of people using the service isn't too big a deal. But spending this much money for something that is small nonprofit is doing like Hatclub in this case is entirely unacceptable. And as such, the response to this has been massive.... Read More

Key Insights

• Hack Club is a nonprofit that has provided coding education and community to teenagers worldwide while using Slack for communications for nearly 11 years. Its long dependence made Slack more than a chat tool because years of organizational knowledge and operational systems accumulated inside the service.
• Slack's proposed price increase was described as an additional $50,000 due that week and approximately $200,000 per year. Hack Club said refusal could lead to workspace deactivation and deletion of its message history, turning a billing dispute into an immediate operational threat.
• The notice period was less than a week and arrived on a Wednesday night, leaving only Thursday and Friday as working days to respond. The commentator argues that a major increase of this kind should include at least a six-month grace period.
• Vendor lock-in becomes dangerous when essential data and customer-facing operations depend on one provider. A vendor can gain substantial leverage if refusing a new price could interrupt communications, remove stored knowledge, stop a website, or otherwise damage the organization's ability to operate.
• Hack Club's Slack dependence extended into login systems, APIs, activity tracking, issue systems, integrations, and program administration. Moving therefore required more than exporting conversations because staff and volunteers also had to rebuild connected workflows and modify programs designed around Slack.
• Mattermost became Hack Club's chosen replacement after the incident demonstrated the importance of owning organizational data. The move reflects a preference for greater control over communications and records, even though the rushed transition imposed delays and significant work across the nonprofit's programs.
• Slack succeeded because it brought channels, threads, inline replies, notifications, tagging, and rapid live conversation into business communication. Its origins in an MMO project helped shape these features, which were initially built for a game and later repurposed as an internal and commercial chat product.
• Enterprise billing can become severe after an organization enters a higher service tier or sales process. The commentator compares Slack's leverage to Cloudflare's potential leverage, emphasizing that inexpensive or free service for ordinary users does not reveal the risks faced by larger or highly dependent customers.

Questions & Answers

Q: Why did Hack Club decide to move away from Slack?

Hack Club decided to leave Slack after the nonprofit said it was asked to pay an additional $50,000 that week and approximately $200,000 per year. According to its account, Slack threatened to deactivate its workspaces and delete message history if it did not agree. The incident demonstrated how dependence on a hosted communication platform could expose critical data and operations to sudden pricing decisions.

Q: How much was Hack Club paying for Slack before the proposed increase?

Hack Club said it had moved from Slack's free nonprofit plan to a $5,000-per-year arrangement several years earlier. The organization considered that amount reasonable because it valued the service provided to its community and paid it willingly. The later demand was dramatically larger, consisting of an additional $50,000 that week and a yearly cost described as approximately $200,000.

Q: How did Slack become essential to Hack Club's operations?

Slack became essential because Hack Club used it for nearly 11 years and connected numerous systems and programs to the workspace. The transcript describes Slack-focused login processes, APIs for tracking activity, issue systems, integrations, communications, and years of institutional knowledge. Consequently, leaving required technical rebuilding and program changes, not merely selecting another application and transferring current conversations.

Q: What are the risks of storing institutional knowledge in Slack?

Storing institutional knowledge in Slack creates risk when the organization cannot independently control continued access to its workspace and history. Hack Club said it faced possible deactivation and message deletion if it rejected the proposed pricing. When years of decisions, conversations, and connected processes reside inside one hosted service, a short-notice billing dispute can become a threat to operational continuity.

Q: Why was Slack's notice period especially disruptive?

The demand reportedly arrived on a Wednesday night and gave Hack Club less than a week to resolve the situation, effectively leaving Thursday and Friday as working days. Staff and volunteers then had to update systems, rebuild integrations, preserve knowledge, and change programs quickly. The commentator considers that timeframe absurd and argues that a six-month grace period should be the minimum for such a large increase.

Q: What work was required for Hack Club to migrate from Slack?

The migration required staff and volunteers to update systems, rebuild integrations, move years of institutional knowledge, and adjust programs built around Slack. The transcript also identifies login, APIs, activity tracking, issue systems, and communications as dependent components. Some programs expected delays, while another planned to shift temporarily toward email-focused login until the organization could establish a more complete replacement.

Q: Why did Hack Club choose Mattermost as its Slack replacement?

Hack Club chose Mattermost after concluding that owning its data was incredibly important. The decision followed a pricing dispute in which the nonprofit believed its workspace and message history could be removed on very short notice. Mattermost is presented as the destination for the migration, with the central motivation being greater control over organizational information and less exposure to a single vendor's demands.

Q: How did Slack become a major business communication platform?

Slack emerged from a failed MMO project whose developers had built a complex internal chat system. They used that system for their own communications, created web and Electron applications, and eventually sold the chat product because it performed better than the game. Its channels, threads, replies, notifications, tagging, and emphasis on rapid conversation addressed business communication needs that email and meetings handled less immediately.

Summary & Key Takeaways

• Hack Club, a nonprofit providing coding education and community to teenagers, used Slack for nearly 11 years and paid $5,000 annually after leaving a free nonprofit plan. It said Slack then demanded an additional $50,000 that week and approximately $200,000 per year, threatening workspace deactivation and deletion of message history.

• The threatened cutoff forced staff and volunteers to migrate years of institutional knowledge, rebuild integrations, update systems, and change Slack-dependent programs. The disruption extended beyond chat because authentication, APIs, activity tracking, issue management, and other operational processes had become connected to the workspace, creating a staggering opportunity cost for the nonprofit.

• Hack Club decided to move to Mattermost after concluding that owning its data was essential. The broader lesson is that a convenient communication service can become dangerous when it controls indispensable records and workflows. Small organizations should assess portability, integration dependence, migration time, and contingency plans before a vendor dispute makes departure urgent.