Working On the Business vs. In It: The Hardest Shift a Founder Makes
The phrase is old enough to be a cliche: work on your business, not in it. Every founder has heard it. Almost none of them have been told what it actually requires, or why it is one of the hardest things a founder ever does.
It is worth taking seriously, because the gap between knowing the phrase and living it is where most service businesses get stuck.
What in the business really means
Working in the business is doing the work the business sells, plus all the work that holds it together. Closing the deals. Catching the detail that would have slipped. Being the person every hard question routes to. In the early days, this is not a flaw. It is the job, and you are good at it. That is precisely why it is so hard to let go of.
The trouble is that being excellent at working in the business is what keeps you trapped in it. Every problem you personally solve is a reason the business cannot solve it without you. Your competence becomes the ceiling.
Why letting go feels like losing control
Here is the part the cliche skips. Moving to working on the business does not feel like freedom at first. It feels like risk. When you hand off a deal, it might be closed worse than you would have closed it. When you let someone else own a client relationship, they might handle it differently. Every handoff is a small loss of control, and founders are, almost by definition, people who got here by not letting go.
So the real obstacle is rarely time or even systems. It is the willingness to let the business do something at 85% of how you would do it, so that it can do it without you at all. A thing done well by a system beats a thing done perfectly by you, because the system can do it a thousand times and you cannot.
What working on the business actually looks like
Working on the business is not stepping away or going hands-off. It is changing what your hands are on. Instead of closing the deal, you build the motion that lets someone else close it. Instead of catching the dropped detail, you design the process that stops it from dropping. Instead of being the answer to every question, you build the system that makes the answer obvious.
Your role shifts from operator to architect. The measure of your work stops being how much you personally produced this week, and becomes how well the business ran without you needing to produce it.
The test
There is a simple, uncomfortable test for where you actually are. If you stepped away for a month, what would happen to revenue? If the honest answer is that it would fall, you are still working in the business, no matter what your title says. The goal is a business where the answer is: not much would change. That is not abandonment. That is the thing you were supposedly building all along.