Can an agent replace Slack?
Where your company talks, and increasingly where its institutional memory sits.
No. Slack is a network — its value is that everyone is in it, which is not a feature you can rebuild. What an agent adds is finally being able to answer questions from the history you are already paying to retain.
- Indicative spend
- €200/mo
- What it actually costs
- from €7/user/mo, €12 for the tier with history you need
- Verdict
- The moat is real — a network, a dataset, or a liability someone else carries.
What the agent takes over
Every job this product exists to perform, with our verdict on each. Follow one through for the step-by-step breakdown.
- Admin and back officeMostly. The inbox triage, the filing, the chasing, the scheduling, the form-filling — an agent does the great majority of what a competent assistant does. What it lacks is knowing which of your relationships need care.MOSTLY
- Project managementHalf. An agent handles the administration of a project — status, chasing, updating, reporting, spotting slippage — better than most people do. It cannot do the part that is about people, which is the part projects fail on.HALF
- Helpdesk triageYes. Reading a ticket, working out what it is really about, tagging it and putting it in front of the right person is exactly what language models do well — and it is the step where human queues quietly lose hours.YES
Why it survives
Network effect inside your own company.
What you would still need it for
- Everyone being there
- Message history
- App integrations
What replaces it
- None. Put an agent in it instead.
The brief
What you would tell an agent to take over from Slack, assembled from the jobs above.
I want to keep Slack. It currently does: Where your company talks, and increasingly where its institutional memory sits. Take over this work: - Admin and back office — MOSTLY. Mostly. The inbox triage, the filing, the chasing, the scheduling, the form-filling — an agent does the great majority of what a competent assistant does. What it lacks is knowing which of your relationships need care. - Project management — HALF. Half. An agent handles the administration of a project — status, chasing, updating, reporting, spotting slippage — better than most people do. It cannot do the part that is about people, which is the part projects fail on. - Helpdesk triage — YES. Yes. Reading a ticket, working out what it is really about, tagging it and putting it in front of the right person is exactly what language models do well — and it is the step where human queues quietly lose hours. Do not take over: - Everyone being there - Message history - App integrations These stay with me across all of it: - Sensitive communication - Anything that spends money - Deciding what matters this week - Conflict - Scope decisions - Client expectation setting - Motivating a struggling team - Deciding staffing - Declaring a major incident externally - Overriding priority for a strategic account Before we start, tell me: which of these you cannot do with the access I can actually give you, and what would break if this ran unattended for a month. — brief built at cananagentdo.com/slack
Compare
Keep the tool, cut the hours
Slack is not the line item worth attacking. The money is in the people-hours spent working inside it, and that is what an agent takes over — with Slack still holding the data.
Put an agent on it