1) The organization requires a general-purpose low-code platform for many non-Workday applications.
If most applications are not Workday-centric, platforms such as Power Platform, ServiceNow, Salesforce, Mendix, OutSystems, or Appian may provide broader applicability.
2) The organization’s development strategy depends on open web development ecosystems.
If developers require unrestricted use of JavaScript tooling, npm packages, and standard web libraries, Extend’s platform-specific approach may be a poor fit.
3) The organization needs rapid citizen development with minimal governance overhead.
Practitioner feedback indicates that Extend implementations can require significant governance and platform oversight, reducing the effectiveness of a clicks-only citizen-development strategy in some environments.
4) The required functionality can be achieved by Workday configuration and integrations alone.
If the use case can be resolved using delivered Workday features, business processes, or standard integration patterns, adopting Extend may introduce unnecessary complexity.
5) Budget constraints or an unclear application roadmap.
If there is not a pipeline of high-value applications, the platform licensing and implementation costs (including partner services) may not be justified.
Roadmap and planned features (public statements)
Workday has described plans and early-adopter availability for AI-assisted developer tooling and AI services for Extend, including AI Gateway services and a Developer Copilot offering. As with all planned features, organizations should validate general availability dates and contractual commitments.
Known issues and limitations should be validated through vendor discussions and pilot projects prior to making large commitments.