Case study · Telecom · Renewal support

A ServiceNow telecom fulfiller rightsizing case study.

This ServiceNow telecom fulfiller rightsizing case study shows how a carrier turned a proposed 10 percent uplift on an inflated fulfiller base into a capped renewal roughly 24 percent below the opening quote, using buyer side reconciliation and benchmark data from real enterprise renewals.

0%

Reduction versus the initial renewal quote

0

Fulfiller licences reclaimed or reclassified

0%

Capped annual uplift, down from 10 percent

How the ServiceNow telecom fulfiller rightsizing case study unfolded

A multi market telecom carrier reached renewal with a ServiceNow estate that had grown across IT service management, infrastructure operations and customer service management over two contract terms. The proposed renewal carried a 10 percent annual uplift applied to roughly 9,200 fulfiller licences, plus a default migration from the legacy Enterprise tier to Prime under the 2026 commercial model. The account team framed the fulfiller base as fixed and the uplift as standard. The carrier brought us in buyer side to test both claims against benchmark data from real enterprise renewals.

The situation

Telecom estates inflate fulfiller counts faster than most industries because field operations, network operations and customer care all touch the platform, and licences follow roles that churn constantly. Nobody inside the carrier could state with confidence how many of the 9,200 fulfillers were active, how many were dormant after restructures, and how many were requesters misclassified as fulfillers. With the renewal date inside four months, the internal default was to accept the uplift and move on.

Our first task was to slow the calendar and replace the headline count with a reconciled one. A fulfiller licence carries many times the cost of a requester, so the boundary between the two is where a telecom renewal leaks the most money. We mapped entitlements against actual usage and broke the bundled proposal into separate decisions on volume, tier and uplift so each could be negotiated on its merits.

What we found

The reconciliation told a very different story than the renewal quote assumed. Close to a fifth of the fulfiller base had not logged activity in six months, concentrated in two markets that had reorganised field operations. A further block of accounts were requesters who approved or viewed work rather than performing it, classified as fulfillers in the count the vendor presented. And the default migration to Prime bundled an AI allocation the carrier did not yet need, where a mapping to Advanced covered the real requirement at a lower baseline. In total, around 2,600 fulfiller licences were dormant or misclassified.

The negotiation

We built the strategy around four moves, sequenced so volume and mix were settled before price. First, a right sized fulfiller request that removed the dormant accounts and reclassified the requesters, anchored to the usage evidence rather than the vendor count. Second, a corrected tier migration that mapped legacy Enterprise to Advanced rather than Prime, with the carrier's existing protections carried across rather than reset. Third, a conservatively sized assist commitment built from a weighted consumption model, with the overage rate fixed at signature. Fourth, a capped annual uplift stated as a number, replacing the open 10 percent.

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

"Once the fulfiller number was ours rather than theirs, the whole renewal moved."ITAM lead, anonymised

The outcome

The agreement signed four weeks before deadline. The fulfiller base was right sized by roughly 2,600 licences, the tier migration landed on Advanced with protections preserved, and the annual uplift was capped at 4 percent, down from the proposed 10 percent, with a renewal cap carried into the next term. In total the renewal closed around 24 percent below the initial quote. The mechanics behind the fulfiller work are detailed in our ServiceNow fulfiller optimization guidance, and the supporting evidence pack in our fulfiller optimization report.

Lessons

Three lessons carry beyond this engagement. In a telecom estate the headline fulfiller count is almost always the largest number, not the right one, and reconciling it is where most of the value sits. A tier migration is an opportunity to carry protections forward, not an excuse to reset them. And the uplift is worth capping as a number, because a percentage left open compounds across every year of the term on a base that should have been smaller to begin with.

Frequently asked questions

What is this ServiceNow telecom fulfiller rightsizing case study about?

It describes a telecom carrier that walked into a renewal with a proposed 10 percent uplift on an inflated fulfiller base. A buyer side reconciliation right sized the fulfiller count, mapped the legacy tier correctly, and closed the renewal around 24 percent below the opening quote.

Is this a real telecom client?

The case study is anonymised. It is based on real enterprise renewal engagements, with the client profile, estate and figures presented as plausible and internally consistent ranges rather than naming any organisation.

What drove the savings in this telecom renewal?

Fulfiller rightsizing did most of the work. Removing dormant and misclassified fulfiller licences, correcting the tier migration to Advanced, and capping the uplift as a number together moved the renewal well below the opening figure.

Are the figures official ServiceNow prices?

No. All figures are typical negotiated ranges based on benchmark observations across real enterprise renewals, used as internal leverage rather than published as official list prices.

Your renewal

Talk to the advisor who ran this engagement.

Talk to the advisor who ran this engagement