Monday morning, on my usual running path, I found a man headfirst in a briar patch.
It had rained, so I'd pushed my run to the afternoon. A quarter mile in, I heard groaning coming off the bank of the overflow pond. A man had slipped off a flat, familiar path, gone down the embankment headfirst into the briars, and could not get himself upright. I climbed down and tried to pull him out alone. I could not. So, I called 911, ran up the path to meet the crew, and led them down. It took three of them.
He is okay. But I have been thinking about it all week because the lesson is not about falling.
He was not doing anything recklessly. It was a path he had probably walked a hundred times. One wet step. The fall was not the problem. The problem was that once he was down, he had nothing in reserve to get himself back up.
That is this week's topic: reserve. The capacity to absorb a wrong step and get back up. And why are the businesses that have it worth more than the ones that do not, without anything about the business changing except the way it absorbs a bad day.
A fall never needs a dangerous path
Here's what I often see in owner-run companies. Things are flat and steady. Revenue is fine. Nobody is worried. Then one wrong step arrives, and it is never an exotic one.
A key customer leaves. The owner gets sick. A lender calls the note. A foreman quits.
Any one of those is the wet patch on the trail. None of them is a character flaw or a sign of bad management. In my experience, the businesses that stumble on them are usually the well-run ones, run by careful people walking paths they know. That is the uncomfortable part. Preparation is not a function of how good you are at walking the path. It is a function of what you built before you needed it.
The ones that get back up aren't the lucky ones. They are the ones with reserves already in place. The ones that cannot get up are left hoping someone happens by. Monday's man got lucky: someone came along at a run, and a three-person crew was a phone call away. Most businesses don't get a rescue crew.
What reserve actually is
Reserve gets framed as a cash conversation, and cash matters. But in the businesses, I work with, cash frequently isn't the binding constraint. The real reserve is a set of things that look boring until the day they are not.
Documented systems. When the foreman quits, does the work keep moving because the process is written down, or does the job wait while everyone crowds around the one person who knew? Documentation is what lets the company absorb the loss instead of leaking it.
A team that carries weight. Not a headcount. I mean people who can make the next decision without routing it through the owner. If every consequential decision returns to you, you are not a reserve for the company. You are the single point of failure wearing the title of owner.
Clean numbers. When a lender calls the note or a big customer wobbles, the first thing anyone needs is an honest picture of the position. If the numbers live in the owner's head and a shoebox of statements, the wrong step becomes two wrong steps, because now nobody can see clearly while things move.
Options. A line of credit you arranged while you did not need it. A second supplier qualified for the work one customer dominates. A cross-trained crew. Options are reserves in the most flexible form, and they are cheap to build when nothing is on fire.
Wednesday I asked a version of this as a poll question: when something breaks in the business, what absorbs the shock first? The owner, documented systems, a cash cushion, or no one. I'd bet the most common honest answer is the owner, and that is worth sitting with. The owner as first absorber works, right up until the shock is the owner. Illness, burnout, distraction, a family emergency. The reserve that is a person has the failure modes of a person.
Where this connects to what the business is worth
The Thursday post this week was about OpenAI's new agents, and I want to connect it here, because the two topics turn out to be the same topic.
OpenAI announced always-on agents pitched as something like a chief of staff. I run parts of my own practice on agents. I call them digital employees. The boundary was never fuzzy: they amplify a documented process. They can only run work that is written down. Work in my head stays mine.
And earlier this week one of my own pipelines hit a snag no machine could diagnose. A human had to read it, decide, and route around it. Agents can be an immense help, but they still need humans to keep an eye on them. They amplify a documented process. They do not replace the judgment about what to do when the process breaks.
Which raises the question that matters: when the automation fails, does it fail loudly to a person who knows what to do, or quietly to nobody?
Notice what that question is really asking. It is the briar-patch question. It does not ask whether things go wrong. It asks what is in reserve when they do. A business where failures surface loudly to a person with documented authority and a written process is a business with reserve built into its operations. A business where things fail quietly to nobody is the man in the briars, waiting on the path for someone to happen by.
That same evidence is exactly what a buyer will ask about. A buyer does not pay for the fact that your quoting process lives in your head. They discount it. A process that is written down, that a capable person can run, whose failures announce themselves and get handled, is a process a buyer can diligence and own. Documented systems, a team that carries weight, clean numbers, options. Every one of those is reserve when things break and transferable value when someone looks at buying the business. It is the same work, collected twice.
A business with reserve is worth more to a buyer than the same business that only runs when the owner is in it. Not because the owner is a problem. Because the reserve is proof that the company, not one person, is the asset.
Building it while the path is dry
Nobody builds reserve during the fall. The time is now, while revenue is fine and nobody is worried, which is also exactly when it feels unnecessary. So, keep it small and concrete.
Pick one function that currently depends on one person, and write down how it actually works, exceptions included. Crosstrain one person on a role that would hurt to lose. Get your numbers to the point where you could hand an honest picture of the company's position to a lender or an advisor this week, not eventually. Arrange one option you don't currently need.
None of that is glamorous. All of it is the difference between a business that gets itself back up the hill and one that is waiting for a passerby.
Monday's man was lucky. You do not have to bet on luck.
One question before you close this out: if your business took a wrong step tomorrow, what absorbs the shock first? If the answer is you, I would like to hear which single thing you would build first. I read every reply.
Steve Duke spent about 30 years learning about both sides of this problem. In his corporate career, he worked for Fortune 100 aerospace companies, including GE Aerospace, Lockheed Martin, and General Dynamics. At one of these companies, he ran a multimillion-dollar business unit with full P&L responsibility. He then left to run his own company and discovered that decades of training do not protect you from becoming the business yourself. A serious health event ended it. He exited, recovered, and built Lucensys™ Group around one idea: every owner exits eventually, and the only question that matters are whether they built something that can fund what comes next.
He wrote Failure to Exit about why most owners arrive unprepared.
His next book carries an old warning for owners: the best time to plant the tree was 20 years ago. The second-best time is now.
Lucensys™ Group works with owner-operated manufacturers, distributors, and industrial-services companies doing $2M to $50M, reducing owner dependence and the risk discounts that cost owners at the table. Charlotte, NC - steve@lucensys.io - (704) 953-5608