Three weeks ago, Salesforce completed its purchase of Slack for something close to twenty-eight billion dollars, the largest acquisition in the company's history and one of the largest in the history of enterprise software. The timing is almost unkind. A fortnight before the deal closed, Microsoft announced that Teams had reached 250 million monthly active users. Slack's last publicly disclosed commercial metric was in the region of 169,000 paying customers. On the conventional scoreboard, one company just spent twenty-eight billion dollars to buy second place in a market that a bundled competitor has already taken. That reading assumes the buyer was purchasing a chat product. It was not.
What was actually bought
The system of record has been commoditised. Every serious organisation already has one for customers, one for finance, one for people, and the differences between the credible options have narrowed to implementation quality. What has not been commoditised — and what nobody owns outright — is the layer where people actually coordinate: where an exception is escalated, an approval is granted, a discount is argued about, a delivery date is renegotiated, a decision is made. That layer currently sits in chat, email and meetings, largely disconnected from the records it modifies. Whoever owns it can route work, capture context, and place their own applications at the point of decision rather than at the point of data entry. That is what twenty-eight billion dollars was spent on: the bet that coordination is worth more than recording, and the recognition that a company selling records has no defence if somebody else owns the conversation. The specific asset inside the purchase that deserves attention is cross-company channels — the shared workspaces that connect an organisation with its customers, suppliers and partners. A bundled competitor can put a chat client on every desktop through licensing. It cannot easily manufacture a network of channels that already exists between companies, because those depend on counterparties agreeing rather than on licences being assigned. Network effects that run between organisations are the one asset that distribution alone does not buy.
What buyers should expect from the product
Over the next eighteen months, expect the acquired platform to become progressively less generic and more opinionated: customer records rendered inside conversations, approvals and alerts routed into channels with actions attached, workflow automation tied into the acquirer's integration and analytics assets, and pricing that increasingly rewards customers who own both. The corollary is that it becomes less differentiated as a general internal messaging tool and more differentiated as a customer-facing workflow surface. That divergence is the most useful thing for a buyer to understand, because it changes the question from which chat tool do we prefer to where does each tool earn its place.
A decision framework, by situation
If you are standardised on the competing suite. Do not migrate. You already have an internal collaboration platform you have paid for. The only serious question is whether external shared channels with customers or partners would generate enough commercial value to justify a second platform in a bounded population — sales, service, key accounts — with an explicit boundary and owner. If you are heavily invested in the acquirer's customer platform. There is genuine consolidation logic here, and the integration will be real rather than theatrical. Go in with open eyes about what you are concentrating: one vendor would then hold your pipeline, your customer data, your service history and the channels through which your people talk to your customers. That is a strong operating position for you and an extremely strong negotiating position for them. If you use neither. A merger is not a reason to buy anything. Revisit in a year, when the integrated product exists rather than being described.
The concentration question nobody raises until renewal
When the conversation layer and the record layer belong to the same vendor, three things change quietly. Renewal leverage moves, because the two contracts stop being independent and a decision to leave one becomes a decision to re-platform both. Data portability gets harder, because the value increasingly lives in the linkage between messages and records rather than in either alone. And workflow becomes sticky in a way that licences never were: automations built in proprietary tooling, by people who have left, that nobody can specify well enough to rebuild. None of this is an argument against buying. It is an argument for writing the exit into the entry. Align contract end dates so you can negotiate both at once rather than sequentially. Secure explicit export rights for message history in a usable format, not merely a statement that data belongs to you. Keep decisions and commitments in systems designed to outlive the tool that captured them. And maintain a written inventory of the automations you depend on, with enough description that they could be rebuilt somewhere else.
The governance problem hiding in shared channels
Cross-company channels are the strategic asset and also the least governed thing in most organisations that already use them. Work through the questions. Who owns a channel shared with a customer — the account manager who created it, or the company? When the contract ends, what happens to two years of conversation, and who can export it? Whose retention policy applies when yours is seven years and theirs is thirty days? If your team discusses pricing or internal escalation in a channel the counterparty can see, who noticed? When an employee on either side leaves, who removes them? And when a dispute arrives, whose disclosure obligation covers the record? These are answerable, and the answers belong in a one-page standard covering channel naming, ownership, joiner and leaver process, retention, what may be discussed externally, and a quarterly review of which external channels are still live. Organisations that adopt shared channels without that standard are building a discovery liability with excellent search.
Practical Guidance for Platform Strategy Review
- Decide the boundary between platforms by function and audience, not by preference, and write it down in one paragraph.
- Value the external channel network separately from internal messaging; it is the part of this deal that could actually generate revenue.
- Align renewal dates across the vendor's products so the negotiation happens once, with leverage.
- Secure message export rights in usable formats and test an export before you need one.
- Inventory business-critical automations with plain-language descriptions so they are rebuildable.
- Publish a shared-channel standard covering ownership, retention, membership review and what may be said in front of a counterparty.
- Negotiate now if you are renewing in the next two quarters, while the acquirer is buying reference customers.
- Do not let the merger drive the decision; let your operating model drive it, and use the merger as the timing excuse.
The Regional Angle
Three observations matter more here than the deal's financial logic. The first is that the shared external channel already exists in this market — it is just ungoverned. The relationship channel between a regional supplier and its customer is overwhelmingly a consumer messaging group containing the account manager, the client's procurement officer, two engineers and, frequently, somebody nobody can identify. It holds pricing, delivery commitments, scanned documents and informal approvals. So the proposition being sold as a new category of collaboration is not new here; it is the formalisation of something that is already the primary commercial channel. Framed that way, the business case improves markedly and the barrier becomes clear: it depends entirely on the counterparty agreeing to move, and in a relationship-led market where the client sets the channel, that is a commercial negotiation rather than an IT rollout. The organisations that will succeed with governed shared channels here are those that make them the condition of a service commitment — faster response, named team, visible status — rather than those that ask clients to install something for the supplier's convenience. The second is that the premise of the deal assumes an operating model that most regional groups do not have. The vision is that the customer platform becomes the centre of the company and the conversation layer becomes its interface. In this market, customer relationship management adoption is genuinely deep in a narrow band of sectors — banking, telecoms, aviation, large developers, some insurers — and thin everywhere else. For a typical diversified family group, the system of record is the ERP, the customer relationship lives in the relationship manager's phone, and there is no pipeline in any system for the strategic accounts that produce most of the margin. For those organisations, this merger is not a product decision at all. Its relevance is the lesson about vendor concentration, and the more immediate question of whether they have any system of record for customer commitments in the first place. The third is practical and short: check hosting and data location before writing either product into a policy. Message data residency is offered in a defined list of regions that does not currently include the Gulf, and the acquirer's own regional infrastructure programme is still building out. If your policies, your customer questionnaires or your public sector tenders require in-country storage of commercial communications, that constraint decides this question for you today, whatever the roadmap promises for next year. Ask for the current, contractual answer in writing rather than the announced one.
The objection worth taking seriously
The strongest objection is that this is a defensive purchase at a distressed strategic moment, and that it will not work. Bundling has already decided the general collaboration market; the acquired company's growth had slowed before the deal; very large software acquisitions have a poor record of delivering the integration described at announcement; and the specific promise — that chat becomes the interface to customer records — has been made before, by several vendors, and has mostly produced notification spam with a logo on it. On that view, buyers should ignore the noise entirely and carry on with whatever they were doing. Much of that is likely to be right about the acquisition itself, and I would not bet against the bundle continuing to take share in undifferentiated internal messaging. But the buyer-side consequences arrive regardless of whether the deal succeeds for its owner. If it works, you face a more capable, more entangled platform and a concentration decision. If it fails, you face a product whose independent roadmap has been redirected, whose pricing will be restructured, and whose future depends on a strategy you did not choose — which is its own kind of risk, and the one that historically hurts customers of acquired software more. Either way the actions are the same: know where your coordination layer lives, govern the external channels you already use, align your renewals, and keep your decisions somewhere that outlives the tool. That work is worth doing this quarter and does not require a view on whether the acquisition was a good idea.
Common Questions
Should we switch platforms because of this?
Almost certainly not. Switching costs are paid in behaviour, not licences. Change only if the external channel network or a deep customer platform integration produces value you can name and measure.
Will pricing change?
Expect bundling first and repricing second, typically at your next renewal rather than immediately. If you renew within two quarters, start the conversation now.
Does this weaken the competing suite's position?
Not in internal collaboration, where distribution is decisive. It opens a different contest over cross-company channels, where the bundle's advantage is much weaker because the counterparty has to agree.
What should we expect over the next twelve months?
Expect a wave of integration announcements at the acquirer's annual conference next month, most of which will ship later and thinner than presented. Expect cross-tenant shared channels from the bundled competitor to become generally available and to turn external collaboration into the main battleground of 2022. Expect standalone enterprise wins for the acquired product to slow as licensing gravity works, offset by growth inside the acquirer's existing customer base. Expect pricing and packaging changes that favour buying both. And expect the first serious compliance incident involving a shared external channel — retention mismatch, an unnoticed participant, or a disclosure request — to force the governance conversation that almost nobody is having today.
Platform Strategy Review — we define where each collaboration platform earns its place, govern the external channels you already run, and structure renewals so consolidation does not quietly become dependence.