The statement used to trigger a defensive response from me in earlier years. I agree that certain incubators use it to gaslight and provide low value to pre-seed founders, but I now also understand the undistorted part of that argument.
I’ll use a case study to illustrate:
A company becomes famous for its plant-based fried “chicken” after appearing on Shark Tank. The sharks tasted it and were convinced they had eaten real chicken. Innovative, right? Another successful validation exercise.
Demand surges after the episode airs. These orders bring in more capital than the company has ever seen. The conversion rate is excellent by all metrics.
Growth continues, but the company files for bankruptcy in the midst of it.
What happened?
Most of us understand “scaling” as an abstract business-school phrase. It involves increasing production, hiring, entering new markets, the list goes on. So how do “growth” and “bankruptcy” end up in one picture? Let’s unpack the mechanism of scaling, because it’s more than “secure capital and hire more people.”
Growth changes the nature of the problem you’re solving. When the constraint stops being money, it becomes something else. The thing that propels you to one phase can become the thing that kills your business in the next one.
So I encourage founders to think of a substantial increase in capital as the beginning of their problems, not the end of them.
1 person → 100 pieces of chicken → 1 shift
automatically meaning:
10 people → 1,000 pieces is not a formula.
Real operations often behave more like:
10 people → 600 pieces + ingredient shortages + equipment bottlenecks + quality variation + training overhead + packaging delays + refrigeration constraints + order-management problems and other holes you can’t see.
Knowing how to make something is simply not the same as knowing how to make 100× as much of it. This is one reason prototypes matter a great deal. A prototype isn’t just a marketing object. It is a small-scale operational model. When we prototype, we discover:
• what breaks; why
• what takes unexpectedly long
• which components are difficult to source
• what can be manufactured
• what can be automated
• what customers misunderstand
• which of our assumptions were wrong
Hiring more staff doesn’t fix those constraints. You want to discover the holes in the system while it’s still in its infancy because the nightmare for founders isn’t: “We don’t know how to get 10,000 customers for our business.”
The real nightmare is: “We just got 10,000 orders and we’re out of our depth because we discovered that producing that much requires an entirely different company.”
At 10 customers, you were solving a product problem. At 1,000, it becomes an operations problem. At 100,000, you may be solving an organizational and infrastructure problem. Either way, the company would’ve evolved into a different beast with a vastly different diet or appetite than initially assumed.
At small scale, founders personally compensate for dozens of imperfections and losses without even realizing it. They become the fixers, ensuring the product ships exactly at the standard they’ve proudly set. But the bottleneck moves with scale.
Something like Shark Tank or a viral post happens. Demand goes up. Suddenly the founder can’t personally put out every fire and life comes at them fast: 10,000 orders isn’t a jackpot. It’s 10,000 promises you must deliver on.
Each time you ask yourself: “How do we grow?”
Follow with: “What breaks if we do?”
Try to answer that question in exponentials, before the market commands you to. That is a more useful mental model than assuming multiplication happens indiscriminately and always in the favorable direction once money enters the equation.
The bigger realization of all is that money is just one input into a scaling system. It is not the system itself, and it doesn’t automatically create capacity.