Case study · Insurance · Tier migration
This ServiceNow insurance tier migration case study shows how an insurer refused a default migration of its entire estate to the Prime tier, mapped each workload to the right level under the 2026 model, and closed the renewal roughly 19 percent below the opening quote using buyer side analysis and benchmark data from real enterprise renewals.
Reduction versus the initial renewal quote
Of the estate mapped to Advanced instead of default Prime
Capped annual uplift, down from 11 percent
A mid size insurer reached renewal carrying a ServiceNow estate built across two contract terms on a mix of legacy tiers, principally Pro Plus and Enterprise Plus, spanning IT service management, HR service delivery and customer service. The 2026 commercial model had replaced the five legacy tiers with Foundation, Advanced and Prime, and the renewal proposal defaulted the entire estate to Prime, the highest level, with an 11 percent annual uplift on top. The account team framed Prime as the natural successor to the insurer's legacy entitlements. The insurer brought us in buyer side to test that mapping against benchmark data from real enterprise renewals.
Insurance estates accumulate tiers unevenly. Core claims and policy teams often sit on richer legacy entitlements, while large populations in shared services and back office hold lighter ones. A blanket migration to Prime treats every one of those workloads as if it needed the top tier, which is rarely true. With the renewal date inside three months and the proposal framed as a straight successor mapping, the internal default was to accept the Prime migration and the uplift together.
Our first task was to separate the migration from the renewal and to challenge the assumption that legacy tier equals top new tier. The 2026 mapping from legacy Standard, Pro, Pro Plus, Enterprise and Enterprise Plus to Foundation, Advanced and Prime is not a simple one to one escalation, and the gap between Advanced and Prime is where an insurance renewal of this shape leaks the most money. We broke the bundled proposal into separate decisions on tier, volume and uplift so each could be negotiated on its merits, in the pattern set out in our ServiceNow tier migration advisory.
Mapping each workload to its real requirement told a very different story than the blanket Prime proposal assumed. Around three fifths of the estate, concentrated in shared services and standard service management, was fully covered by the Advanced tier. The features that distinguish Prime were genuinely needed only in a minority of workflows, mostly in the customer facing claims function. The default migration would have paid the Prime premium across the whole estate to serve a requirement that existed in a fraction of it. The detail behind the mapping sits in our Foundation Advanced Prime comparison.
We built the strategy around three moves, sequenced so tier and mix were settled before price. First, a corrected tier mapping that placed roughly 60 percent of the estate on Advanced and reserved Prime for the workflows that genuinely required it, with the insurer's existing protections carried across rather than reset. Second, a conservatively sized commitment that avoided paying for headroom the insurer did not need at the Prime level. Third, a capped annual uplift stated as a number, replacing the open 11 percent.
The insurer's procurement 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.
The agreement signed three weeks before deadline. Around 60 percent of the estate landed on Advanced rather than the proposed Prime, with protections preserved, and Prime was reserved for the claims workflows that genuinely required it. The annual uplift was capped at 5 percent, down from the proposed 11 percent, with a renewal cap carried into the next term. In total the renewal closed around 19 percent below the initial quote. The approach mirrors the tier work in our other anonymised engagements, including our banking renewal uplift reduction case study and our telecom fulfiller rightsizing case study.
Three lessons carry beyond this engagement. A default migration to the top new tier is a proposal, not a fact, and mapping each workload to its real requirement is where most of the value sits. The gap between Advanced and Prime is the decision that matters most in the 2026 model, because paying the Prime premium across an estate that mostly needs Advanced compounds across every year of the term. And a tier migration is an opportunity to carry protections forward and cap the uplift as a number, not an excuse to reset both.
It describes an insurer whose renewal defaulted the whole estate to the Prime tier under the 2026 model. A buyer side tier mapping moved much of the estate to Advanced where it fit, capped the uplift as a number, and closed the renewal around 19 percent below the opening quote.
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.
Correct tier mapping did most of the work. Refusing the default Prime migration where Advanced covered the requirement, carrying protections forward, and capping the uplift as a number together moved the renewal well below the opening figure.
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