Keep Your IT Person or Hire an MSP? Why the Answer Is Often Both

If you have one IT person and 50 or more staff, the choice you are probably weighing, keep them or replace them with a provider, is a false one. Co-managed IT keeps your person for the daily work and the business context, and adds a managed services provider behind them for monitoring, security tooling, backup, after-hours cover and the depth one person cannot carry alone. In a survey of 1,000 UK IT workers published in April 2026, 53% said they are regularly pulled into troubleshooting minor issues and 43% said their department lacks the resources to handle disruptions; that is the one-person IT team's week in two numbers. For a 60-person Singapore company, a sensible planning figure is your existing IT person (S$8,500 to 12,500 a month all-in) plus roughly S$3,000 to 6,000 a month for the provider layer, hedged below. This is the co-managed guide we promised in our in-house versus managed IT comparison and in 7 signs you've outgrown your IT support.

What co-managed IT means in plain terms

Most Singapore SMEs already run a co-managed model in another department. Your HR executive knows every employee, handles the awkward conversations and decides who gets which laptop. The payroll bureau runs the monthly payroll, files CPF and keeps up with rule changes nobody in your office has time to read. Nobody thinks the bureau is there to replace HR; each does the part it is built for, and the handover line is written down.

Co-managed IT is the same arrangement for technology. Your in-house person stays the face of IT and keeps the business knowledge: which spreadsheet crashes at quarter-end, which supplier portals need which logins. The provider supplies what one person structurally cannot: 24-hour monitoring, a patched and watched security stack, tested backups, a second engineer when a problem is beyond the first, and someone awake when your person is on leave. In a fully managed arrangement the provider does all of it; in co-managed, you split it.

Self-check: if your IT person took three weeks off tomorrow, what would be unmonitored, unpatched and unanswered? That list is the provider's half of a co-managed contract.

The three situations it fits

One IT person at 50 or more staff

Industry staffing guides commonly put one help-desk technician per roughly 70 to 100 users, and that assumes someone else handles security, projects and the servers. At 50 staff, one person is doing all of those jobs at once; at 80, the proactive work (patching, backup checks, reviewing who still has access to what) is the first thing to slip, because nobody files a ticket for it. A second hire costs another S$8,500 a month and more, and gives you two generalists instead of depth.

Your in-house person is drowning in helpdesk

A capable engineer spends the day on password resets, printer queues and "my Teams is weird". The survey figure above, 53% regularly diverted to minor issues, describes this exactly, and the cost is the project that never happens. The split can go either way. Some companies hand first-line support to the provider so their person can do projects; others keep first-line in-house, where the business context lives, and hand over everything behind the scenes. Both work. Leaving one person to do both does not.

Security and after-hours gaps

One person cannot watch screens at 3 am, and should not be the only one who knows the backup password. A clinic solves the same problem with a locum: when the regular doctor is on leave, the same patients still get seen by someone qualified and briefed, and nobody has been replaced. The provider's security monitoring, EDR and MDR tooling and out-of-hours response are the locum for your IT person. Insurers and auditors now ask about this gap directly, and "our IT guy checks it" is no longer an answer they accept.

Who does what: the responsibility split

The model succeeds or fails on one document: every IT responsibility with a name against it. Here is the split we see work most often; yours will differ, and the point is to write it down.

• In-house person owns: first-line support and the face of IT to staff; onboarding and offboarding on the ground; business applications (ERP, POS, the industry software); supplier and licence relationships; the IT budget conversation with you.
• Provider owns: 24-hour monitoring and alerting; patching of servers, laptops and firewalls; the security stack and its daily review; backup, restore testing and the recovery targets; after-hours and leave cover; second- and third-line escalation.
• Shared, with a named lead: the roadmap and quarterly review; major projects such as a server migration or office move; security incidents (provider leads the technical response, your person leads the staff side); documentation, kept where both can see it.

Ask: can your prospective provider give you this list, with their name beside the items they take on, before you sign? A provider that will not commit to a split in writing drifts towards whatever is easiest to bill, and the gaps land on your person.

What it costs a 30- and 60-person Singapore company

These figures derive from the Singapore managed IT range of S$100 to 300 per user per month in our 2026 price guide and the all-in cost of an in-house IT manager of S$8,500 to 12,500 a month. A co-managed layer that excludes first-line support usually prices towards the bottom of that range, around S$50 to 100 per user, because the provider supplies tooling, monitoring and escalation rather than a daily help desk. A starting point for a budget conversation, not a quote; the real number depends on which items on the list above move across.

