Build It So Growth Can't Break It

Scalable and sustainable get used like they mean the same thing. They don't, and the gap between them is where most new operations quietly die. Scalable is what you can add: more volume, more sites, more headcount, more revenue. Sustainable is whether the thing you built can carry that weight without buckling. You can scale something all the way into the ground.

When you stand up something new from scratch, a division, a function, a whole operation, the pull is to build for the growth you can already see. Chase the demand. Add the people. Book the work. The boring foundation gets skipped, because it doesn't show up on this quarter's number. Then the growth actually arrives, and the foundation isn't there to hold it.

The pattern

A company spots demand it isn't capturing. Someone gets told to stand up a new division to go get it, and the mandate is revenue. So the division gets built as a revenue grab. Pull a few people, point them at the demand, start booking work. For two quarters it looks great.

Then the cracks. Non-standard requests nobody scoped. Work getting taken that never should have been taken. Margin leaking somewhere, and no clean way to see where. The one person who understands how the whole thing actually runs is now the bottleneck on every decision. The division didn't struggle because the demand wasn't real. It struggled because it was built to capture growth and never built to survive it.

There's research that backs this up, and it's blunt. A large majority of fast-growing companies that fail don't fail on the idea. They fail because they scaled before the operation could hold it. The costs of scaling show up immediately, and the revenue lags behind. So the first stretch of any new build is almost all outflow. If you can't see where that outflow is going, adding more volume just makes it worse, faster.

Scale is addition. Sustainability is the order you build in.

Growth is something you bolt on top of what already exists. Sustainability is the sequence you build in before the growth shows up. Get the order wrong and every new unit of volume lands on a slab that was never poured.

The prescription is unglamorous: before you add volume, decide what has to be true for the operation to carry it, and build that part first. Not the pipeline. The thing under the pipeline.

A new division is a foundation problem wearing a growth costume.

When I stood up a new operating division inside a nationwide services operation, the demand was real and the pressure was to just go capture it. The move that made it last wasn't chasing the revenue faster. It was building one door that every non-standard request had to come through, with a clear rule for what work we'd take and who signed off before anyone started.

That single decision did two things at once. It caught the revenue we'd been quietly leaking, and it cut the risk we'd been carrying without even knowing it. Same door. Most new divisions skip this, because a request form feels far too small to matter when there's a growth number sitting on the table. That skip is exactly what breaks them at three times the volume.

The first thing a new division needs isn't a pipeline. It's a rule for what work it will and won't take, and a single place that work comes through.

Build the team that can carry more before you need it.

I built a program management function from almost nothing over about four years, and the thing that stuck with me is that a function either scales or it degrades. There's no holding steady. The difference is whether you put the cadence and the structured problem-solving in early, while the team is still small enough that it honestly feels like overkill.

A team that can take on more work without dropping quality is a team someone designed that way on purpose. Nobody backs into it. And this matters more the bigger you get, because the scarcest thing at scale isn't people or money, it's the attention of the few senior people who can actually see the whole board. If everything routes through them, you've capped the operation at whatever they can personally hold in their heads.

Install the operating rhythm while it feels too early. Once you actually need it, it's too late to install it calmly.

Own the pace of the ramp, or the ramp owns your margin.

Every growth-phase operation gets burned the same way. Somebody staffs to the ceiling, targets full utilization from day one, and forgets that new people aren't billable in their first week. The ramp eats the margin before the revenue ever arrives.

I've watched that happen, and I've been the one who had to stand in front of it. During the growth initiative I ran, leadership wanted to accelerate hiring past what the ramp could absorb. I called for a pause, showed the numbers on what pushing faster would do to our billable rate, and we held. The people we'd already hired became fully productive during the hold, and the next phase stayed sustainable. That's the whole job of an operator some weeks: being the line between ambition and what the operation can physically absorb this quarter.

Build ramp room into every hiring target. If you're staffing to 100%, you're planning to lose margin and calling it growth.

Sustainability is a cadence, not a milestone.

You don't arrive at sustainable and stop. It isn't a box you check once. When I led a West Coast regional turnaround, the performance didn't come back because of some clever new strategy. It came back because we rebuilt the operating rhythm, the weekly review where the numbers were visible and every number had a name sitting next to it. Billability held because the rhythm held. Variance came down because somebody looked at it every single week, not because we started counting harder.

This is the part people miss about building from the ground up. The foundation isn't a document you write once and file. It's the standing habit of looking, out loud, at whether the thing is still working. I've never seen an operation stay healthy on a foundation nobody goes back to check.

Pick the three numbers that tell you the operation is holding, and put a standing time on the calendar to look at them together. That rhythm is the foundation.

Monday morning

If you run an operation: take the newest thing you're standing up, a division, a line, a team, and write down the one rule for what work it takes and who signs off. If that rule doesn't exist yet in plain words, that's your week.

If you advise operations: when a client wants to stand up something new, don't open with the growth plan. Open with what has to be true for them to carry the growth. The sequence is the advice.

If you're earlier in your career: the next time you build anything, a report, a small process, a two-person team, build it so someone else could run it without you. That one habit, designing for handoff from day one, is the whole skill compounding quietly in the background.

Until next Tuesday, Mason

Mason Gray writes weekly on operations leadership at mid-market companies. He advises a few operating teams (Decion Technologies) and is in conversations about senior operations roles. Reply to start one.