What should Salesforce do about Slack stagnation?

Question

Pulse RevOps · The Machine · Accepted Answer

## 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 ## 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 | Path | 2025 Valuation | 2027 Valuation | Execution Cost | Expected ROI | |------|---|---|---|---| | **Reposition + Agentforce integration** | $15–18B | $20–25B (if agents take off) | $2.5B R&D | 35–50% upside | | **Sell to Oracle/Cisco** | $12–14B | N/A (divested) | $500M transaction | 45–60% of original | | **Write down + merge into Service Cloud** | $10–12B | $12–15B (faster runway) | $1.8B integration | 20–35% | | **Keep as-is + divest under-performing SKUs** | $8–10B | $8–12B (flat to slight growth) | $600M cost-cuts | Minimal; destroys shareholder value | | **Private equity tuck-in (PE buyout)** | $9–11B | N/A (PE owned) | $300M earnout risk | 30–40% for Salesforce exit | ```mermaid graph LR A["Slack
5-7% growth
Teams dominance"] --> B{"2026 Decision"} B -->|"Agent-first pivot"| C["Reposition:
Agentforce surface
Channel-as-API"] B -->|"Exit (Oracle/Cisco)"| D["Sell 2026-27
12-14B valuation
Avoid writedown"] B -->|"Merge + integrate"| E["Fold into
Service Cloud
10-12B write-down"] B -->|"Status quo
risky"| F["2027 activist pressure
6-8B impairment
shareholder lawsuit"] C --> G["2027: 20-25B
if Agentforce
scales"] D --> H["2027: Divested,
cash returned"] E --> I["2027: Integrated
margin recovery
12-15B book"] F --> J["2027: Writedown,
reputation hit
8-12B value"] style A fill:#f9f9f9 style B fill:#fff4e6 style G fill:#d4f1d4 style H fill:#d4f1d4 style I fill:#d4f1d4 style J fill:#f4d4d4 ``` ## 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",

Path	2025 Valuation	2027 Valuation	Execution Cost	Expected ROI
Reposition + Agentforce integration	$15–18B	$20–25B (if agents take off)	$2.5B R&D	35–50% upside
Sell to Oracle/Cisco	$12–14B	N/A (divested)	$500M transaction	45–60% of original
Write down + merge into Service Cloud	$10–12B	$12–15B (faster runway)	$1.8B integration	20–35%
Keep as-is + divest under-performing SKUs	$8–10B	$8–12B (flat to slight growth)	$600M cost-cuts	Minimal; destroys shareholder value
Private equity tuck-in (PE buyout)	$9–11B	N/A (PE owned)	$300M earnout risk	30–40% for Salesforce exit

What should Salesforce do about Slack stagnation?

Direct Answer

What's Broken Today

What Salesforce Should Actually Do

Bottom Line

Vendor Stack for Validation

Tags

What does the score mean?