Slack's Cross-Company Network Effect
Front Fundraising, Leadership, Employees and Competitors
Shared Channels mattered because they gave Slack a growth loop that Microsoft could not copy just by bundling Teams into Office 365. Teams spread well inside companies because IT could turn it on for everyone at once. Shared Channels let Slack spread across company boundaries, where sales teams, agencies, vendors, and customers already did real work together in message threads and shared files. That turns one paid deployment into a wedge for many adjacent organizations.
-
Microsoft’s core advantage in 2020 was distribution. Teams rode nearly 258 million Office 365 commercial paid seats and reached 75 million daily active users by April 30, 2020. Two thirds of those users were already sharing or working on files inside Teams, which shows the product was embedded in existing Microsoft workflows, not just installed.
-
Slack’s counter was a different kind of network effect. Shared Channels, later folded into Slack Connect, let two companies use the same channel, with both sides sending messages, sharing files, and running apps in one thread. That makes Slack useful not only as an internal chat tool, but as a lightweight extranetwork for customer and partner work.
-
This matters for Front because external collaboration is where inbox, chat, and support workflows start to overlap. Front was competing with Slack, Teams, Intercom, and Zendesk for the daily system teams use to coordinate around customer conversations. If Slack owned more partner and customer interaction upstream, it could pull more workflows into its orbit.
The next step was always a race to own cross company work, not just employee chat. If Slack could turn partner and customer channels into a standard workflow surface, it would chip away at Microsoft’s bundle advantage by creating demand from the edge of the organization inward, and make collaboration software more network shaped than seat shaped.