Building governance before scale makes it unavoidable

Most groups install controls after a failure forces the issue. We would rather carry the cost of oversight early.

Governance is usually retrofitted. A company grows, something goes wrong, and the controls that should have existed for years are installed in the weeks after the incident. The cost of that sequence is rarely counted properly, because it shows up as a lost contract, a departed customer or a regulatory problem rather than as a governance failure.

We have taken the opposite approach, and it is one of the more expensive decisions the Group has made. Building assurance, delegation frameworks, committee structures and reporting standards ahead of the revenue that would justify them means carrying overhead early. It slows the first phase of growth. It is also the reason the second phase is possible.

The principle we work to is blunt: no business should grow faster than its controls and leadership capacity. That is not a statement about ambition. It is a statement about sequence. A company that wins a contract it cannot govern has not won anything, it has acquired a liability with a revenue line attached.

In practice this means a few specific things. Every acquisition requires a named responsible executive before it proceeds, not after. Material contracts are tested for delivery, cash-flow and counterparty risk before they are pursued, not after they are signed. Authority is delegated to the lowest competent level, which requires knowing where competence actually sits rather than assuming it.

It also means confronting underperformance early. The most common governance failure in a growing group is not fraud. It is tolerance: a business that has been struggling for four quarters, a leader who is in the wrong role, a contract that is losing money quietly. Early, fair and constructive intervention is cheaper for everyone involved, including the person on the receiving end of it.

None of this makes a group immune to problems. It changes what happens when a problem arrives: whether it is found by the organisation or by the customer, and whether the response is a process or a scramble.