A US property & casualty insurer had grown its ServiceNow estate organically across eight years — fulfillers, requesters, custom apps on Now Platform, and a transaction-pack consumption model nobody had audited. We rebuilt the entitlement model, remediated custom-app exposure before renewal, and ring-fenced the Now Assist pilot before it became contractually binding.
The client — a US property & casualty insurer with 11,000 ServiceNow fulfillers and 38,000 requester licences — had been a ServiceNow customer since 2017. Across that period, the platform had expanded from ITSM into HR Service Delivery, then customer service workflows, then claims-adjacent workflows running on Now Platform App Engine. Each expansion had layered on transaction packs, additional licensing schedules, and increasingly broad use of custom-built applications.
As renewal approached, ServiceNow's account team flagged two exposures. First, several of the customer's custom applications appeared to be using data structures and integration patterns that fell under licensable scope. Second, transaction-pack consumption had been running ahead of entitlement for nine consecutive months. The renewal proposal monetised both exposures and added a mandatory Now Assist Pro attach across all 11,000 fulfiller seats.
In our experience across ServiceNow engagements, the framing of "custom-app exposure" pre-renewal is almost always more aggressive than the contractual ground supports. ServiceNow's licensing rules treat applications differently depending on whether they consume creator vs. requester data, integrate with the CMDB, or expose UI elements via Service Portal. A meaningful proportion of what gets flagged as exposure is remediable through configuration changes — not licence purchases.
Custom-app exposure is usually remediable. Now Assist is almost always negotiable.
We reconstructed the full ServiceNow entitlement schedule from order forms across the prior six years. The customer had fulfiller, requester, custom-app, employee centre, transaction pack, and HR Service Delivery licences spread across nine separate amendments. None of the documents matched the platform's actual configuration. We produced a unified entitlement-to-deployment map showing exactly where consumption was at, below, or above contractual scope.
Of the 14 custom applications flagged by ServiceNow as creator-scope, we reviewed each one's data model, integration pattern, and UI exposure. Eight could be remediated through targeted configuration changes (de-coupling from CMDB tables, replacing creator-licensable UI patterns with requester-compatible ones). Four required modest creator-licensing purchases at substantially lower volume than ServiceNow had proposed. Two were dropped or replaced by out-of-the-box ServiceNow workflow products at no additional cost.
ServiceNow's proposed Now Assist attach was an 11,000-seat mandatory deployment at the Pro SKU. We negotiated this down to a pilot ring fence — 400 named fulfiller seats, with usage-based reporting, opt-in step-ups, and most-favoured-customer pricing if the customer expanded to full deployment in the next two renewal cycles. The pilot retained the optionality without committing to the scope.
ServiceNow renewals reward technical depth on the customer side. The vendor account team's compliance framing assumes the customer cannot — or will not — reverse-engineer the licensing rules at the table-and-integration level. Customers who do that work change the conversation. The negotiation moves from "buy more licences" to "remediate what is actually out of scope and price what remains." Now Assist follows the same logic: pilot it as a ring fence, capture optionality, refuse the floor.
If you are coming up on a ServiceNow renewal in the next twelve months, the work to map entitlement against actual configuration needs to start at least nine months out. The ServiceNow Contract Optimization Guide walks through the remediation patterns in detail.
The custom-app remediation framework used on this engagement.
Our ServiceNow practice is led by former renewal account directors and platform architects. We map entitlement to configuration before the renewal conversation begins.
Weekly compliance intelligence for IT leaders.
