There is no formula. A manager of a global HR tech team who has worked with Workday for more than 15 years wrote it straight: “I wish there was a formula you could apply, there isn’t.” What there is: dozens of in-house teams who have posted their own size, company size and modules on r/workday. We put 30 of them in one table, sorted by company size, so you can find the teams that look like yours.
Every figure below is what one team reported in the thread linked beside it, not a benchmark we measured. Team counts are people working on Workday (configuration, integrations, reporting, security, support) unless the poster said otherwise.
Reported team sizes, by company size
Under 2,000 employees
| Employees | Scope | Workday team | Thread |
|---|---|---|---|
| Employees600 (plus a 350-person acquisition) | ScopeHRIS configuration and payroll | Workday team1, with Workday Success Plans | ThreadFeb 2025 |
| Employees~1,000 | ScopeHCM, Financials, Prism, Accounting Center, Extend | Workday team3 (1 HRIS, 1 Financials, 1 integrations/Extend), plus AMS averaging 100 hours a month on HCM | ThreadJul 2025 |
| Employees1,050, US | ScopeHCM, Advanced Compensation, Recruiting, Benefits, Absence, Talent, Time Tracking, Payroll | Workday team1; integration work is contracted out | ThreadFeb 2025 |
| Employees1,100 (300 US, 100 EMEA, 700 India) | ScopeHCM, US Benefits, US Payroll, Time and Absence, Talent, Recruiting, Peakon | Workday team2 in HRIS (one employee, one contractor), plus a small help desk contract and an occasional boutique consultant | ThreadAug 2024 |
| Employees1,200, about 20 countries | ScopeHCM, Benefits, Recruiting, Time Tracking, Talent; Core Finance, Procurement, Expenses, Projects, Adaptive | Workday team15: HRIS manager, 2 analysts and 6 functional; Finance manager, 1 analyst and 2 functional; integrations manager and 1 analyst | ThreadJul 2025 |
| Employees~1,600, one US state | ScopeHCM, Payroll, Time Tracking, Advanced Compensation, Absence, Benefits, Learning, Recruiting, Talent, People Analytics, Prism, Help | Workday team4 (1 senior analyst who is technical lead, 2 analysts, 1 associate); “pretty low complexity and generally stable” | ThreadFeb 2025 |
| Employees1,800 corporate employees | ScopeHCM, Compensation, Benefits, Time Tracking, Absence, Reporting, Payroll, Talent, Learning, Security | Workday team7 (a senior manager and 6 analysts), plus an AMS for integrations, complex configuration and break-fix | ThreadJul 2025 |
2,000 to 5,000 employees
| Employees | Scope | Workday team | Thread |
|---|---|---|---|
| Employees2,000, 13 countries | ScopeNot given | Workday team1, with Jira for Workday requests | ThreadSep 2025 |
| Employees2,000 to 3,000 (one poster’s former employer) | ScopeFinancials, Prism, Adaptive, Accounting Center; HCM, Benefits, Payroll, Recruiting, Time and Absence | Workday teamAbout 12: 4 to 6 on Financials, about 6 on HR, 2 in IT for integrations | ThreadAug 2024 |
| Employees2,500, global | ScopeHCM, Payroll, Advanced Compensation, Time Tracking, Absence, Benefits, Learning, Recruiting, Talent | Workday team4 in HRIS and 1 for integrations | ThreadFeb 2025 |
| Employees3,000, US financial services | ScopeHCM, Talent, Benefits, Integrations, Security, Absence, Reporting | Workday team10 | ThreadAug 2024 |
| Employees~3,500, 3 countries | ScopeHCM, Advanced Compensation, Recruiting, Benefits, Absence, Learning, Talent, Journeys, Extend | Workday team6 analysts and 1 audit support person; they moved from a consultant to Success Plans | ThreadFeb 2025 |
| Employees~3,500, several countries | ScopeHCM, Advanced Compensation, Recruiting, Benefits, Learning, Absence, Talent, Time Tracking | Workday team4 (3 functional, 1 integrations), “hopefully getting one other headcount soon” | ThreadFeb 2025 |
| EmployeesAbout 4,000 (“about half” of the 8,000 below), several subsidiaries | ScopeHCM, Payroll, Recruiting, Learning; no Financials | Workday team2, plus an AMS “equivalent to 1 additional FTE” | ThreadFeb 2025 |
| Employees5,000 | ScopeNot given | Workday team5, plus Mercer AMS at about $160 an hour for around 350 hours a year | ThreadOct 2026 |
| Employees5,000 employees and 2,500 contingent workers | ScopeHCM, Payroll, Recruiting, Learning; no Financials | Workday team7 (5 configuration, 2 integrations); a 6-person HR team takes basic support; fully in house | ThreadAug 2025 |
5,000 to 20,000 employees
| Employees | Scope | Workday team | Thread |
|---|---|---|---|
| Employees~6,000, 18 countries | ScopeAlmost all modules | Workday team11, functional and developers | ThreadFeb 2025 |
| Employees~7,000 and 1,500 contingent, 40 countries | ScopeHCM, Absence, Time Tracking, Core and Advanced Compensation, Recruiting, Learning, Security, Integrations, Reporting | Workday team8, with a consulting team on call for extra capacity | ThreadAug 2025 |
| Employees~8,000 in Canada, 3 companies, 14 unions | Scope9 modules, security, integrations, reporting | Workday team17, plus an AMS while the team gains experience | ThreadFeb 2025 |
| Employees13,000, 30 countries | ScopeNot given | Workday team13 (4 support, 2 reports and data, 2 integrations and acquisitions, 4 improvement, 1 senior manager) | ThreadFeb 2025 |
| Employees16,000, US | ScopeHCM, Recruiting, Benefits, PEX and Help, PATT, Advanced Compensation, Talent, Peakon, Prism, Extend | Workday team7 (a lead, 4 functional analysts, 1 security analyst, 1 integrations and Extend) | ThreadFeb 2025 |
| Employees18,000 | ScopeHCM, Absence, Recruiting, Advanced Compensation, Benefits, Talent; live since 2018 | Workday team15 (5 support, 7 functional, 2 technical, 1 architect), not counting managers; HRIS sits in IT | ThreadAug 2025 |
20,000 employees and more
| Employees | Scope | Workday team | Thread |
|---|---|---|---|
| Employees~20,000, 25 countries | ScopeNot given | Workday team12, with 5 about to be laid off | ThreadFeb 2025 |
| Employees20,000, global, mostly US | ScopeNot given | Workday team19, “tactical only” | ThreadFeb 2025 |
| Employees~30,000, 8 countries | ScopeCore HCM, Compensation, Benefits | Workday team12 analysts in two teams | ThreadFeb 2025 |
| Employees~32,000, global | ScopeAlmost everything except Adaptive Planning, Time Tracking and Benefits | Workday team4, “understaffed like hell” | ThreadFeb 2025 |
| Employees~50,000, 30 to 40 countries | ScopeHCM, Recruiting, Talent, Absence, Time Tracking, Advanced Compensation, Journeys, Learning | Workday team16, plus 2 regional support teams | ThreadFeb 2025 |
| Employees100,000, about 35 countries | ScopeHCM, Compensation, Absence, Recruiting, Talent, Goals and Performance, Learning | Workday teamAbout 15 in functional configuration (2 on security), plus separate teams for about 300 integrations and for reporting | ThreadApr 2026 |
| Employees150,000, every country | ScopeComplex ecosystem, many acquisitions | Workday team60, including EIB intake, acquisitions and an integrations team for 500+ integrations and Extend apps | ThreadFeb 2025 |
| Employees250,000, mostly Canada, heavily unionized | Scope9 modules | Workday teamA lead, an analyst and a technical consultant per module, plus 3 in IT; no AMS | ThreadJul 2025 |
Two more data points are suggestions rather than reported teams, and we mark them as such. One commenter wrote they had seen 15,000 to 20,000-worker organizations run Workday with 5 to 6 functional analysts, 2 to 3 integration or reporting specialists and 1 security or admin lead. Another, answering an 8,000-employee HCM and Payroll go-live, suggested a minimum of 6: one each for payroll and time tracking, benefits and HCM, compensation and HCM, security and reporting, and two for integrations, with a manager familiar with Workday.
What makes a team bigger
Read across the table and the same handful of things separate the 1,200-employee team of 15 from the 32,000-employee team of 4:
- Modules. Each functional area brings its own cycles and configuration. The manager quoted above suggests sizing by module rather than headcount, with some modules paired: one person for Payroll, Time Tracking and Absence, one for Performance, Talent and Compensation, one for Core HCM, and a security person.
- Payroll. It brings fixed deadlines and year-end. The two one-person teams at 600 and 1,050 employees both run payroll themselves; the 1,050-employee admin contracts out integrations instead.
- Countries and unions. The 8,000-employee Canadian team with 14 unions runs 17 people; the posters name countries and unions next to headcount when they explain their size.
- Integrations. From “contracted out” at 1,050 employees to a separate team for 300 or 500 integrations at 100,000 and 150,000.
- Where first-line support sits. Teams whose HR or a shared service desk answers employee questions (the 5,000-employee team above, with a 6-person HR team taking basic support) run smaller configuration teams than teams that answer every question themselves.
- Acquisitions. The 13,000 and 150,000-employee teams name integrating acquisitions as a standing job, and the 8,000-employee team takes on two to five small ones a year.
- Experience. The 8,000-employee team in Canada carries an AMS “for now”, because its people have less than a year of Workday experience.
The same manager adds a rule of thumb for whatever estimate you reach: “add 25% to it because you don’t want to burn your team out.”
Where the hours go
Workday itself sets part of the calendar: a feature release twice a year, which Workday’s course manual for HCM administrators says “may require uptake”, new features in your Sandbox Preview tenant about five weeks before each release, and weekly service updates in the weekend maintenance window. On top of that come the company’s own cycles. A team lead with 7 analysts across 45 countries wrote that “about 6 months of the year we’re focused on BAU activities”, naming merit and bonus, performance review cycles and year-end, with enhancements fitted in “as we have capacity”.
The recurring load, in the order it tends to arrive:
- the two feature releases (read What’s New, choose opt-in features, retest in Sandbox Preview); see preparing for 2027 R1 with a small team;
- the weekly checks: failed integrations, background processes, security changes waiting to be activated; see the tenant upkeep calendar;
- the yearly cycles: merit and bonus, performance, open enrollment, year-end and year-begin;
- tickets: reports, calculated fields, business process and organization changes, access requests. How teams take them in and triage them is in HRIS tickets: Workday Help, Jira or ServiceNow;
- audits and access reviews; see Workday change control with an audit trail.
A team of three that is “constantly being hit with a flood of IMs, emails, and Workday cases” across all its Workday modules asked for help in September 2025. Most of the answers weren’t about headcount: one place for every request, a published calendar of the year’s cycles, and leadership setting the priorities against a stated capacity.
When the team can’t grow
If headcount is fixed, the choices are to buy hours (AMS or on-demand consultants; see what Workday AMS costs in 2026), to cut scope, or to add capacity that isn’t a hire. The cost of each is compared in hire an HRIS analyst or add an AI team, and the support models themselves in after go-live: AMS partner, in-house team or both.
Where Kiweely Nest fits
The table shows small teams covering more modules than they have people for. Kiweely Nest (coming next) is built for that team. As kiweely.com/nest describes it, Nest is eleven AI specialists for a company’s own Workday, led by Kai, the Solution Architect, with one each for HCM, Financials, Payroll, Benefits, Compensation, Absence and Time, Recruiting and Talent, Reporting and Security, and a Technical Architect for integrations, Studio and Extend; you choose who joins. Requests arrive as tickets and go to the specialist who knows that part of Workday, routines run checks on a schedule, and nothing changes in your tenant until you approve.
Nest is $999 per seat a month, with 20,000 Kiweely Credits included each month, and it starts with a 30-day pilot whose $999 counts toward an annual contract. Book a demo and bring your own module list.
Frequently asked questions
How many Workday admins does a company of 2,000 employees need?
Teams near that size on r/workday reported anywhere from one person (2,000 employees in 13 countries, with Jira for requests) to four in HRIS plus one for integrations (2,500 employees, nine HCM and Payroll modules). The people answering pointed to modules, countries and integrations more than to headcount.
Is there a standard ratio of HRIS staff to employees for Workday?
No published, sourced ratio exists that we could find. The ratios in the reports below run from about one Workday person per 80 employees to one per 8,000 or more, and the teams themselves say modules, countries, integrations, unions and acquisitions decide it.