Bolt's CEO Fired His Entire HR Team. Then He Hired People Ops.
Bolt's CEO cut his HR department and replaced it with a 2-person People Ops team. He's right about the model — and wrong about what killed his HR.
This week, Bolt CEO Ryan Breslow told a Fortune conference that he fired his entire HR department because they were "creating problems that didn't exist." The headlines exploded. Twitter picked sides. HR professionals got defensive. CEOs nodded along.
But everyone is arguing about the wrong thing.
The real story isn't that Breslow fired HR. It's what he replaced it with. Buried in every article, past the outrage bait, is this sentence: "We replaced it with a couple-person people-ops team."
He didn't eliminate the HR function. He shrunk it, renamed it, and gave it a different mandate. And whether he knows it or not, he just described the future of how most growing companies will handle their people.
The model Breslow stumbled into
Here's what Bolt actually did: they went from a traditional HR department — one that, by Breslow's account, had grown bureaucratic during the company's boom years — to a small People Ops team focused on execution over process.
That's not revolutionary. It's a pattern we've been watching for years.
Companies with 50 to 500 employees don't need a 10-person HR department. They need two or three sharp operators who handle the judgment calls — the hiring decisions, the sensitive conversations, the culture work that requires a human being in the room.
Everything else — onboarding paperwork, compliance monitoring, benefits enrollment, document assignments, time-off approvals, reporting — is execution. It's work that needs to happen reliably, every single time, but it doesn't require a department to do it.
The question isn't whether you need HR. You do. Employment law doesn't care what you call the department. Someone has to run payroll. Someone has to track FMLA. Someone has to make sure your California employees get meal breaks and your terminations have documentation.
The question is whether that someone needs to be eight people, or whether it can be two people with the right platform.
What Breslow got right
The instinct is correct: traditional HR departments in fast-moving companies often create friction. Not because HR is inherently bad, but because the tools they're given force them into manual, process-heavy work that slows everything down.
When your HR team spends their week building spreadsheets for comp cycles, chasing managers for overdue reviews, manually checking compliance across multiple states, and formatting onboarding packets — they're doing necessary work in the most expensive way possible. And the company experiences that as slowness.
Breslow's frustration wasn't with the function. It was with the operating model. He wanted people who "get things done" instead of people drowning in administrative process. That's a tooling problem, not a people problem.
What he got wrong
Firing an entire department and bragging about it at a conference isn't a strategy. It's a reaction.
The "problems" that Breslow says disappeared when HR left? Some of those were probably real compliance requirements that are now going unaddressed. Employment law doesn't pause because you renamed a department. California expense reimbursement rules don't care that you're in "wartime mode." EEOC reporting obligations don't vanish because you reduced headcount.
The problems didn't disappear. They went invisible. And invisible problems in HR become very expensive when they surface — in lawsuits, in DOL audits, in wrongful termination claims.
A two-person People Ops team can absolutely run HR for a company Bolt's size. But only if those two people have infrastructure that handles the execution automatically — the compliance monitoring, the document tracking, the benefits administration, the daily operational work that used to require a department.
Without that infrastructure, you don't have a lean People Ops team. You have two overwhelmed people and a growing stack of compliance risk.
The platform gap
This is the real issue nobody is talking about.
The reason HR departments bloat isn't because HR people love bureaucracy. It's because the software they use — the legacy HRIS platforms — is built for configuration, not execution. These are systems of record, not systems of action.
They'll store your employee data beautifully. But they won't onboard a new hire automatically. They won't scan for compliance gaps at 6am before you open your laptop. They won't flag that a termination in California needs different documentation than one in Florida. They won't run your benefits enrollment without a dedicated administrator.
So companies hire more HR people to operate the software. The department grows. The process gets heavier. The CEO eventually looks at the team and says, "What do these people even do?"
The answer is: they operate software that should be operating itself.
What a two-person People Ops team actually needs
If you're going to run your company's entire people function with two or three operators — and you should — here's what has to be true:
Onboarding can't be a 47-step checklist. It needs to be one sentence. "Onboard Maria as Marketing Manager, starting June 1." Documents get assigned. Welcome emails go out. The manager gets notified. Equipment gets requested. It just happens.
Compliance can't be a quarterly audit. It needs to run daily, automatically. Your California employees need expense reimbursement policies. Your Florida employees need different overtime rules. Someone — or something — needs to watch that every single day, not once a quarter when someone remembers to check.
Benefits enrollment can't require a dedicated person. Employees should be able to self-serve during open enrollment. Plan comparisons, eligibility rules, life event changes — all of it should work without a human administrator shepherding every selection.
Terminations can't be improvised. Every separation should get a legal risk review before it happens. Is this employee in a protected class? Is there a pattern? Is the documentation sufficient? That review needs to happen before the meeting, not after the lawsuit.
Reporting can't be a half-day project. When the CEO asks "what's our turnover by department?" the answer should take seconds, not a spreadsheet exercise.
This is the infrastructure that makes a two-person People Ops team viable. Without it, you're just underfunding HR and calling it innovation.
The Lenavio thesis
We built Lenavio for exactly this scenario.
Not for the 10,000-employee enterprise that needs a legacy HRIS. Not for the 5-person startup that uses a Google Sheet. For the company in the middle — the one with 50 to 500 people, a lean People Ops team, and zero tolerance for administrative drag.
Our AI agents handle compliance monitoring every morning. Onboarding executes from a single command. Legal reviews happen before every termination. Benefits enrollment is self-service. The command bar turns plain English into reports, actions, and workflows.
Your People Ops team handles the judgment — who to hire, when to promote, how to navigate a difficult conversation. Lenavio handles everything else.
Breslow was right that the model is changing. HR departments are shrinking into People Ops teams. The work isn't going away — the way it gets done is.
The question is whether you shrink the team and hope for the best, or whether you give that smaller team the platform that makes the model actually work.
Lenavio is the AI backbone for People Ops teams. Start a free trial at lenavio.com.