Unlike a one-off project, ongoing IT support is a lasting relationship — which makes it all the more important not to compare offers by monthly price alone. Two managed-service offers at a similar price can cover completely different scopes, respond at very different speeds, and cause very different amounts of work if you ever need to switch providers. This guide describes what to clarify before and during the comparison, so the decision doesn't get tested for the first time only after the first major incident.
Define the scope precisely
Managed services can include very different building blocks: a help desk for user requests, remote support, on-site visits, ongoing system monitoring, patch and update management, backup operations, antivirus protection, or support for specific applications. For each offer, clarify individually which of these building blocks are actually included and which would need to be added at extra cost. Also ask about caps: is the number of support tickets per month limited, is there an hour allowance for on-site visits, and what happens once that allowance is used up? An offer with a low monthly price but a narrow scope can turn out more expensive in practice than an offer that looks pricier at first glance but covers more. Also clarify whether the support covers only certain devices and workstations or the entire company network, including servers, printers and mobile devices, so nothing ends up quietly left out. If what you're actually looking for is IT security in the narrower sense — audits, implementing specific protective measures, or an incident-response plan — the guide to commissioning IT security externally is the more precise starting point.
Understand response and resolution time as distinct terms
Offers for IT support frequently use the terms response time and resolution time — and they don't mean the same thing. Response time describes how long it takes before anyone even looks at the problem after it's reported; resolution time (or fix time) describes how long it takes until the problem is actually fixed. A provider can promise a short response time without that automatically implying a short resolution time — so both figures belong separately in a comparison. Also have it explained whether these times are tiered by urgency, for example differently for a total outage versus a minor individual question. This guide deliberately doesn't state specific benchmark figures for appropriate times — what's appropriate depends on how critical your systems are and should be a matter for negotiation, not a number fixed in advance.
Contract term and notice periods
Check the planned minimum contract term, the notice period, and whether the contract renews automatically if it isn't cancelled in time. A long minimum term can mean a better price in return, but it also ties you in even if the relationship turns out not to be a good fit. Also clarify how price adjustments are handled during the term — for example as headcount grows or additional systems are added. For legally relevant contract details, especially around liability and the consequences of termination, it's worth having your legal counsel or appropriately specialized advice review them if in doubt.
Think about handover and exit from the start
Even though the relationship is just starting, it's worth asking how it ends, if it ever needs to. What happens to credentials, administrator rights and documentation if you want to switch providers? Is a structured handover to a new provider supported, and is that already written into the contract or just a verbal promise? A provider who's transparent about this question from the start signals more reliability than one who dodges the topic. Without a regulated exit process, a provider switch can take much longer and cost much more than it needs to. So agree in the original contract on the timeframe within which the handover must be completed after termination, and who bears the effort involved.
Keep documentation current
Agree that IT documentation — system overview, network diagram, software in use, credentials — isn't just created once but kept up to date for the entire contract term. Outdated documentation is worth barely more than none at all when it actually matters. Ask specifically how and how often it's updated, and whether you always have access to it yourself — including so you can hand it over to a different provider.
Availability and escalation
Clarify which channels you can use to report issues — phone, email, a ticketing system, or several in parallel — and during which hours support is actually available. A provider who's officially reachable around the clock but only offers a call center with no technical decision-making authority outside core hours won't help much in an emergency. Also ask about the escalation path: what happens if a reported problem isn't handled within the agreed time — is there a second point of contact, or an automatic escalation to a higher level? Especially for critical systems, it's worth discussing this escalation path concretely up front, rather than testing it for the first time during an actual incident.
Lay the offers side by side
Since managed-service offers can vary widely in scope, timeframes and contract terms, a structured comparison against fixed criteria is worth more than looking at the monthly price alone — the guide to comparing offers describes such an approach in detail. Put your expectations for scope, timeframes and contract term in writing before you send requests; the guide to writing a scope description shows how a complete scope description is structured.
Checklist
- Scope broken down concretely per offer, including caps
- Response time and resolution time understood and compared as separate terms
- Contract term, notice period and renewal terms checked
- Handover and exit process clarified before signing
- Documentation updates during the term agreed
- Availability, support channels and escalation path concretely clarified
If you want to source ongoing IT support or managed services, you can describe your needs on Projektlotse — with the desired scope and the points from this guide. Verified IT providers in your region see the request and get in touch with questions and offers. Your company name, exact address and attachments stay confidential until you release them to individual providers. Use is free during the current start phase.