Per employee against per subscriber, and what churn does to the bill. Three knowledge checks along the way, and 4 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. 4 times in the session the frame splits and a senior licensing analyst gives the view from inside real SAP 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 twenty seven, still in module six, and today it is SuccessFactors and HCM SaaS licensing. I want to warn you at the start that this session breaks a pattern. Everything we have covered so far has been a metric you could work on: classify the users, re-architect the interface, switch off the service. HCM is priced on your headcount, and your headcount is decided by the business. So the levers are different, and if you bring the habits from the last twenty sessions you will spend effort in the wrong place. Today: the two metrics, who actually counts, the module structure, what churn does to the bill, and the reductions that are genuinely available. Three knowledge checks. Let's begin.
Five objectives. First, separate the two metrics, because per employee counts your workforce whether or not they log in, while per subscriber counts who is entitled to use a particular module. Second, know who counts, meaning contractors, seasonal staff, leavers, dormant records and populations you would not immediately think of as employees. Third, read the module structure, since SuccessFactors is a suite of modules each with its own scope, and you rarely need all of them for everyone. Fourth, handle churn, because this is a headcount priced subscription in a business that grows, shrinks, acquires and divests, and the contract has to allow for all four. And fifth, reduce the number honestly, through data hygiene, module scoping and population definitions, which are real reductions rather than reclassification games.
Four things to frame it. Headcount: the meter is your workforce, so HR hires and the licence number moves without anybody consulting procurement. Everyone: per employee metrics count people who never log in, so usage optimisation does not reduce this number at all. Modules: it is a suite rather than a product, scope is the main lever, and the wrong scope is expensive across your entire population. And churn: acquisitions, divestments and seasonal peaks all move the number, in both directions and often within a single year. Let me be direct about why this session feels different.
Guest analyst clip.
A contract discipline rather than an administrative one. That is the reframe, and it changes who needs to be in the room. For most of the metrics in this course, the work happens in a system, done by an analyst. Here the work happens in a document, done before signature, and the people who need to be involved are HR and legal rather than the SAP basis team. Now, the two metrics.
Per employee against per subscriber. What it counts: per employee is your total workforce in scope of the module, while per subscriber is the people entitled to use that module. Logging in: irrelevant in both cases, and I will keep saying that because it is the thing people get wrong. Typical modules: core HR, payroll and the suite wide services tend to be per employee, while learning, recruiting, performance and similar tend to be per subscriber. Your lever: for per employee it is the definition of the counted population, and for per subscriber it is which populations you entitle, module by module. And moves when: per employee moves when you hire, acquire or divest, while per subscriber moves when you extend a module to a new group. Both metrics count entitlement rather than activity, which is the point most people miss.
The suite itself, in four groups. Core HR: Employee Central and the system of record, which is per employee, suite wide, and genuinely the one population that really is everyone. Talent: recruiting, performance, succession and compensation, usually per subscriber, and rarely needed for the whole workforce. Learning: often the largest avoidable line on the whole agreement, because it gets entitled to everyone by default, used by a fraction, and priced across the population. And payroll and time, which are country dependent, sometimes priced separately, and the scope varies considerably depending on where you operate. Read the second and third of those together, because talent and learning are exactly where scope discipline pays.
First knowledge check. Half your four thousand employees never log into SuccessFactors. What does that save you? A, roughly half, since unused accounts can be reclaimed. B, nothing on a per employee metric, because entitlement is what counts. C, it depends on how long they have been inactive. D, nothing, and it is grounds for a refund claim. Pause here and pick an answer before you continue.
The answer is B, and this is the single most important difference between HCM licensing and everything else in this course. A per employee metric counts your workforce in scope of the module, so an employee who has never logged in is counted exactly like one who logs in daily, and there is no account to reclaim. A and C both import the reclassification thinking from session twenty two, which simply does not transfer to this metric. And D is wrong, because you bought entitlement for a population and you received it. The levers here are the definition of the counted population and the module scope, and both of those are contract questions rather than administration.
So who actually counts? Five groups. Employees, obviously, meaning permanent staff in scope of the module, and this part is never the argument. Contractors, sometimes, depending entirely on the definition in your contract. Seasonal and temporary staff, where a retailer at Christmas or an agricultural business at harvest can double a population for two months, so ask how it is measured. Leavers still in the system, because records that are not archived can keep counting, and this one is genuinely fixable. And populations you forgot: pensioners with self service access, board members, joint venture staff, each of which has to be considered against the definition. Let me take the contractor question specifically, because it is the one that varies most.
Guest analyst clip.
If they are in the HR record, assume they count until you have it in writing. That is a conservative default and I recommend it deliberately, because the cost of being wrong is asymmetric. If you assume they count and they do not, you have been slightly cautious in a forecast. If you assume they do not and they do, you find out during a measurement, at the worst possible moment and with no leverage.
Second knowledge check. Your headcount peaks at nine thousand in December and sits at five thousand the rest of the year. What matters most? A, negotiating the lowest possible per employee rate. B, how and when the population is measured. C, whether seasonal staff use the system at all. D, moving seasonal staff to a separate instance. Pause here before you continue.
B. The gap between an average and a peak here is four thousand people, which will dwarf anything you win on the rate, so A is carefully optimising the smaller number. C is the session twenty two reflex again and it does not apply, because entitlement counts regardless of use. D creates an administrative and data problem in order to solve a commercial one, and in my experience it rarely survives contact with HR. The question to settle before signature is precisely this: is the population measured as an annual average, at a point in time, or at the peak? For a seasonal business that single definition can be the largest term in the entire agreement, and it is usually decided by default rather than by negotiation.
Now the renewal mechanics, and four things to establish, because HCM populations move in both directions and most contracts only handle one of them. Growth above the commitment: at what rate, and measured when, which is the same overage question from session twenty two but in a metric HR controls rather than IT. Reduction: can the committed volume come down if you divest or restructure, which is usually not the default. Acquisitions: adding a company mid term, so agree the rate now, because doing it during an integration is doing it badly. And divestments: can entitlement transfer to the buyer, and for how long, because a transition services agreement needs that to exist. The second of those is the distinctive ask here.
Guest analyst clip.
A bounded right is enormously better than none. That is the realistic framing, and I would encourage you to ask for it in exactly those terms. You are not asking to reduce at will, which no vendor will accept. You are asking that if a defined event happens, a divestment or a restructure above a certain size, the commitment can follow. Framed that way it is a much easier conversation, and the answer is a good deal more often yes than people expect.
Right, reducing the number honestly. Five levers. Archive properly, because leavers whose records still count are the closest thing to free money in this session, so define the archiving rule, automate it and check the figure after the first run. Scope modules to populations, since not everyone needs recruiting or learning, and per subscriber modules should be entitled to the group that uses them. Define the population precisely in the contract: who is in, who is out, and how contractors and seasonal staff are treated, because ambiguity always resolves upward. Choose the measurement basis, so annual average rather than peak where your business is seasonal, and ask for it explicitly because the default will not be that. And review module by module, because the suite is bought as a bundle and used unevenly, and a module nobody adopted is shelfware with a headcount multiplier.
Five traps. Buying the whole suite for everyone, which is the most expensive default available and also the most common. Leaving the population undefined, with no written definition of who counts, because at the first true-up the definition will not be the one you assumed. Peak measurement in a seasonal business, so paying all year for a December workforce, which is frequently negotiable and almost never negotiated. No reduction right, so you divest a division and keep paying for its people because the commitment only moves upward. And never archiving, with leaver records accumulating quietly for years, which is the cheapest saving in this session and the one most often left undone.
Last knowledge check. Which lever gives the largest defensible reduction on an HCM subscription? A, deactivating accounts for users who never log in. B, scoping each module to the population that uses it. C, negotiating a deeper discount on the per employee rate. D, consolidating to fewer HR system instances. Pause here, and think about which one changes the counted population.
B. Scope is the lever because it changes what you are counting rather than what you pay per unit. A learning module entitled to nine thousand people when two thousand will ever use it is the largest avoidable line in most HCM agreements I see. A does nothing at all on an entitlement metric, which is the lesson from knowledge check one. C is worth doing, and it is arithmetic on a number you have already accepted as too large. And D is an architecture decision with real merit that does not change the headcount you are licensed for. So get the scope right first, then negotiate the rate on the smaller number. Let me show you where to look.
Guest analyst clip.
Entitlement should follow a decision, not a default. So, five things for running the HCM number. Get the headcount forecast from HR rather than from finance and rather than from last year, because HR owns the meter and they should be in the licensing conversation. Reconcile quarterly, so your HR record against your licensed volume, since small drifts are cheap to fix and expensive to discover at a true-up. Run the archive job on a schedule with somebody checking that it ran, because this is the maintenance task that quietly pays for itself every year. Track adoption by module, not for licensing relief but to decide what to renew, because a module at five percent adoption is a renewal conversation. And flag corporate activity early, since an acquisition or divestment moves this metric immediately, and licensing should hear about it before it closes rather than after.
Three sentences. SuccessFactors is priced on entitlement rather than activity, so a per employee metric counts your workforce whether or not they log in, and the usage optimisation that worked in earlier modules simply does not apply here. The levers are the definition of the counted population and the scope of each module, both of which are contract questions, and scoping a suite module to the group that actually uses it is usually the largest defensible saving available. And workforces move in both directions, so establish the measurement basis, the growth rate, the reduction right and what happens on an acquisition or divestment before you sign, because only one of those four is ever there by default. Next session continues module six with Ariba and the Business Network: procurement licensing, supplier fees, and the network sitting in the middle of both.
Homework before session twenty eight, about ninety minutes, and most of this you can do from documents you already hold. One, find your counted population: what number are you licensed for, and what is your actual headcount today? The gap between those two is the conversation. Two, read the population definition, in your contract, in writing, and check specifically how contractors and seasonal staff are treated. Three, count the leaver records, meaning how many terminated employees are still active records in the system, and then find out whether they count. Four, check adoption per module, so for each module you pay for, what share of the entitled population actually used it in the last quarter. And five, ask about the reduction right, which is one question to your account team: if our headcount falls by twenty percent, what happens to the commitment?
Five guides, all on redresscompliance dot com. SuccessFactors licensing explained covers the metrics and the module structure, module by module, in far more detail than we managed today. HCM population definitions expands slide ten, so contractors, seasonal staff and all the edge cases we listed. SaaS renewal negotiation covers reduction rights, growth rates and what genuinely moves in a renewal conversation. The SAP cloud portfolio overview shows where SuccessFactors sits in the wider SaaS estate, which is useful context for the rest of module six. And shelfware across the SAP cloud is about finding unadopted modules before a renewal rather than after one, which is exactly the adoption question from your homework.
That is session twenty seven. The thing to take away is that entitlement is the meter, not usage, so the work is in the population definition and the module scope. Next time, Ariba and the Business Network. See you then.