You’re Not an MSP Owner. You’re the Highest-Paid Technician on Your Team.
Most MSP owners think the problem is their pricing. Or their team. Or their sales. Fix those and the business takes off.
It doesn’t. Because the problem isn’t any of those things. The problem is identity. And until that changes, nothing else does.
Joe Rojas built and sold three MSPs. By the time he hit a million dollars in ARR on his first one, he’d built what he calls “the most expensive trap you can build” — a company that looked successful from the outside and owned him completely.
“I told myself I was the owner,” Joe says. “I had the title. I signed the checks. I had leadership meetings with myself. But if you watched how I actually spent my day, I was just the guy who answered every escalation. And the business didn’t run. I ran. I ran after every ticket, every technician, every install. Any day I stopped showing up for any amount of time, everything stopped. Because everything stopped where I stopped.”
That’s not a business. That’s a job with a logo.
It Starts When You’re Good at the Work
Almost every MSP starts the same way. You’re better at the technical work than the place you work for. You get sick of making somebody else rich. You go out on your own, get the first client, and do everything. Then the second client. Then the tenth. And you’re still doing everything — except now there’s more of it.
Here’s the trap: you’re good at the work. The work feels productive. You feel like a hero every time you fix something. So every day you reach for the thing you’re best at, which is fixing the broken thing in front of you. You tell yourself you’re building a business. But you’re not. You’re doing a job you also happen to own.
Jeff Loehr calls this the technician’s trap — the same one Michael Gerber described in the E-Myth. You started a business because you were good at a thing. But being good at a thing and being good at running a business that delivers that thing are two completely different jobs.
And every time you take the escalation call, every time you fix the problem yourself because it’ll be faster, every time you sit in front of the ticket queue instead of the strategy doc, you’re choosing one job over the other.
The worst part? It feels like leadership. It isn’t. It’s hiding.
The $1 Million Trap
Reaching a million dollars in ARR feels like an arrival. It’s actually a turning point.
Joe’s first MSP hit seven figures and nothing changed. “I couldn’t take a vacation without the anxiety that the whole thing would fall over while I was gone. I couldn’t go anywhere without a laptop, without a phone, without being connected. I was in the movies sometimes and I’d have to leave the theater. I was physically at my kids’ plays and art exhibits, but mentally I was in my ticket queue.”
More revenue, more clients, more staff — and somehow the trap got tighter. Because more revenue in a workshop just means a bigger workshop. The owner is still the ceiling.
The painful truth: technical skill is the floor, not the ceiling. It’s the table stakes. It’s what you need just to get in the room. The thing that grows a company is the thing most MSP owners have been avoiding all along — because it doesn’t come with the same hit of “I fixed it, I’m the hero, I got it done.”
The 4-Question Test
Before we get to the steps out, here’s a simple diagnostic. Answer honestly.
If you disappeared for two weeks — no phone, no email — what breaks first and how fast?
When a major problem hits, does the team solve it? Or does the team bring it to you to solve?
Look at your last full day of work. How much of it was technical work that a Level 2 tech could have done?
When was the last time you spent a full day working on the business — not in it? Not answering emails about the business, but working on strategy, pricing, what the next 12 months look like?
Jeff adds one more: if a buyer walked in tomorrow and was looking at acquiring your MSP, are they buying a business or buying you? Are they buying the contracts and the systems, or are they buying your personal relationships and institutional knowledge?
If it’s you, there’s no asset. You have a job you can’t quit and can’t sell.
Why It’s an Identity Problem, Not a Skills Problem
Here’s what most MSP owners miss when they decide it’s time to change: they treat it like a competence problem.
“I just need to learn how to delegate better.” “I need better processes.” “I need the right hires.” All of it is true. You do need those things. But they’re not the real blocker.
The real blocker is that your worth, for your entire career, has come from being the best technician in the room. That’s who you are. That’s what makes you feel valuable. So when someone says “stop doing technical work,” it’s not just a calendar change. It’s changing the thing that makes you feel like you matter.
Joe felt it every time he tried to let go. “I’d hire a tech and hand him something, and the second it got hard, I’d swoop in and fix it myself. I kept telling myself he’d learn later. But every time I did it, I taught my team two things: don’t bother getting good — and Joe’s going to take care of it.”
Every individual decision to grab the work back makes perfect sense in isolation. You’re faster. You’re more accurate. The client prefers talking to you. Every single one of those decisions is technically correct.
And the sum of all those correct decisions is a business that can never grow past you.
You can optimize every ticket and lose the company.
The 5-Step Path Out
These steps are in order for a reason. Don’t skip ahead.
Step 1: Run the Priority Analysis. For one week, write down what you actually spend your time on. Then run every item through two questions: Is it urgent? Is it important?
That gives you four quadrants.
High urgency, high importance — the house is on fire. You have to fight it. The problem is that fire should be rare. Every time the house burns, it means you haven’t done the work to make the house fire-resistant.
Low urgency, high importance — making the house fire-resistant. This is the owner’s work. Building systems, fixing pricing, setting strategy, training the team, getting ahead of problems before they become fires. This is the work that never screams at you. And because it doesn’t scream, it never gets done.
High urgency, low importance — pruning the fruit trees. It feels productive, it has to be done at a certain time, and it takes a lot of time. But it’s not leverage. You can outsource it or stop doing it.
Low urgency, low importance — painting the walls. Fine. Not harmful. Not leverage.
Most MSP owners who do this analysis find that nearly their entire week is stacked in the two urgent boxes. That’s the technician’s work: all urgency, no leverage. When you run the analysis, it’s no longer a feeling. It’s right there on the paper.
Step 2: Build Your Hatch Chart. This is not an org chart. An org chart has names in boxes. A hatch chart has the functions that have to happen for the business to run — regardless of who’s doing them.
The seven core functions: Visionary, Strategy, Sales, Client Success, Service Delivery, Operations, Finance, Marketing.
You may be wearing all seven hats yourself right now. That’s fine. The point is to put a name next to each function and see it clearly. Because once Service Delivery is a hat — not just “you” — you can start imagining someone else wearing it. The role becomes separable from the person.
Step 3: Run the CAD Analysis. For every hat you’re wearing, ask three questions. Capacity: do you actually have the time to do this? Ability: are you even the best person for this? Desire: do you want to do it?
What you’ll find is that you’re wearing hats you have no business wearing — and some you’ve been wearing by default for years because nobody else was. The bookkeeping hat. The scheduling hat. Things that have nothing to do with what an owner should be doing.
This is how you sequence the exit. You don’t delegate everything at once. You delegate in order of where the gap between you and the right person is the largest. Low desire, low ability — that goes first. Vision and high-level client relationships — that comes off last, if ever.
Step 4: Document What Only You Know — Then Let Go. This is the step where most owners sabotage themselves.
You’ll delegate the easy stuff. You’ll keep the one thing that makes you the hero — the gnarly escalation that only you know how to handle. And that one thing is the chain that keeps you locked in the business.
You have to write it down. Create the SOP. Extract the thing that lives in your head. And then — this is the part that hurts — you let someone else do it badly the first few times.
They’re going to do it at 80%. You’re going to want to grab it back. You can’t. The cost of them doing it at 80% is the price of you ever being free.
The team that does it at 80% without you beats the team that does it at 100% only when you’re in the room.
Step 5: Schedule Ownership Work and Defend It. Block half a day per week. Put it on the calendar as a recurring commitment. Treat it like a client meeting — it cannot be interrupted. Turn off your phone. Work on strategy, pricing, the next hire, what the next 12 months look like.
The ticket queue will scream. The strategy work will wait quietly. For ten years you’ve answered the ticket. The strategy never got done.
The goal isn’t to never touch technology again. The goal is that when you do touch it, it’s a choice — not a hostage situation. Robert, one of our coaching clients, took a cross-country motorcycle ride. Weeks on the road, most of the time unreachable. His MSP ran the entire time without him.
That’s not a fantasy. It’s what’s on the other side of these five steps.
He didn’t get there by becoming a better technician. He got there by deciding to stop being one.
From MSP to BSP
The MSP is built around a great technician. The BSP — Business Solution Partner — is built around a business that produces great technical outcomes with or without the owner.
The MSP is a job. The BSP is an asset. One you can step away from. One you can sell. One that doesn’t stop running when you stop showing up.
The technician identity isn’t just trapping you. It’s capping what the business can ever be worth.
The whole market is moving in this direction. Clients are taking technical competence for granted. They assume things work. What they’ll pay a premium for is a partner who moves their business forward. You can’t be that partner if you’re buried in the ticket queue.
Where to Start
Take the free BSP Readiness Assessment. Under five minutes. It shows you exactly where the business is most dependent on you and which hat to take off first.
Most owners go in expecting one answer and get a different one. The bottleneck is usually not where they think it is.
