SC

Strategy Canon

Dayforce: sourced choices

21 product and go-to-market choices, oldest first. Back to the case study

  1. 2009Product · Time and pay The initial design connected time records and payroll calculations in one application. DF1
  2. 2009Product · Continuous calculation The proposed architecture recalculated net earnings as time or employee information changed. DF1
  3. 2012Go_To_Market · Combination with Ceridian A successful commercial partnership preceded Ceridian’s acquisition of Dayforce in 2012. DF1
  4. 2015-03Go_To_Market · International development The analyst reported work on EU workforce compliance and a planned new UK payroll product. DF2
  5. 2018-03Product · Employee record The delivered platform used a single employee record across HCM functions. DF1
  6. 2018-03Product · Rules engine A shared rules engine supported payroll and workforce-management requirements. DF1
  7. 2018-03Product · Workforce management Scheduling and time-and-attendance functions supported hourly work. DF1
  8. 2018-03Product · Employee access Self-service and mobile tools let employees access records and schedules. DF1
  9. 2018-03Product · Benefits Benefits administration formed part of the HCM offering. DF1
  10. 2018-03Product · Talent functions Recruiting, onboarding and other talent functions extended the original time-and-pay scope. DF1
  11. 2018-03Product · Reporting Customers could use shared data in reports and dashboards. DF1
  12. 2018-03Product · Migration assistance Implementation work included moving and cleaning customer data. DF1
  13. 2018-03Go_To_Market · Segment The company marketed Dayforce to employers with more than 100 employees. DF1
  14. 2018-03Go_To_Market · Adjacent offering Powerpay targeted Canadian organizations with fewer than 100 employees. DF1
  15. 2018-03Go_To_Market · Direct sales A direct sales force organized by customer size and geography sold the cloud products. DF1
  16. 2018-03Go_To_Market · Subscription unit Dayforce subscriptions were priced per employee per month. DF1
  17. 2018-03Go_To_Market · Contract duration Initial terms were typically three to five years with evergreen renewal afterward. DF1
  18. 2018-03Go_To_Market · Bureau migration A dedicated account-management team helped legacy Bureau customers migrate to Dayforce. DF1
  19. 2018-03Go_To_Market · Lead generation Marketing, outbound business development and partners generated leads. DF1
  20. 2018-03Go_To_Market · Customer success Customer success managers worked with customers from signing through deployment and ongoing use. DF1
  21. 2018-03Go_To_Market · Implementation partners The company used a partner network as well as its own services for deployment. DF1