The Founder-Friendly Trap: When Loyalty Hurts Business

The founder sat across from me, visibly uncomfortable. We were discussing his VP of Operations, someone who had been with the company since the garage days. Employee number three. The person who slept on the office floor during the first product launch, who maxed out a personal credit card to cover payroll when the seed round was late.

"He's family," the founder said.

I asked a different question: "Is he drowning?"

Silence. Then, quietly: "He has been for about a year."

I've watched this conversation play out dozens of times across Series A through C startups, particularly in the U.S. and Mexico markets, where loyalty runs deep. The founder knows. The board suspects. The early employee feels it but can't name it. And everyone keeps pretending because the alternative feels like betrayal.

It's one of the patterns that startup executive search surfaces most consistently. At Alder Koten, where I lead executive search across both markets, the assignment often starts the same way: a founder calls about hiring a new leader, and within ten minutes, it becomes clear that the real problem isn't a missing hire. It's an existing one that nobody wants to talk about.

Here's the pattern: the people who built the company are not always the people who can scale it. And the longer founders wait to confront that reality, the more damage loyalty does to everyone involved, including the people they're trying to protect.

 

The Loyalty Tax

There's a term VCs use when describing "founder-friendly" investors. It means patient capital, alignment with the founder's vision, and trust over micromanagement. Founders love hearing it.

But "founder-friendly" has a shadow definition that nobody talks about. In practice, it often means protecting the founder from the hardest decisions they need to make. And the hardest decision in any scaling company is rarely about product or market. It's about people.

Specifically, it's about the original team.

The OG crew earned their place. They showed up when the outcome was uncertain, when the pay was terrible, and when the job description was "whatever needs doing." That loyalty is real, and it matters. But loyalty is not the same as capability. When founders conflate the two, the entire organization incurs what I call the loyalty tax.

The loyalty tax shows up as slower decisions because a key leader can't process information at the pace the company now demands. It shows up as departments that plateau because their leader hit a complexity ceiling three stages ago. It shows up as high performers leaving because they can see the bottleneck that the founder refuses to acknowledge.

The most expensive version of the loyalty tax is invisible: the opportunities the company forgoes because the team lacks the capacity to execute them.

 

What the OG Team Actually Built

To be clear, this is not about ungrateful founders discarding early believers. The early team built something real. They found product-market fit through sheer will. They created culture through proximity and shared risk. They solved problems with creativity because they didn't have resources.

But the skills that build a company from zero to one are fundamentally different from the skills that scale it from one to one hundred. The person who thrived in chaos, who made decisions on instinct, who wore six hats because there was nobody else to wear them, that person was perfectly calibrated for the conditions they were in.

The VP of Sales who personally closed the first twenty deals cannot necessarily build a repeatable sales process for a team of forty. The Head of Engineering who wrote the original codebase and shipped features at midnight can't necessarily architect systems that support ten product teams across two time zones.

None of this means they failed. It means the job changed underneath them while they were still doing it.

This isn't a character flaw. It's a physics problem. A startup of fifteen runs on proximity and trust. A company at 150 runs on systems and delegation. The cognitive demands, the time horizons, the tolerance for improvisation: all different.

That doesn't always mean replacement. Sometimes it means a redefined role, a lateral move, or structured support.

The founder who recognizes this is not being disloyal. They're being honest about what the business needs now versus what it needed then.

 

The Haas Problem

Formula 1 offers a clean example of how this plays out.

When Gene Haas launched his F1 team in 2016, he needed someone scrappy, resourceful, and willing to build from nothing. Guenther Steiner was that person. A former rally mechanic turned engineer who had bounced through Jaguar and Red Bull's early operations, Steiner had the personality and grit to get an American team onto the F1 grid for the first time in thirty years. He was employee number one in every way that mattered.

And it worked. Haas scored points in their debut race. They finished fifth in the constructors' championship in 2018. Steiner became a global personality through Netflix's Drive to Survive, the most recognizable team principal outside of the sport's traditional power brokers.

