If Slack Remained Independent: What Is It Worth Without a Salesforce Sale?

AI Summary · Serial Entrepreneur Perspective (The following content is AI-extracted; viewpoints belong to the original author; you can skip the full article after reading this)

SaaStr's founder revisited the hypothetical valuation of Slack staying independent ($2.5B) versus its $27.7B sale price. The core difference lies in the business model: a single product versus a multi-product bundle. The article reveals Slack's actual revenue trajectory post-acquisition by Salesforce and the failure of its multi-product bundling strategy, exposing the structural limitations of platform-type products when expanding revenue.

• Use the Slack case to verify the effectiveness boundary of multi-product bundling (like Atlassian) on ARPU improvement
• Learn to triangulate true revenue for subsidiaries not separately disclosed through financial statement footnotes
• ID the "ecosystem moat" trap: a large app directory doesn't equal high retention…
• When assessing SaaS product expansion potential, focus on cross-category bundling ability rather than single-point growth

Original Article (fully embedded below, no need to visit external sites)

Julian Lehr asked a good question the other day on X: what if Slack had never sold to Salesforce, stayed in founder mode, and gone hard at AI? What would the product look like, and what would it be trading at? What would an independent Slack look like today? Probably $2.5B ARR growing 25%, trading at 7x-8x ARR and seeing a recent boost from agents and AI last quarter. Sort of a 2x GitLab. So worth much less than they sold for ($27B+), not even adjusting for time or dilution https://t.co/F3ab1PiQ4S — Jason ✨👾SaaStr.Ai✨ Lemkin (@jasonlk) September 3, 2026 Two answers. It would almost certainly still be one product with an ecosystem bolted on. And it would trade like Atlassian at a discount, which puts it around $16B to $20B. Salesforce paid $27.7B. It May Still Mainly Be One Product, And That's Most Of The Discount Atlassian is arguably the closest comp to Slack. Atlassian's Teamwork Collection, which bundles Jira, Confluence, Loom and Rovo, crossed 1 million seats and 1,000 customers. Collection customers buy 10%+ more seats than they were buying across the same products standalone. Teamwork customers carry four to five times more paid seats per instance than standalone Jira or Confluence customers. Rovo is used by more than 80% of the Fortune 500, and Rovo adopters grow ARR at roughly twice the rate of non-adopters. Cross-sell, not data center migration, drove the last two cloud beats. That is a multiproduct company whose bundle expands spend. Customers consolidate onto the platform and pay more for the privilege. Slack is one product. And the evidence says an independent Slack stays one product, because that was the deliberate strategy. Butterfield built the app directory, now over 2,600 integrations, as the moat. Slack was the hub and everybody else built the spokes. The economic consequence is that Slack's expansion revenue went to Zoom, Notion, Asana and Google rather than to Slack. Salesforce had every incentive and all the capital to change that, and it mostly didn't. Canvas shipped free on every tier, including the free one. Lists shipped inside existing plans. The one time Slack tried a genuine second SKU, Slack AI at $10 per user per month in 2024, it pulled the add-on about fifteen months later and folded AI back into per-seat tiers gated by plan level. Slackbot today runs on an allowance of 15 messages per user per week inside Business+. Atlassian's bundle raises seats and ARPU. Slack's bundling gives the new product away to defend the seat it already has. The multiple reflects that. Salesforce Disclosed Slack's Revenue Twice, Then Stopped Ever

Original · SaaStrAI: Read full article →