Salesforce Licence Optimisation: Strategies to Reduce Spend and Eliminate Shelfware

Step 1: Running a Comprehensive Licence Audit

An effective licence audit collects four categories of data from your Salesforce instance. The exercise should take 2-4 weeks depending on organization size and data complexity. Start with login frequency and feature utilisation, which reveal which users actually consume the platform and which functionality they rely on.

Export a login report from your Salesforce administration console covering the past 12 months. Measure login frequency in bands: active daily, 2-4 times per week, monthly, and never (no login in the past 12 months). Users with no login history in the past 12 months are immediate candidates for license removal or downgrade. Users who log in monthly but rarely use transactional features are candidates for Community Cloud or Platform licenses instead of Sales Cloud.

Next, analyze feature adoption by profile and role. Run reports on actual usage of CRM-specific features: opportunity management, forecasting, territory management, advanced approval workflows, and complex customizations. Export this by user profile. You will typically find that 30-40% of users assigned to high-end profiles (Enterprise or Unlimited editions) never use the advanced features those editions unlock.

Cross-reference login data with profile assignment. If a user logs in quarterly but is assigned an Enterprise license with advanced features they do not use, they are a downgrade candidate. Record these findings in a spreadsheet with columns for username, current license, edition, login frequency, primary features used, and recommended license downgrade.

Step 2: Identifying and Quantifying Shelfware

Shelfware—assigned licenses that go unused—represents the largest pool of waste in most Salesforce deployments. Our experience shows that 40% of assigned users are either inactive or chronically underutilized.

Define shelfware in three tiers. Tier 1: No login in the past 12 months. These licenses should be removed immediately. Tier 2: Sporadic login (1-4 times per year) with minimal feature usage. These users likely have legitimate business reasons for access but do not warrant expensive licenses. Tier 3: Regular login but limited feature usage, suggesting they could operate on cheaper license types.

For Tier 1 users, calculate the immediate savings. If you have 50 inactive users at $165/month per Sales Cloud license, that is 50 × $165 × 12 = $99,000 per year in pure waste. Even accounting for a 5% contingency (users who may have legitimate off-cycle needs), you can safely remove or downgrade 95% of Tier 1 users.

For Tier 2 and Tier 3 users, model the financial impact of downgrading them to Platform licenses ($25/month) or Community Cloud licenses ($5/month), depending on their access requirements. A user downgrade from Sales Cloud ($165) to Platform ($25) saves $140 per user per month, or $1,680 per year. Identify all candidates and sum the annual impact.

Step 3: Right-Sizing from Sales Cloud to Platform Licences

The largest opportunity in most organizations is downgrading users from expensive Sales Cloud licenses to cheaper Platform licenses. Sales Cloud costs $165-$330 per user per month depending on edition. Platform licenses cost $25 per month. The differential is $140-$305 per user per month, or $1,680-$3,660 per year per user.

Identify which users truly need Sales Cloud. These include sales representatives who manage opportunities, create and advance deals, and use forecasting. Everyone else—operations staff, finance analysts, customer success managers, administrators, and reporting-only users—should transition to Platform licenses.

The key is understanding what Platform licenses unlock. Platform licenses include access to Salesforce data, custom objects, workflows, approval processes, reporting, and dashboards. They do not include the Sales Cloud CRM features (opportunity management, leads, territories, forecasting). A user who only needs to read opportunity data or generate reports can operate on a Platform license.

Run a query in Salesforce to identify all users who have never created or edited an opportunity in the past 12 months. Cross-reference this against their current license assignment. Anyone with a Sales Cloud license but zero opportunity activity is a downgrade candidate. Be conservative and flag only users with zero CRM activity for downgrade initially; you can expand the criteria in future years.

Step 4: Edition Downgrades and Stratified Licensing Strategy

Beyond switching from Sales Cloud to Platform, consider downgrading users to lower Sales Cloud editions. Sales Cloud comes in three tiers: Professional (typically $85/month), Enterprise ($165/month), and Unlimited ($330/month). Most organizations default to Enterprise or Unlimited but can operate effectively on Professional edition for the majority of users.

Professional edition includes the core CRM features: leads, accounts, opportunities, and territories. Enterprise edition adds advanced features like custom approval workflows, advanced forecasting, and more customization flexibility. Unlimited edition adds the most advanced features and highest API limits.

Conduct a feature inventory. Which users actually rely on advanced approval workflows? How many rely on Einstein AI or advanced forecasting? For most organizations, these are minority use cases. A stratified strategy might look like: 10% of users on Unlimited edition (heavy power users), 40% on Enterprise edition (standard users), 40% on Professional edition (users with moderate needs), and 10% on Platform licenses (reporting and data access only).

