Most founders know, somewhere, that something needs to change.

Not in a vague, general sense. Specifically. The way work gets handed over. The fact that delivery is still running through them. The projects that close at the wrong price because the relationship matters and they'll make it work.

They know. They've known for a while.

And yet it doesn't change. Not because they lack the intention. Because change in a founder-led agency isn't just operational. It's personal.

The business is a reflection of the founder

In the early years, that's a strength. The founder's instincts, relationships, and standards are the product. They're why clients stayed. Why the team trusted the direction. Why the agency got to where it is.

But at some point (usually somewhere between ten and twenty people) those same instincts become the ceiling.

The way work gets sold reflects how the founder thinks about value. The way delivery runs reflects how they learned to cope under pressure. The way the team communicates reflects what they've learned the founder wants to hear.

When something isn't working, it often traces back to a decision the founder made - reasonably, at the time - that has become the way things are done here.

Pointing that out is complicated. For the founder, it can feel less like operational feedback and more like a verdict on how they built the business. As if getting here wasn't good enough. As if the decisions that worked then were actually mistakes.

That's not a comfortable place to start from.

Why the team can't always make the case

The people closest to the problems often see them most clearly.

The delivery lead who knows exactly which projects are going to run over before they've started. The account manager who absorbs scope because pushing back has never felt safe. The PM who fills in the gaps in every brief because that's just what has to happen.

They know what isn't working. But they've also learned, carefully, what the founder can hear and what they can't.

Feedback that feels like criticism of the founder's decisions tends not to land; or lands badly enough that people stop offering it. So the team adapts. They work around the gaps. They make it work.

And from the founder's perspective, things are broadly fine. The work is getting delivered. Clients are happy. The team isn't complaining.

What they can't see is everything being absorbed on their behalf.

Why financials stay close to the chest

Most founders in agencies of this size carry the numbers alone. Not because they don't trust their team, but because sharing them feels risky in ways that are hard to articulate.

What if the team sees how tight the margins actually are and loses confidence? What if partial information leads to worse decisions than no information? What if knowing the numbers changes the dynamic in a way that's hard to walk back?

So the founder carries it. They make resourcing decisions, pricing calls, and new business judgements with context the team doesn't have. And the team makes delivery decisions without the commercial picture the founder is holding.

What gets lost in that arrangement is more than most founders realise.

The delivery lead who knows a project is priced tightly will behave differently. They'll flag scope earlier. They'll have the client conversation sooner. They'll protect hours more carefully; not because they've been told to, but because they understand what's at stake. Without that context, they're optimising for quality and speed, which is admirable, but it's only half the picture.

When the team doesn't know the numbers, profit becomes something that happens to the business rather than something they're part of. Scope creep is harder to push back on when pushing back feels unrewarding rather than important. Early warning signals (the ones the team are closest to) don't travel upward until it's too late to act on them.

And there's something subtler too. When founders withhold the numbers, teams often sense it even if they can't name it. It creates a dynamic where the founder is managing the team rather than leading with them. Sharing - even partially - tends to shift that in ways that are hard to manufacture any other way.

Both sides are working from an incomplete view. The gap between those two views is often where margin disappears. And where the founder ends up carrying more than they should.

What makes change feel possible

Most founders have tried to fix this.

They've hired a project manager. Introduced a new tool. Run a team meeting about process. Possibly brought in someone to look at the operation and write a report.

And then, six months later, not much has changed. The handovers are still rushed. The financials are still theirs alone. Delivery is still running through them in ways it shouldn't be.

It's easy to conclude from that experience that the team isn't ready, or the timing wasn't right, or that this is just how agencies work at this stage.

But usually the reason change didn't stick is simpler. It was designed around what needed fixing, rather than around where the agency was trying to get to. And it was led by someone inside the system - someone who had to manage the politics of the feedback, the relationships behind the decisions, and their own role in how things got to where they are.

That's too much to hold at once. So the change happens at the edges. The tool gets implemented but the behaviour around it doesn't shift. The process gets documented but not followed. The intentions are genuine. The conditions just weren't right.

The thing an external view actually changes

It isn't the diagnosis. Most founders don't need someone to tell them what's wrong.

What's hard is saying it out loud (in front of the team, or even to themselves) when saying it means examining decisions they made, habits they built, and a way of running things that got the agency here.

An external perspective doesn't carry that weight. It has no history with the decisions that led to this point. It isn't managing a relationship with the person who made them. It can sit in a room with a founder and say "here's what I'm seeing" without it meaning anything other than what it says.

That changes the conversation. Not because the observation is new (often the founder already knew) but because hearing it from outside the system makes it possible to respond to it differently. Without defensiveness. Without it feeling like an indictment.

And crucially, it can start from a different place entirely.

Not what's broken. What you're building.

The most useful question isn't what needs to change.

It's what does this agency look like when it's working the way you want it to?

What does a week feel like when delivery isn't running through you? What does month-end look like when the numbers aren't a surprise? What does it feel like to close a piece of work and trust that what you sold is what gets delivered?

Most founders have a clear picture of that agency. They built this one trying to get there.

Designing toward that - rather than correcting away from the current one - changes what change actually feels like. It stops being about what went wrong and starts being about what comes next.

That's a more honest conversation. And for most founders, it's a more energising one.

Because the goal was never to fix what's broken.

It was to build the agency they meant to build. And most founders are closer than they think.

If you've been sitting with that picture for a while - knowing roughly what needs to shift but not quite finding the conditions to shift it - that's exactly where a Visibility Session is designed to start. Not with a list of what's wrong, but with an honest view of what your operation can currently see, and a conversation about where you're trying to get to.

Book a Visibility Session today.

Latest posts in our blog