Canadian insurance group. Three million Canadian dollars saved on Salesforce.

How a Canadian insurance group turned a premium consolidation proposal into a CAD 3 million saving: cross org deduplication, documented Shield scope, and seasonal surge pricing.

What was the situation at this Canadian financial institution?

A Canadian insurance group running Salesforce across sales, service, and an advisor platform faced a multi year renewal with a proposed expansion the business had not requested. The estate had grown through acquisition, carried overlapping orgs, and the renewal proposal consolidated everything upward into premium editions with Shield attached estate wide.

Procurement had a mandate to cut run rate in Canadian dollars, while the business needed the advisor platform untouched through a regulatory deadline. The engagement started seven months before expiry.

The starting position

• Contract: multiple agreements from acquisitions, misaligned terms, no uplift caps.
• Usage: no consolidated active user view across orgs; Shield deployed on a subset but licensed broadly.
• Proposal on the table: consolidation into premium editions with estate wide add ons and a multi year escalator.

What did the consolidation analysis find?

The analysis found material inactive populations in the acquired orgs, Shield licensed well beyond its deployed scope, and a seasonal workforce pattern that the proposed structure priced at full year rates. The measured baseline reframed the entire proposal.

1. Cross org reconciliation: active users deduplicated across orgs, against the published Salesforce editions and pricing as the unit price anchor.
2. Add on scope mapping: Shield event monitoring and encryption mapped to the orgs where compliance actually required them, with requirements documented against the Shield product scope.
3. Seasonality model: login curves across two years exposed the four month surge pattern.
4. Edition fit: measured feature use by role family against the published edition pricing.

What the deduplication revealed

Acquired orgs carried users licensed twice and departed users licensed still. Deduplication across orgs, not discounting, was the single largest line in the saving.

Where the common advice on compliance add ons is wrong

The standard advice is that regulated institutions should license compliance products estate wide for safety. We disagree. In roughly 10 of the 30 to 40 Salesforce negotiations Fredrik Filipsson advised in 2024 to 2025, the compliance scope was documentable to a subset of orgs, and estate wide licensing was a pricing convenience for the vendor, not a regulatory requirement. The buyer side move at this client was to have the risk team document the actual requirement per org, then license exactly that. Compliance defines the scope; it does not waive the price discipline.

The expansion nobody asked for became the discount everybody claimed. The measured baseline is what actually moved the number.

What were the results and what transfers to other estates?

The renewal closed roughly three million Canadian dollars below the proposal across the term, with the advisor platform ringfenced through the regulatory deadline, Shield licensed to its documented scope, and surge capacity priced for the peak window. The escalator was replaced with a capped uplift and annual reduction rights.

What the term sheet locked in

The uplift cap, the reduction rights, and the surge window pricing were written into the term sheet before the final number was agreed, under the master terms on Salesforce's agreements page.

What transfers: deduplicate across orgs before any consolidation conversation, make risk teams document compliance scope per org, and price seasonal populations for their season.

The transferable sequence

• Months 1 to 3: cross org reconciliation and add on scope mapping.
• Months 4 to 5: mandate, measured baseline, and counterproposal structure.
• Months 6 to 7: commercial negotiation, ringfence, signature.

What to do next

1. Deduplicate active users across every Salesforce org you run.
2. Map each compliance add on to the orgs where it is deployed and required.
3. Have the risk team document the regulatory scope in writing.
4. Model seasonal login curves over at least two years.
5. Price surge populations for the surge window in the term sheet.
6. Replace escalators with capped uplifts and annual reduction rights.
7. Ringfence regulatory critical platforms before applying commercial pressure.

The Salesforce practice runs acquisition consolidation analysis as standard, and more outcomes are in our case studies. The multi vendor negotiation scorecard shows where your renewal stands.

Frequently asked questions

How much did this Salesforce negotiation save?

Roughly three million Canadian dollars against the renewal proposal across the term, with an uplift cap and annual reduction rights replacing the proposed escalator.

What produced the savings?

In order: cross org deduplication of inactive acquired seats, Shield licensed to documented compliance scope instead of estate wide, seasonal surge pricing, and edition refit.

Do compliance products have to be licensed estate wide?

No. The regulatory requirement is documentable per org, and licensing to that documented scope is the defensible position. Compliance defines scope; it does not waive price discipline.

How were seasonal workers handled?

Two years of login curves established a four month surge window, and the term sheet priced surge capacity for that window instead of carrying year round licenses.

How long did the engagement take?

Seven months from start to signature: three on reconciliation and scope mapping, two on the counterproposal, two on commercial negotiation.