When to Stop Doing Everything Yourself
- May 24
- 5 min read
Most founders begin a startup by doing every job that needs doing, writing the code, talking to the customers, designing the landing page, answering the support emails, and remembering which invoices are still unpaid, and in the first year that habit is genuinely a strength, because you learn the business by being inside every part of it.

In the second year, the same habit quietly becomes the thing that limits the company, because the work expands, the hours run out, the pace slows, and the founder who used to be everywhere starts being late everywhere instead, which means by the time it is obvious that you need to delegate, you have already lost weeks you cannot get back.
Knowing when to stop doing everything yourself is one of the most important judgments a founder makes, and it rarely arrives with a clear signal or a comfortable feeling, which is why so many founders miss the moment when it would have been easiest to act. The aim of this piece is to give you a way to spot the moment earlier than your calendar will tell you.
Why the signal is hidden
The usual advice is to delegate when your calendar gets full, but that advice arrives too late, because a full calendar is the result of a delay rather than a warning, and by the time you are running between meetings, you have already been the bottleneck for a while. The earlier signal is quieter and shows up in your work rather than your schedule, because what slips first is the quality of your thinking, and the slip is small enough that it is easy to dismiss.
You start to notice that decisions you used to make in half an hour now take a day, because you are tired, and ideas you used to have in the shower now do not come, because there is no shower long enough to recover from your week, and customers who used to get a thoughtful reply now get a polite but rushed one, all of which together looks less like a crisis and more like a slightly worse version of you. The risk is that you call it a bad month and keep going, when the truth is that you have been operating below your best self for a while and the company has stopped sharpening even though it is still moving.
Three earlier cues to watch

There are cues that show up before the calendar fills, and they are quieter but more reliable.
The first is when you start dreading work you used to enjoy, not because the work itself has changed, but because there is too much of it stacked behind the work in front of you, and a Tuesday customer call that you once looked forward to now makes you flinch when it appears on your calendar, which is the volume telling you something honest.
The second cue is when you start doing tasks worse on purpose to save time, since you stop reading customer emails carefully, you stop testing the small feature before shipping it, and you write a tweet instead of writing the article you had meant to write, and although each cut feels small in the moment, the pattern adds up to a quiet admission that you are no longer the right person to do all of this work alone.
The third cue is when you start avoiding the work that only you can do, which is the most subtle of the three but often the most telling. Most founders have a few responsibilities that genuinely cannot be handed off in the first year, such as the major partnership conversation, the hard product decision, or the early hiring call, and when you find yourself doing small tasks while these larger ones wait, you are usually using the small tasks to hide, because the load has become too heavy to face the harder work in front of you.
Any one of these cues on its own is normal, but when two or three of them show up in the same month, the company is asking you to delegate, even if your calendar still looks fine on paper.
What to hand off first
When founders finally decide to delegate, they often pick the wrong thing first, because the instinct is to hand off the work you dislike, when the right filter is to hand off the work that is most easily described in writing and least dependent on your specific judgment. Repeatable tasks go first, since customer support replies for common questions, invoice reconciliations, newsletter scheduling, and basic social media posts can all be handed off with a short document and a few examples, and none of these tasks require you specifically, only someone careful.

Tasks that depend on your taste, your network, or your accumulated context should come later, because hiring, fundraising conversations, major product decisions, and the tone of your communication with key customers all rely on judgment that takes time to grow in someone else, and trying to delegate them too early tends to create more work than it removes, since you end up fixing the output rather than doing the job yourself.
How to start without losing control
The fear of delegation is usually a fear of losing the thread, because a founder who has been everywhere worries that handing off any one piece will mean the whole picture falls apart, and that worry is reasonable but solvable.
The way to avoid losing the thread is to delegate the work without delegating the visibility, which means setting up a simple rhythm to stay informed without doing the work yourself, whether that is a weekly summary, a shared inbox you can scan, or a short Friday call with whoever now owns the work, because the rhythm is what lets you trust the system without micromanaging it.
The other piece is to delegate by outcome rather than by process, which means telling the person what good looks like and letting them find their way there, because if you describe every step you would have taken, you have not delegated the task, you have only outsourced your hands.
A closing thought
The day you stop doing everything yourself is rarely dramatic, and it usually shows up as a quiet decision to hand one task to one person and trust them to handle it, after which the pattern repeats and each handoff returns a piece of your week to the work that only you can do, which is the work the company needs most.
Founders who delegate early often look back on the decision as the moment the company started feeling like a company, while founders who delay tend to look back on the same period as the moment they almost quit, and the difference between the two stories is rarely talent or luck. It is the willingness to notice the quieter signals and act on them before the calendar leaves no choice.




Comments