Arena: Market Conditions Before Dayforce
Employers paying hourly workforces · 2009 · North America
Disconnected workflowsRegulatory constraintsEntrenched systems
In 2009 an employer paying hourly staff kept time records, employee records and payroll in separate systems; the average organization ran about 12 different HR systems, and data passed between them badly DF3. Payroll staff could not check anything until managers closed out time, usually the day after the pay period ended. The records were then exported, imported and batch-processed, leaving a short window to audit before the payroll had to be funded, and many teams paid first and cleaned up mistakes afterward DF1. Mistakes were costly: US payroll tax ran across thousands of jurisdictions with heavy daily penalties DF3. Buyers rarely changed suppliers; payroll relationships typically lasted more than ten years DF1.
How each step happened
Step 1 of 5 · 2009–12
Continuous pay calculation on one employee record
Dayforce's innovation was to calculate pay continuously on one employee record. With separate time and payroll systems, payroll teams audited in the short window after the pay period closed, and often committed pay knowing they would have to "clean up" the mistakes afterward, David Ossip wrote DF1. Dayforce built one application that recalculated net earnings every time an employee clocked in or out or a time or employee record changed, so payroll staff could audit throughout the pay period DF1. Against ADP, whose enterprise time product fed its payroll downstream, this removed the handoff instead of speeding it up DFX-7.
The choice came from Ossip's earlier work. His previous company scheduled retail staff, held about half of the retail market and was sold in 2007; it had run out of market, and the next job over was HR, payroll and benefits DF3. His 2009 research showed core HR, payroll, time and benefits kept customers longest, so he built those first DF3. Springbrook cut payroll processing from two days to two hours DF1. Ossip says continuous calculation cut the cost of payroll by 80% while raising its accuracy DF3. By 2012 he was selling it as one employee record and one user experience with no integrations between modules DFX-1.
Rivals ADP's enterprise time product was a licensed version of Kronos Workforce Central whose reconciled time data fed ADP payroll downstream DFX-7. By 2017 an activist investor counted 74 ADP products and 1,500 software versions DFX-2.
Novel ArchitectureFounder Domain ExpertiseEnd-to-End Workflow
Step 2 of 5 · 2011–17
An old payroll bureau funds and sells the new platform
A payroll startup lacked tax knowledge for about 15,000 US jurisdictions, where errors drew heavy daily penalties, and buyers willing to trust it with pay DF3. Ceridian, an established payroll provider running a service bureau (it processed payroll for clients), had the distribution and the service reputation but, Ossip wrote, no product for the modern workforce DF1. Its revenue was declining, and the 2008 crisis had cut its float income, the interest earned on client payroll funds before they are paid out DF3. Ceridian invested in Dayforce in February 2011; in 14 months the two sold more than 500 new workforce-management systems, and in April 2012 Ceridian bought Dayforce and made Ossip CEO of the combined company DFX-1 DF1.
Ossip describes the arrangement: bureau cash flow paid for development, bureau customers were a cheaper source of sales, and Ceridian's tax team helped build the Dayforce tax engine DF3. The inherited base was a start, not the whole market. Migrations from the bureau supplied only 26–27% of Cloud revenue growth in 2016 and 2017; new customers supplied the rest DF1. E&H Family Group, whose old system was losing support, compared replacements and chose Dayforce in 2014 DF1. With funding and tax knowledge in hand, Ceridian could take the next step: stop selling the bureau.
Rivals ADP had the same assets, bureau clients, tax filing and float, and applied them to moving clients onto its existing cloud platforms DFX-3. Its rewrite of the payroll engine had about 20 pilot customers in 2019 DFX-4.
Distribution PartnershipsM&A Strategy
Step 3 of 5 · 2012–18
Stop selling the bureau; sell subscriptions instead
Months after the acquisition, Ceridian generally stopped selling its Bureau payroll services to new customers in the United States, and in Canada from 2015, to concentrate on Dayforce DF1. Dayforce was sold as a subscription priced per employee per month, with initial terms of three to five years DF1. The old business shrank by design: Bureau revenue fell 15.8% in 2016 and 18.2% in 2017, while Cloud revenue rose 32.2% and 35.8%, reaching $404.3 million in 2017 DF1.
For ADP the same move meant giving up profit. In 2017 Pershing Square described ADP's client-fund float as a profit stream with a margin near 100% and put ADP's upkeep of its older payroll systems at $410 million a year DFX-2. ADP answered that 83% of its clients were already on its strategic cloud platforms DFX-3.
Selling to new customers meant implementing them. Implementations took three to nine months; Creative Solutions in Healthcare needed help cleaning and moving its data in 2012, and Rubio's deployment in 2016 took about eleven months DF1. In 2015 analyst Holger Mueller named implementation capacity as Ceridian's next limit DF2. Ceridian added customer success managers and implementation partners DF1, and customers live on Dayforce grew from 482 at the end of 2012 to 3,001 at the end of 2017 DF1.
Rivals ADP's rebuilt platform, first shown to analysts in 2018, reached general availability as Lyric HCM in 2024 with more than 120 large accounts, and Josh Bersin listed Ceridian among its direct competitors DFX-5.
Counter-positioningSubscription Pricing
Step 4 of 5 · 2017–25
One record replaces up to 12 HR systems
Ossip planned from the start to enter with time and payroll, then add recruiting, performance, compensation and learning for the same customers DF1. Each module reads the same employee record and rules engine, so it needs no integration with payroll DF1. His life-of-customer analysis set the order: talent modules would be added so their customer life matched that of payroll and time DF3.
The pitch became replacement. Ossip describes a customer running up to 12 systems, each with its own subscription, internal owner and integration work; Dayforce replaces them at a lower total subscription, which he calculates as a cash internal rate of return of about 200–300% over the contract DF3. The continuous calculation from step 1 carried into new products: because employees see net pay during the pay period, Dayforce Wallet pays them at the end of a shift DF3. Thoma Bravo found that cross-selling into existing customers lifted bookings growth from 10% in 2024 to 40% in 2025 DF3.
Rivals Pershing Square's 2017 plan for ADP was to consolidate its 74 products and 1,500 software versions into one system DFX-2. In 2026 ADP competes on breadth, citing more than 800 marketplace solutions against Dayforce's 153 DFX-6.
Multi-ProductScope economies
Step 5 of 5 · 2015–26
Switching costs
The barrier began forming in 2015, as the customers won in step 3 went live, and grew with every module from step 4. A customer's payroll, tax rules, time records and talent data sit on the one record from step 1, under initial terms of three to five years that renew automatically DF1. Leaving means another implementation of months and retraining payroll staff DF1. Ossip says the advantage in tax, built on Ceridian's knowledge, has kept growing DF3. Cloud revenue retention was 95% or above in each year from 2015 to 2017, and gross revenue retention reached 98.0% in 2024, up from 97.1% DF1 DFX-8.
By 2024 Dayforce had 6,876 customers live and $1.76 billion of revenue, up 16.3% DFX-8. Ossip puts its share of the HCM market at about 4%, in a very large market DF3. In February 2026 Thoma Bravo completed its acquisition of Dayforce for about $12.3 billion DF4.
Rivals ADP remains far larger, with $19.2 billion of revenue in fiscal 2024; client revenue retention in its Employer Services segment was 92.0% DFX-9. Its 2026 comparison page attacks Dayforce on implementation, promising in-house implementation for every client against Dayforce's reliance on partners DFX-6.
Switching costs