
Managed IT vs in-house IT: which model suits your organisation?
Managed IT vs in-house IT is the choice between paying a provider to run your IT under a service-level agreement and employing your own staff. Managed IT brings continuity and breadth of skills, in-house IT brings presence and business knowledge, and many South African organisations combine the two. Arke Technologies runs managed and co-managed IT.
Managed IT vs in-house IT: which model suits your organisation?
Last reviewed: September 2026 · , 13 min read
Managed IT vs in-house IT is the choice between paying a provider to run your IT under a service-level agreement and employing your own staff. Managed IT brings continuity and breadth of skills, in-house IT brings presence and business knowledge, and many South African organisations combine the two. Arke Technologies runs managed and co-managed IT.
Last reviewed: September 2026 · , 13 min read
On this page
The short answer
- In-house IT gives you people who know your business and work in your building, but cover and skills only go as deep as your headcount.
- Managed IT buys a team, its tooling and documented processes for a predictable fee per user per month, with the scope fixed in a service-level agreement (SLA).
- Co-managed IT splits the work: your team keeps direction and on-site work, and a provider runs agreed parts such as the service desk, monitoring, security or servers.
- Decide on risk and continuity over the contract term, not on one salary against one monthly fee.
What managed IT and in-house IT each mean
In-house IT means the people who run your technology are your employees. You recruit them, buy their tools, set their priorities and carry the gap when they are on leave or resign. Many organisations start with one capable IT person and add people as their systems multiply.
Managed IT means an external provider, called a managed service provider (MSP), takes responsibility for agreed parts of your IT under an SLA: monitoring, the service desk, patching, security baselines, backup checks, user administration and reporting. You pay a fee per user per month and hold the provider to the terms of the agreement. Our guide to what managed IT services are explains the model in full.
Co-managed IT sits between the two. Your IT manager or team stays in charge, and the provider fills defined gaps; see co-managed IT. Handing the whole function to a provider is IT outsourcing.

