From team to institution

There is a moment in every founder-led business that looks like a growth problem but is actually something else entirely.

The business is growing; the product works, the market is getting value from it, and revenue is moving. All the startup boxes are ticked. Yet, almost imperceptibly, growth starts to feel harder than it should. Decisions are slowing down. Delivery becomes inconsistent. The team is capable but not quite coordinated. Investors are engaging and asking questions nobody can answer cleanly.

The instinct is to diagnose this as a systems problem; get a better CRM, hire a head of sales, write an OKR framework, bring in a consultant.

But the problem is rarely the system. The problem is the authority structure that the system is trying to run on.

The authority problem nobody names

Max Weber identified three types of authority: traditional, charismatic, and rational-legal.

Traditional authority, the way things have always been done, custom and precedent as the governing logic, is the third type. The transition from startup to institution is a contest between the other two.

Rational-legal authority is what mature institutions run on. Rules, roles and process hold the authority, not the individual; when the person leaves, the institution continues.

Charismatic authority is what early-stage companies run on. The founder's vision, judgment, and relationships are the company. Decisions flow through one person because that person is the product, the culture, and the strategy simultaneously.

Charismatic authority is not a flaw. It's what gets a company from zero to traction. It's fast, decisive, and energising. It's the survival mechanism of an organisation that doesn't yet know exactly what it's optimising for.

The problem is that charismatic authority doesn't transfer. As the startup grows and matures, charismatic authority becomes a structural constraint. The team ends up executing faster than decisions can be made, because all the deciding still happens in one person's head. The context compounds, the volume of data increases, and the complexity multiplies.

Either the team waits for decisions and execution slows, or it moves without them and coherence breaks down.

Weber called this the routinisation of charisma. It's the defining challenge of scaling: done wrong, it kills the culture; done right, it encodes it.

What institutionalisation actually means

Samuel Huntington, writing about political development (Political Order in Changing Societies, 1968), defined an institution by four properties. He was writing about states. He was also accidentally writing about your startup.

Each property is a spectrum, not a binary.

• Adaptability: can it evolve, or is it locked to the conditions that created it? For a startup: can the company change how it operates as it grows (processes, structure, decision-making), without losing what made it worth building (values, mission, founding edge)?
• Complexity: has it developed differentiated structures, or does everything still run through one person? For a startup: can it develop specialised roles and functions (sales owns pipeline, delivery owns execution, product owns roadmap), or does everything still route through the founder?
• Autonomy: does it operate independently of the individuals inside it, or is it personality-dependent? For a startup: does it operate on its own systems (decision framework, documented process, CRM as system of record), or does it depend on individuals being present? If a key person leaves, does the company leave with them?
• Coherence: does it hold together under pressure, or does it fragment? For a startup: do the parts pull in the same direction under pressure (strategy, incentives, culture, and data all aligned), or do competing priorities win?

Early-stage startups sit at the low end of all four, by design. They require flexibility over rigidity; founder authority over distributed decision-making; conviction over consensus. That's not a flaw; it's the survival strategy of an organisation that doesn't yet know what it's optimising for.

The problem is what happens when it works.

The success trap

Success locks in the patterns that produced it.

The founder whose judgment was the company's competitive advantage can no longer carry everything. The decisions multiply faster than one person can hold them. The culture that felt like energy starts to look, from the outside, like dependency.

Huntington's warning was about societies that mobilised faster than they built institutions to channel that mobilisation. The result was disorder, not because people were bad, but because the vessel wasn't built for the volume. Startups face the same dynamic at every order of magnitude.

The organisation that carried five people cannot carry fifty, and the system that worked at £1m does not work at £5m. The authority that launched the business cannot be the authority that scales it.

Decay is not inevitable

Fukuyama, building on Huntington in The Origins of Political Order, warned about institutional decay: the process by which institutions built for one set of conditions become captured by the individuals within them and lose the autonomy that made them effective.

He called the worst version repatrimonialisation: institutions reverting to personal rule after a period of rational-legal governance, the authority structure collapsing back into charisma.

In startup terms, this is the founder who tried to delegate, watched it go wrong, and concluded that only they can make the right calls. Every process gets bypassed, every decision routes back through the top; the system exists on paper while the company runs on personality.

This isn't weakness; it's the predictable result of institutionalisation attempted without the preconditions for it to hold.

The preconditions

Before systems can scale, something harder has to happen.

The founder has to be genuinely ready for the system to lead. Not ready to tolerate it or delegate tasks, but ready for process over intuition, visibility over control, structure over experimentation, and a decision framework the team can use without the founder in the room.

That readiness is the gating factor for everything else. Governance lands only when the founder trusts it. CRM becomes a behaviour, not a database, only when leadership models using it. Revenue becomes predictable only when the team has both the data and the authority to act on it.

Without that readiness, the technical work of institutionalisation fails: not because the tools are wrong, but because the authority structure underneath hasn't shifted.

What the transition actually requires

The structural work is necessary; it is not sufficient.

Building governance frameworks, installing operating cadence, defining decision rights, creating reporting architecture: all of it is necessary, and none of it is the hard part.

The hard part is the human transition. The founder who built something real through force of will and irreplaceable relationships, letting go of the system they built, trusting a structure they didn't create, accepting that the instincts that were correct are now a ceiling.

That's not a management consulting problem; it's a leadership identity problem. And it's where most technical frameworks fall short, because they address the structure without addressing the person the structure has to run through.

The companies that make the transition cleanly are the ones where the founder does both: changes the system and changes their relationship to it. The companies that fail are the ones where the system changes but the authority structure underneath doesn't.

The question worth asking

For any founder-led business approaching an inflection point: the question isn't whether to institutionalise. It's whether you do it deliberately, before the pressure forces it, or reactively, after the ceiling hits.

The deliberate version is harder in the short term. It requires the founder to do work that feels like it slows the business down, at the exact moment when speed feels like the only thing that matters.

But the deliberate version is the only one that's clean. Because by the time the ceiling hits, the options narrow: investors who were circling start to see dependency rather than capability, the team that was high-performing starts to feel the drag of unresolved authority, and the culture that was the company's edge starts to look, from the outside, like a single point of failure.

The inflection point doesn't wait for readiness; it arrives on its own schedule.

The only question is whether the institution is ready when it does.