Why Your MSP Still Routes Everything to You

Why you feel like the bottleneck even with a management team

Nearly two decades in. You have a management team, decent revenue, the infrastructure of a real business. And yet every HR issue, every customer fire, every technical problem that nobody else can quite solve still lands on you. One MSP owner described it plainly: "my day seems to be HR and customer services along with the guy that everyone comes to with a problem."

This is not about lacking leadership skills or natural authority. When people bring you every decision, it signals something structural. The business operates from knowledge that lives in your head instead of in repeatable documented processes. Until that knowledge gets extracted and systematized, you are the system. Hiring more people or promoting from within will not change the routing pattern because the documented frameworks those people would need to make decisions independently do not exist yet.

Some owners deliberately keep operations small to sidestep this entirely. One commenter put it: "I consider myself a glorified trunk slammer, with 2 techs, and a great MSP stack... I always was scared to take it to your level because of those challenges you mention." That is a rational choice. But if you have already scaled headcount without systematizing decision-making, you are living in the gap where growth increases the load without building capacity.

1. Every HR judgment call routes to you. Staff conflicts, performance issues, hiring decisions. Your team asks permission instead of applying a framework.
2. Customer escalations skip your managers. Clients know that going straight to the owner gets faster resolution, so they do.
3. Technical problems "nobody else can solve" are your daily interrupts. The escalation path ends at your desk by default.
4. New hires shadow you instead of reading documentation. Because the documentation either does not exist or does not answer the real questions.
5. You cannot take a week off without returning to a pile of decisions. The business pauses when you pause.

The documentation gap (not a leadership gap)

The instinct is usually to hire a managing director. Someone to take the decisions off your plate. But that move is premature when the operational knowledge is still undocumented. A managing director cannot manage what is not written down. They will spend their first year pulling knowledge out of you anyway, with few positive outcomes. You have essentially hired someone to shadow you while you remain the bottleneck.

The work that needs to happen first is knowledge extraction. Pick one common decision type (technical escalations, customer complaints, HR judgment calls) and document your actual framework: the criteria you use, the edge cases, the real examples of when something that looks like a refund situation actually is not. Write down the tacit judgment you have built over nearly two decades so someone else can apply it when you are not in the room.

Most MSP owners resist this because it feels like creating busywork when customer fires are burning. It's easier to just handle the next escalation yourself than to stop and write down what you are doing. But that reflex is exactly what keeps the business dependent on you. Each time you solve it yourself instead of documenting and coaching, you reinforce the pattern where decisions route to you by default.

"It will take you more time, at first, to coach people than just say, 'Oh, it'll be faster (and better) if I just do it myself.' But your people will become more efficient and better."

Extracting what lives in your head

Start with the practical mechanics. Audit one week of decisions that come to you. Categorize them: HR, technical escalation, customer service, vendor relationship. Count which type happens most often. That is where you begin.

Take that category and write down your framework. What signals tell you a customer is genuinely unhappy versus just venting? What threshold determines whether a tech escalation warrants your involvement? Which staff conflicts do you mediate immediately, and which do you let resolve on their own? Include the edge cases where the obvious answer is actually wrong. Use real examples from the past month, anonymized.

Then schedule bi-weekly knowledge extraction sessions for the next decision category, and the one after that. This is not a weekend project. Extracting nearly two decades of operational knowledge is genuinely time-intensive work. But it's also the only way to stop being the person everyone comes to with a problem. The same dynamic shows up in other contexts: if your business runs critical operations on spreadsheets that only you understand, the knowledge lives in your head the same way.

1. Audit one week of decisions. Categorize every question, escalation, or judgment call that lands on you. HR, technical, customer, vendor. Tally each.
2. Pick the most frequent category. This is your first extraction target. Resist the urge to start with the hardest or most interesting one.
3. Write down your actual framework. Not the ideal process, the real one. The criteria you actually use, including the exceptions.
4. Include edge cases and wrong-looking answers. When does the obvious decision turn out to be wrong? Those are the cases your team gets wrong when you are not there.
5. Schedule bi-weekly sessions for the next category. Extraction is ongoing work, not a one-time project. Build the habit.

The coaching time investment

Once the framework exists, the next step is harder. A decision lands on your desk. You have the documented process. Your instinct is to just handle it yourself because coaching someone through the framework will take longer and you already know the answer. That instinct is correct in the short term. Coaching really does take more time initially, often two or three times longer than doing it yourself.

But that short-term thinking is why you are still the bottleneck after nearly two decades. One commenter put it plainly: "It will take you *more* time, at first, to coach people than just say, 'Oh, it'll be faster (and better) if I just do it myself.' But your people will become more efficient and better. You won't need to keep adding and replacing staff, at least not as much."

Track the time delta for the first month: how long coaching takes compared to handling it yourself. Expect it to feel inefficient. The payoff is not immediate. But each coaching session builds capability in your team, and after enough repetitions the decision stops routing to you because someone else can handle it independently. That is how you break the cycle where adding headcount increases the load without building capacity.

Before you hire the MD

So before you hire that managing director or promote someone into a leadership role, get at least your three most common decision types documented and operational. Not polished, not comprehensive, just functional enough that someone else can apply the framework on a real case without pulling you back in.

The business will still have other problems. Documentation alone will not fix a team that fundamentally lacks initiative or judgment. Revenue growth, customer retention, and operational stability come from many factors: market timing, technical excellence, stubborn persistence. But without systematic knowledge transfer, those gains still route through you as the bottleneck. The business cannot scale past what one person can hold in their head.

If nearly two decades of growth still leaves you as the person everyone comes to with a problem, the bottleneck is not your leadership style. It is that the operational knowledge required to make independent decisions lives in your head instead of in documented frameworks your team can use when you are not there.