US healthcare group. Twenty percent off the Workday module stack.

How an 18,000 employee healthcare group used a module deployment audit and a worker count reconciliation to cut Workday module spend 20 percent at renewal.

What was the situation at this healthcare group?

The client is a US healthcare group with roughly 18,000 employees across hospitals, clinics, and corporate functions, running Workday HCM, Payroll, and Financials with a stack of add on modules. The renewal was approaching with spend up 34 percent since the original subscription.

Nobody could say which modules were actually deployed. The contract listed fourteen SKUs; the HRIS team actively used nine.

How the estate got there

• Bundled buying: modules from the Workday Financials and adjacent catalogs were added during expansion negotiations because the bundle discount looked attractive.
• Implementation backlog: two analytics modules, including one from the Workday Adaptive Planning family, were never implemented after the sponsoring executive left.
• Worker count drift: the billable count included divested clinic staff still sitting in the system.

How did the optimization actually work?

The engagement ran a module by module deployment audit, a worker count reconciliation, and a renewal negotiation built on the findings. The audit compared contracted SKUs against measured usage in the tenant, then priced each gap.

The deployment audit

Each contracted module was scored on three axes: implemented, adopted, and value evidenced. Five of fourteen SKUs failed at least one axis. The unused modules mapped to the published Workday HCM product catalog rather than to any internal requirement.

The reconciliation

Worker records were reconciled against payroll actuals. The billable count dropped by roughly 1,100 once divested staff, duplicate contractor records, and stale requisitions were cleared, directly reducing the FSE base the subscription prices on, per the definitions in the Workday legal and agreement documentation.

Where the common advice on Workday renewals is wrong

The standard advice is to negotiate the renewal as one bundle, because Workday discounts the package. We disagree. In roughly 25 of the 30 to 40 Workday engagements Fredrik Filipsson benchmarked in 2024 to 2025, the bundle frame is exactly what protects dead SKUs; the discount on modules you do not use is not a saving. The buyer side move is to disposition every module before renewal and let the bundle price reform around the modules that survive. Workday resists line item surgery, but a documented non deployment record makes the position defensible.

A module you never implemented is not a discount opportunity at renewal. It is a refund argument, and it only works if you bring the deployment record.

What were the results and the structural protections?

The renewal signed with module spend down 20 percent against the expiring run rate. Three dropped SKUs, a reduced planning scope, and roughly 1,100 fewer billable workers produced the reduction; a capped escalator protects it going forward.

• Escalator cap: annual increases capped at a fixed percentage, ending silent 5 to 7 percent compounding.
• Revisit clause: dropped modules can re enter at the original discount band if a business case emerges.
• Quarterly count hygiene: worker reconciliation now runs quarterly, not at renewal panic.

What transfers to other Workday estates

Module disposition, worker reconciliation, and escalator caps work in any industry. Healthcare amplifies the worker count lever because of workforce churn, but the audit method is universal.

What to do next

1. List every contracted Workday SKU against measured tenant usage.
2. Score each module: implemented, adopted, value evidenced.
3. Reconcile billable worker counts against payroll actuals.
4. Build the disposition sheet: renew, reduce, drop, with evidence per line.
5. Open renewal talks at T minus 6 months with the disposition as the anchor.
6. Cap the escalator and paper a revisit clause for dropped modules.

The Workday practice runs module audits as a standard engagement, and the case study library has more renewals like this one.

Frequently asked questions

How much did the healthcare group save on Workday?

Module spend fell 20 percent at renewal against the expiring run rate, driven by three dropped SKUs, a reduced planning scope, and roughly 1,100 fewer billable worker records.

What is a Workday module deployment audit?

A module by module comparison of contracted SKUs against measured tenant usage, scoring each on implemented, adopted, and value evidenced. Modules failing an axis become renewal disposition candidates.

Why did the billable worker count drop by 1,100?

Reconciliation against payroll actuals cleared divested clinic staff, duplicate contractor records, and stale requisitions that had accumulated in the tenant. The subscription prices on that count, so hygiene is money.

Will Workday agree to drop modules at renewal?

Workday resists line item removal, but a documented non deployment record makes the position defensible. In this engagement two never implemented modules came out, with a revisit clause preserving the discount band.

How do you stop module sprawl returning?

Quarterly worker reconciliation, a deployment gate before any new module purchase, and an escalator cap so growth in spend requires a decision rather than a default.