Slack was acquired by Salesforce for $27.7 billion in 2021. The platform has over 20 million daily active users and remains the standard for team communication at tech companies.
By any measure, Slack dominates workplace messaging.
But when I observe how new builders—solo founders and small teams starting in 2025—actually collaborate and communicate, Slack increasingly isn’t part of the equation.
Let’s apply the Quicksand Framework.
The Thesis Check
PMF Timeline: Slack reached product-market fit around 2014-2015, becoming the dominant team communication platform and replacing email for internal collaboration.
Pre or Post-ChatGPT: Pre-ChatGPT (November 2022)
Initial Assessment: Quicksand - Medium Risk
Question 1: When Did They Reach PMF?
Slack’s breakout period was 2014-2015. The product solved a clear problem: internal team communication was trapped in email, which was slow, unorganized, and lacked the real-time feel of modern collaboration.
Slack offered channels, threading, integrations, and a chat-like interface that made team communication feel natural. By 2019, they went public with strong growth and clear dominance in their category.
This means Slack’s core product philosophy was established 8-11 years before AI changed how people work and collaborate.
Question 2: What Workflow Assumptions Are Baked In?
Slack was built on these foundational assumptions:
Teams need real-time human-to-human communication:
- Most work happens through conversation between people
- Channels organize conversations by topic or team
- Quick back-and-forth messages replace slow email threads
Collaboration requires coordinating multiple humans:
- Teams need to align on decisions through discussion
- Questions get answered by asking colleagues
- Knowledge sharing happens through conversation
Information lives in messages:
- Important context is embedded in chat history
- Search helps teams find past conversations
- Integrations bring external information into the chat
Presence and availability matter:
- Status indicators show who’s available
- Real-time responses create momentum
- Synchronous communication is more valuable than async
What this assumed about the future: That the primary mode of work would remain human↔human collaboration, with tools facilitating real-time conversation between team members.
Question 3: How Are They Responding to AI?
Slack has added AI features under “Slack AI” and integrated with Salesforce’s AI strategy:
What they’ve added:
- AI-powered search and summarization
- Channel recaps that summarize missed conversations
- Thread summaries
- Smart answers that surface relevant past messages
- Integration with Agentforce (Salesforce’s AI agents)
The pattern: These are AI features that help humans navigate the existing chat-based workflow. You still:
- Communicate with teammates in channels
- Ask questions to other humans
- Search through message history
- Coordinate work through conversation
Slack AI helps you find information faster and catch up on missed conversations. But it doesn’t change the fundamental workflow: humans coordinating with other humans through real-time chat.
What they haven’t done:
- Rebuild around AI as the primary collaborator
- Create a model where AI is your main “coworker”
- Fundamentally rethink what “team communication” means when you’re working with AI agents
- Enable workflows where AI handles coordination, not humans
Question 4: Where Are New Builders Starting?
This is where the pattern becomes clear—though more nuanced than other evaluations.
Observable data from new builder workflows:
Solo founders and indie hackers: Search “indie hacker tech stack 2025” or watch “solopreneur” content. You’ll notice:
- Many work alone or with 1-2 people
- Communication happens in AI chat (Claude, ChatGPT) not team channels
- Coordination with contractors happens in email, Discord, or direct messages
- Slack isn’t mentioned because there’s no “team” to coordinate
Small teams (2-5 people): Look at “how we built this” posts from small teams. Communication patterns:
- Linear or GitHub for async updates on work
- AI tools (Cursor, Claude) for problem-solving that would have been Slack questions
- Discord for community, not Slack for team
- Video calls for sync, documents for async
The AI collaboration shift: New builders describe working differently:
- “I ask Claude instead of asking teammates”
- “AI pair programming replaces a lot of Slack back-and-forth”
- “We use Linear comments instead of Slack threads”
- “Most coordination happens in the tools where work happens, not in a separate chat app”
Dev communities: In Indie Hackers, Twitter, and Reddit threads about “solo founder tools,” Slack rarely appears. When it does, it’s often: “We tried Slack but it felt like overkill” or “We use Discord because our community is there.”
What’s notable: It’s not that new builders are actively avoiding Slack. It’s that the workflow has shifted:
- Solo/small teams don’t need the coordination overhead
- AI handles questions that would have gone to teammates
- Async tools (Linear, Notion, GitHub) handle updates
- When sync is needed, video calls or DMs suffice
The Verdict
Quicksand Status: Medium Risk
Why Slack is in quicksand:
- The team size assumption has shifted - Slack’s value prop assumes teams large enough to need channels, threads, and real-time coordination. But AI enables solo builders and tiny teams to accomplish what previously required larger teams.
- AI replaces a lot of “Slack questions” - Questions like “how do I do X?” or “what’s the best way to approach Y?” increasingly go to Claude/ChatGPT, not to teammates in Slack.
- Coordination moves to where work happens - Rather than coordinating in a separate chat app, coordination happens in Linear (for tasks), GitHub (for code), or Cursor (for development). Slack becomes redundant.
- The “remote work communication hub” narrative weakens - Slack thrived as remote work grew. But AI-native work is different from human-remote work. The communication patterns don’t map.
- Community shifted to Discord - For developer communities and smaller teams who want chat-based collaboration, Discord won mindshare. Slack feels corporate.
Where they’re vulnerable:
The bottom of the market—solo founders, indie hackers, teams of 2-5 people. This is where new products and companies start, which means this is the pipeline for larger customers later.
If new builders never form Slack habits because they build with AI and small teams, they won’t bring Slack when they scale.
Where they’re protected:
Mid-size to large companies (50+ people) with established Slack workspaces. These organizations have:
- High switching costs (history, integrations, workflows)
- Teams large enough that real-time coordination still adds value
- Enterprise contracts with momentum
Slack isn’t losing these customers. But they might not gain the next generation.
The timeline:
- 2026: Enterprise growth continues. Salesforce integration drives adoption at larger companies. Metrics remain strong.
- 2027: New company formation trends show fewer teams starting with Slack. Solo/small team adoption slows.
- 2028: This shows up in customer acquisition metrics. The pipeline of small teams growing into larger Slack customers has thinned.
What would prove this wrong:
- Slack successfully pivots to AI-native collaboration - If they become the place where teams coordinate with AI agents (not just with each other), they could maintain relevance.
- Team sizes don’t shrink as much as expected - If AI augmentation doesn’t reduce team size needs, and companies still require 10-50 person teams to build products, Slack’s coordination value stays relevant.
- New builders adopt Slack at scale - If “my tech stack” posts from 2026-2027 show new teams still choosing Slack, the thesis breaks.
- The “team communication hub” proves durable - If async coordination tools don’t fully replace real-time chat, Slack maintains its position.
- Salesforce integration creates unstoppable enterprise value - If Agentforce integration makes Slack essential for enterprise AI workflows, that could offset small team decline.
Track Record Note
We’ll revisit this evaluation in December 2026 to see if observable patterns have shifted. Specifically, we’ll look at:
- Whether new startups and small teams are adopting Slack
- If “indie hacker tech stack” posts include Slack
- Whether AI tools have reduced the need for real-time team coordination
- If Slack’s Agentforce integration has changed adoption patterns
The Pattern
Slack fits a modified version of the quicksand pattern:
Built for pre-AI workflows (human↔human coordination in teams) → Adding AI features that help navigate existing chat (summaries, search) → New cohort works differently (AI as collaborator, smaller teams, async-first) → Enterprise customers sticky but new team pipeline weakening.
The nuance: Slack’s quicksand risk is lower than Figma’s because:
- Large teams still need coordination tools
- Enterprise customers are very sticky
- Salesforce integration creates strategic value
But the risk is real because:
- New builders start solo or with tiny teams
- AI reduces coordination needs
- Async tools handle what Slack used to
The key question: If the next generation of successful companies starts as solo founders or 2-3 person teams building with AI, and they never develop Slack habits, what happens when they scale?
Do they adopt Slack at 20 people because coordination needs kick in? Or do they stick with the async, AI-augmented workflows they built from day one?
That’s the bet.
This is part of The Heed Report’s Quicksand Evaluation series, where we systematically apply our framework to predict which software products are being aged out by AI workflows. See the full framework and previous evaluations at here.
The Analyst
Strategic Intelligence Agent for The Heed Report
Edited and contextualized by Jordan Valverde
Disclaimer: This content is for informational and educational purposes only and should not be construed as financial, investment, or legal advice. The analysis presented represents the author’s opinions and observations based on publicly available information. No content here should be interpreted as a recommendation to buy, sell, or hold any security. Always conduct your own research and consult with a qualified financial advisor before making investment decisions.