// Guide · Selection
Choosing an IT service provider: what decides the outcome
A selection process that works without an in-house IT department — the sequence, the criteria, the warning signs, and the questions that make two providers genuinely comparable.
// Starting point
Why the search so often goes wrong
Nobody goes looking in calm conditions. There is usually a trigger: the person who used to handle things has retired, an outage hurt, or the company has grown past the point where IT can run on goodwill. Quotes collected under that kind of pressure end up being compared as numbers, even though each number describes a different amount of work.
Turning the order around helps. Decide first which tasks you want to hand over, then ask providers how they would cover them. If you are unsure where the boundaries of such a mandate normally sit, our overview of IT services lays out the usual fields — daily operations, security, cabling in the building.
The second recurring mistake is fixating on an address. For companies in Düsseldorf and across the Rhine-Ruhr region, travel time is what matters. We work from Monheim am Rhein for the surrounding region, which puts Düsseldorf, Cologne and Leverkusen within easy reach; what that means day to day is described on our home page.
// Sequence
Four steps to a decision you can defend
The effort sits at the front. Skip step one and you pay for it later, usually in a discussion about what was included.
Write down what you need
Note who currently does what, what quietly never gets done, and which failure would cost you most. That note is your tender document — it does not need to be polished, only complete.
Narrow the field early
A recommendation from a company like yours beats a search result. Check early whether a firm knows your size and your sector, rather than counting the logos on a reference page.
Examine two or three properly
Ask them to explain your environment back to you, not their portfolio. Anyone who spends two hours on site without a single question about your setup has not really looked.
Settle contract and handover
Scope, availability, documentation and exit belong in writing. Treat the first weeks as a takeover phase with its own plan, not as business as usual.
// Criteria
Six points that make the difference
Most things can be renegotiated later. These six decide whether the arrangement still works in its third year.
-
Reachability with a named deputy
One familiar contact is good; a documented stand-in is better. Ask what happens to your account when that person is away for a fortnight.
-
Depth of service under one roof
The more trades a firm owns itself — network, servers, workstations, backup — the less often a fault turns into an argument about responsibility.
-
On-site response when remote is not enough
Plenty can be fixed over a remote session; broken hardware cannot. Clarify where a call-out starts from and how quickly that can be arranged.
-
Documentation that belongs to you
Network diagrams, asset lists and credentials must be available to you on request. Knowledge that exists only at the provider is a dependency, whatever the contract says.
-
Invoices you can read
You should be able to see what was worked on. Flat fees are fine as long as it is clear what they cover and what sits outside them.
-
An exit that is written down
A provider who documents how a handover to a successor works does not need to hold customers through dependency. That clause tells you a lot about the rest.
// Reading the room
What the first meeting reveals
Both lists describe patterns you can spot in conversation, long before anything is signed.
Worth pressing on
- Products appear in the proposal before anyone has seen the environment
- Questions about documentation are answered with a reference to internal systems
- Response times are promised verbally but never written down
- The question of how a contract ends gets no clear answer
Someone actually looked
- Questions about how you work, not just how many devices you own
- A proposed order of work instead of a single sweeping replacement
- A straight answer about what the firm does not do in-house
- The inventory is planned in as the first piece of work
// First meeting
Eight questions that create clarity
Take the list with you. The point is not to catch anyone out, but to make two proposals describe the same thing.
- Who exactly looks after us, and who covers for that person?
- How do we report a fault outside office hours, and what happens next?
- What does the monthly fee include, and what is billed separately?
- How do you document our environment, and how do we get those records?
- Who owns the licences, contracts and administrator accounts?
- Which work do you carry out yourselves, and what goes to subcontractors?
- What does the takeover plan for the first weeks look like?
- What happens to our data and access if we give notice?
// Common questions
What companies ask before they choose
01 Does the provider have to sit in Düsseldorf itself?
What counts is how long an engineer needs to reach your building, not the postcode on the letterhead. A firm on the edge of the region that arrives within the hour is worth more than a Düsseldorf address whose technicians travel in from somewhere else entirely. Ask about the actual dispatch plan instead of the billing address.
02 How many providers should we put on the shortlist?
Two or three, examined properly. Once you invite five, the attention you can give each one drops until price becomes the tie-breaker by default — and price tells you nothing while the scope of work still differs between the offers.
03 How do we tell whether a firm is too small or too large for us?
Too small shows up when a single holiday leaves nobody able to cover, because the knowledge lives in one head. Too large shows up when you are routed through a queue and repeat your situation from scratch at every call. Both are easy to test: ask who looks after you, and who steps in for that person.
04 Should everything go to one provider?
Not necessarily, but every additional company creates a seam where an outage turns into a discussion about who owns the problem. When network, servers and workstations sit with one team, that discussion never starts. Specialist software is often better left with the vendor who built it.
05 What belongs in the contract?
The scope of work with its boundaries, how and when you can reach someone including response commitments, the rules on documentation and administrator accounts, plus term and notice periods. Add a clause covering what gets handed over if you ever move on.
06 How long does switching providers realistically take?
Plan for several weeks between signature and settled operation. That time goes into the inventory, transferring accounts, setting up monitoring and working through the first list of findings — not into the technology itself.
Read on
All guides
Already in the middle of a selection process?
Use us as your comparison quote. We look at the environment, name what stands out to us — and say so plainly if the route you are already on is the right one.