How do you do the owner absence test?

Take each function in turn — finance, people, clients, decisions, compliance, operations — and ask one honest question: if you disappeared for four weeks with no phone, would this keep running, slow down, stop, or create a risk? Mark each one. The functions you mark "stop" or "risk" are your dependency points, and the order you'd worry about them is your priority list for fixing them.

What does it mean if my business fails the test?

It means you have founder dependency — which is normal and fixable, not a failing. It also means real key-person risk: the business is worth less to a buyer, more fragile if you're unwell, and harder to grow because you're the ceiling. The test's value is that it turns a vague unease ("everything comes back to me") into a specific, ranked list of what to change.

The Owner Absence Test

One question, six functions: could your business run for four weeks without you? Where the answer is no, you've found founder dependency.

Understand founder dependency Book a 30-min review

The short answer

The owner absence test is a simple diagnostic for founder dependency: could the owner step away from the business for four weeks without it slowing, stalling or creating risk? Working through each function in turn reveals exactly where the business depends on the owner personally rather than on people and systems.

Take the test

Six functions. One honest question each.

Imagine four weeks away, no phone. For each function, mark whether it would keep running, slow down, stop, or create a risk. Every “stop” or “risk” is a dependency point.

Finance

Would invoicing, bill payment, payroll and BAS keep running on time — without you approving each one?

People

Would staff know what to do, who to ask, and how to handle an issue — without escalating to you?

Clients

Would your key clients be looked after by someone other than you, and not feel the difference?

Decisions

Would day-to-day decisions get made against a clear standard, rather than waiting in your inbox?

Compliance

Would tax, award and cyber obligations still be met, on time, with no one chasing you for a sign-off?

Operations

Would the work get delivered, suppliers managed and problems resolved without you in the loop?

Count your “stop” and “risk” answers. One or two is a business with a few dependency points to close. Four or more is a business that, honestly, still owns you — and a clear map of what to change first.

FAQ

Frequently asked questions

Four weeks is long enough to be real. A business can limp through a long weekend on adrenaline and a few phone calls; almost anything holds for a day or two. Four weeks is the point at which the things that only happen because you personally drive them start to lapse — the follow-ups, the approvals, the decisions, the relationships. It's the timeframe that exposes genuine dependency rather than short-term cover.

Work down your dependency list and move each item out of your head: define the decision so someone else can make it, introduce a second relationship owner, document the knowledge, or hand the function to a team that's accountable for it. A capable back office does the heaviest lifting here — when finance, people, operations and compliance run as a service, most of the "would stop" answers become "would keep running".

Can't find the answer you're looking for? Get in touch

Turn your dependency points into a plan.

A connected back office takes finance, people, operations and compliance off your desk — so the 'would stop' answers become 'would keep running'. Book a 30-minute review.