A Workday prospect who asks for an “AI-agent-driven implementation” usually means one of three things. Workday’s own pages already define two of them. The third is delivery work that still has to land in the tenant under a person’s approval.
This methodology is for the customer program office—not a partner brochure. It keeps Workday’s published boundaries intact and still lets you use agents where they remove real hours.
Name the three layers before you buy anything
| Layer | What Workday (or the vendor) documents | Owner on your RACI |
|---|---|---|
| LayerRuntime agents | What Workday (or the vendor) documentsWorkday-built, custom, partner, external, and Sana User agents registered in ASOR | Owner on your RACICustomer security/AI admin; functional owners for each skill |
| LayerImplementation advice | What Workday (or the vendor) documentsDeployment Agent with Ask: read-only inspection in non-Production as documented; not a Production chat assistant. Configuration Cloud, in opt-in partner early access since 18 Nov 2026, adds changes carried out once approved (Workday’s Configuration Cloud announcement) | Owner on your RACIPartner + customer architects; person who opens the task still owns the edit |
| LayerDelivery execution | What Workday (or the vendor) documentsA desktop or equivalent agent that changes configuration, builds Extend/Studio artifacts, and tests as real people after approval—for example Kiweely Vine | Owner on your RACINamed consultants; customer approver for Production-bound work |
If a vendor proposal collapses all three into “our AI implements Workday,” reject the sentence. Ask them to map every SOW task to one row above.
Methodology by phase
Discover and decide
People own workshops, decisions, and the decision log. Agents may draft options. Nothing an agent writes is “configuration” until a Workday task runs.
Configure in Implementation (or the agreed prototype tenant)
- Enable ASOR and register only the Workday-built agents you will use. Production registration needs UMSA per Workday’s About Workday Agents page.
- Use Deployment Agent Ask in the active non-Production tenant for inspection. Verify answers by opening the named objects. Workday deletes Ask chat after 14 days—copy lasting rationale into the project file the same day.
- Use a delivery agent (or human hands) to enter the change after approval. Do not leave the only copy of a design in a chat thread.
Integrate and Extend
Choose EIB, connector, Orchestrate, or Studio with your integration standards first. Let Developer Agent scaffold Extend where you already decided an app is required. A delivery agent may drive Studio on the consultant’s machine and must still ask before deploy and run if you use Vine. Workday checks Extend versions; Production promotion stays yours.
Migrate and prove
Object Transporter, security activation, and client persona tests stay human-owned. Agents prepare; people sign. A proxy test as an implementer is not evidence that the manager path works.
Hypercare
Deployment Agent is not a Production conversational assistant. Runtime ASOR agents may run under their published skills and Flex Credit meters. Delivery agents may help with approved fixes. The record of truth is the business process event and the audit trail, not the chat.
Commercial guardrails for the prospect
- Flex Credits are the customer’s meter for Workday-native AI (Flex Credits overview; Rate Card 5 November 2026). Put console alerts in place before the first Ask binge in Sandbox.
- Partner desktop AI is a separate bill. Require firm-managed AI accounts for client content; see the RFP answer template.
- Measure ROI with credits per outcome and cycle time on named workstreams, not with a single savings percentage (ROI method).
Where kiweely fits for prospects
When you want the delivery-execution layer documented above, Kiweely Vine is the desktop agent that does approved Workday tenant work under the consultant’s sign-in. Vine Free is free for your Workday personal developer account and its tenant. Any other tenant needs Vine Personal at $99 a month for one person, or a Vine Team seat at $149 a month. Firm seats are $149 a month. It does not replace ASOR, Deployment Agent, or Object Transporter. Put it on the RACI as delivery execution only. For the weekly split, use hybrid Workday delivery.
Frequently asked questions
Should we require the SI to use Workday Deployment Agent?
Require it when you want Workday’s own non-Production inspection and documentation corpus under your UMSA/ASOR setup. As documented it is advice, not automatic configuration; Configuration Cloud, in partner early access, can carry out approved changes. Pair it with a named owner for every edit and activation.
Should we require a delivery agent such as Vine?
Require a delivery agent when you are buying reduced build/test clicking with consent gates and persona evidence. Do not require it as a substitute for Customer Central roles or Object Transporter.
How do we stop “AI” from becoming unpaid hypercare?
Write Production write rules into the SOW: named approver, no self-approved Production promotions, evidence defined as Workday events and readbacks. Agents that chat without a done-event do not close tickets.