Salesforce License Optimization and Usage Management: A CIO's Strategic Playbook

The CIO's Salesforce Cost Problem in 2026

Salesforce's annual revenue exceeded $37 billion in fiscal year 2026 (ending January 31, 2026), and the trajectory reflects a company that has systematically expanded its revenue per customer through platform breadth, mandatory product bundling, and contractual price escalation. For the CIO, this trajectory translates into one of the fastest-growing line items in the IT budget — often growing at 15 to 25 percent per year through a combination of the annual uplift clause (8 to 10 percent standard in Order Forms), organic seat expansion, and the accumulation of add-on products across renewal cycles.

The governance challenge is structural. Salesforce is purchased centrally through IT but consumed across Sales, Service, Marketing, Finance, and increasingly Operations — each with its own expansion requests, add-on requirements, and renewal timelines. Without a central licence management function, organisations find themselves discovering the true cost of Salesforce only at the point of renewal, when the leverage has already shifted to the vendor.

This playbook addresses the governance gap with a framework that covers five domains: baseline auditing, licence right-sizing, consumption product management, renewal negotiation strategy, and ongoing governance. Each domain is operationally specific — the goal is not a high-level strategy but a working programme that a CIO can deploy with existing IT, Procurement, and Finance resources.

Domain 1: The Baseline Audit

No optimisation programme is credible without a reliable baseline. The baseline audit answers three questions: what Salesforce products are you contracted for, what is assigned to users, and what is genuinely being used. The gap between contracted and used is the optimisation opportunity.

Contracted Inventory

Start with the complete contract portfolio. This means every active Order Form across every Salesforce product — Sales Cloud, Service Cloud, Platform, Marketing Cloud, Data Cloud, MuleSoft, Tableau, CPQ, Revenue Cloud, Agentforce, and any industry-specific editions. In organisations that have been using Salesforce for five or more years, the contract portfolio typically includes multiple layered Order Forms from successive renewals and expansion amendments, and the contracted inventory across all of them is rarely consolidated in a single place.

Create a contract inventory that maps every Order Form to the product covered, the contracted quantity, the current pricing, the annual uplift clause, and the renewal date. This inventory is the foundation for all subsequent optimisation work and the single most important deliverable of the baseline phase.

Assigned and Active Users

The Company Information page in Salesforce Setup provides the total, assigned, and remaining licence counts for every licence type. Export this data as a CSV and cross-reference it against your HR employee master to identify accounts belonging to individuals who are no longer employed. Departed employees whose Salesforce accounts were not deactivated at termination are one of the most consistent sources of licence waste in enterprise deployments.

Beyond terminated employees, run a login activity report for all active users. Filter by last login date and segment users into cohorts: active in the last 30 days, active 31 to 60 days ago, active 61 to 90 days ago, and not active in more than 90 days. The 90-day inactive cohort represents confirmed waste in almost all audit scenarios. The 61 to 90 day cohort requires investigation — these users may be on leave, between projects, or genuinely inactive.

Repeat this analysis for feature licences and permission set licences. These products — Einstein AI capabilities, Revenue Intelligence, Sales Cloud Everywhere, and Salesforce Maps — are often licensed at significant per-user cost and deployed broadly when initial contracts are signed, but utilisation frequently drops sharply after the initial deployment period.

Feature Utilisation Analysis

Login frequency is a necessary but insufficient measure of utilisation. A user who logs in daily but uses only a fraction of their licence's functionality is still a right-sizing candidate. Use the Salesforce Lightning Usage App (Setup → Lightning Usage) to review page visit frequency, object interaction rates, and feature adoption metrics by user profile.

The key comparison is between the licence tier assigned and the functionality actually used. Users on Sales Cloud Enterprise licences ($165 per user per month) who interact exclusively with custom objects and reports but never touch Opportunities, Leads, or Forecasting are candidates for migration to Platform licences ($25 per user per month). The right-sizing opportunity in this scenario is substantial: $140 per user per month in savings for every user correctly reclassified.

Domain 2: Licence Right-Sizing

