MSP owner-dependency checklist

Signs the business routes through you

• You are the final escalation point for technical problems, client complaints and vendor disputes.
• Quotes wait for you. So do purchases over a small amount, and hiring decisions.
• Your largest clients call your mobile rather than the help desk.
• A week away means a week of catching up, and you check email anyway.
• You suspect a buyer would ask what happens to the business when you leave, and you do not like the answer.

None of these is a character flaw. Owner dependency is what happens when the owner is the most experienced, most trusted and most available person in the building for a decade. The fix is not working harder at delegating. It is making specific decisions transferable, one at a time.

Step 1: keep a two-week decision log

Memory is a poor guide here; you will remember the big decisions and forget the forty small ones that actually fill the day. For two working weeks, write down every decision or intervention that came to you. It takes a minute each.

Record the delay, not just your time. The cost of owner dependency is mostly in the waiting: the ticket that sat until you replied, the quote that went out two days late.

Step 2: the checklist, area by area

Answer these after the log, using it as evidence. Mark every question where the honest answer is “only me”.

Escalations

• Which escalations in the last month ended with you, and why did they need you specifically?
• Is there a written escalation path that names a person other than you?
• Do technicians escalate to you because they must, or because it is faster than the official path?

Sales and pricing

• Can anyone else quote a standard engagement without asking you?
• Is there a written price list, or does each quote start from your memory?
• Who follows up a proposal if you are away for two weeks?

Purchasing and vendors

• Who can approve a purchase, and up to what amount?
• Which vendors will only talk to you, and which accounts are in your name alone?
• Where are the renewal dates written down?

Client relationships

• For each of your five largest clients, who do they call first — you or the business?
• Has anyone else run a review meeting with them in the last year?
• If you left, which clients would leave with you?

Finance

• Who can see whether last month was profitable without asking you?
• Who raises invoices and chases unpaid ones?
• Does anyone else hold banking or payroll access, with appropriate controls?

People

• Who interviews, onboards and reviews technicians?
• Who decides what a technician works on when two clients both say urgent?
• Who handles a performance problem if you are not there?

Knowledge and access

• Which systems, passwords or configurations exist only in your head or your personal vault?
• Is there documentation for the things only you know, and has someone else used it?
• Could the business recover a critical system with you unreachable for a day?

Step 3: sort every item four ways

Every “only me” from the log and the checklist goes into one of four groups.

Expect the “Keep” group to be shorter than you think, and the “Stop” group not to be empty.

Step 4: hand off with rules, not hope

Delegation fails when the person receiving it does not know their limits, so they keep checking with you. For each item you move, write down:

1. Who owns it now, by name, and who covers when they are away.
2. The decision rule. A spending limit, a list of approved options, a definition of what counts as urgent.
3. When it still comes to you. Be explicit, or everything will.
4. How you will hear about it. A weekly summary, not a request for permission.
5. What happens when they get it wrong. They will, occasionally. If a mistake within the rules leads to the decision coming back to you, the hand-off is over.

Client relationships need their own plan: introduce the person who will own the account, run the next review meeting together, then let them run the one after. Clients follow the person who consistently solves their problems.

A hypothetical example

Imagine an owner whose two-week log has sixty entries. Twenty-two are purchase approvals, most for routine replacement hardware. Fifteen are technician escalations, and in eleven of those the technician already knew the answer but wanted cover. Eight are client calls to the owner’s mobile from the same three clients. The rest are a mix of quotes and vendor questions.

Sorted, the purchase approvals become “delegate with rules”: a spending limit and a short approved-hardware list for the service manager. The escalations split: the eleven where the answer was known point to a missing written escalation path, so the service manager becomes the escalation point with the owner behind them for named situations only. The three clients go into a relationship hand-over plan. Nothing here required new software; it required decisions written down.

A ninety-day sequence

• Weeks 1–2: keep the decision log. Change nothing yet.
• Weeks 3–4: work through the checklist and sort every item. Pick the three items that cost the most waiting time.
• Weeks 5–8: hand those three off, with written rules. Keep a short weekly check-in on how they are going.
• Weeks 9–12: keep a second two-week log and compare. Then pick the next three.

The second log is the measure. If the same kinds of decisions still reach you, find out why before moving on: usually the rule was unclear or the hand-off was undermined by a well-meant exception. If the escalation path is the problem, start there; if you are absorbing unbilled client work personally, the pricing review will show it.