Full narration of the briefing. Click a section heading to jump the player to that moment.
Part three gave the carrier what it was using. On its own that is only half a position, because knowing you have eight hundred and twenty spare seats tells you nothing about whether the seats you do use are fairly priced. The other half is the benchmark: what comparable organisations actually pay for the same clouds at the same scale. Not list price, which is a starting position dressed as a fact.
Not last year's discount, which only tells you what you accepted last time. What peers pay, now, for the same thing. Without that number, every discount you are offered sounds generous, because there is nothing to measure it against.
The comparison set matters as much as the result. This carrier's annual run rate was compared against fifty seven Salesforce enterprise agreements in the Asia Pacific telecom cluster. Same region, same industry, comparable scale, which is what makes a benchmark defensible rather than merely interesting. And it was held against three separate things, not one: per user list price, per cloud bundle discount, and the consumption metric on Marketing Cloud and MuleSoft.
That third dimension is the one most buyers skip, and it is where a bundle can look competitive on seats while the metered lines quietly carry the margin.
Five dimensions came back with a gap, and the spread is the interesting part. Sales Cloud Enterprise, list at a hundred and sixty five dollars per user per month, benchmark a hundred and fourteen, a gap of thirty one percent. Service Cloud Enterprise, same list of a hundred and sixty five, benchmark a hundred and eight, thirty five percent. Marketing Cloud Pro, list twelve hundred and fifty dollars per ten thousand contacts, benchmark eight hundred and twenty, thirty four percent.
MuleSoft Anypoint, list two dollars fifty a credit, benchmark one eighty, twenty eight percent. Tableau Creator, list seventy five dollars a month, benchmark fifty eight, twenty three percent.
Now read that spread properly, because it is more useful than the average. Twenty three percent on Tableau and thirty five percent on Service Cloud are not the same negotiation, and a single bundle discount averages them into one number that conceals both. That is precisely why a bundle is attractive to sell: it is one line, one percentage, one conversation. Decompose it and you can see which clouds are carrying the deal and which are being subsidised by it.
The carrier's overall benchmark landed thirty two percent below the Salesforce proposal, and it held in Australian dollars and in US dollars, which removes the currency conversation before anyone starts it.
Be clear about what this instrument is and is not, because misusing it costs you credibility you will need later. A benchmark is evidence about the market, not an entitlement and not a demand. Walking in and announcing that peers pay thirty two percent less, therefore give me thirty two percent, is the fastest way to be told your situation is different, and there will be some truth in that. What the benchmark actually does is change the shape of the conversation: it moves you from asking for a discount to discussing why your price sits where it does relative to the market.
That is a question the account team has to answer internally, and it is much harder to answer with silence.
Which leads to the move this carrier made, and it is the second of the seven levers. Bundle decomposition. Every cloud priced separately, then each one compared against the bundle line it sits inside. Two things fall out of that.
You find the clouds where the bundle is genuinely good value, and you say so, which buys you credibility for the rest of the conversation. And you find the clouds where it is not, which is where you concentrate. It also makes a descope possible, because you cannot remove a cloud from a price you cannot see. A bundle you have decomposed is a bundle you can negotiate.
A bundle you have accepted as one number is a number you can only argue about.
So at this point the carrier had a complete position, four months before the proposal deadline. What it used, cloud by cloud, dated and filed. What the market pays, dimension by dimension, held against fifty seven comparable agreements. And a close date chosen deliberately, sixty days before the deadline and before the new list published.
None of the three is an argument on its own. Together they are a case, and a case is what the person across the table needs in order to go and get you a number their organisation will actually approve. Next part, the seven levers that case turned into, and what each one was worth.
Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded. Want Redress to contact you? Reach out and we respond the same day.
Talk to a Salesforce negotiator