创造者日报 · 2026-09-16（精选 30 条）
Julian Lehr asked a good question the other day on X: what if Slack had never sold to Salesforce, stayed in founder mode, and went 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 that 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
I run a small social scheduling SaaS on my own. A few months ago I shipped an MCP server so Claude, ChatGPT and Cursor could schedule posts through the same API the app uses. It is used for real now, roughly 700 to 800 connector calls a day at the CDN last week, none of them mine. What follows is the list of things that were different from the demo, in the order they bit. The agent does not know which account you meant. The moment a brand has two Facebook Pages or two LinkedIn orgs, & ;post this to LinkedIn& ; is ambiguous. Every post now has to carry one account id, and the tool description tells the agent to list accounts first and check that the account is still connected. Disconnected accounts were already the number one cause of failed posts for humans. Agents made it worse because they do not notice the red badge. Validate at create time, not at fire time. A scheduled post fails hours after the agent finished talking, and nobody is there to read the error. So media is required at create time on the platforms that need it (TikTok, YouTube, Instagram, Pinterest), even for drafts, the media type has to match the file, and size caps are enforced on upload. The agent gets the rejection while it can still fix it. Retries duplicate. Our create call has no idempotency key. If the transport drops and the agent retries, you get two scheduled posts. Listing and deleting posts are tools too, so the agent can clean up, but that is the honest gap and it is next on the list. Do not make the agent wait for the publish. The MCP call only creates the scheduled post; publishing runs later as a server job. A 200MB video never sits on the MCP transport, which is where every timeout report we saw came from. Approvals need to be a tool, not a dashboard. Posts can be created as pending approval, and either a person or the agent, via an approve call, moves them to approved. Nothing publishes while pending. Without this, teams turn the agent off after the first wrong post. Some platform limits should be enforced by you, not discovered by the agent. X charges far more for posts with links, so we cap link posts per month per plan. An agent that loves adding links hits the cap on purpose. Assistants quote your docs verbatim. When someone asks ChatGPT for a scheduler with an MCP server, the answer lists the vendors whose pages print the endpoint URL and the setup steps in plain text. Pages that describe the feature in marketing language are skipped. We rewrote ours accordingly, and it is the cheapest change on this list. Live-data features are hard to get through app-store revi
邮件版免费订阅：中文频道 · English Edition
PS：TG / X 等墙外链接在大陆网络可能无法直接打开或被安全插件去链/截断——已全文内嵌的可直接读，未内嵌的原址可复制到浏览器（或自备网络环境）打开。
我们只收录能动手的机会、能提效的工具、可复制的增长打法与有壁垒的认知——少而准，为你省时间。