A Guide to Choosing an IT Service Provider

The choice of IT service provider is often made based on the cheapest quote or the first recommendation from someone you know. Both can work out - but neither is a reliable criterion. A more systematic approach significantly reduces the risk of an expensive wrong decision.

First: define your own needs clearly

Before even requesting quotes, it's worth asking honestly: what exactly is needed? Plain support for faults, ongoing care under managed services, consulting for a planned cloud migration, or targeted support for IT security and compliance - the more concretely the requirement is defined, the more precisely you can select afterward, and the more comparable the quotes you receive will be.

Security and data protection as a selection criterion

An IT service provider typically gets far-reaching access to a customer's systems and data. That's why questions about security and data protection belong in the selection from the start: how does the provider secure its own systems? Is it prepared for GDPR requirements? Germany's NIS2 implementation act raises the stakes further: even for businesses not directly covered by NIS2 themselves, the IT security of their suppliers and service providers is increasingly becoming a hard selection criterion within their own supply chain.

Regional proximity matters - but not for everything

For many SMEs, a local provider is helpful, especially for hardware deployments, network work, or when someone needs to be available in person quickly in an emergency. For pure consulting or cloud topics, distance matters less. It's worth clarifying for yourself where personal presence actually matters - and where it doesn't.

Warning signs worth watching for

Some signs, based on experience, tend to point to problems later on:

• Missing documentation of systems, passwords, and configurations.
• Purely reactive work without monitoring or proactive maintenance.
• Untested backups - a backup log alone says nothing about a working restore.
• Quotes with no security or maintenance component, focused purely on the hourly rate.
• Vague response times without concrete, contractually fixed commitments.

Ten questions for the selection conversation

These questions help make different providers' answers comparable:

1. What's included in the base price, and what's billed separately?
2. What are the contractually guaranteed response and recovery times, specifically?
3. How is the security of their own systems and of customer data ensured?
4. How and how often are backups tested - not just performed?
5. What does day-to-day collaboration look like - fixed contacts or a rotating ticket system?
6. How transparent is billing, and what additional costs can arise during a project?
7. How does the provider handle systems that weren't set up by them?
8. What documentation is created during the engagement, and who owns it in the end?
9. How scalable is the collaboration as the business grows or changes?
10. What exactly happens when the collaboration ends - handover of access, documentation, and systems?

Plan for a trial period

Rather than committing long-term right away, a manageable trial period - around three months - is worthwhile: response times, communication, and reliability are easier to judge in practice than in a sales conversation.

Checklist

• Have you clearly defined your own needs before requesting quotes?
• Are security and data protection questions part of the selection?
• Have you checked regional proximity where it's actually relevant?
• Have you asked for references from a comparable industry or size?
• Are response times contractually guaranteed, not just verbal?
• Have you agreed on a trial period instead of an immediate long-term commitment?

Practical example: An IT handover starts with the right questions

Illustrative scenario, not a documented customer case study.

Starting point: A company wants to change its IT provider. It has a device list and current invoices, but no consolidated overview of access, contracts, and responsibilities.

Problem identified: During preparation, it is unclear who manages the domain contract and which administrator accounts are available to the company. An immediate switch would carry these unresolved dependencies forward.

Action: Before the handover, the team records contract partners, contacts, and required permissions. With the company’s authorisation, it requests missing information, checks transferred access, and agrees a switching date.

How to verify the result: A handover checklist identifies the responsible contact, verified access, and outstanding tasks for each important system. The customer can see which prerequisites are met and which work remains.

Your next step: Ask about the handover process and documentation of outstanding issues during your selection meeting. Our switching IT providers page explains the proposed process.

Conclusion

The cheapest hourly rate is rarely the decisive criterion - processes, documentation, security, and communication say much more about how the collaboration will actually go. As a vendor-neutral IT company, we advise you through our IT Consulting independent of any single vendor's interests. Get in touch via our contact page if you want to put your current IT support to the test.