Calculate the annual savings. If you downgrade 200 Enterprise edition users ($165/month) to Professional edition ($85/month), that is 200 × ($165-$85) × 12 = $192,000 per year in savings. Combined with other downgrades, a stratified strategy often delivers 15-20% total savings.

Step 5: Rationalizing Add-Ons and Optional Features

Salesforce add-ons—Einstein AI, CPQ, Commerce Cloud, Data Cloud, Shield, and others—generate significant spend that is often misaligned with actual usage. Export your current add-on assignments by user and feature module.

Einstein AI is frequently over-assigned. It might be licensed to 100 users at $50/user/month, but only 20 users actively use Einstein features. Run adoption reports to identify which Einstein modules are actually active (Einstein Analytics, Einstein Search, Einstein Bot, etc.). Remove Einstein assignments from users who have not accessed those features in the past 90 days.

CPQ (Configure Price Quote) is another opportunity. If you assigned CPQ to 50 users but only 5 sales engineers actively use it, consider downgrading the 45 unused licenses. CPQ costs $50-$100 per user per month, so downgrades deliver meaningful savings.

Commerce Cloud is often provisioned for business units that later changed strategy or outsourced the function. Verify that active Commerce Cloud deployments are still generating value. Similarly, Shield is often assigned to all users in regulated industries even though most roles do not require advanced security features. Assign Shield only to roles that handle sensitive data and require field audit trails.

Agentforce and Data Cloud require different treatment because they are consumption-based. Rather than removing them entirely, focus on consumption governance: monitor monthly burn rates, set budgets, and implement controls to prevent overage charges. We discuss this further below.

Step 6: Negotiating the Annual Uplift Cap

Salesforce contracts include an annual uplift clause, typically 8-10%, that automatically increases your license fees each contract year. This compounds dramatically over three-year terms. A $1M annual commitment with an 8% annual uplift costs $1M in Year 1, $1.08M in Year 2, and $1.166M in Year 3—$3.246M total instead of $3M flat.

During renewal negotiations, demand a cap on annual uplift. The industry benchmark is 3-5%, substantially lower than Salesforce's default 8-10%. You have leverage if you have identified 20-30% in optimization opportunities: reducing your spend while improving alignment with business needs demonstrates professional procurement discipline and gives Salesforce motivation to be competitive on renewal terms.

Frame the conversation around True Forward, Salesforce's mechanism for calculating growth costs at renewal. If you have grown user count or consumption since your last renewal, Salesforce charges you for that incremental growth at the new contract rate, which may be 20-30% higher than your original rate. Negotiate for the ability to spread True Forward growth costs over the renewal term rather than taking them all upfront.

Timing matters. Start renewal discussions 120-180 days before your contract end date. This gives you time to complete an audit, model optimization scenarios, and build a negotiation strategy. Salesforce's fiscal year ends January 31, so if your renewal is in Q3 or Q4, you have leverage (Salesforce is motivated to close deals before fiscal year-end). If your renewal is in Q1 or Q2, Salesforce is typically under less time pressure, so your leverage is lower.

Step 7: Managing Consumption-Based Services

Agentforce, Data Cloud, and other consumption-based services require proactive monitoring to prevent surprise overages. Agentforce charges $2 per conversation plus Flex Credits (100K credits = $500). Data Cloud uses a credit-based model. MuleSoft is priced on vCore allocation. All three are prone to overage charges if consumption is not forecasted and monitored.

For Agentforce, forecast conversation volume based on your intended use case. If you plan to deploy AI agents for customer support and expect 10,000 conversations per month, budget $240,000 per year just for Agentforce per-conversation fees. Add Flex Credit consumption on top of that. Many organizations are surprised by the total cost when they model both dimensions.

For Data Cloud, right-size your credit allocation by analyzing your data sources and transformation complexity. Run a pilot to measure actual credit consumption, then forecast annual consumption and set your credit commitment accordingly. Monitor monthly consumption and flag any months where you exceed 80% of your allocation; that is a signal to request additional credits during the next contract negotiation.

For MuleSoft, baseline your current vCore utilization. Many organizations purchase 4 vCores but only use 1.5 consistently. Run load tests during peak traffic periods to determine your actual peak vCore usage, then right-size your allocation to 20-30% above peak. This avoids both performance degradation (under-provisioning) and wasted capacity (over-provisioning).

Step 8: Building a Renewal Strategy and Timeline

A successful optimization programme requires careful orchestration across audit, negotiation, and renewal. Create a project timeline starting 120-180 days before your renewal date.

Days 120-90 before renewal: Complete your licence audit, quantify optimization opportunities, and model financial scenarios. Identify which users should be downgraded, which add-ons should be removed, and what annual uplift cap you will target. Brief your CFO and procurement team on the findings.

