Dayforce CDO Carrie Rasmussen: Time Saved by AI Agents Must Be Priced or Reduced
Carrie Rasmussen, Chief Digital Officer and CIO of Dayforce, cited an example from her own management at the Discover 2026 conference to illustrate the economic trade-offs of AI agents: If an AI agent boosts the efficiency of a 10-person team by 20-30%, while token costs exactly match 20-30% of those 10 employees' salaries and benefits, is that 20-30% of freed-up time actually worth the price? If the company believes this time can be converted into higher-value strategic work, the team headcount can remain unchanged; if the company feels 'this area of the business doesn't need to be so strong, being a B-player is fine,' then return the excess staff to the corporate pool, reducing the 10 people to 8. She emphasized this was 'an example within my own jurisdiction to show how these trade-offs operate,' not a validated pricing model.
The value of this example lies not in the numbers themselves, but in shifting the decision on deploying AI agents from 'should we buy this tool' to 'who prices the saved time.' Jeremy Johnson, Dayforce's Chief Financial Officer, pointed out at the same conference that enterprise technology transformation used to follow a three-step process: HR defines requirements, IT evaluates the technology, and Finance approves the budget. AI shatters this linear flow because introducing an agent involves workforce planning, technology selection, and cost structure simultaneously, requiring all three functions to sit together and make the same decision.
Chief People Officer Amy Cappellanto-Wolf described this cross-functional decision-making as a 'business design issue.' She gave a hiring example: previously, HR only looked at what talent was needed; now, they must first ask 'does this job really require hiring another person? Can an agent do it? If an agent can do it, what is the cost comparison? Where is human judgment required?' She believes these questions fall outside the purview of any single function. HR's unique opportunity is to help the business think about 'how work gets done,' including deciding what should be human-led, what should be AI-assisted, what should be automated, and what she considers the most unique option—what should be stopped.
Rasmussen further extended this logic to vendor assessment. She believes AI will first eliminate point solutions—small vendors with single functionalities—because core platforms (Salesforce, NetSuite, Microsoft, and Dayforce itself) now have extension capabilities, allowing enterprises to add features directly on the platform without separate procurement. Her other screening criterion is more intuitive: if a software company's product interface lacks a conversational AI entry point, it is already outdated. 'It's just that OpenAI chat box, the simplest page, everyone copied it. If you don't see it, you feel like this product is so ancient.'
However, this approach has several clear boundaries. First, the correspondence between token costs and salaries/benefits is Rasmussen's illustrative estimate; she did not disclose specific calculation methods, measurement periods, or applicable conditions. Second, the model assumes a linear correlation between efficiency gains and cost savings, but in reality, agent output quality, error rates, and human supervision costs significantly impact net benefits. Third, the option to 'return staff to the corporate pool' may face execution obstacles in markets with strict labor laws. Finally, this logic primarily applies to relatively standardized, quantifiable work scenarios; for creative, complex judgment, or highly contextualized work, 'saved time' itself is difficult to price.
Sources :diginomica