The IT manager at a 90-person Houston manufacturer laid it out plainly. He had one sharp systems guy and one overwhelmed helpdesk tech. The two of them kept the plant running, but the manager hadn’t taken a real vacation in two years, the after-hours phone always seemed to ring at 11 p.m., and a new customer’s security questionnaire had sat on his desk for three weeks because nobody had time to answer it honestly.
His first question wasn’t “how much.” It was, “If we bring you in, what exactly do you do and what do we keep?” That’s the right question, and the honest answer is: it depends on which version of co-managed IT fits your team. This post walks through the three flavors — Full, Desktop, and Server CoMITs — and how to figure out which split fits the team you already have.
First, a quick refresher on the model
Co-managed IT is a partnership, not a takeover. If you’ve been following this series you’ve heard us say it, but it shapes everything below: co-managed IT means your internal IT person or team keeps their job, keeps control, and stays the face of support — while an outside MSP supplies enterprise-grade tooling, deeper bench strength, and labor where it’s needed. It is not outsourcing, not a headcount-cutting maneuver, and not us replacing your people. (For the full breakdown, start with the pillar piece, What Is Co-Managed IT?)
The framework comes from Bob Coppedge and his team at Simplex-IT, who built much of the industry playbook for this model. Their core idea: co-management shares “software, tools, methodologies and portals” so a small internal team suddenly gets enterprise tooling it could never justify buying alone. Coppedge’s phrasing has stuck with us — we don’t want to replace internal IT, we lift it up. He also notes that roughly 70% of MSPs already have a co-managed client without realizing it, which tells you how naturally this forms once a capable internal person is in the picture. Simplex-IT named three flavors, and the names describe exactly who owns what.
Full CoMITs: internal IT runs everything, we backstop it
In a Full CoMITs arrangement, your internal team keeps all day-to-day operations. Helpdesk, servers, devices, projects — they own the lot. What changes is what stands behind them. The MSP supplies:
- The enterprise toolset — RMM, security stack, documentation, ticketing, monitoring — that a small team can’t cost-justify on its own.
- Advisory and escalation — a senior bench to call when something gnarly lands.
- Overflow, vacation, and after-hours labor — coverage so one person leaving for a week doesn’t mean the company goes dark.
Who it’s best for
Full CoMITs fits a team that is genuinely capable but stretched on hours. They know their environment cold. They don’t need someone to take work off their plate so much as they need better tools, a senior phone-a-friend, and a way to keep the lights on when they’re out. Our Houston manufacturer above is a textbook case: competent people, real expertise, but no slack in the week and no safety net for nights and vacations.
Desktop CoMITs: you keep the users, we take the back end
In Desktop CoMITs, your internal IT keeps end users and devices — the helpdesk relationship they’re already good at — and the MSP takes the servers, infrastructure, and back-end. Your people stay the friendly face who walks Karen in accounting through her printer problem. We handle the parts of the stack that hum quietly until they don’t: servers, virtualization, networking, backups, the infrastructure layer that demands depth most small teams don’t have.
Who it’s best for
This flavor fits a team that is great with people but thin on infrastructure depth. Plenty of internal IT folks are excellent at end-user support — patient, responsive, trusted across the office — but were never server engineers and don’t want to be paged at 2 a.m. about a failed RAID array. Picture a Houston professional-services firm — a 60-person accounting practice — whose one IT person is beloved at the helpdesk but is frankly guessing when it comes to the server room and the firewall. Desktop CoMITs lets that person keep doing what they’re great at while we own the infrastructure they shouldn’t have to lose sleep over.
Server CoMITs: you keep the systems, we drain the ticket queue
Server CoMITs is the mirror image. Your internal team keeps servers and infrastructure — often exactly where their expertise lives — and the MSP takes the helpdesk, endpoints, and after-hours user support. Your systems engineer gets to be a systems engineer instead of getting yanked off a migration every twenty minutes to reset a password.
Who it’s best for
This one fits a team that is strong on systems but drowning in tickets — the talented infrastructure person whose real value (architecture, projects, keeping the core healthy) is being eaten alive by day-to-day user requests. Healthcare is a common home for it. A Houston specialty clinic might have a sharp systems administrator who knows the EHR servers and the network cold, but who can’t make progress because forty clinical staff generate a steady drip of “my login won’t work” and “the scanner’s offline.” Server CoMITs hands that ticket queue — including evenings and weekends — to us, and gives that admin their week back.
How to choose your flavor
You don’t need to overthink this. Three honest questions get you most of the way there:
- Where is your team genuinely strong? Whatever they’re good at and enjoy, they should keep. Lean into the strength, don’t outsource it.
- Where are they buried or out of their depth? That’s the part the MSP takes.
- What’s eating their week? If it’s tickets, look at Server CoMITs. If it’s the infrastructure they were never trained for, look at Desktop CoMITs. If it’s simply not enough hours in the day, look at Full CoMITs.
Whatever you land on, the split gets written down. Every co-managed engagement is documented in a responsibility matrix — a plain table that names, line by line, who owns what: who patches the servers, who answers the after-hours phone, who onboards a new hire, who owns the firewall. No gray zones, no “I thought you had it.” And because it’s written down, it can evolve — teams routinely start as Server CoMITs to stop the ticket bleeding, then shift work back and forth as the internal person grows. The matrix is a living document, not a life sentence.
The most important thing to hear: there is no wrong starting point. Pick the flavor that relieves the most pain today; you can adjust the boundary at any month-to-month review.
The honest caveat: who this is NOT for
If you have no internal IT at all, co-managed isn’t your fit — fully managed is. Every flavor above assumes there’s an internal person or team to partner with. Co-management lifts up existing IT; it doesn’t conjure it from nothing. If there’s no one in-house to own a side of the matrix, you need a provider who runs the whole thing — that’s fully managed IT — and we’ll tell you that plainly rather than sell you a co-managed plan with no one to co-manage with. The flip side is just as honest: if you do have capable internal IT, you probably shouldn’t hand the whole thing to an MSP and sideline a good employee. That’s where co-management earns its keep.
Why the tooling math matters here
Part of what makes every flavor work is access to talent and tools that are brutally expensive to build in-house. Consider security alone. The U.S. Bureau of Labor Statistics puts the median pay for information security analysts at about $124,910 per year, and those roles often take 6+ months to fill — if you can find someone at all. A small business can’t justify that hire, and shouldn’t have to. Co-management gives your internal person that bench and enterprise tooling on a shared basis — the whole point of sharing “software, tools, methodologies and portals.”
Frequently asked questions
Can we change flavors later?
Yes, and many clients do. The responsibility matrix is reviewed regularly and adjusted as your team grows or a key person leaves — you might start as Server CoMITs to stop the ticket bleeding and migrate toward Full CoMITs as your internal person levels up. Because engagements are month-to-month with no long-term lock-in, changing the split never means renegotiating a contract.
Will our internal IT person feel replaced?
They shouldn’t, and a well-run engagement makes sure of it. In every flavor, internal IT keeps control and usually stays the face of support to your staff. We’re the bench behind them, not the people standing in front of them. The model exists to lift your team up, not to manage them out.
How do we know which flavor is right before committing?
You don’t have to guess alone. We’ll sit down with you and your IT lead, map where the team is strong and where it’s buried, and recommend a starting split — then put it in writing. For a ballpark on cost, our pricing calculator gets you a number before any call.
The bottom line
Full, Desktop, and Server CoMITs aren’t three products — they’re three places to draw one line, based on where your team is strong and where they’re drowning. Keep what your people are good at, hand off what’s burying them, write the split down in a responsibility matrix with shared visibility into the same tools, and adjust the boundary as you go. There’s no wrong starting point, and no long-term lock-in if you guess wrong.
If you have a capable internal IT person who’s stretched too thin, co-managed IT is very likely the answer — the only real question is which flavor. Book a free discovery call, and bring your IT lead with you; this works best when the person who’ll live the matrix is in the room. We’ll help you find the right split, or tell you honestly if co-management isn’t your fit at all.
Aspendora Technologies provides co-managed IT and managed IT services to Houston-area businesses, since 2010.