Most small businesses don’t struggle with whether they need IT support. They struggle with how much of it they want to own themselves. Do you hand the whole thing to an external team and get out of the way? Or do you keep an internal person (or two) and bring in a provider to fill the gaps?
That’s the fully managed vs co-managed decision, and it’s one of the most consequential IT choices an SMB will make. The right answer depends less on your size and more on what you already have in-house, how much control you want, and what kinds of problems you want solved. This guide breaks down both models, what each actually costs in time and money, and how to tell which one fits.
What Is Fully Managed IT Support?
Fully managed IT support means a third-party provider handles everything in your IT environment. Helpdesk tickets, user onboarding, endpoint management, email, basic networking, security hygiene, software updates — all of it. You don’t have an internal IT person, or if you do, they’re focused on something else entirely (like a technical product role, not operations).
With a fully managed model, your provider is the IT department. They own the runbook. They’re accountable when something goes wrong, and they’re the first call when anything breaks. You get predictable monthly pricing in exchange for handing over day-to-day operational responsibility.
This is the model most SMBs default to, and for good reason: it’s simple, it’s clean, and it removes IT as a thing you have to think about. For a broader look at how this fits into the spectrum of modern support options, our remote IT support services guide covers the full landscape.
What Is Co-Managed IT Support?
Co-managed IT support is a partnership model. You have someone (or a small team) on the inside handling IT, and you bring in an external provider to share the load. The split varies — that’s actually the whole point — but the typical arrangement looks something like this:
- Your internal person handles day-to-day user interactions, tribal knowledge, and anything that benefits from being physically present
- The external provider handles overflow tickets, after-hours coverage, specialized work your internal staff doesn’t have time for, and the deeper layers of stack management
The word “co-managed” is doing a lot of work here. In practice, it’s less a single model and more a spectrum. Some co-managed relationships lean heavy on the provider, with the internal person acting as a liaison. Others lean the opposite direction, with the provider only showing up for overflow or specific projects. The arrangement is negotiated based on what the business actually needs, not a fixed template.
Co-managed works well when you already have good internal IT but need more hours in the day, broader expertise, or a safety net for when your person is unavailable.
Scope: What Each Model Actually Covers
The clearest way to understand the difference is to look at who owns what.
Fully managed IT support:
– Ticket intake and triage — provider
– User onboarding and offboarding — provider
– Endpoint setup and management — provider
– Email and M365 administration — provider
– Password resets and account management — provider
– Basic networking and connectivity support — provider
– Vendor coordination for hardware and software — provider
– Documentation and asset tracking — provider
Co-managed IT support (typical split):
– Ticket intake and triage — shared
– User onboarding and offboarding — internal
– Endpoint setup and management — shared
– Email and M365 administration — provider (deeper tasks)
– Password resets and account management — internal
– Basic networking and connectivity support — shared
– Vendor coordination for hardware and software — internal
– Documentation and asset tracking — shared
– After-hours and overflow support — provider
– Specialized projects and escalations — provider
The co-managed split isn’t fixed. It’s a negotiation, and a good provider will sit down with you and draw the line based on what your internal person is actually good at (and interested in doing) versus where you need help.
Cost: How the Math Compares
Fully managed pricing is usually straightforward: a flat monthly fee per user or per device, sometimes tiered by service level. For a typical SMB, fully managed support runs somewhere in the range of $100–$250 per user per month, depending on scope and coverage. The appeal is predictability — you know exactly what you’re spending and what you’re getting.
Co-managed pricing is lower on the per-user basis because you’re sharing the work. You might pay $40–$120 per user per month on top of whatever your internal person costs you in salary. On paper, co-managed can look cheaper — but only if you’re not also paying a full internal salary. Once you add up both sides, the total is usually higher than fully managed, because you’re paying for both the internal headcount and the external support.
So the cost comparison really depends on where you start:
- No internal IT person today: fully managed is almost always cheaper and easier than hiring someone plus contracting a provider
- You already have an internal IT person: co-managed extends their capacity without doubling your spend
- You’re considering hiring your first IT person: look hard at fully managed first; you may not need the internal role at all
CompTIA’s research on managed services has consistently shown that SMBs tend to underestimate the total cost of an internal IT hire once benefits, tools, training, and turnover are factored in. That hidden cost is the main reason so many small businesses end up at fully managed even when they initially planned to hire in-house.
Ownership and Control: The Less Obvious Trade-Off
Cost is the easy part of the comparison. The harder part is control.
With fully managed IT support, you’re trusting a provider to make day-to-day decisions. They pick the ticketing system, they set the processes, they decide how to handle edge cases within the bounds of your SLA. You get to review the results, but you’re not in the driver’s seat on operations. For most SMBs, that’s exactly what they want — fewer decisions to make, fewer things to think about, more time back.
With co-managed, you keep the steering wheel. Your internal person knows your business, sits in your office (or on your Slack), and can make judgment calls in the moment. The provider supports them but doesn’t override them. This matters more than people realize when you have unusual workflows, industry-specific software, or a culture that depends on IT being in lockstep with how the business actually runs.
The trade-off is accountability. When something breaks in a fully managed environment, there’s one throat to choke. In a co-managed environment, the line between “our job” and “their job” can get blurry under pressure. Clear scope definitions up front solve most of this, but not all of it.
Which Model Fits Which Type of Business
Fully managed IT support is the right fit when: – You have no internal IT staff (or your “IT person” is really a bookkeeper who got volunteered) – Your needs are mostly standard: user support, email, endpoints, basic networking – You want predictable costs and minimal management overhead – You’d rather focus on your actual business than on IT operations – You’re growing and don’t want IT to be the thing that slows you down
Co-managed IT support is the right fit when: – You already have a competent internal IT person or small team – You need specific expertise your internal person doesn’t have (security, cloud, specialized platforms) – You need extended coverage — after hours, weekends, vacation backup – Your business has unusual or highly custom IT requirements – You’re not ready to let go of operational control, for reasons that make sense for your business
If you find yourself torn between the two, the deciding factor is usually this: do you have an internal IT person you trust and want to keep? If yes, co-managed. If no, don’t hire one just to make co-managed possible — go fully managed instead.
How to Make the Decision
A useful exercise: list every IT task that happened in your business over the last month. Password resets, a new hire setup, an email outage, a software update, a printer that stopped working. For each one, ask: who did it, how long did it take, and would it have been better, faster, or cheaper if someone else had handled it?
Patterns emerge fast. If most of the list is routine and nobody internal is enjoying handling it, that’s a fully managed signal. If most of the list is routine and your internal person handles it well and you just wish they had backup and specialized help, that’s a co-managed signal.
Also talk to providers about both options. A good provider will tell you honestly which model fits — and if they try to push you into the more expensive option without a real reason, that’s useful information too.
For SMBs leaning toward the all-in-one approach, our overview of fully managed IT solutions for growing companies digs deeper into what a fully managed engagement actually looks like in practice.
Getting Started
Whichever model you choose, the transition is usually smoother than expected. A fully managed onboarding takes a few weeks: inventory, documentation, access setup, handover. Co-managed is typically faster since your internal person already knows the environment — the provider just needs to get up to speed on what they’re taking over.
The honest answer for most small businesses is that fully managed works — it’s simpler, cheaper when you don’t already have internal IT, and removes a category of work you probably don’t want to be doing anyway. Co-managed is the right call when you’ve already built something internally worth keeping, and you just need it to scale.
Either way, the worst option is the one too many SMBs are stuck with: doing IT informally, reactively, and whenever someone has a spare minute. A clear model — fully managed or co-managed — beats no model every time.
Microwize provides remote IT support for small and mid-sized businesses in New Jersey and across the U.S. If you’d like help figuring out which model fits, get in touch.