30-person company: your IT person at S$8,500 to 12,500 a month plus a provider layer of roughly S$1,500 to 3,000, about S$10,000 to 15,500 in total. Fully managed with no hire would be S$3,000 to 9,000. At this size, co-managed is usually only the right shape when the IT person also runs something else, such as operations or the ERP, that you would have to hire for anyway.

60-person company: your IT person at S$8,500 to 12,500 plus a provider layer of roughly S$3,000 to 6,000, about S$11,500 to 18,500 in total. Fully managed would be S$6,000 to 18,000; a second in-house hire at S$8,500 and up still leaves the 3 am gap open. Here the arithmetic usually favours co-managed, which is why it has become the common pattern for Singapore SMEs between 50 and 150 staff.

When co-managed is not the answer

We tell a good share of the owners who ask about this to do something else. The usual reasons:

You have under 30 staff and a plain setup. A fully managed plan costs less than one salary and covers more hours. Hire an IT person later, when there is a full-time job for them.

Your IT person wants to leave, or should. Co-managed is built around a person who knows the business and wants to stay. If the real problem is performance or attrition, a provider stacked on top hides it for a year rather than fixing it.

You want one party to hold accountable. Shared responsibility is only safer when the split is written down and enforced. If you know you will never read that document, fully managed is the honest choice.

The provider will not share control. Some providers insist on holding every admin password and every piece of documentation, with your person reduced to raising tickets. That is fully managed with an extra salary on top. Walk away.

The people side: "are they replacing me?"

Your IT person will think this the moment you mention a provider, whether or not they say it, and it is a reasonable fear: "we're bringing in an MSP" has opened many redundancy conversations. Handle it badly and you lose the one person who knows where everything is, in the worst week to lose them.

Say it plainly and early: "I am not replacing you. I am buying you a night shift, a security team and a second opinion, so that the next time the server dies on a public holiday it is not only your phone that rings." Then show them the responsibility split and let them mark it up. Most engineers, once they see the list, want the provider to take the 3 am alerts and the patching; nobody went into IT to reset passwords at midnight.

Their role changes shape: they become the person who understands both the business and the technology, manages the provider on your behalf, and finally has time for the projects that have sat on the whiteboard for two years. In our experience that is a promotion in all but title, and often in title too. One red flag: a provider that pitches co-managed with "and over time you may not need the headcount" is selling you fully managed on a delay. Ask them, in front of your IT person, how they see the role in two years.

Frequently asked questions

Will the provider and my IT person just blame each other when something breaks?

Only if the split is not written down. With a named owner for each responsibility and one shared ticket system, "whose job was this" has an answer in seconds.

Does co-managed IT cost less than fully managed?

The provider fee is usually lower, because first-line support and business applications stay with your person. Including their salary, the total is higher; you are paying for business context and a dedicated person on site.

Who holds the admin passwords and the documentation?

Both parties, in a shared system: a password manager with separate vaults and a documentation platform both can see. If either side insists on sole custody, that is a warning about how the relationship will go.

Can we start with a small scope and expand?

Yes, and we recommend it. Monitoring, patching and backup are the usual first slice because they slip first when one person is busy; security tooling and after-hours response come next.

Send this to your IT provider (and your IT person)

Copy this to the provider you are considering, with your IT person in copy. Their reaction to being copied is itself useful information.

Hi, we are considering a co-managed arrangement where our in-house IT staff member keeps first-line support and business applications, and you take on the areas one person cannot cover. Please send me: (1) a responsibility list covering monitoring, patching, security tooling, backup and restore testing, after-hours response, escalation, documentation and projects, with your name against the items you would own and "shared" where applicable; (2) how our IT staff member would access your ticket system, monitoring and documentation; (3) your proposed monthly fee for that scope for [N] users, excluding first-line support; and (4) how you see our in-house role developing over the next two years. We would like our IT staff member in the next conversation.

Our approach

Evernet Systems, a Singapore managed IT services provider, runs co-managed arrangements alongside fully managed ones, and we like them: an in-house person who knows the business makes our engineers better. That is our bias. It only works when the owner holds two parties to one written split and the in-house person is in the room from the first meeting, so we insist on both.

The honest line: if you have fewer than 30 staff, or your IT person is on the way out, we will usually tell you co-managed is the wrong shape, and say which shape is right. If you have 50 or more staff and one good person who is drowning, it is probably the answer, and the SLA you agree with the provider should cover their half of the list in the same detail as a fully managed contract. Book a discovery call and bring your IT person; you will get a straight answer, even if it is "keep what you have and hire a second engineer".