CASE 07 · GROWTH EXPOSES DESIGN
Building commercial infrastructure for an industrial manufacturer preparing for expansion shows that growth does not create complexity from nothing. It exposes systems that were never designed to work together.
Growth exposes systems that were never designed to work together, as an industrial manufacturer preparing for expansion found.
The situation in brief.
Industrial manufacturing
Decades of technical credibility
Preparing for expansion
The manufacturer in this case study was not struggling. It had decades of technical credibility in industrial and electrical manufacturing, established customers and a strong reputation. What had not developed to the same degree was the infrastructure behind its commercial and marketing activity: a series of websites built at different times by different suppliers, no consolidated customer information, and no consistent reporting that gave leadership a single view of commercial activity.
None of this was dysfunctional at a smaller scale. Individual people simply held the knowledge that a system would otherwise have held, and that had worked until the business began preparing for genuine expansion.
That is when the nature of the problem changed. One organisation can run for a long time on individual memory — who knows this customer, who remembers that quotation, who has the number. Multiply the moving parts, and the same informality that felt efficient starts producing quiet fragmentation instead.
At that point the useful question stops being “do we need a better website” and becomes “what commercial infrastructure does this organisation need in order to stay coherent as it grows” — a governance question wearing a marketing question’s clothes.
The shift was visible in the questions being asked. A website could no longer be treated as an isolated communications project. The questions became how several entities would present themselves, where enquiries would travel, how customer information would be retained, what leadership would be able to see, and which parts of the system had to remain coherent as the organisation expanded. The deliverables had not changed; the level at which the problem had to be considered had.
Every individual decision had been reasonable on its own terms: a website was needed, a supplier built one. Solving individual problems repeatedly over years does not add up to a system.
Websites, a CRM licence and an agency do not make a commercial ecosystem on their own. Tools only operationalise decisions someone has already made.
Inside individuals it is fragile and leaves with them. Inside the organisation it becomes something leadership can see patterns in.
A system that makes sense only to the person who designed it is not yet an organisational capability. People needed to understand why information was captured.
A CRM is usually treated as a software choice: which platform, what it costs, what it can automate. Those questions come later. The real questions are organisational: what information should the business retain, who owns a given customer relationship, what happens the moment an enquiry arrives, how does someone else know what has already happened, and what should leadership be able to see.
The budget discussion belonged to the same governance problem. Ambition is easy to approve in principle; implementation consumes money, attention and time. Software, content, development, data, training, maintenance and external expertise all compete with other priorities. Connecting the desired future state to those real constraints was part of turning an aspiration into something the organisation could govern.
The same applied to the group of websites. Built independently, each can succeed on its own terms. Once several parts of a business are meant to operate coherently, a website stops being a communications asset and becomes part of an architecture. Reporting carried the same trap: information only has governance value once it changes a decision, so the question was never what could be measured, but what leadership genuinely needed to know in order to decide something differently.
None of this was really about marketing technology. It was about moving the organisation from individual assets towards a system, from knowledge held by people towards knowledge held by the organisation, and from scattered activity towards something leadership could actually see.
The analogy the business understood instinctively is the factory floor: nobody expects production capacity to expand by placing more machines in a room and hoping people coordinate themselves around them. Manufacturing capacity gets designed before it scales. Commercial capacity rarely gets the same discipline, and that gap — not any single decision — is what growth quietly reveals.
Leadership teams reading this case study often continue exploring related business challenges, industries and executive perspectives.
Every organisation operates within its own commercial environment, leadership structure and growth journey. These case studies describe patterns rather than templates. Services can be delivered remotely, and we accept requests from organisations wherever they are located.
