In-House IT vs Outsourcing in Saudi Arabia: The Costs That Never Reach the Salary Line

The decision usually arrives as a single comparison: one IT salary against one monthly fee. It is a clean comparison and it is the wrong one, because only one of the two numbers is complete.

This article is about building the comparison properly. We are not going to tell you what a systems administrator earns in Riyadh — that number moves by city, sector and seniority, and a figure invented for an article is exactly the kind of thing this site exists not to publish. Put your own salary number in. What follows is everything that sits around it, and the coverage question that no salary answers.

What sits around a salary

Before comparing anything, add these to the employment side of the ledger. Every one is real and none of them appears in the offer letter:

• Recruitment — agency fees or the internal cost of running a hiring process, plus the weeks the role sits empty.
• GOSI and statutory contributions, which are a percentage on top of salary, not part of it.
• Allowances — housing and transport are conventional in the Kingdom and are frequently quoted separately from base pay.
• Visa, iqama and sponsorship costs where the hire is an expatriate, including renewals and dependants.
• Training and certification — a technical person who is not kept current becomes less useful every year, and vendor certifications carry both a course cost and time away from the desk.
• Tools — remote monitoring and management, a ticketing system, antivirus and endpoint management consoles, backup software. An outsourcing fee includes these; a salary does not.
• Specialists — the firewall migration, the exchange problem, the storage failure. Your generalist will call somebody, and you will pay that somebody.
• Management time — someone senior has to set priorities for the role, review the work, and cover the gap when it is vacant.

Saudization is a factor, and it is not only a cost

Saudi nationalisation requirements apply to companies operating in the Kingdom, and the ratio expected of you depends on your sector and size. Technical roles sit inside that calculation like any other headcount, so an IT hire is not a neutral decision — it can move your standing in either direction, and the specifics are worth confirming with your PRO or HR advisor against the current programme rules rather than against a blog article.

The point for this comparison is narrower and more practical: an outsourced service is a supplier relationship, not a headcount, so it does not participate in that calculation at all. For some companies that is a meaningful simplification. For others, who want to build local technical capability deliberately, it is a reason to hire. Both are legitimate; what matters is making the choice knowingly.

The part a salary cannot buy: cover

This is the argument that usually settles it, and it has nothing to do with money.

• One person cannot cover the hours. Backups run overnight. A disk fills at 2am. A shop opens on a Friday. An employee works office hours, and everything outside them is either an unpaid favour or an on-call arrangement you have to negotiate.
• One person cannot know everything. Firewalls, Microsoft 365, backups, cameras and security are five specialisms. A generalist covers each to a point and then calls a specialist — whom you are already paying for, in the outsourcing model.
• One person takes leave, gets ill, and eventually resigns. When they are away, IT stops. When they leave, the knowledge leaves with them, because it lived in their head and not in a document.

That third point is the expensive one, and it is invisible until it happens. Ask any company that has lost its only IT person how long the handover took and what was still undocumented six months later.

We sell both, which is why this is not a sales pitch for one

There are two ways to outsource and we do both, so nothing above is written to push you toward the one that suits us:

• The managed function — the help desk, the monitoring, the patching, the vendor conversations and the reporting, priced per device and per user, so it stops being anyone internal’s job.
• Staff augmentation — named engineers by skill level, with your team on site or remote, monthly. It is the closest thing to hiring, without the recruitment, the cover problem or the single point of failure: your engineer is backed by the same help desk and escalation path, so they are never the only person who knows.

Both are on the IT outsourcing page. Augmentation is priced on the role rather than per device, so tell us what you need covered and we will quote it.

When hiring outright is the right answer

It genuinely is, sometimes — though in our experience it is the smaller group, and most companies of this size are better served by a support contract plus whatever internal presence they already have. Hire outright when:

• IT is part of what you sell, rather than what you run on. A software company needs engineers, not a support contract.
• You need someone physically present all day, every day — a large single site with constant hands-on demand.
• Your systems are unusual enough that generic expertise does not apply, and the knowledge genuinely has to be internal.
• You are deliberately building local technical capability as a strategic goal.

The answer most companies actually land on

Not either. The most common arrangement we sell is a company that keeps its IT person and outsources the parts that do not fit one role: the out-of-hours cover, the monitoring, the security, the specialist work, and a second pair of hands during projects. The internal person stops being a single point of failure and starts being the person who knows the business.

That is co-managed IT, and it is covered in full in co-managed versus fully outsourced IT. Every area is priced on its own, so you can hand over one and keep the rest.