The Hosted Employee metric at scale: module packaging, global workforce counting, and the levers specific to the system that counts everyone. Three knowledge checks along the way, and 1 clip from a senior cloud advisor.
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. Once in the session the frame splits and a senior cloud advisor gives the view from inside real Oracle 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 of thirty. Last week, ERP, where the argument was who uses the system. This week, HCM Cloud, where the argument is who works here, and I promised that would be harder than it sounds. Here is why: HCM is the one system in the estate whose price is set by your entire organization chart rather than by any deployment decision you make. Hire a warehouse crew in Poland, your HR software bill moves. Divest a division, it does not move, and that asymmetry alone is worth this session. Today: the module landscape, the Hosted Employee metric as it actually behaves on an invoice, the global counting questions that multinationals must settle at the order, the rate band arithmetic, and the negotiation levers specific to the one Oracle pillar where the competition is genuinely credible. The system that counts everyone deserves a buyer who counts back. Let's start.
Five takeaways. One, the landscape: Core HR, the talent modules, payroll, and workforce management, what each family covers and how each one prices on the workforce. Two, the metric at work: how Hosted Employee becomes an invoice, population times rate stack adjusted by bands, three multipliers, three separate negotiations. Three, global counting: entity scope, phased country rollouts, payroll localization, and the four questions a multinational settles at the order or regrets at the renewal. Four, the levers: what genuinely moves in an HCM negotiation, and the ranking matters, competitive tension first, scope and definitions second, structure third, and the discount percentage, everyone's favorite topic, deliberately last. And five, the playbook: the HCM order assembled the module four way, scoped population, staged rollout, protected renewal. This is also the session where session sixteen's definition work pays compound interest, because everything we learned about who counts is about to be multiplied by forty six thousand.
The landscape, four module families. Core HR, sometimes called Global HR: the person record, the organizational structures, employee and manager self service, and commercially it is the base, everything else in HCM requires it, session eighteen's dependency chain rule, applied here on day one. The talent family: recruiting, onboarding, performance, learning, succession, sold as individual modules or bundles, each adding its per employee rate. Payroll: priced per employee per country, and country is the operative word, payroll only exists where Oracle has built the localization, the statutory rules, the tax engine, the filings, and that constraint drives a whole knowledge check later. And workforce management: time and labor, absence, scheduling, the modules that reach your hourly and seasonal populations, which, recall the retail story from session sixteen, is exactly where workforce definitions get expensive. Now the commercial shape of all this, and it is worth saying plainly: nearly everything prices per Hosted Employee, on the same workforce, module by module. So the bill is roughly the rate stack times the population. Add a module, you multiply the same big number again. Add people, every module in the stack feels it. Two directions of multiplication, one invoice, and that structure is the whole session in miniature.
From definition to invoice, three multipliers, and I want you to see the invoice as their product because each multiplier is a separate negotiation. Multiplier one, the population: the workforce as the service description defines it, for the entities in scope. Session sixteen's definition argument, who counts as an employee, and this session's entity argument, which parts of the group are even on the order, both land here, and this is the biggest multiplier, the one where scoping mistakes cost seven figures. Multiplier two, the rate stack: each module adds its per employee rate on the same population. Core HR plus four talent modules plus time and labor is six rates stacked on one workforce, so the module list is itself a cost decision, challenge modules, not just rates, a module you defer is a rate you delete. Multiplier three, the bands: rates step down in volume tiers, and where your population sits against the band boundaries changes the unit economics, boundaries being exactly as negotiable as the rates between them, more on that later. Here is the seller's preference: they would like the entire conversation to be about multiplier two's discount percentage, because it is the smallest of the three. The buyer's discipline is to negotiate them in order: population first, stack second, bands and rates last. First check, and it is the population multiplier at full scale.
First check. A group with forty six thousand employees worldwide deploys HCM in phase one to its US and UK entities, twelve thousand employees. The quote prices Core HR and the talent modules at forty six thousand Hosted Employees. What actually decides which number you pay for? A, forty six thousand, the metric always counts the global workforce. B, twelve thousand, automatically, you pay for what you deploy. C, the order's entity and population scope: as written it may well mean forty six thousand, and the fix is scoping the order to the deploying entities with price holds for the rest. Or D, whatever the implementation partner's workbook says. Pause here. Where would the contract even say twelve thousand? Which document scopes the population?
The answer is C, and the key insight is that neither A nor B is a law of nature, both are just possible orders, and the default one is the expensive one. An order whose scope reads the customer and its affiliates, unqualified, prices the global forty six thousand from day one, which means three years of subscriptions for thirty four thousand people who have no go live date, and that is precisely how the standard quote arrives, not out of malice but because the unqualified scope is the path of least drafting. The fix is contractual: scope the order to the named entities actually deploying, twelve thousand people, and carry the remaining entities as price holds at today's rates and discounts, exercised wave by wave as the rollout reaches them. That is session eighteen's start narrow, hold wide, executed at workforce scale, and it is the single largest saving available in most first HCM deals. B has the right instinct and the wrong mechanism: deployment does not scope a contract, words do, and if the order says affiliates, your phase plan is commercially irrelevant. D, the workbook, you dispatched last session, provenance rules apply to workforces exactly as they apply to users. The multinational rule, worth writing on the wall: the entity list on the order is the population, so the entity list is the negotiation.
The four counting questions, and every one of them follows the same economic law: cheap to settle at signature, expensive to settle at renewal. Question one, which entities count? The default sweeps the customer and its affiliates; the negotiated answer names entities per deployment wave with holds for the rest, the first check's fix. Question two, which workers count? The default definition sweeps contractors and temps, session sixteen's territory; the negotiated answer carries the amendments, seasonal worker bands, contractor carve outs, priced tiers for short tenure staff. Question three, which countries get payroll? The default prices payroll wherever you deploy it; the negotiated answer buys payroll only where Oracle has localization and runs partner payroll elsewhere, next check's subject. And question four, what happens at M&A? The default is that acquired headcount joins the count at the next true up, and divested headcount, note carefully, joins nothing and leaves nothing, the asymmetry we close the session on. The negotiated answer pre prices acquisition bands and takes divestiture adjustment rights, and module six devotes a whole session to the corporate events playbook. Four questions, four defaults that favor the seller, four negotiated answers that cost almost nothing at signature. Our guest analyst has the first question at forty six thousand employee scale, let's hear it.
Guest analyst The largest single line item saving I have ever produced on a SaaS deal came from an entity list, not a discount. A European industrial group, forty six thousand employees across nineteen countries, buying Fusion HCM to replace four regional HR systems. The proposed order was clean, well discounted, and scoped, in one quiet phrase, to the customer and its affiliates. Phase one of the rollout covered Germany and the UK: twelve thousand people, eighteen months of work. Phases two through four stretched four years into the future, and phase four, honestly, was aspiration. The quote priced all forty six thousand from month one. Nobody had questioned it because the per employee rate looked excellent, and it did, they had negotiated the rate hard and the scope not at all. We rewrote the order: named entities for phase one, twelve thousand hosted employees, with price holds locking the same rate and discount for every remaining entity, exercisable per wave. Same rate, same discount, thirty four thousand fewer subscriptions running while the rollout caught up. Just under four million a year at the start, and phase four never fully happened, a divestiture took a chunk of the group in year three, so those subscriptions would have been pure loss for their entire life. Here is what I want you to take from it: the rate is how the deal looks. The scope is what the deal is. And in workforce metrics, scope is spelled as a list of legal entities on the order, so read that list the way you would read the price, because it is the price.
The rate is how the deal looks, the scope is what the deal is, four million a year sitting in an entity list. And notice the divestiture postscript: the subscriptions that never started were for people who ended up leaving the group anyway. Scope first, rate second, always. Second check.
Check two, payroll geography. You operate in fourteen countries. Oracle payroll is localized for six of them. The quote includes payroll for the full forty six thousand person workforce. The analyst's move: A, buy it, global payroll from one vendor is simpler. B, scope payroll to the localized countries' population only, run partner or local payroll elsewhere, and hold prices for countries Oracle localizes later. C, buy no Oracle payroll at all, localization gaps make it worthless. Or D, buy it but only run it in six countries. Pause here. What exactly does a payroll subscription do in a country where the product cannot legally run payroll?
The answer is B, and the reasoning starts from what payroll actually is: the most jurisdiction bound module in the entire portfolio. Statutory rules, tax engines, filing formats, all built per country, and in a country without Oracle's localization, a payroll subscription is a subscription to software that cannot legally do the job there. It is not degraded, it is inapplicable. So B scopes the payroll spend to the six countries where the product works, priced on those countries' population rather than the global count, runs proven local or partner payroll in the other eight, and, the forward looking piece, holds rates for countries Oracle localizes later, so that when Poland or Brazil arrives on the roadmap you expand at today's competitive pricing instead of tomorrow's captive pricing. A buys a simplicity that does not exist: the eight unlocalized countries still need their local payroll regardless, so the single vendor dream means paying twice in most of your footprint. D is A with honesty about the shelfware: billing forty six thousand while running six countries is check one's population mismatch replayed on the priciest module family. And C overcorrects, throwing away the six countries where consolidation onto Oracle payroll may genuinely be the right operational call. The generalizable rule: modules whose value is jurisdiction bound get scoped by jurisdiction, priced on jurisdiction population, and expanded by price hold. Payroll is just the purest case.
Rate bands and packaging, the tier arithmetic, five points. One, bands step rates down: per employee rates fall as population tiers rise, so know which band you are in and price the marginal employee, not the average one, the last thousand people you add cost less than the first thousand, and your growth forecast should be priced accordingly. Two, boundaries are negotiable: a forty six thousand person workforce sitting near a fifty thousand band boundary can very often be priced at the next band's rate, the argument writes itself, growth is coming, and the seller wants the larger commitment on the books, ask. Three, the stack compounds: six modules on forty six thousand people means a small per module rate difference is seven figures a year, which is why you negotiate the stack price as a stack, the whole per employee cost across all modules, rather than being walked through module by module where each rate looks individually reasonable. Four, suites versus modules: HCM sells talent bundles and full suite pricing, and session eighteen's bundle test transfers without modification, dollars against deployment, never discount percentages against list. And five, the warning that sets up our last check: growth pricing cuts both ways. Bands reward growth automatically, the count trues up, the rate steps down, everyone smiles. Shrinkage does not travel backwards. A workforce that falls below a band boundary, or falls at all, keeps its committed quantity until renewal. Hold that thought.
The HCM levers, four of them, ranked by the money they move, and the ranking is the lesson. First, competitive tension, and this is what makes HCM different from every other room in the Oracle house: the alternatives are genuinely credible. Workday and SuccessFactors win these deals routinely, Oracle's own account teams treat HCM as contested territory, and a real, visible evaluation, not a brochure on the table but an actual scored process with executive sponsorship, moves more money than every other lever combined. It is also the lever with an expiry date: it exists until you sign, and then it is gone for five years. Second, scope and definition: the entity list, the workforce definition amendments, payroll by jurisdiction, everything from today's first hour. These set the population multiplier, and the population multiplies everything else. Third, structure: ramps by deployment wave, price holds for later entities, the renewal cap, and the divestiture adjustment language that our final check is about to make you want. Fourth, and deliberately last, rate and bands: the discount percentage and the boundary arguments, negotiated after the other three have decided what the percentage actually applies to. The order of operations is the entire point: population, then structure, then price. A great discount on an unscoped global workforce is a bad deal wearing a good number, and Tom's four million a year entity list is the proof. Last check.
Last check. Two years into a five year HCM term, you divest a division. The workforce drops from forty six thousand to thirty nine thousand. The subscription bills forty six thousand. What happens, and what would have changed it? A, the bill drops to thirty nine thousand at the next invoice, SaaS tracks headcount. B, nothing until renewal: quantities do not come down mid term, and the fix was divestiture adjustment language negotiated at signature, when it costs almost nothing. C, Oracle audits the divestiture and reprices upward. Or D, the divested entity keeps using your subscription until your term ends. Pause here. Which direction do mid term quantity changes travel? And who carried the risk of that asymmetry?
The answer is B, and this is the sharpest edge of the asymmetry we have been circling since session sixteen. Growth flows into the count at true up, automatically, that is what the metric is for. Shrinkage flows nowhere until renewal. So for the three remaining years of the term, you pay for seven thousand people who no longer work for you, roughly fifteen percent of the HCM bill purchasing nothing, and it is fully contractual. Now the part that should sting: the fix existed and it was nearly free. Divestiture and workforce adjustment language on the original order, a clause granting quantity reduction rights on qualifying corporate events, is a concession sellers grant at signature with a shrug, because nobody at the table expects to use it, and refuse at the event with equal confidence, because by then it is worth exactly what it costs. It is the down lane, negotiated while everyone is busy admiring the up lane. A describes a utility meter; Hosted Employee is a committed quantity with a one way true up, not a meter that runs backwards. And D is not a workaround, it is a violation: the divested entity stops being an affiliate under your order's scope on the day the deal closes, and letting it ride your subscription is unlicensed use with a paper trail an auditor could follow blindfolded. Transition access gets negotiated with Oracle explicitly, and module six's corporate events session covers exactly how. The rule for today: negotiate the down lane while you are signing the up lane. It will never be cheaper.
The HCM buyer's playbook, three files. The population file: the workforce definition read aloud, with the seasonal and contractor amendments negotiated, session sixteen's homework industrialized; the entity list scoped to deployment waves with price holds for the rest, Tom's four million lesson; payroll scoped by localized jurisdiction; and the M&A and divestiture adjustment language on the order, the down lane, secured while it is free. The commercial file: the rate stack priced as a stack against the scoped population, not module by module; band boundaries negotiated wherever your workforce sits near one; session eighteen's bundle test applied to any suite offer; and the standard structure, ramp, cap, holds, per session seventeen. And the leverage file, the one unique to this room: a real alternative, evaluated visibly, scored, sponsored, because HCM is the pillar where Oracle's competition is most credible, and a live Workday evaluation at the table moves more money than every clause in the other two files combined. Three files, one order, and the system that counts everyone gets a buyer who counted first. Next session closes module four with the biggest strategic move in the applications estate: the migration itself, on premises to SaaS, what happens to the perpetual licenses you spent decades buying, and the point of no return.
Session nineteen, three sentences. One: HCM bills population times rate stack adjusted by bands, three multipliers negotiated separately and in order, and the population multiplier, entities, definitions, jurisdictions, moves the most money, the rate is how the deal looks, the scope is what the deal is. Two: multinationals settle four counting questions at the order, which entities, which workers, which payroll countries, what happens at corporate events, because every one of them is nearly free at signature and priced like a hostage at renewal. Three: quantities travel one way mid term, so the divestiture adjustment clause gets negotiated while signing the growth lane, and HCM's uniquely credible competitive tension is spent before signature or wasted forever. Next week: the migration session, trading support streams for subscriptions, the fate of the perpetual estate, and the point of no return, module four's finale. See you there.
Homework, about an hour, the population file for your own workforce. One, count the real workforce from your HR systems: employees, contractors, temps, and the seasonal pattern by month, per legal entity, this is the number Oracle will eventually count, and you want to have computed it first. Two, map entities to waves: if HCM is deployed or planned, which entities are actually live, and what does the order's scope language literally say counts, then compute the gap, Tom's four million lived in exactly that gap. Three, check the payroll geography: the countries where you run payroll against the countries your vendor localizes, and any subscription covering the difference is check two's finding wearing your logo. Four, find the down lane: read your order for divestiture or workforce adjustment language, and if it is absent, write down what a fifteen percent workforce drop would cost you through end of term, that number is the price of the missing clause and the argument for adding it at renewal. And five, price the bands: find your population's band and its boundaries, and if you sit within ten percent of one, write the boundary argument down now, it belongs in the renewal file. An hour with the org chart, and the system that counts everyone stops being the bill nobody can explain.
Five reads before next session, all free on redress compliance dot com. First, the Oracle HCM Cloud licensing guide, the module families and the workforce metric in reference depth, today's map with more detail per module. Second, Hosted Named User versus Hosted Employee, the metric mechanics underneath the population multiplier, shared with session sixteen and worth rereading now that you have seen the multiplier at scale. Third, Workday versus Oracle HCM licensing costs, the competitive tension lever with numbers on both sides of it. Fourth, Workday versus Oracle versus SuccessFactors, the three way market that makes HCM the most contestable deal in the Oracle portfolio, and therefore the best place in the whole estate to practice running a real evaluation. And fifth, the Oracle Fusion modules list, the catalog including the HCM families and their dependency chains. That's session nineteen. Population, stack, bands, in that order, the entity list read like a price, and the down lane negotiated with the up. Next week we close module four with the migration itself. See you there.