STEP 06
GROWTH MAKES
DEPENDENCE WORSE.
The instinct when you are overloaded is to grow, on the theory that more revenue buys more help. It does. It also multiplies the number of things that route through you, and it feels like progress the entire time.
Scale is an amplifier. It makes a good process better and a bad process unsurvivable.
Why volume deepens the trap
An owner-dependent business does not become less owner-dependent as it grows. Every additional person added without a defined process becomes another source of questions. Every additional customer adds exceptions, and exceptions route to the only person authorized to decide them.
The arithmetic is unkind. Coordination load does not grow with headcount, it grows with the number of pairs of people who have to stay aligned, which rises much faster. Three people have three relationships. Seven have twenty-one. If alignment depends on conversations with you rather than on written definitions of done, your calendar absorbs all of it.
This is why businesses stall at recognizable plateaus. It is not market size or effort. It is that the informal method that got them there has a ceiling determined by one person's available hours.
What has to exist before you add volume
Before turning on more marketing, taking a larger contract, or opening a second crew or a second market, these should already be true.
- The core workflow is written with a definition of done at each handoff, and the people doing it have followed the written version for long enough that its errors have surfaced.
- The seats are defined and someone other than you can decide the routine exceptions.
- The weekly numbers exist and someone other than you would notice if they moved in the wrong direction.
- You know your current constraint and can name it in one sentence. If you cannot, adding volume will find it for you at the worst possible moment.
- Quality is measured, so degradation shows up as a number rather than as a review or a lost customer three months later.
Scaling before these exist is not aggressive. It is expensive, because acquiring customers you then serve badly costs more than not acquiring them.
The rest of the material, including more of Ben Lovro's writing on real estate, business and systems, lives on the main site.
The constraint moves, and that is the whole game
At any moment one thing limits how much work the business can complete. Everything else has slack. Adding capacity anywhere other than the constraint produces cost and no additional output, which is the most common way growth spending is wasted.
The sequence is straightforward and it is a loop. Find the constraint. Relieve it. Find where the constraint moved to, because it always moves. Relieve that. In a small service business it typically walks a familiar path: first the owner's selling time, then delivery capacity, then the estimating or scheduling function, then cash, then management attention.
The signal that you moved the constraint successfully is that the backlog shifts to a different place rather than disappearing. If you add capacity and nothing changes, you added it in the wrong place.
Signs you scaled too early
These show up in a predictable order, and each has a common misdiagnosis.
| What you see | What it usually means |
|---|---|
| More revenue, less cash | Working capital is funding growth and collections have not kept pace |
| Rising complaints in one stage | That stage became the constraint and is being run past its capacity |
| Your hours went up after hiring | You hired into an undefined process and bought supervision |
| Good people leaving | Undefined seats, unclear decision rights, or overload concentrated on the reliable ones |
| Heroics are normal | The process depends on exceptional effort, which is not repeatable and not fair |
Growth worth declining
Not all volume is good volume, and an owner who cannot say no to revenue does not control the business.
Work outside your defined scope is the most common trap. It arrives as a favor for a good customer and it has no process, no standard price, no definition of done and no one trained on it. It consumes the attention of your most capable people, which means it also slows the work you are actually good at.
A written buy box, or its equivalent in your industry, is what lets someone other than you decline correctly. Without it, every marginal opportunity is a decision, and every decision is another item routed through the owner. That is the same bottleneck arriving in a different costume.
The second category worth declining is volume that arrives faster than you can train for it. Capacity in a small business is not hours, it is trained people, and training runs at a fixed speed regardless of how much work is waiting. Accepting six months of work into a team that can absorb two produces late delivery, rework and the departure of the people who carried it, which costs more than the revenue was worth.
Declining well is a process like anything else. A written scope, a standard answer, and a named seat authorized to give it. Then the decline happens on the first call instead of three weeks later after you have been pulled into a conversation about an exception.
Frequently asked
Questions people actually ask
Should I stop growing until systems are in place?
Rarely all the way. The practical version is to stop adding new kinds of work while you write the process for the work you already do. Sequencing beats pausing.
What is the most common constraint in a small service business?
The owner's own selling or estimating time, followed closely by scheduling. Both are decision-heavy and both tend to be undelegated for longer than necessary.
How do I find my constraint?
Look for where work accumulates. The stage with a queue in front of it is the constraint. If the queue is in front of you, that is the answer.
Is it wrong to grow fast?
Speed is not the problem. Growing faster than your definitions of done is the problem, because quality degrades invisibly at first and shows up later as churn and rework.
When is a second location or crew appropriate?
When the first one runs correctly without you on site and there is a documented process someone else has already executed. Replicating an undefined operation reproduces the dependence in a second place.
Does adding people ever fix owner dependence?
Only when they are added into defined seats with real decision rights. Otherwise each hire adds coordination load, and coordination load lands on the owner by default.
Make your next move
A year from now, what will you be glad you started today?
You don't need another promise that everything will be easy. You need something useful to learn — and a next step you're willing to take.