Being Needed Is Not the Same as Being Valuable
There is a question I've learned to ask carefully, because it lands hard when it lands right.
A founder is telling me about his team. How much they depend on him. The decisions that still flow through him. The calls that still come to him. Nothing quite closes without him in the room.
He says it with a mix of exhaustion and something that isn't quite pride but sits in the same neighbourhood.
And I ask: who built it that way?
Not as an accusation. As a genuine question. Because the two answers, I did and it just happened, lead to very different conversations. And the honest answer is almost always some version of both.
Here is what nobody says out loud.
Being needed feels like evidence.
Not consciously. Not in a way most founders would admit. But the phone that rings with your name on it, the decision that stalls until you weigh in, the team that looks to you before it moves. All of it carries a signal underneath the noise.
You matter.
For a person who has spent years proving that, years building something from nothing, years carrying more than anyone knew, the signal is not nothing. It's confirmation. The daily proof that what you built still turns on you.
The problem is that confirmation and value are not the same thing.
The business case for staying in the middle is real.
You are faster than the team. Your judgment is better. Your read on the room, the customer, the deal, sharper. When you step in, things move. When you step back, things slow. The evidence keeps arriving, reliably, because you are genuinely good at this.
Which is exactly why the other thing is so hard to see.
A business that needs you to function can be evidence of your value. It can also, at the same time, be evidence of a ceiling. Those two things are hard to hold together, because the first one feels so good it tends to crowd out the second.
You know this. Most founders know this. They've read the books, sat in the offsites, hired the coaches.
They still take the calls.
So the question is not whether you understand the business case for letting go. The question is what letting go would actually mean.
Because for some people, being the one everything runs through is not only a business structure. It is an identity. The role and the self have been the same thing for long enough that separating them is not a management problem.
Try this honestly.
If the business ran well without you in every room. If the team made good decisions without your input. If the calls stopped coming and the questions got answered before they reached you.
What would that feel like?
If the first honest answer is relief, you are in one place.
If something else moves, something that looks like relief but sits differently in the body, you are somewhere more interesting.
I'm not describing weakness. The person who built something that needs him got there by being genuinely useful. By stepping up when stepping up was required. By developing a capacity for carrying weight that most people never build. There's nothing small about that.
But the same thing that looks like commitment from the outside can be doing something else entirely from the inside. The founder who is in every room, on every call, in every decision. He looks invested. Hands-on. Devoted to the outcome.
Sometimes that's true.
Sometimes what's true is that the business became the place where the question of his worth gets answered every day. The answer keeps coming back yes. And without ever deciding it, he built a life where the silence that would come if it stopped is something he can't quite face.
There is a cost to all of this.
The team stops developing judgment they're never trusted to use. The ceiling becomes real. A company organized around one person's bandwidth doesn't grow past it. And the leader himself ends up in something he can't quite name: a life where his own worth is one slow week away from feeling uncertain.
That's the one that's hardest to say out loud.
Because what it means is that the dependency isn't only something the team created.
What am I, if not the one everything runs through?
Most leaders never ask that question.
They stay busy instead. The org chart. The delegation framework. The decision rights. The operating rhythm. All of it real work, and none of it reaching this.
The harder question is the one business conversations don't make room for.
Not how do I build a team that doesn't need me.
But what have I been getting from a team that does?
You probably already know which answer just moved in you.
That's usually where this work begins.
Anthony DiMarco works with founders and leaders on the business and the person running it at the same time. Because the company only ever runs as well as the leader.