Systems Before Speed
Every growth plan we inherit wants to move faster. Almost none of the businesses we acquire have the systems to survive the speed they are asking for.
A business doing eight million in revenue on informal systems is not a smaller version of a business doing twenty. It is a different organism. The informal version runs on the founder’s memory, a handful of trusted lieutenants, and heroic effort at month-end. It works — until volume, headcount, or a single departure breaks it.
The boring quartet
The infrastructure that matters is almost comically unglamorous. Reliable monthly management accounts, produced in days rather than weeks. A weekly leadership meeting with a fixed agenda and visible actions. A hiring process that exists on paper and is actually followed. Documented pricing authority, so discounts stop leaking margin one exception at a time.
None of this requires consultants or software projects. It requires an owner who insists, gently and repeatedly, that the business runs on process rather than adrenaline — and who models that discipline in their own behaviour.
Speed as an output
The paradox is that systems, which feel like bureaucracy to a founder-led team, are what make speed safe. Clean numbers make decisions faster. Clear authority makes execution faster. A real hiring pipeline makes growth faster. Speed is not something a small business decides to have; it is the output of infrastructure most never build.
We sequence accordingly. In year one we would rather see the management system mature than the revenue line jump. The growth that follows tends to arrive anyway — and unlike growth built on adrenaline, it stays.
— Harp + Partners