5 Signs you need a 2IC

The processes, the client preferences, the 'how we do things here,' the passwords, the workarounds, the history of why things are set up the way they are. If it lives primarily in your head, you are a single point of failure. And that single point of failure is you.

It develops gradually. Nobody designs it this way. But the business grows around the founder's knowledge and judgment, and there's never quite enough time to extract it, document it, or build systems around it. It's always faster to just do it yourself.

The result is a business that can only run when you're in it. People can execute what you brief clearly, but they can't fill in the gaps, make judgment calls, or hold the picture when you step away. So you never actually step away.

Approving things. Answering questions your team should be able to answer. Solving problems that shouldn't reach you. Deciding things that shouldn't need your input. Track your time honestly for a week. If a significant chunk of it is operational decision-making, you've found the problem.

You are functioning as your own second-in-command. And doing it badly, not because you're not capable, but because it is not where your time and energy should be going. Every hour spent approving a caption or troubleshooting a tool is an hour not spent on the things only you can do. The vision. The strategy. The relationships. The work that actually moves the business forward.

This is the one that causes the most self-doubt. You've invested in help. You have people. And yet you're still running on empty. You feel like you should feel better. Why don't you feel helped?

Because the team needs managing. And if you're the one managing them, you haven't reduced your load. You've shifted it sideways and added a new layer of complexity. Now you have people to coordinate, output to review, questions to field, and the ongoing cognitive weight of keeping track of what everyone is doing and whether it's getting done right.

A team without operational leadership between them and the founder will always route back to the founder. Not because they're incapable. Because that's the path of least resistance when there's nobody else to route to.

This is a real diagnostic. Not theoretical. If you disappeared for 72 hours with no phone, no email, no Slack, what would happen?

If the honest answer is 'probably fine,' your operational foundation is solid enough. If the honest answer involves a list of things to brief first, decisions to pre-approve, fires you'd worry about, and a gnawing anxiety that would follow you the whole time, that's telling you something important.

A business that cannot function without its founder for three days does not have a capacity problem. It has a dependency problem. The business is structurally reliant on your presence, your attention, your judgment, in a way that makes stepping back genuinely risky.

The founder who takes a real break and comes back to a business that held together has built an operation that can actually run. That's not a luxury. That's what a sustainable business looks like.

You can see the problems. You're not oblivious. You know the content system is inconsistent. You know the onboarding process is a bit chaotic. You know the project management tool is set up wrong and nobody's really using it properly. You know you need better reporting, a cleaner team structure, a more documented way of doing things.

You've known it for a while. The list of things-to-fix-when-you-have-time exists somewhere, in your head or a doc or in the back of your mind at 11pm when you can't sleep.

But you can never get to it. Because by the time you've dealt with everything that needs dealing with today, there's nothing left.