Full narration of the briefing. Click a section heading to jump the player to that moment.
Application User is the metric you control. Now the metrics that control you. The Employee metric does not count users. It counts the population the module serves: the whole workforce, part timers and often contractors, whether they log in or not.
So a four thousand person company licensing Core HR pays against four thousand people, not the sixty in the HR department. HCM and self service modules price this way as standard, at roughly a hundred to a hundred and seventy dollars per employee for Core HR, eighty to a hundred and thirty for Payroll, forty to ninety for Learning Management, reconciled against your HR records rather than your login logs. We have seen an estate paying an Employee metric against a nine thousand person population for a module only two hundred people ever touched, bought that way in 2011 because the discount looked better on the day.
Put the three side by side on one module and the difference stops being theoretical. Day one, four thousand staff and two hundred and fifty real users. On Application User you hold two hundred and fifty licences. On Employee you hold four thousand.
On a revenue metric you are priced against current revenue. Now acquire a two thousand person business. Application User: you add only the people who actually log in. Employee: two thousand licences arrive automatically.
Revenue: the line reprices against combined revenue. Now outsource the payroll processing. Application User: you remove those users at renewal. Employee: no relief, because the population is unchanged.
Revenue: no relief either. And if revenue doubles while usage stays flat, only one of the three costs you more, and it is the one with nothing to do with software.
So each metric has its own failure mode, and the job is to choose the one your business is least likely to trigger. Application User hurts you through the dormant accounts you forgot, which is a hygiene problem with a hygiene fix. Employee hurts you through growth and acquisition, which is a strategy problem you cannot fix afterwards. Revenue and cost of goods sold metrics hurt you through success itself, repricing on reported financial results, entirely outside the control of whoever owns the licence.
Volume metrics, the expense report and order line bands, hurt you differently again. They breach silently, because nobody in the organisation owns the counter, and you find out when the true up arrives.
That said, the Employee metric is not a trap by nature, and refusing it everywhere is its own mistake. It has two honest uses. The first is a module almost everyone in the company genuinely uses, where per head pricing beats counting and removes the administrative overhead of tracking authorisations for thousands of people. The second is a stable or shrinking workforce in a mature business, where it buys predictability, and you are in effect betting against your own headcount growth and expecting to win.
Outside those two cases, understand what you are signing. An Employee line is a bet on your own decline. If the company described in your board pack is growing, do not price your software on the assumption that it will not.
Which brings us to the five questions, and they get answered in writing before any module line signs, because afterwards they are simply facts you live with. One: if headcount doubles and usage does not, what happens to this line? Two: do acquired populations land inside the metric automatically, and from what date? Three: is there a written divestiture reduction right, so that selling a division reduces the licence and not just the headcount?
Four: does the metric follow outsourced work, or do you keep paying for a process you no longer run? Five, and this is the one people skip: the contractual definition of the metric, word for word, taken from your ordering document rather than from a data sheet.
One last shape, because it converts a good idea into a very large invoice. Self service is the counting trap. Rolling iProcurement or Self Service HR out to the whole workforce authorises the whole workforce, unless the contracted metric says otherwise in writing. A project justified as convenience, taking paper forms out of a shared service centre, quietly becomes an enterprise wide licence event, and the trigger was a deployment decision that never reached procurement.
So before any self service rollout, read the metric definition on that specific line, and ask the counting question out loud: when this project finishes, how many people are authorised who were not authorised this morning?
Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded. Want Redress to contact you? Reach out and we respond the same day.
Talk to a Oracle negotiator