186 The Thing Killing Your Company Is Called Success
Your revenue doubled. Your team tripled. And somehow, everything takes longer than it did when there were five people around one table. You've hired project managers, bought new software, and restructured the team. The problems didn't go away. They just got harder to see.
Growth doesn't break bad companies. It breaks the invisible systems that good companies never knew they were running on.
Every early-stage company operates on informal infrastructure. The founder knows every customer. The salesperson knows every product detail because they sit ten feet from the developer. Information moves fast because proximity makes it move. Nobody writes any of this down because nobody needs to. Then you scale, and all of that vanishes overnight.
The danger isn't that the systems break. It's that they break without announcing themselves. Response times slow. Customers start getting inconsistent answers. Decisions that used to take an hour now require a meeting, then a follow-up meeting, then approval from someone who wasn't in either meeting. You assume it's the people. You hire more. The problems multiply.
The people problem turns out to be a profile problem. Early companies attract fact-finders: people who want to explore everything, learn every edge case, dive into ambiguity. That energy is precisely what you need at zero-to-one. At fifty people and climbing, you need commanders and activators. Execution-oriented people who can build order without losing momentum. The same profile that made someone invaluable at ten people creates friction at a hundred. That isn't about loyalty or failure. It's about what each phase of a company demands.
Meanwhile, silos form before you name them. A developer notices something wrong in the product. The data analyst sees unusual patterns. The salesperson is hearing the same objection from ten different prospects. Nobody has a mechanism to connect those signals. So all three observations disappear into separate inboxes and the company makes a worse decision than any one of those three people would have made alone.
The hardest part isn't operational. It's that the founder's job changes completely and nobody tells you when.
The skills that built the company are the same skills that start slowing it down. Founder energy, creative force, hands-on problem solving: these are exactly what you need at zero-to-one and exactly what you don't need when the company requires a systematic operator. A CEO has three non-negotiable jobs: fund the plan, put the right people in the right seats, and hold the culture. Everything else is delegable. Most founders treat these three things as something to get to after the real work is done.
Add the capital dimension and it gets harder. The bootstrapped scarcity mindset that made you disciplined in year one actively works against you in growth mode. The truism that holds across nearly every founder's experience: it takes twice as long and costs twice as much as planned. Building that into the model isn't pessimism. It's operational reality. Founders who raise "just enough" end up raising again six months later from a weaker position on worse terms.
If your calendar is full of decisions that shouldn't require you, the founder has become the company's operating system. That's not leadership. It's a single point of failure dressed as involvement.
Growth doesn't reveal your company's weaknesses. It amplifies them. The founders who get through this phase aren't the ones who hire their way out of it. They're the ones who figure out which rung snapped first, fix that one, and resist the temptation to treat every symptom as a separate problem.
Watch the Full Episode on scaling growth problems with Chris Franks and Stephanie Hays below:
Follow us to watch live on YouTube and LinkedIn or listen to episodes on Apple Podcasts and Spotify.