Right-sizing is the process of aligning every user's assigned licence to the minimum licence type that satisfies their genuine functional requirements. It is the highest-leverage optimisation action available to most organisations because it reduces both the current annual cost and the base on which future uplifts are calculated.

The Core Licence Hierarchy

Salesforce's user licence hierarchy progresses from Platform ($25 per user per month) through Sales Cloud or Service Cloud Starter ($25), Professional ($80), Enterprise ($165), and Unlimited ($330) to Einstein 1 / Agentforce 1 ($550). Each tier includes expanded functionality relative to the tier below, but many users in enterprise deployments have access to capabilities several tiers beyond what their role requires.

A structured right-sizing exercise maps every user's Salesforce role — sales representative, service agent, marketing coordinator, finance analyst, custom application user, executive — to the minimum licence tier that supports their workflows. This mapping is then cross-referenced with actual utilisation data from the lightning usage app to validate that the proposed lower-tier licence provides sufficient access.

The most common right-sizing opportunities in enterprise deployments are: Sales Cloud Enterprise users who should be on Platform licences, Service Cloud Unlimited users who should be on Enterprise, and Einstein or Agentforce add-on holders with zero or near-zero feature activation. Each category requires a different reclamation workflow, but the financial impact of addressing all three systematically is typically a 15 to 25 percent reduction in the total Salesforce seat cost before any renewal negotiation occurs.

Experience Cloud and External User Licences

External user licences — Customer Community, Partner Community, and Customer Community Plus — are a frequently over-purchased product category. Salesforce prices external licences either per user per month (named user model) or per login per month (login-based model). Organisations that deploy Experience Cloud portals for customer self-service often purchase named user licences for all registered customers when a login-based model at a fraction of the per-user cost would better match the actual usage pattern.

Audit the ratio of named external users to monthly active users. If fewer than 20 to 30 percent of registered external users are accessing the portal in any given month, a conversion from named user to login-based licensing is almost always more cost-effective. Salesforce will typically resist this conversion at renewal because it reduces their revenue, but the utilisation data makes the business case objectively defensible.

Integration and Service Account Licences

API integrations, data pipelines, and system-to-system connections require dedicated Salesforce user accounts. These integration users are frequently provisioned with full Sales Cloud or Service Cloud licences when an Integration User licence or Platform licence would satisfy the API access requirements at significantly lower cost. Integration User licences are designed specifically for system-to-system connectivity and carry no human user interface access requirements — they provide the API access needed without the full CRM licence cost.

Identify every Salesforce user account that is used exclusively for system integration rather than human interaction. Review the API access patterns against Integration User licence capabilities. Where the integration requires only API access to standard and custom objects without CRM-specific functionality, migration to Integration User licences produces immediate cost reduction.

Domain 3: Consumption Product Management

Salesforce's product portfolio has expanded significantly beyond its traditional seat-based licensing model. Data Cloud, Agentforce, MuleSoft, and Tableau each use consumption-based or hybrid pricing models that require active management to prevent mid-year overages and structural cost inflation at renewal.

Data Cloud Credit Management

Salesforce Data Cloud uses a credit consumption model where different features — data ingestion, data transforms, data queries, data activations, and identity resolution — each consume credits from a shared pool. A single user action can simultaneously consume credits from multiple pools. For example, running a batch data transform consumes both Batch Data Transforms credits and Data Queries credits when the transform preview is executed.

The most critical management action for Data Cloud is establishing a monthly consumption rate baseline in the first 90 days of deployment. This baseline identifies which features are consuming credits at the highest rate and whether the contracted credit volume is appropriately sized for the actual workload. Organisations that signed Data Cloud agreements based on vendor projections rather than measured consumption rates frequently discover that their credit allocation is exhausted before their contract year ends, triggering overage charges at a rate higher than the bulk contracted price.

Monitor consumption velocity monthly. If the monthly burn rate indicates the annual credit pool will be exhausted in fewer than ten months, escalate to an optimisation review before the credit pool is depleted. Credit optimisation actions include reducing data transformation frequency, increasing batch window sizes to reduce API call volumes, and archiving historical data that does not require active processing. Exhaust the optimisation options before purchasing additional credits — overage credits are significantly more expensive than contracted credits and should be the last resort.

