How to compare a managed IT contract in 2026

To compare managed IT contracts, you first have to bring them to the same scope: two monthly fees are only comparable if you know precisely what each one includes, with which committed response times and which exit conditions. This article reviews the six clauses that make the real difference between two offers, the three pricing models used in Switzerland, and the red flags that should make you walk away.

Why two managed IT offers are never comparable as they stand

"Complete managed IT", "unlimited support", "24/7 monitoring": the same words cover very different realities from one provider to another. One includes off-site backup in its fee, the other bills it as an option. One commits to a 4-business-hour response, the other "does its best". One operates from French-speaking Switzerland, the other subcontracts its helpdesk abroad.

Comparing prices without comparing contracts therefore means comparing different things. If you are still at the stage of choosing the provider itself (reputation, local presence, references), start with our guide on how to choose your IT provider in Switzerland; if you want to understand what managed services should cover, read our article on managed IT services for SMEs. Here, we focus on the contract.

The 6 clauses to examine before signing

1. The exact scope: included and excluded

The contract must precisely list the equipment covered (workstations, servers, network equipment, printers), the supported software, the sites concerned and the number of users. Beware of vaguely defined scopes ("the company's IT infrastructure"): in the event of a dispute, you will have no recourse. Above all, check the list of exclusions, often relegated to an appendix: projects (migrations, office moves), on-site interventions, user training or disaster recovery are frequently billed on top.

2. SLAs and response times

This is the heart of the contract. A serious SLA defines criticality levels (critical, major, minor) with, for each, a response time quantified in business hours, the support coverage hours, and ideally penalties if commitments are not met. Also ask how SLA compliance is measured and reported: a provider that sends you a monthly report with its actual response times has nothing to hide.

3. Hosting and data location

The contract must specify where your data, your backups and the provider's tools (monitoring, ticketing, remote access) are hosted, and list its subcontractors. Since the revised Swiss Data Protection Act (FADP), this is a compliance requirement as much as a technical choice: your provider is a processor within the meaning of the law. If you are unsure about your own obligations, an FADP audit quickly clarifies your situation.

4. Reversibility and the exit clause

The most often neglected clause, and the most expensive one when it is missing. It must guarantee the return of your data and documentation (administrator passwords, network diagram, inventory), a handover period, and transition assistance to the next provider. A provider that refuses to commit on reversibility plans to keep you through constraint rather than quality.

5. Price revision

Check the indexation conditions: is the annual increase capped or unrestricted? What happens if your headcount decreases, does the fee adjust downwards? Contracts that only adjust in one direction deserve to be renegotiated before signing.

6. Subcontracting

The contract must state whether the provider can subcontract all or part of the service, to whom, and whether you must be informed. A helpdesk subcontracted abroad is not necessarily a problem, but you should know before signing, not discover it on the first call.

The three pricing models

• The fee per workstation or per user (CHF 40 to 150 per workstation per month depending on scope): the most common and most predictable model. The provider has an incentive to prevent incidents, since each intervention costs it money. This is the right model for most SMEs.
• The prepaid block of hours: you buy a credit of hours consumed as requests come in. Flexible for very small structures, but with no proactive monitoring: nobody watches your backups between two tickets.
• Time and materials (billing by time spent): suited to one-off projects, not to day-to-day operations. On time and materials, the provider earns more when you have more problems; the incentive is inverted.

The comparison checklist

Before putting two offers side by side, check for each one:

• The precise list of equipment and software covered, and the exclusions
• Quantified response times per criticality level, and coverage hours
• What is included in the fee: backups, EDR, firewall, MFA, Microsoft 365 management
• The location of your data, backups and the provider's tools
• The commitment period, notice period and exit clause
• The price revision conditions, both upwards and downwards
• The list of subcontractors and the support language
• A real example of a monthly report

The red flags

Some signs should make you discard an offer, whatever its price: the absence of a written SLA, a scope defined in one sentence, refusal to provide verifiable client references, inability to say where your data is hosted, disproportionate exit penalties, or a quote well below the market with no structural explanation. A provider that promises everything, immediately, without ever saying "no" or "that's out of scope", is mostly telling you what you want to hear.

Put the offers to the test

Once two or three offers are shortlisted, ask each provider to price the same concrete scenario. The answers, their precision and their honesty will teach you more than any sales brochure. For work that goes beyond day-to-day operations (migration, network redesign), also make sure the provider can run structured IT projects.

At AlpenData, we built AlpenCare to stand up to comparison on each of these points: a documented SLA with quantified response times, a scope listed equipment by equipment, data operated primarily on Swiss infrastructure and an exit clause included. We are happy to answer the checklist above, in writing.

Frequently asked questions

What commitment period is reasonable for a managed IT contract?

An initial term of 6 to 12 months is reasonable: setting up managed services requires several weeks of investment from the provider, so a very short commitment is not realistic. Beyond 24 months, be cautious, especially if early-exit penalties are high. After the initial term, prefer a short renewal cycle, ideally monthly: it is the sign of a provider that intends to keep you through quality.

What is a good SLA for a Swiss SME?

A good SLA defines criticality levels with quantified response times: for example, a critical incident (production stopped) handled within 1 to 4 business hours, a major incident within 4 to 8 hours, a standard request within 1 to 2 days. It also specifies support coverage hours and what happens outside them. 'We are very responsive' is not an SLA.

What should an exit clause (reversibility) contain?

It must guarantee the return of all your data and documentation in a usable format (exports, administrator passwords, network diagram, asset inventory), a defined handover period, transition assistance to the new provider, and the cost of that assistance if any. Without a written exit clause, changing providers becomes slow, expensive and contentious.

Should you require data hosting in Switzerland?

For sensitive personal data and regulated sectors (healthcare, legal, fiduciary), hosting in Switzerland is strongly recommended: it simplifies FADP compliance and avoids exposure to the US CLOUD Act. For other data, require at minimum to know precisely where it is stored and which subcontractors have access to it.

How do you compare two managed IT offers with very different prices?

Bring both offers to the same scope before comparing prices: list what is included in the monthly fee (backups, EDR, firewall, unlimited support or not) and what is billed extra. A large price gap is almost always explained by a reduced scope, offshore support or the absence of committed response times, rarely by better efficiency.