Slack implementation cost: plans, AI and rollout services

Slack is the one Salesforce product where many buyers skip the implementation entirely. Somebody creates a workspace, people join, and channels multiply. That works for a team of thirty. It fails for an organisation that needs single sign-on, retention rules, eDiscovery, external partners in shared channels and Salesforce records surfacing in conversations. This page prices the licence as Slack publishes it today, then sets out what a deliberate rollout costs and what quotes miss.

#What you pay for Slack

Slack's pricing page lists four plans, with prices shown in US dollars even on the Australian site, as at October 2026:

The page was also running an introductory discount on Pro and Business+ for the first three months when we read it, so check the current offer before you build a budget around list price.

The billing rule is unusually buyer-friendly, and it changes how you forecast. In Slack's words: "Members who take an action in Slack at any time within a 28-day period will be considered active for billing purposes." If someone you have paid for becomes inactive, Slack adds a prorated credit for the unused time, and new members are charged a prorated amount for the rest of the billing period. In practice you pay for people who use it, not for the headcount you predicted.

What happened to the Slack AI add-on

For a while Slack AI was sold as a separate add-on. The current pricing page no longer lists one. AI is described as part of each plan at different levels: Basic AI on Free and Pro, Advanced AI on Business+ and Enterprise-grade AI on Enterprise+, covering conversation summaries, Slackbot as a personal AI agent, AI workflow generation, AI search, daily recaps and file summaries. Slackbot comes with subscription limits. The page says Business+ customers on invoice subscriptions can lift message limits by buying Flex Credits through Salesforce, and that existing Salesforce customers on Free and Pro invoice subscriptions can get access to Slackbot. If your business case depends on heavy Slackbot or Agentforce use, ask your account executive for the Flex Credit price; it is not on the page.

Where Enterprise Grid went

Older proposals talk about Enterprise Grid as the top tier. The current pricing page lists Enterprise+ as the top published plan and sends buyers to sales for it. If you are renewing an older Grid agreement, ask how it maps to Enterprise+, and what changes in features and price, before the renewal date rather than after it.

Doti and what it means for your bill

Salesforce's acquisition record states: "Salesforce completed its acquisition of Doti on December 1, 2025." Whatever Doti's technology contributes will reach customers as Slack capability. As at October 2026 the pricing page shows no separate Doti product or line item, so there is nothing extra to budget under that name.

#A worked licence example

Take a hypothetical organisation with 400 people who will be active in Slack. On Pro paid annually, that is US$2,900 a month, or US$34,800 a year at list price. On Business+ paid annually it is US$6,000 a month, or US$72,000 a year. On Enterprise+ it is US$18,000 a month, or US$216,000 a year.

The jump from Business+ to Enterprise+ triples the licence bill, so it should be justified by a specific requirement: data loss prevention, multiple identity configurations, large-scale external collaboration, or a compliance obligation. Business+ already brings SAML single sign-on and Advanced AI, which covers what many mid-sized organisations need.

The monthly and annual columns also tell a story. Paying monthly costs US$1.50 more per user on Pro and US$3 more on Business+. For a pilot of a few weeks, monthly billing is the flexible choice. Once the rollout is committed, annual billing is the cheaper one, and annual payers can ask to be invoiced rather than charged to a card.

#Phasing the rollout

Because Slack bills active members, a phased rollout costs little in idle seats. That makes phasing the sensible default. Start with one or two teams whose work is naturally conversational, such as a sales pod working deals or a service team swarming cases. Prove the Salesforce use cases with them, then widen.

Each wave should have the same short checklist: accounts provisioned through the identity provider, default channels joined, a thirty-minute orientation, a champion in the team, and a review two weeks later of what people actually use. Use that review to retire channels nobody reads and to promote the workflows that saved time.

The common mistake is the reverse: inviting the whole company on day one with no naming rules and no channel owners. Within a month there are duplicate channels, private conversations about things that should be public, and a security team asking why guests can see internal discussions. Fixing that later means archiving, renaming and re-educating, which costs more than designing it up front.

#What a Slack implementation is made of

Discovery and workspace design. Decide how many workspaces you need, which is often one, and the channel naming scheme, default channels, and who can create channels and invite guests. Enterprise+ organisations with several business units decide how far each unit is separated.

Identity and provisioning. Single sign-on with your identity provider, user provisioning and deprovisioning, and guest account policy. Pro supports sign-in with Google; Business+ adds SAML-based single sign-on; Enterprise+ supports multiple SAML configurations. Getting deprovisioning right matters doubly here, because a leaver who keeps access keeps every channel.

