Does Slack need to own everything you build

Slack is shipping Slackforce Surfaces, a feature that lets you describe a chart or dashboard you need and watch an AI build it inside the chat window, pulling data from Google Drive or Salesforce. The pitch is seamless: stop bouncing between tools, do the work where you're already talking about it. It's also the third iteration of the same bet Slack has made in the last five years. The previous two lost to reality.

Canvas launched in 2021 with identical reasoning — unified workspace, less context-switching, collaborative documents born inside Slack. Finance teams kept building in Excel. Analytics teams kept using Tableau. Six months in, most Canvas channels held async standup notes and internal wikis, the work that didn't demand specialization anyway. The fragmentation Slack promised to solve simply moved: some teams worked in Slack while others didn't. Non-users context-switched harder than before because now they had to check two places.

The absurdity is worth naming. A knowledge worker's real friction isn't that their tools are separate — it's that knowledge work resists containment. Accounting needs Tableau because Slack charts don't model variance. Product needs Figma because describing a design in text is slower than moving pixels. Sales needs Salesforce because forecasting in a spreadsheet embedded in chat is theater. Each field has accumulated the specialized vocabulary and workflows that actually work. Slack can't flatten that without making all of it worse.

What Slack is actually selling is a different problem: the genuinely tedious work of bouncing from Slack to your browser to find the right tool, opening it, hunting for the data you need. That friction is real. But "you can build it in Slack now" doesn't eliminate the friction. It just moves the friction to the moment someone who actually needs the real version has to rebuild it properly later. The actual winner is whoever makes you stay in the flow you're already in, not whoever promises to contain all flows at once.

For anyone managing a team, the question isn't whether this feature is useful. It probably is, for the 10 percent of charting work that's truly casual. The question is how many Slack features you can introduce before the platform becomes the job itself. Your people spend the day navigating Slack's own complexity instead of doing work. Every integration is a bet that staying put beats getting the right tool. Five years in, Slack keeps doubling down on a bet that consistently fails to win.