Editorial photograph of a procurement leader at a Brazilian retail bank reviewing the Salesforce SELA against global benchmark data
Case Study · Salesforce · Brazil

A Brazilian bank cuts Salesforce by 25%.

A retail bank in Brazil compared its SELA against the Redress global benchmark. Six clouds, two thousand seats, three year term. The benchmark gap held a twenty five percent reduction. The renewal closed at the lower number.

Read the Framework Salesforce Hub
25%Annual cost reduction
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

A Brazilian retail bank held a Salesforce Enterprise License Agreement covering Sales Cloud, Service Cloud, Marketing Cloud, Experience Cloud, MuleSoft, and Tableau. The annual run rate sat at fifteen million reais. The renewal proposal landed nine months out at a sixteen percent uplift.

The bank engaged Redress for a benchmark assessment. The Redress global benchmark for a six cloud SELA at the bank's seat band sat twenty seven percent below the renewal proposal. The negotiation closed at a twenty five percent net reduction, holding the savings across the next three year term.

Read this case study alongside the Salesforce knowledge hub, the Salesforce advisory practice, the Salesforce SELA Playbook, the Cracking the Salesforce SELA reference, and the Vendor Shield subscription.

Key Takeaways

What a CFO and CIO at a regional bank need to know in 90 seconds

  • Six cloud SELA at two thousand seats benchmarks twenty seven percent below the Salesforce list proposal. The gap holds across emerging market currencies.
  • The seven percent annual uplift on the SELA was capped at three percent. The cap held for the full three year term.
  • Marketing Cloud and Experience Cloud were partially descoped. Active seat counts validated the descope without losing the bundle discount.
  • MuleSoft consumption was converted to a flexible credit. The conversion released eighteen percent of the MuleSoft annual line.
  • Tableau Creator and Viewer ratios were rebalanced. The rebalance saved on Creator licenses without losing analyst capability.
  • Quarterly true up was replaced with annual true up. The change reduced the cash flow exposure on volume drift.
  • The renewal closed forty five days before the term end. The pre close discipline avoided the auto renewal trap.

Starting position

The bank ran six Salesforce clouds across the retail, commercial, and private banking lines of business. The total active seat count sat at one thousand eight hundred and sixty, against a contracted entitlement of two thousand and two hundred seats. The estate had grown through acquisition and consolidation.

The starting estate at signing

CloudContracted seatsActive seatsAnnual lineBuyer side flag
Sales Cloud Enterprise1,2001,140R$5.2MTrue up cushion
Service Cloud Enterprise600540R$2.6MActive seat gap
Marketing Cloud Pro1 org1 orgR$1.9MSender count drift
Experience Cloud50,000 logins32,000 loginsR$1.4MLogin band over scoped
MuleSoft Anypoint4 vCores3.2 vCoresR$2.5MvCore underutilised
Tableau Creator + Viewer200 + 1,000140 + 920R$1.4MCreator overcounted

The starting position blind spot

The bank had not run an active seat reconciliation since the prior renewal. The provisioned seat count carried inactive employees, leavers, and seasonal contractors. The benchmark assessment surfaced the gap on day one.

The benchmark gap

The Redress global benchmark for a six cloud SELA at the bank's seat band runs across one hundred and sixty comparable engagements. The benchmark covers North America, Europe, Latin America, and Asia. The Brazil regional currency adjustment carries through the model.

Five benchmark variables that drove the gap

  • Per seat list price by edition. The Enterprise edition list at the bank's band benchmarked twenty two percent below the proposal.
  • Bundle discount band. The six cloud bundle discount benchmarked at thirty four percent versus the proposed twenty seven percent.
  • Annual uplift cap. The benchmark holds at three percent. The proposal opened at seven percent.
  • True up cadence. Annual true up benchmarks better than quarterly for emerging market FX exposure.
  • MuleSoft consumption flex. The benchmark converts vCore commitments to a credit pool with eighteen month rollover.

The benchmark surfaced the position in writing

The Redress benchmark report carried the variance against the proposal line by line. The report became the buyer side opening position. The Salesforce account team negotiated against documented benchmarks, not against an unsupported request.

