When AWS shifted enterprise IT from fixed infrastructure to metered consumption, two patterns emerged. Companies that treated the cloud as just a cheaper data center saw modest savings. Companies that treated Cloud FinOps as a design discipline unlocked far greater value.
The patterns from that era are by now familiar. One global manufacturer saved nearly a million dollars in under a year through disciplined cost engineering. A hyper-growth SaaS provider, on the other hand, saw its AWS bill multiply due to a lack of consumption oversight. Same bill structure, very different outcomes.
Workday customers are stepping into a similar opportunity, with a decade of FinOps hindsight to draw from.
In February 2026, Workday published its Flex Credits and Platform Entitlement Policy and an accompanying Rate Card. Together they introduce a consumption model for AI and platform innovations, layered on top of the existing subscription. Workday's published Policy and Rate Card are the authoritative source for entitlements, structure, and current credit rates; this perspective focuses on the model and how customers can think about it.
The model in plain terms
The Flex Credits consumption model has three pieces, and understanding how they relate is most of the work. Usage flows through them in sequence:
Some Workday activity sits in an included Platform Components bucket that doesn't consume credits regardless of volume. Three other Platform Components (APIs, integration events, and document storage) have an annual Platform Entitlement sized to your workforce and SKUs. When usage exceeds that entitlement, or when your teams use Workday's AI agents, the work draws from a separate annual pool of Flex Credits. Both entitlements reset every year.
- Sandbox and other non-Production testing (with one current exception — the BP Optimize Agent consumes credits in non-Production)
- Workday-built integrations that haven't been customized (including Core Connectors)
- Integrations built using Enterprise Interface Builder (EIB)
- Storage held exclusively in Workday's Contract & Document Intelligence, CLM, Strategic Sourcing, and Media Cloud products
- Apps built by partners under Workday's formal "Built on Workday" program
- API calls — system-to-system requests
- Integration events — including custom integrations and extensions built using Workday Studio, Workday Orchestrate, or Document Transformation
- Document storage — gigabytes held in general Workday storage
This matters for capabilities on the near-term roadmap. The Workday Assistant will be succeeded by the Self-Service Agent in the 2027 R2 release. The Self-Service Agent is charged per action under the Flex Credit model, and is one of a broader roadmap (Sana for Workday, Workday Data Cloud, Sana Agent Builder, Agent-to-Agent Connectors) priced through the same mechanism. Customers with a Flex Credit Balance in place will be able to adopt these capabilities as they become available without a separate procurement step.
Both the Platform Entitlement and the Flex Credit Entitlement reset every year. Unused balances don't roll over.
Workday isn't alone in this
Salesforce introduced credit-based metering for its Einstein AI capabilities. ServiceNow has done the same for Now Assist. SAP is moving in the same direction with AI Units. The mechanics differ in detail across vendors, but the underlying pattern is consistent: AI capabilities are being priced as metered consumption layered on top of traditional licenses, with customers expected to manage usage as an operational discipline. The companies that build that discipline once benefit from it across vendors.
What this looks like in numbers
The examples below use the same 5,000-employee customer profile to illustrate three different consumption patterns. The shape of the math is similar at other sizes; only the absolute numbers shift.
Platform overage. A 5,000-employee customer using 4 million API calls against a 3.5 million Platform Entitlement would draw a small share of its annual Flex Credit Entitlement — under 10% — to cover the 500,000-call overage. Each overage on its own is modest; the FinOps point is that overages compound across components and integrations.
AI agent intensity. Workday's higher-tier AI agents, like the candidate rediscovery agent (Fetch), are designed for strategic use rather than routine invocation. Running a high-tier agent on every transaction can exhaust a customer's annual Flex Credit Entitlement quickly; using it on the most strategic transactions leaves credits available for other AI work. Same agent. Same rate. Different discipline. The metric that matters isn't credits consumed, it's value delivered per unit of work.
Storage hygiene. Document storage in general Workday storage counts against the Document Storage Platform Entitlement, billed on a daily fractional basis when exceeded. Storage held exclusively in Workday's contract and sourcing products is exempt, but copies made to general storage for other purposes start counting.
Visibility: PCC and ASOR
Workday provides the Platform Consumption Console (PCC) as the system of record for usage, paired with the Agent System of Record (ASOR) for agents. The PCC displays Platform Entitlement, Used, and Credit Consumption for each Platform Component, alongside the Flex Credit Entitlement, purchased credits, Credit Balance, and current Rate Card rates in context. ASOR provides visibility into deployed agents, their skills, and the roles they're enabled for.
Notifications fire in the PCC and the Workday Inbox at 80%, 90%, and 100% of the credit entitlement. These go to users assigned the Management Dashboard: Platform Consumption Console security domain — make sure the right people (typically a mix of IT, HR Ops, and Finance) have access.
What to do now
-
1
Start with visibilityFamiliarize yourself with the Platform Consumption Console (PCC) and the Agent System of Record (ASOR). Assign named owners across IT, HR Ops, and Finance to monitor the PCC's 80%, 90%, and 100% notification thresholds.
-
2
Govern integrations as a portfolio, not a backlogMaintain an inventory with clear source-and-destination system ownership. Decommission schedules that are no longer needed. Negotiate design patterns with vendors before integrations are built, not after the first month's consumption report.
-
3
Enable AI agents deliberatelyPilot in non-Production first — agents and applicable platform components in non-Production environments are free and don't consume credits, with one current exception: the BP Optimize Agent consumes credits even in non-Production. Measure value per action against credit cost before turning anything on at scale. High-value agents pay for themselves on the right use cases; used as default UI, they exhaust budgets quickly.
-
4
Plan with dataEngage your Workday account team on credit volume planning. Bring real consumption data from the PCC to those conversations rather than relying on intuition.
The bigger picture
Flex Credits are Workday's path to faster, more flexible AI adoption: pay for what you use, scale on demand, direct credits to the business outcomes that matter most. The companies that pair that flexibility with architectural discipline will get the most business value from Workday's platform and AI innovations — the same lesson AWS-mature companies learned over more than a decade.
