A quick history. Workday launched Extend Professional as the upgrade tier with more apps, more data records, more tenants, the Workday AI Gateway, the Extend Developer Co-Pilot, and native AWS integration. Essentials covered the basics for teams building a handful of internal apps. The trade-offs were genuinely about complexity and scale.
Then Workday acquired Flowise in 2025 and made the Flowise Agent Builder part of the Extend Professional entitlement. That single change reframed the decision. Pro is now the path that includes "build your own agents". Essentials is not. The cost of the upgrade no longer competes only with app limits. It competes with whether your team is in or out of the agent building era.
What you get with Essentials
Unlimited development apps and three production apps. Ten million data records. The App Builder and Workday Orchestrate. One development tenant and three named support contacts. App Pack bundling for additional production apps if you need them later.
This is the right fit for a team that wants to start small, ship a few internal apps, and stay inside Workday's data and security model. If you have not committed to AI, do not need AWS-native services, and do not see yourself building agents in the next eighteen months, Essentials still does the job.
What you get with Professional
Everything in Essentials, plus ten production apps, a hundred million data records, three development tenants, and five named support contacts. The interesting additions are the capability differences.
Three Pro entitlements sit alongside that. The Workday AI Gateway lets your apps and agents call Workday-native AI services (document intelligence, Q&A over policies, sentiment analysis, skills cloud, ML forecasting) without managing models or paying per token, which is the cleanest path when your AI use cases map onto what the Gateway already covers. The Extend Developer Co-Pilot is a GenAI assistant that accelerates UI and code creation inside the developer experience, useful for teams building several apps a year and marginal for teams building one. Native AWS integration provides direct connectivity to Amazon Rekognition, Textract, Comprehend, Translate, Lambda, and EventBridge through a managed AWS account that Workday provisions, useful when you need image recognition, document parsing, translation, or event-driven workflows at scale.
The Flowise Agent Builder is the piece that changed the maths. A visual, low-code workbench for designing, deploying, and managing custom agents on top of Workday, rolling out to Extend Professional customers in the first half of 2026 alongside the broader Workday Build platform. This is the capability that turns Extend from "custom app platform" into "custom agent platform".
“Agent building used to be the next conversation. With Flowise in Pro, it is the conversation, and the line between the two SKUs runs straight through it.”
What that means in practice
If your team has any agent ambition for the next eighteen months, Professional is now close to a default decision. Custom agents on top of Workday live in Flowise Agent Builder. The Builder lives in Pro. There is no third option that achieves both, short of running the open-source Flowise yourself outside Workday's security envelope, which most enterprise teams will not want to do for HR use cases.
If your team has no agent ambition (genuinely no agent ambition, not "we will think about it later") then the maths goes back to where it was. Essentials covers a handful of internal apps perfectly well. Two-thirds of the Pro entitlement does not move the needle for you.
The cases that get interesting are in the middle. You are not building agents yet, but you will be. The honest answer for most of these teams is to upgrade. The cost of starting on Essentials and migrating later is higher than the cost of starting on Pro and growing into the agent capability over time.
The decision questions, refreshed
Five questions in 2026, in roughly this order. Will you build custom agents within eighteen months? If yes, Professional. If no, keep reading.
Do you have AI use cases that map onto AI Gateway (document intelligence, Q&A over policies, sentiment, skills cloud, forecasting)? If yes, Professional. AI Gateway alone is a meaningful upgrade for those use cases.
Do you need AWS services (image recognition, document parsing, translation at scale, Lambda-style event handling)? If yes, Professional.
Are you planning more than three production apps in the next year? If yes, Professional. The app cap on Essentials starts to bite once a team gets comfortable with the platform.
Is your team building Extend capability in-house? If yes, Professional. The three development tenants and five support contacts are not a small thing once you have multiple developers working in parallel.
None of these are binary, and the answer is rarely a single yes that tips the decision. If most of the questions land squarely on no, Essentials is genuinely the right call. If two or more land on yes (and especially if the agent question lands on yes), Pro starts to pay for itself in capability rather than just app count.
What about the cost question
We do not publish list prices and Workday's customer-specific pricing varies. Two practical notes from working through this conversation with clients. First, the Pro premium is meaningful but rarely dominant compared to the build effort of even one custom agent. Second, the cost of upgrading mid-stream tends to be higher than the cost of starting on Pro. The friction is administrative more than financial: contract renegotiation, internal approvals, replanning. If you are likely to need Pro within two years, start there.
The case for staying on Essentials
There is a real case, and we make it with clients regularly. If your team is small, your use cases are well-defined, your AI strategy is genuinely two years out, and you would rather not pay for capability you will not use, Essentials is the honest answer. The marketing tilt is heavily toward Pro for the obvious reason that Pro has the headline features. The right SKU is the one your team will actually use, not the one with the longest spec sheet.
A small note on the agent SKU question
Workday announced the Flowise Agent Builder as part of Extend Professional rather than as a separate purchase. This was a deliberate signal: agent building is treated as a core developer capability, not as an upcharge. For customers already on Pro, the Builder shows up in the entitlement without a renegotiation. For customers on Essentials considering an upgrade, the Builder is part of the value of moving up. This is more generous than some of the early speculation expected, and it changes the calculus around investing in Extend capability.
A working heuristic
A short test that has held up with clients: if you can name three Workday gaps that would benefit from a custom app or agent in the next eighteen months, go Professional. If you cannot name three, go Essentials and revisit in a year. Two of the three can be apps. At least one should be an agent, because the agent is what justifies the agent-building tier. Without the agent in the list, you are paying for capability you will not exercise.