Agentforce Pricing and Consumption Management

Agentforce, Salesforce's AI agent platform, uses a consumption-based pricing model. The original pricing structure charged $2 per conversation — each autonomous AI agent interaction counted as one conversation. In May 2025, Salesforce introduced Flex Credits as an alternative consumption model, allowing organisations to purchase credit pools that can be applied across Agentforce and other AI services rather than being tied to specific conversation counts.

The Agentforce 1 Edition, available at $550 per user per month for AI-first deployments, includes unmetered Agentforce usage but is priced at a significant premium over the base platform tiers. For organisations whose primary Agentforce use cases involve moderate AI conversation volumes, the add-on consumption model may be more cost-effective than upgrading to Agentforce 1 Edition.

The governance challenge with Agentforce is that consumption is determined by how the AI agents are deployed and what triggers them — configurations that are controlled by developers and Salesforce admins, not by end users. CIOs should establish a consumption monitoring dashboard that tracks daily Agentforce conversation volume against the monthly contracted allowance, with automated alerts when consumption approaches 70 percent of the monthly allocation. Agent workflow configurations that generate unnecessary conversations — loops, error retries, or inefficient trigger conditions — are the most common drivers of unexpected Agentforce consumption.

MuleSoft vCore Sizing

MuleSoft Anypoint Platform is licensed on a vCore-based model. vCores are the compute capacity units that scale with integration workload. At approximately $1,250 per vCore per month (at standard commercial rates, before negotiation), vCore allocation is one of the highest cost-per-unit items in the Salesforce portfolio for integration-heavy organisations.

The most common MuleSoft pricing trap is over-provisioning at initial deployment. Integration architects typically request vCores based on peak throughput requirements during implementation, without accounting for the fact that most enterprise integrations operate well below peak capacity for most of the year. The result is contracted vCore allocations that are 200 to 400 percent higher than the actual average workload requires.

Audit MuleSoft vCore utilisation using the Anypoint Platform monitoring console. Review the CPU and memory utilisation metrics for each vCore over a 90-day window. vCores that are running below 20 to 30 percent average CPU utilisation are candidates for workload consolidation — moving multiple integration flows to fewer vCores reduces the contracted vCore count without any impact on integration performance. MuleSoft supports horizontal scaling at peak loads, which means workloads that occasionally spike to high utilisation can be managed with fewer baseline vCores and elastic capacity rather than statically provisioning for peak.

Right-sizing MuleSoft vCores at renewal is one of the highest-impact negotiation actions available for integration-heavy Salesforce deployments. A reduction from 20 contracted vCores to 12 vCores, based on measured utilisation data, saves approximately $120,000 per year at standard rates — and the utilisation data from the monitoring console makes the request objectively supported.

Domain 4: Renewal Negotiation Strategy

The renewal is where the governance work pays off. Licence count data, right-sizing analysis, and consumption metrics are negotiating instruments — their value is highest when they are presented early in the renewal process, before Salesforce has structured its commercial proposal.

The Salesforce Fiscal Year and Negotiation Calendar

Salesforce's fiscal year ends January 31. The end of each fiscal quarter — April 30, July 31, October 31, and January 31 — creates pressure on Salesforce's sales organisation to close deals before quarter-end. Organisations with renewal dates near these quarter-end dates have structural negotiating leverage that organisations renewing in the middle of quarters do not. Salesforce account teams are authorised to provide deeper discounts in the final weeks of a fiscal quarter to meet their quota commitments.

Initiate the renewal conversation 90 to 120 days before your contract expiry date, regardless of where that date falls relative to Salesforce's fiscal quarter. This timeline gives you the flexibility to run the process to a close near a Salesforce quarter-end if the negotiation requires it, without creating artificial urgency that forces you to accept an unfavourable deal.

Addressing the Annual Uplift Clause

