What should Salesforce do about Slack stagnation?

Direct Answer

Slack is Salesforce's $27.7B writedown-in-motion. Growth collapsed to ~5-7% post-Teams takeover; activist pressure is mounting. Reposition Slack as an agentic-workflow backbone for Agentforce—not another communication app—or divest by 2027.

Four Moves:

1. Rebrand Slack as "Agentforce Surface" — channel-as-API for multi-tenant agent routing, not teams chatting
2. Merge Slack APIs into Service Cloud; unbundle chat from workflow/automation
3. Sell to Oracle, Cisco, or private equity (pre-writedown valuation hit)
4. If bullish: write down to ~$8–12B, strip SKUs, and architect a pure agent-dispatch layer

What's Broken Today

• Acquisition blunder: $27.7B for a commodity communication layer; Microsoft Teams won the enterprise consolidation war
• Growth cliff: 5–7% annual growth vs. Initial 50%+ acquisition thesis; activists calling for impairment
• No native moat: Teams is embedded in Microsoft 365; Slack is a standalone tax
• Agentforce integration incomplete: Slack channels aren't yet first-class agent primitives; wasted upside
• Customer confusion: IT sees Slack as a communication tool, not a revenue-ops surface; no clear product lift from Slack→CRM bridge
• Writedown timing risk: 2026–27 will force $5–8B impairment if growth doesn't reaccelerate

👉 Quick Call with Kory White, Fractional CRO · See Kory on LinkedIn · CRO Syndicate

What Salesforce Should Actually Do

1. Rebrand Slack as Agentforce's "Dispatch Surface" — Agents live in channels; channels are API endpoints for agent-to-agent handoff, not Slack 2.0
2. Unbundle chat from workflow — Ship a lightweight chat layer; sell the core value as "agent orchestration," not messaging
3. Integrate Slack channels into Einstein Copilot state machine — Every channel = a workflow queue; agents read/write to channels as state transitions
4. Sell or merge with Service Cloud — Fold Slack's infrastructure into Service Cloud; eliminate the product line, keep the primitives
5. If you keep it: write down to $10B, cut SKUs 40%, and go agent-first — Slash costs; rebrand as Slack Agentforce OS
6. Evaluate strategic acquirers — Cisco (communication hyperscaler), Oracle (workflow + DB), TPG/Silver Lake (PE tuck-in to a rollup)
7. Run the numbers on a 2027 exit — Model NPV of a 3–5 year agent-workflow repositioning vs. 2026 $6–8B writedown + sale at 0.8–1.0x gross revenue
8. Don't let this drag into 2028 — Every quarter delays the exit/writedown decision, sentiment hardens, and Slack becomes a dead weight on Salesforce's margin profile

FAQ

How much did Salesforce pay for Slack and why is it now a problem? Salesforce paid $27.7B for Slack, but growth collapsed to roughly 5-7% annually after Microsoft Teams won the enterprise consolidation war, far below the 50%-plus acquisition thesis. The article frames Slack as a "writedown-in-motion" because Teams is embedded in Microsoft 365 while Slack remains a standalone tax with no native moat.

Activist pressure is mounting toward a 2026-27 impairment.

What does "Agentforce Surface" mean as a repositioning for Slack? The proposal rebrands Slack as Agentforce's "Dispatch Surface," where channels become API endpoints for agent-to-agent handoff rather than teams chatting. Slack channels would integrate into the Einstein Copilot state machine so each channel acts as a workflow queue that agents read and write as state transitions.

The chat layer gets unbundled, with the core value sold as agent orchestration, not messaging.

Who are the potential buyers if Salesforce decides to sell Slack? The article names Cisco as a communication hyperscaler, Oracle for workflow plus database strength, and private equity firms like TPG or Silver Lake for a PE tuck-in into a rollup. A sale to Oracle or Cisco is modeled at a $12-14B valuation, recovering 45-60% of the original purchase price.

The advice is to exit pre-writedown before activist pressure forces a distressed move.

What happens financially if Salesforce does nothing about Slack? The status-quo path invites a 2027 activist-driven $6-8B impairment plus a potential shareholder lawsuit, with Slack's value falling to $8-12B. Keeping Slack as-is and divesting underperforming SKUs is described as destroying shareholder value with minimal ROI.

The article warns that every quarter of delay hardens sentiment and turns Slack into dead weight on Salesforce's margin profile.

Why is Element listed in the validation vendor stack? Element is an open-source messaging alternative included as the on-premises option if Salesforce wants to decouple Slack's infrastructure from Microsoft. The broader vendor stack also uses Pavilion to benchmark Slack adoption in sales orgs, Bridge Group for Slack ROI case studies, Klue for Teams adoption-curve and feature-parity analysis, and Force Management to test whether Slack works as a coaching surface.

These vendors validate the repositioning decision with real adoption data.

Bottom Line

Slack is a $27.7B anchor. Either commit to making it Agentforce's command-layer by 2027 (requires aggressive integration, 2–3 year runway, and agent adoption) or sell/writedown now before activist pressure forces a distressed move. The "do nothing" path invites a 2027 $6–8B impairment and shareholder litigation.

CFOs are already drawing up contingency plans. Move before they do.

Vendor Stack for Validation

• Pavilion: Sales execution & revenue org benchmarking (Slack adoption % in sales orgs)
• Bridge Group: Sales ops + stack audit (Slack ROI per-org case studies)
• Klue: Competitive intelligence (Teams adoption curve, feature parity analysis)
• Force Management: Sales methodology & coaching (Slack as a coaching surface—does it work?)
• Element: Open-source messaging alternative (if Salesforce buys, runs on-prem Slack alternative; decouples from Microsoft)

Tags

["salesforce", "slack", "agentforce", "m&a", "writedown", "competitive-threat", "teams", "activation", "cfo-lens", "2027-decision"]