The Brain Injury Thought Experiment: What Breaks First When You're Gone?

I want you to do something uncomfortable.

Imagine you had a brain injury tomorrow. Nothing fatal. But you're out. Completely unreachable for 90 days. No phone, no email, no Slack. Your team knows you're alive. They know you're coming back. But for the next three months, you don't exist as far as the business is concerned.

Now sit with that for a second.

What breaks first?

If your first instinct was to push the thought away because the answer is too uncomfortable, that's the point. Most MSP owners can't finish that thought without their chest tightening. Not because their business is a disaster. Because they've spent years quietly filling every crack in the foundation themselves, and they've never stopped long enough to look at what they're holding up.

This post is that stop.

Let's actually walk through it

Don't answer this as "here's what should happen." Answer it as "here's what would actually happen." Be honest with yourself. Nobody's watching.

Day one.

The team shows up. Everything looks normal. Your phone isn't being answered but that happens sometimes. A few tickets come in that your senior tech would normally run by you before closing. He makes a call on his own. It's probably fine. Probably.

Your office manager goes to process a timesheet approval and realizes she's been sending those to you for three years. She emails your personal account. No response. She holds it.

A prospect from last week calls back. They want to move forward. Your salesperson, if you have one, takes the call. If you don't have one, it goes to voicemail. Either way, the next step in your sales process is a conversation with you. That conversation doesn't happen.

End of week one.

Payroll is due. Your office manager, your bookkeeper, whoever handles the money, they need an approval. Maybe it's a signature. Maybe it's a login only you have. Maybe it's just that nobody has ever processed payroll without you reviewing the numbers first because that's how it's always worked.

That payroll either gets delayed, gets processed wrong, or someone makes an executive decision they were never authorized to make. None of those are good.

The prospect from day one has gone quiet. No follow-up happened because the follow-up process lives in your head.

Three tickets are sitting in a queue that your techs are unsure about. Not because they don't know the technical answer. Because the decision of how to handle the client relationship around the answer is something you always made. They're waiting. The clock is ticking. The client is starting to wonder.

End of week two.

A vendor calls about a renewal. The contact is you. The decision authority is you. The relationship is yours. Your team takes a message.

Your biggest client has a question about their upcoming QBR. Who's running it? You always run them. Your team scrambles. One of your techs volunteers. He's never run a QBR. The client notices.

Your pipeline is drying up. Every new lead that came in through your network, your relationships, your reputation, those leads either called you directly or came through a process that ends with you. Without you in the system, leads are arriving and going nowhere.

End of month one.

Morale is cracking. Not because your team doesn't care. Because nobody knows who's in charge. You never documented that either. There's a senior tech who's been there six years and an office manager who handles everything administrative and they've been quietly avoiding each other all month because neither one knows whose call it is when something big comes up.

A client escalation hit last week. It needed an owner decision. Your team improvised. The client accepted it but wasn't happy. You'll hear about it when you get back.

Your monthly close didn't happen. Your bookkeeper ran the numbers but the review and approval that leads to any financial decision has always been you sitting down with a spreadsheet. Nobody else has that login. Nobody else knows what they're looking for when they look at those numbers.

New business has completely stalled. Your inside sales process, if it can be called a process, is really just you following up with people you know. Your outside sales, same thing. The pipeline that existed when you left is aging. Nobody is working it because working it means having conversations that require context only you have.

Month two.

Team members are starting to make decisions they shouldn't have to make. Not wrong decisions necessarily. But decisions that should have a framework behind them and don't. Every judgment call is a coin flip because nobody has a clear picture of how you'd want it handled.

A good employee gives notice. Not because anything terrible happened. Because the uncertainty is exhausting and she got a call from someone who wanted her. You would have retained her. You always did. You knew what mattered to her. Nobody else did.

The clients who needed hand-holding are starting to ask questions about stability. One of them calls your office manager and asks directly: "Is everything okay over there?" She assures them it is. But she's not sure herself.

Month three.

Your business is technically still running. Tickets are getting closed. Invoices are going out. But you're returning to a company that's smaller, quieter, and more fragile than the one you left. Some of what broke will be fixable. Some of it won't be.

The part that's hard to say out loud

