01
Response time and the service agreement
What it is. The service agreement, or SLA, states in writing how fast the provider picks up your call, how fast the work starts, and what counts as an emergency.
Why it matters. Without a written definition, a promise to answer quickly means nothing. A cash register frozen on a Friday afternoon and a flickering screen should not carry the same priority.
The question to ask. “Show me your priority levels and the response time you commit to for each one.”
Red flag. A response time promised out loud that the provider will not write into the agreement.
02
Local presence and on-site service
What it is. The ability to send someone to your site when a problem cannot be solved remotely, and how often they visit when nothing is broken.
Why it matters. A dead server, a burned-out switch or an office move are not fixed from a keyboard. The real distance between the provider and you decides what happens that day.
The question to ask. “Where does the person who would come to our site start from, and how many clients do you already have in our region?”
Red flag. A long list of cities on a website, without a single client or a single person on the ground.
03
Service in your language
What it is. Being able to speak, write and read your reports in English or in French, from the first call through to the technical documentation.
Why it matters. Your employees describe a problem in their own words. A service desk that answers in one language only makes every exchange longer and loses information along the way.
The question to ask. “Do the person who answers the phone, the person who writes the reports and the person who travels all work in our language?”
Red flag. Phone service in your language, but a portal, reports and alerts in another one.
04
Partner status and verifiable certifications
What it is. Official partnerships with software vendors, Microsoft first among them, and certificates you can check yourself at the source.
Why it matters. A partnership opens the door to vendor support when a problem goes beyond the provider. A logo pasted on a website proves nothing on its own.
The question to ask. “Under exactly what name are you registered with Microsoft, and where can I check it myself?”
Red flag. Partner logos with no registered name, or a partnership level announced on the site that matches nothing public.
05
Law 25 compliance and where your data lives
What it is. What the provider actually does about the protection of personal information: access management, encryption, logging, an incident register, and the country where your data and your backups are hosted.
Why it matters. In front of the Commission d’accès à l’information, the responsibility stays yours. A provider who cannot answer leaves you carrying the risk alone.
The question to ask. “In what country are our data and our backups hosted, and what exactly do you do the day a privacy incident happens?”
Red flag. A generic answer along the lines of “we are compliant”, without naming a single measure or a single document.
06
Cybersecurity included in the service
What it is. Protection for workstations and servers, multi-factor authentication, email filtering and alert monitoring, included in the package rather than sold on the side.
Why it matters. Protection billed as an extra often ends up never being turned on. And a security tool nobody watches protects nobody.
The question to ask. “Who looks at the security alerts, at what hours, and what happens when an alert fires at 2 a.m.?”
Red flag. An antivirus presented as complete cybersecurity, with no monitoring and no incident response.
07
Backup and disaster recovery that are actually tested
What it is. Copies of your data taken automatically, kept somewhere other than your own servers, and above all restored for real at regular intervals.
Why it matters. A backup that has never been restored is not a backup, it is an assumption. Most bad surprises show up on the day of the restore.
The question to ask. “When did you last run a restore test at a client, and can you show me the report?”
Red flag. A provider who talks about Microsoft 365 data as if backup were already included in the Microsoft subscription.
08
A contract and an invoice you can read
What it is. Knowing what the monthly amount covers, what is billed on top, how the amount moves when you hire someone, and how the agreement ends.
Why it matters. Bad relationships with a provider almost always start with a surprise invoice or with an exit clause nobody had read.
The question to ask. “Give me three examples of work that is not covered by the package, and tell me the minimum term.”
Red flag. A long term, automatic renewal and an exit penalty, presented as a simple formality.
09
Verifiable client reviews and references
What it is. Public reviews attached to real names, and current clients you can call before you sign.
Why it matters. A public rating puts the provider’s reputation on the line. An anonymous testimonial on a web page commits nobody.
The question to ask. “Can you give me two clients my size, in my sector, that I can call this week?”
Red flag. No public review profile at all, or references that go back several years.
10
Strategic guidance and the IT master plan
What it is. Someone who looks at your IT over three years: master plan, budget, equipment replacement, security priorities. That is the IT director role, rented part time, usually called a vCIO.
Why it matters. Without that role, you pay to put out fires and the same fires come back. It is also what lets you plan spending instead of absorbing it.
The question to ask. “How often do you meet us when nothing is broken, and what does a master plan you have already delivered look like?”
Red flag. No meeting on the calendar outside of emergencies.
11
The provider’s tooling and who owns your documentation
What it is. The tools the provider uses to run your environment: monitoring, tickets, passwords, documentation. And what belongs to you in all of that.
Why it matters. The day you change providers, the quality of the documentation decides whether the transition takes two weeks or six months. A provider that builds its own tools can also fix a problem without waiting in a vendor’s queue.
The question to ask. “If we left in a year, what exactly do we receive, in what format, and how fast?”
Red flag. Documentation that lives in one technician’s head, or a refusal to hand back administrative credentials.
12
The ability to support automation and artificial intelligence
What it is. The provider’s ability to go past break-fix: automating repetitive tasks, framing how artificial intelligence tools get used, and building a small tool when nothing on the market does the job.
Why it matters. Your employees already use artificial intelligence tools, with or without guardrails. And a lot of the time lost in a small business goes to manual tasks nobody has taken the time to automate.
The question to ask. “Have you already automated a process at a client, and how do you frame the use of artificial intelligence with company data?”
Red flag. Talk about artificial intelligence without a single example delivered at a client.