Why Now Assist exists.
Now Assist is the umbrella for generative AI capability across the Now Platform. The capability is delivered as a Pro Plus tier upgrade across the existing module SKUs (ITSM Pro Plus, CSM Pro Plus, HRSD Pro Plus, SecOps Pro Plus) and, more recently, through a separate AI Agents tier with its own consumption metric.
The construct is deliberate. ServiceNow is unwilling to expose the generative AI capability outside the commercial relationship, and unwilling to bundle it into the base Pro tier without an additional commitment. The Pro Plus construct allows ServiceNow to position the AI capability as an upgrade with its own price step, and allows the customer to take the upgrade as a discrete decision at the renewal date.
The buyer position at the table needs to be informed by three understandings. Firstly, that Now Assist is sized at the user count of the underlying Pro module, not at the actual AI consumption. Secondly, that the AI Agents tier carries a separate consumption metric that operates alongside the Pro Plus subscription. Thirdly, that the Now Assist proposal is typically presented at the same renewal cycle as the underlying module renewal, and that the two negotiations are commercially intertwined.
This paper sets out the buyer position across the three understandings, in the order they are typically encountered inside a ServiceNow engagement.
The Now Assist SKU shape.
Now Assist is delivered through five principal SKUs at the Pro Plus tier and a separate AI Agents tier. Each Pro Plus SKU is an upgrade from the corresponding Pro SKU; the upgrade price-step is the cost of the AI capability for the module.
Now Assist for ITSM (ITSM Pro Plus). Generative AI for IT Service Management. Capabilities include incident summarisation, agent assist, virtual agent natural-language understanding upgrades, knowledge base generation and resolution recommendations. Sized on the fulfilment-user count of the underlying ITSM Pro module.
Now Assist for CSM (CSM Pro Plus). Generative AI for Customer Service Management. Capabilities include case summarisation, agent assist, customer-facing AI on the portal, sentiment analysis and field-service work-order generation. Sized on the agent count of the underlying CSM Pro module.
Now Assist for HRSD (HRSD Pro Plus). Generative AI for HR Service Delivery. Capabilities include case summarisation, employee virtual-agent upgrades, knowledge generation and onboarding workflow. Sized on the HR fulfilment-user count of the underlying HRSD Pro module.
Now Assist for SecOps and IRM (SecOps / IRM Pro Plus). Generative AI for Security Operations and Integrated Risk Management. Capabilities include incident summarisation, control evidence generation and risk-narrative drafting. Sized on the fulfilment-user count of the underlying SecOps or IRM Pro module.
Now Assist for Creator (Creator Pro Plus). Generative AI for the platform developer. Capabilities include flow generation, scripting assistance, table-design recommendations and test-case generation. Sized on the developer count or the platform user-band, depending on the contract construct.
The five Pro Plus SKUs sit alongside the AI Agents tier, which carries a separate consumption metric. The AI Agents tier is treated in Section IV.
User-band sizing.
The Now Assist Pro Plus SKUs are sized at the user-band of the underlying Pro module. The user-band construct prices in discrete steps as the user count crosses each threshold; the price between thresholds is constant.
The user count is contested. The ServiceNow position is, typically, the maximum user count recorded across the trailing year; the buyer position is, typically, the average user count or the active user count at the renewal date. The methodology Admodum applies inside a Now Assist sizing engagement is set out below.
- Establish the fulfilment-user count from the underlying Pro module. The fulfilment-user definition is set out in the companion fulfilment-user reconciliation paper. The starting point for Now Assist sizing is the fulfilment-user count established for the Pro module.
- Identify the leavers and joiners across the trailing twelve months. Apply the leaver list to the trailing maximum; apply the joiner list with the start date for each.
- Project the user count across the renewal term, accounting for organic growth, planned hiring, retirements and any known restructuring. The projection should be honest about both growth and decay.
- Identify the user-band thresholds and position the user count at the renewal date below the next threshold by a small margin. Where the projection crosses a threshold mid-term, the price-step should be negotiated into the contract as a known event rather than a surprise at the next renewal.
- Lock the user-band at the renewal date with a forward-looking growth clause that prices the threshold cross at a defined rate, rather than at the table-walk rate.
The discipline is straightforward and is the single most economically productive piece of work the buyer can do in the lead-up to the Now Assist renewal. The cost of doing the work is small; the price-step on a single threshold cross can be material.
AI Agents and the consumption metric.
The AI Agents tier sits alongside Now Assist. AI Agents are autonomous workflows that the customer configures to perform multi-step tasks across the Now Platform; the configuration is performed in the AI Agent Studio and the runtime consumption is metered separately from the user-based Pro Plus subscription.
The consumption metric for AI Agents has been positioned by ServiceNow as a per-agent or per-conversation metric depending on the contract construct. The metric is contentious; it does not map cleanly to operational capacity planning, and the customer’s ability to project consumption at the renewal table is limited until production deployment is well-established.
The buyer position at the AI Agents negotiation should be informed by three considerations. Firstly, the consumption commitment should be sized to the expected production consumption, not to the marketing target. Secondly, the commitment should be structured with a ramp across the renewal term, not a flat commitment on day one. Thirdly, any unused commitment should carry forward, or the commitment should be sized such that the unused volume is small. The shape of these guardrails is identical to the shape of the Azure MACC guardrails, set out in the Azure MACC paper.
The reading list at the end of this paper draws the parallel to the Microsoft Azure Consumption Commitment, the AWS EDP and the OpenAI / Anthropic enterprise commitment constructs. The AI Agents commitment design is, commercially, of the same family.
The included value position.
The Pro Plus tier carries an included value position that is worth understanding before the negotiation opens. Each Now Assist for {module} subscription includes an included quota of generative AI capability for the named module. The quota is published; the quota varies by module; the quota is rarely exhausted in normal operations.
The buyer position should be that the included quota is the included value for the period; that overage charges are not assumed; and that the negotiation focuses on the per-user price-step rather than on the included quota. Where the quota is a meaningful constraint on a specific deployment, the constraint should be negotiated into the contract explicitly, rather than left to be discovered after deployment.
The upgrade path from Pro to Pro Plus is, by ServiceNow design, a one-step movement. Pro Plus is not available without Pro; Pro Plus replaces Pro at the upgrade price-step rather than being added alongside it. The construct simplifies the procurement and contains the negotiation to a single price step per module.
The relative-discount construct is the second consideration. ServiceNow typically presents Pro Plus at the same percentage discount as the underlying Pro module. The buyer position should be that Pro Plus is a discrete decision and should carry its own discount discipline, rather than being anchored on the Pro discount; the relative-discount framing is a procurement convenience for ServiceNow, not an economic logic for the buyer.
The pilot-to-production transition.
Now Assist is, in most ServiceNow estates, in a pilot or early-production state. The pilot has been delivered through a defined user count on a defined module, the use cases have been demonstrated, the proof of value has been written, and the decision to move from pilot to production is being prepared.
The commercial overhang from pilot to production is the single most expensive moment in the Now Assist journey. The pilot has typically been priced on a heavily discounted basis, with a short-term commitment, on a discrete user count. The production deployment is priced at the standard Pro Plus rate, on the full module user-band, with a multi-year commitment. The transition is a step-change in cost, often disguised by the standard renewal cycle.
The buyer guardrails at the pilot-to-production transition are three. Firstly, the pilot terms should be read carefully at the front of the pilot, not at the end; the production conversion mechanic should be agreed before the pilot opens. Secondly, the production user-band should be sized using the methodology in Section III, not on the assumption that the pilot user count is the basis. Thirdly, the production commitment should be structured with a ramp, not a flat commitment on day one.
The Admodum experience is that buyers who treat the pilot as a free trial and the production conversion as a procurement formality typically pay a meaningful premium across the production deployment. The discipline is to treat the pilot as the first step of the production commercial negotiation.
The renewal posture.
The Now Assist renewal sits inside the Now Platform renewal. The Pro Plus subscriptions renew on the same anniversary as the underlying Pro modules; the AI Agents commitment renews on its own anniversary or on the platform anniversary depending on the contract construct.
The twelve-month preparation cycle for the Now Assist renewal runs alongside the platform renewal preparation. The fulfilment-user reconciliation work for the Pro module is the first input; the Now Assist user-band sizing follows from it. The AI Agents commitment design runs in parallel; the consumption projection should be informed by the trailing twelve months of production consumption.
The BATNA position for Now Assist is more limited than for the underlying platform; the AI capability is delivered through the Now Platform and the natural alternative is not a different AI vendor but a downgrade to Pro without the Pro Plus tier. The BATNA is therefore a credible decision to forgo the AI capability for selected modules; the BATNA is sharpened where the AI capability has not been deployed at meaningful scale on those modules.
The renewal anchor for Now Assist is the per-user price-step delta between Pro and Pro Plus, benchmarked against comparable peer engagements (which Admodum can supply from the Benchmarking Programme). The anchor should be defended on the face of the benchmark and on the face of the deployed-use evidence, not on the face of the published list price.
Reading list and references.
This paper sits alongside three companion Admodum papers and the ServiceNow practice page.
The ServiceNow fulfilment-user reconciliation paper covers the underlying Pro module user-count discipline. The methodology established there is the starting point for the Now Assist user-band sizing in Section III of this paper.
The Azure MACC design and defence paper covers the commitment-versus-discount framing across the Microsoft consumption commitment. The AI Agents commitment design carries the same commercial DNA; the guardrails are the same shape.
The Workday renewal preparation paper covers the parallel SaaS renewal discipline at Workday, including the Illuminate AI commercial scope. Read alongside this paper where the buyer is preparing across both Workday and ServiceNow renewals on a shared timeline.
For the ServiceNow practice itself, see the ServiceNow practice page and the ServiceNow Knowledge Hub. For the engagement model, see fixed fee, contingency or annual retainer. For the programme that closes the renewal, see the Renewal Programme; for the benchmark that anchors the renewal price, see the Benchmarking Programme.