But somewhere between the Netflix fame and the fifth-place finish, the team stopped progressing. By 2023, Haas sat dead last in the constructors' standings with twelve points. The car couldn't be developed mid-season. Engineers were demoralized. Ayao Komatsu, the team's director of engineering, later revealed he nearly quit during the 2023 Azerbaijan Grand Prix because "people were not talking to each other, no transparency, no alignment." The team, he said, "was not behaving as a team."

Steiner's style, the same scrappy, personality-driven, top-down approach that built the team, had become the ceiling preventing it from growing. The fear-based management that creates urgency in a startup creates paralysis in a scaling organization. The centralized decision-making that works when there are twenty people collapses when there are two hundred.

Gene Haas made the call. He didn't renew Steiner's contract heading into 2024.

The result was immediate. Under Komatsu's leadership, Haas jumped from last place to seventh in the constructors' championship, nearly quintupling their points total. The engineers who had been told for years that "Haas can't upgrade the car" were suddenly developing mid-season improvements that worked.

What changed? Komatsu's answer was disarmingly simple: "Communication. Putting everybody on the same page. Listening to them rather than me telling them."

The talent was always there. The conditions weren't.

 

Why Founders Delay

If the pattern is this predictable, why do founders wait so long to act?

Three reasons, and they compound.

First, guilt. The OG team took risks for you before anyone else would. Replacing them feels like rewriting history, like saying their contributions were insufficient. Founders internalize this as a moral failure rather than a strategic reality.

Second, identity. Founders often see themselves in their early team. The same scrappiness, the same willingness to figure it out. Acknowledging that the OG team has hit a ceiling means confronting the possibility that the founder might hit one too. It's easier to avoid the mirror.

Third, and this is the one that's harder to name: founders delay because the current situation is familiar. Dysfunction you understand feels safer than competence you don't control. A VP who needs your input on every decision is exhausting, but at least you know what's happening. A seasoned operator who runs their function independently requires a different kind of trust, one that some founders aren't ready to extend.

The irony is brutal. The founder who delays this decision out of loyalty is actually being disloyal to the person they're trying to protect. That early employee feels it. They know they're struggling. They see the new hires with more relevant experience. Each month, the founder delays the honest conversation, the person spends a month slowly losing confidence in an impossible situation.

That's not loyalty. That's avoidance dressed up as kindness.

And the board sees it. Every board meeting in which a department's underperformance is explained away with "we're working on it" or "they just need more support" erodes the founder's credibility. Eventually, the board stops trusting the founder's judgment on people entirely. Once that trust is lost, the founder loses control not only of this hiring decision but of every subsequent hiring decision. The very autonomy the founder is trying to preserve gets stripped away because they couldn't make one hard call six months earlier.

 

What "Founder-Friendly" Actually Means

Being truly founder-friendly to the business means making decisions based on what the company needs at this stage, not what it needed at the last one. It means treating early employees with enough respect to have an honest conversation, rather than letting them drown in a role that has outgrown them.

What it should never lead to is silence. The worst outcome is not the hard conversation. The worst outcome is when the founder says nothing, an early employee slowly fails in public, and the board eventually forces a change that strips everyone of dignity.

 

The Pattern

The companies that navigate this well separate gratitude from governance. They honor what was built without pretending the builders are automatically equipped for what comes next. They have the conversation early enough that the early employee still has options, still has confidence, and still has a relationship with the founder that isn't poisoned by years of mutual pretending.

The companies that navigate this poorly wait until the board forces the issue. And by then, the early employee isn't just out of a role. They're out of trust, out of confidence, and often out of the industry entirely.

Steiner built something from nothing. He put an American team on the F1 grid and made it globally relevant. But the team needed different conditions to take the next step. Recognizing that wasn't a betrayal of what he built. It was the only way to build on it.

A founder who can't distinguish between loyalty to a person and loyalty to a business isn't being kind. They're being expensive.

Charlie Solórzano is a Managing Partner at Alder Koten, advising founders and boards on cross-border leadership transitions across the U.S. and Mexico using his proprietary framework: The Race Conditions Model™.