License utilization analysis is the structured discipline that surfaces shelfware, identifies tier mismatches, and produces the data foundation for renewal negotiation. Unlike a one-time shelfware audit, license utilization analysis is an ongoing practice that tracks adoption, feature usage, and license efficiency continuously. The organizations that consistently produce the strongest Salesforce renewal outcomes are typically the organizations with mature utilization analysis discipline. This guide walks through how to build that discipline: the metrics, the tooling, the cadence, and the analytical framework that surfaces actionable findings on the 2026 Salesforce platform.
What license utilization analysis covers
The utilization analysis covers several dimensions:
Active versus inactive users. The most basic metric — what percentage of provisioned users log in within defined windows. The active-user ratio is the headline indicator of license health.
Feature usage patterns. Beyond login activity, what features each user actually exercises. The feature usage indicates whether users are exercising the capabilities that justify their license tier.
Adoption depth. How deeply users engage with the platform — viewing dashboards versus authoring reports versus building automations versus configuring metadata. The depth indicates the user’s actual functional role.
Time-on-platform. Session duration, frequency, and pattern data that indicates the user’s engagement intensity.
Workflow execution. The actual transactions performed in the platform — opportunities created and edited, cases worked, leads processed, custom object records managed.
API and integration usage. Beyond UI usage, the API call patterns from integrated systems that consume Salesforce data and capabilities.
License tier appropriateness. The mapping of user functional patterns to license tier requirements, identifying mismatches.
The key utilization metrics
| Metric | What it measures | Target range |
|---|---|---|
| 30-day active ratio | % of provisioned users logged in in last 30 days | >75% healthy, <60% concerning |
| 90-day active ratio | % of provisioned users logged in in last 90 days | >90% healthy, <80% concerning |
| Tier appropriateness | % of users on the correct license tier for usage | >85% healthy |
| Feature exercise rate | % of provisioned features actually used | Varies; >60% healthy |
| Median session count | Sessions per active user per month | >10 for primary users |
| Adoption velocity | New-feature adoption rate after release | >50% adoption within 90 days for relevant populations |
The target ranges are starting points; the appropriate targets depend on the deployment context. A customer-facing portal with low expected login frequency has different targets than an internal sales-team deployment with daily-user expectations.
Building the utilization data foundation
The utilization analysis depends on solid data foundations. The key components:
User activity data
Login history, session data, page views, and click tracking. The data is available natively in Salesforce (Login History, with more detail through Event Monitoring) and through third-party adoption analytics tools.
Feature usage data
Specific feature exercise patterns. Some features have native logging; others require Event Monitoring or custom instrumentation.
Workflow transaction data
Records created, modified, and viewed. Standard Salesforce reporting provides much of this data through custom report types and field history tracking.
Provisioning data
Which users have which licenses, when they were provisioned, what role they hold, what business unit they belong to. The provisioning data joins to the activity data to produce population-segmented analyses.
Cost data
The pricing for each license type at the customer’s negotiated rates. The cost data converts utilization findings into economic findings.
The analysis cadence that works
The utilization analysis should run on a structured cadence:
Monthly: Adoption monitoring. Track active-user ratios, key feature usage, and adoption velocity for new features. The monthly cadence surfaces emerging issues quickly.
Quarterly: Tier-mix review. Refresh the tier-appropriateness analysis quarterly. Identify populations that may warrant tier reassignment.
Annually: Comprehensive utilization audit. The deep annual audit covers the full set of metrics, identifies structural issues, and feeds into the renewal preparation.
Renewal-cycle: Targeted analysis. The 6-month-before-renewal analysis specifically structured to support the renewal conversation, with detail on shelfware identification, tier optimization opportunities, and contract restructuring options.
Ad hoc: Project-driven analysis. Specific projects (M&A integration, departmental restructuring, technology consolidation) may warrant targeted analyses outside the regular cadence.
The tooling options
The utilization analysis can be performed with several tooling approaches:
Native Salesforce reporting. Custom report types, dashboards, and ad-hoc reports against Login History, Setup Audit Trail, and Field History tables. Free with Salesforce CRM licenses but requires manual analysis and limited cross-org visibility.
Salesforce Adoption Analytics. Where available, the native Adoption Analytics provides pre-built reporting on adoption patterns. Useful for first-cycle analysis but may not scale to mature deployments.
Event Monitoring. The Event Monitoring add-on provides detailed user activity data that supports deeper analysis. Required for the most sophisticated utilization work.
CRM Analytics. The Salesforce-native analytics platform can support utilization dashboards with pre-built datasets and visualizations.
Third-party adoption tools. Various third-party tools specialize in Salesforce adoption analytics, providing pre-built reporting and benchmarks. The cost and value vary; the tools often justify themselves for large deployments.
Custom analytics stacks. Some organizations export Salesforce usage data into broader analytics platforms (Snowflake, Databricks, custom data warehouses) for unified analysis with other systems. The approach is powerful but requires data engineering investment.
Common analytical findings
Across the 500-plus engagements our advisory has supported, the utilization analyses consistently surface several patterns:
Tail of low-activity users. A typical deployment has a substantial tail of provisioned users with very low activity — the bottom 15–25 percent of users by activity producing meaningful shelfware exposure.
Tier ceiling underutilization. Users on Enterprise or Unlimited editions who use only Professional-tier features represent tier-mismatch opportunities, often substantial in aggregate dollar terms.
Feature underutilization. Specific features (forecasting, territory management, advanced analytics, AI capabilities) are often licensed broadly but used narrowly. The opportunities to restructure are substantial.
Departmental variation. Different departments often show dramatically different adoption patterns. The findings can support department-specific license strategies rather than uniform organization-wide licensing.
Role-based mismatches. Specific roles (often executive roles, occasional users, intermittent users) frequently sit on inappropriate license tiers. The role-based audit produces actionable findings.
Time-of-day and seasonal patterns. Some user populations show usage concentrated in specific periods (month-end, quarter-end, season-specific). The patterns can inform license strategy — for instance, temporary license arrangements for seasonal peaks rather than year-round capacity.
Translating findings into action
The utilization analysis is only valuable if it produces action. The action categories:
Deprovisioning. Inactive users should be deprovisioned to free up licenses for reuse or for non-renewal at the next cycle.
Tier reassignment. Users on inappropriate tiers should be moved to the right tier — at renewal for downgrades, immediately if upgrades are needed for business workflows.
Training intervention. Low-adoption findings sometimes indicate training needs rather than over-licensing. Targeted training can convert low-adoption populations into actual users.
Feature rationalization. Features that are licensed but underused may not justify the license tier; the decision is whether to invest in adoption or to retier.
Process redesign. Some utilization findings reflect process issues rather than licensing issues. The Salesforce platform is licensed appropriately, but the business process does not effectively leverage it. The fix is process redesign, not licensing changes.
Renewal restructuring. The cumulative findings shape the renewal conversation. The structural changes (license count reductions, tier rebalancing, contract restructuring) happen at renewal.
The maturity model
License utilization analysis maturity evolves over multiple cycles:
Level 1: Ad hoc. Utilization analysis happens only when prompted (often by renewal). Findings are reactive and often incomplete.
Level 2: Annual. Annual structured audit produces findings that feed into renewal. Useful but limited in scope.
Level 3: Quarterly. Quarterly structured analysis with action plans. The cadence catches issues earlier and produces sustained improvement.
Level 4: Continuous. Monthly monitoring with quarterly action cycles and annual deep audits. The integrated discipline produces continuous improvement and the strongest renewal outcomes.
Level 5: Predictive. The mature discipline uses predictive analytics to anticipate adoption challenges, identify emerging shelfware, and proactively shape license strategy. Rare but produces the most sophisticated outcomes.
Most organizations operate at Level 1 or 2. The advancement to Level 3 or higher requires investment in tooling, process, and analytical capability, but the returns are typically substantial — particularly for large deployments where the absolute savings opportunities are large.
What to verify in the utilization analysis
- The data sources cover all material activity dimensions (login, feature usage, transactions).
- The metrics reflect the deployment context appropriately.
- The analysis cadence matches the deployment scale and the strategic value.
- The findings are validated with business leaders before action.
- The action plans have clear ownership and timelines.
- The renewal-cycle preparation uses the utilization findings as the foundation.
- The continuous improvement compounds savings across cycles rather than producing one-time benefits.
License utilization analysis is the discipline that converts visibility into value. The $420 million in cumulative savings our advisory has delivered across 500-plus engagements has been built on rigorous utilization analysis — without that foundation, the negotiation conversations have less substantive material to work with. The 34 percent average reduction we secure against opening Salesforce positions is consistently strongest for customers with mature utilization disciplines, where the data foundation supports specific, defensible negotiation positions rather than general assertions.
For most organizations, the path to mature utilization discipline involves incremental investment in tooling and process, with sustained returns that compound across renewal cycles. The discipline pays for itself in the first cycle for most large deployments and produces accelerating returns thereafter.
The benchmarking dimensions
License utilization analysis is more valuable when benchmarked against patterns from other deployments. The benchmarking dimensions:
Active-user ratios by industry. Different industries have different healthy active-user ratios. Healthcare deployments often run lower active ratios than financial services. Manufacturing deployments often have different patterns than retail.
Tier-mix patterns by company size. Mid-market companies often have different tier-mix patterns than enterprises. The patterns can inform the right-sizing analysis.
Feature adoption velocity. Different features have different typical adoption velocity. AI features have different adoption patterns than core CRM features. The patterns help calibrate expectations.
Productivity benchmarks. Sessions per user, records created per user, cases closed per user. The benchmarks help identify high-performing and low-performing populations.
Engagement depth benchmarks. The distribution of users between casual viewers, regular workers, and power users typically follows patterns that can be benchmarked.
The benchmarking should be used as a calibration tool rather than as a target — each deployment has unique characteristics, but the benchmarks help identify outliers that warrant investigation.
The adoption playbooks that drive utilization
Beyond the measurement discipline, organizations that produce strong utilization often have structured adoption playbooks. The playbook elements:
Onboarding journeys. Structured onboarding for new users that drives early adoption of the relevant capabilities.
Role-based training. Training programs tailored to specific user populations rather than generic platform training.
Adoption metrics in performance reviews. Including Salesforce adoption metrics in manager-level performance conversations creates accountability for usage.
Champion programs. Identifying and developing power users who advocate for adoption within their teams.
Feedback loops. Structured feedback mechanisms that surface adoption barriers and inform platform investment decisions.
Continuous improvement cycles. Regular review of adoption data with structured action plans to address identified issues.
The adoption discipline is the offensive counterpart to the shelfware-identification defense. Strong adoption discipline reduces the shelfware exposure structurally, while the shelfware analysis catches the residual exposure that adoption efforts did not eliminate.
The integration of utilization analysis with broader IT governance
License utilization analysis works best when integrated with broader IT governance practices:
Identity governance. The user provisioning and deprovisioning workflows should connect to identity governance systems so that role changes and departures automatically affect license assignments.
Access management. Periodic access reviews should incorporate license-tier appropriateness alongside data access reviews.
Cost allocation. Salesforce license costs should be allocated to consuming business units, creating visibility into the cost of usage by population.
Vendor management. Salesforce utilization findings should feed into the broader vendor management framework alongside other enterprise software utilization.
Procurement integration. The procurement team should have visibility into utilization findings to support the renewal preparation.
The integrated discipline produces stronger outcomes than the standalone utilization analysis because it leverages the existing governance infrastructure rather than building a separate Salesforce-specific practice.
The cost-of-discipline considerations
The utilization analysis discipline has its own cost — the tooling, the staffing, the time investment. For most large Salesforce deployments, the cost is justified by the savings opportunities, but the cost-benefit analysis should be explicit:
- Small deployments (under $250K annual Salesforce spend) may not justify a dedicated utilization analysis function
- Mid-size deployments ($250K–$2M annual spend) typically benefit from quarterly analysis with modest tooling investment
- Large deployments ($2M+ annual spend) typically justify continuous monitoring with substantial tooling and dedicated staffing
- Very large deployments ($10M+ annual spend) typically support sophisticated utilization analytics with predictive capabilities
The investment scales with the deployment, and the returns scale accordingly. The discipline of right-sizing the utilization analysis investment to the deployment scale is part of the broader optimization conversation.