Standard, Premier and Signature, what the percentage buys, and whether you need it. 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 twenty three, support. This is a line most organisations have not examined since the year they first implemented Salesforce, and it is priced as a percentage of everything else you buy, which means it has been quietly growing the entire time. We met this mechanism in session ten with sandbox add ons. Support works the same way, at a larger percentage, applied to a bigger base. So today: why an indexed line behaves differently, what each tier actually adds, the five numbers that test whether yours is earning its price, the alternatives, and what to ask for on the support line specifically. Three knowledge checks. Let's begin.
Five objectives. First, see it as an index, because a percentage of net spend rises with every purchase whether or not you use support more. Second, say what each tier adds: response times, named contacts, proactive services and access to expertise. Third, test the value with evidence, meaning case volume, severity mix and what you actually consumed last year. Fourth, know the alternatives: a partner, internal capability, or a lower tier plus targeted expert services. And fifth, negotiate it as its own line, because it is usually bundled into the total and very rarely examined on its own.
So, a percentage rather than a price. It is indexed, being a share of net subscription spend, so it grows when the subscription grows. It is unrelated, because your support needs do not rise because you bought more marketing contacts. It is material, since at higher tiers this is a significant line comparable to a whole product. And it is rarely reviewed, being bundled into the total, renewed automatically, and examined by almost nobody. Let me put some proportion around that third point.
Guest analyst clip.
One of the easiest lines to leave unexamined for a decade, and one of the more straightforward to test once you decide to look. Which is a good combination, because it means the work is small and the finding is often large.
Right, the ladder. Standard is the included support: documentation, community and basic case handling, which suits stable estates with internal capability and no critical dependency. Premier adds faster response targets, broader case coverage and access to guidance and training, which suits most organisations running Salesforce as a business critical system. And Signature adds named technical contacts, proactive monitoring and event readiness support, which suits large or complex estates where an outage has immediate financial consequence. The published response targets are the visible difference between them. The invisible difference, and in my experience the one that actually matters day to day, is whether you have a named human who already knows your org and does not need the situation explained from the beginning each time.
First knowledge check. You buy an additional cloud. What happens to your support line? A, nothing until the support agreement renews separately. B, it rises, because it is a percentage of net spend. C, it rises only if you raise more cases. D, it falls, because the percentage reduces at higher spend. Pause here and pick an answer before you continue.
B. Support is indexed to what you spend rather than to what you consume, so every purchase carries a support increment that is almost never mentioned in the business case for that purchase. A treats it as a separate agreement when it usually rides on the subscription. C is how buyers assume it works, and a usage based support charge would at least be defensible. And D is the volume discount instinct again, and a declining band is something you can negotiate rather than something you are given.
So where is the value, if you use it. Response time on severity one, which is the only tier difference that matters during an outage, and it is contractual rather than aspirational. A named contact who knows you, which is the difference between explaining your org each time and being understood. Proactive review before peak, genuinely valuable for seasonal businesses and frequently unused by everybody else. And access to product expertise, worth real money during a major implementation and much less between them. So ask what you consumed, because every one of those is countable, and if the count is zero then the tier is not earning its price. Let me give you the numbers to pull.
Guest analyst clip.
Five numbers, and they take an afternoon. Cases raised last year, total and the trend, because a falling case count against a rising support bill is the finding on its own. Severity mix, meaning how many were genuinely critical, and most estates raise very few. Response times achieved against the target you are paying for, which is the tier's core promise.
Proactive services consumed, so health checks, reviews and readiness sessions, booked and attended rather than merely offered. And support cost per case, which is crude and clarifying: divide the annual line by the case count, look at the number, and notice your own reaction to it.
Second knowledge check. Which finding most justifies moving down a support tier? A, the support cost has risen every year. B, low case volume, no severity one incidents, and no proactive services consumed. C, another organisation of your size pays less. D, your budget has been reduced. Pause here before you continue.
B. That is consumption evidence about your own estate, and it answers the only question that matters, which is whether you are using what the tier provides. A is the index doing exactly what an index does, so it is a reason to look rather than a reason to move. C invites a debate about whether the comparison is fair, which you will not win with data you do not have. And D is honest and it is not an argument, because the tier is either earning its cost or it is not, and budget pressure does not change that answer either way.
So, four alternatives. A lower tier plus targeted services, buying expertise for the project that needs it rather than a year of standing access. A partner support arrangement, often cheaper and frequently more responsive, and it does not cover platform defects, which is the limit of it. Internal capability, because a strong admin team resolves most of what reaches a vendor queue anyway. And tier by phase: higher support during a major implementation, lower once the estate settles. Let me be balanced about these, because I do not want to leave you with the impression that the answer is always to buy less.
Guest analyst clip.
Nothing is free. Each of those moves work somewhere, so price the work rather than just the licence line, and a support reduction that lands two extra incidents a year on a stretched internal team is not a saving, it is a transfer.
Now, five asks on the support line specifically. See it as a separate line, broken out on the order form with its own percentage stated plainly, because you cannot negotiate what you cannot see. A declining percentage, since as spend grows the rate should fall, because your support need does not scale with your subscription. A cap in absolute terms, or better, convert the percentage to a fixed fee for the term. Exclusions from the base, because consumption lines and pass through costs should not carry a support percentage. And a tier review point, meaning the right to move tier at each anniversary rather than only at renewal, which is the ask that makes every future review actionable.
Five failures. Bought once and renewed forever, so a tier chosen during the original implementation and still in place six years later. Never separated from the total, invisible inside the subscription line, so nobody has ever priced it alone. Percentage applied to everything, including consumption lines that carry no meaningful support burden. Tier justified by anxiety, bought for the outage that has not happened, with no view of whether the tier would actually help when it does. And no usage evidence, so the conversation becomes opinion against opinion, and the incumbent tier always wins that one.
Last knowledge check. What should the support percentage not be applied to? A, the core subscription. B, consumption lines and pass through costs. C, additional user licences. D, edition upgrades. Pause here and pick an answer before you continue.
B. A support percentage is meant to fund the cost of supporting a platform, and a credit balance or a pass through charge carries no comparable support burden, so including them in the base inflates the line for no additional service. A is the legitimate base, and arguing about it is a rate discussion rather than a scope one. C and D both increase the platform you are supporting, so their inclusion is at least coherent. Exclusions are a scope argument, and scope arguments are usually easier to win than rate arguments. Let me set out the review.
Guest analyst clip.
One afternoon, once a year, before the renewal window rather than during it. Pull the five numbers: cases, severity mix, response times achieved, proactive services used, cost per case. Compare against the tier, so what the tier promises against what you demonstrably consumed. Ask the operations team whether the support relationship helped in the last twelve months, and ask for specific examples rather than a general impression. Price one alternative, a lower tier plus targeted services, costed, because even if you keep the tier you now know what you are choosing. And record the decision: keep, move up or move down, with the evidence beside it, dated, so next year starts from something.
Three sentences. Support is priced as a percentage of net spend, which makes it the second indexed line in your agreement, rising every time you buy anything at all even though your need for support has no relationship to how many marketing contacts you now hold. The tier is either earning its price or it is not, and that is answerable with five numbers you can pull in an afternoon: case volume, severity mix, response times achieved, proactive services consumed, and a crude cost per case. And negotiate it as its own line: a declining rate, a cap or a fixed fee, exclusions for consumption and pass through costs, and the right to change tier at each anniversary.
Homework before session twenty four, about ninety minutes. One, find the support line: the percentage, the base it applies to, and the annual figure in currency, because many people have never seen that third number. Two, pull twelve months of cases, count and severity mix, and most estates are surprised by how low the critical count is. Three, check proactive services, so what your tier includes and which of those you actually booked and attended. Four, calculate cost per case by dividing the annual support figure by cases raised, and look at the number honestly. And five, ask operations one question: did the support relationship materially help this year, and where.
Five guides, all on redresscompliance dot com. Salesforce hidden costs covers the lines that ride alongside the subscription, support included. Salesforce contract terms, ten clauses, shows where the support percentage sits in the paperwork. Salesforce licensing cost twenty twenty six gives the full cost picture including the percentage based lines. Salesforce add ons pricing covers how the surrounding catalogue is priced and packaged. And the Salesforce negotiation CIO playbook covers sequencing the support conversation inside the wider deal.
That is session twenty three. The thing to take away is that any line priced as a percentage of your spend deserves a review it almost never gets, and five numbers pulled in an afternoon will tell you whether yours is earning its price. Next time, shelfware, true ups and the no downgrade reality: why Salesforce counts go up and rarely come back down, and what to do about that. See you then.