Days 90-60 before renewal: Develop your negotiation strategy. Document your cost optimization plan, model the financial impact of each change, and prepare talking points for your conversation with Salesforce. Draft a proposed contract with the license changes and terms you are requesting.

Days 60-30 before renewal: Initiate renewal discussions with Salesforce. Present your optimization findings and proposed new structure. Be clear on what drives your costs down (user downgrades, edition consolidation, add-on rationalization) and what business benefit each decision delivers. Invite Salesforce to propose counter-offers.

Days 30-0 before renewal: Finalize contract terms with Salesforce. Once you have reached agreement on license structure, user count, edition mix, add-ons, and uplift cap, ensure all changes are implemented in the renewal contract. Coordinate with IT to execute license changes in your instance (reassign users to new license types, remove inactive licenses, provision new add-ons, etc.).

Step 9: Implementing License Changes Without Operational Disruption

Downgrading users or removing licenses requires careful coordination to avoid business disruption. Develop a detailed implementation plan and communicate it clearly to stakeholders.

For inactive users (Tier 1): Remove licenses immediately. If a user logs in after license removal, IT can quickly restore access. The risk of operational disruption is minimal because they are already inactive.

For Tier 2 and Tier 3 users: Downgrade licenses in batches aligned to your contract renewal date. Test downgrades with a small cohort first (10-20 users) to verify that Platform or Community licenses meet their access needs. Gather feedback, make adjustments, then roll out in larger batches. Plan the bulk implementation for a date shortly after your contract renewal goes live, when your new license allocation takes effect.

For edition downgrades: These are less disruptive because users retain the same feature set, just at lower tiers. Downgrade in bands aligned to your organization's fiscal calendar or business cycle. Communicate the change to affected users in advance so they understand what is happening and why.

Monitor adoption for 30 days post-implementation. If users encounter unexpected issues or complain about lost functionality, be prepared to reverse specific downgrades. However, most organizations find that downgrades go smoothly because the audit correctly identified users who do not need expensive licenses.

Step 10: Establishing Ongoing Governance and Monitoring

Post-renewal, establish quarterly governance to ensure your optimization gains stick. Create a simple monitoring framework with four elements:

User inventory: Maintain a quarterly count of active, inactive, and downgraded users. Track login frequency and edition assignment. Flag any new users who are onboarded at high license tiers and verify the business justification.

Feature adoption: Run quarterly adoption reports on add-ons (Einstein, CPQ, Commerce, Shield). Remove add-on assignments from users with zero activity in the past 90 days. This prevents add-on creep where over-time more users are assigned features they do not use.

Consumption tracking: For Agentforce, Data Cloud, and MuleSoft, monitor monthly consumption against budget. If you are trending toward overages, alert your Salesforce account team early. Many overages are negotiable if you raise them before month-end.

Cost trending: Track your actual monthly spend against your budgeted renewal cost. Flag any unexpected variances (add-ons being reapplied, users being re-licensed at higher tiers, new consumption-based services being provisioned without approval). Review quarterly with finance and IT.

Schedule a contract business review with Salesforce 6-9 months before your next renewal. Present your year-to-date optimization results, discuss any business changes (headcount growth, new use cases), and jointly forecast next renewal costs. This keeps Salesforce engaged and aware of your commitment to cost discipline, which typically translates to better renewal pricing.

Timeline to Results: Expect Quick Wins

A well-executed optimisation programme delivers results in phases. Removing Tier 1 (inactive) users typically generates immediate savings with no business risk. This can be done within 30-60 days and often saves 5-10% of your total Salesforce spend.

User downgrades and edition consolidation follow after you have validated that downgraded users do not need expensive licenses. Plan 60-90 days to complete downgrades across your organization. This phase typically yields 10-15% additional savings.

Add-on rationalization and uplift cap negotiation are tied to contract renewal. These are completed as part of your renewal cycle and lock in 5-10% additional savings plus a better renewal rate (lower uplift cap). Total reductions from all four dimensions typically reach 20-30%.

Conclusion: Taking Ownership of Salesforce Costs

Salesforce cost optimization is not mysterious or risky. It is a systematic, methodical discipline that every large-scale Salesforce customer should practice. Most organizations have 20-30% in optimization opportunity simply sitting on the table, captured by a audit and a focused negotiation effort.

The steps outlined in this guide—auditing usage, identifying shelfware, right-sizing licenses, rationalizing add-ons, negotiating uplift caps, and managing consumption—are all within your control. You do not need external consultants or vendors to execute them, though expert guidance accelerates results and ensures you do not miss opportunities.

The key is starting early (120-180 days before renewal), being methodical, and treating licence optimization as an ongoing discipline rather than a one-time exercise. Organizations that do typically reduce spend by 20-30% within the first renewal cycle and maintain those gains indefinitely.