Fully Managed vs Co-Managed: Which Fits a Business Your Size

Two ways to solve the same problem

We have spent this month on one situation: the person at your business who ended up handling technology without ever being asked to, and what happens when the company grows past what that arrangement can carry.

This last post is about the two ways out, because there are two, and a lot of businesses assume there is only one.

Fully managed, in plain terms

We handle technology. All of it, or close to it.

Monitoring, updates, backups, the help desk your staff call when something stops working, account setup and removal, hardware and software purchasing, vendor wrangling, and the planning conversation about what needs doing next year. Your team has a number to call and someone answers it. Our managed IT services page lays out the full scope.

This tends to fit organizations with nobody internal whose job includes technology, where the current arrangement is somebody’s unpaid second job, and where leadership would rather stop thinking about this category entirely. That describes most professional services firms and nonprofits we work with.

Co-managed, in plain terms

You keep somebody internal. We work alongside them.

The split varies and is agreed rather than assumed. A common arrangement has us carrying the continuous load, meaning monitoring, patching, backups, after-hours cover, and the routine ticket volume, while your person stays the internal face of technology, keeps the institutional knowledge, and handles what needs somebody who knows the business. When a project comes along that is bigger than one person, we bring the additional hands, and the longer-term planning side sits under our IT guidance service.

This tends to fit organizations that already have someone doing technology work in a real and acknowledged way, where the constraint is depth or hours rather than the absence of a person, and where the internal person genuinely wants to keep part of the job.

How to tell which one you are

The instinct is to decide by headcount, and headcount is the least reliable guide available. We have seen fifteen-person organizations that are clearly co-managed and sixty-person organizations that are clearly fully managed.

Three questions do a better job.

Does anyone’s actual job description include technology? Not “everybody knows Priya handles the computers.” Whether it is written down, resourced, and reviewed. If it is not, you are probably looking at fully managed, whatever the org chart implies.

What is the constraint you are trying to fix? If the problem is that nobody has the specialist knowledge, co-managed adds depth alongside someone who stays. If the problem is that the person carrying this is already underwater and needs the load gone rather than shared, co-managed can quietly make it worse by adding coordination to an already full plate. Reliable network management and steady cybersecurity coverage matter under either model, so this question is really about who owns them day to day.

What does the person themselves want? This gets asked least and matters most. Some people enjoy the technology part and would be genuinely sorry to lose it. Others have been waiting years for somebody to take it away and have never felt able to say so. It is worth asking them directly and privately, and it is worth believing the answer.

Nobody is being replaced

Worth stating plainly, since it is the fear that stalls this decision more than any other.

In our experience the internal person is rarely the obstacle once they understand what is actually on offer. What they are usually afraid of is that a provider will arrive, declare everything wrong, and make them look bad in front of leadership. That fear is reasonable and it happens. It is also not how a decent arrangement starts, and if you are evaluating providers it is a fair thing to ask them about directly.

The part that takes the pressure off

Here is what we most want you to take from this post: the choice is not permanent, and you should be deeply suspicious of any arrangement that requires it to be.

Businesses move between these models regularly and in both directions. An organization on fully managed hires an operations person who turns out to be capable and interested, and the arrangement shifts. A co-managed client loses their internal person and needs us to absorb the whole thing for a while. Growth changes the answer. So does a single hire.

That is why we do not do long-term contracts. Not as a promotion, but because tying a business into a multi-year commitment for a decision that should be revisited as circumstances change is not a good arrangement for the client, and an arrangement that only works while the client is locked in is not much of an arrangement.

It also matters for whoever holds your job next. If you are an operations lead or an executive director, some of what you sign becomes your successor’s inheritance. Being able to say you did not commit them to anything they cannot change is worth something, and it is the kind of detail a board notices.

Where the month lands

Four weeks of posts, and one argument underneath all of them. Growth is what broke your old way of handling technology. Nothing was neglected and nobody failed. The arrangement simply stopped fitting, quietly, somewhere along the way. We covered the true cost of that arrangement earlier this month, along with the IT mistakes that tend to come with it.

Fully managed and co-managed are both reasonable answers. The wrong answer is continuing by default because the decision never made it onto anyone’s agenda.

Talk it through, no obligation

CMIT Solutions of Austin East works with growing businesses across East Austin, Round Rock, Pflugerville, Manor, Elgin, Cedar Park, and Bastrop. Our free thirty-minute IT assessment includes a straight conversation about which model actually fits you, and we are perfectly willing to tell you that neither is worth doing yet. Our IT support team can also walk you through our IT packages beforehand if you want to see the options first.