1. What we mean by a managed IT services provider
A managed IT services provider, often referred to by the acronym MSP (Managed Service Provider), looks after part of your company's IT infrastructure on an ongoing basis: workstations, servers, network, email, security, backup and user support. It does not work only when something breaks. Its task is to keep systems running and to reduce problems before they become production outages or incidents.
The practical difference from an engineer called out to fix a problem is this: with a callout you pay for the work of that moment, whereas with a managed service you buy responsibility for a defined scope. For this reason the choice is not only technical. The provider becomes part of your operations, knows your configurations, may hold administrative access and keeps information about your organisation. Changing it later costs time and effort, so it is worth deciding carefully from the outset.
2. Before you look: define the need
The most common mistake is asking for quotes without knowing what you want. The provider replies with a generic price list and you cannot compare anything. Before writing to anyone, prepare a short but concrete description of how the company works today. You do not need a perfect document: you need a common basis that allows two different providers to answer the same question.
Gather at least the following information and keep it on a single page. With these basics you can already separate essential requests from accessory ones. A qualitative indication of budget also helps, provided it is realistic: state whether you are looking for a basic service or a complete presence, and let the provider propose how to cover the gaps. A provider that listens to this request will help you see where the need is real and where it is only a habit to review.
- Systems and applications in use, including those in the cloud or managed by others
- Data processed and the places where it is stored
- Times when work cannot be interrupted
- Recurring problems that currently block people
- Known legal obligations, for example regarding data protection
3. Service models on the market
There are several models of collaboration, and not all of them suit every company. The first step is to understand which one you need, because comparing offers based on different models leads to wrong conclusions. A monthly fee that looks high may cost less than many callouts a month, and a pay-as-you-go service may look cheap until production stops. A proper comparison only arises when you put the cost and the risk that each model leaves with you side by side.
| Model | How it works | Suitable when | Weak point |
|---|---|---|---|
| Break-fix | Work is paid for when needed, on request | Problems are rare and not critical | Priority, response times and prevention are not guaranteed |
| Fully managed, fixed fee | A defined scope is managed on an ongoing basis | You want a single point of contact and predictable costs | If the scope is vague, out-of-scope requests become extra costs |
| Co-managed | Internal staff work alongside the provider, with divided roles | You already have an internal IT person to support | Without clear roles, gaps and duplication appear |
| Domain specialist | Covers a specific area, for example backup or security | You already have a generalist provider and a targeted gap | More suppliers to coordinate and fragmented responsibilities |
4. Evaluation criteria that really matter
Brochures often list the same certifications and the same buzzwords. To distinguish a serious provider from a generic one, look at how it actually works. Ask to see the process for taking on a request, how priorities are assigned and who decides when a problem should be escalated. A prepared provider answers with precise examples, not slogans.
Assess at least these aspects. There is no universal score: weight each criterion according to the risk you face. If your data is sensitive, transparency about access weighs more than response speed. Note the answers in a simple table, so the comparison stays objective and you can explain the choice to management or partners. The document is useful even if you change your mind midway, because it shows the basis on which you decided.
- Experience with your real systems, not only generic ones
- A clear process for requests, priorities and escalation
- Transparency about who accesses your data and with what permissions
- Ability to manage security, backup and recovery
- Contractual clarity on scope, responsibilities and exit
- Verifiable references in sectors close to yours
5. The questions to ask the provider
The right questions bring out the difference between promises and practice. You do not need a long interview: a few precise questions are worth more than an endless list. Always ask for written answers and compare the answers from different providers to the same questions. If an answer is evasive, that is not a fault in itself: it is a signal to explore further before signing. Ask for the answer in writing, so the information remains available after the negotiation.
- Who will be the technical contact after signing, and who replaces them when they are absent?
- Which systems are included in the fee and which remain outside?
- How are administrative access rights managed, and who approves them?
- Where is the data stored and which parties can access it under the applicable law?
- How are backups tested, and when was the last test restore carried out?
- Which reports will I receive and how often?
- What happens to data and documentation if I decide to change provider?
6. Warning signs in offers
Some signals often appear in weak offers and it is worth recognising them immediately. A price much lower than the others, without a written scope, is the first: it often means the exclusions are hidden in the general terms. Another is the absence of any reference to backup, recovery and security, as if these were minor details. A serious offer treats these topics as a central part of the service, not as an appendix.
If you spot one of these signals, do not close the negotiation: ask for a written clarification. A reliable provider gives it without difficulty, and its answer will tell you more than the sales material. The time taken to respond is also an indicator. If the proposal arrives late and without a clear contact, the subsequent relationship is unlikely to be any more orderly. Assess the quality of the first exchange as well as the content of the offer.
- Very low price with no precise list of what is included
- No mention of backup, recovery or access management
- Vague answers about where data resides and who can access it
- Request for full administrative credentials without limits or logging
- No reports, no indicators and no periodic review planned
7. How to compare offers properly
Offers cannot be compared if they describe different services. Before putting two proposals side by side, check that they cover the same systems, the same support hours, the same responsibilities and the same level of security. A common document, with a realistic scenario from your company, makes the comparison simpler and more honest. Without this shared basis, each provider answers a different question and the comparison becomes difficult.
Send the same description to all providers and ask for a structured response. If possible, talk to the technical manager who will handle your case, not only to the salesperson. Compare the risks that each offer leaves uncovered, not just the monthly cost. For the formal request stage, the guide on writing a request for proposal explains how to structure the document.
8. The deep dives to read, in order
This guide covers the choice of provider. The decisions that follow require specific deep dives, which answer more operational questions. Read them in the following order, because each assumes the previous one is clear. You do not have to read them all at once: choose the one that matches the stage you are at, starting from the first if you still need to define the scope. Each deep dive refers back to concepts already explained in the earlier ones, so skipping one increases the risk of misunderstanding.
- What a managed IT service includes, with scope, exclusions and grey areas
- How to design realistic service levels, meaning SLAs
- The clauses to check in the support contract
- Pricing models: fixed fee, consumption or hours
- In-house or outsourced IT: how to decide
- The indicators and reports to demand from the provider
- How to write a request for proposal for IT services
- Handover and exit from a provider
9. How to start
The first concrete step requires a few hours and no purchase. This week, prepare the needs definition page described in section two: systems, data, critical times, recurring problems and known obligations. Share it with the person in the company who decides on IT and with those who really know the processes. A shared reading prevents the choice from depending on a single person or a single impression.
Then choose a small group of providers to contact and ask all of them for a written reply to the same description, with the questions from section five. Compare the answers before discussing price. A provider that has understood your need will propose a clear scope, and the choice will become much simpler. Keep the answers you receive, because you will need them at the time of decision and at the later review.
Frequently Asked Questions
Is an MSP the same thing as a local computer technician?
Not necessarily. A local technician can be very good, but often works on a callout basis and does not have a structure that guarantees continuity, cover during absences and shared documentation. A well-organised MSP has processes for taking on requests, monitoring tools and several people trained on your systems. What to verify is not the legal form, but how the provider guarantees the service when the main contact is unavailable.
Must I entrust all my IT to a single provider?
It is not mandatory. Entrusting everything to one party simplifies responsibilities but creates a stronger dependency. A common arrangement is to entrust the general service to one provider and specialist skills, such as security or backup, to another. In every case you need a clear map of who does what, otherwise the boundaries between the two overlap precisely at the critical moments.
Does a European provider automatically guarantee data protection?
No, these are two separate questions. Where data is stored and who can legally access it depend on the structure of the service, the subcontractors and the laws to which they are subject. Ask the provider for a list of the subcontractors that handle data, the storage location and the access arrangements. Then verify with your adviser that the processing complies with the GDPR and that the processor appointment contract matches the service.
Is the lowest price the right criterion?
Price matters, but it is not the main criterion. A cheaper offer may exclude activities that later emerge as extras, or may reduce the number of competent people dedicated to your case. Always compare the same scope, the same responsibilities and the same guarantees, and then assess the cost. A reasonable price for a clear service is often better value than a low price for an uncertain one.
How long does it take to choose a new provider?
It depends on the complexity of the infrastructure and on how quickly the company makes decisions. A well-prepared process, with a written need and a structured comparison, is faster than an improvised one. Do not rush to sign: the choice of provider affects years of operations, and a few extra weeks of comparison cost far less than a wrong contract.
Do I need a written contract even for occasional support?
Yes, even if the service is small. A written agreement defines at least who intervenes, with what permissions, on which systems, within what indicative timeframes and how data is handled. Occasional support without written terms often becomes the starting point of a relationship that nobody has ever governed. The contract can be simple, but it must exist.
What should I ask a provider before signing?
Ask for the list of included and excluded services, the name of the technical contact, the support and escalation arrangements, the reports you will receive and the exit conditions. Also ask who accesses your data and with what permissions, and how backups are handled. The answers should be in writing and attached to or referenced in the contract, so you have a reference in case of dispute.