The tiers, Slack Connect, and whether the bundle is a saving or a commitment. Three knowledge checks along the way, and 4 clips from a senior licensing analyst.
This is a taught session, not a talking head. The instructor works through analyst grade slides, and three times the video stops on a question with four options on screen. Pause, commit to an answer, and the next slide explains which option is right and why each of the others is wrong. 4 times in the session the frame splits and a senior licensing analyst gives the view from inside real SAP negotiations, and the instructor picks the clip apart when the slides return.
The full narration of this session, section by section, for reading and reference. Guest analyst clips are marked.
Welcome back. Session eighteen, Slack, and this is the one line in the whole portfolio that touches every person in your organisation. Sales Cloud reaches the sales team. Service Cloud reaches the contact centre. Slack reaches the warehouse, the finance team, the graduates and the board. The per user figure is small enough that nobody argues about it, and multiplied by every employee it is a serious annual number. So today: why the multiplier changes the arithmetic, what each tier is actually for, guests and Slack Connect, the inactive account problem that regrows every year, and the four tests before you fold this into the wider Salesforce agreement. Three knowledge checks. Let's begin.
Five objectives. First, respect the multiplier, because a small monthly figure across your entire headcount is not a small line. Second, read the tiers: what each step buys, and which of those things your organisation actually requires. Third, use guests properly, since external collaboration has cheaper shapes than a full licence and the defaults do not find them. Fourth, handle inactive accounts, which is the largest and least contentious saving here and needs a repeating process rather than a project. And fifth, judge the bundle, because Slack inside the Salesforce agreement can be a saving or a floor, and the difference is measurable.
So, the line that covers everyone. Whole headcount, priced per person across an organisation rather than per function. A small unit price, which is precisely why nobody scrutinises the per user figure. A large total, because a modest monthly rate times every employee is a material annual line. And hard to remove, because communications tools become infrastructure and switching is a change programme rather than a procurement decision. Let me explain what that combination does to your negotiating position.
Guest analyst clip.
So the leverage is not the unit price, which is small and well defended. It is the count, the tier and the terms, all three of which are more movable than most buyers assume, and two of which you can fix without asking anybody's permission.
Right, the tiers and what each step is for. Free gives basic messaging with limits on history and integrations, which suits small teams and pilots that should not quietly become the standard. Paid standard gives full history, unlimited integrations and group calls, and that is most organisations for most of their people. The business tier adds compliance exports, advanced identity and stronger guarantees, which regulated environments and estates with real compliance obligations genuinely need. And the enterprise tier adds multi workspace administration, advanced governance and support, which suits large or federated organisations with many workspaces. The step up is usually bought for one or two specific capabilities, so name them before you agree, because the tier applies to every user while the requirement often applies to a subset.
First knowledge check. Compliance asks for message exports for legal hold. What should you check first? A, nothing, upgrade the whole organisation to the tier that includes it. B, which tier includes it, whether the obligation covers everyone, and what an upgrade costs across the full headcount. C, whether a third party tool can do it more cheaply. D, whether the compliance requirement can be waived. Pause here and pick an answer before you continue.
B. A tier upgrade applies to every licensed person, so a requirement covering a regulated subset can multiply into a whole population charge, and that three part question sizes it before anybody commits. A is the common path, and it is exactly how a departmental obligation becomes an organisation wide cost. C is worth pricing and it comes second, because it may not satisfy the obligation and integration has its own cost. And D is not your decision to propose, and treating a compliance requirement as negotiable is a very good way to lose the room.
Guests and Connect next, which is external collaboration without a full licence. Single channel access puts an external person in one channel at a much lower cost than a full licence. Multi channel guests give broader access, still below a full seat, and are still frequently overlooked. Connect between organisations lets two licensed organisations share channels with each paying for their own people. The default is the expensive one, because nobody researches guest options under time pressure so a full licence gets issued. And review the external population, because contractors and partners licensed as employees is the standard finding in every estate I have looked at. Now, the inactive accounts.
Guest analyst clip.
It regrows, which is the part to hold onto. So the categories: leavers who were never deactivated, common wherever provisioning is not joined to the identity system. Contractors past their end date, where the project finished and the account did not. Accounts with no activity for a quarter, not always removable and always worth asking about.
And bots and service accounts, where some are necessary and some belong to an integration nobody runs any more. Take those in order, because the leavers are uncontentious and the service accounts need somebody technical in the room before you touch anything.
Second knowledge check. Which of these usually delivers the largest Slack saving? A, negotiating a lower per user rate. B, removing inactive accounts and correcting guest licensing. C, moving down a tier. D, reducing the number of workspaces. Pause here before you continue.
B. Quantity beats rate here, because the unit price is small and well defended while the count is large and nobody owns it, and correcting it needs no agreement from anybody outside your organisation. A is worth doing at renewal, and it applies a percentage to a number that may well be wrong. C is real and rarely available, since tiers are usually bought for a capability somebody still needs. And D tidies administration while changing the licence count very little, because the same people simply appear in fewer places.
Which brings me to the bundle. Four tests before you fold it in. What is the standalone price? Establish it first, or you cannot tell what the bundle is worth. What quantity is assumed? A bundle priced on full headcount removes your ability to reduce the count later, which matters enormously given everything we just said. What happens at renewal? A bundled line renews inside a larger negotiation where it is easy to lose sight of. And can you separate it again? Ask explicitly, because a line you cannot unbundle is a line you cannot competitively test. Let me put that fourth one in context.
Guest analyst clip.
Then decide on the numbers. Bundles are often good value, and they are never good value simply because they are tidy, and tidiness is what they are usually sold on when the numbers are not compelling.
Now, the AI tier, which is module three arriving in a new place. AI features come as an upgrade: summaries, search and assistance, offered as a tier or an add on across the population. Apply the flat or metered test from session fourteen, and ask it before the demonstration rather than after. Multiply by everyone, because an AI uplift on a whole organisation licence is one of the largest single AI decisions you will make, larger in total than most of the ones that get far more scrutiny. Adoption decides the value, so measure it on a pilot population first, because a per user AI charge assumes per user use. And buy it for a subset if you can, because if the value concentrates in some teams then licence those teams rather than the organisation.
Five failures. Licensed on headcount rather than users, with a count taken from the HR system instead of from actual active accounts. Guests licensed as employees, because the guest option was not obvious at the moment somebody needed access. A tier bought for one team, so one department's compliance requirement applied to the entire organisation. The bundle never priced standalone, so nobody can say whether it saved anything at all. And no deactivation process, where the clean happens once, gets celebrated, and the population regrows within the year.
Last knowledge check. You clean up four hundred inactive accounts. What matters most next? A, reporting the saving to the sponsor. B, joining deactivation to the leaver process so it does not regrow. C, renegotiating the rate on the reduced count. D, repeating the exercise next quarter. Pause here and pick an answer before you continue.
B. A one off clean fixes today and changes nothing about the mechanism that produced four hundred stale accounts, so without the process the same number returns before your next renewal and the saving was really a loan. A is worth doing and it is not a control. C only helps if you can also reduce the committed quantity, which is a contract question rather than a cleanup one. And D is the manual version of B, and it works right up until the person who remembers to do it moves on. Let me describe what the repeating version looks like.
Guest analyst clip.
Fifteen minutes, if the plumbing is right. Active accounts against licensed, the gap, every quarter, with a trend line so regrowth is visible rather than discovered. Leavers cross check against the identity system, and anything appearing there is a process failure rather than a licensing one, which is a useful distinction when you go and ask for it to be fixed. Guests and external accounts: who they are, which organisation, and whether the cheaper shape applies. Tier justification, one line on why you are on this tier, reviewed annually rather than assumed. And the committed quantity, because a reduction you cannot bill is only a tidy directory.
Three sentences. Slack is the only line in this portfolio priced across your entire headcount, which turns a small and well defended unit price into a material annual figure, so the leverage sits in the count, the tier and the terms rather than in the rate. The largest saving is almost always quantity: inactive accounts nobody owns, contractors past their end date, and external collaborators licensed as employees when a guest shape would have served, and all of it regrows unless deactivation is joined to the leaver process. And before folding Slack into the wider agreement, establish the standalone price, the quantity assumed, what happens at renewal, and whether it can be separated again.
Homework before session nineteen, about ninety minutes. One, compare licensed against active, meaning licensed accounts against those active in the last ninety days, and write down the gap. Two, cross check leavers against your identity system, and find out whether deactivation is automated at all, because that answer determines whether this is a cleanup or a process fix. Three, list every external account: which organisation, which access shape, and what it costs today. Four, write the tier justification in one line, and if nobody can write it, that is the finding. And five, find the standalone price, because if Slack is bundled you cannot judge the bundle without it.
Five guides, all on redresscompliance dot com. Slack enterprise pricing covers the tiers, the enterprise agreement and where the money concentrates. Salesforce multi cloud negotiation explains how a bundled line behaves inside a larger agreement. Which line to open first covers sequencing a multi product negotiation, bundles included. Salesforce add ons pricing sets out the wider add on catalogue and how each line is priced. And Salesforce hidden costs covers what arrives after signature across the whole portfolio.
That is session eighteen. The thing to take away is that when a line covers everybody, the rate is the least interesting number on it, and the count is the one nobody owns. Next time, Marketing Cloud and Account Engagement: contact based metrics, sends, and the growth you do not control, which is a different problem again because the number rises whether or not you do anything at all. See you then.