Plenty of businesses have one IT person. They know every printer, every user and every workaround, and they are also the reason nothing gets patched during a busy month, because there is only one of them. Co-managed IT is the arrangement where a provider backs that person up rather than replacing them.
It works well when the split is written down and both sides use the same tools. It fails when the provider treats the internal person as a ticket source, or the internal person treats the provider as a threat. Here is how to set it up so neither happens.
Decide the split by task, not by title
Start from a list of everything IT does for the business and assign each line to one owner: the internal person, the provider, or shared with a named lead. The usual pattern is that the internal person keeps what needs presence and context (desk-side support, onboarding, vendor relationships, the odd application only they understand) and the provider takes what needs scale and coverage (monitoring, patching, backups, after-hours response, projects).
Write it as a table with three columns and review it quarterly. The table is what stops the argument about whose fault the unpatched server was. It also gives the internal person a clear path to hand off the things they are tired of and keep the things they enjoy.
- Internal: desk-side support, new hire setup, local vendors, business-specific applications
- Provider: RMM and monitoring, patch rings, backup verification, security stack, after-hours desk
- Shared with a lead: projects, security incidents, documentation, quarterly review
- Escalation: which tickets the internal person hands to the provider and how
- Approvals: who can approve spend, and who can approve a change to production
One set of tools, both logged in
The internal person gets a seat in the provider's RMM, ticketing system, documentation platform and password vault, with the same views the provider's technicians have for that client. Two separate ticket queues for one company is how requests fall between them.
Give them real access, not a read-only demo. They should be able to run scripts, take remote sessions, and close tickets. Their actions show up in the same audit log as everyone else's. In return, they follow the same rules: changes go through tickets, credentials live in the vault, documentation gets updated when something changes.
- Create the internal person's account in the RMM, ticketing, documentation and vault
- Scope their access to their own company, with full technician rights inside it
- Migrate their existing notes and passwords into the shared platforms
- Agree the ticket categories that route to them versus the provider
- Train them on the provider's change and documentation rules in one session
Coverage: holidays, sickness and the 2am page
The most immediate value of co-managed IT is that the business is no longer one flu away from having no IT. Write the coverage rules explicitly: when the internal person is out, the provider handles desk-side requests remotely and dispatches for anything physical. After hours, the provider's desk answers and the internal person is not on the escalation chain unless they want to be.
Both sides should be honest about capacity. If the internal person is also the office manager, they are not a full-time technician and the split should reflect that. If the provider is small, say what after-hours coverage really looks like. A 24/7 desk with a short critical response target is a real commitment; put it in the agreement only if it is staffed.
Keeping the relationship healthy
A short weekly call between the internal person and the provider's account lead does most of the work: open tickets, upcoming changes, anything the business mentioned. The quarterly review then includes the internal person as a presenter, not an audience member, reporting on their side of the table.
Treat the internal person's knowledge as the asset it is. Get it into the documentation platform with their name on the pages. It protects the business when they eventually move on, and it gives them credit for the years of context they are sharing. If you are an internal IT lead looking for a provider that will work this way, RackLedge sets up co-managed arrangements with exactly this kind of written split.
- Weekly 20-minute sync between the internal person and the account lead
- Internal person presents their section at the quarterly review
- Their tribal knowledge captured in documentation with their name on it
- Ownership table reviewed quarterly and adjusted as skills and interest change
- A written path for handing more, or less, to the provider over time
Frequently asked questions
Does co-managed IT cost less than fully managed?
Usually the provider's fee is lower because the internal person carries part of the load, but the business is still paying that person's salary. Compare the total, and value the coverage and depth rather than only the monthly figure.
What if the internal person resists the arrangement?
Usually the fear is replacement. A written ownership table that gives them the interesting work and takes away the tedious work, plus a clear statement from the owner about their role, resolves most of it.
Who is accountable when something goes wrong?
Whoever owns that line in the table. If the line is shared, the named lead. If it is not in the table, add it that day so the next incident has an owner.
Takeaway
Co-managed IT is a written split of tasks, one set of tools that both sides log into, honest coverage rules, and a weekly conversation. The internal person keeps context and presence; the provider brings scale and after-hours coverage. The table of who owns what is the whole arrangement; keep it current.