Back to Blog
What’s Really Holding Your MSP Back? How to Find and Fix Your Biggest Growth Constraint

Last summer, I was describing my job to someone thinking about joining our team. I said what was true at the time: I spend a lot of time on a lot of things, but I’m the product guy. I’m not the guy who’s going to go build those relationships long term and push those deals forward. I just don’t have the time.

There were partnership deals we could have been working. We didn’t have the right people or the time to go after them, and a big part of that was me.

Fast forward to early this year. We made a few team changes, and the big one was bringing in someone to take over support and customer success. That’s a really noisy part of the business that needs a lot of attention. From day one, she just took it, figured it out and added a tonne of structure. Everybody suddenly had clear focus on what they were doing.

For me it was transformational. All of a sudden I had about 30 hours free up in my calendar. I could actually think, look at what was going on, read, research and try things.

I didn’t need to work harder. I was the constraint, and we finally spent against it.

Not every problem is worth solving first

Every MSP has dozens of things it could improve. Tickets, onboarding, billing, documentation, reporting, sales. But you have limited cash, limited time and limited management attention. You have to make tradeoffs.

The problem that’s most visible isn’t always the one that matters most. We can’t solve everything at once, and when we try, a fixable problem tends to snowball into some giant thing that feels unsolvable.

So the first job is figuring out what’s actually holding you back.

Identify what’s actually constraining growth

Usually it’s one of these:

  • Not enough sales opportunities
  • Low conversion rates
  • Technician capacity
  • Poor utilization
  • Customer churn
  • Weak margins
  • Working capital and cash flow

And it changes as you grow. Early on, it’s often demand. Then you win enough work that delivery capacity becomes the problem. Then it’s margins, or cash, or the founder’s calendar. Fix one and another shows up.

A while back, we sat down as a leadership team to figure out ours. On the surface, we had a closing issue, and that was clear. But the data was also telling us something more interesting. A big chunk of our new customers weren’t coming from the places where we were spending a tonne of time, a tonne of money, or both. My question was simple: where are they coming from, and how do we go there? Are we focusing on the wrong place?

That’s the question to ask about your own business before you spend another dollar.

Spend against the constraint, not the loudest complaint

Every dollar you add should go at a specific business outcome. If demand is weak, that might mean more sales activity. If you’ve got more demand than your team can deliver, it means more service capacity. Not the other way around.

Invest in the wrong area and you just add cost. Hiring another tech when your real problem is a thin pipeline doesn’t grow the business. It grows payroll.

The flip side matters too. When something really is the constraint, spend on it. We had a CRM clean-up that dragged on far too long. My view was that paying for more hours from the person helping us, to get it done properly now, was a great investment compared with letting it go another few months.

Automation isn’t always the answer

Alex Hormozi told a story on The Diary of a CEO that stuck with me. A company spent roughly $350,000 automating a process that was costing them about $11,000 a month in manual work. The process could be automated. But it wasn’t what was limiting their growth. Their real constraint was demand.

Being able to automate something doesn’t make it the most important thing to automate.

I’m a big believer in automation. Internally, I want every project looked at through an AI lens, with someone technical enough to spot where we could automate. But it has to be done properly, or you’ve just built something that’s hard to maintain. And it has to point at something that matters. Before you automate, ask what return you expect, both financially and in time you actually get back.

Eliminate, simplify, automate, delegate, invest

A simple order of operations for any piece of work:

  1. Eliminate work that serves no useful purpose.
  2. Simplify processes that are more complicated than they need to be.
  3. Automate repetitive, predictable activities.
  4. Delegate what still needs a human.
  5. Invest more resources where the business case justifies it.

On delegation: be specific. “I need help” isn’t helpful. What exactly do you need, from whom, and by when?

Spend human dollars on human value

People are great at relationships, judgment, creativity, accountability and complex problem-solving. Systems are great at speed, accuracy, consistency, repetition and predictable workflows.

Necessary work isn’t always valuable human work. Invoices, reconciliations, reminders and repetitive reports still have to happen. They should just happen as quickly, accurately and cheaply as possible.

That frees your people to focus on higher-value stuff than “did the data make it where it needs to go?” Your best tech shouldn’t be chasing payments. Your service manager shouldn’t be rebuilding the same report every Friday.

Spend aggressively where people create value. Reduce the cost of work that simply has to get done.

Reassess the constraint regularly

Once you fix one bottleneck, another one shows up. That’s normal. It means you’re making progress.

Use your financial and operational reporting to check whether the investment actually worked. Did close rates improve? Did capacity free up? Did margin move?

Then make it part of how you run the business, not a one-time project. We do this through quarterly planning. Each quarter, we ask what’s limiting us now and pick a small number of priorities to go after it.

Don’t optimize everything

Looking back, the answer wasn’t for me to work more hours. I already work a lot. The answer was to find the real constraint, which was my time and attention, and put the right person against it.

Once those 30 hours came back, I could actually think, research and try things, and that’s had a massive impact on where we’re going.

Don’t optimize everything. Find what matters most, and improve that first.