A man contacted me through a former client to have his life audited from a GeoFree perspective. He was not looking to change much. He wanted to know what business leverage actually looked like, and what he had potentially missed.
His opening line was the sort of thing people say when they believe the hard part is behind them. Two hours of work a day, everything online, running smoothly.
I made an assumption on the spot, and it was wrong. I heard two hours a day and concluded that the Engine work, the income and the structure underneath it, was largely done. Two hours a day sounds like the end of a long project.
Underneath those two hours sat five people. A copywriter. An assistant. A designer. A developer. Somebody handling distribution. Every one of them working at least eight hours a day.
The two hours were true. They were also the only two hours anybody credited.
Hours are a symptom, not business leverage
The reason this matters beyond one person's arrangement is that almost every conversation about scaling a portable business is conducted in hours. How many you work. How few you could work. What you would do with the ones you got back.
Hours are a downstream number. They tell you how the work is currently distributed. They tell you nothing about what happens when the distribution is disturbed, which is the only question that matters once your life is supposed to be able to move.
Two people can both work two hours a day. One of them has a structure that keeps running through a fortnight of silence. The other has a structure in which five people are waiting for approvals that only arrive from one inbox. From the outside, identical. On the day something goes wrong, not remotely comparable.
Business leverage is maximum output from minimal, intentional inputs. What it is not is the appearance of minimal input, produced by moving the input somewhere it does not get counted. A structure where the labour of several people is credited entirely to one is not leverage. It is concealment, however accurate the claim sitting on top of it happens to be.
The fork that is not a fork
Anyone who runs out of hours to sell eventually meets the same advice. Hire people, or build something that earns while you are not in the room. Two roads, pick one.
Both roads can produce the same failure, because the failure is not on the road. It is in the condition neither road automatically satisfies.
Hire people, and you can end up with five specialists who each hold one piece of a process that has never been written down, all coordinated through you. That is not delegation. That is a more expensive version of the same bottleneck, with holiday requests attached.
Build a product, and you can end up with something that needs launching each quarter, needs a list maintained, needs refunds handled and questions answered, and needs the judgement of exactly one person to decide what goes in the next version. Passive is a label attached to work that has moved out of sight.
The condition that decides whether either road produces leverage is simple to state and uncomfortable to apply. Every system should be working to replace itself. Every person doing work should also be training the person who could do it without them. Corporate human resources runs on precisely this logic, whoever can do the work better or cheaper and when to make the switch, whether anybody enjoys hearing it put plainly or not.
Apply that condition and hiring produces leverage. Skip it and hiring produces headcount.
What the fix actually looked like
The fix for the man with the two hour day was not more people. Adding a sixth name to a structure with five undocumented roles just gives you six.
Each of the five trained an apprentice. Each apprentice sat in a different jurisdiction. Lose any one primary, for any reason, and the apprentice becomes the primary and begins training the next one. The succession chain runs by itself, and no single location, illness, resignation or border closure takes a function offline.
His fragility went to close to zero. That is what the audit was for and that is what it produced.
There is a second half to this that I got wrong on my first telling, and it is worth stating rather than tidying away. This was not a shared win. The leverage moved. It did not multiply.
Every apprentice was trained to do exactly one thing, which was to serve that business better. None of them gained a portable, independent version of their own skill. He took the ability to walk away from any of the five, and in the same move he made sure none of them could ever build that ability over him. That is what happened. Anyone building this structure should know that is what they are building.
The version of this that has no employees at all
You might not have five people underneath you. The test still applies, and it applies to a solo practice more sharply than to anything else.
If you sell your judgement, whether as a consultant, an adviser, a designer or anything else where the work is the person, you have the most portable-looking business in existence and one of the hardest to leave. It travels anywhere. It stops the moment you do. The calendar is the inventory and the inventory is you.
Three things separate a practice that owns something from a practice that is a well paid job:
The first is documentation that a competent stranger could act on. Not a summary of what you do. The logins, the judgement calls, the thresholds, the person to call when something breaks. If the document cannot be written, that is not a scheduling problem, it is a description of your exposure.
The second is a second pair of hands on the part that is genuinely repeatable, taken end to end rather than in fragments. Fragments create supervision. Whole tasks create capacity.
The third is a written sequence that exists before anybody arrives. This is the one I resisted for most of my working life. For decades my answer to anyone asking what to prepare before we started was to prepare nothing, because I wanted their organic reactions rather than a script. A client in South Korea eventually told me at the end of an engagement that if the list had existed in advance, we would only have gone over what she could not work out alone, instead of spending two weeks arriving at the same place. She was right. It had never been my job to send that list, and she had never asked for one, which is exactly why it took decades to hear it properly. The sequence had always been the product. It had just never been written down where anyone could use it without me in the room.
The test worth running
Take the list of everything that happened in your business in the last month. Beside each item, write the name of the person who could have done it if you had been unreachable.
Where the answer is a name, that function is distributed. Where the answer is your own name, that function is a dependency, whether or not there is anyone else on the payroll.
Then count. Not hours. Names.
The number of hours you work tells you what this month felt like. The number of functions that fail with you tells you what you have actually built, and whether it can survive being left.