One of the activities that I do with some clients is to watch back video recordings of their meetings to try and give some objective feedback on what can be improved. Typically, I get asked to look at sales calls because this is usually a very valuable area to work on.
But a few months ago, I was sent a recording of what was supposed to be a routine client call. The account director had assured the founder (who was also on the call) that the client was happy. Ten minutes in, I watched the founder discover that the client was actually dissatisfied and for the first time, was talking about not renewing their contract in a few months time.
The feedback from the client was direct but fair. The account manager hadn’t sent campaign reports over or joined internal calls that they promised to. Results were actually okay, but the management of the account was very disorganised. The founder had no idea any of this was happening until they were sitting on the call.
Here’s what struck me when watching the video – this wasn’t just about one underperforming team member. This was about what happens when the founder is always there to catch things. Your team never develops the judgement to see problems coming, because they don’t have to. You’ll spot them first and bail them out.
The rescue instinct (and why it’s so hard to resist)
There’s a natural founder impulse when you’re in a meeting and something starts to go sideways. A client asks a question your account manager struggles to answer. Someone on your team gives a response that isn’t quite right. You can feel the conversation tilting.
So you jump in. You clarify. You add context. You rescue the moment.
It feels productive. The client gets their answer. Crisis averted. Your team member looks grateful rather than embarrassed. Everyone moves on and you can see the client visibly relax a little.
But what’s actually happening is you’re preventing your team from developing the capability they need to manage these situations independently. Every time you step in, you’re reinforcing that they don’t need to be the one reading the room, catching the signals, or taking ownership of the relationship.
Once clients become conditioned to founder involvement, transitioning them later becomes significantly harder. But the deeper problem is that by always being present, you never create the conditions for your team to build genuine account management capability.
Or, as one of my first managers taught me – you need to develop your “spidey sense”.
What you’re actually preventing (it’s not just confidence)
When you’re always in the room, your team doesn’t learn to read warning signs. They don’t have to, because you’ll catch them.
This isn’t about confidence or even about specific technical skills. It’s about pattern recognition that only comes from being the one who’s responsible for understanding whether a client is actually satisfied or just being polite. Whether that comment in the meeting was a passing thought or the beginning of a retention risk.
It’s that feeling you have when the client is holding something back, but is outwardly saying that they are happy.
Then a few weeks later, they give their notice and leave.
The specific capability gap that many people have is the difference between executing tasks and genuinely owning accounts. Your team can write the brief, attend the meeting, and send the report. But they can’t gauge satisfaction, spot early retention risks, or understand what “good” looks like for different account types.
What to actually do (and why it requires you to watch things wobble)
The only way your team learns to read the room is by being in rooms where you’re not there to rescue them.
This is genuinely difficult in practice. It means accepting that some things will wobble. That’s the cost of building capability and it’s worth it.
Start with lower stakes situations. Internal meetings where the consequences of a misstep are manageable. Smaller clients where you have strong relationships and some room for error. Renewal conversations where the relationship is solid and you can afford a slightly clumsy approach.
You can be in the room with them, but they need to be the one who feels the tension and holds the conversation.
Your role shifts from participant to coach. Brief them beforehand on what to watch for. What are the signals that the client is actually concerned versus just asking questions? What does good look like for this type of account? Then debrief afterward on what they noticed, or didn’t.
The critical thing here is being intentional about the transition. You’re not just throwing your team in and hoping for the best. You’re deliberately creating situations where they can develop judgement, with appropriate scaffolding and support.
When this doesn’t apply (and the edge cases)
There are genuinely high stakes situations where founder presence is necessary. Major renewals with your largest clients or crisis management when a relationship is already at risk. New business pitches above a certain threshold where your personal involvement is part of what the client is buying.
The difference is whether you’re being intentional or not. The goal is that you’re there by design for a specific reason, not by default because you don’t trust your team or they say that they really need you..
Some clients explicitly pay for founder involvement. That’s fine. But it should be articulated in the agreement and priced accordingly. The goal isn’t to be absent. It’s to make your presence a strategic choice rather than an operational necessity.
The thing we avoid saying out loud
Watching your team struggle in the moment feels irresponsible. Like you’re failing your clients by not jumping in when you could solve the problem in thirty seconds.
But actually, you’re failing your clients more by creating a business model that requires you to be everywhere. A business where account directors can’t spot dissatisfaction until it reaches breaking point. Where team members need you on every difficult call because they’ve never been allowed to handle one alone.
Your clients don’t need you in every meeting. They need a team that’s been allowed to develop judgement. You can’t build that by always being there to catch things.
The wobbles are part of the process. Accept them now, or accept that your agency will always be constrained by how many meetings you can personally attend.