How to reduce Salesforce license and platform costs: audit the drift, not the contract

Short answer: Most Salesforce overspend is not the result of a bad negotiation. It is drift: people who left, licenses that no longer match what anyone actually does, add-ons bought for a project that finished, and data nobody ever deleted. An honest audit of activity, license mix, feature licenses, add-ons and storage usually finds more money than the renewal conversation will.

Why do most orgs overpay for Salesforce?

Because the org changes every week and the contract changes once a year. Every offboarding, role change, cancelled project and abandoned integration leaves a paid artefact behind, and removing it is nobody's job. Zylo's 2026 SaaS Management Index puts average license utilisation at 54%, with $19.8M in wasted spend annually per organisation across the SaaS estate (Zylo).

Drift also compounds. Salesforce announced an average 6% list price increase effective 1 August 2025 across Enterprise and Unlimited editions of Sales Cloud, Service Cloud, Field Service and selected Industry Clouds, with no change to Foundations, Starter and Pro editions (Salesforce). Every seat you are not using gets slightly more expensive to not use.

Where does the money actually leak?

Inactive and departed users

Start with last login. Anyone with no login in 90 days is either gone, on the wrong license, or was never onboarded. One detail matters here: freezing a user blocks the login but keeps consuming the license. Only deactivating releases it for reassignment.

A license mix nobody revisited

Most orgs buy one edition for everyone at go-live and never revisit it. Three years later, warehouse staff, finance approvers and read-only managers are all on the same full CRM seat as the sales team.

Feature and permission set licenses

Some are free, some are paid, and the paid ones tend to get assigned in bulk during a rollout and never reviewed again. Pull the assignment counts and compare them against who has used the feature this quarter.

Add-ons that outlived their project

Managed packages, industry add-ons and AppExchange subscriptions bought for a specific initiative. If nobody can name the business process an add-on serves today, it is a candidate for removal.

Storage and data volume

File and data storage grows quietly: old attachments, orphaned records, a recycle bin nobody empties, and integration logs written to a custom object with no retention rule. Data volume is a real cost line, not a rounding error.

Integration users and sandboxes

Integration accounts often sit on a full CRM license because that is what was available on the day. Check what your edition entitles you to before renewing another one. The same goes for sandboxes that were spun up for a migration and never refreshed or removed.

How do you run a license audit in a week?

1. Export every user with last login, license type, profile and role. Flag anyone with no login in 90 days.
2. Split that list into leavers and occasional users. Leavers get deactivated, which returns the license to the pool.
3. Map the remaining users to what they actually open. Object usage tells you more than a job title does.
4. List every paid add-on with a named owner. No owner, no business process, no renewal.
5. Check storage consumption against your entitlement and identify the top consumers.
6. Total the findings and take them into the renewal, not after it. The numbers are only leverage if they exist before the conversation starts.

When does switching to a cheaper license type make sense?

When the user genuinely lives in custom objects rather than in the standard CRM. Platform licenses keep Accounts, Contacts, custom objects, reports and dashboards, but they do not give access to Leads, Opportunities, Cases or Campaigns, and Entitlements, Orders and Price Books are out too. Salesforce Ben's worked example puts a Platform seat at $25 per user per month against $165 for Enterprise (Salesforce Ben).

The discipline is simple: before you move anyone, list the objects and features they touched over a full quarter. A migration that saves a licence fee and then breaks a service agent's case queue costs more than it saved.

What should you not cut?

• The sandbox you actually deploy through. Saving that line item means testing in production.
• Backup and recovery. The cheapest possible org is the one that cannot be restored.
• Audit and security capabilities you are relying on for a compliance obligation.
• The admin capacity that runs the audit. Cut that and you are back here in eighteen months.

How do you keep the drift from coming back?

• Put deactivation in the offboarding checklist, not in someone's memory.
• Give every paid add-on a named owner and a review date.
• Re-run the activity export quarterly. It takes an hour once the query exists.
• Attach a retention rule to any object an integration writes to.

We do this pass at Tekunda before designing anything new on a client org, for a plain reason: a smaller, cleaner org is cheaper to run and faster to change.

FAQ

Does deactivating a user free up the license?

Yes. Deactivating releases the license for reassignment. Freezing only blocks the login and keeps the license consumed, which is why frozen users are a common hidden cost.

Can we reduce our license count in the middle of a contract?

Usually not. Most subscriptions are committed for the term, so the practical move is to reassign freed licenses instead of buying more, and to right-size at renewal.

How much can a license audit realistically recover?

It depends on how long the org has run unattended. With average utilisation at 54% across SaaS estates, an org that has never audited should expect to find unused seats, unassigned add-ons and storage it is paying to keep.

Is a Platform license always the cheaper option?

Only when the user does not need the standard CRM objects. Check real object usage over a quarter before moving anyone, because the objects Platform excludes are the ones service and sales teams live in.

When should we start preparing for renewal?

Early enough that the usage data already exists when the conversation opens, and early enough to deactivate and reassign rather than simply accept the quote.