The Shift Nobody Warns You About.

I sat down with two founders recently. Good conversation, good people, building something real. We were working through what they were experiencing in their organization — the friction, the noise, the feeling that things that used to be easy were suddenly harder. And at some point, one of them looked at me and asked: is this normal?

Yes. Almost always, yes.

What they were hitting is one of the most predictable inflection points in a growing business. It doesn't get talked about enough, and when it does, it usually gets framed as a leadership problem or a culture problem, when really, it's just a math problem. You've crossed a threshold, and the way things worked before simply doesn't scale past it.

Here's what that threshold looks like, and more importantly, what to do when you find yourself standing on it.

When Everyone Knows Everyone

In the early days of a business (let's say under 10 to 15 people) there's something quietly powerful at work. Almost everyone in that room is one or two degrees of separation from the founder. You hired people you knew. Or people someone you trusted knew. Or people whose reputation preceded them from a shared community, industry, or network.

What that creates, without anyone designing it, is a team where everyone has been vouched for. Everyone feels connected to the origin of the business. There's an implicit shared understanding of what you're building and why; not because you held a values workshop, but because it was transmitted through relationship before the first day of work even started.

This does something else too: it creates what I'd call an owner-operator mindset across the whole team. When you're small, people don't think rigidly about roles. They think about what needs to get done. If there's a gap, they step into it. If there's something unfamiliar, they figure it out. They're invested in the outcome, not just the job description. They watch costs. They care about the customer. They're in on the purpose, not because you've communicated it perfectly, but because they've lived it alongside you.

That culture isn't something you built, it emerged. And for a while, it runs the business better than any policy ever could.

What Changes Around 10 to 15

The shift usually hits somewhere between 10 and 15 employees, though I've seen it land a little earlier or a little later depending on the business. Some companies don't feel it until 20 or 25. But it comes.

Here's what changes: you start hiring people who are three degrees of separation out. Someone great comes in who knows someone great, but they don't have that direct thread back to you or to the founding story. They joined a business that was already in motion.

And that's not a problem. That's growth.

But it means the invisible infrastructure you were relying on — shared values by osmosis, trust by proximity, informal alignment — starts to develop gaps.

The owner-operator mindset doesn't transfer automatically. It has to be cultivated intentionally now, instead of emerging naturally. That's a different kind of leadership work, and a lot of founders aren't ready for it because they've never had to do it before.

The Manager Who Never Signed Up to Manage

Around the 8 to 10 employee mark, something else usually happens. It stops making sense for everyone to report directly to the founder. So, someone (usually the person with the most business context, the most product knowledge, the longest tenure) becomes a manager.

Here's the thing… that person was probably never hired to manage. They might never have managed anyone in their life. They became a manager because it made logical sense, not because leadership was ever their calling or their training. And now they're navigating performance conversations, hiring decisions, team dynamics, all in real time, without a roadmap.

This is where employee situations start to surface. Not because the manager is bad at their job. Because they're being asked to do a job they were never prepared for, with tools they were never given. And the team below them feels that gap.

The Inconsistency Problem

By the time a company is 12, 15, 18 people, there's almost always a version of this: employee number two has five weeks of vacation. Employee number five has two. Someone was promised equity when the business needed their skills badly. Someone else negotiated a bonus that nobody else has. A hire was made with a flexible work arrangement agreed to verbally, that nobody wrote down, that three managers ago made a lot of sense.

None of these decisions were wrong when they were made. They were pragmatic, personal, human. That's how early-stage hiring and people-management works.

But now they sit side by side in the same organization, and they're visible to each other in ways they weren't before. And the question employees start asking (sometimes quietly at first, then less quietly) is: why does that apply to them and not to me?

That's not a morale problem. That's a structural problem that's showing up as a morale problem. And the answer isn't to undo the decisions of the past. It's to build the infrastructure that makes future decisions fair, consistent, and defensible.

Product vs. Service: The Timeline Difference

One thing I always flag for founders is that the timeline for this varies a lot depending on what kind of business you're running.

Product businesses (whether you're making something physical or building something digital) tend to hit these growing pains earlier. The reason is that you're often hiring people with deep, specialized expertise. A product engineer, a supply chain specialist, a UX designer. These are people who came for the role, not for the founder. They have skills the business needs that nobody else in the room has. And because of that, they have different conversations at the offer stage, different expectations, different reference points for what "normal" looks like.

Service businesses, on the other hand, tend to carry the informal people culture further; sometimes all the way to 30 or 40 employees. That's because service businesses are already in the business of people. Managing relationships, adapting to clients, working in teams, it's embedded in how the work gets done. That human fluency tends to mask the structural gaps for longer.

Neither path is better or worse. But knowing which one you're on tells you a lot about when to pay attention and how urgently to act.

What This Actually Calls For

When I told these two founders what I was seeing, I think what they were really asking wasn't just is this normal, it was what do we do about it?

Here's the honest answer: the work at this stage isn't glamorous, but it's foundational.

It means getting clear on your people infrastructure before the inconsistencies calcify. Documenting what you've promised and building from there toward something consistent.

Looking honestly at who your first managers are and whether they have the support they need to lead, not just the authority. Being intentional about how you transmit culture to people who didn't come in through the inner network.

It means recognizing that the things that made you successful at 8 people (the informality, the flexibility, the trust that ran on personal relationships) are actually liabilities at 18 if you don't build something more durable underneath them.

None of this requires becoming a corporate, bureaucratic version of what you built. That's the fear I hear most from founders at this stage. They don't want to lose the feeling of what they have. And they don't have to. But the way you protect that feeling isn't by leaving everything informal. It's by getting deliberate about what you actually value and building structure that reflects it, structure that can hold the business as it keeps growing.

The founders I met with left that conversation with more to think about, not less. That's usually how it goes. But they also left knowing that what they were feeling wasn't failure. It wasn't proof that something was broken. It was proof that they'd built something worth growing.

That's a very different starting point.