Here is the short version. Consumption pricing moves the risk from the vendor to you, because you commit to a volume up front and pay overage top-ups if you exceed it. Forecast too high and you over-commit cash to assists you never burn; forecast too low and you expose yourself to overage at a worse unit rate. The buyer-side answer is to estimate assists bottom-up from the actions you actually plan to automate, then size a base commitment to that evidence. This sits in our ITSM total cost of ownership calculators toolkit, the buyer's set of models for pricing a deal.
Sizing a Now Assist commitment this cycle? Book a contract negotiation review and we will model your assists and cap the overage before you commit.
How is Now Assist consumption actually measured?
Now Assist is metered in assists, a consumption unit rather than a per-user licence. As of 2026 guidance, a smaller action such as a summary, a suggested response or a knowledge lookup consumes on the order of 25 assists, while a larger agentic action that completes a multi-step task can consume around 150. These numbers are indicative and depend on the action and configuration, so confirm the current consumption table against your order form rather than treating any single figure as fixed. Now Assist is positioned in the higher ServiceNow tier following the 2026 packaging change, so the consumption model arrives alongside a tier decision, which is covered in our wider ServiceNow platform analysis.
How do you estimate assists from your own data?
Build the estimate bottom-up, action by action, so the forecast rests on your ticket volumes rather than the vendor's enthusiasm. The method below is the one we run with buyers.
- List the actions you will automate. Summaries, agent assist replies, knowledge generation, and fully agentic resolutions are different sizes, so keep them separate.
- Pull the monthly volume of each action from your incident and request data, not from an aspiration.
- Apply an assist size per action using the consumption table, smaller actions at the lower figure and agentic actions at the higher.
- Multiply and sum to a monthly assist total, then annualise.
- Apply an adoption ramp. Usage in month one is not usage in month twelve, so model a curve rather than full adoption from day one.
A worked sizing illustration
The figures below are illustrative placeholders to show the method, not ServiceNow pricing. Replace the volumes with your own and the assist sizes with the current consumption table.
| Action type | Monthly volume (your data) | Assists per action (indicative) | Monthly assists |
|---|---|---|---|
| Incident summary | example: 4,000 | ~25 | ~100,000 |
| Agent assist reply | example: 2,000 | ~25 | ~50,000 |
| Agentic resolution | example: 400 | ~150 | ~60,000 |
| Indicative monthly total | ~210,000 |
Annualised with an adoption ramp, that monthly total becomes the base you size the commitment against. The point of the table is the structure, not the numbers: real volumes and the current consumption rates are what you confirm against your order form before you commit a single dollar.
How do you cap the downside on a consumption deal?
Treat the commitment like any other multi-year cash exposure and put guardrails on it. Negotiate a right-sized base rather than the vendor's headline volume, a capped overage rate so unexpected usage does not price at a premium, a true-up mechanism instead of an automatic upsize, and a re-price point once you have real consumption data. Start below the vendor's proposed volume, because adding assists later with evidence is far easier than recovering an over-commitment. The broader benchmark context for AI add-on pricing across vendors is in 2026 ITSM AI add-on pricing benchmark data.
Our gated ServiceNow Now Assist Cost Control Guide includes the full assist-estimation worksheet and the overage-cap language behind this article.
What to do next
Pull your incident and request volumes, list the actions you will actually automate, and build the assist estimate before the vendor proposes a number. Then size the base low, cap the overage, and set a re-price point. We model Now Assist consumption and negotiate the commitment for ServiceNow buyers on fixed fee or gainshare through our contract negotiation service, and since 2019 the firm has negotiated more than $420M in ITSM contract value at a 30% average reduction.
Frequently asked questions
- How is ServiceNow Now Assist consumption measured?
- In assists, not per user. A smaller action runs roughly 25 assists and a larger agentic action around 150. These are indicative and vary by action, so confirm the current consumption table against your order form.
- Why should I model assists before buying Now Assist?
- Because the price is a volume forecast. Too high over-commits cash; too low exposes you to overage. Estimating from your ticket data sizes the commitment to evidence.
- How do I cap the risk on a Now Assist commitment?
- Right-size the base, cap the overage rate, use a true-up rather than an automatic upsize, and set a re-price point. Start lower than the vendor proposes.
Book a contract negotiation review.
We model your assists from real ticket data, size the base and cap the overage before you sign. Fixed fee or gainshare.
Book a contract negotiation review →