ServiceNow License Right-Sizing for Fortune 500 Pharmaceutical: $1.2M Saved

The Challenge

A Renewal Approaching — and No Visibility Into What Was Actually Being Used

The client — a Fortune 500 pharmaceutical company with global operations across North America, Europe, and Asia-Pacific — had deployed ServiceNow ITSM Pro across 14 business units over a four-year period. With a major enterprise renewal due within six months, the VP of IT Procurement flagged a concern that had gone unaddressed since the last contract cycle: the organisation had no reliable data on who was using which licence tier, or why.

ServiceNow's sales team had proposed a renewal quote representing a 12% uplift on the existing contract — adding approximately $520,000 to annual spend — and was simultaneously pushing the client towards an ITSM Pro Plus upgrade to access AI-assisted features under Now Assist. The combined ask would have increased total ServiceNow expenditure by close to 30% year-on-year.

The client's internal ITAM function had generated a utilisation report, but the data covered only the previous 30 days and was limited to active login counts. It did not capture licence tier mismatches, dormant accounts, or users whose roles had changed since their licences were provisioned. The procurement team had no independent baseline from which to push back on ServiceNow's renewal proposal.

The Licence Structure That Created the Exposure

ServiceNow's ITSM licensing architecture distinguishes between three primary user categories: Fulfillers, who require full platform access and carry the highest per-seat cost; Business Stakeholders, who can approve requests, view records, and access reports at a substantially lower rate; and Requesters, who interact only with the self-service portal and are effectively zero-cost. The client's estate was almost entirely provisioned at Fulfiller level — a legacy of a bulk provisioning decision made during the original deployment when it was simpler to give everyone the same licence type than to profile individual roles.

Four years on, this approach had generated a significant and growing overspend. Business analysts, regional managers, compliance officers, and HR business partners — all of whom used ServiceNow primarily to approve requests and review reports — were sitting on Fulfiller licences priced at roughly three times the Business Stakeholder rate.

The Approach

Phase 1 — Licence Inventory and Usage Profiling (Weeks 1–3)

Redress Compliance began with a structured licence inventory across the client's ServiceNow instance. Using ServiceNow's native Subscription Management module alongside a bespoke extraction methodology, the team built a complete picture of all 1,400 active licences: tier assignment, last login date, average weekly session frequency, module access patterns, and the business function of each licence holder.

The analysis revealed three distinct population segments with different remediation paths:

• Over-provisioned Fulfillers (487 users): Active users whose actual platform behaviour — predominantly approval workflows, report viewing, and occasional incident submission — mapped entirely to Business Stakeholder entitlements. None of these users had raised or resolved an incident or service request in the previous 12 months.
• Inactive accounts (214 users): Accounts with no login activity in the previous 90 days. Cross-referencing against the HR system confirmed that 189 of these accounts belonged to employees who had left the organisation or transferred to business units that no longer used ServiceNow. The remaining 25 accounts were provisioned for a project team whose engagement had concluded.
• Correctly provisioned Fulfillers (553 users): Service desk agents, ITSM process owners, and IT operations staff with genuine Fulfiller-level usage patterns. These licences were validated and excluded from any remediation recommendation.

Phase 2 — Financial Modelling and Renewal Leverage Analysis (Weeks 4–5)

With the usage data profiled, the team constructed a detailed financial model comparing the client's current contractual commitment against a right-sized baseline. The model incorporated ServiceNow's published list rates, the client's existing negotiated discount position, and the uplift trajectory implied by ServiceNow's renewal proposal.

The model also identified that ServiceNow's proposed 12% renewal uplift was applied to the full 1,400-licence base rather than to a right-sized equivalent. Negotiating from the corrected baseline, and countering the uplift with benchmark data from comparable enterprise renewals, would further improve the client's total cost position.

Phase 3 — Negotiation Preparation and Vendor Engagement (Weeks 6–9)

Redress Compliance prepared a detailed negotiation brief for the client's procurement team. The brief included a counter-proposal to ServiceNow anchored on the right-sized licence count, benchmark renewal uplift data from four comparable pharmaceutical and life sciences deployments, a rejection rationale for the ITSM Pro Plus upsell, and a proposed contractual structure that locked price protections across the remaining three-year term.

A key element of the negotiation strategy was the sequencing of the licence remediation discussion relative to the renewal commitment. By surfacing the inactive account data and tier mismatches before any renewal conversation had progressed, the client established that ServiceNow had been receiving payment for licences that were effectively unused — a position that substantially altered the power dynamic in the renewal negotiation.

ServiceNow's response to the counter-proposal was to offer a revised uplift of 4.5% on the right-sized licence base, inclusion of ServiceNow Virtual Agent at no additional charge, and a three-year price cap on ITSM Pro Fulfiller rates. The client accepted this revised position.

The Outcome

Total Value of the Engagement

Combining the annualised right-sizing savings, the renewal uplift reduction, and the three-year price protection benefit, the total contract-term value of the engagement was approximately $3.6 million. The engagement was delivered on a fixed-fee basis in nine weeks, generating a return on advisory investment in excess of 18:1.

The client subsequently established a quarterly ServiceNow licence review process using the methodology developed during the engagement. This process is expected to identify further incremental savings as headcount changes and module usage evolves ahead of the next renewal cycle in 2028.

Why the Right-Sizing Came Before the Negotiation

A recurring mistake in enterprise software renewals is to begin the vendor conversation before the internal data is clean. Organisations that approach ServiceNow — or any SaaS vendor — without a validated utilisation baseline are negotiating blind. The vendor has the usage data; the customer typically does not. Closing that information asymmetry before the first renewal meeting is the single most important step in any licence optimisation exercise.

In this engagement, the sequence mattered as much as the analysis. The utilisation data was extracted, validated, and presented to ServiceNow as a statement of fact — not a negotiating position. ServiceNow could not credibly argue that 214 accounts with zero login activity in 90 days represented active use. That factual foundation, combined with benchmark data on comparable renewals, gave the client's procurement team the confidence to reject the initial proposal and negotiate from a position of evidential strength.

Key Lessons for Enterprise ServiceNow Customers

This engagement surfaces several lessons applicable to any large ServiceNow deployment approaching renewal:

• Bulk provisioning decisions made at go-live rarely age well. Role profiles change, headcount moves across business units, and projects end — but licences frequently remain static until someone looks.
• ServiceNow's own usage analytics are a starting point, not a final answer. Native reports show login activity but do not automatically surface licence tier mismatches or cross-reference against HR systems to identify leavers.
• The Pro Plus / Now Assist upsell carries a price premium that rarely survives independent analysis. For most enterprise ITSM deployments, the productivity gains from AI-assisted features do not justify the licence uplift when those features can be partially accessed through lower-cost alternatives.
• Price protection clauses are underused. Most enterprise ServiceNow agreements can accommodate multi-year rate caps or uplift limits if the customer requests them at the point of renewal — but few customers do.