$3.2M in year one. I had built myself the most expensive job I ever worked.
Lesson: Revenue is not the scoreboard I thought it was.
My first year in my first business I did $3.2 million in revenue. I was also sleeping four hours a night and living inside a restaurant. I told my dad like I expected a trophy. He looked at me and said, "it's better to make a dollar doing nothing than a hundred dollars working your ass off." He was mostly teasing. But he was not wrong. I had revenue. I did not have a business. I had built myself the most expensive job I had ever worked and was proud of the number without once looking at what it cost me to produce it.
Insight: The real ceiling is repetition without structure.
- A real business makes money when you are not in the room. Everything else is just a complicated way to stay busy. The revenue going up while your hours match it is not growth, it is a warning sign.
- Most owners hit their ceiling not because of demand, competition, or talent. They hit it because they are answering the same questions, approving the same decisions, and fixing the same mistakes on repeat, without ever building the structure to stop doing it.
- At some point "just part of the job" stops being an excuse and becomes the actual problem. The things that feel necessary usually just feel that way because you have not built the system yet.
The trap is not that you do not know better. The trap is that the number keeps going up, so you stop asking whether any of it is actually working.
Action Item: Find the thing your business should already know how to do without you.
- Think back over the last five business days. Write down one thing you handled personally that came up before, and the time before that. If it is recurring, it is a system problem, not a workload problem.
- Write down what good looks like when that problem is handled correctly. Two to three sentences, plain language. That is the start of the process. No process doc needed yet, just the standard.
- Hand that standard to the person closest to the problem and tell them to own it next time it comes up. Do not coach them through it. Let the standard do that work instead.