Scaling a company isn't doing more of what worked. Every stage of growth breaks something specific, and it's usually a habit that used to be your biggest strength. The fix isn't a playbook borrowed from a company ten times your size. It's naming the one constraint your next stage can't live with, making one decision about it, and putting a name and a date next to that decision.
Every stage breaks something
Every growth chart looks like a straight line from the outside. From the inside it's a series of rebuilds. The way you run one location does not run ten, and the way you run ten isn't a bigger version of the way you ran one. A founder can personally review every job at one site. At ten sites, that same habit means nine of them are waiting on one person.
The pattern I see over and over: the things that make a young company fast become the things that make a growing company slow. The founder who answers every question. The operations lead who carries the whole system in her head. Planning that happens informally on a call. Hiring friends of the team because you trust them.
Every one of those is a strength at 20 people. At 80, one of them is your ceiling. The hard part is that nobody wants to call a strength a problem, so the company keeps growing into the wall.
Why big-company playbooks fail at your stage
When founders feel the strain, the instinct is to import structure. A consultant's framework. A process from a former employer. A management layer that worked at a public company.
The reality is that most of this is theory for a company your size. It adds overhead to every part of the business when only one part is actually limiting you. Everything important isn't equally constraining. If you install structure everywhere, you slow down the parts that were working and barely touch the part that wasn't.
What your company needs is the minimum structure for the next stage. Not the structure for the stage after that.
Stage, constraint, decision, control
The sequence I use is simple and it runs in this order.
Stage. Diagnose where you really are, across demand, delivery capacity, cash, leadership bandwidth, systems and founder dependence. Most companies are at different stages in different dimensions. Sales may be ready for $30M while delivery is still running like a $10M business.
Constraint. Find the single condition that limits the move to the next stage, and prove it. "We need better people" isn't evidence. "Every new account adds 6 hours of manual setup and we have 2 people doing it" is evidence.
Decision. Turn the constraint into one leadership decision. Not five initiatives. One call, with one owner.
Control. Put an operating control around it: what gets measured, who reviews it, and what happens at 30, 60 and 90 days.
Write the decision down
This is the step almost everyone skips. Keep a scaling decision log: the decision, the owner, the assumptions you made, the evidence you had, and the date you'll review it.
Why bother? Because six months from now your team will remember the decision differently than you do. A written log turns "I thought we agreed" into "here's what we assumed, and here's what actually happened." It also tells you whether you were wrong about the constraint, which is some of the most useful information a leadership team can get.
Build a machine, not a scramble. Scrambling feels like progress. A machine is what actually carries you to the next stage.
What to do this week
- List the three habits you're proudest of as a company. Ask which one would break first if volume doubled.
- Gather the evidence. Where are delays, rework or escalations piling up right now?
- Pick one constraint and say it out loud to your leadership team: "This is the thing that will stop us from getting to the next stage. Everything else is second."
- Make one decision about it, assign one owner, and put review dates on the calendar at 30, 60 and 90 days.
- Start the log. One page is plenty.
Scaling OS
The Scaling OS walks you from diagnosis to action. It scores your company across the key dimensions to show your stage and your limiting factor, builds a constraint map that asks for real evidence, turns that into a scaling constraint brief with a 30/60/90-day control plan, and keeps a decision log with owners and review dates. It also flags founder dependency, because the easiest way to scale a hidden bottleneck is to be the bottleneck.
Growth will find your weakest point whether you name it or not. Better to name it first.
Open the Scaling OS →Get the next lesson in your inbox
Short, practical lessons like this one for founders running $1M–$20M companies, plus every new free tool before anyone else.
If this is the call in front of you, let's talk it through.
A focused 30-minute conversation. No pitch. Just a direct discussion about the decision and whether I can help.
Book a call with Danny →
Danny Feldman is a 3× founder and the advisor behind Feldman Advisory. He founded and scaled Stellar to $100M in annual revenue across 15 states, raised $55M+ as a founder, and used AI to double revenue before exiting to private equity. Earlier, he recruited and trained 55,000+ sales reps at Cutco and grew a division from 1 to 58 locations. Operator to operator, he now helps founders of $1M–$20M companies get out of the middle of the business, build the leadership team, and raise capital. Book a 30-minute call →