Key Takeaways
- Co managed IT lets your internal IT team share responsibilities with a managed service provider (MSP). You decide which work stays in-house and where outside support makes sense.
- Start with a recurring problem you can name, such as a project that keeps getting delayed or a critical system only one person knows how to support.
- Before you choose a provider, agree on who owns each IT task, who can approve changes, and who updates your staff when something goes wrong.
- Measure success against the problem you set out to solve. That might mean fewer after-hours calls to your IT director or more time to finish a long-planned upgrade.
Your IT director has blocked out Friday morning to plan an office move. By 10 a.m., a new employee needs access to three applications, the warehouse printer has stopped printing shipping labels, and a vendor is waiting for help with a connection. Each request deserves attention. The office move gets pushed to next week.
When that pattern becomes familiar, co managed IT can help. Your internal staff and an outside IT provider divide the work, giving your business additional support while keeping the people who know your operations involved in the decisions that matter.
For a small or midsize business, the first question is simple. Which work could someone else reliably handle, and what would that free your team to accomplish?
How does co managed IT work?
Co managed IT is an arrangement in which your business keeps its internal IT staff and partners with an MSP for an agreed set of responsibilities. One company might need a help desk for everyday requests. Another might already have excellent support technicians and need an experienced network engineer to open a second location.
Take the warehouse printer. An outside technician can troubleshoot it, but your internal team knows that a printer outage at 3 p.m. could mean missing the last carrier pickup. A good handoff captures that detail in the support instructions. The next time the printer goes down, the technician knows how quickly to respond, which workaround staff can use, and whom to call if shipments are at risk.
Here’s how a business might divide the work.
| Area | Your internal team | Your IT provider |
|---|---|---|
| Employee support | Identifies business-critical issues and handles questions about specialized applications | Handles everyday requests and escalates issues that need local knowledge |
| New employee setup | Confirms the role, start date, and approved access | Prepares the device and sets up approved accounts using a shared checklist |
| Backup and recovery | Decides which systems need to come back first and verifies that staff can use them | Monitors backup jobs, investigates failures, and tests whether critical data can be restored |
| IT projects | Sets the budget, business requirements, and acceptable downtime | Supplies specialist skills or covers support while internal staff lead the project |
When does co managed IT make sense?
Projects keep losing their place on the calendar. Look back at the last two projects that slipped. Was the person leading them also answering every urgent ticket? Repeated delays are one of the signs your in-house IT team needs a co-managed partner. Handing off part of the support queue could give that person dependable time to finish the work.
One employee is always on call, even on vacation. What would happen if your IT lead took a full week off? Could someone else contact your vendors, find the recovery instructions, and get approval for an urgent change? If several answers depend on calling the person on vacation, you have a clear starting point for backup coverage.
You need a specific skill for a project. Opening a branch office may call for network design experience that your business rarely needs afterward. Your internal lead can own the rollout and coordinate with department heads while a provider designs and documents the network. If you’ll need that expertise every day across several locations, a permanent hire may make more sense.
What should you agree on before signing?
Ask a prospective provider to walk through one ordinary ticket and one urgent incident with your IT lead. Try this question: “If our order system goes down at 4:45 on a Friday, who takes the first call, and when does our operations manager get an update?”
Use the answers to settle four things in writing.
- Ownership. Where do employees report an issue? Who stays responsible for the ticket if it moves between the provider, your IT team, and a software vendor?
- Coverage. What hours are included? How soon should someone respond, and what triggers an after-hours escalation?
- Authority. Which changes can the provider make independently? If the outage turns out to be a security incident, your incident recovery plan should identify who can authorize downtime and who takes over if that person is unavailable.
- Records and access. Where will both teams find current instructions and ticket history? How will your business retain access to its accounts, configurations, and documentation if the agreement ends?
When you bring a managed service provider into your existing IT team, involve the people who answer support calls today. They can tell you which requests are easy to hand over and which depend on a vendor relationship, a shipping deadline, or a system quirk nobody has written down.
How do you know if co managed IT is working?
Choose a measure that reflects why you brought in help. If your goal is to protect project time, record how many planned project hours your IT lead actually gets over a typical month. After the provider takes on routine support, compare that figure and check whether the project reached its next milestone. For the office move, that might mean getting the network design approved in time to order equipment.
Also ask employees about the handoff. If they still call your IT director after opening a ticket because they don’t know who will respond, the ticket count may look better while the interruptions continue. A confirmation that names the technician and tells the employee when to expect an update gives them a reason to trust the new process.
Give your IT team time for the work only they can do
Ask your IT lead, “If you had one uninterrupted morning every week, what would you finally get done?” Their answer gives you a concrete way to judge whether co managed IT would be worth the investment. If Friday mornings are supposed to be for planning the office move, success means your IT director can count on that time, and the warehouse can still get its shipping labels printed.
If your business is weighing an additional hire or outside support, bring that answer to a conversation with Tom McDonald at NSI. Talk through what keeps interrupting your team, what should stay in-house, and what a partner could own. Schedule a conversation with Tom.
FAQs
What’s the difference between co managed IT and fully managed IT?
With co managed IT, your internal staff and a provider each own defined parts of the IT workload. With fully managed IT, the provider generally handles most day-to-day IT operations. Your business still sets priorities and approves spending.
Can co managed IT work with a one-person IT department?
Yes. A single IT manager might keep responsibility for business applications, budgets, and vendor relationships while a provider handles routine tickets or vacation coverage. Both sides need current documentation and enough access to handle their assigned work independently.
How much does co managed IT cost?
Pricing depends on the work you assign, the users and locations covered, the support hours, and any project fees. Give each provider the same scenario and ask what the monthly fee covers, what costs extra, and who approves additional charges. If you’re comparing provider pricing with the cost of hiring in-house, use the same coverage hours, responsibilities, and skill requirements for both estimates.