Shelfware is the polite name for the most common—and most consequential—Salesforce overspend pattern: licenses that are paid for and not used. Across the engagements we observe, the median enterprise Salesforce footprint carries 18-32% shelfware at any given renewal moment, with the distribution heavily concentrated in three product surfaces (Sales Cloud, Service Cloud, and high-margin add-ons like Inbox, Maps, and CPQ) and in three operational populations (offboarded users still provisioned, users provisioned to populations that never adopted, and users provisioned at an over-tiered edition relative to their operational requirement). The shelfware does not surface because the operational reporting is not in place to surface it; the dashboard template below puts that reporting in place.
This article defines the operational reporting that surfaces Salesforce shelfware, with the specific metrics, the thresholds, the cadence, and the operational handoff that converts the reporting into renewal leverage. The framing is vendor-neutral and buyer-side. The dashboard template is product-agnostic—it applies to Sales Cloud, Service Cloud, Marketing Cloud, Data Cloud, Tableau, Slack, MuleSoft, and the broader Salesforce footprint—with product-specific variations noted where the operational signal differs by surface.
The four core dashboard metrics
The shelfware dashboard is structured around four core metrics—the metrics that, taken together, surface every meaningful shelfware pattern across the Salesforce footprint. The metrics are operationally derived from the Salesforce login history, the user-record metadata, and the entitled-license inventory. The dashboard refreshes weekly, with the trailing-90-day window as the operational lens.
1. Provisioned-to-active ratio
The provisioned-to-active ratio is the ratio of provisioned users (users with active assigned licenses) to active users (users who have logged in at least once in the trailing 90 days). The ratio is calculated per product, per edition, and per role population, with the aggregate ratio reported across the broader footprint. A healthy ratio is at or above 0.85—at least 85% of provisioned users are logging in monthly. A ratio below 0.70 indicates material shelfware exposure; a ratio below 0.55 indicates a shelfware crisis.
2. Active-but-dormant user count
The active-but-dormant user count captures users who are technically active (have logged in at least once in the trailing 90 days) but whose engagement intensity is below the operational threshold for the assigned license tier. The threshold varies by product: for Sales Cloud Enterprise, the dormancy threshold is fewer than 4 logins per month; for Service Cloud, fewer than 8 logins per month; for high-margin add-ons like Inbox or Maps, fewer than 2 sessions per month. The active-but-dormant population is the most consequential shelfware category because the users are technically active and therefore frequently overlooked in the standard usage review.
3. Edition-to-utilization mismatch
The edition-to-utilization mismatch surfaces users provisioned at an edition tier above their operational utilization. The metric compares the entitled edition (Enterprise, Unlimited, Performance) against the operational feature utilization across the trailing 90 days. A user provisioned at Unlimited who uses only Enterprise-tier features is a candidate for edition down-tier at the next renewal moment, capturing the per-user delta between Unlimited ($330 PEPM) and Enterprise ($165 PEPM)—a $1,980 per-user annual recovery without operational impact.
4. Add-on utilization rate
The add-on utilization rate captures the per-user adoption of entitled add-ons—Inbox, Maps, CPQ, Einstein Activity Capture, Sales Engagement, Service Cloud Voice, and the broader add-on portfolio. The metric is calculated per add-on, per provisioned user, with the utilization threshold typically set at 50% (the user accessed the add-on capability in at least half the trailing 90-day window). The add-on utilization rate consistently surfaces the highest-margin reclamation candidates because the add-on per-user pricing is materially higher than the base license pricing—the per-user delta on an unused Einstein Activity Capture add-on is $300 PEPM (~$3,600 annually).
| Metric | Healthy threshold | Crisis threshold |
|---|---|---|
| Provisioned-to-active ratio | > 0.85 | < 0.55 |
| Active-but-dormant rate | < 12% | > 30% |
| Edition mismatch (Unlimited > Enterprise) | < 15% | > 35% |
| Add-on utilization (Inbox, Maps) | > 60% | < 30% |
| Add-on utilization (Einstein add-ons) | > 50% | < 25% |
The operational drill-down dimensions
Each of the four core metrics drills down across four operational dimensions—the dimensions that, taken together, locate the reclamation candidates with operational precision.
By role population
The role population dimension surfaces shelfware concentrated in specific role populations—frequently the populations that received Salesforce as part of a broad organizational rollout but never adopted the capability operationally. Field service technicians provisioned at Service Cloud who never log in. Inside sales representatives provisioned at Sales Cloud Inbox who never access email integration. Marketing operations users provisioned at Marketing Cloud Engagement who never compose campaigns. The role-population drill-down localizes the reclamation candidates to specific organizational populations where the reclamation conversation can be operationally grounded.
By manager or business unit
The manager or business unit dimension surfaces shelfware concentrated in specific organizational reporting lines, supporting the chargeback or showback model that converts the shelfware reporting into operational accountability. A business unit with a 38% dormancy rate is a different reclamation conversation than a business unit with a 12% dormancy rate, and the manager-level drill-down supports the targeted reclamation engagement rather than a blanket reclamation push.
By geography
The geography dimension surfaces shelfware concentrated in specific geographic populations—frequently the populations that received Salesforce as part of a global rollout but never adopted at the local operational level. The geography drill-down supports the geo-specific reclamation conversation and surfaces the operational variation across the global footprint.
By tenure
The tenure dimension surfaces shelfware concentrated in long-tenured users (frequently the users whose role responsibilities have shifted away from the assigned product surface) and in short-tenured users (frequently the users whose onboarding never completed at the assigned product surface). The tenure drill-down supports the lifecycle-aware reclamation conversation rather than a tenure-blind reclamation push.
The operational cadence
The dashboard refreshes weekly, with the trailing-90-day window as the operational lens. The weekly refresh supports the operational tracking of the reclamation pipeline and surfaces the new dormancy events as they emerge. The quarterly review—conducted at the leadership level—aggregates the trailing quarter into a reclamation plan for the next 90 days, with specific population, manager, geography, and tenure targets. The pre-renewal review—conducted 120-90 days before the renewal date—aggregates the trailing year into the renewal-side reclamation plan, with the specific seat counts, edition mismatches, and add-on reclamation candidates identified for the renewal negotiation. The renewal commercial outcome is materially shaped by the quality of the pre-renewal reclamation plan.
The handoff to renewal negotiation
The dashboard's commercial value is realized at the handoff to renewal negotiation. The pre-renewal reclamation plan should specify: the seat counts that are candidates for scope-down (with role, manager, geography, and tenure dimensions documented); the edition mismatches that are candidates for edition down-tier; the add-on reclamation candidates with the per-user delta and the annual recovery calculation; the role-population reassignments that should be coordinated with the scope-down (e.g., from full Sales Cloud to Sales Cloud Lightning Login or to External Identity); and the operational signoff from the manager populations on each reclamation candidate, supporting the credibility of the scope-down position in the renewal conversation. The dashboard converts the abstract "we have shelfware" position into the specific reclamation plan that the renewal negotiation can be built around.
The technical implementation
The dashboard is technically implemented against three data sources: the Salesforce User object (the entitled-license inventory and provisioning metadata), the Salesforce LoginHistory object (the active-versus-dormant operational signal), and the Salesforce EventLogFile (the feature-level utilization signal for add-on and edition-mismatch analysis). The implementation can be native (Salesforce reports, dashboards, or CRM Analytics) or external (a BI tool, a data warehouse, or a custom application against the Salesforce APIs). The native implementation has the advantage of zero-data-egress and zero-integration-overhead; the external implementation has the advantage of broader analytical flexibility and cross-system reporting. For most enterprise footprints, the native implementation is sufficient for the operational reporting, with external implementation reserved for the broader cross-system reporting use case.
The product-specific variations
The dashboard template is product-agnostic in its structure, but each product surface has specific operational signal that warrants product-specific dashboard variations. Sales Cloud dashboards should add the opportunity-touch metric (the number of opportunities the user has touched in the trailing 90 days), which surfaces the active-but-dormant Sales Cloud population. Service Cloud dashboards should add the case-resolution metric, which surfaces the active-but-dormant Service Cloud population. Marketing Cloud dashboards should add the send-volume and campaign-creation metrics, surfacing the active-but-dormant Marketing Cloud population. Data Cloud dashboards should add the credit-consumption-per-user metric, surfacing the over-provisioned Data Cloud user populations. Tableau dashboards should add the view-and-author metric, distinguishing the Tableau Explorer from the Tableau Creator utilization profile. Slack dashboards should add the active-channel-membership and message-volume metrics, surfacing the dormant Slack populations.
Benchmark outcomes by deployment scale
For a mid-market customer with a $1M-$5M annual Salesforce footprint, the disciplined shelfware dashboard typically surfaces $200K-$1.4M in annualized reclamation candidates, capturing 20-30% reductions at the next renewal moment. For a large-enterprise customer with a $20M-$80M annual Salesforce footprint, the disciplined dashboard typically surfaces $4M-$24M in annualized reclamation candidates, capturing 20-35% reductions at the next renewal moment. The proportional outcomes consistently scale with the broader footprint and the underlying shelfware concentration.
Where to begin
The most useful first step is the trailing-90-day operational baseline—the provisioned-to-active ratio, the active-but-dormant rate, the edition mismatch rate, and the add-on utilization rate, calculated against the current entitled license inventory and the current operational utilization. The baseline establishes the starting point for the dashboard implementation and surfaces the immediate reclamation candidates that should be prioritized at the next renewal moment. The dashboard implementation follows the baseline, with the weekly refresh cadence and the quarterly leadership review establishing the operational rhythm that converts the shelfware reporting into renewal leverage.
The strategic frame
The shelfware dashboard is the operational backbone of the disciplined Salesforce commercial commitment. The dashboard converts the abstract "we should optimize" position into the specific reclamation plan that the renewal negotiation can be built around, with operational signoff, manager-level accountability, and pre-renewal reclamation plan that captures 20-40% reductions at the next renewal moment. Customers who treat the shelfware dashboard as a strategic operational asset—with the weekly refresh, the quarterly review, the pre-renewal reclamation planning, and the disciplined handoff to the renewal conversation—consistently capture material commercial outcomes that customers without the dashboard reporting cannot capture.