It's time to move off Slack...

TL;DR

Hack Club alleges Slack demanded $50,000 immediately and $200,000 per year, threatening to deactivate its workspace and delete 11 years of message history within days.

Briefing Cornell Notes

Briefing

Slack’s nonprofit pricing dispute with Hack Club has ignited a backlash over enterprise billing tactics: a small organization says Slack demanded an immediate $50,000 payment and $200,000 per year or it would deactivate its workspace and delete 11 years of message history. The central grievance isn’t just the size of the increase, but the leverage Slack holds because chat history is operationally and institutionally critical—making “pay or lose data” feel less like a contract renegotiation and more like coercion.

Hack Club, a nonprofit serving teens worldwide through coding education and community, says it had a special $5,000-a-year arrangement after Slack moved it off a free nonprofit plan. The organization claims it was charged for staff and volunteers rather than every teen in its community, and that it built programs around that rate. Then, according to Hack Club, Slack changed the terms to charge every user without a new contract, delayed outreach, and set a short deadline—reportedly only days—to resolve a bill that escalated dramatically. The threat to deactivate the workspace and erase message history within roughly a week is framed as catastrophic: staff and volunteers would have to rebuild integrations, migrate years of institutional knowledge, and absorb major opportunity costs.

The dispute also sparked a broader argument about how enterprise chat platforms monetize entrenchment. Slack’s “shared channels” and Slack Connect make cross-company collaboration easy, which in practice can force organizations to keep paying even if they want to switch tools. The transcript contrasts Slack’s pricing model—$18 per user per month for a standard business plan, with higher costs tied to tiers and message-history limits—with Microsoft Teams, which is positioned as cheaper when bundled with Microsoft 365. Examples cited include hard caps on message history and Slack Connect restrictions on free tiers, all of which can turn collaboration into an ongoing cost rather than a utility.

Beyond pricing, the transcript traces Slack’s origins to a gaming studio that built an overengineered internal chat system for an MMO, then spun it into a product that became dominant in business communications. That history matters in the narrative because it explains why Slack’s feature set—channels, threads, tagging, and real-time messaging—won adoption quickly and became hard to replace.

Resolution came after public pressure. Hack Club says Slack restored nonprofit pricing after the issue surfaced, and Slack’s CEO issued an apology while attributing the problem to a billing oversight. Critics in the transcript remain skeptical, pointing to the reported aggressive demands and the short timeline as evidence that the public apology doesn’t address the underlying incentives. The fallout includes donations and a push for organizations to “own their data,” with Hack Club planning migration away from Slack toward alternatives like Mattermost and interim steps such as an email-focused login while systems are rebuilt.

Overall, the dispute is presented as a warning about dependency: when a communication platform becomes the backbone of operations, billing changes can become existential—especially for nonprofits and smaller organizations that lack the leverage to absorb sudden migrations or data loss.

Cornell Notes

Hack Club says Slack escalated its nonprofit billing from a special $5,000-a-year arrangement to a demand for $50,000 immediately and $200,000 per year, threatening to deactivate its workspace and delete 11 years of message history within days. The transcript frames this as leverage-based “extortion,” because chat history and integrations are operationally tied to the organization’s work. It also argues that Slack’s entrenchment—especially Slack Connect and shared channels—makes switching difficult even for teams that dislike the pricing. After public exposure, Slack restored nonprofit pricing, but skepticism remains about whether the incentives and tactics that led to the threat have truly changed. The episode is used to push smaller orgs toward tools that better support data ownership and migration readiness.

Why does the threat to delete message history matter more than the dollar amount?

Because the transcript treats chat history as institutional memory and operational infrastructure. Hack Club describes years of work—staff and volunteer coordination, integrations, and accumulated knowledge—being tied to Slack. If Slack deactivates the workspace and removes message history, the organization must rebuild systems and migrate knowledge under severe time pressure, turning a billing dispute into a business-continuity crisis.

What billing mechanism does Hack Club claim changed, and how did that trigger the escalation?

Hack Club says it previously paid a special rate that charged for staff and volunteers rather than every teen in its community. It claims Slack later changed terms to charge every single user without telling it or sending a new contract, then ignored outreach and delayed responses while setting a deadline. That shift is portrayed as the start of a “death spiral” of upselling and higher charges.

How does Slack’s collaboration model make switching away harder in practice?

The transcript emphasizes Slack Connect and shared channels as a key lock-in. When multiple companies collaborate through shared channels, organizations may still need to keep Slack to participate in those cross-company spaces. It argues that bots can’t fully replace this because Slack Connect expects a human user experience and misuse could lead to being banned.

What pricing comparisons are used to argue Slack is out of line?

The transcript cites Slack’s per-user pricing (e.g., $18 per user per month for a standard business plan, and $9 per month if certain features like SSO/management are not used). It also contrasts this with Microsoft Teams pricing (e.g., $4 per user per month, or $6 when bundled with Microsoft 365 Business). It further points to message-history caps and Slack Connect limitations on free tiers as additional cost drivers.

How does the transcript connect Slack’s dominance to its origins?

It traces Slack to a gaming studio that built a complex internal chat system for an MMO, then repackaged it as a product. The argument is that gaming-driven needs for immediate communication shaped Slack’s feature set—channels, threads, tagging, and real-time back-and-forth—helping it win adoption and become entrenched in business workflows.

What does the transcript say happened after the public backlash?

Hack Club says Slack restored nonprofit pricing after the dispute became public. Slack’s CEO issued an apology and attributed the issue to a billing oversight, while Hack Club and commenters remain skeptical because the reported threat and short timeline are seen as inconsistent with a simple “oversight” explanation. The transcript also notes Hack Club’s plan to migrate toward Mattermost and use interim systems while rebuilding.

Review Questions

What specific leverage does Slack have in this dispute, and how does that leverage change the power balance between a nonprofit and a vendor?
Which Slack features are described as creating the strongest switching friction for organizations collaborating with other companies?
How do message-history limits and Slack Connect restrictions function as ongoing cost pressures in the transcript’s pricing critique?

Key Points

1
Hack Club alleges Slack demanded $50,000 immediately and $200,000 per year, threatening to deactivate its workspace and delete 11 years of message history within days.
2
The dispute centers on dependency: chat history, integrations, and coordination workflows make sudden deactivation operationally catastrophic for nonprofits.
3
Slack’s shared channels and Slack Connect are portrayed as a lock-in mechanism that can force organizations to keep paying even if they want to switch tools.
4
The transcript argues Slack’s per-user pricing and tiered limits (including message-history caps and Connect constraints) can turn collaboration into a recurring “ransom” cost.
5
Hack Club says its special nonprofit rate changed from charging staff/volunteers to charging every user, allegedly without a new contract.
6
Public exposure led to Slack restoring nonprofit pricing, but critics remain unconvinced that the underlying billing and communications incentives changed.
7
The episode is used to advocate for data ownership and migration planning, with Hack Club moving toward Mattermost and interim communication steps.

Highlights

The most alarming claim is the “pay or lose data” threat: deactivation and deletion of 11 years of Slack message history within days.

Slack Connect and shared channels are framed as the practical reason switching tools can be difficult even when teams dislike the pricing.

The transcript ties Slack’s business dominance to gaming-era communication design—channels, threads, tagging, and real-time back-and-forth.

After backlash, nonprofit pricing was reportedly restored, but skepticism persists because the reported demands and timeline look like more than a simple billing mistake.

Topics

Slack Billing
Nonprofit Pricing
Data Lock-In
Slack Connect
Migration to Mattermost

Mentioned

Christina Hackclub
Denise Dresser