Most ServiceNow overspend traces back to one mistake: licensing people as fulfillers who only ever approve or request. Here is what each license type actually allows, what it costs, and how to right-size the mix.
The short answer: ServiceNow has three core access roles. A fulfiller works records and is the only paid per-user license — roughly $100–$185 per month depending on tier. An approver approves requests within a workflow and is generally included at no incremental per-user cost. A requester raises requests through the service portal and is also generally unlicensed at the per-user level. The cost mistake is licensing approvers and requesters as fulfillers.
ServiceNow's per-user economics rest entirely on the fulfiller count, so the question that decides your bill is not "how many people use ServiceNow" but "how many people genuinely fulfil work in it." In our work across 340+ enterprise engagements, the single most common ServiceNow finding is a population of named fulfillers who, on inspection, only ever approve or request. Each one is paid for at the full agent rate. Understanding the three roles precisely is the foundation of right-sizing.
A fulfiller is an agent who actively works records inside a ServiceNow product — creating, updating, resolving and reassigning incidents, problems, changes, cases or HR tickets. Fulfillers consume the bulk of the platform's write capability, and they are the only role that carries a per-user subscription fee. The fulfiller rate is set by the package tier on the product they work in (ITSM Standard, Professional or Enterprise, for example), which is why the ServiceNow pricing tiers matter as much as the headcount. Every fulfiller you license at Enterprise when Professional would do compounds the same way an extra agent does.
An approver participates in a workflow by approving or rejecting a request — a manager signing off a hardware order, a change advisory board member endorsing a change. Approver access is generally included with no incremental per-user fee, because approving is not the same as fulfilling. The trap is operational: organisations frequently grant a fulfiller role to managers so they can "see everything," when an approver role and a few reports would meet the need. Those convenience grants are billed as fulfillers. Reclassifying them is often the fastest ServiceNow saving available.
We reconcile licensed agents against actual fulfilling activity and reclaim the difference.
A requester is an end user who raises requests through the employee or service portal — ordering equipment, logging an issue, submitting an HR query. Requester access is generally unlicensed at the per-user level; it is the broad base of the organisation interacting with ServiceNow without working records. For the large majority of employees, requester is the correct and sufficient role. Problems arise only when self-service portals are configured to require elevated access, quietly pushing requesters toward fulfiller-grade licensing they do not need.
The table below summarises the practical differences. Use it to audit your own user population: anyone who is not genuinely fulfilling work is a candidate for reclassification.
| License type | What it allows | Typical per-user cost | When to use it |
|---|---|---|---|
| Fulfiller | Create, update, resolve and reassign records across assigned products | $100–$185 / mo (tier-based) | Genuine agents working tickets day to day |
| Approver | Approve or reject requests within a workflow | Generally included | Managers and CAB members who sign off, not fulfil |
| Requester | Raise and track requests via the service portal | Generally unlicensed | The broad employee base interacting with self-service |
ServiceNow fulfiller benchmarks by tier, plus the reclassification playbook for trimming the agent count.
Right-sizing is a reconciliation exercise. Pull the list of named fulfillers and overlay it with actual fulfilling activity from the platform — records touched, not just logins. The fulfillers with no real write activity over a representative period are the reclassification targets: move them to approver or requester roles and remove the paid license. Then check the tier: where Enterprise was sold but only Professional features are switched on, the downgrade is a second layer of saving. This is the core of a license optimization engagement, and it sits directly underneath the cost model described in the ServiceNow pricing breakdown. The same role-versus-cost discipline shows up across vendors — Oracle's named-user model has an equivalent trap, covered in our Oracle named-user licensing guide — and the ITSM-specific detail lives in the ServiceNow ITSM licensing guide.
Our ServiceNow practice reconciles licensed agents against real fulfilling activity and right-sizes the mix — buyer-side only.
Weekly compliance intelligence for IT leaders.