Summary
Searching for the “best IT company in Lebanon” returns directories and lists, but no list knows your systems, your budget or how much downtime your business can tolerate. The right provider is the one that can show, in writing, how it will keep your systems secure and running, who will do the work, and how you can leave if it does not work out.
This guide gives you twelve questions to ask any IT services company or managed service provider (MSP), what a good answer sounds like, the red flags, the contract terms that protect you and a simple scoring sheet. It is written to be useful whichever provider you choose.
What is different about choosing IT support in Lebanon
- Power and connectivity. Power cuts, generator switch-overs and single internet links cause many outages. Your provider must design for them.
- People. Skilled engineers are in demand abroad. Ask how the provider keeps knowledge documented, so your service does not depend on one person.
- Payment and currency. Agree the currency, payment method and price-review rules in the contract.
- Discretion. Many companies do not publish their suppliers or clients. Reference calls are normal and more informative than logos.
- Regional reach. If you also operate in the UAE or the Gulf, check whether the same team can support you there.
Twelve questions to ask
1. Who will actually work on our systems?
Ask for the names and roles of the engineers assigned to you, and who covers when they are on leave or leave the company. Emigration has thinned many Lebanese IT teams, so a provider that depends on one senior person is a real risk.
A good answer: Named primary and backup engineers, documented systems so another engineer can take over, and an escalation path to a senior person.
2. What response and resolution times are in the contract?
A promise of “fast support” is not a service level. You need priority levels with definitions, response and resolution targets for each, the hours they apply, and what happens when the provider misses them.
A good answer: A written SLA, for example a critical outage answered within an agreed number of minutes during covered hours, with monthly reporting and service credits or an exit right for repeated misses.
3. Who owns the administrator passwords and documentation?
Your company should own every administrator account, licence and domain, even if the provider manages them. Many disputes start when a provider leaves and the client discovers it cannot log in to its own firewall.
A good answer: Credentials kept in a password vault you control, licences registered to your company, and up-to-date network and system documentation handed to you on request and at exit.
4. How do you prove our backups work?
Backup jobs that report “success” do not prove that a server can be restored. Ask when they last restored a whole machine for a client and how long it took.
A good answer: Scheduled test restores with a short written result, an immutable or offline copy for ransomware, and agreed recovery times per system. How we approach backup and recovery.
5. How do you handle power cuts and generator switch-overs?
Repeated power loss corrupts disks, databases and network equipment. A provider working in Lebanon should treat power as part of the IT design, not as the building’s problem.
A good answer: Correctly sized UPS units with monitoring, automatic graceful shutdown of servers and storage before the batteries run out, and alerts when equipment runs on battery.
6. What happens when the internet goes down?
Cloud email, Microsoft 365 and remote access all stop when the only internet link fails.
A good answer: Two links from different providers where the business needs it, automatic failover on the firewall, and a mobile data backup for small offices.
7. Which security baseline do you apply from the first month?
Most successful attacks exploit basic gaps. A serious provider applies a minimum set of controls immediately, not after an incident.
A good answer: Multi-factor authentication on email and remote access, patching on a schedule, endpoint protection with central monitoring, email filtering, separate administrator accounts and reviewed firewall rules. Our cybersecurity services.
8. Are you independent, or tied to one brand?
A provider paid mainly on hardware or licence margins may recommend what earns it the most. Partnerships are normal; ask how recommendations are made.
A good answer: Two or three options with a 5-year cost comparison, and a clear statement of where the provider earns margin.
9. How do you charge, and in which currency?
Compare the total annual cost, not hourly rates. Clarify what a fixed monthly fee includes, how work outside the scope is billed, and the currency and payment method.
A good answer: A fixed monthly fee per user, device or server with a written list of inclusions, published rates for extra work, and no surprise charges for routine tasks.
10. Can you come on-site, and how quickly?
Most issues are fixed remotely, but some need an engineer in the room: hardware failures, network changes, a dead server on a weekend.
A good answer: Clear on-site response terms by area and time of day, and remote-access tools protected with multi-factor authentication and logged.
11. What do onboarding and exit look like?
The first 60 to 90 days decide the relationship: inventory, documentation, quick security fixes. The exit terms decide how painful a change would be later.
A good answer: A written onboarding plan with an inventory and a risk report, and a contract clause that obliges the provider to hand over everything and assist the transition.
12. Can we speak to clients like us?
Many Lebanese companies prefer not to be named publicly, so a short reference call is more useful than a logo wall.
A good answer: One or two reference calls with organizations of a similar size or sector, arranged with those clients’ permission.
Red flags
- No written service levels, or service levels with no remedy when they are missed.
- The provider keeps your administrator passwords and will not give you access.
- “Backups are fine” without any restore test you can see.
- One person knows everything and nothing is documented.
- Every proposal is a single brand, with no alternative and no cost comparison.
- No multi-factor authentication on email or remote access after the first month.
- No exit or handover clause in the contract.
Contract terms that protect you
| Area | What the contract should state |
|---|---|
| Service levels | Priority definitions, response and resolution targets, covered hours, monthly reporting, remedies for misses |
| Scope | Users, devices, servers, sites and cloud services covered; what is excluded; how extra work is quoted |
| Security | Minimum controls the provider maintains, incident notification time, confidentiality |
| Ownership | Your company owns accounts, licences, domains, data and documentation |
| Backup | What is backed up, retention, how often restores are tested, recovery targets |
| Exit | Notice period, full handover of credentials and documentation, transition assistance |
A simple scoring sheet
Score each shortlisted provider from 1 to 5 on each line, multiply by the weight and compare totals. Adjust the weights to your priorities: a regulated company may give security and backup more weight; a company with several branches may weigh on-site coverage more heavily.
| Criterion | Weight | Provider A | Provider B |
|---|---|---|---|
| Security baseline and proof of working backups | 25% | ||
| Service levels and support coverage, including on-site | 20% | ||
| People: named engineers, skills, continuity | 15% | ||
| Ownership, documentation and exit terms | 15% | ||
| Total annual cost and clarity of pricing | 15% | ||
| References from similar organizations | 10% |
A practical way to decide
- Write down your systems, users and sites, and the outages that hurt most in the past year.
- Shortlist two or three providers and send them the same brief.
- Ask each to start with a short assessment, so you see their work before signing a long contract.
- Score them with the sheet above, check references, and negotiate the contract terms in the table.
About FOXMINDS: we are an IT services and cybersecurity company in New Jdeideh, Beirut, working with organizations in Lebanon and the UAE since 2009. If you would like these twelve questions answered for your company, ask for a managed IT proposal or read about our managed IT services.