Twenty pages on the Illuminate construct as an umbrella across Workday HCM, Payroll, Financials, Adaptive Planning, Talent and Extend; the included-AI position; the premium-AI and named-agent SKUs; the consumption metric; the buyer-side sizing protocol; the pilot-to-production transition; and the renewal posture inside the headcount-based subscription cycle.
Illuminate is the umbrella brand Workday uses for the AI-driven capabilities being woven through the product line. The brand reaches across HCM, Payroll, Financials, Adaptive Planning, Talent Optimisation, Recruiting, Learning, Strategic Sourcing, Extend and the orchestration layer. The publisher-side commercial logic is to consolidate the AI roadmap under a single visible identity and to drive a clear procurement conversation at renewal across the AI surface.
The buyer-side commercial reading is that the brand resolves uneven adoption of AI capability across the customer base and gives Workday a route to monetise the AI roadmap. The procurement decision the brand asks the buyer to make is whether the included-AI position inside the existing subscription is sufficient, whether premium-AI uplift is justified, whether the named-agent SKUs deliver against the role-based use case and whether the consumption-priced tier is sized to the activity volume the capability drives.
The Admodum reading is that Illuminate is best treated not as a single procurement decision but as a sequence of four reads against four distinct commercial constructs. The reads are independent; the procurement work is to take them in the right order against the buyer’s headcount-based subscription cycle. This paper is the methodology Admodum applies inside the Workday practice across the cycle.
A meaningful subset of Illuminate capabilities sits inside the existing headcount-based subscription as included entitlement. These are enhancements to existing modules that Workday delivers as part of the release programme, at no incremental SKU cost, accessible to customers on the relevant module subscription.
The included-AI population varies by module and by release window, with the principal known categories being:
The included-AI position is the first thing the buyer-side methodology reads. Where an Illuminate capability sits inside the subscription as included entitlement, the procurement conversation is not whether to buy it but whether to enable it and how to capture the value. The procurement question is moved from price to deployment.
A second tier of Illuminate capability sits outside the included subscription as premium-AI modules or as named-agent SKUs. These are capabilities Workday prices independently, with a per-tenant subscription, a named-agent licence, a consumption commitment or a hybrid construct.
The premium-AI modules are capability bundles that extend an existing module with materially deeper AI functionality. Examples in current Workday positioning include advanced talent optimisation, advanced recruiting AI, advanced anomaly detection inside Financials and the deeper sourcing and procurement AI surface inside Strategic Sourcing. Each is priced on a per-tenant or per-module basis at a premium against the base module subscription.
The named-agent SKUs are the higher-visibility components of the Illuminate roadmap. Each agent is a defined autonomous-or-semi-autonomous capability with a named scope and a per-agent price. The current named-agent population at the time of this paper includes the Recruiting Agent, the Succession Agent, the Compensation Agent and the Optimisation Agent, with additional agents anticipated across the next release windows.
The named-agent SKU is sold as a discrete commitment, not as an embedded enhancement. The buyer enrols a defined population of agents (and, in some constructs, a defined activity ceiling per agent), with a per-agent subscription and a top-line price visible at the SKU line. The construct is closer to a third-party-application licence than to an embedded-module entitlement.
A third tier of Illuminate capability prices on a consumption basis. The construct measures activity volume (typically agent conversations, agent tasks, recommendations served or transactions analysed) and bills against a committed activity quantum, with an over-consumption schedule that prices activity above the commitment at a published rate.
The consumption metric is the most variable of the four commercial constructs and the one with the most buyer-side risk. The activity volume is difficult to forecast in advance of deployment; the consumption rate is set against a published list that Workday can adjust at renewal; and the over-consumption price can move materially from the committed-quantum price.
The Admodum buyer-side discovery protocol reads the consumption-metric definition at the SKU level, identifies the precise activity counter, models the activity volume from a defined deployment plan against a defined population, and sizes the committed quantum to the trailing-twelve-month deployment record after the pilot. The discovery is not optional; the consumption-priced tier is too variable to commit on forecast alone.
The interaction with the wider AI commitment is also important. Where the buyer holds an Azure MACC commitment or an AWS EDP commitment with a meaningful AI consumption component, the activity that runs through the Workday consumption metric does not draw against those commitments. The two AI commitment surfaces are independent and the buyer-side sizing must address them independently.
The buyer-side Illuminate sizing protocol takes the four reads in sequence and produces a single procurement position. The protocol runs across four stages: the included-AI inventory, the premium-AI shortlist, the named-agent population and the consumption-metric forecast.
The sizing-protocol output is the buyer-side Illuminate commitment, sized against the deployed-use evidence rather than the marketing-led rollout target. The commitment is the procurement instrument; the renewal posture (Section VII) is the operational envelope inside which the commitment is renegotiated.
The pilot is the load-bearing input to the procurement decision. The Admodum pilot discipline runs against three guardrails that protect the production sizing from being driven by pilot enthusiasm rather than by deployed-use evidence.
The pilot agreement should expose the production pricing at the moment of pilot start, not at the moment of pilot close. Where Workday proposes a discounted pilot construct, the production pricing must be visible at the pilot start. The pilot should not be the price-discovery instrument for the production commitment.
The pilot deliverable is a memo to the CHRO, CFO and CIO that scores the deployed-use evidence across the role-types in scope, recommends the production-band sizing, recommends the consumption-metric committed quantum and recommends the renewal cadence. The memo is the load-bearing document; the procurement conversation runs from the memo, not from the pilot satisfaction survey.
The production ramp should be designed against the deployment plan, not against the Workday-proposed activation schedule. The ramp opens at the role-type with the strongest evidence, steps to the role-type with the next-strongest evidence at year two and reviews the lower-evidence role-types at year three. The ramp is rarely a flat commitment.
Illuminate sits inside the Workday renewal cycle. The headcount-reconciliation work, the module rationalisation, the Workday Extend platform sizing and the deployment-partner separation playbook (all set out in the Workday Renewal Preparation paper) interact with the Illuminate sizing question across the renewal window.
The interaction with the headcount reconciliation is direct: an Illuminate commitment sized to the wrong headcount is sized incorrectly across the term. The headcount reconciliation runs first; the Illuminate sizing then runs against the corrected headcount.
The interaction with module rationalisation is also direct: the included-AI population is determined by the modules in the subscription. Where the renewal contemplates a module addition or removal, the Illuminate sizing must reread the included-AI inventory against the new module footprint. Where the renewal contemplates an Extend platform sizing change, the Illuminate consumption-metric forecast must be revisited against the Extend orchestration capacity.
The premium-AI uplift question lands inside the renewal as a separate procurement decision. Workday will sometimes propose a coupled construct (a tighter base-module discount in exchange for a premium-AI uplift commitment). The buyer-side discipline is to value the two constructs independently and to assess whether the coupled deal is genuinely better than the un-coupled position. Where the coupling is favourable the buyer takes it; where the coupling masks an unjustified premium-AI commitment the buyer separates the two decisions and negotiates each on its own evidence.
The closing posture protocol runs inside the Renewal Programme on a fixed fee, contingency or annual retainer basis, with the included-AI inventory, the premium-AI shortlist, the named-agent population and the consumption-metric forecast each carried through to the closing memorandum.
The Workday Illuminate AI paper sits inside the Workday cluster of the Admodum white paper library and the broader AI-commercial reading. The companion papers extend the methodology to adjacent commercial mechanics:
The methodology in this paper is the methodology Admodum has applied across the Workday Illuminate engagements of the past twelve months. Each engagement is structured as fixed fee, contingency / gainshare or annual retainer, depending on the buyer’s posture at the renewal window. The full case studies library carries Illuminate engagement summaries; the blog publishes the running practice analysis.
A senior Admodum advisor will walk the methodology through with your CIO, CHRO, CFO, HR technology or sourcing team on a private call. Engagements run as fixed fee, contingency or annual retainer.