New MSP, or Just Better Communication?

We run a site about switching IT providers, so this might be a strange thing to say: some businesses that come to us do not need a new provider. They need a working relationship with the one they have. Switching when the real problem is communication just moves the same frustration to a new logo, and six months of transition effort gets spent fixing nothing.

So before you switch, it is worth an honest hour figuring out which problem you actually have. Here is how we think about the difference, and a checklist to run before you make any calls.

The two kinds of broken

IT relationships fail in two distinct ways, and they feel identical from the owner's chair.

A broken provider lacks the capability or the will: no documentation, no security discipline, one overloaded engineer, billing games, recurring problems that never get root-caused. These are structural. No amount of clearer communication from you fixes a provider who does not have a second engineer or a patching process.

A broken process is different. The provider has capable people and real systems, but the connection between you is misconfigured: tickets go to a personal cell number instead of the helpdesk, nobody on your side is the designated contact, expectations were never written down, and the quarterly review meeting quietly stopped happening two years ago. These failures produce the same symptoms (slow responses, surprises, frustration) but they are fixable in weeks, sometimes in one meeting.

The distinction matters because the remedies are opposites. A broken process deserves a reset conversation. A broken provider deserves a transition plan.

Signs it might just be communication

Consider the fix-it-first route if most of these are true:

• When something is truly on fire, they show up and the work is good. The complaints are about the everyday, not the emergencies.
• Your team texts or emails individual engineers instead of using the ticket system, so half the requests never enter any queue at all.
• You have never actually told them what a good response time looks like for you, and there is no service-level expectation in writing anywhere.
• Invoices confuse you, but when you have asked line-item questions, you got straight answers.
• There is no regular meeting on the calendar. Everything is reactive because no one built a rhythm for it to be anything else.
• The relationship was good once, and nothing dramatic happened; it just drifted as both companies got busier.

The fix-it-first checklist

If that sounds like your situation, run this play before shopping for replacements. It costs one meeting and about 60 days.

1. Name one owner on your side. Pick a single person who routes requests, tracks open items, and speaks for the business. Providers serve chaotic clients badly, and ten people emailing ten engineers is chaos.
2. Ask for their intake rules, and follow them. Every real ticket goes through the ticket system, every time, even from the CEO. You cannot measure response times on requests that were sent to someone's personal phone.
3. Put expectations in writing. One page: how fast you expect acknowledgment, how fast you expect resolution by severity, and how you want to be told about anything that will appear on an invoice. Ask them to agree or counter in writing.
4. Request a monthly 30-minute review. Open tickets, recurring issues, upcoming renewals, one roadmap item. If they run this well, most of your frustration will dissolve within two cycles.
5. Raise the billing questions directly. Ask them to walk you through the last invoice, line by line, once. A good provider treats this as normal. Note how it goes.
6. Set a review date. Sixty days out, on the calendar, with a simple question attached: is this measurably better?

What the checklist reveals

Here is the quiet value of the exercise: it is also a diagnostic. A provider with real capability responds to this reset visibly and fast, because you have just made yourself an easier client to serve well. A provider whose problems are structural cannot fake it for 60 days. The monthly meeting gets rescheduled twice, the written expectations never come back countersigned, the same printer falls off the network again, and the invoice walkthrough gets defensive.

Either way, you learn the truth cheaply, and without burning the relationship or your own credibility on an unnecessary switch.

Signs no amount of communication will fix it

Skip the 60 days and go straight to planning your exit if any of these are true, because they are capability problems, not process problems:

• They cannot show you working MFA, managed endpoint protection, or a tested backup. Security gaps are not a communication style; they are exposure, and your insurer sees them the same way.
• Everything depends on one person, and there is no documentation behind them.
• They hold your domain, DNS, or admin accounts in their own name and get evasive when you ask about it. That is an ownership problem, and it is worth checking today regardless of what else you decide.
• The same root-cause issues have survived multiple honest conversations already. If you have effectively run this checklist before and are reading this article anyway, that is your answer.
• You feel unable to leave because they control access to your own systems. That is the ninth and biggest sign on our list of signs to fire your IT provider, and it only gets worse with time.

An honest way to decide

A second opinion helps here, and it does not have to come from someone with an agenda. When we build a free switch plan, part of the work is mapping what your current provider is actually doing well and badly. Sometimes the plan's honest conclusion is "your setup is sound, fix the process." When it is, we say so, because a client who switches for the wrong reason ends up unhappy with us instead. Month-to-month service only works when the diagnosis is right.