Choosing an IT Support Model: In-House or Outsourced?

The Right IT Support Model for Your Company: In-House or an Outside Provider?

In many Syrian companies, IT support is “the young guy who knows computers” or a technician called in when something breaks. That works until the server fails on the day the accounts are closed. Here we set out the possible models and how to choose between them.

Cloud, infrastructure and security 5 min read

By Nour Aldein Tleti. Updated 7 October 2026.

What IT support model suits my company?

A very small company usually manages with an on-demand outside provider plus one employee who coordinates internally. As devices and systems grow, a regular support contract with clear preventive tasks fits better. Larger organisations need an in-house team backed by specialist providers for critical systems.

The basic models

On-demand support: You call a technician when something breaks and pay per visit. Fine to start with, but it does not prevent faults or guarantee a fast response.
A regular support contract: An outside provider looks after devices, backups and updates regularly, and responds to faults within an agreed time.
An in-house IT employee: Someone who knows the company and its systems and is available every day, but cannot be an expert in everything.
The mixed model: An internal coordinator for daily tasks, and an outside provider for networks, servers, security and specialist systems.

How to choose

Number of users and devices: The higher the number, the more daily faults and the greater the need for someone close by.
How critical the systems are: If a system outage stops sales or service, you need a guaranteed response, not “when the technician is free”.
Branches and locations: Companies spread across several cities need good remote support, and someone who can travel on site when necessary.
Documentation and ownership: Whatever the model, passwords and settings must stay documented and owned by the company.
Field conditions: With power cuts and travel sometimes difficult, ask the support provider what they do when reaching the office or connecting remotely is not possible.

What a support agreement should include

Scope of work: A clear list of what support covers, such as devices, network, server, email and systems, and what it does not.
Response times: How quickly normal and urgent faults are answered, working hours, and the contact channel, such as WhatsApp or phone.
Preventive tasks: Updates, backup checks and regular account reviews, with a short report.
Handover of information: An explicit commitment to hand over all passwords and settings when the contract ends.
Confidentiality: A commitment not to access customer data or financial files beyond what the work requires, and not to share them with anyone.

Moving to organised IT support

01
List devices and systems
Every computer, printer, router and server, and every program or subscription the company relies on.
02
Gather the passwords
Move them from the technician’s memory or scattered notes into a password manager owned by the company.
03
Identify what the business depends on
Rank systems by the impact of an outage, so you know where you need a guaranteed fast response.
04
Choose the model and write the agreement
Set out the scope, response times, preventive tasks and information handover in writing.
05
Review after a trial period
Assess response speed and how often faults recur, and adjust the agreement or model based on the results.

Comparing the models

Model	Suits	Main risk
On demand	A small office with few devices	Slow response and problems piling up without prevention
Regular outside contract	A small or medium company with no IT team	The provider knowing little about how the business works, if it is not documented
In-house employee	A company with many daily systems	The whole company depending on one person
Mixed	Medium and large or multi-branch organisations	Overlapping responsibilities if they are not clearly defined

Read also

Cloud, infrastructure and security

Frequently asked questions

Is it enough to have a young employee who knows computers?

It is enough for simple tasks, but networks, servers and security need specialist knowledge. Ideally that person acts as an internal coordinator backed by a specialist provider.

How does remote support work with weak internet?

Many faults are solved with a short remote session or guidance over the phone. But the agreement should include an on-site visit when a remote fix is not possible.

What should I ask a technician for when we stop working together?

All passwords and admin accounts, router and server settings, a list of devices and licences, and where the backups are.

How do I measure the quality of support?

Log faults, how long they take to fix and how often they recur. Good support reduces repeat faults over time instead of just fixing them each time.

When should I move from on-demand support to a regular contract?

When the same faults keep recurring, work stops more than once because of a technical problem, or you add a system you cannot afford to have down. At that point prevention costs less than repair.