A 20-person team isn’t a 2,000-person one.
We scope, staff and price every project to your headcount and complexity. See how that works at your size.
TipEvery service and solution page shows what it looks like at each size.
Get in touch
Our work
/
Case study

Fixing Rippling onboarding at 350+ hires a month

An AI data center company that moved from Deel to Rippling, with payroll stable but onboarding and provisioning breaking under hypergrowth.

Before
Manual onboarding
No Ashby link · contractors outside Rippling · unreliable Okta
→
After
Ashby → Rippling → Okta
Rebuilt provisioning · contractors in Rippling · data cleanup

350+ | Hires a month, employees and contractors 3 | Systems in one flow: Ashby, Rippling, Okta 2 | Retainer phases

The challenge

New hires without access on day one

The company moved from Deel to Rippling on July 1, 2026. Payroll and benefits were stable; everything upstream was not.

The instance had been set up without documentation or alignment with IT and Finance. There was no Ashby integration, contractors and vendors were missing from Rippling, Okta app provisioning was unreliable and manual data entry caused errors. New hires were not provisioned on time, and access gaps created security exposure.

How the project runs
  • Audit Onboarding audit in the first sessions; provisioning failures ranked for fast resolution
  • Rebuild Ashby-to-Rippling and Okta provisioning flows fixed
  • Bring in contractors Contractor records moved into Rippling
  • Clean up Phase 2: employee data quality and ongoing optimization
Where it stands

Provisioning flow rebuilt

Talk to a specialist
  • Onboarding audit complete
  • Ashby, Rippling and Okta connected end to end
  • Contractor records in Rippling
  • Data-quality remediation and optimization retainer in place
← All projects