The Two Week Absence Test: The Simplest Measure of Owner Dependence

The two week absence test is the simplest measure of owner dependence there is: leave the business for two full weeks with your phone off, then read what broke. Nothing else tells you as honestly where the business still runs through you, and unlike a valuation or a scorecard, it costs nothing to run and cannot be argued with afterwards.

Why two weeks and not one?

One week is survivable on stored goodwill. Decisions wait, invoices sit, and a customer with a problem is usually willing to hold until Monday. Two weeks is past the point where anything can be deferred, so the business has to actually decide, quote, invoice, and apologise without you.

This matters because it is the same question a buyer is asking, only asked earlier and by a friendlier party. A business that needs its owner present is priced as a job with a payroll attached, which is why owner dependence sits alongside customer concentration as one of the two risks that most reliably pull a multiple down.

How do I run it properly?

You are not looking for what went wrong. You are looking for what had to wait for you specifically.

SharePop Studio

• Announce it, do not sneak it. Tell the team the date a month out. The preparation they do in that month is itself part of the result.
• Name a decision-maker before you go. "Ask Dana" is a system. "Use your judgment" is not.
• Turn off the phone rather than promising not to check it. An owner who is reachable is an owner who gets reached, and the test measures nothing.
• Leave one genuine emergency channel with a named person and a written threshold for using it, for example a safety incident or a customer above a certain size threatening to leave.
• Do not pre-clear the calendar. Emptying the fortnight of anything difficult produces a clean result and no information.
• Write the debrief within two days of getting back, while the team still remembers what they improvised.

What am I actually looking for when I get back?

Not whether things went wrong. Things will go wrong whether you are there or not. You are looking for what had to wait for you specifically.

• Decisions that stalled. Anything that sat untouched for a fortnight is a decision category you have not delegated.
• Customers who asked for you by name. Relationship concentration, not loyalty. It is fixable by introducing a second face before the next absence.
• Questions nobody could answer. Knowledge that lives in your head and nowhere else.
• Work that simply stopped. A process with exactly one person who can do it, and that person is you.
• Anything that was quietly done wrong and only surfaced later. The most valuable finding, and the one a shorter test never produces.

What do I do with the list?

Sort it by what would be most expensive if it happened without warning, then fix in that order. Most lists resolve into the same four categories: a deputy who can decide (how to build a second-in-command), processes that exist outside your head (how to document your business processes), relationships held by the company rather than by you (how to transfer customer relationships to your team), and decision rules the team can apply (how to delegate decisions, not just tasks).

Then run it again in a year. The second result is the one worth showing a buyer, because 70% of owners who sold spent under two years preparing, per UBS Investor Watch, and a track record of the business coping without you is the part of that preparation that cannot be produced quickly.

The Advisor Studio by SharePop turns that list into a ranked plan with a dollar figure beside each item, so the order of work is obvious rather than instinctive.