AI Workforce Planning and the Changing Cost of Work

AI Workforce Planning and the Changing Cost of Work

Labor Cost Optimization | Deep Dive

AI workforce planning changes hours, responsibilities and cost differently across functions, leaving staffing assumptions dependent on completed work.

Finance leaders setting staffing budgets face a gap between AI-assisted task speed and labor expense recorded across departments. The AI impact on workforce cannot be inferred from faster individual tasks because employees may spend released hours on judgment, review or transferred work. AI workforce planning therefore depends on identifying work that ends, continues under another employee or generates new obligations before assumptions reach payroll forecasts.

Subscribe to our insights

Across FP&A, sales and marketing, operations, HR, customer support and software development, AI adoption affects paid hours through different mechanisms. Routine preparation may decline without changing analyst staffing, and higher campaign output may increase review hours. Automated customer interactions can transfer difficult cases to experienced agents, whereas engineering results vary with task conditions and developer experience. The financial consequence requires distinguishing additional output, accepted work and the full cost of employees responsible for producing it, as departments record transferred work differently.

SidebarHow we help clients
  • Workforce capacity assessment. City Shift Finance connects workload, paid hours and staffing requirements across company functions to identify where AI adoption changes actual labor demand.
  • Role and skill requirements. City Shift Finance assesses changes in employee responsibilities, capabilities and supervisory requirements as routine tasks move into automated processes.
  • Headcount and labor planning. City Shift Finance connects anticipated productivity changes with hiring, vacancies, overtime and budgets, separating expected capacity from work completed.
  • Financial performance assessment. City Shift Finance compares labor expense, accepted output, implementation requirements and continuing costs to assess financial consequences of workforce changes.

For a CFO or COO, AI workforce planning connects workforce decisions to evidence held in finance, scheduling, delivery and customer records. The comparison includes completed work, paid hours, rework and skills needed after deployment. Some functions release capacity without reducing positions; others require additional review or training before savings can persist. Claims about employee departures, decision quality or commercial response require separate evidence because changes in task time alone cannot establish those outcomes.

FP&A: When preparation hours move toward executive decisions

Finance analysts collect departmental submissions, correct inconsistent inputs and rebuild assumptions before executives receive a usable forecast. Recurring preparation absorbs paid hours that might otherwise support the financial decisions awaiting management review.

SidebarForecast capacity records
  • Preparation hours by activity. Time records distinguish source collection, recurring adjustments, corrections and forecast interpretation, revealing how much analyst capacity remains committed to preparation rather than financial judgment.
  • Forecast completion intervals. Planning calendars record the elapsed time between departmental submissions, completed forecast revisions and the delivery of approved financial information to executive management.
  • Executive request turnaround. Finance request logs capture time spent producing scenarios, resolving management questions and preparing additional financial interpretation after the initial forecast submission.
  • Corrections and revision hours. Forecast histories and time records distinguish initial preparation from subsequent corrections, repeated calculations and additional revisions following management review.

AI-assisted accounting activity can change routine processing time across recurring monthly reporting activities. Corporate FP&A is a different function, however, and faster accounting work does not itself establish greater forecast accuracy or better executive decisions. “Human + AI in Accounting: Early Evidence from the Field,” Journal of Accounting Research, 2026.

Analysts with preparation time available can interpret variances, test commercial assumptions and respond to executive requests; their responsibilities then rely more heavily on financial judgment and the ability to challenge automated interpretations. Yet the released hours may remain absorbed by corrections. Capacity is not identical to completed decisions, particularly when the resulting management choices remain untested against subsequent performance.

Speed is valuable when a decision is time-sensitive, but it doesn’t substitute for judgment about what the numbers mean.

Nathan Mauck, Professor of Finance, UMKC, and CFO, NSF Critical Materials Crossroads Engine

Across some workplaces, individual task time falls without a corresponding change in the composition of work. “Shifting Work Patterns with Generative AI,” NBER Working Paper 33795, 2025. Analysts may complete the same preparation cycle sooner under revised processing arrangements; others spend the reporting period collecting departmental inputs. The difference affects the time remaining for management questions, but neither speed nor adoption establishes that those questions receive more useful answers.

Meanwhile, AI in financial planning and analysis changes the distribution of routine tasks and interpretive responsibilities; finance schedules capture preparation hours, forecast revisions and request turnaround; they do not directly establish whether the decisions taken after a forecast reaches executives improve the operating results that follow.

