Why businesses choose a shared model
Internal IT people are often stretched thin. They handle every password reset, laptop setup and printer jam, and the strategic work never quite gets started. Security monitoring, patch reporting and backup testing slip because there is always something more urgent. Bringing in a provider for those background jobs frees the internal person to focus on the staff, systems and projects that benefit from someone who is in the building every day.
The other common reason is resilience. A single IT person cannot cover their own annual leave, a sick week or the late-night server failure. A co-managed arrangement gives the business a second set of hands that already knows the environment, so a holiday or resignation does not leave everyone stranded or scrambling for a stranger to work out how things are set up.
Typical ways the work is split
There is no single template, but a common split puts the internal person in charge of first-line help, staff onboarding, line-of-business software and day-to-day relationships, while the provider runs monitoring, patching, endpoint security, backup checks and after-hours cover. Projects might be shared, with the internal person scoping what the business needs and the provider delivering the technical build.
Another version flips the emphasis: the provider runs the help desk so the internal person can work on improvement projects, reporting and supplier management. Neither approach is right or wrong. What matters is writing the split down task by task, so nothing falls into the gap where each side assumes the other is handling it.
Shared tools and shared access
Co-managed IT works best when both parties use the same tools. That usually means the internal person gets access to the provider's ticketing system, monitoring dashboards and documentation platform, so they can see alerts and history without asking. Duplicate systems create confusion: two places to log requests, two sets of notes and two versions of the truth about how a firewall is configured.
Admin access needs careful handling. Both parties will need elevated permissions, but each person should have their own named account rather than sharing a single admin login. That way every change can be traced, and if either side leaves the arrangement, their access can be removed cleanly without resetting passwords that the other side relies on.
Getting the responsibility matrix right
Before starting, build a simple table listing every recurring IT task: patching, backups, new users, leavers, licence renewals, firewall changes, security alerts, supplier calls, hardware purchasing and so on. For each, record who does it, who approves it and who checks it was done. Review the table together after the first month and again each quarter, because real work rarely matches the plan exactly.
Pay particular attention to security alerts and backups. These are the two jobs most likely to slip in a shared arrangement, because each side can reasonably assume the other is watching. Assign a single owner for each, with the other as a named backup, and agree what happens when an alert arrives outside office hours.
What co-managed IT costs
Pricing varies. Some providers offer a reduced per-user fee because the internal person handles first-line requests. Others charge a platform fee for tools and monitoring plus an hourly or block rate for escalated work. A few price the arrangement as a retainer for a set number of hours each month. Ask how each option handles a busy month, so a security incident does not turn into a large surprise bill.
When weighing the cost, compare it with the alternatives rather than with nothing. Hiring a second internal IT person costs considerably more. Buying monitoring, backup and security tools separately for one internal person to run costs money and time to set up. Co-managed IT often lands between the two, with the bonus of a team that can scale up when you need it.
Keeping the relationship healthy
Treat the internal IT person as the provider's main contact and include them in every review. A co-managed setup fails when the provider and the internal person compete rather than collaborate, or when the internal person feels they are being replaced. Be clear with both sides that the goal is more capability, not a quiet handover.
Meet regularly, even briefly. A short monthly catch-up covering open issues, upcoming changes and anything the internal person needs help with keeps both sides aligned. Once a quarter, step back and look at bigger themes: recurring faults, security posture, upcoming hardware replacement and whether the split of tasks still makes sense as the business grows.
In short
- Co-managed IT shares work between your internal IT staff and an outside provider.
- Write down who owns each recurring task so nothing falls through the gap.
- Use shared tools and named admin accounts, never a single shared login.
- Give backups and security alerts one clear owner each.