Home · Services · Co-managed IT
You already have somebody. They are good, but busy. We fill the gaps to help and not replace.
Why firms ask for it
The internal IT person at a firm of forty, or a hundred and forty, covers help desk, network, security, projects and vendors. We can help prevent something being forgotten.

Overnight, weekends, holiday weeks. An internal team of one or two has no rotation, and everyone quietly hopes nothing happens while they are away.
Monitoring, patching, backup, phishing training, a security operations center. Hard to justify for one firm alone. We license them across every partner.
A single IT person has nobody to check their projects or security against. We are that experienced ear.
Which arrangement
Three ways to buy support. What changes between them is who handles the day-to-day.
Nobody. You call a shop when something breaks and pay for the visit. Prevention is not billable, so it does not get done.
Your IT person, with a written split of the seven lines that follow. We carry the rest.
We do, help desk included. One owner for the whole environment, with the plan and the budget attached.
You are under ten people, nothing you hold is regulated, and a day without email is survivable.
You have one or two technical staff and more work than they can carry: a growth year, a system replacement, an audit with a date on it, or a skill nobody has.
There is no internal technical seat, or the seat is open and staying open.
The first serious outage. One of those usually costs more than a year of either alternative.
Three situations, set out below under when co-managed is the wrong answer.
You hire technical staff and keep them, and then the help desk is paid for twice.
The split

Usually your person. They know the business and they know the people. We take overflow and everything outside working hours. Some firms invert it and send all first-line to us.
When a machine starts encrypting files at midnight, somebody has to isolate it without waiting for a meeting. Where you own the security stack, that call stays with your person. Where we run it, we ask for that authority in writing, with a named list of who gets called straight after.
The tenant, the domain name and the top-level accounts stay in the firm's name, with your person holding them. Our access is granted and can be revoked. Where we are running the department, we co-hold them so there is cover when your person is out. Worth checking against whoever you use today.
A server replacement or an office move eats a quarter of an internal calendar. We take the project so your person keeps the day running, or we work under them if they would rather lead. The plan is written and the hours are quoted up front.
One record of the environment that both sides write into, held somewhere the firm owns. Two half-complete sets is the usual failure, and it shows up during an incident or an audit. It is also what protects you if your person leaves.
Circuits, phone systems, the design or accounting package your work depends on. Sitting on hold is the lowest value hour in your person's week, so we share the chase with them, and take it outright once we are running the department. They keep the application vendors who know your configuration.
Both of us, in the same room. Our advisor brings what we see across other firms of your size, and a forecast for your company. Your person brings what no outsider knows about your business.
If you are looking for more information on what might be best, the IT spending benchmark and the managed IT services page can assist.
The conversation worth having

The only IT person never takes a week off without a laptop. A written handover makes it a real week.
Endpoint detection, immutable backup, phishing simulation, a password platform. One firm cannot justify the spend. Your person gets the console.
Working alone means every design decision goes unreviewed until it fails. Our engineers see the same problem across many firms.
Patch chasing, warranty lookups, hold music, the offboarding checklist. None of it is why they took the job.
In practice

Their IT lead had the replacement on his list for two years and no quarter free to do it. We ran the project alongside him. It finished without taking over his calendar, and he kept the environment he is accountable for. No dramatic number attached to this one, which is the point: the work was overdue rather than on fire.
When the internal person is leaving inside six months, since you are buying a handover and not a partnership. When nobody internally has authority to agree the split, because the arrangement then has no owner on your side. When the real problem is that the person is not up to the job, that is a management conversation and not something a provider should be hired to have for you.
The first call
Renascence IT Consulting has worked alongside in-house IT teams since 2005. Fifteen minutes with both of you. They will have sharper questions than you do, and how a provider answers those in front of you tells you most of what you need to know.