One product counts every employee, the other counts only the people who work cases, and the buyer moves invert accordingly. Three knowledge checks along the way, and 3 clips from a senior licensing analyst.
This is a taught session, not a talking head. The instructor works through analyst grade slides, and three times the video stops on a question with four options on screen. Pause, commit to an answer, and the next slide explains which option is right and why each of the others is wrong. 3 times in the session the frame splits and a senior licensing analyst gives the view from inside real ServiceNow negotiations, and the instructor picks the clip apart when the slides return.
The full narration of this session, section by section, for reading and reference. Guest analyst clips are marked.
Welcome back. Session nineteen, and this one is a deliberate pairing, because HRSD and CSM are the two products in the catalog that sit closest together in the sales story and furthest apart in the licensing. Both are service delivery. Both have cases, portals, knowledge bases, agents. Everything about them looks parallel. And they price on opposite units. HRSD counts every employee you have, whatever they do, whether they log in or not. CSM counts only the people who actually work cases. Which means the instinct that saves you real money on one of them costs you real money on the other, and I have watched competent buyers walk into an HRSD negotiation carrying the CSM argument and get precisely nowhere with it, politely, for an hour. So today we separate them properly. Three checks, homework at the end, and by the finish you should never mix these two up again.
Five objectives. First, separate the two units cleanly, per employee against per fulfiller, and understand that this is not a detail, it decides which conversation you are even allowed to have. Second, scope the workforce, because in HRSD the definition of employee is the negotiation, and opening proposals ran ten to twenty five percent above the defensible count in the estates we looked at. Third, hold the CSM boundary, which means routing occasional contributors through requester and portal flows instead of licensing them, because deflected work costs nothing per seat. Fourth, test both tier ladders on measured production use of the differentiating features, which is the same test we ran on ITSM in session sixteen, applied to two more products. And fifth, time the attachment, because both of these negotiate materially better inside a platform renewal than bought standalone in the middle of a term, and that timing decision is usually made by somebody who does not know it is a pricing decision.
Four numbers to frame it. Everyone, which is HRSD's unit, priced per employee across your whole workforce on the logic that any employee could raise an HR case, so the fulfiller model does not apply at all and there is no active user count to right size. Ten to twenty five percent, how far opening workforce definitions ran above the defensible employee count once somebody actually scoped it, which tells you the definition is where the money is. Fifteen to thirty percent, how far CSM fulfiller counts ran above measured active case workers, inflated by a gray zone of people who touch a case occasionally and got a seat because it was easier. And zero dollars, which is what customers, requesters, portal visitors, and virtual agent interactions cost you per seat in CSM. That last one is not a footnote. Deflection is free capacity, and almost nobody prices its absence.
Guest analyst clip. The HRSD conversation I remember most clearly went badly for about forty minutes and then turned completely, and the turn came from a single question. The customer was a manufacturer, and the quote priced somewhere north of thirty thousand employees. They had come in ready to argue about adoption, because adoption was low, and they were getting nowhere, correctly, because adoption is not what the meter counts. So I asked where the thirty thousand came from. It came from an HR headcount export. And when we opened that export it contained the entire contractor population, several thousand people, who received their HR services from their own employers, not from this customer at all. It contained a seasonal workforce counted at Christmas peak rather than at annual average. And it contained two subsidiaries in another country running their own HR systems entirely. Nobody had done anything wrong. Somebody had been asked for a headcount and had produced an accurate headcount. It just was not a licensing population. My advice, and it applies to every per employee product you will ever buy, is that before you argue about the price you argue about the population, because a good unit price on the wrong population is a bad deal that looks like a win.
Before you argue about the price, argue about the population. And notice how that headcount export got produced, because somebody asked HR for a number and HR gave them a true number. That is the same pattern as every other session in this course. The data is accurate and it is answering a different question from the one the contract asks. Let's do HRSD properly.
Four rows, and I want you to read them as a set because together they say something uncomfortable. The unit is per employee across the workforce, on the reasoning that any employee can raise an HR case, so your headcount is the bill and the size of your HR team is completely irrelevant to the price. The fulfiller model does not apply, at all, which means the audit we spent all of module three building does not help you here. There are two negotiations, the definition of employee and then the price per unit, and the order matters enormously, because a lower unit price applied to an inflated population is a poor trade that presents itself as a discount. And the shelfware risk is the sharpest on the whole platform, because you are paying per employee for a portal that may or may not get used, and that bill scales with your headcount rather than with your adoption. Hire a thousand people and your HRSD cost goes up whether or not a single one of them opens it.
So here is the definition conversation, five populations, every one of them arguable in good faith. Contractors, do they consume HR services from you or from their own employer, and there is a defensible answer either way depending on how you actually operate, which is worth real money at a hundred people, let alone at several thousand. Seasonal and temporary staff, counted at peak or at average, and a retailer with a Christmas workforce has a completely genuine argument about which of those numbers describes their year. Subsidiaries and joint ventures, in scope or licensed separately, and does the entity structure in the contract match how HR services actually get delivered on the ground. Non desk and deskless workers, populations with no platform access whatsoever who nonetheless appear in every headcount export ever produced. And then the fifth one, which is the one that saves you doing this again. Whatever you agree, the definition goes into the order form in writing, with the version discipline from session four, because if it lives only in an email then next year's headcount export re-opens the entire argument and you will not win it twice.
Knowledge check one. Your HRSD quote prices twenty four thousand employees. Your HR team is sixty people, and portal adoption sits at fifteen percent. Which of those facts reduces the bill? A, the sixty person HR team, since they are the actual users. B, the fifteen percent adoption, since most employees never log in. C, neither directly, only the workforce definition and the unit price move it. D, both, weighted by usage. Pause here, and ask yourself what the meter actually counts.
The answer is C, neither directly. Per employee means per employee. The sixty person HR team in answer A is the fulfiller instinct, imported from a product that prices differently, and it is the single commonest thing buyers say in their first HRSD meeting. The fifteen percent adoption in answer B is the activity instinct, also imported, also wrong here, and I want to be careful about this one because low adoption is a completely real problem. It is just not a licensing lever. It is the value question sitting behind the licence, and it is exactly what makes HRSD the most expensive shelfware available on this platform, because unlike everything else the bill grows with headcount rather than with use. What actually moves the number is which twenty four thousand people are defensibly your employees, and then what each one costs. Definition first, unit price second, in that order, every time.
Now flip completely, because CSM prices per fulfiller and everything inverts. Four populations. Agents working cases daily in the workspace, clearly licensed fulfillers, and that is the measured core you build your count on. Engineers and field staff who occasionally update a case, and that is the gray zone, the population that inflates counts, and the buyer move is routing them through requester and virtual agent flows so they need no seat at all. Back office users touching cases monthly, also gray zone, and the move there is auditing against the ninety day activity threshold before you renew rather than after. And customers, requesters, and portal visitors, unlicensed always, which means you should deflect work to them deliberately because it is free capacity. Now the note underneath. Fulfiller counts ran fifteen to thirty percent above measured active case workers in the majority of estates we reviewed, and the drift that produced that is gradual and invisible. Nobody ever decided to over license. It happened one reasonable request at a time over three years.
Knowledge check two. Forty field engineers update customer cases roughly twice a month each. What is the structural answer? A, license all forty as fulfillers, the access is real. B, route their updates through requester and virtual agent flows and license none of them. C, license twenty and share the accounts. D, license them at a discounted occasional user rate. Pause here, and ask yourself whether this is a licensing problem or a workflow design problem.
The answer is B, route them, and this is the core idea of the whole session. The structural answer to occasional contributors is routing, not generous licensing, because deflected work consumes no fulfiller seats whatsoever. Answer A is exactly how the fifteen to thirty percent inflation happens, one entirely reasonable decision at a time, and every single one of those decisions was defensible in the moment. Answer C is account sharing, which breaches most agreements and swaps a cost problem for a compliance problem, which is a bad trade in both directions. And answer D is asking for a rate instead of solving the design question underneath it, which is the most seductive of the four because it feels like negotiating. Design the workflow boundary first, license the measured population second. If you only take one sentence from today, take that one.
Which brings us to deflection, and the framing I want on this slide is that in CSM the cheapest seat is the one you never need. Four paths. The portal, where the customer resolves it themselves at no seat cost, which makes deflection rate a commercial metric and not just a service one. Communities, peer resolution, also free of seats, and dramatically under used by most estates precisely because nobody has ever put a price on its absence. Virtual agent, automated resolution before a case reaches a queue at all, drawing on the assist pool we built in module two rather than on a seat. And requester flows, the route for occasional internal contributors, which is what stops a twice monthly update ever justifying a full seat for anybody. Every one of those is a workflow design decision made by service designers, and every one of them has a licence price attached that the service designers have never been told about.
Guest analyst clip. I sat in a room once where a customer experience team presented their deflection improvement programme, and it was genuinely good work. They had taken portal self service from about eighteen percent to just over forty percent of contacts over eighteen months. Knowledge articles rewritten, the search fixed, virtual agent handling the top twenty intents. They presented it as a customer satisfaction story, because that is what they were measured on, and it was one. What nobody in that room had done was put the licensing number next to it. Because at forty percent deflection they were resolving a very large volume of contact without a fulfiller ever touching it, and their fulfiller count had held flat through a period when case volume grew substantially. That is a licence line that did not grow. When we worked it through, the deflection programme had prevented a seat expansion worth more than the programme cost, and nobody had ever claimed that benefit, because the people who did the work were not measured on licence spend and the people measured on licence spend never heard about the work. My advice is very simple. If you run CSM, get your deflection rate into the same report as your fulfiller count, and put them in front of the same person. The two numbers are the same conversation and almost every organisation I see keeps them in different buildings.
Get your deflection rate and your fulfiller count into the same report, in front of the same person. And notice the shape of that story, because it is the good version of the gap we keep finding. Usually the gap costs you money quietly. That time it saved money quietly and nobody got the credit. Now, the tier ladders, because both of these products have one.
Both products tier, and the good news is that the test is identical. HRSD has a core tier centred on HR case management and knowledge, and a higher tier covering the full employee journey suite, and estates frequently carried the higher tier for populations whose actual usage justified the core one. CSM has a steeper step, with the advanced workspace, AI, predictive intelligence, and process mining sitting above the base, and fewer than half of the estates we saw on Professional were demonstrably using the differentiators they were paying for. One test for both, and it is the session sixteen test. Measured production use of the specific features that separate the tiers, over a defined period. Availability is not use. A roadmap is not evidence. And here is the reframing that does the work. A year of no use is a downgrade case, not a maturity journey, and the moment you say it that way out loud an uncomfortable observation becomes a negotiating position. Same method as ITSM. The products differ, the test does not.
Knowledge check three. You need to add CSM mid term, nine months before your platform renewal. What does the timing cost you? A, nothing, module pricing is independent of the platform deal. B, materially, because both HRSD and CSM negotiate better attached to a platform renewal than standalone mid term. C, only the co-terming, which is administrative. D, nothing, if you secure a good discount on the module itself. Pause here, and ask where the vendor actually has room to move.
The answer is B, materially. HRSD attached to a platform renewal negotiated fifteen to thirty percent better than the same product bought standalone mid term, and the CSM line moves further inside the larger deal for exactly the same structural reason. ServiceNow has more room on a bigger transaction with a competing moment attached to it, and mid term you have removed both of those things yourself. Answer A treats modules as independent when the discount structure is anything but. Answer C mistakes a pricing event for an administrative one. And answer D is the real trap, the one I see most often, because a good discount on a standalone module is measured against a list price you would never have paid inside the platform deal anyway. You can feel like you negotiated hard and still have paid more than the buyer who waited nine months and said nothing.
Let me put the two products side by side through one frame, because the divergence is the thing to remember. What is counted. HRSD, every employee whatever they do. CSM, only the people who work cases. One is a scoping problem, the other is a classification problem. Where the saving lives. HRSD, in the workforce definition. CSM, in the fulfiller boundary and in deflection. Nothing transfers between them, which is the whole reason for teaching them together. What evidence wins. HRSD, entity and employment scoping. CSM, ninety days of fulfiller activity, which cut line spend ten to twenty five percent for the buyers who actually brought it to the table. And what both share, which is worth holding on to. The tier test on measured use, a capped uplift, and attaching to the platform renewal rather than buying mid term.
Guest analyst clip. There is a decision that gets made in almost every organisation I work with, and it is made by somebody with no reason to know it is a pricing decision. A business unit wants a product. HR wants HRSD, or the customer service director wants CSM. They have budget, they have a business case, they want it live this quarter. And somebody in procurement, doing their job well, goes and gets a quote and negotiates it hard and buys it. Nine months later the platform renewal comes around and that product is now an existing line in the estate, priced, signed, and completely outside the negotiation. What has happened is that the customer spent their leverage on the smaller transaction. Inside the renewal, that module would have been part of a much bigger conversation with a genuine competing moment attached to it. Standalone, it was a transaction ServiceNow could take or leave. Now I am not telling you to make the business wait nine months for something they need, that is not always a real option and it is not always the right call. What I am telling you is that somebody should say the sentence out loud before you buy. If we wait until the renewal, this line is worth this much less. Sometimes the answer is still buy it now, and that is fine, because at least it was a decision. Most of the time nobody says the sentence at all.
Somebody should say the sentence out loud before you buy. And that is a governance fix rather than a negotiation skill, which is a theme running through this whole course. Session twenty closes module four with the specialist estate, SecOps and IRM, where the metrics diverge again and connectors carry a cost most buyers genuinely never see coming.
Three sentences. HRSD prices per employee across the whole workforce because any employee can raise a case, so the fulfiller audit does not help you and the workforce definition carries the entire negotiation, with opening proposals running ten to twenty five percent above the defensible count. CSM prices per fulfiller, counts ran fifteen to thirty percent above measured active case workers, and the structural answer to occasional contributors is routing rather than licensing, because portal, community, and virtual agent resolution costs nothing per seat. And both tier on features that fewer than half of buyers can demonstrate they use, both reward ninety days of activity evidence, and both negotiate materially better attached to a platform renewal than bought standalone in the middle of a term.
Homework, about an hour, five items. Define your workforce, which means if you hold HRSD write down which populations sit inside the licensed count and whether contractors, seasonal staff, and subsidiaries were ever actually discussed or just included. Measure HRSD adoption, what share of employees opened the portal last quarter, and treat that as the value question behind the licence rather than a lever on it. Pull ninety days of CSM activity, case work per fulfiller, and mark everyone below the threshold as a gray zone candidate exactly as we did in module three. Find your deflection rate, what share of contacts resolve in portal, community, or virtual agent, and remember after that clip that this is a commercial number. And check the tier evidence, which means for either product sitting on the higher tier, name the specific differentiating feature your teams used in production last quarter. If you cannot name it, you have found something.
Five guides to go deeper. The HRSD licensing guide covers the per employee model in full, the packages, the workforce definition levers, and the specific places buyers give money away. The CSM licensing guide takes the fulfiller boundary, the gray zone populations, deflection as free capacity, and the activity evidence that cut spend ten to twenty five percent. Fulfiller versus requester licensing explained is the module three boundary, which CSM inherits directly and HRSD ignores entirely, which is worth reading precisely because of that contrast. The license rightsizing playbook has the activity audit that produces your CSM evidence, and the renewal timing that both products reward. And the ServiceNow products list for 2026 shows where employee and customer workflows sit in the catalog and how their units differ from the technology families. Next time, SecOps and IRM, and the end of module four. See you there.