Co-managed IT means your internal tech and an outside crew share the work on purpose. It's the normal shape for businesses big enough to have an IT person but not big enough to have an IT department. Done right, your person stops drowning and the outside crew stays out of their way. Done wrong, it's a turf war with a monthly invoice.
Why this arrangement exists
One internal IT person is a bottleneck by definition. They can't be strong in everything, they can't be awake at 3 a.m., and they can't take a vacation without the office holding its breath. But they know the business, the people, and the weird payroll system in a way no outsider ever will. Co-managed keeps that knowledge and rents everything else: after-hours monitoring, enterprise tooling at pooled prices, specialists for the projects one generalist shouldn't solo.
The split that works
Most co-managed setups land near this division:
- Internal IT owns: day-to-day help desk, new-hire setups, vendor relationships, anything requiring a walk to someone's desk, and the institutional knowledge.
- The outside crew owns: monitoring and alerting, patch management, backup verification, security stack, after-hours response, and escalations past the internal person's comfort zone.
- Shared, with a named owner: projects. A server migration might be the crew's project with your person as the inside hands, or your person's project with the crew on call. Either works. Unnamed ownership doesn't.
The three failure modes
- Fuzzy boundaries. Both sides assume the other patched the server. Nobody did. The fix is a written responsibility list, reviewed quarterly. Boring, effective.
- The provider treats your tech as a threat. Some MSPs quietly position to replace internal staff. Ask directly how they work alongside internal IT and listen for respect or salesmanship.
- Your tech treats the provider as a threat. Understandable, and mostly solved by being plain that the crew exists so they can take vacations and stop working weekends, not to replace them. Involve them in choosing the provider. If they screen the candidates, they'll make the winner succeed.
What it costs
Less than full management, since your person absorbs the front-line volume. Providers usually price it per-device or as a reduced per-user rate, commonly 30 to 50 percent under full coverage for the same head count. Pricing mechanics are in what managed IT costs.
How to know it's working
Six months in, ask three questions. Has your IT person taken a real vacation? Are patches and backup checks happening on a schedule someone can show you? Does anything live in exactly one person's head? The last one has a cheap fix and it's called documentation. If the answers are yes, yes, and no, the arrangement is doing its job.
Want this handled instead of homeworked? That's the job.
Email us →