Latest / Startup Stories with Fexingo: Conversations About Founders, Funding, and Building Companies from Zero / How Rippling Built a Unified HR Platform by Automating the Busywork
Transcript
- Lucas: So Parker Conrad co-founded Zenefits, the all-in-one HR platform that imploded in 2015 after regulatory failures — and then he quietly spent a year building a new company that would become Rippling. And what's interesting is that Conrad didn't try to avoid his past mistakes. He actually leaned into a more ambitious version of the same thesis. Luna: Meaning instead of building a narrower product, he made Rippling even broader? Lucas: Exactly. Zenefits connected HR data to payroll, benefits, and compliance — but it relied on third-party integrations for IT and device management. Rippling's insight was: why not own the full stack? If you already know when someone's hired, you should be able to automatically provision their laptop, set up their Slack account, and grant them access to Salesforce — all from one system. Luna: And that's the pitch that got them a $13.25 billion valuation in 2023. But let's back up — how did Conrad go from Zenefits' collapse to raising $500 million in a single round? Lucas: Well, the origin story is pretty understated. After leaving Zenefits in 2016, Conrad spent about a year as a venture partner at a16z, then quietly started building what would become Rippling. He raised a small seed round from a few friends and angels — no big announcement, no press release. The company launched in 2018 with a product that did payroll and employee management, but the real differentiator was the IT layer. Luna: Right — because most payroll systems like Gusto or ADP assume you'll handle device provisioning separately. Rippling said, 'What if your first day at work automatically gives you a configured laptop?' Lucas: Exactly. And that's a harder technical problem than it sounds. You need integrations with hardware vendors like Apple and Dell, with app providers like Google Workspace and Microsoft 365, with identity providers like Okta — and all of those connections have to work in reverse when someone leaves. One click offboarding, rather than spending half a day deprovisioning accounts manually. Luna: And that 'one click' story is exactly what sold CFOs and IT heads. I remember reading that Rippling's early pitch deck claimed the average company spends 12 hours per employee on IT setup and offboarding. That's huge for a business with 500 employees. Lucas: Right — 12 hours times 500 employees times an average IT wage of, say, $50 an hour — that's $300,000 in annual hidden cost. Rippling's software costs a fraction of that. So the ROI case was immediate. And what helped was that Conrad had learned from Zenefits that selling to HR alone wasn't enough. HR departments don't control IT budgets. So Rippling built a product that could be sold to both the head of HR and the CIO simultaneously. Luna: That dual buyer strategy is something few SaaS companies pull off well. Usually you optimise for one persona and the other feels neglected. Lucas: Yeah, and Rippling made a deliberate architectural choice to avoid that: a unified data model. When you enter an employee's information in Rippling, it flows to payroll, to benefits, to device management, to app provisioning — all from a single source of truth. There's no syncing, no integration headaches, no 'oh, we updated payroll but forgot to update Slack.' It's all the same database. Luna: That sounds obvious, but most companies still operate with separate systems that talk to each other via APIs. Rippling bet that building everything yourself would be faster and more reliable than stitching together best of breed tools. Lucas: And the bet has paid off so far. By late 2024, Rippling had over 20,000 customers, including big names like Stripe and Coinbase. Their revenue growth has been roughly doubling year-over-year — though they're still private, so we don't have exact numbers. But what's interesting is that they've expanded beyond just HR and IT. They now offer spend management, travel booking, and even app security. Luna: Which sounds like a classic platform play — start with a wedge product, then expand into adjacent categories once you own the data. But doesn't that risk spreading too thin? Lucas: It's a risk, but Conrad has argued that the unified data model gives them a moat. Competitors like Gusto or BambooHR would have to rebuild their entire architecture to match Rippling's integration depth. And for new features like spend management, Rippling already has the employee roster — they don't need to sync with a separate HR system. The cost of adding a new module is lower for them than for a point solution. Luna: Still, I wonder about the enterprise sales cycle. Selling to both HR and IT at a Fortune 500 company is complicated. And those companies often have legacy systems they're not eager to rip out. Lucas: True. Rippling's sweet spot seems to be companies between 50 and 2,000 employees — big enough to have dedicated IT and HR teams, but not so locked into legacy infrastructure that switching is painful. Above that, you're competing with Workday and SAP, which have decades of enterprise relationships. Rippling hasn't really cracked that upper market yet. Luna: So let's talk about the competition. What's Gusto doing in response? They have a similar product now, but they started as a payroll-only company and added HR later. Can they catch up on the IT side? Lucas: Gusto has been adding integrations — they bought a company called EasyPaycheck and have been building out their own device management features. But the difference is architectural. Gusto's product is still payroll-first, with HR and IT as add-ons. They don't have the unified data model that Rippling was built on. So when you update an employee's role in Gusto, it doesn't automatically propagate to their laptop or their Slack account unless you've set up a third-party integration. Rippling does it natively. Luna: It reminds me of the difference between Shopify and a traditional ecommerce platform. Shopify built for the unified experience from day one, while incumbents like Magento had to bolt on features. Lucas: Yeah, and the same dynamic played out in CRM with Salesforce vs. HubSpot. The unified approach tends to win when the customer is overwhelmed by managing multiple point solutions. And that's exactly the pain Rippling solves. Luna: But speaking of the audience — if these conversations about startup strategy have helped you think about your own business or career, we wanted to mention a small way you can support the show. It's not a big ask — honestly, if today's episode was worth a coffee to you, that's the link: buy me a coffee dot com slash fexingo. Lucas: Yeah, it's a tiny gesture that goes a long way toward keeping this podcast independent and ad-free. We don't run sponsorships, so listener support is really what keeps us going. Luna: Exactly. And now back to Rippling — there's another angle I want to dig into. Conrad has been very public about his philosophy on remote work. Rippling actually requires employees to be in the office three days a week. That's a strong stance for a tech company in 2025. Lucas: It is. And it's somewhat ironic, given that Rippling's product helps companies manage remote employees. But Conrad's argument is that innovation happens faster when people are together. He's said that the first version of Rippling was built by a small team in a single room, and that proximity was critical for the kind of cross-functional collaboration needed to build a unified platform. Luna: But does that limit their talent pool? In a competitive hiring market for engineers, mandating three days in the office could scare off top candidates who want full flexibility. Lucas: It's a tradeoff. Rippling has said they want people who believe in the mission enough to show up. And they've been able to hire well because their growth story is compelling. But you're right — not everyone can afford that stance. If you're a startup without Rippling's traction, you'd probably need to offer remote flexibility to compete. Luna: So where does Rippling go from here? They've raised a lot of capital — over $1.5 billion in total — and they're burning through it to grow. The question is whether they can achieve profitability before the market turns. Lucas: They haven't disclosed profitability, but in a 2024 interview, Conrad said they're 'not too far from it.' The unit economics look strong because each new customer brings a high average revenue per account — Rippling charges per employee per module, so a company with 500 employees using payroll, IT, and spend management could be paying $50,000 to $100,000 a year. And retention has been high, reportedly over 90%. Luna: That's a solid foundation. But the risk is that they keep expanding into new categories and the product gets bloated. Or that a competitor like Microsoft or Apple builds device management directly into their operating systems, cutting out the middleman. Lucas: That's a real threat. Apple already has device enrollment in Apple Business Manager. Microsoft has Intune for device management. If they added payroll and HR features, they could undercut Rippling. But building a payroll system is notoriously hard — it's heavily regulated, varies by state and country, and requires deep partnerships with banks and tax agencies. That's not something tech giants typically want to dive into. Luna: So maybe Rippling's moat is the regulatory complexity of payroll, not just the technical integrations. Lucas: Exactly. And they've been expanding internationally — they now support payroll in over 50 countries. Each country has its own tax codes, labour laws, and banking infrastructure. That's a massive barrier to entry. Even a company like Deel, which focuses on global payroll, had to build a complex network of local entities. Rippling is doing that while also managing IT and HR. Luna: It's an ambitious vision. But if they pull it off, they could become the operating system for employee management. One platform that handles everything from hiring to paying to equipping to offboarding. Lucas: And that's exactly what Conrad has said — he wants Rippling to be 'the single source of truth for employee data.' Not just HR, not just IT, but everything. The question is whether that ambition will lead to a market-defining company or a cautionary tale of overreach. Luna: I guess we'll find out in the next few years. For now, Rippling is one of the most interesting SaaS stories to watch — especially because it's built by a founder who already had a spectacular failure and came back with an even bolder vision. Lucas: Yeah, and that's a reminder that failure in startups isn't always the end. Sometimes it's the first draft of a better idea.