Across very different businesses, the pattern is consistent: growth creates complexity, and complexity eventually demands an operating model. The earlier you build that model, the more choices you preserve.
Scale changes what the company needs from you
I have spent more than three decades building, operating, and scaling technology and services businesses. The industries and technologies have changed. The operating lesson has not: what gets a company to one stage is rarely enough to carry it through the next.
In the beginning, founders and senior operators are often the system. We carry the context, make the decisions, solve the exceptions, and connect functions that do not yet have formal processes between them. That can work extremely well when the organization is small. It is also why early-stage companies can move with a speed that larger companies struggle to reproduce.
But if the business keeps growing, the same approach becomes the constraint. The company starts asking more questions than a small leadership team can answer. The work becomes more interconnected. Errors have a larger consequence. Customers expect consistency. Regulators, partners, and investors expect stronger controls. At that point, scale is no longer about personal capacity. It is about organizational capacity.
I learned to pay attention to the operating model
Earlier in my career, I worked in insurance operations and technology, where the consequences of weak systems and unclear controls become visible quickly. Later, I founded FileControl, an early SaaS e-discovery platform serving large legal departments and law firms. I then spent years helping build operations and technology at Houston International Insurance Group during a period of growth and acquisition integration. Today, through Murkez Technologies and TexInvestCo, I continue to work at the intersection of operations, technology, AI, and ownership.
Those are very different environments, but they all reinforce the same principle: technology does not sit beside the operating model. It is part of it. So are people, process, data, controls, decision rights, and the economics of how the work gets done.
When those elements are designed together, a business becomes easier to scale. When they evolve separately, complexity starts to compound.
Capital can create opportunity. Execution determines what happens next. The best investments are built, not bought.
Growth hides problems until volume makes them expensive
A weak process can survive at low volume because good people compensate for it. An awkward system can survive because someone knows the workaround. A reporting gap can survive because a manager knows which spreadsheet to trust. None of that means the operating model is strong. It means the volume has not exposed the weakness yet.
This is one reason I prefer to look at the exceptions. Where does work leave the normal process? Where does someone have to intervene manually? Which decisions keep moving upward? Where are teams maintaining their own records because they do not trust the shared system?
Those areas often tell you more about the future constraint than the process map does.
Execution has to become institutional, not heroic
I respect people who solve difficult problems. Every business needs them. The mistake is designing a company that requires heroics as the normal operating model.
If the same person has to rescue the same process every month, we do not have a people problem. We have a design problem. If a senior executive has to approve routine exceptions because no one else has the context or authority, we have not scaled the decision system. If growth requires adding another layer of coordination each time, we are scaling complexity instead of capability.
The goal is to capture what the best operators know and turn as much of it as possible into process, technology, information, and clear ownership — without removing the judgment that actually creates value.
AI makes this discipline more important
AI can now perform useful work across almost every business function. We use AI and automation inside managed operations because the value is much greater when the technology is connected directly to the workflow.
But AI does not eliminate the need for operating discipline. In many ways it increases it. You need to know which data can be used, where human review is required, how output quality is measured, what happens when the model is wrong, and who owns the result.
I do not see AI as a separate layer sitting on top of the business. I see it as another capability that has to be embedded into a well-designed operating model.
Scale is about preserving options
A strong operating foundation gives a company choices. It can grow faster without losing control. It can integrate an acquisition more effectively. It can add new capabilities without rebuilding everything underneath them. It can use technology as leverage instead of using people to compensate for technology. It can give management better visibility and investors greater confidence in what the business can absorb next.
That is why I think about scale before the company is forced to. The objective is not to build bureaucracy. It is to make the business simpler to operate as it becomes more complex.
Capital can create opportunity. Execution determines what happens next. The best investments are built, not bought.