Home / Case Studies / Salesforce True-Up Defence
SalesforceBankingTrue-UpData Cloud

Salesforce true-up defended. $6.1M held back.

A regional banking group received a $6.1M Salesforce true-up notification one quarter ahead of renewal. The opening position from Salesforce bundled the true-up into a Data Cloud commitment and a multi-year edition uplift. Ten weeks later, the true-up resolved at a fraction of the opening number, Data Cloud was repriced against actual ingestion, and the edition uplift was capped through the term.

Modern bank corporate centre
$6.1M
True-up exposure defended
68%
Reduction vs. opening true-up
10 wk
Notification to signature
Capped
Multi-year edition uplift
The contract going in

True-up notice, renewal one quarter out.

The bank ran a substantial Sales Cloud and Service Cloud estate, a growing Marketing Cloud footprint and a recent Data Cloud activation. The true-up notice arrived three months before the master contract was due for renewal, which compressed the negotiation window and concentrated leverage on the Salesforce side.

  • True-up calculated against contractual licence ceiling, not deployed seats.
  • Data Cloud activation tracked at a fraction of the contracted ingestion volume.
  • Multi-year edition uplift clause sitting silent in the existing agreement.
Salesforce's opening position

True-up plus uplift, Data Cloud held flat.

The Salesforce account team proposed settling the $6.1M true-up by rolling it into a new three-year commitment, accepting the edition uplift in years two and three, and preserving the Data Cloud commitment as priced at signature.

What we flagged

The true-up was being used as the entry point for a larger conversation, not as a discrete commercial question. Settling the true-up as part of a renewal package would have made the renewal harder to negotiate on its own merits.

The work

Ten weeks. Four workstreams.

1. True-up evidence

Reconstructed the seat count history across the contract term, including reductions Salesforce had not credited and reassignments that had been counted twice.

2. Data Cloud reprice

Pulled ingestion telemetry against the contracted volume. Repriced the Data Cloud commitment against realistic year-one and year-two adoption.

3. Uplift cap

Negotiated a contractual cap on multi-year edition uplift, ending the silent reset that the existing clause had enabled.

4. Separation of true-up and renewal

Settled the true-up as a discrete commercial event. The renewal was then negotiated on its own merits, without the true-up exposure as leverage.

Lesson

Salesforce true-up notices often arrive in the run-up to renewal for a reason. Separating the true-up from the renewal is the single most important commercial move available to the buyer.

The contract going out

True-up scoped, Data Cloud sized, uplift capped.

The true-up settled against a defensible seat history at a small fraction of the opening number. Data Cloud was repriced against actual ingestion with a two-step adoption ramp. The multi-year edition uplift was capped contractually through the new term.

$6.1M
Defended
True-up exposure reduced from opening position to settled position.
Sized
Data Cloud
Repriced against actual ingestion with a contractual adoption ramp.
Capped
Edition uplift
Multi-year uplift capped contractually for the term.
“We came in expecting to lose a known number and discovered the known number was itself a position. The advisor's framework converted a six-million-dollar conversation into a much smaller one, on its own timetable.”
Chief Procurement Officer · Banking · Anonymised by client request
Related resources

More on Salesforce negotiation strategy.

← Back to all case studies

Got a Salesforce true-up notice?

Tell us the notice date and the renewal date. We will respond within one business day with the lead and the most relevant precedent.