What I Learned Scaling — and Then Unscaling

The whole business world is obsessed with scaling up — more people, more overhead, more of everything, as if bigger is automatically better. I did that. I built up to an 18-person operation. And then I did something the business world rarely talks about: I deliberately unscaled, back down to a lean solo studio producing comparable output. Both directions taught me a lot, and the lessons from unscaling were the more surprising ones. Here's what I learned going each way.

What scaling up taught me

Scaling up genuinely teaches you things, and I don't regret having done it. Running a larger operation forced me to learn systems, delegation, and how to get work done through other people. It taught me what it takes to deliver at volume and how to manage the machinery of a bigger business. Those lessons were real and valuable. But scaling also taught me its costs, which get glossed over in the "growth at all costs" narrative.

• Overhead grows faster than you expect, and it doesn't shrink easily when you need it to.
• Coordination consumes real energy. More people means more communication, more handoffs, more places for things to fragment.
• You drift from the actual work. The bigger it got, the more I managed and the less I did the craft I loved.
• Quality gets harder to control as more hands touch each thing.

Why I chose to unscale

The insight that led me to unscale was that scale had brought costs without proportional benefits for what I actually wanted. Then technology changed the math entirely. With modern tools and a well-built AI system, one focused operator could produce what used to require a room full of people. Suddenly the overhead and coordination of a big team weren't a necessary price of output — they were optional. So I made the deliberate choice to go lean, keeping the output while shedding the weight. It wasn't a retreat; it was an upgrade made possible by a shift in what one person could do.

Scaling up used to be the only way to increase output. Technology broke that link. Now you can increase output and decrease overhead at the same time — if you're willing to unscale.

What unscaling taught me

Going lean taught me lessons I couldn't have learned any other way, and they reshaped how I think about business.

• Coherence beats headcount. Work flowing through one focused operator holds together in a way a larger team struggles to match.
• Overhead was hiding the real economics. Stripping it away revealed how much of "running a business" was just managing the size of the business.
• Focus gets easier when you're lean. Fewer moving parts means more of your energy goes to what matters, which is the whole case for the lean studio.
• Creative control returned. I got back the direct connection to the work that scaling had taken from me.

The lesson isn't "small is always better"

I want to be honest and avoid preaching a new dogma. The lesson from doing both isn't that small is always better than big — it's that the right size depends on your goals and your tools, and that bigger is not automatically better the way the culture assumes. For some businesses and some goals, scale genuinely makes sense. But the reflexive belief that growth means adding people and overhead is outdated, especially now that technology lets one person do so much. The real skill is choosing your size deliberately, based on what you actually want and what your tools make possible, rather than defaulting to "grow bigger" because that's the only story anyone tells.

The question to ask before you hire

The most practical takeaway from having gone both directions is a question I'd urge any founder to ask before adding headcount: is this a job that genuinely requires another person, or is it a job that leverage could handle? For a long time that question had an obvious answer — more work meant more people, full stop. Now it doesn't. A lot of what businesses reflexively hire for can be handled by systems and tools directed by an existing operator, at higher quality and far lower cost. Asking the question honestly, before you default to hiring, can save you from strapping on overhead you don't actually need.

This isn't anti-hiring dogma — sometimes the honest answer is yes, you need another person, and then you hire. But the discipline of pausing to ask changes the trajectory of a business. Every unnecessary hire adds overhead, coordination, and complexity that's hard to reverse, while every job you can handle with leverage keeps you lean and coherent. The founders who build the healthiest businesses in this era aren't the ones who hire fastest; they're the ones who hire deliberately, only when leverage genuinely can't do the job, and let tools handle the rest. That question, asked consistently, is a large part of what let me run lean without sacrificing output.

Before you hire, ask: does this genuinely need another person, or could leverage handle it? For a long time the answer was always 'a person.' Now it often isn't.

Having gone both directions, I'd tell any founder to question the automatic assumption that scaling up is the goal. Sometimes the smarter, more profitable, more enjoyable move is to stay lean and let leverage do the scaling. If you want to think through the right size and structure for your business given today's tools, schedule a strategy session or get in touch.