Shelfware is one of those words that sounds politely technical but describes something that is genuinely painful once you calculate the numbers. It refers to software that has been licensed, paid for, and left largely or entirely unused. In the enterprise software world, shelfware is not an edge case. Research consistently shows that large organisations are actively using a fraction of the software they are paying for, and the cost of that unused capability runs into significant figures every year.
Salesforce is one of the most common sources of enterprise shelfware, and that is not because the platform lacks value. It is because Salesforce has grown into one of the most expansive and modular enterprise platforms in existence. Sales Cloud, Service Cloud, Marketing Cloud, Data Cloud, Revenue Cloud, Experience Cloud, Einstein features, Agentforce, MuleSoft, Slack, and a growing library of add-ons and industry-specific products mean that most large organisations have licensed significantly more Salesforce capability than their teams are actively using at any point in time.
This blog looks directly at the shelfware problem in Salesforce. Not in the abstract, but in the specific, practical ways it shows up in real enterprise deployments. We will talk about what shelfware actually costs, where it comes from, and what organisations can do to close the gap between what they are paying for and what they are getting value from.
What Salesforce Shelfware Actually Costs
The cost calculation for Salesforce shelfware is more than the headline licence fee divided by the number of active users. It includes the support costs that run regardless of usage, the implementation investment that was made to configure features that nobody adopted, the internal IT and admin resource that maintains systems and workflows that the business no longer actively relies on, and the opportunity cost of budget that could have been redirected to higher-value investments.
For a large enterprise running a complex Salesforce estate, those costs add up quickly. An organisation paying for two hundred Salesforce Enterprise Edition licences where eighty of those users log in fewer than five times a month has not just over-licensed. It has funded the full implementation and ongoing support of a CRM environment for a population of users who have effectively checked out of the system. The commercial waste is real whether it shows up as a single line item or not.
Flexera’s annual State of Tech Spend report consistently documents that enterprise organisations are actively using between fifty and sixty percent of the SaaS capabilities they pay for. Their Flexera State of Tech Spend and SaaS utilisation research provides benchmarking data that helps organisations understand whether their Salesforce utilisation gap is typical or significantly worse than the market average, and what financial impact closing that gap could have.
The shelfware problem is often invisible until someone looks for it. Finance sees a Salesforce line item on the technology budget and assumes the business is getting value because it is a large, well-known platform. IT sees the system running without technical issues and assumes everything is fine. It is only when someone actually maps which features are being used, by which users, at what frequency, that the true picture emerges. And that picture, in most large Salesforce environments, contains meaningful waste.
Where Salesforce Shelfware Comes From
Understanding the source of shelfware is important because different causes require different fixes. The most common origins of unused Salesforce capability fall into three categories.
Features Licensed Before the Business Was Ready
This is perhaps the most common. An organisation negotiates a Salesforce deal that includes capabilities beyond what it currently needs, either because the vendor has positioned them as part of a bundle, because the procurement team wanted to future-proof the investment, or because someone in the business requested a feature during the buying process that never actually got deployed. Three years later, the licences are renewing at full price for a capability set that the organisation has never fully activated.
Products Added for Specific Projects That Did Not Scale
Salesforce is often expanded in response to specific business initiatives. A new product launch, a customer service transformation programme, a digital marketing overhaul. These initiatives drive licence and product additions that are sized for the ambition of the project at the time. When the project scales back, when leadership changes, or when the initiative delivers less than expected, the Salesforce footprint it created often does not scale back with it. The licences stay, the features stay active, and the cost continues even though the business need that justified it has changed.
Adoption That Never Happened
The third and most common source of shelfware is features that were enabled but never adopted. Einstein AI features switched on but not embedded in any workflow. Industry-specific components configured during implementation but never used in practice. Add-on products purchased on the strength of a vendor demonstration that did not translate into genuine operational use once the project team moved on. Each of these represents a gap between the capability the organisation is paying for and the value it is extracting.
Gartner research on software asset management identifies low feature adoption as the single largest contributor to unnecessary SaaS spend across enterprise software portfolios. Their Gartner software asset management and SaaS optimisation research document the adoption patterns that create shelfware in platforms like Salesforce, along with the governance practices that the most commercially disciplined organisations use to prevent unused features from accumulating over time.
The Features Most Likely to Be Shelfware in Your Salesforce Estate
While every organisation is different, there are feature categories that appear as shelfware more often than others across enterprise Salesforce deployments. Einstein AI scoring and prediction features are frequently activated during implementation but not consistently used by sales or service teams, either because the data quality was not sufficient to make the predictions useful or because no one embedded the scores into actual workflows and management conversations.
Marketing Cloud modules, particularly advanced features like Interaction Studio or the more sophisticated Journey Builder configurations, are often licensed at a scale that reflects marketing ambitions at the time of purchase rather than actual campaign complexity. The simpler use cases that most marketing teams run do not require the full capability set they are paying for.
Salesforce Communities and Experience Cloud portals are another common shelfware category. Building a customer or partner portal requires significant investment in design, development, and content management. Many organisations license the capability, begin an implementation, and then scale back when the complexity becomes apparent or the business priority shifts. The licence stays active while the portal sits incomplete or underused.
How to Actually Find the Shelfware in Your Environment
Identifying shelfware requires looking at three things: what your licences include, what is actually activated, and what is genuinely used. The gap between all three levels is where you find the cost you can recover.
The licence audit starts with pulling a complete picture of every Salesforce product and feature included in your current agreements, including all add-ons, all edition-specific capabilities, and all Einstein and AI features. For most organisations, this exercise alone surfaces capabilities they had forgotten they were paying for.
The activation audit looks at which of those licensed features are actually switched on in your Salesforce configuration. Features can be licensed but never configured. Finding those gaps identifies things that could be downgraded or removed at renewal without any operational impact.
The usage audit goes deeper, looking at user login frequency, feature interaction rates, and data completeness in the areas of the system that are supposed to be driving value. Low login rates, high feature non-interaction, and poor data quality in key fields are all signals of shelfware in practice even when the feature is technically activated.
Salesforce Ben publishes practical guidance on Salesforce licence optimisation and cost reduction that walks through the specific admin processes and reports organisations can use to identify and address shelfware in their Salesforce environments. Their Salesforce Ben licence cost reduction and utilisation guidance provides the hands-on technical perspective that complements the commercial analysis, giving Salesforce admins and IT managers practical tools for building their own shelfware audit.
What to Do With What You Find
Once the shelfware audit is complete, the commercial response depends on where you are in the contract cycle. Mid-contract, the options are limited in terms of immediate cost reduction because most Salesforce agreements lock user counts and product scope until renewal. But the audit findings are not wasted. They become the evidence base for the renewal negotiation, where the organisation can argue for a right-sized commercial structure based on actual utilisation rather than historical assumptions.
At renewal, the leverage is significant. An organisation that arrives at the Salesforce renewal table with clear utilisation data showing which features are used at what level, which users are active versus dormant, and which products are genuinely delivering value has a compelling commercial case for a restructured deal. The alternative, renewing without that data, means accepting a structure that is likely to carry the same shelfware forward for another three years.
MIT Sloan Management Review research on technology value realisation documents how enterprises that conduct regular software utilisation reviews consistently achieve better commercial outcomes from their platform investments than those that renew on autopilot. Their MIT Sloan technology investment and value realisation research provide evidence-based frameworks for connecting software utilisation analysis to commercial decision-making that directly applies to the Salesforce renewal conversation.
The Governance That Prevents Shelfware Building Up Again
A shelfware audit is not a one-time fix. Without governance changes, the same patterns will re-emerge within a few years. The governance practices that prevent shelfware from accumulating are not complex but they do require deliberate implementation. User licence reviews on a quarterly basis that identify inactive users and reallocate or remove their licences. A formal approval process for any new Salesforce product or feature addition that includes an adoption plan and a utilisation target before the commercial commitment is made. Renewal preparation that starts at least six months before the contract end and is built on current utilisation data rather than assumptions.
These are not expensive disciplines. They are, largely, a matter of making Salesforce commercial management a deliberate ongoing responsibility rather than something that only gets attention when a renewal invoice arrives. The organisations that do this consistently find that their Salesforce investment delivers substantially more value per pound spent than those that do not.
Conclusion
Salesforce shelfware is one of the most straightforward and recoverable sources of unnecessary technology spend in most large organisations. The capability is already there. The licences are already paid for. The cost of the shelfware is already embedded in the budget. What is needed is the willingness to look, the discipline to measure, and the commercial preparation to act on what you find at renewal. The organisations that do this are not spending less on Salesforce because they have less. They are spending more wisely because they know exactly what they have and what it is worth.
