Southern US telco. Twenty percent off the Salesforce renewal.

A southern US telco carried three Salesforce orgs and 4,300 seats accumulated through acquisitions into one renewal. Org consolidation, an edition reset, and utilization evidence closed the deal 20 percent below the prior run rate.

What did the telco's Salesforce estate look like before the deal?

Two acquisitions had left the company with three production orgs: the legacy Sales Cloud org, an acquired org mixing sales and Service Cloud, and a smaller regional org. Each had its own admin team, its own renewal date, and its own pricing history.

• Seats: about 4,300 across the three orgs, with an estimated 600 to 900 users holding seats in more than one org.
• Editions: a mix of Unlimited and Enterprise with no documented rationale for who sat where.
• Contracts: three paper trails with different discount levels against published pricing.

Why had nobody consolidated earlier?

Renewal dates never aligned, and each org had an internal owner defending it. The renewal that finally synchronized two of the three dates created the consolidation window.

How did utilization evidence reshape the seat and edition model?

Login history, feature adoption, and API usage were pulled for all three orgs over 120 days. The analysis separated seat duplication from edition inflation, and both from genuine growth need.

What did the edition analysis actually compare?

Feature usage against the edition entitlement grid: sandbox counts, API limits, and platform features. A seat consuming nothing above Enterprise entitlements is an Enterprise seat, whatever the invoice says.

How did the consolidation roadmap become negotiation leverage?

The consolidation plan gave every duplicate seat a documented exit path, which converted soft utilization talk into hard volume risk for the vendor. The negotiation framed one question: price the consolidated estate honestly, or watch it shrink seat by seat.

• Sequencing: the consolidated baseline went to the account team before any org level quote was issued.
• Term trade: a three year term on the consolidated org bought a renewal cap and locked the edition mix, under the master subscription agreement framework.
• Common date: the third org was brought onto the same renewal date mid term at the negotiated rates.

What closed the 20 percent gap?

Roughly half came from removing duplicate and dormant seats, a third from the edition reset, and the remainder from term structure. No single heroic discount; three documented corrections stacked.

What should other post acquisition Salesforce customers take from this?

Acquisition debt in a Salesforce estate compounds quietly through every renewal it survives. The correction is a project, but the evidence phase is fast and the leverage expires once the renewal signs.

1. Inventory orgs, seats, and editions across every acquired entity now, not at renewal.
2. Pull 120 days of login, feature, and API usage per org.
3. Identify multi org users and assign each a single target seat.
4. Map every seat's feature use to the cheapest edition that covers it.
5. Take the consolidated baseline into the renewal before quotes are issued.
6. Trade term length for a renewal cap and a locked edition mix.

Does this work without actually consolidating orgs?

Partially. The seat and edition corrections stand on their own, but the full 20 percent needed the consolidation roadmap, because credible volume risk is what moves a vendor from discount talk to structural pricing.

Where the common advice on Salesforce renewals is wrong

The standard advice is to benchmark your discount percentage against peers and push the gap. We disagree. In roughly 20 to 30 Salesforce negotiations Morten Andersen advised in 2024 to 2025, discount benchmarking alone moved low single digits, because it accepts the vendor's seat count and edition mix as given. The structural corrections, duplicate seats, edition inflation, dormant licenses, moved 15 to 25 percent in post acquisition estates. The buyer side move is to fix the estate model first and negotiate the rate second. The discount argument flatters the invoice; the structure argument shrinks it.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

What to do next

Five moves turn this analysis into a lower invoice on the next renewal.

A sequence you can run this quarter

1. List every Salesforce org, contract, and renewal date across acquired entities.
2. Pull 120 days of login, feature, and API usage for each org.
3. Quantify multi org duplicate users and dormant seats.
4. Map feature usage to the minimum edition per population.
5. Build the consolidation roadmap before opening renewal talks.
6. Anchor the negotiation on the consolidated baseline with a renewal cap.

White Paper · Salesforce

Salesforce Negotiation CIO Playbook

The CIO grade buyer side framework for a Salesforce negotiation. Read it free.

Read the white paper

Frequently asked questions

How much did this telco save on its Salesforce renewal?

20 percent below the prior combined run rate across a 4,300 seat estate, locked on a three year term with a renewal cap. The saving stacked from duplicate seat removal, an edition reset, and term structure rather than one headline discount.

How common is seat duplication after acquisitions?

Very. Estates we reviewed in 2024 to 2025 carried 15 to 30 percent structural duplication where users held seats in multiple acquired orgs. It persists because org renewals are negotiated separately and nobody owns the cross org view.

What is edition inflation in a Salesforce estate?

Seats licensed at Unlimited while consuming only Enterprise level features. The check is feature usage against the edition entitlement grid: sandboxes, API limits, platform features. About 700 seats failed that test in this case.

Do you need to consolidate orgs to get the savings?

The seat and edition corrections deliver partial savings alone, but the full result needed the consolidation roadmap. Documented volume risk is what shifts the vendor from discount percentages to structural pricing.

When should the consolidated baseline be presented to Salesforce?

Before the account team issues any quote. Baselines presented first set the negotiation frame; evidence introduced after a quote reads as a discount request and consistently moves less in our file.

What term structure did the deal use?

Three years on the consolidated org with a renewal price cap and a locked edition mix, with the third org moved onto the same date mid term at the negotiated rates. Term length was the currency that bought the cap.