Article

Fully managed vs co-managed IT: which model fits your team?

Fully managed IT suits organisations without internal IT staff; co-managed IT suits those with an IT person or team who need capacity, cover and specialist skills. Decide who should own day-to-day decisions, and write that split down.

The short answer

Fully managed IT: one provider monitors, supports, maintains and secures your systems and users. It fits organisations with no IT staff, or one overloaded non-specialist.

Co-managed IT: your IT person or team stays in charge; a provider adds monitoring, patching, routine tasks, after-hours cover, specialist escalation and projects. It fits organisations that value in-house knowledge but lack capacity or depth.

Both work. Both fail when nobody writes down who owns what.

Side by side

Fully managedCo-managed
Who leads day to dayThe providerYour internal IT lead
Users callThe provider's help deskUsually your IT team, provider behind them
Tools (monitoring, patching, ticketing)Provider'sShared, or provider's with your team's access
After-hours coverProvider, for managed-service clients under the agreementProvider, for agreed systems and alerts
Strategy and budgetProvider's vCIO with your leadershipYour IT lead, supported by the provider's vCIO
Best whenNo IT staff, or IT is someone's side jobOne or more IT staff who need backup
Main riskLosing internal knowledge of the businessUnclear boundaries between two teams
Switching models later

Neither model is permanent: co-managed while you have an internal IT person, fully managed if they leave, or the reverse when you grow enough to hire. Keep documentation, credentials and domain registrations in your organisation's name so either move is straightforward.

How to decide

Is IT someone's actual job?

If not, fully managed is usually simpler and safer.

Keep knowledge in-house?

Specialist systems (clinical software, manufacturing controls, custom databases) benefit from an insider.

What is slipping?

After-hours, patching, security monitoring: co-managed fills those. Everything: fully managed.

Will both sides share?

Co-managed needs one ticket system, one set of documentation and named accounts.

The responsibility matrix

A co-managed agreement stands or falls on a clear split. A starting point to adapt:

TaskYour IT teamProviderShared
First-line user support during business hoursYes
After-hours alerts and triageYes
Operating system and third-party patchingYes
Line-of-business application supportYes
New user setup and offboardingYes
Firewall and network changesYes (approval by your IT lead)
Backup monitoring and restore testingYes
Security alert investigationYes
Vendor relationships for core business systemsYes
Roadmap and budgetYes (owner)vCIO support

The rows matter less than every row having an owner.

Hypothetical example
Demonstration, not a client project

A regional distributor with two internal IT staff chooses co-managed IT. The internal team keeps the warehouse scanners, the ERP and user support. As a managed-service client, it gets the provider's 24/7 monitoring and support, plus patching, backup testing, endpoint security alerts and a Windows server upgrade the team never had time for. A monthly review between the IT lead and the provider's vCIO keeps the list current.

What usually goes wrong

PitfallFix
Two sources of truth (tickets, documents, a password spreadsheet)One ticket system and one documentation platform; unrecorded means it did not happen
Shared admin logins hide who changed whatNamed, least-privilege provider accounts with multi-factor authentication
A Friday-evening change becomes a 2 a.m. alertAn agreed change process, even a light one; include generator servicing and internet link switches
The internal team feels displacedInvolve them in choosing the provider and the matrix; their job should get easier and more interesting
Fully managed, no business contactName who approves changes, purchases and priorities

Good practice (NIST Cybersecurity Framework) gives individuals only the privileges they need, and providers only the access their services require. Under the Nigeria Data Protection Act 2023, a provider handling personal data for you is a data processor, so access control and a written processing agreement matter too.

Rather talk it through? We can run a short responsibility-mapping session with your IT lead and show which model closes your gaps. Talk to a Promatics specialist

When to bring in help

A stable team, documented systems, a tested backup and holiday cover? You may not need either yet. Bring in a provider when IT staff cannot safely take leave, patching and monitoring lag, or projects wait months. No internal IT? See managed IT services.

How Promatics approaches co-managed IT

  1. MapA responsibility-mapping workshop with your IT lead.
  2. OnboardTools and access through separate named accounts, so every action is traceable.
  3. Share the workYou keep specialties; we take monitoring, patching, routine work, after-hours, escalation.
  4. ReviewRegular reviews with our vCIO keep the split honest.

Our co-managed IT page sets out the full scope.

Sources and further reading

Product capabilities and guidance change. These are the primary sources this article relies on, checked on the review date above.

  1. Cybersecurity Framework (supply chain risk management), NIST

This article is general information, not legal, accounting or security advice for your specific situation. Examples are hypothetical unless stated otherwise.

Talk to Promatics

Find the support model that fits the team you have

Choosing is easier with someone who has seen both models work. We will map who should own what and show you where the gaps are.

  • A written responsibility matrix, not vague promises
  • Your IT staff keep control of what they know best
  • After-hours cover and specialist escalation included