Forecast dates and paid hours describe the capacity available to finance leaders, but decision quality requires separate records connecting forecast assumptions with management choices and the operating outcomes recorded afterward.

Sales and marketing: Output expands faster than review capacity

Marketing teams can produce additional campaign variations with AI assistance before increasing employee hours assigned to initial creation. Distribution still requires approved messages and commercial spending, and production capacity can outpace available review hours as approvals accumulate.

SidebarCampaign cost records
  • Production hours per asset. Project records separate initial creation time from editing, approval and review hours across comparable campaign formats and production periods.
  • Revision and rejection history. Content records identify rejected material, repeated review rounds, factual corrections and additional production activity before final campaign approval.
  • Campaign spending and conversion. Financial and marketing records connect production expense, media expenditure, resulting inquiries and completed sales across comparable commercial campaigns.
  • Response variation between campaigns. Campaign histories show differences in response, conversion and customer acquisition costs between messages directed toward comparable audiences and commercial objectives.

Editors and campaign managers retain responsibility for checking facts, customer relevance and compliance. More generated material can lengthen approval queues, creating additional paid revision time after the initial production cost falls.

Production roles increasingly involve selecting usable material and assessing its commercial purpose. AI-assisted outputs can converge in style, although the observed reduction in diversity concerned fiction writing. “Generative AI enhances individual creativity but reduces the collective diversity of novel content,” Science Advances, 2024. Campaign costs also include review and distribution, so lower production hours improve returns only when customer response supports the additional spending.

The answer arrives quickly, but the human understanding needed to interpret and act on that answer develops more slowly.

Adrian Wolfberg, Former U.S. Intelligence Officer and Organizational Scientist

Meanwhile, AI in marketing can increase the content available to campaigns already competing for customer attention; more content is not necessarily more revenue. Customer purchases changed across tested online retail deployments, although those differences apply to the conditions observed. “Generative AI and Sales Productivity: Field Experiments in Online Retail,” arXiv, 2025, revised 2026. Those outcomes cannot establish production expense or profitability for every marketing team, where review and distribution costs may offset initial savings.

Finance records distinguish creation costs from approvals, corrections and media expense across related campaign periods. Campaign histories capture whether additional material changes purchases or customer acquisition spending. Similarity creates possible commercial exposure when messages reach comparable audiences. Neither similarity nor production volume establishes a loss without the corresponding spending and customer response.

Net returns depend on production, review and distribution costs together; the number of assets released cannot substitute for sales contribution measured against the spending required to reach customers.

Operations: Faster execution can preserve existing defects

Operating managers introduce AI into routines with established handoffs, exceptions and uneven processing standards; faster transactions may carry existing defects farther through operating systems before someone intervenes. Processing speed therefore differs from the acceptable work completed within the operating period and the paid time needed for correction.

SidebarOperating cost records
  • Hours per completed transaction. Operating records connect paid hours with transactions completed and accepted, distinguishing processing volume from work that later requires correction.
  • Exception and rework records. Incident logs capture failed transactions, repeated processing, manual interventions and employee time consumed resolving exceptions arising from operational activity.
  • Training and staffing exposure. Workforce records show training hours, vacancies, overtime and temporary coverage associated with employees assuming revised operating responsibilities.
  • Financial baseline and actuals. Approved budgets and operating ledgers distinguish anticipated labor savings, implementation expenditure and subsequent operating costs against the original financial assumptions.

Live security operations records associate AI assistance with differences in task productivity, although those associations cannot isolate every cause of changed performance or establish that an employer reduced its total operating expense. “Generative AI and Security Operations Center Productivity: Evidence from Live Operations,” arXiv, 2024.

Supervisors may absorb more exceptions as automated activity takes over recurring tasks; their work shifts toward intervention, verification and decisions about unusual cases requiring specialist judgment. Those responsibilities draw on skills different from repetitive processing. Training time and supervisor coverage can consequently remain after routine hours decline, limiting the resulting reduction in paid labor.

The reframe was simple: stop running AI projects and start redesigning how the organization works.

Ambarish Majumdar, Lead, AI Automation for Sales Workflows, Meta

