A ServiceNow manufacturing ELA renegotiation case study.

How the ServiceNow manufacturing ELA renegotiation case study unfolded

A global manufacturer reached the end of a four year enterprise license agreement with ServiceNow embedded across IT, plant operations and HR. The account team proposed the simplest path: roll the existing ELA forward, apply a 10 percent uplift to the whole bundle, migrate the estate to Prime under the 2026 commercial model, and add a Now Assist allocation sized to a vendor forecast. Each move was framed as continuity. The manufacturer brought us in on the buyer side to test whether continuity was the same thing as value.

The situation

The original ELA had been signed when the platform was expanding quickly, so the bundle was sized to an optimistic growth curve rather than to settled usage. Four years on, the organisation had restructured two divisions and consolidated several plants, but the ELA had carried the old base forward untouched. With the renewal date inside four months, the internal default was to accept a number near the proposal and avoid reopening a complex agreement.

Our first task was to slow the calendar and separate the bundle into the decisions it actually contained. A rolled forward ELA hides several questions inside one number: how large the base should be, which tier each population needs, how expansion should be priced, and how much metered AI to commit. We pulled those apart so each could be negotiated on its own evidence rather than waved through as a package.

What we found

Reconciling entitlements against genuine usage told a different story than the rolled forward bundle assumed. Around 16 percent of fulfiller licences inside the ELA sat with users who had left or moved to approval only roles after the restructure. An ITOM capability bundled at the original signing had never been deployed beyond two sites. The proposed Prime migration applied the top tier across the whole estate, while a mapping to Advanced covered the real requirement for most populations at a lower baseline. And the Now Assist forecast counted AI actions without weighting agentic ones, oversizing the committed pool while understating the consumption that would actually matter.

The negotiation

We built the strategy around four moves, sequenced so the size and shape of the ELA were settled before price. First, a resized base that removed the dormant fulfillers and the undeployed ITOM capability, so the bundle reflected the post restructure organisation. Second, a corrected tier mix that mapped most of the estate to Advanced rather than Prime, reserving the top tier for the populations that genuinely used it. Third, expansion rights at a fixed rate, so genuine future growth would be added predictably rather than pre purchased inside the bundle. Fourth, a Now Assist commitment built from a weighted consumption model with the overage rate fixed at signature and rollover secured for unused assists.

The manufacturer's team led every conversation. We stayed behind the table, reviewing each ELA revision, drafting counters, and briefing executives before each session, in the pattern set out in our ServiceNow renewal negotiation advisory.

The outcome

The renegotiated ELA signed six weeks before deadline. The base matched the reconciled organisation, the tier mix landed mostly on Advanced with Prime reserved where usage justified it, and expansion rights priced future growth at a fixed rate rather than inside the committed bundle. The annual uplift was capped at 5 percent, down from the proposed 10 percent, with the cap carried into the next term. The Now Assist line carried a fixed overage rate and assist rollover. In total the agreement closed roughly 19 percent below the proposed bundle, saving the manufacturer in the region of 2.4 million dollars over the four year term. The mechanics behind the work are set out in our broader ServiceNow renewal guidance.

Lessons

Three lessons carry beyond this engagement. A rolled forward ELA is the most expensive form of continuity, because it makes an oversized base permanent and uplifts it every year. A tier migration inside a bundle should be mapped to usage, not defaulted to the top tier across the whole estate. And a metered AI commitment belongs in an ELA only when it is sized from a weighted consumption model and protected with a fixed overage rate, so the bundle does not quietly transfer the AI risk onto the buyer. For comparable outcomes elsewhere, see our banking renewal uplift reduction and telecom fulfiller rightsizing case studies.