Multi-workflow estates are where fulfiller counts quietly multiply. Consolidating onto one platform is sold as efficiency, and it can be, but the licensing does not consolidate unless you make it. Left alone, the count grows by workflow rather than by person, and a 1,000-person organisation can be billed for two or three thousand fulfiller positions. The wider expansion context is in our buyer guide to ESM expansion pricing, HR, CSM and beyond; this piece is the right-sizing method.
Book a contract negotiation review →What does right-sizing fulfillers across workflows mean?
It means each person is counted against the workflows they genuinely fulfill work in, not against every workflow they can technically open. An HR business partner who resolves HR cases is an HR fulfiller. If that same person can also see the IT queue but never works it, they are not an ITSM fulfiller, and licensing them as one is waste. The exercise is reconciling real fulfillment activity, workflow by workflow, against the seats you are being charged for.
Where does the double-count come from?
From access being mistaken for use. When workflows share a platform, granting someone visibility into a second or third workflow is trivial, and the licensing often follows the access rather than the activity. The vendor has no incentive to challenge a generous count. So a person with login rights to ITSM, HR and CSM gets billed across all three, even if they only ever fulfill in one. The fix is to separate who can access from who actually fulfills, and license the second, not the first. The double-pay trap when extending into HR and facilities is detailed in avoiding paying twice when you extend ITSM to HR and facilities.
How do I count each person correctly?
The table is the reconciliation frame. Build it per person, across workflows, before the renewal quote lands. Packaging and shared-license rules vary by deal size, so confirm specifics against your order form.
| Person type | Workflows accessible | Correct fulfiller count |
|---|---|---|
| IT analyst resolving IT tickets | ITSM only | One, in ITSM |
| HR partner who can view IT queue | HR and ITSM | One, in HR (no ITSM fulfillment) |
| Manager who approves but never fulfills | Several, read and approve | Zero fulfiller seats, approver or requester role |
| Field tech who also logs IT issues | FSM and ITSM | One, in FSM (logs IT as a requester) |
| Cross-functional lead fulfilling two workflows | ITSM and CSM, both worked | Two, or a shared seat if the model allows |
What are the steps to right-size across workflows?
- Pull the fulfiller list per workflow. Get the actual licensed count in ITSM, HR, CSM and FSM separately, with names.
- Match names across workflows. Find every person counted in more than one workflow and check whether they fulfill in each or merely access it.
- Reclassify access-only users. Move approvers, viewers and occasional users to requester or approver roles, which are not fulfiller seats.
- Apply reseat discipline. Reassign seats from leavers and movers rather than buying new ones, so the total holds flat as people change roles.
- Quantify the duplication. Put a figure on the seats removed so the case is financial. The method is in quantifying ESM shelfware across workflows, and the FSM-specific version is in ServiceNow Field Service Management cost control.
- Lock the count and cap the uplift. Take the reconciled count into the renewal and cap the annual increase so the saving survives.
Our gated ITSM license optimization field guide includes the per-person reconciliation worksheet and the reseat tracker that keep multi-workflow fulfiller counts honest between renewals.
Why this is the highest-yield ESM move
Right-sizing fulfillers is the lever with the most room in a multi-workflow estate, because the duplication is structural rather than occasional. Cutting it does not reduce capability; every person who needs to fulfill still can. It only removes the seats you were paying for twice. Across more than 500 ITSM engagements since 2019, covering over $420M of contract value, the firm averages a 30% reduction, and per-person reconciliation across workflows is one of the most repeatable sources of that number.
When you are ready, the engagement runs through our contract negotiation service on fixed fee or gainshare, with the full account context on the ServiceNow platform page.
What mistakes recur when right-sizing across workflows?
Four errors show up often enough to name. The first is licensing access instead of activity. The fact that someone can open the CSM queue does not make them a CSM fulfiller, yet the count frequently follows the permission rather than the work. Strip access-only users back to requester or approver roles before you do anything else; it is usually the largest single cut. The second is ignoring movers. People change roles constantly, and a fulfiller who moved from IT to a non-fulfilling position six months ago is still being billed unless reseat discipline reclaims the seat. A live reseat tracker keeps the count flat as the organisation churns.
The third mistake is treating the count as a one-off project. Right-sizing at renewal and then letting the count drift for three years gives most of the saving back. The reconciliation has to be a standing process, run at least quarterly, so the next renewal opens from a clean number rather than another inflated one. The fourth is negotiating the count without capping the uplift. A reconciled base that then escalates at an uncapped annual rate erodes inside two cycles, which is why the cap is part of the same conversation, not a separate one.
The thread through all four is that fulfiller spend is governed continuously, not annually. The renewal is where you lock the number and the cap; the quarters in between are where reseat discipline and access hygiene keep that number from quietly climbing back. Buyers who treat it as ongoing housekeeping hold the saving; buyers who treat it as a one-time clean-up watch it return.
Frequently asked questions
- What does right-sizing fulfillers across workflows mean?
- Counting each person once against the workflows they genuinely fulfill, rather than licensing them as a full fulfiller in every workflow they can access. On a shared platform the same person is easily counted several times.
- Can one fulfiller license cover multiple workflows?
- It depends on the model and tier, and packaging varies by deal size. The goal is to avoid paying for the same person multiple times for access they do not use. Where a shared or reseat model exists, use it.
- What is the fulfiller reseat lever?
- Reassigning a seat from a leaver or mover to someone who needs it instead of buying new. Disciplined reseating keeps the count flat as roles change, protecting the saving between renewals.
Count each person once.
We reconcile fulfillers per person across ITSM, HR, CSM and FSM, reseat rather than rebuy, and cap the uplift so the saving holds. Fixed fee or gainshare.
Book a contract negotiation review →