Building Operational Infrastructure From Scratch Inside a Growing Agency
- Operations
There’s a particular kind of chaos that exists inside small agencies. Not the loud, obvious kind. The quiet kind. The kind where everyone is working hard, clients are being served, projects are being delivered; but nobody is quite sure how. Timelines shift. Budgets overrun. A project that should have taken three weeks takes six. A client who seemed happy sends an email that starts with “we need to talk.”
I joined HC Media Group as Chief Operating Officer in Jan 2026. The business had talent, it had clients, and it had genuine ambition. What it didn’t have was a system. My job was to build one.
This is what that looked like.
Starting with the real problem
The first thing I did wasn’t design a process or implement a tool. It was listen. Two weeks of conversations, observations, and quietly mapping how decisions were actually being made versus how people thought they were being made.
What I found was familiar. Directors were spending time on operational decisions that should have been resolved at team level. Team members were waiting for direction that should have been theirs to own. Projects were starting without clear briefs, running without clear budgets, and finishing without anyone asking what could have gone better. Nobody was doing anything wrong. The infrastructure just wasn’t there to let people do things right.
That’s the thing about operational chaos in small businesses. It’s rarely caused by bad people. It’s caused by the absence of structure that allows good people to perform consistently.
Separating operational decisions from business direction decisions
The first structural change I introduced was what I call decision up-flow. The principle is simple: directors should be making decisions about the direction of the business, not the daily operational mechanics of running it.
In practice, this meant creating a fortnightly team lead meeting where operational decisions are made collectively by the people closest to the work. Those decisions are documented, compiled into a monthly summary, and presented to directors for ratification. Anything business critical can be fast-tracked. Everything else follows the rhythm.
It sounds straightforward. The impact isn’t. When directors stop being the default answer to every operational question, two things happen. They get their time back to think strategically. And the team starts building genuine ownership over how the business runs.
The counterpart to this is decision down-flow. Directors set direction. Team leads figure out implementation. The distinction matters because it creates accountability at the right level. “Ben, I need you to figure out how we make a WordPress project work at the £8k pricing mark” is a very different conversation to a director micromanaging a build. One empowers. The other creates dependency.
Documenting what good looks like
You cannot scale what only exists in someone’s head.
One of the earliest things I established was a Team Operations Board; a centralised space where every department documents its process. Not as a bureaucratic exercise. As a practical tool. The development process, the SEO workflow, the project delivery phases. Written down, owned by the relevant team lead, updated as things improve.
The objective is straightforward, if someone new joins the business tomorrow, they should be able to understand how work gets done without it living exclusively in the institutional memory of whoever has been there longest. That’s a fragility most small agencies carry without realising it. The moment a key person leaves, knowledge walks out with them.
Process documentation removes that single point of failure. It also has a less obvious benefit. The act of writing a process down forces the people doing the work to examine it critically. Inefficiencies surface. Inconsistencies become visible. It’s one of the cheapest forms of operational improvement available.
Assigning ownership through Champions
Process without ownership is just documentation that nobody reads.
For each new operational initiative I introduced, I assigned a Champion. Not a manager overseeing it from a distance. A team member with genuine responsibility for making it work. Their job is to facilitate the implementation of a new process, drive its adoption, and ensure it sticks.
This does two things simultaneously. It drives change more effectively than top-down mandates. And it gives individual team members career-based objectives that connect directly to business goals. The person championing the SEO workflow documentation isn’t just completing a task. They’re building expertise, demonstrating leadership, and contributing to something with visible business impact.
In small teams this matters enormously. People need to see that their contribution extends beyond their immediate workload.
Defining capacity before commitments
One of the most common ways agencies destroy profitability is by committing resource they don’t have. A new project lands, everyone wants to say yes, and three weeks later the team is overwhelmed and a client somewhere isn’t getting the attention they’re paying for.
The concept I introduced here is what I call Employee Maximum. Before any project gets scheduled, we need to know how many active projects each team member can carry effectively. Not theoretically. Actually, based on their contracted hours, their current commitments, and realistic delivery expectations.
This feeds directly into scheduling. Project managers need a real view of availability before they make promises. Without it, every commitment is essentially a guess. With it, you can say with confidence whether a deadline is achievable before you give it to a client.
We also introduced a budget overreach threshold. Once a project hits 25% over its agreed internal budget, accountability triggers. Not as a blame mechanism. As an early warning system. The goal is intervention before overruns become crises, not a post-mortem after they already have.
The infrastructure isn’t the destination
What I’ve described here is a foundation. Decision frameworks, process documentation, capacity management, ownership structures. None of it is glamorous. Most of it is invisible to clients. But it’s the difference between an agency that delivers consistently and one that delivers brilliantly sometimes and chaotically the rest of the time.
The commercial case is simple. Consistent delivery builds client trust. Client trust reduces churn. Reduced churn improves financial stability. Financial stability gives the business space to grow intentionally rather than reactively.
I’ve spent most of my career at the intersection of technology and operations. What I’ve learned is that the agencies that scale aren’t always the ones with the best creative work or the most aggressive sales teams. They’re the ones that built the infrastructure to support growth before they needed it.
That work is unglamorous, often invisible, and almost always underestimated.
It’s also the most important work an agency can do.