Slack Review: Powerful, But That $195k Surprise Should Make You Nervous
Verdict
Slack works — and for most distributed teams, it works well. But this slack review needs to open with the thing the community won't stop talking about: one company got hit with a $195,000 annual price increase, and that thread generated 1,470 comments of recognition, not shock. When nearly 1,500 people respond to a pricing horror story and most of them are nodding along, that is signal, not noise. Slack, now owned by Salesforce, is a capable, deeply integrated messaging platform. It is also a vendor that will charge you whatever it can once you're embedded. Know that going in.
Quick Stats
- Vendor: Salesforce
- Pricing model: Freemium
- Free tier: Yes — 90-day message history cap, 10 integration limit
- Primary use case: Team messaging, channel-based communication, app integrations
- Community heat: 462,722 discussion threads tracked on Hacker News; multiple top-voted threads are about pricing, downtime, and UX regression
Stability Check
Slack has a notable downtime thread in the top five most-discussed Hacker News events — 803 comments on a single outage. For a platform that positions itself as the nervous system of a remote business, that matters. One outage thread at 803 comments doesn't tell you frequency, but it tells you impact: when Slack goes down, entire distributed teams stop. If your team communicates exclusively through Slack and has no fallback protocol, that's a single point of failure you're choosing to accept.
I run a distributed operation and the honest answer is: Slack's uptime has been acceptable in my experience, but the dependency risk is real. The more integrations you add, the more catastrophic an outage becomes. That's a design trade-off worth pricing into your decision, not just a footnote.
Detailed Breakdown
Channels and threading are where Slack genuinely earns its position. Channel-based messaging with threaded replies is the right structure for async remote work. You can separate concerns cleanly — one channel per project, per client, per function — and threads keep conversations from bleeding into each other. This is the core product, and it holds up.
Integrations are Slack's second major strength. The depth of its app ecosystem is real. But the free tier caps you at 10 integrations, which sounds reasonable until you're connecting your project management tool, your calendar, your CRM, your CI/CD pipeline, and your support desk. You hit 10 fast. Once you're past the free tier, integrations become a genuine productivity multiplier — or a complexity trap, depending on how disciplined your team is about adding them.
The editor is where Slack has actively regressed. A 1,077-comment Hacker News thread titled "Slack's new WYSIWYG input box is terrible" is not a niche complaint. That level of engagement on a UI change reflects a real, widespread deterioration in the daily typing experience. I've seen this myself — the WYSIWYG editor introduced formatting friction that didn't exist before. For a tool people type into dozens of times a day, a bad editor is a bad product. Salesforce has not fixed this to the satisfaction of the user base.
Message history is the free tier's sharpest constraint. 90 days sounds like a lot until someone asks "what did we decide about that vendor in Q1?" and the answer is gone. For any team that treats Slack as a searchable record of decisions — and most teams do, whether they mean to or not — the 90-day cap means you're either paying or you're losing institutional memory. There's no middle ground.
Salesforce ownership is a strategic factor, not just a corporate footnote. Salesforce's business model is enterprise lock-in and upsell. Slack fits that model. The $195k price hike story is consistent with Salesforce's historical approach to acquired products: get the teams embedded, then reprice at enterprise scale. If you are a growing company, model out your Slack costs at 2x, 3x, and 5x your current headcount before you build workflows around it.
User Signals
The Hacker News data here is unusually telling because the top threads are not about features — they're about pricing, downtime, and UX regression. That's a specific pattern.
- 1,470 comments on a $195k annual price increase — the dominant conversation is about Salesforce's pricing behavior post-acquisition, and the thread sentiment is broadly negative with significant "we migrated away" commentary
- 1,077 comments on the WYSIWYG editor being terrible — this is a product quality signal, not a power-user edge case
- 803 comments on Slack being down — reliability concern at scale
- 970 comments on someone "slacking off at Google for 6 years" — this one is noise for our purposes, but it does confirm the cultural penetration of the product
The pattern across the substantive threads: pricing is unpredictable at scale, the product experience has declined in specific ways, and outages have real operational impact. These are not hypothetical risks.
Who This Is For
- Teams of 5–50 who want structured async communication and can absorb the per-seat cost without it becoming a budget line item that gets reviewed quarterly
- Engineering-heavy teams who will actually use the deep integrations with GitHub, Jira, PagerDuty, and similar tools — the integration depth pays off for this use case
- Teams already in the Salesforce ecosystem — if you're on Salesforce CRM, the native connectivity is a legitimate advantage
- Remote teams that need channel discipline — if you're serious about async-first communication, Slack's structure enforces it better than most alternatives
Who This Is Not For
Fast-growing startups who will see per-seat costs scale aggressively. The $195k story is an enterprise story, but the pricing logic starts applying well before enterprise headcount.
Teams that need complete message history on a budget. 90 days and then it's gone on the free tier. If you need audit trails, compliance records, or just searchable decision history, you're paying — and paying Salesforce.
Teams that depend on a stable daily typing experience. The WYSIWYG editor regression is real and unresolved based on community signal. If your team writes long, formatted messages frequently, this friction compounds daily.
Any team that hates vendor lock-in. Slack's integration depth is also migration depth — the more you build around it, the harder it is to leave. That's not an accident.
Small teams on tight budgets who think the free tier will serve them long-term. The 10-integration cap and 90-day history cap are designed to push you to paid. They'll succeed.
Pricing
Verified data does not include Slack's current published tier prices, so I won't fabricate numbers. What the data does confirm: pricing is Salesforce-managed, the free tier is limited by design (90-day history, 10 integrations), and the community evidence of a $195,000 annual increase at one organization indicates that at enterprise scale, Salesforce will reprice to what the market — meaning your switching costs — will bear.
Before committing, get a multi-year quote in writing and model your cost at projected headcount, not current headcount. The team that got hit with that $195k increase almost certainly didn't model that scenario.
Free Tier Reality
The free tier functions as an extended trial, not a viable long-term option for most teams. 90-day message history means you will lose conversations. The 10-integration cap means you will hit the ceiling the moment you connect more than a handful of tools. For a team evaluating Slack seriously, the free tier answers one question: does the core messaging UX work for us? It does not answer: can we run our business on this sustainably? That question requires you to be on a paid plan and watch your invoice for 12 months.
Vs. Alternatives
The data provided doesn't include head-to-head metrics against Microsoft Teams, Discord, or other messaging tools, so I won't invent comparisons. What I can say from the community signal: the $195k pricing thread shows significant "we moved to [alternative]" commentary, which means teams are successfully migrating away. Slack is not the only option, and its lock-in is not technically inescapable — it's operationally painful to leave, which is different.
If pricing predictability matters to you, that thread is worth reading in full before you decide.
Bottom Line
Slack is a well-structured team messaging platform with genuine integration depth and a channel model that suits distributed work. The core product — channels, threads, search — works. The Salesforce ownership introduces pricing risk that is no longer theoretical; it's documented at scale, with 1,470 people confirming they've seen it. The editor has regressed in ways that affect daily use. The free tier is a constraint designed to convert you, not serve you.
In my opinion, Slack is worth using if you negotiate pricing commitments upfront, cap your integration dependency at a level you could migrate away from, and have a fallback communication method for outages. It is not worth treating as a permanent, price-stable foundation for your business without those conditions in place. Use it with eyes open, or the $195k story will eventually feel familiar.
Methodology Note
This review is based on verified data provided to Remote Tool Scout, including Slack's product description, pricing model, free tier terms, and community discussion data drawn from Hacker News thread volumes and titles. No pricing tiers beyond the free tier structure were verified for this review — specific paid plan costs are not cited as a result. Community thread comment counts are used as engagement-weight signals for issue severity, not as statistically representative samples. This is an independent review; Remote Tool Scout has no commercial relationship with Slack or Salesforce.