VC-backed SaaS · Rippling
92% less onboarding work. About $66,000 a year back.
If every new hire takes days of someone's hands-on time, you pay twice: once in hours, and again if the hire walks.
What it was costing them
Every new hire took 25 hours of hand work: accounts, laptops, benefits, then chasing whatever got missed. At $80 an hour and three hires a month, that's $6,000 a month before the new person did a day of real work.
What it was risking
The hours are the small number. A hire who starts without access, a laptop or benefits starts doubting the decision. Gallup puts the cost of replacing an employee at one-half to two times their salary.† For a $150,000 engineer, that's $75,000 to $300,000. Lose one hire a year to a bad first week and it costs more than a year of setup hours.
What we did
- Built one Rippling sequence. Add the person once, and accounts, laptop and benefits follow.
- Put identity first in the sequence, so access is right on day one.
- Left the team with review and exceptions. Nothing else.
Before and after
| BeforeClient-reported | AfterClient-reported | |
|---|---|---|
| Hands-on hours per hire | 25 | Under 2 |
| Setup cost per month (3 hires) | $6,000 | Under $480 |
| Setup cost per year | $72,000 | Under $5,760 |
More than $5,500 a month back. About $66,000 a year. And every hire starts ready.
- What we'd do differently:
- We started device provisioning before the client had settled on an identity provider, and redid part of it when the access model changed. We agree the identity model first now.
- Evidence:
- Before is client-reported: 25 hours per hire at $80 an hour fully loaded, three hires a month. After is client-reported: under 2 hours per hire with the new sequence. †Gallup, 2019. The $150,000 salary is an example, not this client's number.