Retention and compliance. Message and file retention policies, legal hold, export rights and data loss prevention on the plans that offer it. Slack's page notes that paid subscriptions keep data for life by default with adjustable settings. That default suits few regulated organisations, so someone must set the policy and get it signed off by legal.

Migration. Moving history from another chat tool, or consolidating several Slack workspaces into one. Ask which history is genuinely needed. Migrating every message from a decade of a previous tool is expensive and rarely read.

Salesforce integration. Installing Salesforce for Slack, mapping users between Slack and Salesforce, deciding which record alerts post to which channels, and building record-based channels for deals or cases. If Agentforce agents will work in Slack, this is also where their access and the people they hand off to are set.

Workflows and apps. Workflow Builder automations for requests and approvals, and the apps from the Slack App Directory you will allow. App approval policy belongs in the rollout, not after it.

Slack Connect. Shared channels with customers and partners need rules: who may start them, what may be shared, and how external members are reviewed. Enterprise+ lists group external messaging with up to 250 organisations.

Training and change management. Short role-based sessions, channel etiquette, and champions in each team. This is where most of the value is won or lost.

#What drives the cost up or down

The biggest variable is the starting point. A greenfield rollout with SSO and sensible defaults is a small project. Consolidating several Slack workspaces left behind by earlier teams or acquisitions is a migration project with real data risk. Moving from another chat platform adds export, mapping and a period of running both.

Compliance is the second variable. A firm that needs eDiscovery, legal hold, data loss prevention and Enterprise Key Management needs those designed and tested. Slack lists Enterprise Key Management as an add-on, so it is a separate commercial line.

Salesforce depth is the third. Posting opportunity alerts to a channel is configuration. Swarming cases with record-based channels, approvals that write back to Salesforce, and agents acting on records are design and build work, and need permission and data-access reviews on the Salesforce side.

#Getting comparable quotes

Give bidders the same facts: active users, plan, number of existing workspaces, source of any migration and the history window you need, identity provider, retention and compliance requirements, the Salesforce use cases, and the number of workflows. Ask for the quote by work package.

#What quotes leave out

Running two tools at once. If you are moving from another chat platform, both licences usually overlap for at least a few weeks. Put that overlap in the budget.

Add-ons and credits. Enterprise Key Management and Slackbot Flex Credits are bought separately from the plan.

Salesforce licences and access. Users who will act on Salesforce records from Slack still need the right Salesforce licence and permissions.

Admin time. Someone has to review channel requests, approve apps, manage guests and archive dead channels. On a large rollout this is a part-time role, and nobody prices it.

Plan changes. Moving from Pro to Business+ later for SAML single sign-on, or to Enterprise+ for compliance, changes the per-user price. Price the plan you will need within a year, not the cheapest one that works today.

#Choosing the plan before the project

The plan sets the scope of the implementation, so choose it first. Pro suits small teams that can live with Google sign-in. Business+ is the usual minimum for a company with an identity provider and a security team. Enterprise+ is for organisations that need enterprise-grade AI, multiple SAML configurations, data loss prevention, large-scale external collaboration or the controls a regulator will ask about.

Within Salesforce, there is often a second question: whether Slack replaces Chatter, Quip or email for certain processes. Each of those is a change to how people work, and each should be on the plan as its own item.

#Measuring whether it worked

A Slack business case usually promises fewer emails, faster answers and quicker deal or case resolution. Decide how you will measure those before go-live, or the review at renewal becomes a debate about feelings. Slack's own analytics show active members and message activity, which tells you about adoption but not about outcomes. Pair them with Salesforce measures the integration can influence: time from case creation to first internal response in a swarming channel, time an opportunity spends waiting on an approval, or the number of handoffs before a request is resolved.

Pick two or three measures, capture a baseline in the month before rollout, and review them after each wave. If a measure does not move, look at the workflow before you blame the tool. Often the channel exists but the alert that should start the conversation was never configured, or it posts to a channel nobody watches.

#Where to go next

For what Slack is inside Salesforce today, read Slack with Salesforce. The subscription detail is on the Slack licence cost page, and the design of the connection on integrating Slack with Salesforce. If you are thinking of leaving at renewal, read should I migrate from Slack. The acquisition story is on what happened to Slack, and partner selection on hiring a Slack partner.