In response, departments reassign duties before employee skills catch up. Potential job redesign can redistribute tasks among workers without establishing realized labor savings for a particular employer. “Beyond Automation: Redesigning Jobs with LLMs to Enhance Productivity,” arXiv, 2025. Some operating hours move into training. Supervisors then cover both ordinary duties and support for newly reassigned work, extending paid time beyond the original deployment budget. Other hours remain in exception queues, where they continue to produce operating expense without appearing in the initial automation target.

For AI in operations, missing predeployment baselines prevent a reliable comparison of removed labor with overtime, rework and contracted support; vacancies and error correction may coincide with delayed skill preparation across operating departments; those effects require actual operating records before a change in overtime or correction costs can be attributed to AI.

Accepted output and paid intervention hours determine operating expense across the full work cycle; initial processing speed provides an incomplete account of what the organization paid to complete.

HR: Administrative capacity and the financial cost of employee experience

HR teams answer recurring benefits and policy questions alongside sensitive hiring, onboarding and scheduling decisions; automated responses may reduce routine handling hours, but unresolved employee requests still consume specialist time and can delay critical staffing decisions.

SidebarWorkforce administration records
  • Employee inquiry resolution. HR case histories connect benefits and policy inquiries with resolution time, repeated contact, escalation and employee requests remaining unresolved.
  • Hiring and selection outcomes. Recruitment records show screening decisions, candidate progression, selection rates, complaints and decisions requiring additional review under employment requirements.
  • Onboarding and early departures. Personnel records connect start dates, onboarding completion, initial employee support requests and voluntary separations during early employment periods.
  • Scheduling and staffing requirements. Workforce planning records show approved headcount, unfilled positions, scheduling changes, absence coverage and overtime attributable to staffing requirements.

Recruitment teams retain responsibility for selection decisions when software assists candidate screening; federal requirements address adverse impact and selection procedure validity in covered employment decisions. Faster processing does not eliminate those obligations or the time employees must spend documenting and reviewing decisions for compliance. “Uniform Guidelines on Employee Selection Procedures (1978),” Electronic Code of Federal Regulations, Current 2026.

Onboarding combines routine communications with assistance for employees entering unfamiliar roles; automation can reduce repeated administrative messages, but unresolved cases still require human support. Delayed intervention may expose an employee to additional uncertainty during the earliest employment periods. Any related departure remains a possible consequence rather than an established effect of AI-assisted HR activity.

Our workforce design engagement with City Shift Finance stands among the best investments this organization has made in years.

Chief People Officer, Nonprofit

For their part, scheduling and AI headcount planning depend on actual vacancies, coverage requirements and employee availability; these records describe hours and positions differently from benefits inquiry logs used to measure administrative workload. AI in HR therefore spans functions with distinct skills and legal responsibilities; a reduction in inquiry handling time cannot establish equivalent savings in hiring or staffing decisions.

Administrative contact reductions could affect employee experience and early turnover; national separation statistics do not establish that causal connection for any particular employer. “JOLTS Home,” U.S. Bureau of Labor Statistics, 2026. They record departures without attributing them to a particular technology; early departures remain a separate financial exposure that personnel records can distinguish from the administrative hours saved on routine inquiries.

HR costs include transactions, compliant hiring, employee support and vacancies across different employment periods; paid administrative hours alone cannot account for the workforce expense associated with unresolved needs or staff departures.

Customer support: Automation changes the remaining human workload

Support centers can handle more inquiries when agents receive help retrieving information and drafting replies, reducing time on certain recurring requests. Those gains depend on the contacts involved and cannot automatically be extended to fully autonomous systems that operate without agents.

SidebarContact resolution records
  • Initial resolution by channel. Contact histories distinguish successful initial resolutions from unresolved conversations, repeated automated responses and subsequent transfers to human agents.
  • Repeat customer contact. Customer records connect repeated inquiries with their originating issues, showing additional contacts and the paid handling time they require.
  • Escalation workload and complexity. Workforce records show escalated case volumes, handling time, supervisor interventions and the distribution of complex contacts across employee experience levels.
  • Service cost and customer departures. Operating and customer records connect handling expense with unresolved cases, complaints, cancelled accounts and subsequent customer activity.

AI in customer service has improved productivity for human agents under tested conditions; the gain varies by employee experience. Those assisted interactions differ from automated contacts resolved without employee participation, especially when the latter generate additional transfers or callbacks. “Generative AI at Work,” The Quarterly Journal of Economics, 2025.