Six commercial levers

The negotiation deployed six commercial levers in sequence. The sequence matters. Volume and price first, then term and uplift, then bundle composition, then exit and renewal cadence. The wrong sequence concedes leverage early.

The six lever sequence the bank used

  • Lever 1: Right size the seat count. Active seat count became the contracted seat count, with a fifteen percent growth band.
  • Lever 2: Cap the annual uplift. Three percent cap on the SELA total, not on each line separately.
  • Lever 3: Convert MuleSoft to credit. vCores became a credit pool with eighteen month rollover.
  • Lever 4: Rebalance Tableau. Forty Creator licenses converted to Viewer at the higher discount.
  • Lever 5: Annual true up. Quarterly true up replaced with annual, with a documented exception for acquisitions.
  • Lever 6: Pre term close. The renewal closed forty five days before the term end, avoiding the auto renewal trap.

The Salesforce SELA discipline is the same in every region

The bank's regional reading was that Latin America negotiations played differently. The benchmark proved the position holds globally. The same SELA discipline that bends North American renewals bends Brazil renewals. The currency adjustment is mechanical, not commercial.

The bank's procurement team carried the benchmark report into every escalation. The report neutralised the regional argument and held the position through the close.

Negotiation timeline

The negotiation ran on a one hundred and twenty day timeline against a renewal due date. The cadence stayed inside the buyer side window. Salesforce escalated twice. Both escalations resolved on the buyer side position.

One hundred and twenty day negotiation timeline

DayEventBuyer side actionSalesforce response
Day 0Renewal proposal landedEngaged Redress benchmarkStandard list pricing
Day 30Benchmark report completeCounter proposal filedAccount team escalated to leadership
Day 60First escalation callHeld the lever sequenceInitial concession on uplift
Day 90Second escalation callWalked the bundle compositionFinal pricing offer on bundle
Day 105Final terms agreedLegal review with carve outsContract redline cycle
Day 120Pre term renewal closeSigned forty five days earlyClosed before auto renewal

The timeline discipline that held

The bank carried the benchmark report through every milestone. The procurement team did not improvise. The escalation calls ran from the documented position. Salesforce had nothing to negotiate against except a benchmarked counter proposal.

Settlement and outcome

The settlement closed at a twenty five percent net annual reduction. The reduction held across the three year term with the three percent cap. The total contract value over the term ran below the prior term, despite the cloud expansion.

Outcome line by line

CloudPrior annualNew annualSavingLever applied
Sales CloudR$5.2MR$4.0M23%Right size + bundle
Service CloudR$2.6MR$2.0M23%Right size + bundle
Marketing CloudR$1.9MR$1.4M26%Sender band right size
Experience CloudR$1.4MR$1.0M29%Login band right size
MuleSoftR$2.5MR$2.05M18%vCore to credit
TableauR$1.4MR$1.05M25%Creator to Viewer

The benchmark is the negotiation. Without the benchmark the bank carried a reasonable counter. With the benchmark the bank carried documented variance. Salesforce had to defend a price against published comparable engagements, not against an opinion.

Renewal posture

The bank now runs the Salesforce estate inside the Redress Renewal Program. The program runs a quarterly seat reconciliation, an annual benchmark refresh, and a six month pre renewal positioning brief. The next renewal opens with the benchmark already in writing.

What to do next

The seven step checklist below is the buyer side starting position for any Salesforce SELA renewal.

  1. Reconcile active seats against contracted seats. Strip out leavers, inactive accounts, and seasonal contractors.
  2. Run the global benchmark. Pull comparable engagements at the same cloud mix and seat band.
  3. File the counter proposal. Document the variance line by line against the renewal proposal.
  4. Sequence the levers. Volume and price, then term and uplift, then bundle composition, then exit cadence.
  5. Walk the timeline. One hundred and twenty days from proposal to close, with two escalation calls in the middle.
  6. Close pre term. Sign forty five days before the term end to avoid the auto renewal trap.
  7. Run the renewal program. Quarterly reconciliation, annual benchmark refresh, six month pre renewal brief.

Frequently asked questions

