There’s a point in almost every growing company where things start feeling harder, even though nothing is obviously broken. Revenue might still be growing, you’re hiring good people, customers are happy, and the product is getting better. But somehow everything takes… longer.
Decisions that used to happen in an afternoon now take three meetings. People complain about communication. Teams are working on things other teams don’t know about, and the CEO spends more time aligning people and less time actually building the business.
The instinct is usually to look at each problem individually. Maybe meetings need to be more productive, communication has gotten messy, managers need more support, and the list goes on. Any (or all) of those things might be true, but they can distract from the bigger issue: the company changed, and the way you run it didn’t.
I’ve watched companies go from a handful of employees to hundreds, from essentially zero revenue to tens of millions of dollars, and eventually into businesses with multiple products, departments and management layers. One thing I’ve learned is that a company with 10 employees, 100 employees and 500 employees might have the same name and sell the same product, but they’re not the same company.
Every time you add a zero to the employee count, the company needs to relearn how to operate. Something I’ve learned the hard way over the years is that a lot of the things that made a company successful at the last stage will actively work against it in the next one.
At 10 people, almost everything works
This is probably one of the most misleading stages of building a company. Building a 10-person company is incredibly hard, but organizationally, you get away with a lot because everyone is still so close to everything.
You don’t need great communication systems when the whole team talks all day. Documentation can be loose because someone usually knows the answer, roles don’t have to be perfectly defined because everyone is doing five jobs, and priorities can change on Tuesday morning and everyone knows about it by lunch.
You might not even have managers yet. Everyone knows the customers and the product, and everyone understands what the company is trying to accomplish. The founder sits in the middle of almost everything.
And it works incredibly well, which is exactly why the problems come later. Founders naturally assume the company should continue operating this way, just with more people.
Then you get to 100
By the time you get to 100 people, the cracks are harder to ignore. The company may still think and operate like the 20-person version of itself, but there are too many people, teams and decisions for that to work anymore.
The founder still wants to know everything happening across the business… but they can’t. Sales assumes product knows what customers are asking for. Engineering assumes sales understands what’s actually on the roadmap. Someone changes pricing and six weeks later someone else is still sending the old deck. A customer gets promised something because nobody realized another team already decided not to build it.
This is usually when everyone starts talking about communication. Maybe communication needs to improve, but that isn’t really the problem. The company has outgrown proximity.
When there were 15 people, information moved because everyone was close to the same conversations. You didn’t have a communication system because people were the communication system. At 100 people, that stops working. Information has to move intentionally, decisions need owners, priorities need to be written down, people need to know who can make which decisions, and managers need to actually manage.
The founder also has to stop being the human API connecting every part of the company, which is particularly difficult because being involved in everything is usually part of what made the founder successful in the first place. At 15 people, jumping into a sales call, rewriting marketing copy, changing the roadmap, recruiting an engineer and fixing a customer issue in the same afternoon is a superpower. At 150 people, doing the same thing can create absolute chaos.
The founder’s job has to shift from being the person who makes things happen to being the person who builds an organization capable of making things happen. Nobody really tells you when that transition occurs. You usually find out because the old way stops working.
Management becomes the product
This is also where management quality starts having a much bigger impact on the trajectory of the company. Early-stage companies can survive mediocre management because strong individual contributors can compensate for it. A great salesperson can work around a mediocre sales manager. A great engineer can work around a mediocre engineering manager. A great customer success person can personally save an unhappy customer.
That stops scaling.
A bad manager with eight people underneath them doesn’t create one problem. Whatever they’re getting wrong now affects eight people, and then those people start hiring. The problem compounds.
This is why promoting the best individual contributor into management can become dangerous. The best salesperson becomes VP of Sales, the best engineer starts running engineering, or the person who has been there longest starts managing a department. Sometimes they’re fantastic. Other times, you look at the org chart a few years later and realize it’s a collection of decisions that made perfect sense two years ago and make absolutely no sense today.
That’s how companies accumulate organizational debt. Nobody intentionally designed the structure. The company grew, people filled the gaps as they appeared, and eventually the structure just happened.
Then you get to 500
At 500 people, you lose something else: the ability for everyone to understand the whole company. People making important decisions may have never met each other. There are employees who have never spoken to the founder and managers managing managers who are responsible for people the executive team may barely know.
That distance changes how people make decisions because everyone starts optimizing for their part of the business. Sales wants flexibility because it helps close deals, while engineering wants predictability because it helps ship software. Finance wants discipline because it helps forecast. Customer success wants exceptions because they help retain customers, while product wants fewer exceptions because exceptions destroy the roadmap.
Everyone can be completely rational and do their job well, and collectively the company can still make terrible decisions.
This is where the job changes again. At 100 people, you need better management. At 500, you need better systems.
You have to figure out how decisions get made, who owns something that crosses multiple departments, how resources get allocated and what happens when two executives disagree. Something learned by a customer success rep needs a way to make it into the product roadmap, and leadership needs a way to know what is actually happening three layers below them.
These might sound like boring organizational questions. At this size, they’re growth questions.
The founder has to change, too
The company isn’t the only thing that has to evolve. The founder does too.
At 10 people, the founder is usually doing the work. As the company grows, more of the job becomes building the team doing the work, and eventually building the system that allows those teams to do the work. That’s a completely different job, and some founders hate it.
The feedback loops are longer. You’re further away from customers and the product, and more of your impact comes through people you hired, who hired other people, who are actually doing the work.
Your words also carry a lot more weight. At 20 people, saying, “We should think about doing this,” might start a conversation. At 500 people, it might accidentally start a six-month initiative.
The blast radius of leadership gets bigger, which means leadership has to become much more intentional.
You can’t preserve the startup forever
I hear founders say some version of “We don’t want to become a big company” all the time. What they usually mean is they don’t want to become slow or bureaucratic. They don’t want people saying, “That’s not my job.”
I agree with all of that. But sometimes the desire to preserve startup culture becomes an excuse not to build the systems the company actually needs. You cannot run 500 people the way you ran 20, and you probably shouldn’t try.
The goal isn’t to preserve the 20-person company. It’s to preserve what made the 20-person company good: urgency, ownership, customer obsession, speed, curiosity and a willingness to challenge assumptions.
Those things can survive. But the operating model around them has to change.
This is where companies get stuck
We talk constantly about product-market fit and eventually go-to-market fit. I think there’s another type of fit that gets much less attention: company-stage fit.
Does the organization you’ve built actually fit the company you’re running?
You can have a $30M revenue company still operating like it’s at $5M. You can also have a $5M company that hired a bunch of executives from $500M companies and suddenly has planning committees, approval processes and layers of management everywhere.
Both are problems. Too little structure creates chaos, while too much structure kills speed. The difficult part is knowing when to change because there is no notification that pops up when you hit 73 employees telling you that your previous operating model is no longer supported.
Instead, you start seeing the symptoms. Decisions take longer, meetings multiply, priorities conflict, work gets duplicated and leadership spends more time stepping in to resolve issues. Everyone is working harder while the company somehow feels slower.
We tend to diagnose these individually as communication, leadership, process, hiring or people problems. And sometimes they are. But when several start happening at once, they’re usually all symptoms of the reality that the company grew faster than the way it operates.
I think that’s one of the least appreciated parts of scaling. The companies that scale well aren’t the ones that figure out the perfect structure early. They’re the ones willing to repeatedly tear apart the structure that used to work.
The organization that gets you from 10 to 100 probably won’t get you from 100 to 500, and the organization that gets you to 500 probably shouldn’t look much like the one that got you to 10.
That’s not losing the culture. That’s scaling the company.
