Practice · VII.

ServiceNow. Renewal and module rationalisation.

The Now Platform renewal anchor, the fulfilment-user reconciliation, the workflow module consolidation, the Now Assist and AI Agents expansion, the SaaS contract uplift mechanic, and the multi-year discount design. Six commercial conversations that compound across the renewal window. Independent buyer-side advisory across the full ServiceNow estate. Module shelfware identified, fulfilment users reconciled, AI commitments scoped against documented use cases.

Speak with a Senior Advisor Engagement models

Where the practice intervenes

Six points on the ServiceNow contract cycle.

Pre-renewal

Estate reconstruction

Nine months before the renewal anchor, the ServiceNow estate is reconstructed across ITSM, ITOM, ITBM, HR Service Delivery, Customer Service Management, Security Operations, GRC, App Engine, and the Now Assist and AI Agents portfolio. Fulfilment users, requester populations, module entitlement and consumption metrics are mapped. The position paper governs the renewal commercial conversation.

Fulfilment users

ii.

User reconciliation

ServiceNow fulfilment-user classification across ITIL Pro, ITIL Approver, ITIL Lite and Requester populations is reconciled against documented usage. Reclassification opportunities are identified. Shelfware fulfilment seats are documented. The user position is filed before the renewal commercial letter is returned.

Module consolidation

iii.

Workflow rationalisation

Workflow modules are reconciled against documented adoption. Underused modules are identified. Consolidation opportunities between overlapping modules are documented. Module swap rights at the renewal anchor are negotiated against the prior-term commitment.

Now Assist / AI

iv.

AI consumption scope

ServiceNow Now Assist and the AI Agents consumption-based pricing is sized against documented use cases at workflow population level. Pilot scope, expansion criteria, dollarised business case and exit terms are documented before the AI commitment is approved.

Uplift contest

SaaS uplift response

The SaaS contract uplift mechanic is contested against documented usage and comparable-deal benchmarks across the firm's ServiceNow engagement book. The uplift is rejected in writing where the deployment has not expanded. Where the deployment has expanded, the uplift is negotiated against documented additional value.

Multi-year design

vi.

Closing contract terms

The renewal closes against a multi-year commitment with documented discount tiers, price protection on uplift, contraction rights, module swap rights and the renewal anchor terms. The closing contract is reviewed clause by clause. The senior advisor sits opposite the publisher's account team for the full negotiation.

Named senior advisor

The senior advisor named on the engagement letter leads every ServiceNow conversation. No leverage model, no rotation of junior consultants, no anonymous correspondence with the publisher. The advisor signs every position document.

II.

Counter-signed positions

Every written counter-position to ServiceNow is signed by the senior advisor and counter-signed by a second partner before transmission. Two named signatures on every position document for the full five-year retention period.

III.

Independent on every clause

Admodum holds no commercial relationship with ServiceNow. No reseller margin, no implementation partner referral, no Store placement. We do not work both sides.

IV.

Uplift is a position, not a default

The SaaS contract uplift mechanic is contested against documented usage and comparable-deal benchmarks. Where the deployment has not expanded, the uplift is rejected in writing. Where the deployment has expanded, the uplift is negotiated against documented additional value.

Five-year retention

Every position paper, counter-position, and closing memorandum is retained inside the firm for five years from engagement close. The buyer can request source workings at any point.

VI.

Reset the baseline every cycle

Every ServiceNow renewal closes with a written baseline reset. The closing position, the contractual amendments accepted, and the live obligations carried forward are tied into the next renewal preparation cycle through the Renewal Programme.

Operating principles

How the practice is run.

Uplift is a position, not a default.

The SaaS contract uplift mechanic is the publisher's default renewal posture. Without a documented position paper, the uplift becomes the closing position by inertia. The position paper contests the uplift in writing against documented usage and comparable-deal benchmarks.

Fulfilment user by population.

Fulfilment-user reconciliation is documented at workflow-population level. Different populations carry different entitlement needs. The right mix of ITIL Pro, ITIL Approver, ITIL Lite and Requester user types is documented per population with reclassification paths.

Module by adoption.

Workflow modules are reconciled against documented adoption. Underused modules are identified at workflow-population level. Module consolidation opportunities and swap rights at the renewal anchor are negotiated against the prior-term commitment.

AI with a documented exit.

Now Assist and AI Agents commitments are approved against a documented business case at workflow-population level, with documented expansion criteria and exit terms. The pilot population is named. The expansion criteria are dollarised. The exit terms are in the contract.

Questions

Asked before engagement.

What is the fulfiller versus requester distinction?

Only users who fulfil work in the platform need paid licences; requesters who raise and track their own items do not. Role misassignment quietly converts requesters into billable fulfillers, which is why a role reconciliation is the first step of every ServiceNow engagement.

How do we control the ServiceNow renewal uplift?

Benchmark the unit rates, consolidate overlapping modules, correct the fulfiller count, and contract an uplift cap. ServiceNow's multi-product subscriptions reward buyers who renegotiate the whole portfolio as one position rather than accepting per-line uplifts.

How is Now Assist priced?

As an AI add-on layered onto existing subscriptions, with packaging that has changed repeatedly. Scope it against named use cases and pilot telemetry, and keep the commitment separable from the core renewal so one negotiation cannot hostage the other.

How are engagements priced?

Three frameworks: fixed fee for scoped deliverables, contingency tied to verified savings, and an annual retainer for continuous coverage across every vendor. The model is agreed on the first call, which is always complimentary, and independence is warranted in writing on every engagement letter.