HomeTraining AcademyOracle Licensing MasterySession 31
Oracle Licensing Mastery · Module 7 · Session 31 of 40 · 28:30

The SaaS portfolio and its metrics

Module 7 opens on the third licensing world, and it shares almost no mechanics with the first two. No perpetual, no BYOL, no core factor, just a subscription priced on a metric, and the metric is the entire deal. This session maps the Fusion pillars and NetSuite, names the metrics each is sold on, hosted named user, employee, transaction, and shows where they inflate: the employee metric set on Fusion Financials that charges for 6,000 staff when 300 use it, a 20x overcount worth millions a year; the NetSuite warehouse users over tiered to full licenses; the friendly bundle whose free modules compound at every renewal. It closes with one Fusion estate metered honestly, the right metric per module, the renewal capped at signature.

What you will be able to do after this session

  • 1Map the portfolio. Know the Fusion pillars and NetSuite, and what each is actually sold as.
  • 2Name the metrics. Distinguish hosted named user, employee, and transaction metrics, and which applies where.
  • 3Count honestly. Size a SaaS subscription to real usage, not to the headcount Oracle would default to.
  • 4Read the economics. Understand the subscription model: no perpetual, no BYOL, and the uplift that returns.
  • 5Spot the metric traps. See where employee metrics and module counts inflate a SaaS deal before you sign it.

How the session works

A taught session with three knowledge checks: the 6,000 employee company sold Fusion Financials on the employee metric for 300 actual users, a 20x overcount; the 200 NetSuite warehouse staff assigned full user licenses when a limited tier fits; and the attractive bundle whose three unused modules compound at every renewal. It closes with one Fusion estate metered to reality, HCM on the employee metric correctly, Financials re metered to named users, the bundle rejected on renewal math.

Homework before the next session, about one hour

  • 1Map your SaaS estate. Every Oracle SaaS subscription: which pillar, which modules, which metric, and how many units. Most estates have never listed it.
  • 2Check one metric against use. Pick a named user or employee metric module and count the actual users. Does the subscription match, or overcount?
  • 3Tier a user list. One NetSuite or Fusion module: every user against the thinnest tier that fits their role. Note the re tiering savings.
  • 4Find the bundles. Any SuiteSuccess or Fusion bundle: modules deployed versus purchased. The unused are your renewal exposure.
  • 5Find the renewal dates. Every SaaS renewal date and current uplift, into the session 25 calendar beside the support and cloud renewals.
Learning the playbook and want it applied to your numbers? We work on contingency: 25% of what we save you. Nothing saved, nothing paid.
Review my deal