📘 This case study is part of the ServiceNow Knowledge Hub — covering licensing models, renewal strategies, pricing benchmarks, and optimisation best practices for enterprise ServiceNow deployments. For licensing fundamentals, see ServiceNow Licensing Types. For renewal strategy, see ServiceNow Renewal: Complete Guide.
Executive Summary
A Fortune 500 pharmaceutical company headquartered in New Jersey — with approximately 45,000 employees, 80+ manufacturing and R&D sites worldwide, and annual revenues exceeding $18 billion — had built a substantial ServiceNow estate over seven years. What began as an IT Service Management deployment had expanded organically to include Security Operations (SecOps), HR Service Delivery (HRSD), IT Operations Management (ITOM), and Software Asset Management (SAM), with total annual spend reaching $3.2M ($9.6M over the three-year contract term).
Seven years of organic growth had created a licensing estate that no longer reflected operational reality. Fulfiller licenses had been provisioned for projects that were completed, for contractors who had departed, and for employees who had changed roles. Two modules were running at Enterprise tier when the features actually in use were available at Professional tier. ITOM and SecOps subscriptions had been sized for ambitious deployment plans that had only been partially realised.
The company's IT Asset Management team knew there was waste but lacked the ServiceNow-specific licensing expertise and benchmarking data to quantify it precisely or determine what could be safely eliminated. They engaged Redress Compliance to conduct a full license right-sizing exercise — an independent, line-by-line analysis of every ServiceNow entitlement against actual usage.
The result: $1.2M in annualised savings — achieved entirely through optimisation, with zero reduction in the company's ServiceNow capabilities. Every module, every workflow, and every integration the company was actively using remained fully operational.
340 Fulfiller Licenses Eliminated
Detailed user-by-user analysis identified 340 named fulfillers who had not logged in for 90+ days, had changed roles, or were duplicate accounts from contractor rotations.
2 Module Tier Downgrades
ITSM and HRSD were running at Enterprise tier. Feature usage analysis confirmed Professional tier covered 100% of active functionality.
ITOM and SecOps Right-Sized
Subscription units for ITOM Discovery and SecOps were reduced to match actual infrastructure scope and security event volumes.
Zero Operational Impact
Every active workflow, integration, dashboard, and user remained fully functional. Savings came entirely from waste elimination.
Background and Context
The Company's ServiceNow Estate
The pharmaceutical company's ServiceNow deployment was one of the more complex estates Redress has assessed. Over seven years, the platform had become deeply embedded in the organisation's operations, supporting critical processes across IT, security, HR, and compliance.
| Module | Scope | Fulfillers | Key Details |
|---|---|---|---|
| ITSM Enterprise | Global IT operations | 1,400 | Incident, Problem, Change, Release, Asset Management. Foundation of the estate supporting service desk agents, infrastructure engineers, application support, change managers. |
| Security Operations (SecOps) | Security incident and vulnerability management | 150 | Integrated with Splunk (SIEM), Qualys and Tenable (vulnerability scanners), threat intelligence feeds. Licensed for defined monthly security event volume. |
| HR Service Delivery (HRSD) Enterprise | Employee lifecycle | 85 | Onboarding, HR case management, benefits enquiries, policy acknowledgements. Licensed for 42,000 employees. |
| IT Operations Management (ITOM) | Hybrid infrastructure discovery | — | Discovery and Service Mapping across on-premises data centres, AWS, and Azure. Licensed for 15,000 discoverable nodes. |
| Software Asset Management (SAM) | Licence reconciliation | — | Managing Oracle, Microsoft, SAP, and other major vendor licences across the enterprise. |
The estate had been built by different teams at different times, each with their own business case and procurement negotiation. The result was a patchwork of SKUs, metrics, discount levels, and co-termination dates that made it extremely difficult to understand the true cost structure or identify optimisation opportunities.
Why License Right-Sizing Matters
ServiceNow's licensing model creates specific dynamics that make right-sizing both important and challenging. Fulfiller licenses are named — meaning each individual user requires their own licence, and unused licenses cannot be reassigned without a formal true-up process. Module tiers (Standard, Professional, Enterprise) carry significantly different price points, but the feature differences between tiers are often poorly understood by customers. Consumption-based metrics (ITOM nodes, SecOps events) are frequently over-provisioned at initial purchase because deployments rarely reach their projected scope on schedule.
For a deeper understanding of how ServiceNow structures its licensing, see the comprehensive guide on ServiceNow Licensing Types and Best Practices for ITAM Professionals.
Industry benchmark: In Redress's experience, 20 to 35% of enterprise ServiceNow spend is allocated to unused or underutilised entitlements. The waste is not the result of poor management — it is the inevitable outcome of a licensing model that charges for capacity rather than consumption, in an environment where usage patterns change continuously.
The Challenges
Fulfiller License Sprawl
The company had 1,400 ITSM fulfillers, 150 SecOps fulfillers, and 85 HRSD fulfillers licensed across the estate. Over seven years, these numbers had only ever gone up. When new team members joined, licenses were provisioned. When contractors arrived, licenses were provisioned. When employees moved into roles requiring ServiceNow access, licenses were provisioned. But the reverse process — deprovisioning licenses when people left, changed roles, or completed projects — was inconsistent at best. The ITAM team suspected there were hundreds of unused licenses but had no systematic way to confirm this without risking deactivating someone who still needed access.
Enterprise Tier Licensing Without Enterprise Tier Usage
Both ITSM and HRSD had been licensed at Enterprise tier — the most expensive option. The original business cases identified specific Enterprise features as requirements: Predictive Intelligence and Performance Analytics for ITSM, and Employee Journey Management and Advanced Workforce Analytics for HRSD. However, these features had either never been fully deployed, had been trialled and abandoned, or were being used by such a small subset of users that they did not justify the tier premium. The procurement team had no visibility into feature-level usage and therefore no basis to challenge the tier selection.
Over-Provisioned ITOM and SecOps
ITOM Discovery had been licensed for 15,000 nodes, reflecting an ambitious plan to discover and map the company's entire global infrastructure. In practice, only 9,200 nodes were being actively discovered — legacy manufacturing systems and several acquired-company environments had never been onboarded. Similarly, SecOps had been sized for a projected security event volume that assumed full integration with all security tools across all regions. Actual event volume was approximately 60% of licensed capacity, as several regional SIEM integrations had been deprioritised.
No Centralised Licensing Governance
ServiceNow licensing was managed by three different teams: IT operations managed ITSM and ITOM, the CISO's office managed SecOps, and HR managed HRSD. Each team managed its own relationship with ServiceNow, its own budget, and its own provisioning processes. There was no centralised view of the total ServiceNow estate, no unified process for license lifecycle management, and no regular review cadence to identify and reclaim unused entitlements.
🎯 Signs Your ServiceNow Estate Needs Right-Sizing:
Fulfiller count has only ever increased — you almost certainly have waste. You don't know which tier features you actually use — Enterprise vs Professional is a significant cost difference. Multiple teams manage different modules — decentralised ownership creates siloed procurement and invisible waste. You've had M&A activity, restructuring, or contractor rotations — every organisational change creates licensing drift. You can't answer "what are we paying per fulfiller?" — if pricing is opaque even internally, optimisation is impossible.
Is your ServiceNow estate right-sized? Most enterprises are paying for capacity they don't use. Our ServiceNow Advisory Services identify and eliminate waste — delivering measurable savings with zero operational impact.
Book a Free Consultation →Redress Compliance's Approach
Complete Estate Inventory and Entitlement Mapping
Redress began by constructing a complete inventory of the company's ServiceNow entitlements — every SKU, every metric, every quantity, every discount, every co-termination date. This involved reviewing the original contract, all amendments and add-ons, renewal documentation, and ServiceNow's internal entitlement records. The result was a single, unified view of the entire ServiceNow estate for the first time: what the company was paying for, what metrics applied, and what the effective per-unit cost was for each component.
User-Level Fulfiller Analysis
Redress conducted a user-by-user analysis of all 1,635 fulfiller licenses across ITSM, SecOps, and HRSD. For each licensed user, the analysis examined: last login date, login frequency over the past 180 days, role assignments and permissions, actual activity (tickets touched, changes approved, records modified), and current employment status (active employee, contractor, departed). Every fulfiller was categorised into one of four buckets: Active (regular usage, clearly needed), Occasional (infrequent but legitimate usage), Dormant (no meaningful activity in 90+ days), and Ghost (departed employees or expired contractor accounts still holding licenses). The results: 340 fulfillers fell into the Dormant or Ghost categories — over 20% of the licensed base.
Feature-Level Tier Analysis
For ITSM and HRSD, Redress conducted a feature-level analysis to determine whether Enterprise tier was justified. This involved mapping every Enterprise-exclusive feature against actual usage data. The analysis revealed ITSM was using precisely two Enterprise features (Predictive Intelligence for incident routing and Workforce Optimisation for scheduling), but Predictive Intelligence had less than 15% adoption rate among agents and Workforce Optimisation was used by only one team of 30 people. HRSD Enterprise features were essentially unused — the HR team had never completed the implementation of Employee Journey Management.
Consumption Metric Right-Sizing
For ITOM and SecOps, Redress analysed actual consumption against licensed capacity. ITOM Discovery was running at 61% utilisation (9,200 active nodes out of 15,000 licensed). SecOps event ingestion was at 58% of licensed volume. Redress worked with the company's infrastructure and security teams to determine realistic growth projections, applying a 15% headroom buffer above projected peak usage — producing right-sized quantities covering all current and planned usage without paying for speculative capacity.
Optimisation Roadmap and Implementation Support
Redress delivered a detailed optimisation roadmap with specific, actionable recommendations, risk assessments for each change, and a prioritised implementation sequence. Critically, the roadmap included a 30-day monitoring plan: after deprovisioning dormant fulfillers, the team monitored for any access issues, escalations, or workflow disruptions. Redress also provided the commercial analysis needed to renegotiate affected contract components with ServiceNow, including benchmarking data to ensure right-sized quantities were priced at or below market rates.
Savings and Optimisation Analysis
| Component | Before Right-Sizing | After Right-Sizing | Annual Saving |
|---|---|---|---|
| ITSM Fulfillers | 1,400 (Enterprise tier) | 1,120 (Professional tier) | $520K |
| SecOps Fulfillers | 150 | 118 | $96K |
| HRSD | Enterprise tier (42,000 employees) | Professional tier (42,000 employees) | $285K |
| ITOM Discovery | 15,000 nodes | 10,600 nodes | $188K |
| SecOps Event Volume | 100% licensed capacity | 70% (actual + headroom) | $111K |
| Total Annual Saving | $1.2M |
Where the Savings Came From
Fulfiller Elimination + ITSM Tier Downgrade
Removing 280 unused ITSM fulfillers and downgrading from Enterprise to Professional tier delivered $520K — the single largest saving. The tier downgrade alone saved approximately $180K; the fulfiller reduction saved $340K.
HRSD Tier Downgrade
Moving HRSD from Enterprise to Professional tier saved $285K annually. Enterprise features that had never been deployed were eliminated from the contract with no impact on HR operations.
ITOM + SecOps + SecOps Fulfillers
Right-sizing ITOM nodes, SecOps event capacity, and SecOps fulfillers saved a combined $395K. Each adjustment included a 15% growth buffer above current peak usage.
Results and Business Impact
$1.2M Annual Savings — $3.6M Over the Contract Term
The right-sizing exercise delivered $1.2M in annualised savings, translating to $3.6M over the remaining three-year contract term. These were permanent, structural savings — not one-time credits or temporary discounts. The company's ServiceNow spend decreased from $3.2M to $2.0M per year with no reduction in operational capability. Every active user, every deployed workflow, every integration, and every dashboard remained fully functional.
Licensing Governance Framework Established
Beyond the immediate savings, Redress helped implement a licensing governance framework to prevent waste from re-accumulating. The framework included: a quarterly fulfiller review process (automated reports identifying accounts with no login for 60+ days), a centralised provisioning and deprovisioning workflow (new fulfiller requests routed through ITAM regardless of module), annual tier reviews (feature usage analysis before each renewal), and a unified ServiceNow licensing dashboard visible to all stakeholder teams.
Stronger Renewal Position
The right-sizing exercise was completed eight months before the company's next ServiceNow renewal. By establishing a clean, right-sized licensing baseline ahead of the renewal, the company eliminated the risk of renewing at an inflated level and created a significantly stronger negotiation position. ServiceNow's renewal proposal would now be benchmarked against actual, validated usage rather than historical over-provisioning. For pricing strategy, see ServiceNow Pricing and Negotiation: Top 20 Tips and the ServiceNow pricing guide.
"License right-sizing is the highest-ROI activity in enterprise ServiceNow management. Every organisation that has grown its ServiceNow estate over multiple years has accumulated waste — it's structural, not a failure of management. The question is not whether the waste exists, but how much. In this engagement, 20% of fulfiller licenses were unused and two modules were running at tiers that cost 30 to 40% more than necessary. These are not unusual findings — they are typical of what we see in every enterprise ServiceNow assessment." — Fredrik Filipsson, Co-Founder, Redress Compliance
Lessons Learned and Best Practices
Right-Size Before You Renew, Not During
The most common mistake is attempting to right-size during the renewal negotiation itself. This gives ServiceNow leverage to resist reductions and compresses analysis into weeks rather than months. Right-sizing should be completed 6 to 12 months before renewal, producing a validated, defensible baseline that becomes the starting point for commercial negotiation.
Fulfiller Audits Should Be User-by-User
High-level metrics ("we have 1,400 fulfillers and about 1,200 seem active") are insufficient. Right-sizing requires user-by-user analysis: login history, activity patterns, role assignments, and employment status for every licensed individual. Statistical estimates leave waste in the system and create risk of deprovisioning active users.
Challenge the Tier — Every Single Renewal
The gap between Professional and Enterprise pricing is substantial — typically 25 to 40% depending on the module. Many enterprises pay Enterprise prices for Professional-level usage because original business cases identified Enterprise features that were never fully deployed. Before every renewal, conduct a feature-level analysis: list every Enterprise-exclusive feature, determine whether it is actively used, and by how many users.
Centralise ServiceNow Licensing Governance
Decentralised ownership — where IT manages ITSM, security manages SecOps, and HR manages HRSD — is the primary driver of invisible waste. Each team optimises for its own needs without visibility into the total estate. Centralising governance under ITAM or procurement creates accountability, enables cross-module optimisation, and prevents re-accumulation of waste.
Build Headroom Into Right-Sized Numbers
Right-sizing is not about cutting to the absolute minimum. Aggressive reductions create operational risk and trigger urgent mid-term purchases. Redress applies a standard methodology: current validated usage plus a 10 to 15% growth buffer, ensuring headroom for organic growth without paying for speculative capacity. This balanced approach delivered $1.2M in savings while maintaining comfortable margin above active usage.
"We knew there was waste in our ServiceNow estate, but we couldn't quantify it or agree internally on what was safe to eliminate. Redress gave us the independent, evidence-based analysis we needed. The $1.2M saving was significant, but what really changed our position was the governance framework — for the first time, we have a single view of our entire ServiceNow licensing and a process to keep it optimised. We went into our renewal negotiation with data, not guesswork."
VP of IT Asset Management, Fortune 500 Pharmaceutical Company
Similar Engagements
The patterns identified in this engagement — fulfiller sprawl, over-tiered modules, and over-provisioned consumption metrics — are consistent across virtually every enterprise ServiceNow estate that has grown organically over multiple years.
Professional Services Firm — $1.5M Saved on $12M Renewal
A New York-based professional services firm engaged Redress 14 months before its ServiceNow renewal. The engagement identified $2.8M in shelfware and delivered $1.5M in savings through early negotiation, pricing benchmarking, and licensing rationalisation. Read the full case study.
Frequently Asked Questions
Based on Redress's advisory portfolio across dozens of enterprise ServiceNow assessments, 20 to 35% of total spend is typically allocated to unused or underutilised entitlements. The primary sources are dormant fulfiller licenses (users who have departed, changed roles, or completed projects), over-tiered modules (Enterprise tier pricing for Professional-level usage), and over-provisioned consumption metrics (ITOM nodes, SecOps events) sized for deployment plans that were only partially realised.
In many cases, yes. The key is conducting a feature-level analysis before making the change. List every Enterprise-exclusive feature for each module, determine which are actively deployed and used, and assess whether usage justifies the tier premium. If Enterprise features are unused or used by only a small subset of users, the downgrade is straightforward. ServiceNow may resist during renewal negotiations, but with documented feature usage data, the customer's position is defensible. For a detailed example, see our Enterprise to Professional downgrade case study.
The safest approach is a multi-factor analysis: login history (last 90 to 180 days), activity records (tickets touched, records modified), role assignments, and HR system cross-reference (employment status, department, job title). Users who show no login activity AND have departed or changed to a non-ServiceNow role are safe to deprovision. For borderline cases, a 30-day monitoring period after deprovisioning (with the ability to quickly re-activate) mitigates risk.
Always before. Right-sizing during a renewal compresses the analysis timeline, gives ServiceNow grounds to challenge your usage data, and forces optimisation decisions under commercial pressure. Complete the exercise 6 to 12 months before renewal. This produces a validated, defensible baseline that becomes the starting point for negotiation — fundamentally changing the commercial dynamic. For renewal strategy, see our ServiceNow Renewal: Complete Guide.
At minimum: a quarterly fulfiller review (automated reports on accounts with no login for 60+ days), a centralised provisioning and deprovisioning workflow (all license requests through ITAM regardless of module), an annual tier review (feature usage analysis before renewal), and a unified licensing dashboard that gives all stakeholder teams visibility into the total estate. Without governance, waste re-accumulates within 12 to 18 months.
🚀 Is Your ServiceNow Estate Right-Sized?
Most enterprises are paying for ServiceNow capacity they don't use. Redress Compliance's license optimisation service identifies and eliminates waste — delivering measurable savings with zero operational impact.
ServiceNow Advisory Services | Right-Sizing Assessment | Book a Free Consultation
📚 ServiceNow Advisory Resources
ServiceNow Knowledge Hub Professional Services Firm — $1.5M Saved on Renewal Edition Downgrade — $800K Saved Enterprise to Pro ServiceNow Pricing and Negotiation: Top 20 Tips ServiceNow Licensing Types Guide Top 5 ServiceNow Competitors ServiceNow Advisory Services📂 Related Reading
ServiceNow SecOps Licensing Guide ServiceNow HRSD Licensing Guide ServiceNow ITOM Licensing Guide Fulfiller vs Requester Licensing Explained How to Avoid True-Up Surprises ServiceNow Shelfware: How to Identify and Eliminate ServiceNow Renewal: Complete Guide ServiceNow Pricing Guide ServiceNow Customer Service Management (CSM) ServiceNow ITSM: Comprehensive Guide ServiceNow for Oracle License Management🧰 Tools and Resources: ServiceNow Assessment Tools | All Audit Defence Kits | All Renewal Playbooks | Enterprise Assessment Tools | Pricing Benchmarking