A post titled “Slack has raised our charges by $195k per year” exploded across Hacker News this week, hitting over 3,400 points and generating nearly 1,500 comments. The numbers are staggering, but the real story isn’t about one company’s pricing decision — it’s about a structural problem in how we’ve built our technology stacks.
The Pricing Shock#
The details from the original post paint a grim picture. An organization that had been paying a certain rate for Slack Enterprise suddenly received a renewal quote with a $195,000 annual increase. Not a gradual ramp. Not a modest inflationary adjustment. A sudden, substantial jump that forces a binary choice: absorb the cost or migrate away.
This pattern should feel familiar. Salesforce does it. Oracle does it. AWS does it (more subtly, through the complexity of their pricing models). Once your organization is deeply embedded in a platform — your workflows, integrations, institutional knowledge, and data all living there — the switching costs become enormous. And that’s when the price increases come.
Slack specifically has been on this trajectory since the Salesforce acquisition. The integration with Salesforce’s broader enterprise sales machine has shifted Slack from a bottoms-up developer tool to a top-down enterprise platform with enterprise pricing to match. The product may not have changed much, but the go-to-market motion certainly has.
The Hidden Cost of Platform Dependency#
Here’s what the $195K number actually represents: the price of dependency. Every Slack bot you’ve built, every workflow automation, every integration with your ticketing system, monitoring tools, and deployment pipelines — all of that represents switching costs. Salesforce (and every other enterprise SaaS vendor) knows exactly how embedded they are in your operations, and they price accordingly.
I’ve seen this movie before, multiple times across my career. In the early 2000s, it was Oracle database licensing. In the 2010s, it was VMware. Now it’s SaaS platforms. The pattern is always the same:
- Offer a compelling product at a reasonable price
- Achieve deep organizational penetration
- Get acquired by (or become) a company focused on maximizing revenue per customer
- Raise prices because switching costs make it rational for customers to pay
The frustration in the Hacker News comments was palpable. Engineers who had championed Slack within their organizations now feel betrayed. But the reality is that this outcome was predictable the moment Slack became critical infrastructure without any contractual price protection.
What Engineering Leaders Should Do#
If this story has you nervously looking at your own SaaS bills, here’s a practical framework:
Audit Your SaaS Stack#
Most organizations have no idea how much they’re actually spending on SaaS. Shadow IT purchases, seat-based licenses for people who barely use the tool, overlapping functionality between platforms — it adds up quickly. Before you can optimize, you need visibility.
Run a comprehensive audit. List every SaaS product, its cost, its contract renewal date, and critically, how deeply integrated it is with your workflows. That integration depth is your switching cost, and it’s your leverage (or lack thereof) in negotiations.
Build Abstraction Layers#
For critical communication infrastructure, consider building abstraction layers in your integrations. Instead of having your deployment pipeline post directly to Slack’s API, have it post to an internal messaging abstraction that can route to Slack, Teams, Mattermost, or whatever comes next.
Yes, this is more work upfront. Yes, most teams won’t do it until they feel the pain. But the teams that have abstraction layers in place can credibly threaten to switch platforms during contract negotiations, and that threat is worth real money.
Evaluate Open Source Alternatives#
The Mattermost and Rocket.Chat communities are probably having a very good week. Self-hosted communication platforms have matured significantly, and for organizations with the engineering capacity to run them, they offer both cost predictability and data sovereignty.
The trade-off is operational overhead. Running a communication platform at scale isn’t trivial — you need to handle availability, security updates, mobile apps, and user support. But for organizations spending six figures or more on Slack, the math might work.
Negotiate Aggressively#
If you’re staying with Slack, use this moment as leverage. Salesforce’s sales team knows that this pricing controversy has organizations evaluating alternatives. Multi-year commitments with price caps, volume discounts, and contractual protections against sudden increases should all be on the table.
The Bigger Picture: SaaS Inflation#
What we’re witnessing across the industry is a SaaS inflation crisis. The total cost of a modern technology stack — cloud infrastructure, communication, project management, CI/CD, monitoring, security tools — has been growing faster than most organizations’ revenue. Something has to give.
I think we’re heading toward a correction. Not a crash, but a rationalization. Organizations that treated SaaS spending as an afterthought are being forced to make hard choices. The “just put it on the company card” era of SaaS procurement is ending.
The smart move for engineering leaders is to get ahead of this. Don’t wait for your CFO to come asking why the technology budget is growing 30% year over year while revenue grows 10%. Build cost awareness into your engineering culture now. Evaluate open source alternatives not as a cost-cutting exercise but as a strategic hedge against vendor pricing power.
My Take#
I have a lot of sympathy for the teams caught in this situation, but I have limited sympathy for the organizations that let it happen. We’ve known for decades that vendor lock-in leads to pricing power abuse. The SaaS model made it feel different because the switching costs were less visible — they’re in integrations and workflows rather than data format lock-in — but the dynamics are identical.
My rule of thumb: any tool that touches more than 50% of your engineering team’s daily workflow should be treated as critical infrastructure, with all the risk management that implies. That means contractual protections, switching cost analysis, and viable alternatives identified before you need them.
A $195K price increase is painful. But the lesson is worth learning: in the cloud era, the rent can always go up.
This post is part of the Infrastructure Notes series, where I cover the tools, platforms, and practices that keep our systems running — or don’t.