A small in-house team can run Workday after go-live if it can cover six kinds of work: the two feature releases a year, the weekly service updates, the daily tickets, business process and security changes, failing integrations, and year-end. Most teams don’t cover all six alone. They keep the daily tickets and the decisions, and buy the rest from an AMS (application management services) partner, either as a hybrid where the partner owns a slice such as integrations or release testing, or as full AMS where the partner runs support. A small team usually falls behind not because any one request is hard, but because each one is many manual steps in more than one tenant, and the queue never stops.
For in-house Workday teams that want AI capacity to do that configuration, reporting, integration and release testing work in their own tenants, Kiweely Nest (coming next) is a team of eleven AI specialists led by a Solution Architect, starting with a 30-day paid pilot.
In-house, hybrid or full AMS: what each covers
The three models below are the ones Deloitte describes for Workday support after go-live (staff augmentation, co-sourced and full AMS; staff augmentation is a person or two added to the in-house column). The split inside each is the common pattern, not a Workday rule; your contract decides the details.
| Work after go-live | In-house team only | Hybrid (co-sourced) | Full AMS partner |
|---|---|---|---|
| Work after go-liveFeature releases (twice a year) | In-house team onlyTeam reads What’s New, picks opt-in features, retests in Sandbox Preview | Hybrid (co-sourced)Team decides what to take; partner runs release regression testing | Full AMS partnerPartner runs the release review and testing; team approves |
| Work after go-liveWeekly service updates | In-house team onlyTeam watches for changes in its own processes | Hybrid (co-sourced)Same; partner on call for anything that breaks | Full AMS partnerPartner monitors and raises issues |
| Work after go-liveTickets (reports, small BP and org changes, calculated fields) | In-house team onlyAll of them | Hybrid (co-sourced)Team takes most; partner takes overflow | Full AMS partnerPartner works the queue under an agreed service level |
| Work after go-liveBusiness process and security changes | In-house team onlyTeam designs, builds, activates and tests | Hybrid (co-sourced)Team decides; partner builds larger designs and new security groups | Full AMS partnerPartner builds; team approves and owns access reviews |
| Work after go-liveIntegrations (Studio, EIB, carrier and payroll feeds) | In-house team onlyTeam reads failed integration events and reruns | Hybrid (co-sourced)Partner owns integration fixes and new builds | Full AMS partnerPartner owns them end to end |
| Work after go-liveYear-end, open enrollment, merit cycles | In-house team onlyTeam runs the calendar and the configuration | Hybrid (co-sourced)Team runs the calendar; partner does specialist Payroll and Benefits configuration | Full AMS partnerPartner runs them with the team’s sign-off |
Two figures help size it. Deloitte writes that the stabilisation period after go-live “often” needs additional capacity for three to six months (Deloitte, AMS blog series: Operate support models, published 26 October 2024). And Forrester’s July 2026 findings on Workday services partners say leading providers are “expanding their focus to optimization, adoption, release management, managed services, and ongoing business transformation” (Forrester, Five Key Findings From The Forrester Wave: Workday Services, Q2 2026, 22 July 2026), so expect partners to sell release management and managed services as standing offers rather than ad hoc hours. We found no published, sourced ratio of Workday staff per employee; what 30 in-house teams reported about their own size is collected in Workday team size by company size.
Three models, as in-house teams reported them
The table is the theory. Here is what teams on r/workday said they actually run, each what one team reported in the linked thread:
- Fully in house. A company with 5,000 employees and 2,500 contingent workers on HCM, Payroll, Recruiting and Learning runs 7 people (5 configuration, 2 integrations); a 6-person HR team takes data management and basic questions, and a partner comes in only for large new modules or special projects, twice in two years (August 2025). An HRIS team of 15 at an 18,000-employee company (August 2025) uses third parties only for a massive project such as an acquisition, “once every few years”, the same person wrote (July 2025).
- In house, plus on-demand hours. A 5,000-employee company with a 5-person HRIS team uses Mercer for about 350 hours a year at about $160 an hour, roughly $56,000 a year (October 2026). A 1,200-employee company with a 15-person Workday team uses on-demand services “if we get stuck on something specific” (July 2025).
- A small team leaning on AMS. A 1,000-employee company with three people (one each for HRIS, Financials and integrations) averages 100 AMS hours a month on HCM, and is adding US and UK payroll with no extra headcount (July 2025). A company of about 4,000 runs two internal Workday people and an AMS “equivalent to 1 additional FTE” (February 2025).
The advice in those threads leans one way: “a solid in-house team that can do 95% of what needs to be done”, with a partner for special projects, drew the most agreement in one of them, and a consultant in another “never” recommends full AMS, preferring in-house cover plus on-demand hours. The other side is real too: an independent post-implementation consultant wrote in September 2026 that they hadn’t seen an organization in the last five years that could support Workday entirely on its own.
What the hours cost, with every rate named and dated, is in what Workday AMS costs in 2026; how that compares with hiring is in hire an HRIS analyst or add an AI team.
What Workday itself offers after go-live
Workday sells post-production help of its own alongside its partners. Its Success Plans page lists four plans: Standard (online resources and customer support with contractual response times), Accelerate Essentials (configuration and adoption guidance from Workday experts, 24/7 global support), Accelerate (adds personalized change management advice and detailed tenant assessments) and Accelerate Plus (adds one-to-one technical account management and help with governance planning). The page publishes no prices. The page describes guidance and support, not people who do your configuration work, which is the gap AMS or your own team fills. Workday’s Expert Assist appears with a price only in its UK public-sector rate card (£200 and £160, February 2026), covered in the AMS cost guide.
What the work after go-live actually is
Workday’s own deployment guide ends the Deploy stage with stabilizing the deployment and the “transition to customer operations”. These are the jobs that keep arriving after that. The Workday facts are from Workday’s documentation, listed in the sources.
- Feature releases. Workday ships a feature release twice a year, and its course manual for HCM administrators says a release “may require uptake”. New features arrive in your Sandbox Preview tenant about five weeks before the release date, and then go to every tenant on the same day. In that window someone runs the What’s New in Workday report, decides which opt-in features to take, and retests the processes the release touches.
- Weekly service updates. Smaller changes land weekly in the maintenance window. Most are invisible; the ones that touch your processes still need a look.
- Tickets. A new approval step, a condition rule that routes to the wrong person, a new cost center, a reorganization, a report for the board pack, a calculated field that returns blank. Each is configuration in the business process framework, the report writer or the organization tasks, built and tested in Sandbox first.
- Security changes. New roles, a domain that must be opened to a group, people who changed jobs and still hold access. In Workday a change to a security policy isn’t live until someone runs Activate Pending Security Policy Changes, so a forgotten activation is a classic “I changed it but nothing happened” ticket.
- Integrations. Every integration run, successful or not, is recorded as an integration event. When a payroll feed or a benefits carrier file fails, someone has to read the event, find the cause (data, security or the integration itself), fix it and rerun.
- Audits and access reviews. Who can see compensation, who can approve what, which changes were made and by whom. Reports such as View Security for Securable Item answer one item at a time.
- The yearly cycles. Open enrollment, merit and bonus cycles, and year-end. Our year-end payroll checklist for lean HRIS teams walks through the US year-end sequence.
What decides between the three
- Payroll in scope. Payroll carries the hardest deadlines and the rarest skills, so it is the slice most in-house teams keep a partner for, even when they run everything else.
- How many integrations run. Each one is a failure that can arrive overnight. A team without Studio skills either learns them or buys that slice.
- Who can approve Production changes. Full AMS still needs someone inside who owns the decisions. Without that person, no model works well.
- How much of the queue is known work. Reports, small BP changes and calculated fields are the bulk of tickets and the easiest to keep in-house.
- Release ownership. Twice a year someone must read What’s New, pick features and retest. If nobody inside has the time, that is the first thing to buy.
How an AMS contract changes once Workday’s own agents use Flex Credits is covered in how Flex Credits change Workday AMS contracts, and the rules for using AI in support versus implementation in implementation vs AMS: an AI policy.
Once you’ve chosen, three guides cover running it: change control with an audit trail, HRIS tickets in Workday Help, Jira or ServiceNow and the tenant upkeep calendar.
Why it’s slow for a small team
Take one ordinary ticket: add a manager approval step to a business process for one country.
- Read the current definition and its condition rules, and find out which definition actually applies to that country.
- Make the change in Sandbox.
- Open security for the new step if the approver can’t see it, and activate the pending security changes.
- Test it as the employee and as the manager, not as an administrator, because an administrator sees things the real approver won’t.
- Move it to Production. Workday’s migration reference names Object Transporter for isolated changes such as specific business process definitions, and Configuration Change Tracker for saving project work before a Sandbox refresh.
- Write down what changed and why, for the next audit.
None of those steps is difficult. Together they are an afternoon, and a team of two has a queue of them, a release to retest every six months and an integration that failed overnight. That is why the queue goes to AMS.
Where AI fits today
Workday’s Deployment Agent is a conversational assistant for Implementation, Sandbox, Preview and Customer Central tenants. With its Ask skill it reads configuration such as calculated fields, condition rules and business processes to answer questions about your tenant; Workday’s documentation says it isn’t available as a conversational assistant in Production. It explains and inspects; someone still makes, tests, migrates and documents the change. Our post on shadow AI in Workday AMS covers what that means for a support desk.
What a small in-house team needs on top of that is capacity that does the work in the tenant, which is the slice it would otherwise buy from AMS.
If you are still before go-live, read how long a Workday implementation takes and Workday’s implementation stages, and what stays manual.
What Kiweely does here
Kiweely Vine (live today) is the agent for consultants and developers, including AMS consultants who do this work for a client. Its published films show single pieces of the post-go-live queue, each one task in Kiweely’s own Workday Development tenant with test data, not a customer result:
- A custom report from one business question: 38 minutes from the question to the checked report.
- A calculated field for benefits review status, used in a saved report: 50 min 18 s.
- A messy cost-center list cleaned and loaded by EIB, 18 of 18 rows loaded: 97 minutes.
- A Studio payroll reconciliation integration built, deployed and run: 83 minutes.
- An Orchestration for a new-hire handoff that flagged a missing work email: 59 minutes.
- An Extend training approval app with its business process routing and security set up and activated, tested as the employees and managers through Start Proxy: 1 h 51 min.
Those are Vine’s films, not Nest’s. They show how long one piece of this work took on film, nothing more.
Kiweely Nest (coming next) is built for this team. As kiweely.com/nest describes it, it is a team of eleven AI specialists led by Kai, the Solution Architect: you tell Kai what the company needs, Kai makes the plan and hands each part to the right specialist, for HCM, Financials, Payroll, Benefits, Compensation, Absence and Time, Recruiting and Talent, Reporting and Security, plus a Technical Architect for integrations, Studio and Extend. Requests from colleagues arrive as tickets and go to the specialist who knows that part of Workday. Projects such as open enrollment are planned, routines run checks on a schedule, and dashboards show what the team is doing. A change is built and tested in a lower tenant first, and bringing it to Production needs your approval. Nest is $999 per seat a month with 20,000 Kiweely Credits a month included, and it starts with a 30-day pilot whose $999 counts toward an annual contract. Book a demo to walk through a day in Nest with your own Workday work in mind.
Sources checked
- Workday Success Plans
- Workday Education, HCM Core for Administrators: Workday Tenants and Tools
- Workday Administrator Guide: Reference: Migration Implementation Tools
- Workday Administrator Guide: Activate Pending Security Policy Changes
- Workday Administrator Guide: Business Process Framework Concepts
- Workday Administrator Guide: Full Glossary of Terms (Integration Event)
- Workday Administrator Guide: Deployment Agent in Implementation Environments and Customer Central
- Workday: Your Ultimate Guide to a Successful Workday Deployment (the Deploy stage)