Skip to main content

Insights

Choosing an IT provider in Luxembourg: ten questions to ask

Before you sign, put the same ten questions to every provider: who does the work, in which language, on site or remotely, with which access rights, what documentation, how data is protected, and how the relationship starts and ends. Answers are easier to compare than brochures.

Published on By Smart ITReading 7 minutes

Organisational byline. Prepared with AI tools; every cited fact is automatically checked against its source.

Luxembourg City at dusk, looking over the rooftops of the Grund.

An IT support provider, and even more so a managed IT services provider that runs part or all of your IT on an ongoing basis, will have access to your accounts, your data and your everyday tools. The choice therefore depends less on a list of technologies than on how the provider is organised. The ten questions below make those organisations comparable. They apply whichever provider you are considering.

For each question, you will find why it matters, what a reassuring answer contains and what should raise a flag. A reassuring answer is rarely a promise: it is a precise explanation that the provider is willing to put in writing.

The ten questions

1. Who will actually do the work, and who covers when they are away?

  • Why it matters: service quality depends on the people who know your environment. Knowledge held by a single person becomes a risk during holidays or after a departure.
  • Reassuring answer: a named contact, one or more people able to stand in, and a shared record that lets another technician pick up a request without starting from scratch.
  • Red flag: "you will always deal with the same person", with no explanation of what happens when that person is unavailable.

2. In which languages are support and documentation provided?

  • Why it matters: in a team that works in English, French, German or Luxembourgish, a request that is misunderstood is handled badly. The language of written documentation matters as much as the language spoken on the phone.
  • Reassuring answer: working languages stated for phone support, written exchanges and documentation, matching the actual make-up of your teams.
  • Red flag: a vague "we adapt" with no indication of who speaks which language, or documentation available only in a language half your staff cannot read.

3. What is handled remotely, and what requires a site visit?

  • Why it matters: many requests can be resolved remotely, but cabling, a laptop replacement or a jammed printer need someone on site. The split also affects the budget.
  • Reassuring answer: a clear division between remote and on-site work, how a visit is decided and whether it is included or billed separately.
  • Red flag: site visits described as always available, with no written conditions, or a remote-only service when you have equipment on your premises.

4. How is a request handled, from first report to closure?

  • Why it matters: without a defined process, requests get lost between an email, a call and a personal message to the technician.
  • Reassuring answer: one or two reporting channels, tracking of every request (for example in a ticketing tool, a log of requests and their status), explained prioritisation and closure confirmed with the user.
  • Red flag: no request history you can consult, or response times promised verbally but missing from the written proposal.

Commitments on response times, availability and scope belong in the contract. They are covered in the clauses to check in a managed IT contract.

5. Who holds the administrator accounts?

  • Why it matters: administrator accounts give full control over email, servers, the firewall or the domain name. If your company does not hold them, it depends on the provider for every decision, including the decision to change provider.
  • Reassuring answer: your company remains the holder of subscriptions, the domain name and at least one emergency administrator account kept under its own control. The provider works with named accounts, and its access can be withdrawn.
  • Red flag: subscriptions or a domain name registered in the provider's name, a shared administrator account nobody in your company knows about, or a refusal to hand over access.

6. What documentation is provided, and when?

  • Why it matters: documentation (hardware inventory, network diagram, list of licences and renewal dates, procedures) lets another person understand your set-up.
  • Reassuring answer: a list of documents kept up to date, a storage location your company can access, and handover planned at the start and at regular intervals.
  • Red flag: documentation "available on request" with no defined content, or kept only in the provider's own systems.

7. How is data protected, and who else has access to it?

A provider that accesses personal data on your behalf generally acts as a processor under the General Data Protection Regulation (GDPR). Article 28 of the GDPR states that "the controller shall use only processors providing sufficient guarantees". It adds that processing by a processor is governed by a contract or other legal act, and that the processor shall not engage another processor without prior specific or general written authorisation of the controller.

  • Why it matters: your company remains responsible for its customers' and employees' data, even when a third party handles it.
  • Reassuring answer: a data processing agreement offered with the contract, the list of other providers involved (hosting, backup, remote access tool), where data is stored, and security measures explained in plain terms.
  • Red flag: no document on data protection, or third-party tools you only discover after signing.

8. How does onboarding of your existing set-up work?

  • Why it matters: the first weeks are a vulnerable period. Access is transferred, passwords are changed, tools are replaced.
  • Reassuring answer: a step-by-step method, with an inventory of access and equipment, backups checked before any change, and a schedule agreed with you and, where possible, with the current provider.
  • Red flag: a plan to replace everything before the existing set-up has been reviewed, or nothing said about what happens if the outgoing provider is slow to hand over information.

9. How does the contract end?

  • Why it matters: the exit is easiest to negotiate at signing. A poorly prepared end of contract can lock you out of your own tools.
  • Reassuring answer: notice period and term in writing, return of access and documentation, the support offered to the next provider and how it is billed.
  • Red flag: automatic renewal without reminder, exit fees that are not itemised, or a handover that will be "looked at when the time comes".

For personal data, Article 28 provides that the processor, at the choice of the controller, "deletes or returns all the personal data to the controller after the end of the provision of services relating to processing". It is worth asking how this step is organised in practice.

10. Does the company legally exist, and does it hold the required permits?

You can check this before the first meeting. According to Guichet.lu, the Luxembourg Trade and Companies Register (RCS) is a public register and can be freely accessed; it is managed by Luxembourg Business Registers (LBR). You search it on the LBR website.

Guichet.lu also states that, apart from a few exceptions, any economic activity carried out on a regular basis is subject to the prior granting of a business permit, and that a search tool lets you check whether a company holds one.

  • Reassuring answer: the same company name, RCS number and address on the proposal, the invoices and the register.
  • Red flag: a company you cannot find in the register, a different name on the contract, or reluctance to share these details.

A grid to compare the answers

Ask every provider the same questions and record the answers in one grid. What counts is not the most ambitious answer, but the one that appears in the written proposal.

What to get in writing before you sign
QuestionGet in writing
PeopleMain contact, stand-ins, access to the technical record
LanguagesLanguages for support, written exchanges and documentation
On site or remoteSplit of work, conditions and billing of site visits
Request handlingReporting channels, request tracking, prioritisation
Administrator accountsHolder of subscriptions and domain, your emergency access
DocumentationList of documents, storage location, update frequency
DataData processing agreement, other providers involved, data location
OnboardingSteps, schedule, backups checked before changes
End of contractNotice, return of access and data, transition support
Legal existenceCompany name, RCS number, business permit

Illustrative example: two providers both offer a "dedicated contact". The first names two stand-ins in its proposal and the tool where all work is logged. The second does not put this in writing. At a comparable price, the first leaves you less dependent on a single person.

Price comes next, once proposals are comparable. What drives it is covered in the cost of an IT maintenance contract.

Frequently asked questions

In short

A sound choice depends less on the list of services than on precise answers about people, access, documentation, data and exit. Anything missing from the written proposal should carry no weight in the decision. Smart IT's services in this area are described on the managed IT support page. If you would first like to describe your situation, the free audit can be a starting point.

Prepare your questions with an outside view

The free audit is a 45-minute remote conversation, with no commitment, followed by a written summary. It helps you describe your situation before you approach providers.

Request a free audit