He hired very experienced people. It almost ruined his company.

You went on a hiring spree. Brought in some of the most talented, experienced, senior people you'd ever met. Convinced they'd 10x your company.

Within six months, every single one of them was gone — and the business had actually shrunk.

I worked with a founder who went through exactly this. And the mistake he made is far more common than you'd think.

I recorded a full video breakdown here — including everything that went down and how to avoid the same fate. But if you'd rather read, here's the full story and the three-question framework I now give every founder before they make a senior hire.

The company in question

The company had been around for several years. About ten people, profitable, a founder who ran it the way most founders run small companies: he decided the priorities. He decided what mattered, when. If something needed approval, it went to him. If something was unclear, it went to him.

He had bigger ambitions though. He wanted to expand into adjacent business lines and grow into an industry leader.

Around this time, his business coach gave him a challenge: 10X the company.

The founder took it seriously. He thought about what 10X would require. And he concluded: he needed people. Senior people. Proven track record. Big, reputable companies. So he hired almost ten of them over a few weeks — someone to run product, someone to run marketing, someone to run operations, sales, the works. Within three months, the team doubled.

On paper, this looks like a company growing up. A founder finally bringing in "adults." Building a real leadership team. The founder was psyched. The team was psyched. The new hires were psyched.

Two months in, problems started appearing.

What actually happened

The senior hires had noticed from day one that there was no documentation and no onboarding — but that was fine. They were used to big teams with a lot of structure, but they were also excited to get their hands dirty again.

After a month of urgent operational work to meet pre-existing deadlines, they finally had time to get to the strategic work they'd signed up for: looking at business strategy, defining goals, hiring people, implementing structure.

But they ran into a wall.

The founder provided no financial visibility and granted none of them the authority to make key decisions. Proposals were blocked — not with a hard no, but with subtle evasion. When they pushed for structure to reduce the chaos, the founder undermined them, saying "we need to be agile." He'd praise their efforts to the rest of the team, then continue doing things exactly as before.

Three months in, the founder started expressing doubt. He'd justified the higher salaries to himself with the math that one expensive senior hire must be multiple times more productive than a lesser-paid junior. The output clearly didn't show that. He was not shy about showing his disappointment.

Within six months, every single one of these senior hires either left or was pushed out.

The founder felt a sense of relief — with the team small again, he could feel in control. But things didn't get back to the way they were. His cash reserves took a hit from hiring so many senior people at once. The senior hires had been well-liked and respected by the original team. When all of them left, morale dipped to an all-time low. One by one, the original team members started leaving too.

The founder ended up shrinking the business. There was no mention of the 10x growth plan ever again.

What went wrong

Plenty of things went wrong, but three did most of the damage. The scary part isn't that these mistakes were made — it's how common they are.

1. He believed talent is the system

The first problem: he believed that if you have talent, you don't need systems.

His logic was simple. Hire excellent people, hand them the mess, and let them sort it out. That's what excellent people do. If they can't — well, they weren't excellent. He also believed that in a chaotic sink-or-swim environment, the weak would weed themselves out. Rinse and repeat, you'd have a team of survivors who could do it all.

This sounds tough-minded. It's actually a fantasy.

You're not testing them on their ability to do their jobs well. You're testing them for whether they can tolerate ambiguity. The people who survive are the ones with the highest pain threshold, or the least leverage to push back, or the ones who simply don't care. None of that is the same as good.

And honestly — if these hires were producing anything in this chaos, what could they have produced with a working setup?

Hiring excellent people is excellent, but you have to set them up to succeed: clarity, resources, authority. Without those three things, you'll end up with a bunch of expensive people producing subpar results, and you'll blame them for it.

2. He hired people to move mountains, but only gave them shovels

Imagine you're opening a restaurant and you hire the best chef in the country. You tell her to make it the best restaurant ever. Then you put her in a kitchen with no stove, no knives, a few ingredients — and no budget.

Is she still the best chef in the country? Technically yes. Is she cooking up an eight-course dinner tonight? No. She spent the day looking for pans and she's exhausted. She did manage to serve one dish.

Now you're mad at her for failing to live up to her reputation.

What makes senior people senior is that they have the know-how and the authority to operate at a high level inside a clear setup. It doesn't mean they can conjure that setup from nothing. Even if the chef knows what the optimal kitchen layout should be, she can't install the stove herself.

Back to our story: it didn't take long for the senior hires to realise they were never supposed to build a team. They were the team.

Even the most seasoned operators cannot work miracles if the basics aren't in place — who decides what, who owns what, what the budget actually is.

You might be thinking: "fine, then I'll hire someone whose specific job is to build the structure. A Chief Operations Officer, or a business systems consultant brought in to define how the company runs." Totally legitimate. Plenty of companies do this and it works. (You can even hire me for this — shameless plug.) But it only works if three things are true: the role is defined, the authority is real, and the founder is willing to take direction from their own hire.

Which brings me to the third problem.

3. He thought he was above the systems

To say this plainly: the founder didn't like being told what to do.

He believed systems were for other people, not him. That's why he'd praise new organisation efforts in public while telling his senior hires privately that "we need to be agile." Why he evaded every request for visibility on goals, plans, budgets. He was the founder, and he reserved the right to run the company however he pleased.

He could hold other people accountable. But the moment a senior hire tried to hold him accountable, he felt threatened — and started quietly labelling them as too expensive.

Here's the thing about systems. They only work if the person at the top lives inside them too. You can't change priorities whenever you feel like it, because there's a process for that now. You can't override your head of marketing's call, because that's her decision now. You can't keep the finances a secret, because the people running things need to know what they're working with.

Every system you add to your company puts a small fence around what the founder gets to do on a whim. For a founder used to doing whatever he wants whenever he wants, that fence feels like a cage.

So he hired senior people to make his company look more grown-up. But he didn't want to grow up himself.

Three questions before your next senior hire

Hiring juniors and hiring people into senior leadership positions are completely different ball games. You can't hire seniors and expect them to be minions — that's not what you hired them for. They will challenge you, because otherwise they can't do their job right. You have to be psychologically prepared for that.

Before your next hire — not just senior hires — stop asking "is this person good?" and ask these three questions instead.

What does this person actually own? Not vaguely. Specifically. What can they point at and say "this is mine"?

What can they decide without checking with you? Including decisions you might disagree with.

What happens to that ownership when their judgment and yours diverge? This is the hard one. If the honest answer is "I'll probably override them," then you haven't actually given them ownership. You've given them the appearance of it.

If you can't answer those three questions clearly before the hire, take a step back. Hiring isn't just a financial decision — it affects both your life and theirs.

But here's the thing: this post isn't really about hiring senior people. It's about what founders are actually willing to give up when they say they want to grow. Bringing in a leadership team isn't just an HR exercise. It's a transfer of trust, authority, and — yes — some control. The founders who do it well aren't the ones who hired the best people. They're the ones who were genuinely ready to let those people lead.