Run the methodology with a senior advisor.
A senior Admodum advisor will walk the methodology through with your CIO, CFO, sourcing or platform-owner team on a private call. Engagements run as fixed fee, contingency or annual retainer.
Thirty pages on the ServiceNow renewal cycle, fulfilment-user reconciliation, module consolidation across ITSM, ITOM, HRSD, CSM, SecOps and IRM, Now Assist scope, AI Agent commitment, SaaS uplift contestation, Strategic Portfolio Management and the BATNA-driven renewal posture.
The ServiceNow renewal is anchored to the Subscription Service Order Form. Standard terms run on three-year cycles, with annual ramp shaping and a recurring SaaS uplift on each anniversary. The renewal preparation cycle, properly run, opens twelve months before the renewal anniversary and runs through the seller’s account-team motion into the closing window.
The first quarter of the cycle is governance. The renewal steering group is convened with named representatives from IT, security, HR, procurement, finance and the platform owners. The current ServiceNow portfolio is reconstructed: every module entitled, every fulfilment-user count, every Approver Concurrent or Requester count, every Custom Table license, every AI add-on, every Integration Hub entitlement. The reconstruction is the foundation on which every other lever depends.
The second and third quarters are scenario development. The fulfilment-user reconciliation is run. The module consolidation analysis is completed. The Now Assist and AI Agent commercial position is sized against the operational adoption record. The Strategic Portfolio Management and Customer Workflow expansions the seller has positioned through QBR are reconciled against actual deployment.
The fourth quarter is execution. The renewal proposal is contested line by line; the SaaS uplift is negotiated explicitly; the multi-year term and ramp shape are set; the AI commitments are sized to the documented use cases; the BATNA position is held at the table.
The buyer who begins the renewal in the eight weeks before signature absorbs the seller’s opening position. The buyer who begins twelve months earlier sets the position the seller responds to.
The fulfilment user is the ServiceNow license metric for users who process work inside the platform: incident agents, change managers, problem coordinators, HR case workers, security operations analysts, customer-service agents and the broader population that creates, updates and closes records inside the platform’s structured tables. The fulfilment-user count is the highest-leverage commercial variable inside the ServiceNow renewal.
A fulfilment user is, in ServiceNow’s reading, a user who performs fulfilment activity inside the platform. The reading is permissive: any user who creates, updates or closes records inside a fulfilment-bearing table is a fulfilment user, regardless of role or frequency. The buyer’s reconciliation must therefore run against the user-activity history, not against the role-assignment record.
The user-activity report identifies users who have performed fulfilment activity inside a defined window (typically ninety to one hundred and eighty days). Users below the activity threshold are candidates for retirement: their fulfilment-user entitlement is recovered, the licence is returned to the pool, and the renewal count is reduced.
Not every user is a fulfilment user. Approvers and Requesters are separate license categories at materially different price points. An Approver Concurrent user can review and approve workflow approvals (and read the records they touch) but cannot fulfil work; a Requester can submit requests through the Service Portal without holding a fulfilment licence. The reconciliation must reclassify users from fulfilment to Approver or Requester wherever the user’s actual activity supports the lower-tier assignment.
The Service Portal carries the unauthenticated requester pattern that allows the broad employee population to interact with ServiceNow without a paid licence. The reconciliation should examine whether requester workflows that are currently routed through licensed user accounts can be moved to the Service Portal pattern, reducing the licensed user count without reducing the operational reach.
The ServiceNow module stack (ITSM, ITOM, HRSD, CSM, SecOps, IRM, Strategic Portfolio Management, Customer Workflow, App Engine, Now Platform) is licensed module-by-module with overlapping functionality across modules. The module-consolidation analysis identifies where the same operational outcome is delivered by two or more licensed modules and where one can be retired in favour of the other.
The most common consolidation lines are: ITSM Discovery and ITOM Discovery (where both are licensed and only one is operationally used), HRSD case management and ITSM case management (where HR cases run inside ITSM without HRSD’s specialised capability), CSM Customer Communities and Now Communities (where one or the other is the live deployment), SecOps Vulnerability Response and an external vulnerability-management tool that the buyer has not retired, and the App Engine Custom Table entitlement against the actual count of custom tables the buyer maintains.
The consolidation runs against the deployment evidence: which module is operationally active, which is dormant, which is duplicative. The buyer’s renewal position retires the dormant module licenses, consolidates the duplicative ones, and re-anchors the renewal envelope against the rationalised module portfolio.
The seller’s counter-position will frame the consolidated module portfolio as risking operational value the buyer has not yet realised. The counter-counter-position is that the renewal commits the buyer to three years of fees for value the buyer is not realising today, with the alternative being a future re-acquisition at the same or better price when the value case is documented.
Now Assist is ServiceNow’s generative-AI product family, sold as a per-user add-on on top of the existing module licence at a defined monthly price. The Now Assist scope decision is the most aggressive commercial expansion the seller will position inside the renewal cycle.
Now Assist is delivered across several SKUs: Now Assist for ITSM (incident summarisation, resolution-note generation, change-request authoring), Now Assist for HRSD (HR case summarisation, knowledge-article generation), Now Assist for CSM (customer-case summarisation, response drafting), Now Assist for Creator (low-code development assistance), and the broader Now Assist platform capability. Each SKU is priced per user; the scoping decision is which user populations receive which Now Assist capability.
The buyer’s scoping position must run against the documented use cases. A Now Assist deployment that demonstrably reduces incident-handling time, accelerates HR case resolution, or improves customer-service response quality has a value frame. A Now Assist deployment that runs alongside the agent without measurable productivity improvement has no value frame and is a cost line the buyer carries without an offsetting saving.
The scoping pilot is the operational basis for the scoping decision. A ninety-day pilot, run inside a defined user population, with documented productivity metrics, is the substrate on which a scaled commitment should be sized. A Now Assist commitment sized to the seller’s narrative without the pilot evidence is a commitment the buyer will reduce or retire at the next renewal.
ServiceNow AI Agents, launched into the broader market in 2024 and aggressively expanded across the customer base in 2025-2026, represent the next layer of AI commercial expansion above Now Assist. The AI Agent product family is positioned as autonomous-workflow execution: agents that process work inside the platform without requiring a human fulfilment user.
The AI Agent commercial model runs on consumption-based units (agent-task units or a comparable denomination) priced per execution, with multi-year commitments shaped against forecast adoption. The commercial model represents a structural departure from the per-user model that has anchored the ServiceNow commercial relationship for two decades: the buyer is no longer licensing the human population; the buyer is licensing the work performed.
The commitment design must reconcile against the documented agent use cases. An AI Agent deployment that handles a defined work pattern (Tier 1 incident triage, standard change request execution, HR case routing) at a measured automation rate has a documented value frame. An AI Agent deployment positioned across the broader work portfolio without the use-case substrate is a commitment without a value frame; the consumption ramp the seller projects is the seller’s narrative, not the buyer’s documented forecast.
The interaction between AI Agents and the fulfilment-user count is the second commercial consideration. As agents take work that fulfilment users currently perform, the fulfilment-user count should reduce; if the renewal anchors the fulfilment count at the historical level alongside an AI Agent commitment, the buyer pays for both the agent and the human work the agent is replacing.
The annual SaaS uplift inside ServiceNow renewals has, across 2023-2026, ranged from seven to twelve percent on the prior-year subscription value. The uplift is positioned by the seller as a standard contractual term; in practice it is a negotiable line item that the buyer should contest explicitly at every multi-year renewal.
The contestation runs against three positions. The first is the benchmark position: comparable enterprise SaaS uplifts inside the buyer’s broader software portfolio (Microsoft, Salesforce, SAP, Oracle) typically run at three to seven percent for renewed terms with a measurable consumption increase. A ServiceNow uplift materially above the broader-portfolio benchmark is a contestable line.
The second is the commitment position: where the buyer is committing to a multi-year term with an aggressive ramp, an expanded module footprint or a substantial AI commitment, the uplift should be reduced or eliminated as a quid-pro-quo against the expanded commitment. The seller’s counter-position will assert that the uplift is structurally required; the counter-counter-position is the documented historical-renewal record from comparable Admodum engagements that demonstrates the uplift is, in practice, negotiable.
The third is the cap position: where the uplift cannot be eliminated, it should be capped at a defined percentage for the full multi-year term, with the cap documented as a contractual term, not as a side-letter assurance. An uncapped multi-year uplift is the seller’s preferred outcome; a capped multi-year uplift is the buyer’s minimum acceptable outcome.
Strategic Portfolio Management (SPM, the former PPM) and the adjacent App Engine, Customer Workflow and Field Service Management modules are the high-growth expansion lines the seller has prioritised across the recent renewal cycles. Each carries its own user-license category, its own commercial mechanics and its own deployment-readiness profile.
SPM is licensed by SPM-fulfilment user at a price point above the standard ITSM fulfilment user. The deployment pattern typically anchors to the IT-leadership population (portfolio managers, programme managers, project managers) and the financial-planning population (IT finance, demand managers). The reconciliation must run against the actual deployment population, with attention to the over-assignment pattern that places SPM users across populations that consume PPM-equivalent capability without requiring the full SPM scope.
App Engine is licensed by Custom Table entitlement and by App Engine User where the buyer’s low-code applications are deployed. The reconciliation must run against the actual count of custom tables in production, the actual count of low-code applications and the actual user population consuming each. App Engine entitlements that are licensed but not deployed are the most common shelfware category inside ServiceNow estates.
Customer Workflow and Field Service Management are operationally-aligned expansions that grow inside the renewal cycle where the buyer’s customer-facing or field-operations function adopts ServiceNow as the operating platform. The renewal-cycle reconciliation must run against the documented deployment and the operational adoption record, not against the seller’s growth projection.
The BATNA for the ServiceNow renewal is rarely a full ServiceNow exit. The platform’s integration footprint inside the enterprise IT estate, the workflow customisation, the data history and the broad user-population muscle memory make a full exit a multi-year programme with substantial transition cost. The BATNA is therefore typically a partial-substitution posture or a contained-growth posture.
The partial-substitution BATNAs run against specific module categories. The HRSD scope can in many estates be substituted by Workday HCM’s native case-management capability or by a specialist HR-service-delivery provider. The CSM scope can be substituted by Salesforce Service Cloud or by Zendesk for the customer-service population. The SecOps Vulnerability Response can be substituted by a specialist vulnerability-management vendor. The Strategic Portfolio Management scope can be substituted by Smartsheet, Planview or another PPM-specialist provider. The Customer Workflow scope can be substituted by the broader CRM stack or by a specialist workflow vendor.
The contained-growth posture is the BATNA the buyer holds where partial substitution is not operationally credible. The posture commits to the existing ServiceNow footprint at a defined scope, refuses the seller’s module expansion narrative, contests the AI commercial scope and holds the renewal envelope flat or marginally up against the rationalised footprint. The seller’s commercial response will calibrate to the credibility of the buyer’s posture: a contained-growth posture without substitution credibility is contested less aggressively than a contained-growth posture with documented substitution analysis behind it.
The ServiceNow renewal paper sits inside a broader infrastructure and platform reading list. The companion papers extend the methodology to adjacent commercial mechanics:
The methodology in this paper is the methodology Admodum has applied across thirty-eight ServiceNow renewal engagements inside the firm’s engagement history. Each engagement is structured as fixed fee, contingency / gainshare or annual retainer, depending on the buyer’s posture at the renewal window.
A senior Admodum advisor will walk the methodology through with your CIO, CFO, sourcing or platform-owner team on a private call. Engagements run as fixed fee, contingency or annual retainer.