Salesforce's standard Order Form includes an annual uplift clause that allows list prices to increase by 8 to 10 percent per year at each renewal term. For a 1,000-seat Sales Cloud Enterprise contract at $165 per user per month ($1,980,000 per year), a 10 percent uplift adds $198,000 to the annual contract value at each renewal. Over a three-year term, this compounding effect adds more than $600,000 to the total contract value.

Negotiating a cap on the annual uplift clause is one of the highest-priority contractual protections for any enterprise Salesforce buyer. The negotiating position should aim for a contractual cap of 3 to 5 percent per year, documented in the Order Form. Salesforce will typically offer a cap of 5 to 7 percent before falling back to the standard 8 to 10 percent if the buyer lacks leverage. The most effective leverage is a documented evaluation of competitive alternatives — whether genuine or exploratory — combined with a current licence utilisation dataset that demonstrates a willingness to reduce contracted quantity if pricing is not addressed.

Be aware that Salesforce will often offer to waive or reduce the uplift in exchange for expanded product footprint — adding Agentforce licences, upgrading to Unlimited edition, or committing to Data Cloud expansion. Evaluate these offers on their actual utilisation merit, not on Salesforce's projected value. Products added to secure a lower uplift rate but not genuinely deployed represent a different form of waste.

Multi-Year Deals and Price Locks

Multi-year deals provide two forms of value: price certainty and negotiating leverage. A three-year commitment gives Salesforce revenue predictability, which they compensate with deeper discounts, lower uplifts, and more flexible contractual terms. For organisations with stable Salesforce footprints, a three-year deal with a contractual price lock and a capped uplift is the most cost-effective structure available.

However, multi-year deals carry risk in a rapidly evolving product environment. Organisations that commit to three years of Agentforce pricing today are making assumptions about AI consumption patterns that are difficult to validate. The Salesforce Flex Credit model, introduced in May 2025, already represents a significant change in how AI consumption is metered. Negotiating flexibility provisions — contractual rights to renegotiate consumption product volumes at the midpoint of a multi-year deal — mitigates the risk of being locked into an over- or under-provisioned AI consumption commitment for three years.

Using Competitive Alternatives as Leverage

Salesforce's pricing is not fixed — it responds to competitive pressure. The most consistent pricing concessions in Salesforce renewal negotiations come from organisations that can credibly demonstrate evaluation of alternatives. For CRM functionality, alternatives include Microsoft Dynamics 365, HubSpot, and SAP Sales Cloud. For service management, ServiceNow and Zendesk provide credible substitutes for specific use cases. For integration, Boomi, MuleSoft alternatives like SnapLogic, and Microsoft Azure Integration Services create competitive pressure on MuleSoft renewal pricing.

A credible competitive evaluation does not require a full-scale RFP. A documented assessment of two or three alternatives — including cost benchmarks, capability comparison, and migration effort estimates — is sufficient to introduce competitive pressure into the renewal negotiation. Salesforce's account team will seek to understand the depth of the competitive evaluation. Be prepared to discuss it factually without revealing the strategic outcome you intend to reach.

Domain 5: Ongoing Governance

The optimisation gains achieved through a structured baseline audit and renewal negotiation erode within 12 to 18 months without ongoing governance. Licence counts drift upward through departmental expansion requests, ad-hoc add-on purchases, and integration account proliferation. Consumption products accumulate mid-year overages without monitoring. The annual uplift compounds on a growing base.

The Quarterly Licence Review

A quarterly licence review is the minimum governance cadence required to maintain optimisation gains. The quarterly review covers: login activity and inactive user identification across all licence types, feature utilisation metrics for high-cost add-ons, consumption rate tracking for Data Cloud credits and Agentforce conversations, vCore utilisation for MuleSoft, and any new Order Form amendments added during the quarter that should be reflected in the master contract inventory.

The quarterly review should produce three outputs: a list of reclamation actions (inactive users to deactivate, add-ons to unassign, integration accounts to right-size), a consumption forecast against remaining annual allocation, and an updated renewal timeline showing which contracts are approaching the 90-day engagement window.

HR System Integration for Licence Governance

