Three months into my role as CEO at D-tree International, I realized I had become the bottleneck.
Not because I was incompetent. Not because I didn't care. But because every decision, every approval, every strategic conversation was running through me. The team would submit their work, then wait. And wait. While I tried to context-switch between program design and board presentations and donor relationships and operational planning.
I was working harder than I ever had. And somehow, that was exactly the problem.
Most founders ask when they should hire a COO when they're already drowning. The real question isn't about timing — it's about recognizing the pattern.
The Real Signs It's Time
You know it's time to hire a COO when you catch yourself becoming the thing that slows everyone else down.
Not when you're busy. Every founder is busy. Not when you're stressed. Growth is stressful. But when your team starts organizing their work around your availability instead of around what the business needs.
At D-tree, I started noticing that people would save up decisions for our weekly one-on-ones. Important decisions. Time-sensitive decisions. But because I was the only one who could make them — or at least, that's what we all believed — they would sit and wait.
Meanwhile, I was spending my days jumping between fifteen different contexts. Reviewing a grant proposal in the morning, then switching to a personnel issue, then diving into program metrics, then fielding a donor call. By the time someone needed a decision from me, I needed twenty minutes just to remember what we were talking about.
The work was getting done. But it wasn't getting done well. And it certainly wasn't getting done efficiently.
What Founder Independence Actually Looks Like
Here's what most founders get wrong about operational leadership: they think hiring a COO means giving up control.
What it actually means is giving up the illusion that you have to control everything.
When we brought in operational leadership at D-tree, the shift wasn't that I stopped being involved in decisions. It's that I stopped being the bottleneck for decisions that didn't need me.
Suddenly, the team could move forward on program adjustments while I focused on strategic partnerships. They could troubleshoot implementation challenges while I worked on board relations. Not because I didn't care about those things, but because someone else could carry them with the same level of care and competence.
A founder-independent operation doesn't mean the founder becomes irrelevant. It means the founder becomes available for the work that only they can do.
The Cost of Waiting Too Long
I've seen founders wait until their organizations are in crisis to bring in operational support. Revenue is flat. The team is burned out. Key people are leaving.
By then, you're not hiring a COO to optimize growth. You're hiring them to stop the bleeding.
The founders I work with now — the ones who bring me in as a Fractional COO — are the ones who recognize the pattern early. They're still growing. Their teams are still engaged. But they can see where this is headed if they don't make a change.
They're asking the right question: How do I build this in a way that doesn't require me to be the center of everything?
Not because they want to work less. Most of the founders I know will always work hard. But because they want their work to create momentum instead of just maintaining motion.
It's Not About Size
The question isn't whether your organization is big enough for a COO. It's whether you're ready to stop being the hub through which everything flows.
Some founders need operational support at ten people. Others can go to fifty before they hit the wall. It depends on the business model, the team's experience, the complexity of what you're building.
But here's what I know from experience: if you're asking the question, you're probably closer than you think.
If your team is waiting for you to make decisions that they're perfectly capable of making themselves — if you find yourself saying 'let me think about it' to things that used to be easy — if you're working longer hours but seeing less progress — you might not need to hire a full-time COO tomorrow.
But you probably need to start building the systems and structures that would let you step back from being the center of everything.
The best time to hire a COO isn't when everything is broken. It's when you catch yourself becoming the thing that slows everyone else down. And you decide you want to build something bigger than what you can personally manage.