A lot of growing companies land in the same setup: one or two people internally handling the daily IT needs, with an MSP layered on for broader infrastructure management. On paper, it looks like solid coverage. In practice, this arrangement is often the source of exactly the friction it was supposed to prevent.
The question that usually goes unasked is simple: does anyone actually know who owns what?
The coverage illusion
The intuitive logic makes sense. Internal IT handles end users, the MSP handles the infrastructure. Simple division of labor.
In reality, the line between these two is almost never that clean. What happens when an end-user issue turns out to be a network configuration problem? Who is responsible for the SaaS tools that fall outside the MSP’s defined scope? When something breaks at 7pm, who do employees call — internal IT, the MSP, or both?
Both parties are usually doing their jobs. The problem is that the overlap between those jobs is where the gaps live. And gaps rarely have owners.
Signs the arrangement is creating more friction than it resolves
Not every internal IT + MSP setup has this problem. But these are the signals that it does:
Your internal IT person is frustrated by the MSP — and vice versa. When escalations go unacknowledged, when the MSP routes requests back to internal IT that internal IT believes are the MSP’s responsibility, or when the MSP treats the internal team as peripheral rather than as a partner, the relationship becomes adversarial rather than complementary.
The MSP’s service reviews do not involve your internal IT staff. If the MSP is reporting directly to the business owner or COO without including the people who work inside the environment every day, that is a signal that oversight is being treated as an executive function rather than a team function.
Your internal IT person is spending most of their time on work the MSP should be handling. Or the reverse — the MSP is fielding requests that should be handled internally. Scope confusion drives inefficiency in both directions.
Nobody can answer the question “who owns this?” Pick a critical system — your backup environment, your email platform, your security tooling. If the answer to who is responsible for it is “well, the MSP handles the infrastructure but IT manages the users,” that ambiguity is an operational risk.
The question nobody asks
Most companies with this setup have never formally documented the scope of the MSP’s responsibility versus the scope of internal IT. The MSP’s statement of work defines specific services, but there is a wide territory between “MSP scope” and “internal IT scope” where nobody has drawn a line.
That undocumented middle is where problems accumulate. Things that both parties assumed the other was handling. Recurring issues that get closed by the help desk without root cause because the root cause lives in someone else’s lane. Vendor relationships that drift because neither party has a clear mandate to manage them.
What a healthy version of this looks like
The goal is not to restructure either the MSP relationship or the internal IT role. It is to make the overlap visible and intentional.
That means a documented scope of work that both parties have reviewed and agreed to, with explicit coverage for the gray areas. It means internal IT having a clear mandate — and an escalation path that actually works — so they are not fighting for the MSP’s attention. It means someone periodically reviewing whether the arrangement is still working as the business grows, because what made sense at 40 employees often needs adjustment at 75.
It also means having someone above both parties who can see the whole picture. Internal IT is too close to daily operations to evaluate the MSP’s strategic performance. The MSP is not positioned to evaluate itself. And a business owner or COO is usually not equipped to evaluate either one.
Where fractional IT leadership fits in this picture
Fractional IT leadership does not replace internal IT or an MSP. It operates above both of them.
In the specific scenario of internal IT plus an MSP, the fractional IT leader’s job is to define who owns what, hold the MSP accountable to its scope, give internal IT a clear mandate and someone to escalate to, and make sure the arrangement is producing the outcome the business actually needs. It is the structure that makes both relationships more effective rather than less.
For business owners and COOs, it means no longer needing to be the tiebreaker in every escalation that crosses the line between internal and external IT. That decision fatigue is real. It is also entirely avoidable.
If the internal IT plus MSP arrangement at your business feels like it should be working better than it is, the issue is usually not the people — it is the structure. A direct conversation about what that looks like for your specific setup is the fastest way to figure out what is actually missing.
Not sure where the gaps in your IT setup actually are?
A brief consultation about your specific arrangement — internal IT, MSP, or both — is the fastest way to get a clear picture of what is and is not working. Or start with the free IT assessment to see where your technology risk sits today.