Co-managed IT splits responsibility between your internal IT staff and an outside provider. Fully managed IT hands the whole function to the provider. For most Utah businesses the choice is not about company size or budget. It comes down to whether you have someone in-house whose time is better spent on your business than on patching servers at ten o’clock at night.
We see both arrangements across the Wasatch Front, and businesses usually land on one of them by accident. You hired an IT person because something broke one too many times. Six months later they are answering password resets all day and the project you actually hired them for has not moved. Or they took a week off in July and nobody noticed the backups had stopped running.
Both models fix that. They fix it differently, and picking the wrong one wastes either your money or your best technical employee.
Key Takeaways
- Co-managed IT keeps your internal staff and hands the provider what one person cannot cover alone: monitoring, patching, security, backup and connectivity.
- Fully managed IT hands over the entire function, including the helpdesk your employees call. No internal counterpart needed.
- Bigger companies use providers more, not less. Among Utah-sized businesses of 100 to 249 employees, 62% work with a managed provider, against 40% of firms under 20 people.
- Co-managed is not fully managed at a discount. You keep a coordination job, and someone on your side has to own the boundary.
- Neither model covers your internet circuit unless your provider owns it. 1Wire does, which is why Utah businesses working with us call one number instead of three.
- Both models are available from 1Wire’s managed IT solutions for businesses across Utah.
Co-managed IT and fully managed IT at a glance
| Co-managed IT | Fully managed IT | |
|---|---|---|
| Internal IT staff | Required. The model needs someone on your side. | Not required. The provider is the IT function. |
| Who your employees call | Usually your internal person first, escalating out. | The provider's helpdesk, every time. |
| After-hours coverage | Provider covers the hours your staff cannot. | Provider covers all of it. |
| Business-specific knowledge | Stays in-house, where it is strongest. | Transfers to the provider through documentation and onboarding. |
| Tool stack | Negotiated. Settle ownership before signing. | Provider's, included in the service. |
| Coordination workload | Stays with you. Someone owns the boundary. | Handed over with everything else. |
| Best fit | You have IT staff and want to redeploy them onto projects. | You have no IT staff, or IT is someone's second job. |
| Common failure | Nobody owns the gap between the two teams. | Business context never gets documented at handover. |
What is co-managed IT?
Co-managed IT is an arrangement where your internal staff and an outside provider divide the IT function between them, with each side owning a defined set of responsibilities.
Your person keeps the work that benefits from being in the building and knowing your business. That usually means desk-side support, onboarding new hires, the applications specific to your industry, and the relationships with your other vendors. The provider takes the work that needs a team, a tool stack, and coverage at hours when your employee is asleep. That usually means monitoring, patching, security, backup verification, and network and firewall management.
You probably want co-managed IT if you already have IT staff and they are spending their week on maintenance instead of the projects you hired them for.
We see this constantly in Utah offices between twenty and a hundred people. A manufacturer in Ogden, a clinic group in Murray, a professional services firm in Draper. There is one capable person holding the whole thing together, and the business has quietly outgrown what one person can cover. Co-managed IT keeps that person and gives them a bench.
Both models are covered under 1Wire’s managed IT solutions, which is where you can see everything included in each.
What is fully managed IT?
Fully managed IT is an arrangement where an outside provider owns the entire IT function, including the helpdesk your employees call, the systems behind it, and the planning that decides what gets replaced next year.
There is no internal counterpart. Your employees submit tickets to the provider. The provider monitors, patches, secures, backs up, documents, and advises. You get one bill and one number to call.
You probably want fully managed IT if you have no internal IT staff, or if the person currently handling IT is doing it on top of another job they were actually hired for.
That second case is more common than the first across Utah. In plenty of businesses here, IT belongs to whoever is best with computers. Usually that is the office manager or the controller, and it is costing you their real work.
The bigger the company, the more likely it uses a provider
Here is the finding that surprises most Utah owners. Managed provider use goes up with company size, not down.
The Global Technology Industry Association surveyed 720 North American small and mid-sized businesses in May 2025. Among firms with 2 to 19 employees, 40% used a managed services provider. Among firms with 20 to 99 employees, that rose to 57%. Among firms with 100 to 249 employees, it reached 62%.
Sit with that for a second. Companies in that top bracket almost all have internal IT staff. They have the budget and the headcount to run IT entirely in-house, and they are the group most likely to be working with an outside provider anyway.
That is co-managed IT, whether or not those companies call it that. Hiring internal staff does not remove the need for a provider. Past a certain size it tends to create one, because the internal team stops being able to cover everything and starts needing depth in specific places.
That top bracket describes a lot of Utah businesses. A 150-person operation in Lehi or Layton has an IT manager and probably a technician under them, and it is still more likely than not to have a provider alongside them.
The same research found 76% of small and mid-sized businesses lack the in-house skills to properly address security issues. A separate Forrester Consulting study of 421 SMB decision-makers, commissioned by Datto in 2023, found 52% named a lack of in-house staff expertise as a live challenge, and 74% said their organization did not have the capacity to train employees as their systems grew more complex.
None of that means your IT person is not good at their job. It means no single person covers networking, security, cloud administration, backup, compliance and the helpdesk at the same time, and the ones who claim they can are usually behind on something they have not told you about.
How the work actually splits
A co-managed arrangement works when the boundary is written down before anything goes wrong.
Your internal staff generally keeps anything that depends on knowing your business. They know which application the shipping department cannot function without, which employee needs a workaround for the scanner, and which vendor to call about the practice management software. That knowledge does not transfer well and it should not have to.
The provider takes anything that depends on a team and a tool stack. Round-the-clock monitoring is the clearest example. Your person in Provo cannot watch a network at three in the morning and then work a full day, and they should not be asked to. Patching, firewall management, backup testing and security response all fall in the same category.
Some things get shared, and those are where co-managed arrangements go wrong. Ticket escalation, project planning, vendor management and documentation all need a named owner on each side. When nobody owns the boundary, work falls through it, and both sides assume the other one handled it.
| Responsibility | Usually owned by | Why it lands there |
|---|---|---|
| Desk-side and walk-up support | Your staff | Faster in person, and it builds the relationships that make the rest work. |
| Industry-specific applications | Your staff | Nobody outside your building knows that software the way your person does. |
| Employee onboarding and offboarding | Your staff | Tied to HR timing and access decisions that belong in-house. |
| Round-the-clock monitoring | Provider | One person cannot watch a network at 3 a.m. and work the next day. |
| Patching and updates | Provider | Constant, scheduled, and the first thing to slip when your person gets busy. |
| Firewall and network security | Provider | Needs specialist depth and current threat intelligence. |
| Backup and tested restores | Provider | Backups fail silently. Verification needs to be someone's actual job. |
| Connectivity and failover | Provider | Neither your staff nor most providers own the circuit. 1Wire does. |
| Ticket escalation path | Shared, needs a named owner | The most common place work stalls, because both sides assume the other has it. |
| Project planning and budgets | Shared, needs a named owner | Your staff knows the business need, the provider knows the lead times. |
| Documentation | Shared, needs a named owner | Decide now whether it stays accessible to you if the relationship ends. |
| Vendor management | Shared, needs a named owner | Splitting it by vendor works. Leaving it unassigned does not. |
What co-managed IT costs you in oversight
We should be honest about this part, because most articles on this topic skip it.
Co-managed IT is not fully managed IT with a discount. You are keeping a coordination job that fully managed IT would have taken off your plate. Someone on your side has to own the relationship, route the work that arrives in the wrong place, and make the call when a problem sits in the gap between the two teams.
If your internal person is already stretched to breaking, adding relationship management to their week can make things worse before it makes them better. That is a real risk and worth naming before you sign anything.
Three questions worth answering up front. Who owns the monitoring and ticketing tools, you or the provider, and what happens to your data if the relationship ends? Who does an employee call first when something breaks? And when a problem crosses the boundary at four in the afternoon, who owns it until it is resolved?
Good answers to those three make co-managed IT work. Vague answers are how Utah businesses end up paying for a provider and still doing the work themselves.
When fully managed is the better answer
Co-managed IT needs a participant. If you do not have internal IT staff and are not planning to hire, it is a model with one side missing, and fully managed is the straightforward answer.
It is also the better answer when your internal person is a generalist who would rather be doing something else. Not everyone who ended up handling IT wants to keep handling IT. In a lot of Utah offices the honest conversation is that your operations manager is good with computers and would be far more valuable running operations.
And if you are choosing between hiring your first IT person and bringing in a provider at all, that is a different question with a different answer. We wrote about it separately in managed IT vs. in-house IT.
The part both models leave out
Here is something that catches Utah businesses in either arrangement.
Your internal team does not own your internet circuit. In most cases neither does your managed provider, because most providers resell someone else’s connection and hand you off when it goes down. So you draw a careful boundary between your staff and your provider, and then the circuit drops on a Tuesday morning and both sides are on hold with a third company.
That gap is worth closing when you are already redrawing responsibilities. We provide the connection and the support on the same contract, backed by a 99.9% uptime SLA, with backup internet connections that fail over automatically when the primary drops. One provider, one call, no finger-pointing about whose problem it is.
That combination is what 1Wire’s managed IT solutions are built around, and it is the part most Utah businesses do not think to ask about until the day it matters.
For a full picture of what falls under managed IT, see our guide to the different types of managed IT.
Co-managed and fully managed IT across Utah
We have been supporting Utah businesses since 2006, and we work in both models depending on what a business already has in place.
We support co-managed arrangements for companies with internal IT teams in Salt Lake City, Ogden, Provo, Orem, Layton, Murray and Draper, and fully managed IT for businesses across the Wasatch Front and down through St. George. Because we are based here and our technicians are here, we can put someone on site when a problem needs hands on it, which matters more in a co-managed arrangement than people expect. Your internal person should not be the only one who can physically reach the network closet.
You also get people who answer the phone in Utah, not a queue in another time zone. For an IT manager handing off after-hours coverage, that is the difference between a partner and a ticket system.
Not sure which model fits your business? Book a time with us. No obligation. Just expert advice.
Frequently Asked Questions
What is co-managed IT?
Co-managed IT is an arrangement where your internal IT staff and an outside provider split the IT function between them, each owning a defined set of responsibilities. Your staff typically keeps desk-side support and business-specific applications. The provider typically takes monitoring, patching, security and backup.
What is the difference between co-managed and fully managed IT?
Fully managed IT means the provider owns the entire IT function and there is no internal counterpart. Co-managed IT means you keep internal staff and divide responsibilities with the provider. The deciding factor is whether you have IT staff you want to keep and redeploy.
Is co-managed IT cheaper than fully managed IT?
Not automatically. Co-managed covers a narrower scope, so the provider’s portion is usually smaller, but you are still paying your internal staff and keeping a coordination workload in-house. Compare the total cost of both sides, not just the provider’s invoice.
Can a Utah business with only one IT person use co-managed IT?
Yes, and that is one of the most common cases we see. A single internal person cannot cover monitoring, security, patching and the helpdesk at once. Co-managed IT gives them coverage in the areas one person cannot hold alone, particularly outside business hours.
Who owns the tools and documentation in a co-managed arrangement?
It depends on the agreement, which is why it should be settled before you sign. Ask who owns the monitoring and ticketing platforms, whether documentation stays accessible to you, and what happens to your configuration data if the relationship ends.
Does 1Wire offer co-managed IT in Salt Lake City, Ogden and Provo?
Yes. 1Wire provides both co-managed and fully managed IT to businesses throughout Utah, including Salt Lake City, Ogden, Provo, Orem, Layton, Murray, Draper and St. George, and we have been doing it since 2006. See managed IT solutions for what each model includes.
