Verified pricing snapshot

Slack pricing and procurement cost model

Model Slack Pro and Business+ list prices, active-member billing, annual versus monthly rates, integrations, retention, security, and renewal.

Slack selected public list-price chart
Buyer answer

Slack's published US rates are $7.25 per active user per month annually or $8.75 monthly for Pro, and $15 annually or $18 monthly for Business+. Forecast active members, guest treatment, retention, identity, compliance, integrations, support, and consolidation before relying on the headline rate.

Price-check boundary

Official public sources checked 15 September 2026. Prices below are USD list-price references, not a quote. Country, currency, tax, reseller, promotion, contract, legacy subscription, quantity, and renewal date can change the payable amount.

Published plan-price snapshot

PlanBilling basisPublished rateWhat to verify
FreeNo charge$0Usage and history limits apply
ProAnnual$7.25Per active user per month
ProMonthly$8.75Per active user per month
Business+Annual$15Per active user per month
Business+Monthly$18Per active user per month

A price row answers only the starting arithmetic. Before approval, preserve the dated vendor page or quote, record the currency and billing term, and identify every population that will be charged. If the vendor page and order form differ, the signed order form and governing contract control the purchase.

How Slack billing changes total cost

  • Slack describes paid-plan billing around active members and applies credits under its fair billing policy when qualifying members become inactive.
  • Annual and monthly rates differ materially; do not multiply a monthly rate by twelve without recording the commitment basis.
  • External collaboration, identity, message retention, exports, legal hold, compliance, and support requirements can change edition or architecture.
  • Model application integrations and workflow replacements: Slack may add cost while also displacing meeting, messaging, alerting, or workflow tools.

Illustrative annual license baselines

The examples use the second paid public plan shown above where available. They are reproducible arithmetic, not a forecast or recommendation.

PopulationAssumptionAnnual baselineExcluded
25 paid usersPro · Monthly$2,625/yearLicense baseline only; excludes tax, add-ons, implementation, migration, support, internal labor, and discounts.
100 paid usersPro · Monthly$10,500/yearLicense baseline only; excludes tax, add-ons, implementation, migration, support, internal labor, and discounts.
250 paid usersPro · Monthly$26,250/yearLicense baseline only; excludes tax, add-ons, implementation, migration, support, internal labor, and discounts.

Cost drivers the quote must expose

  1. Active paid members, single- and multi-channel guests, bots, external collaborators, and growth
  2. Annual versus monthly commitment and fair-billing credit treatment
  3. History, retention, export, eDiscovery, identity, security, and support needs
  4. Paid apps, workflow automation, integration maintenance, and administration
  5. Migration, governance, consolidation, renewal, and exit/export work

Build base, expected, and stress cases. A useful model separates recurring licenses and consumption from one-time vendor services, internal implementation effort, dependent tools, and exit work. Record unknown values as a range with an owner and decision deadline rather than silently entering zero.

Questions to put in writing

  • Which account types are billable under the quoted plan and configuration?
  • How are deactivations and credits calculated and shown on invoices?
  • Which retention, export, identity, and compliance requirements force Business+ or Enterprise Grid?
  • Which existing tools will Slack replace, overlap with, or require?
  • What evidence and format are available for a future workspace export or migration?

Renewal and exit checks

Record the initial term, renewal term, auto-renewal status, notice deadline and delivery method, protected pricing, uplift rule, minimum quantity, reduction window, reassignment rights, usage true-up, data-export method, post-termination access, deletion schedule, and retained-data exceptions. Test the export before the renewal decision if the product will hold business-critical records.

Official sources used

PR97 summarizes public vendor information for comparison. It has not inspected your tenant, order form, reseller proposal, or negotiated contract. Recheck the linked official source and written quote on the day of decision.

Editable working file

Normalize the quote in one worksheet

Capture plan, billable unit, allowances, services, internal cost, renewal, and exit assumptions beside their evidence.

Open pricing worksheet

Slack approval record

The approval should state which operating roles require this service, why the selected edition is necessary, and which evidence proves the mandatory workflow. For Slack, record the exact quote, plan, billable population, included allowance, add-on, service scope, implementation owner, and first renewal deadline beside the decision.

Commercial facts to reconcile

  • Slack describes paid-plan billing around active members and applies credits under its fair billing policy when qualifying members become inactive.
  • Annual and monthly rates differ materially; do not multiply a monthly rate by twelve without recording the commitment basis.
  • External collaboration, identity, message retention, exports, legal hold, compliance, and support requirements can change edition or architecture.
  • Active paid members, single- and multi-channel guests, bots, external collaborators, and growth
  • Annual versus monthly commitment and fair-billing credit treatment
  • History, retention, export, eDiscovery, identity, security, and support needs
  • Paid apps, workflow automation, integration maintenance, and administration

Reviewer questions

  1. Which account types are billable under the quoted plan and configuration?
  2. How are deactivations and credits calculated and shown on invoices?
  3. Which retention, export, identity, and compliance requirements force Business+ or Enterprise Grid?

After launch, compare the first invoice with provisioned access and expected usage. Review adoption by required role and workflow at 30, 60, and 90 days. Before notice is due, test a current export and decide whether to retain, resize, renegotiate, replace, or cancel. Keep this evidence with the order form so future reviewers can reproduce both the cost and the reason for the purchase.