Fully automated replies can be inaccurate, repetitive or disconnected from the original customer request. Fabricated generated material is a recognized system risk during automated customer responses. “Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile,” National Institute of Standards and Technology, 2024. An exchange may end before resolving the underlying customer problem. Subsequent contacts then require additional employee time, changing the labor cost associated with the initial automated response.

A contact removed from the human queue represents a saving only when the customer's issue stays resolved.

Labor Cost Optimization Team, City Shift Finance

Meanwhile, agents receiving failed automated transfers must reconstruct customer histories before resolving a case; the remaining work may demand more judgment and experience from agents handling unresolved customer cases. Escalation time can absorb savings from routine contacts when customer issues remain unresolved; a transfer completed quickly offers little cost advantage when the customer repeats the same issue during a second paid interaction.

Contact histories distinguish initial containment from lasting resolution through reopened cases, repeat calls and abandoned conversations. Customer departures following failed exchanges represent potential commercial exposure. The human agent experiment does not establish that outcome for automated interactions. Attribution requires records connecting failed customer exchanges with later account closures and the costs of repeated support.

Net staffing capacity depends on resolved demand and the handling time of remaining cases; similar contact volumes can conceal different costs when escalation and repeat inquiries increase.

Software and IT: AI workforce planning against measured development capacity

Software leaders may incorporate expected coding assistance into delivery schedules, but engineering capacity depends on accepted work and hours spent reviewing changes. Perceived drafting speed cannot establish additional output when code reviews and corrections continue to consume paid engineering hours.

SidebarEngineering delivery records
  • Completion time by experience. Task histories connect assignment dates, completion hours and developer experience, distinguishing comparable work completed by different staffing groups.
  • Accepted work and revisions. Delivery records show completed tasks, reopened work, review decisions and additional development hours before assigned work receives final acceptance.
  • Review and intervention hours. Engineering time records capture senior employee reviews, corrections, troubleshooting and support provided to less-experienced developers during task completion.
  • Staffing plans versus delivery. Approved headcount plans and payroll records show anticipated engineering capacity, actual labor expense and completed work during comparable development periods.

Software developers completed more assigned work in certain randomized deployments; results differ across tasks and settings involving different development requirements. They cannot establish one productivity rate for every engineering team facing different codebases, review demands and developer experience. “The Effects of Generative AI on High-Skilled Work: Evidence from Three Field Experiments with Software Developers,” Management Science, 2026.

By contrast, experienced developers working in familiar repositories completed assigned tasks more slowly when permitted AI tools in a randomized trial. “Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity,” METR, 2025-07-10. Participants nonetheless reported a perception of faster progress. The discrepancy separates self-reported efficiency from measured work completed under trial conditions. Staffing plans premised on perceived gains may therefore record capacity that the delivery schedule has not produced.

When AI dramatically increases what a person can produce, output volume becomes a poor measure of contribution.

Barbara Gatumuta, Head of Human Resources & Administration, Cosmos Limited

Engineering work continues after initial code generation through review and acceptance; reviewers identify errors, request changes and accept completed tasks after additional engineering work. Junior and senior employees can experience those obligations differently, changing the skills required and the hours assigned to supervision; a faster first draft does not remove the paid time consumed by corrections and additional review before final acceptance.

AI workforce planning connects expected software capacity with accepted work and paid review hours. Finance plans incorporating AI and workforce productivity assumptions can anticipate savings before delivery records establish them. Developer experience influences both hiring expense and supervision requirements. Completed work and review records establish whether the planned capacity was achieved within the hours assigned.

Headcount assumptions remain provisional until completed tasks support the planned capacity; actual delivery time, revisions and supervisor hours determine whether an expected reduction in labor cost has materialized.

About the author(s)

City Shift Finance partners authored this report, drawing on the firm's work in labor cost management, workforce planning and financial performance across business functions.

The authors thank Nathan Mauck, Professor of Finance at UMKC and CFO of NSF Critical Materials Crossroads Engine; Adrian Wolfberg, former U.S. Intelligence Officer and Organizational Scientist; Ambarish Majumdar, Lead, AI Automation for Sales Workflows at Meta; Barbara Gatumuta, Head of Human Resources & Administration at Cosmos Limited.

The authors also thank the Labor Cost Optimization Team for its contributions to the report and Tyler, the firm's editor, for his dedication.

Contact us

Create your account

Continue your analyses, email calculation records, and return to your work from one account.

Have an account?

Contact us

Contact us

Contact

Topics of Interest:

Sign up to download