Does the Salesforce benchmark hold in emerging markets?

Yes. The Redress global benchmark covers North America, Europe, Latin America, and Asia engagements. The currency adjustment is mechanical and does not change the underlying discount band. The same SELA discipline that bends a North American renewal bends a Brazil renewal. The bank in this case study held the benchmark variance through the close.

What seat band benchmarks at the deepest discount?

The discount curve steepens at the two thousand seat threshold and again at five thousand seats. A bank at the two thousand seat band benchmarks at a twenty seven to thirty four percent bundle discount on a six cloud SELA. The discount band is documented across one hundred and sixty comparable engagements in the Redress benchmark.

Can MuleSoft vCores be converted to credit?

Yes. Salesforce will convert MuleSoft vCore commitments to a flexible credit pool with eighteen month rollover. The conversion runs through the SELA, not the MuleSoft order document separately. The bank in this case study released eighteen percent of the MuleSoft annual line through the conversion. The credit pool absorbed seasonal traffic peaks without overprovisioning.

What is the Salesforce auto renewal trap?

Salesforce SELA contracts default to auto renewal at the contracted price plus the auto renewal uplift. The auto renewal trap fires when the renewal negotiation runs past the term end and the contract auto renews on the prior commercial terms. The fix is to close the renewal forty five days before the term end. The bank in this case study closed at day one hundred and five against a one hundred and twenty day window.

Should the customer reveal the benchmark to Salesforce?

Yes. The benchmark report is the counter proposal. Filing the report in writing forces the Salesforce account team to defend the price against documented comparable engagements. Without the report the negotiation runs on opinion. With the report the negotiation runs on data. The Salesforce response cycle compresses from weeks to days.

How does Redress engage on Salesforce SELA?

Redress runs Salesforce engagements inside Vendor Shield, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. The work covers seat reconciliation, global benchmark refresh, lever sequence design, escalation support, and pre term close discipline. Always buyer side, never Salesforce paid.

How Redress engages on Salesforce

Redress runs Salesforce engagements inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. The Salesforce commercial leadership sits with the founders.

Read the related benchmarking, about us, locations, and contact pages.

Score your Salesforce position against the buyer side benchmark in under five minutes.
Open the Salesforce Utilization Calculator →
White Paper · Salesforce

Download the Salesforce Renewal Playbook.

A buyer side reference on Salesforce SELA leverage, the global benchmark variance, the six lever sequence, the escalation discipline, and the pre term close. Built from over one hundred and sixty Salesforce engagements.

Independent. Buyer side. Written for CIOs, CFOs, and procurement leaders carrying Salesforce estates. No Salesforce influence. No partner kickback.

Salesforce Renewal Playbook

Open the white paper in your browser. Corporate email only.

Open the Paper →
25%
Annual cost reduction
3%
Uplift cap held
6
Commercial levers
500+
Enterprise clients
100%
Buyer side

The benchmark is the negotiation. Without the benchmark the bank carried a reasonable counter. With the benchmark the bank carried documented variance. Salesforce had to defend a price against published comparable engagements, not against an opinion.

Group CFO
Brazilian retail bank
More Reading

More from this practice.

Salesforce Hub →
Cracking the Salesforce SELA
Salesforce · Article
Cracking the Salesforce SELA
SELA mechanics decoded.
16 min read
SELA Playbook
Salesforce · White Paper
SELA Playbook
Salesforce renewal masterplan.
18 min read
Salesforce Advisory
Salesforce · Service
Salesforce Advisory
The Salesforce practice.
10 min read
Salesforce Knowledge Hub
Salesforce · Hub
Salesforce Knowledge Hub
Master Salesforce reference.
18 min read
Benchmarking Service
Service · Benchmark
Benchmarking Service
The benchmarking practice.
10 min read
Editorial photograph of enterprise contract negotiation strategy

A Salesforce renewal is one buyer side benchmark away from solved.

We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.

Salesforce intelligence, monthly.

SELA benchmark refreshes, six lever sequence design, escalation discipline, MuleSoft credit conversion, Tableau rebalancing, and pre term close tactics across every Salesforce engagement we run.