Managed IT vs in-house IT compared
The table sets the three models side by side on the questions boards, finance teams and procurement officers ask.
| Question | In-house IT | Managed IT | Co-managed IT |
|---|---|---|---|
| How you pay | Salaries, recruitment, training and tools | A fee per user per month under an SLA; projects quoted separately | Your team's cost, plus a fee for the provider's scope |
| Cover for leave, illness and resignation | As deep as your headcount | The provider's obligation under the SLA | The provider covers its scope; your team covers the rest |
| Breadth of skills | Limited to the people you employ | A team across service desk, networks, Microsoft 365, security, servers and cloud | Your generalists plus the provider's specialists |
| Monitoring, remote access, ticketing and patching tools | You buy, run and secure them | Part of the service | Usually the provider's, shared with your team |
| Knowledge of your business | Deep and immediate | Built during onboarding and kept in documentation | Held by your team and documented by both |
| Control of priorities | Direct | Through the SLA, service reviews and change control | Direct for your scope; through the SLA for the provider's |
| Scaling up or down | Hire, or restructure | Add or remove users on the fee | Change the provider's scope |
| Evidence for auditors and boards | Whatever your team records | Monthly reports, ticket history and change records | Both, if responsibilities are written down |
| Exit | Knowledge leaves with people | Handover of data, credentials and documentation, if the contract requires it | As for managed IT, for the provider's scope |
What in-house IT really costs
The visible cost of in-house IT is a salary: IT support technicians in Johannesburg earn about R21,054 a month on average (Indeed, September 2026). The full cost adds items that seldom sit on the same budget line:
A second person. One technician is a single point of failure. When that person is on leave, ill or resigns, support stops, so continuity needs a second person or a provider standing behind the first.
Breadth. Networks, Microsoft 365 or Google Workspace, servers, backup and cybersecurity are separate specialisms, and one person rarely covers all of them in depth.
Tools. Remote access, monitoring, ticketing, patch management, backup and endpoint security each need licences, set-up and upkeep.
Training and certification, to keep skills current as platforms change.
Recruitment and management time, including the cost of a vacancy while systems wait.
Documentation. Systems that live in one person's head become a liability on the day that person leaves.
What managed IT costs
R180 to R400 per user per month
published South African managed IT rates (matnet.co.za, September 2026), with some providers listing R450 (MiBOT, September 2026).
R550 to R750 an hour, ex VAT
published rates for IT project work (matnet.co.za, September 2026).
At those published rates, 60 users would cost about R10,800 to R24,000 a month for a managed service, a range that overlaps the pay of one technician before that person's tools, cover and training are added. The fee moves with the number of users and devices, sites and servers, the security and compliance scope, on-site requirements and the hours of cover you need. Work outside the SLA, such as a migration or a new site, is quoted as a project.
At Arke Technologies, managed IT is priced per user per month after an assessment and billed monthly in advance by debit order, and project work is quoted per project. See managed IT pricing and our guide to how much managed IT services cost in South Africa.
When in-house IT is the better choice
An internal team is the stronger model when:
Someone must be physically present all day, for example on a production floor, across a campus of computer labs, or at a site where equipment is handled daily.
Your systems are bespoke and change weekly, and knowing how they work is part of your competitive advantage.
You are large enough for depth, with several people who cover for each other and hold the main specialisms between them.
Technology direction is strategic, and you want it set inside your own leadership team.
Even then, consider buying in the layers a small team cannot staff economically, such as security monitoring or a second line of server expertise.
When managed IT is the better choice
A provider is the stronger model when:
Support depends on one or two people, and a resignation would leave systems unmanaged.
You need skills you cannot justify full-time: cybersecurity, Microsoft 365 or Google Workspace administration, networks, servers and cloud. Our guide to what cyber security involves shows how wide that field has become.
Your board, auditors or governing body want evidence: SLA reports, ticket history, change records and documented controls.
You run several sites or remote staff, and need the same standard of support everywhere.
Finance wants a predictable cost per user instead of recruitment, tools and overtime.
The middle ground: co-managed IT
Co-managed IT is often the practical answer for an organisation that already employs an IT manager or a small team. The internal team keeps what it does best: knowing the business, setting priorities, managing suppliers and working on site. The provider takes the load that stretches a small team, such as first-line support, patching and monitoring, or specialist work in security and server management.
It works when responsibilities are written down: a responsibility matrix in the SLA, one ticket queue so nothing falls between two teams, and one monthly report that covers both. If your needs grow, the scope can widen into fully managed IT; if you build more capability in-house, the provider should hand work back with the documentation to run it.
Risks on both sides, and how to control them
| Risk | In-house IT | Managed IT | The control |
|---|---|---|---|
| Key-person dependency | High: one person may hold the knowledge and the passwords | Lower, if the provider documents everything | Written documentation, with admin credentials held by your organisation |
| Skills gaps | Security and cloud skills are hard to hold in a small team | Depends on the provider's depth | Ask who does the work and how they are certified |
| Vague scope | Unclear job descriptions | Unclear SLAs and exclusions | An SLA that fixes scope, priorities, exclusions, on-site policy, price and term |
| Slow response | The queue depends on one person's day | Depends on the SLA | Incidents prioritised P1 to P4, with targets agreed for your organisation |
| Lock-in | Knowledge locked in people | Credentials or tools locked in the provider | A contracted exit: handover of data, credentials and documentation |
| Access to your systems | Standing admin rights for staff | Remote access by outsiders | Approved, logged sessions and least-privilege admin accounts |
This is how Arke Technologies applies those controls. Every remote session is approved and logged, on our own remote-access platform, built on open-source RustDesk and run on our own servers in Johannesburg; see RustDesk for business. Our monitoring checks each computer every 15 minutes and logs faults as tickets automatically. Routine fixes run from a library of standard repairs, and the riskier ones need a recorded human approval before they run. Everyone with access to your systems is bound by confidentiality and our security controls. Incidents are prioritised from P1 (critical outage) to P4 (low-impact request), with response and resolution targets matched to the business impact of downtime and agreed in your SLA.
Governance, compliance and procurement
King IV. Principle 12 makes the governing body responsible for technology and information governance. Outsourcing moves the work, not the accountability, so the board needs reports it can act on; our monthly service review and report provide them. See King IV and technology governance.
POPIA. A provider that processes personal information for you acts as an operator, and section 21 of POPIA requires a written contract that obliges the operator to keep that information secure. Whoever runs your IT, check that the contract does this and ask who will have access to your systems. See our POPIA compliance checklist.
PFMA, MFMA and the SITA Act. Municipalities, public entities and state-owned entities can buy managed IT through a proposal, SLA and purchase order, or a tender response, within their own supply chain rules. National and provincial departments must also follow the SITA Act, which routes much of their IT buying through the State Information Technology Agency; see PFMA, MFMA and ICT procurement and SITA and government IT.
Procurement fit. Arke Technologies (Pty) Ltd is a Level 1 B-BBEE contributor, which gives buyers 135% procurement recognition (sworn affidavit available on request). Company documents, our CSD supplier number and SARS tax compliance status are available on request, and we complete standard bidding documents (SBD forms) when a bid requires them; see company facts.
Service management. An ITIL-aligned service desk practice covers incidents, requests, problems and changes, with documented runbooks and an agreed escalation path; see ITIL and IT service management.
How to decide: five questions
01.
What must never stop, and what does an hour of downtime cost?
The answer defines your P1 incidents and the targets your SLA should carry.
02.
Who covers when your IT person is away?
If the honest answer is nobody, you have a continuity risk whichever model you choose.
03.
Which skills do you need but not employ?
Security, Microsoft 365 or Google Workspace administration, networks, servers and cloud are the usual gaps.
04.
What evidence do your board, auditors or governing body expect?
Reports, ticket history and change records are easier to produce from a managed service than from a busy individual.
05.
What happens at exit?
Whoever runs your IT, your organisation should hold the admin credentials, the data and the documentation.
Our guide on how to choose an IT company in South Africa lists the questions to put to a provider.
How Arke Technologies works alongside or instead of your team
Every engagement runs from discovery and assessment to a proposal, the SLA, onboarding and a monthly service review. Onboarding has four phases:
01.
Discovery
We document your assets, users, systems and dependencies, and identify vulnerabilities and gaps.
02.
Baseline
We set security baselines, configuration standards, monitoring thresholds and documentation requirements.
03.
Management
We take on the agreed scope under the SLA: service desk, monitoring, patching, user administration and maintenance.
04.
Optimisation
Monthly service reviews track performance, security and cost, and agree the next improvements.
Delivery is remote-first, on our own tooling, by a certified team we hire for experience, education and certifications: one contract and one accountable team for managed IT services, the IT service desk and remote IT support. You keep ownership of your data, credentials and documentation throughout. To start, request an IT assessment.
Related services
Related guides
- What are managed IT services?
- How much do managed IT services cost in South Africa?
- What is cyber security? A guide for South African organisations
- RustDesk for business: self-hosted remote access explained
- King IV and technology governance: what boards must know
- POPIA compliance checklist for organisations
Last reviewed: September 2026 · , 13 min read
Compare the two models on your own numbers
We will assess your environment and set out, in writing, what an in-house, managed or co-managed model would cover, cost and require of your team.
Request an IT assessmentRelated services
Related guides
- What are managed IT services?
- How much do managed IT services cost in South Africa?
- What is cyber security? A guide for South African organisations
- RustDesk for business: self-hosted remote access explained
- King IV and technology governance: what boards must know
- POPIA compliance checklist for organisations
Get our guides by email
Plain, sourced guides for the people who decide on and buy technology, sent to your inbox.
Frequently asked questions
Is managed IT better than in-house IT? Show answer Hide answer
Managed IT is better when you need continuity, broad skills and audit evidence at a predictable monthly cost; in-house IT is better when you need people on site all day or deep knowledge of bespoke systems. A combination often works best: keep an IT manager in-house, and use a provider for the service desk, monitoring and security.
Is managed IT cheaper than hiring an IT person? Show answer Hide answer
Often, once the full cost of employment is counted. IT support technicians in Johannesburg earn about R21,054 a month on average (Indeed, September 2026), before leave cover, training and tools, while published managed IT rates run from about R180 to R400 per user per month (matnet.co.za, September 2026). The break-even point depends on your user count and scope.
Can we keep our IT manager and still use managed IT? Show answer Hide answer
Yes. That arrangement is co-managed IT: your IT manager keeps direction, supplier relationships and on-site work, while the provider runs agreed parts such as the service desk, monitoring, patching or security. The SLA records who does what, and a single ticket queue and monthly report cover both teams, so work does not fall between them.
Do we lose control if we outsource IT? Show answer Hide answer
Not if the contract is written well. You set priorities through the SLA, the monthly service review and change control; you keep ownership of your data, admin credentials and documentation; and every remote session into your systems is approved and logged. With Arke Technologies each of these is standard, and an exit comes with a full handover.
How long does a move from in-house to managed IT take? Show answer Hide answer
It depends on the size and condition of your environment, so we set the timetable in the proposal after discovery and assessment. Onboarding runs in four phases (discovery, baseline, management and optimisation), and responsibility can transfer area by area rather than on a single day, which keeps the risk low for your staff and users.
What should a managed IT contract include? Show answer Hide answer
A managed IT contract should fix the scope, the P1 to P4 priority definitions with their response and resolution targets, exclusions, on-site policy, price per user and term. It should also set the reporting cadence, escalation path, change control and exit terms, including the handover of data, credentials and documentation. Ask to see a sample monthly report before you sign.
Can government bodies and schools use managed IT? Show answer Hide answer
Yes. Municipalities, public entities and state-owned entities can buy managed IT through a proposal, SLA and purchase order, or through a tender, within MFMA or PFMA rules; national and provincial departments must also follow the SITA Act. Schools buy through their governing body's procurement process. Arke Technologies is a Level 1 B-BBEE contributor, and our CSD supplier number, tax compliance status and company documents are available on request.
Compare the two models on your own numbers
We will assess your environment and set out, in writing, what an in-house, managed or co-managed model would cover, cost and require of your team. Call 010 447 2445 or email info@arketechnologies.com, or read more insights and guides.