A ServiceNow professional services true up defense case study.

How the ServiceNow professional services true up defense case study unfolded

A professional services firm received a true up claim ten weeks before its renewal, asserting a large unlicensed fulfiller population across its delivery teams. The claim arrived with a number attached and a deadline that lined up with the renewal date. The firm brought us in on the buyer side to test whether the claim measured real usage or simply counted role names, and to keep a compliance question from being used to soften its position on renewal price.

The situation

The firm ran a heavy custom build to support client delivery, with many users holding roles that looked like fulfiller roles but were used in a requester pattern in practice. The opening claim counted those roles at face value, producing an exposure number far larger than behaviour justified. With the renewal inside three months, the internal instinct was to settle quickly to clear the issue before the contract conversation, which is exactly the outcome a review timed to a renewal is designed to produce.

Our first move was to separate the two events. A true up claim and a renewal are almost always part of the same conversation, and conceding the claim early hands the vendor leverage on price. We treated the claim as an opening commercial position to be tested, not a settled bill to be paid.

What we found

Reconciling the disputed accounts against actual activity told a different story than the claim assumed. A large share of the users named in the claim had performed no fulfiller actions in the review period: they held a role but worked in a requester pattern, raising and tracking their own items without resolving others. The custom delivery applications, which the claim treated as extending the platform beyond entitlement, mapped cleanly to existing licensed functionality once the access was inventoried. The genuine shortfall was a fraction of the opening number.

The negotiation

We built the defence around three moves. First, we bounded the scope of the data request so the review stayed on the disputed population rather than expanding into the whole estate. Second, we reconciled fulfiller and requester roles against behaviour using the activity data already inside the platform, producing evidence the account team had to engage with on the merits. Third, we negotiated the remaining finding as a commercial claim attached to the renewal, sequencing it so the settlement and the contract were read together rather than traded against each other. The approach follows our ServiceNow renewal negotiation advisory.

The firm's team led every conversation. We stayed behind the table, reviewing each revision of the claim, drafting counters, and briefing executives before each session.

The outcome

The true up settled six weeks before the renewal deadline. With the scope bounded and the population reconciled against behaviour, the genuine shortfall was a small fraction of the opening claim, and the settlement closed roughly 60 percent below the opening exposure number, a reduction in the region of 2.2 million dollars. Reclassifying the requester pattern users also removed shelfware that lowered the renewal base, so the same reconciliation helped twice. The mechanics behind the work are set out in our broader ServiceNow renewal guidance. Final contract language should be reviewed by counsel.

Lessons

Three lessons carry beyond this engagement. A true up claim is an opening position, not a settled bill, and the largest reductions come from reconciling roles against behaviour rather than accepting role names. A claim timed to a renewal should be sequenced so the two are settled together, because conceding the claim early hands the vendor leverage on price. And the activity data needed to defend a claim already sits inside the platform, so the strongest evidence is the buyer own. For comparable outcomes elsewhere, see our banking true up defense and logistics true up defense case studies.