The most operationally efficient approach to ongoing licence governance is integrating HR system termination events with Salesforce licence management workflows. When an employee is terminated in the HR system, the integration should automatically trigger a Salesforce deactivation workflow and place the reclaimed licence in a holding pool for reassignment. This eliminates the most common source of licence waste — departed employees whose Salesforce access persists because the IT offboarding process was not followed.

Most enterprise HR systems (Workday, SAP SuccessFactors, Oracle HCM) provide API endpoints that can be connected to Salesforce via a lightweight integration or via an identity management platform. The implementation effort is typically two to four weeks, and the ongoing governance benefit — eliminating the human dependency on manual offboarding — is permanent.

Licence Request Governance and Approval Workflows

New licence requests should flow through a governed approval process that requires justification of the licence type requested, documentation of the business workflows the licence will support, and confirmation that no existing licences can be reallocated from the inactive pool. This approval workflow prevents the pattern of reactively adding licences without evaluating alternatives and ensures that the contracted licence pool is always the minimum required for current business needs.

For high-cost add-ons — Agentforce 1 Edition, Revenue Cloud, Data Cloud — the approval workflow should also require a consumption projection that documents the expected usage volume and confirms that the consumption model (named user, per-conversation, per-credit) is appropriate for the proposed use case. Consumption products added without a usage baseline are the most frequent source of mid-year overage surprises in 2026 Salesforce deployments.

The Optimisation Roadmap: A 12-Month Plan

Implementing this playbook effectively requires a sequenced approach that builds governance capabilities progressively rather than attempting to address all five domains simultaneously.

Months 1 to 3 — Baseline and Quick Wins: Complete the contract inventory, run the login activity analysis, identify inactive users, and execute immediate deactivation actions. Conduct the feature licence utilisation analysis and begin the right-sizing mapping exercise. The goal of this phase is to establish the baseline and capture the highest-confidence reclamation actions before the renewal conversation starts.

Months 4 to 6 — Consumption Analysis and Renewal Preparation: Complete the Data Cloud consumption velocity analysis, audit MuleSoft vCore utilisation, and establish Agentforce consumption monitoring. If renewal is approaching, prepare the negotiation position document incorporating all audit findings. Begin the competitive evaluation process if not already underway.

Months 7 to 9 — Renewal Execution: Execute the renewal negotiation using the baseline data, right-sizing analysis, and competitive evaluation as the core negotiating instruments. Secure contractual uplift caps, multi-year pricing locks where appropriate, and flexibility provisions for consumption products. Document all negotiated terms in the updated contract inventory.

Months 10 to 12 — Governance Institutionalisation: Implement the quarterly licence review cadence, deploy HR system integration for automated licence reclamation, and establish the licence request governance workflow. These governance investments ensure the optimisation gains from the earlier phases are maintained through subsequent renewal cycles.

Key Takeaways for the CIO

The annual uplift is the compounding cost you must address first. An 8 to 10 percent annual uplift on a $2 million Salesforce contract adds more than $600,000 to the three-year contract value. Negotiating a contractual cap of 3 to 5 percent is the highest-ROI single action available at renewal — but it requires the audit data and competitive context to justify.

Right-sizing is more impactful than simple licence reduction. Migrating over-provisioned users to appropriate licence tiers delivers larger savings than simply reducing seat counts, because right-sizing also reduces the base on which future uplifts are calculated.

Consumption products require active monthly management. Data Cloud credits, Agentforce conversations, and MuleSoft vCores do not self-govern. Mid-year overages on consumption products are almost always preventable with proper monitoring. Implement consumption dashboards and alert thresholds before deployment, not after the first overage invoice.

Governance is the only sustainable solution. A one-time audit delivers one-time savings. A governance programme — quarterly reviews, HR integration, approval workflows — delivers compounding savings across every subsequent renewal cycle.

Independent advice is the prerequisite for the CIO. Salesforce account teams are incentivised to grow revenue per customer. Every optimisation and negotiation conversation with them is, by definition, adversarial. An independent adviser with no Salesforce revenue alignment provides the objective analysis, benchmarking, and negotiation support that a purely internal capability cannot replicate.