The COO Who Built a Citadel

A COO Who Built a Citadel can feel like the grown-up move.

The business has reached the point where the founder is tired. Too many decisions. Too many people needing answers. Too many things living inside the owner’s head.

So the answer seems obvious.

Hire the operator.

Bring in the adult supervision.

Build the systems.

Professionalize the company.

We’ve all seen this. A founder finally does what everyone has been telling him to do. He brings in a senior operator to build the structure the business supposedly needs.

And the operator does exactly that.

Processes appear.

Management layers appear.

Frameworks appear.

Meetings multiply.

Dashboards improve.

The business gets more sophisticated.

And less profitable.

That is the part we do not talk about enough.

You Didn’t Hire a COO. You Hired a Cost Structure.

The COO hire makes perfect sense on paper. That is why so many of us make it, or at least think seriously about making it.

We want relief. We want the business to stop running through us. We want someone else to own the follow-through, clean up the chaos, manage the people, and turn all the moving parts into something that feels more like a real company.

There is nothing wrong with wanting that.

But here is where the trap starts.

We think hiring an operator buys us freedom. Sometimes it just buys us overhead.

In this case, the operator was not malicious. He was not incompetent. He did what operators do. He built structure.

The problem was that the structure was not tied to whether the market wanted more of what the company was selling, whether the margins could support the new overhead, or whether volume could justify the cost being added.

So the business kept getting more organized.

And more expensive.

The Business Got More Sophisticated. And Less Profitable.

This is the citadel effect.

From the outside, it looks impressive. There are systems now. There are roles. There are cleaner reporting lines. There is a sense that the business has matured.

But inside, the economics are quietly getting worse.

We have all seen businesses that look impressive from the outside and fragile from the inside. The founder feels like progress is happening because the company finally looks more professional. But nobody stops long enough to ask whether the professionalization is actually helping the business make money.

Nobody asks whether customers actually want more of the product.

Nobody asks whether volume can support the infrastructure.

Nobody asks whether the unit economics justify the overhead.

Nobody asks whether all this structure is making the company more valuable, or just heavier.

Everyone wants a business that looks bigger. Very few stop to ask whether it actually became better.

And that is how cost gets added faster than value.

Not all at once. Not dramatically. Just one reasonable decision at a time.

A new manager.

A new process.

A new meeting.

A new system.

A new layer.

And eventually, the business has built a fortress around itself.

A fortress full of cost.

A System Can’t Save Economics That Never Worked

We saw the same issue with a technology implementation.

A business invested heavily into a platform, but the deeper issue was not the technology itself. The issue was that nobody had clearly translated the business requirements into what the technology needed to do.

That sounds simple.

It is not.

A lot of companies buy the tool first and then try to figure out how the business should fit inside it. That is backwards.

Technology has a nasty habit. It tells the truth. If your economics work, it helps. If they do not, it exposes them faster.

We think technology creates leverage. What it often creates is a faster version of whatever already exists.

The right sequence is boring, but it matters:

  1. Understand the economics.
  2. Validate demand.
  3. Build repeatability.
  4. Then add systems, people, and technology.

That order matters.

Because systems should serve the business. The business should not contort itself around systems.

The Job of an Operator Is Different Than the Job of an Owner

An operator can help run the machine.

But somebody still has to decide whether the machine should be running in the first place.

That is the part founders cannot outsource.

A lot of us eventually discover that what we wanted was not less responsibility. We wanted better leverage. We wanted the business to run without every answer coming from us, but we did not want to hand over the judgment that determines whether the business is actually becoming more valuable.

That is the owner’s job.

The owner has to stay close to the economics. The market. The customer. The money.

If we step away from that too early, we may get the very thing we asked for.

A business with more structure.

More people.

More meetings.

More process.

But not more value.

And if the goal is to build something that can eventually sell, or support family wealth outside the company, that matters.

Because income is not the same thing as asset value.

A business can make money and still be hard to sell.

A business can be busy and still be fragile.

A business can look mature and still depend on assumptions nobody has tested.

Before You Add Another Layer, Stop and Ask This

Before adding another salary, another department, another meeting, or another piece of software, we need to slow down and ask the harder question.

Is growth actually constrained by execution?

Because sometimes the problem is not execution.

Sometimes it is demand.

Sometimes it is pricing.

Sometimes it is margin.

Sometimes it is the fact that the business model cannot support the weight we keep adding to it.

We have all blamed execution for problems that were really economics problems.

That is why a COO hire should never be treated as a cure-all. It may be the right move. But only if the business can support the structure that person is about to build.

If the core issue is unclear demand, weak margins, or a model that depends too heavily on the founder, adding an operator may not fix the business.

It may just make the problems more expensive.

Good Systems Follow Success. They Don’t Create It.

Good systems matter.

But good systems should follow what is already working.

They should help the company deliver more consistently, protect margin, improve customer experience, and make the business less dependent on the founder.

The numbers matter. Margins matter. Profitability matters. But what really matters is whether the business becomes more valuable because of the systems we are building.

We often measure activity because it is visible.

More meetings.

More reports.

More dashboards.

More structure.

Value is harder to measure. That is exactly why we have to measure it.

Because a buyer is not impressed by complexity for its own sake. A buyer wants to know whether the business can keep producing results without the founder dragging it forward every day.

That is the shift from owner-operator to owner-investor.

We stop asking, “How do I get this off my plate?”

We start asking, “Does this make the business more valuable?”

Those are very different questions.

And they lead to very different companies.

The operator was not the villain.

The systems were not the problem.

The meetings were not the problem either.

The problem was that nobody stopped to ask whether all that effort was moving the business closer to what actually mattered.

More customers.

Better margins.

More value.

More options.

That is the trap.

We spend years building businesses that look impressive from the inside while quietly becoming less valuable from the outside.

And by the time we realize it, we have built ourselves a fortress.

A fortress full of process.

A fortress full of meetings.

A fortress full of overhead.

A fortress nobody wants to buy.

Before you make the next COO hire, or add the next layer, ask yourself a harder question:

Are we building a better business?

Or are we just building a bigger version of the same problem?

That answer will determine whether your company becomes an asset… or a very expensive job.