The ServiceNow fulfilment user reconciliation.

The fulfilment user count is the contestable count.

ServiceNow licensing turns, on most renewals, on the fulfilment user count. The fulfilment user is the user with permission to operate inside the Now Platform: to update records, to run workflows, to act on assigned work. The publisher reads the fulfilment user count from the role-assignment data the platform itself generates. The buyer who reads the count from the same source, on the same cadence, with the same role-mapping convention, arrives at the renewal table with the same count the publisher uses. The buyer who reads the count from a different source, with a different mapping convention, or on a different cadence, arrives at a different count, and the renewal price sits in the gap.

The fulfilment-user reconciliation is not a settlement exercise. The reconciliation runs through the year. The role-assignment register, the deprovisioning protocol, the inherited-role audit, the role-cleanup cadence, the leavers protocol, the contractor reconciliation, the team-handover process, all of these touch the fulfilment user count. The renewal protocol is the documented version of that operating model, and the buyer who brings it to the renewal table brings the contestable count as a fact, not as a position.

This paper covers the methodology Admodum applies inside the ServiceNow renewal: the fulfilment-user reconciliation protocol, the module-consolidation case, the Now Assist and AI Agent scope contestation, the SaaS uplift defence and the BATNA-driven renewal posture. The methodology is the one that has been applied across twenty-three ServiceNow renewals in the firm’s engagement history.