Chicago IT guide
Co-Managed IT vs Managed IT
If you are comparing IT support options, you have probably seen both terms and wondered whether the difference actually matters. It does. The two models solve different problems, and choosing the wrong one usually shows up later as either wasted spend or gaps nobody owns.
With fully managed IT, an outside provider runs your technology and acts as your IT department. With co-managed IT, you keep your internal IT staff, and a provider works alongside them in agreed areas such as help desk overflow, after-hours coverage, security or projects. The deciding factor is whether you have internal IT people today.
Co-Managed IT vs Managed IT at a Glance
| Fully managed IT | Co-managed IT | |
| Internal IT staff | None, or not in a technical role | One or more internal IT people |
| Who does the daily work | The provider | Shared, based on an agreed split |
| Who owns IT decisions | You and the provider, with the provider leading on technical direction | Your internal IT lead, with the provider advising and supporting |
| Best fit | Businesses without in-house IT | Businesses whose IT team needs more time, coverage or skills |
| What the agreement defines | The full scope of your IT operation | Exactly which areas each side owns |
| Main risk | Choosing a provider that doesn’t learn your business | Unclear lines of responsibility |
A note on terms: some providers use “managed IT” as an umbrella that covers both models. In this article, “managed IT” means fully managed IT, which Datastrive also calls outsourced IT. Co-managed IT is the shared version.
What Is Managed IT?
Fully managed IT means an outside team takes responsibility for your technology from end to end. That usually includes help desk support for employees, maintenance of your network, servers and devices, security, backup, vendor coordination and technology planning.
You still make the business decisions. You set priorities, approve budgets and decide what matters most. The provider does the work and brings the technical judgment behind each recommendation.
Fully managed IT fits businesses that depend on technology every day but don’t have a dedicated IT person. It also fits businesses where IT has landed informally on an office manager or a tech-savvy employee who has a different job to do.
What Is Co-Managed IT?
Co-managed IT means your internal IT staff stay in place, and an outside provider adds capacity or expertise where your team needs it. Your IT lead keeps ownership of the environment, and the provider works as an extension of that team.
Common co-managed arrangements include:
- Help desk overflow. The provider handles routine employee requests so your IT staff can focus on projects and bigger problems.
- After-hours coverage. Someone is available outside your team’s working hours for agreed types of issues.
- Security depth. Specialist support for security tools, monitoring and hardening that a generalist IT team may not have time to manage.
- Infrastructure and engineering. Senior help with networks, servers or cloud platforms.
- Project capacity. Extra hands for migrations, office moves or major upgrades.
- Planning support. A second opinion on roadmaps, budgets and technology decisions.
Every co-managed arrangement is different, because every internal IT team has different strengths. The right split depends on what your people already do well and where they are stretched.
The Real Difference: Who Owns What
Most articles on this topic stop at definitions. The more useful question is who is responsible for each part of your IT. Here is how responsibility typically splits in each model. In a co-managed arrangement, the exact split is agreed with each business.
| Area | Fully managed IT | Co-managed IT (a typical split) |
| Employee support requests | Provider | Shared: often internal first, provider for overflow |
| After-hours issues | Provider, within the agreed scope | Provider, within the agreed scope |
| Patching and device maintenance | Provider | Often provider, reported to internal IT |
| Networks and servers | Provider | Shared, depending on internal skills |
| Security baseline | Provider | Shared, with each control assigned to one side |
| Backup and recovery testing | Provider | Agreed owner, with results visible to both sides |
| Vendors and licensing | Provider | Usually internal IT, with provider support |
| Technology planning and budget | Provider advises, you decide | Internal IT leads, provider advises |
| Projects | Provider | Shared, or provider for specialist projects |
| Admin access and documentation | Provider maintains it, you keep copies | Both sides, with one shared record |
The rows marked “shared” are where co-managed IT succeeds or fails. Shared work is fine. Shared work that nobody wrote down is where problems start.
How to Decide: Five Questions to Ask
1. Do you have internal IT staff today?
This question settles most decisions on its own. If nobody on your team has IT as their actual job, you need fully managed IT. If you have an IT person or team, co-managed is usually the starting point.
2. What does your IT person actually spend their time on?
Ask them, or look at their week. If most of their time goes to password resets and printer problems, they aren’t doing the planning and project work you hired them for. Moving routine support to a co-managed provider often gives that time back.
3. Is the gap time, skills or coverage?
These are different problems. A time gap needs more hands. A skills gap needs specialists, often in security or infrastructure. A coverage gap needs someone available when your IT person is out. Knowing which one you have tells you what the co-managed scope should include.
4. What happens when your IT person is unavailable?
Vacations, sick days and resignations happen. If the honest answer is “nothing gets done until they’re back,” you have a single point of failure. Both models address this, but in different ways. Co-managed IT adds backup behind your person. Fully managed IT spreads the work across a team.
5. Who should own IT decisions?
Some businesses want an internal person who owns technology direction and knows the business from the inside. Others would rather hand technical direction to a partner and focus on running the company. Neither preference is wrong. It simply points you toward one model or the other.
When Fully Managed IT Makes Sense
Fully managed IT is usually the better fit when:
- You have no internal IT staff, and technology questions land on whoever is most willing to help.
- Your only IT person is leaving and you would rather not rebuild the role.
- You want one accountable team for support, security, backup and planning.
- Your business depends on technology but running it isn’t where you want management attention going.
When Co-Managed IT Makes Sense
Co-managed IT is usually the better fit when:
- You have an internal IT person or team with real knowledge of your business and systems.
- Your IT staff are overloaded with support requests and can’t get to projects.
- You need specialist skills, such as security or network engineering, that don’t justify a full-time hire.
- You need coverage outside your team’s working hours.
- You want your internal IT lead to stay in charge of technology direction.
What Makes Co-Managed IT Work, and What Makes It Fail
Co-managed IT has more moving parts than fully managed IT, because two teams share one environment. The arrangements that work tend to have five things in common.
Written responsibilities. Every area in the table above has a named owner. When something goes wrong, nobody has to ask whose job it was.
One set of records. Both teams work from the same documentation, the same asset list and ideally the same ticketing system. Two versions of the truth cause most co-managed friction.
Agreed admin access. Both sides know who holds which admin accounts, and changes are logged. This matters for security as much as for coordination.
A clear escalation path. Your employees know where to send requests. Both teams know when an issue moves from one side to the other.
Regular check-ins. A short, scheduled review keeps the split current as your business and your team change.
Co-managed IT tends to fail when the provider is treated as a ticket queue, or when the internal team feels like it is being replaced. Neither side can succeed without the other. A good co-managed partner makes your internal IT person stronger, not redundant.
Security Works the Same Way in Both Models
The security baseline your business needs doesn’t change based on who does the work. What changes is how responsibility is assigned.
Datastrive builds every agreement around the CIS Controls v8.1 framework, published by the Center for Internet Security. Implementation Group 1, the framework’s baseline for essential cyber hygiene, is the minimum for every business we work with. That covers keeping track of devices and software, controlling access, configuring systems securely and making sure data can be recovered.
In fully managed IT, the provider owns that baseline. In co-managed IT, each control should be assigned to one side, with results visible to both. A shared control that nobody owns is a common gap. No framework makes a business impossible to breach, but a clear standard with clear owners gives your security a consistent foundation.
How the Costs Compare
You may read that one model is always cheaper. That isn’t a safe generalization. The honest comparison looks at your total cost of IT, not just the provider’s invoice.
With fully managed IT, the provider’s agreement covers most of your IT work, so the agreement is broader. You are not also paying an internal IT salary.
With co-managed IT, the provider’s scope is narrower, but you are still paying for your internal staff. The value comes from making that investment go further, by giving your team time, skills and coverage they wouldn’t otherwise have.
The right question isn’t “which one costs less?” It is “which one covers what we actually need without paying twice for the same work?” Our managed IT services pricing guide explains how agreements are usually structured and what affects the cost.
Can You Move From One Model to the Other?
Yes, and many businesses do as they change. A company that grows and hires its first IT person may move from fully managed to co-managed. A company whose IT person leaves may move from co-managed to fully managed, rather than rushing a replacement hire.
If you are changing providers at the same time, the planning matters even more. Our guide on how to switch IT providers walks through contracts, access and handover step by step.
How Datastrive Approaches Both Models
We work with Chicago-area businesses in both models. Businesses with roughly 20 to 200 employees and no internal IT staff usually come to us for fully managed IT. Larger organizations, up to around 500 employees, often have internal IT teams that need co-managed support, such as help desk overflow, after-hours support, security or engineering depth.
Either way, the starting point is the same. We learn how your business runs, look at your current setup, and give you a written plan in plain numbers. That plan shows what we recommend, what we don’t think you need, and what it costs. If your internal team already has an area well covered, we won’t include it just to make the agreement bigger. We treat your money like it’s ours.
We are also clear about what the partnership needs from you: treating our team as an extension of yours, being open about what isn’t working, and asking us for lots of help. You can read more about how we work on our Why Datastrive page or learn about our managed IT services in Chicago.
Frequently Asked Questions
Is co-managed IT cheaper than managed IT?
Not automatically. A co-managed agreement usually has a narrower scope, but you are also paying for internal IT staff. Compare the total cost of your IT, including salaries, against what each model covers.
Is co-managed IT the same as IT staff augmentation?
They overlap but aren’t the same. Staff augmentation usually means adding individual people to your team. Co-managed IT is an ongoing service agreement where a provider takes defined responsibilities, bringing its own team, processes and tools.
Can a small business use co-managed IT?
Yes, if it has internal IT staff. A 40-person company with one IT person is a common co-managed fit, because a single person can’t cover every skill and every hour.
Who holds admin access in a co-managed IT arrangement?
Both sides typically need some level of admin access. Agree in writing who holds which accounts, log changes, and make sure your business can always access its own systems.
What happens if our internal IT person leaves?
A co-managed provider already knows your environment, which makes the gap far less disruptive. You can then decide whether to hire a replacement or move to fully managed IT.
Does co-managed IT include after-hours support?
It can. After-hours coverage is one of the most common reasons businesses choose co-managed IT. What it covers should be defined in the agreement, so everyone knows which issues are handled and how.
How do existing Datastrive partners request support?
Through the client portal at portal.datastrive.com, by email at [email protected], or by phone at (773) 863-3868. In co-managed arrangements, these shared channels keep every request tracked and visible to both teams.
Choose the Model That Fits the Team You Have
The choice between co-managed IT and managed IT comes down to one question: what does your IT team look like today, and where does it need help? If you’d like an honest outside view, we’re happy to look at your setup and tell you which model fits. That includes telling you when your current arrangement is already working.