If you’re the IT manager — or the IT department — at a growing company, you know the math problem: the ticket queue never empties, the project list never shrinks, security expects 24/7 attention, and there’s exactly one of you. Co-managed IT exists for precisely this situation. Done right, it’s not a threat to your role; it’s the staff you were never going to get headcount for. Done wrong, it’s a turf war with a monthly fee. Here’s how to make it the first one.

What co-managed actually means

You keep ownership of your environment and strategy. An outside provider plugs in underneath and alongside you — typically taking the always-on, tooling-heavy work: monitoring and alerting, patch cycles, backup verification, security operations, and overflow or after-hours help desk. You stop being the only person who can be paged, and you get enterprise tooling (RMM, EDR/MDR, documentation platforms) without buying and running it yourself. (The general model, explained.)

The honest pitch from our side of the table: nobody knows your environment like you do, and no internal hire can be awake at 3 a.m. every night. The arrangement works because those are different jobs.

What to offload first (and what to keep)

Offload the undifferentiated grind — the work that has to happen, benefits from scale, and teaches you nothing about your business:

  • 24/7 monitoring and alert triage, so you’re woken for real incidents, not noise (why around-the-clock matters)
  • Patch management with testing and reporting (the discipline itself)
  • Backup jobs, verification, and restore testing
  • Security operations — someone watching the EDR console when you’re on vacation
  • Tier-1 password-reset-and-printer tickets, if volume is eating your projects

Keep what makes you valuable:

  • Architecture and strategy — where the environment is going
  • The line-of-business applications only you understand
  • Vendor and budget decisions
  • The relationships — being the face of IT to your leadership and users

The test for any task: does doing this personally require my knowledge of this company? If not, it’s a candidate.

The turf question, handled like adults

Co-managed arrangements fail on ambiguity, not on ill will. Settle these in writing before the first ticket:

  1. Who owns which systems and which ticket types — a simple responsibility matrix beats a hundred Slack clarifications
  2. Admin access and change control — both sides log changes in one place; nobody’s surprised by a modified firewall rule
  3. Escalation paths in both directions — when their help desk hits something local, they come to you; when you’re buried, you hand off cleanly
  4. Documentation lives where you can see it — their notes on your environment belong to the company, not the provider. This is non-negotiable and any decent MSP agrees without flinching.
  5. Who talks to your leadership — usually you, with the provider supplying the reporting. A provider that tries to route around its internal IT counterpart is telling you something; believe them.

What to demand from the provider

You’re a more sophisticated buyer than most, so buy like one. Ask how their alert triage actually works at 2 a.m. — staffed by whom, where. Ask to see the reporting you’d receive, because you’ll be forwarding it upward. Ask how they handle providers-and-internal-IT relationships specifically: how many co-managed clients, and can you talk to one of their internal IT counterparts? Ask what happens at offboarding — documentation, credentials, tooling removal. And check the service-level commitments apply to you as a requester, not just to end users.

The good ones treat internal IT as the client, not the competition. The relationship should make you look better in front of your leadership — measurably: faster resolution times, patched percentages, tested restores, projects actually shipping.

The career reframe

The quiet worry with co-managed is “am I outsourcing myself out of a job?” In practice we’ve seen the opposite: the IT manager who offloads the 3 a.m. pages and the patch grind is the one who finally ships the ERP migration, builds the security roadmap, and shows up to leadership meetings with strategy instead of a backlog. The grind was never the valuable part of your job. It was just the loudest.

The bottom line

Co-managed IT works when the split is explicit: you keep the knowledge, judgment, and relationships; the provider brings scale, tooling, and hours you can’t staff. Put the responsibility matrix in writing, insist on shared documentation and honest reporting, and pick a provider that sees you as the client. You’ll keep control — and finally get some sleep.