None of what I just described happened because your team is incompetent. It happened because you built the business with yourself as the load-bearing wall, and you never told anyone which wall was holding the ceiling up.

That's not a criticism. Every MSP owner I've worked with has done the same thing. You got good at something, clients came to you personally, you built a team around yourself, and the business grew. That's how it works in the beginning.

The problem is you never replaced yourself. You got bigger without getting less necessary. And at some point, the gap between what the business looks like from the outside and what it would actually survive became dangerous.

Here's the version of this I see most often. The owner is talented, respected, hardworking. His team is solid. The clients love them. But every important thing in the business runs through the owner. Not because he wanted it that way. Because it just grew that way, one year at a time, one relationship at a time, one judgment call at a time.

Payroll approval. Sales relationships. Client escalations. Vendor decisions. Financial review. Culture leadership. Hiring calls. Every one of those is sitting in one person's lap. And that person has never had a brain injury. So it's never been a problem.

Until it is.

The 30-day version of this test

You don't have to wait for a health scare to run this experiment. Here's the practical version.

Sit down with a piece of paper. Write down every decision that required you last week. Not the big strategic ones. The small ones. The approvals, the client calls, the judgments, the things people brought to you because that's just what they do.

Then sort them into two columns.

The first column is things that genuinely require the owner. Real ownership decisions. Things that should stay with you because they're consequential and contextual and require your judgment in ways that can't be documented.

The second column is things that required you because nobody else was ever set up to handle them. Habit, not necessity. Proximity, not judgment.

That second column is your field guide to-do list.

Everything in that column is a system that needs to be built, documented, and handed off. Not because you want to stop working. Because the day your business can run for 30 days without you is the day it's worth something to someone other than you.

The real question

Here's what I ask every MSP owner who goes through this exercise.

If you had to leave tomorrow, what would you need to build today so the business survives without you?

Start there. Not with systems for convenience. Systems for survival.

That's the whole premise of the field guide. It starts with this question. It ends with a business that has real answers for it.

Frequently asked questions

What is the brain injury thought experiment for MSPs?

It's a planning exercise where an MSP owner imagines being completely unreachable for 90 days. Not a vacation. A genuine forced absence with no check-ins, no phone calls, no Slack. The exercise forces you to trace every function, decision, and relationship that currently runs through you personally, then ask what happens to each one when you're not there. Most owners who go through it honestly find the answer uncomfortable enough to prompt real change.

What are the first things that break in an MSP when the owner is suddenly unavailable?

Payroll approval breaks within days because the authorization chain runs through one person. Sales follow-up stops immediately because the pipeline lives in the owner's head, not in a system. Client escalations pile up because nobody has documented authority to make the call. Those three things break first every time. What surprises most owners is how fast it happens. Not weeks. Days. The business looks fine on the surface until someone tries to do something that requires a decision, and then it becomes obvious that every real decision required the owner.

What's the 30-day MSP readiness test?

Write down every decision that required you last week. Not the big strategic ones. The small ones: the approvals, the client calls, the judgment calls that people brought to you because that's just what they do. Sort them into two columns. Column 1: things that genuinely require the owner. Column 2: things that only came to you out of habit because no system existed for handling them. Column 2 is your build list. When you've cleared it, you have a business that can run without you for 30 days.

How is the thought experiment different from just taking a vacation?

On vacation you have a return date, you can check in if something blows up, and people hold non-urgent things until you're back. A forced absence removes all of those safety valves. It reveals which parts of your business run on systems and which parts run on your personal availability. Most MSP owners discover on vacation that things are fine because people are quietly waiting for their return. The thought experiment removes that option and shows you the real picture.

How do MSP owners start fixing this without it becoming an overwhelming project?

Start with the payroll and financial approval chain. That's the one that creates an actual crisis fastest. Get a second person authorized and trained on every financial function. Then move to client escalation: write down how you'd want your top three client situations handled and give that to your service manager. Then tackle sales follow-up: document the next steps in your pipeline for every active deal and assign them. You're not trying to rebuild the whole business in a week. You're trying to make sure the first five days of your absence don't become a five-alarm fire.

If this thought experiment revealed more gaps than you expected, that's not a failure. That's information. The Field Guide Builder helps you close those gaps one system at a time. Start here.: https://builttorunmsp.com