Buying IT Services

Questions to ask an MSP before you sign

Clod Feijao

· 6 min read

Signing with a managed services provider is a bigger decision than it looks on paper. Even when the contract is short, the provider ends up with the keys to your systems, knowledge of how your business runs, and a hand in every new hire's first day. Changing later is possible, but it costs time and attention.

So it is worth asking hard questions before you sign. These are the ones I would ask if I were on your side of the table. A good provider will answer them plainly. Pay attention to the ones that get vague answers.

Response and support

What are your response commitments, and how are priorities defined?

Ask for response targets by priority, in writing, and then ask what each priority means. A "critical" issue at one provider might be the whole office being down; at another it might be one person who cannot print. Also ask about the difference between response and resolution. A fast acknowledgement is not the same as a fix.

What are your support hours, and what happens outside them?

Many providers support business hours, which suits most organizations. If you need help on evenings or weekends, ask whether it is available, how it is billed and who actually answers. Be wary of round-the-clock promises that turn out to mean an automated alert with nobody reading it.

How do my staff ask for help?

Phone, email, a portal, chat? Can staff reach a person, or only fill in a form? The easier it is to ask, the more likely small problems are caught early.

Scope and exclusions

What is not included?

This is the most important question on the list. Every agreement has exclusions. Common ones are projects, new office setups, hardware, software licences, on-site visits, after-hours work and support for specialized line-of-business applications. None of these are unreasonable to exclude. What matters is that you know before the first invoice, not after.

How do you handle work that is out of scope?

Ask how it is priced, who approves it, and whether you will be told before out-of-scope work starts. You should never discover a project for the first time on an invoice.

When do you come on site?

Plenty of work can be done remotely, and done faster that way. But some problems need hands on equipment. Ask which areas the provider covers in person, how visits are arranged, and whether they are included or billed separately. If you have several locations, ask about each one.

How does the price change as we grow or shrink?

Per-user and per-device pricing adjust in different ways. Ask how often counts are reviewed, whether there are minimums, and how quickly a departing employee comes off the bill.

Security

What security baseline do you apply to every client?

A mature provider has a standard set of controls applied everywhere, not a menu you have to remember to order. Ask what it includes. You should hear about multi-factor authentication, patching, endpoint protection, email filtering, backups and control of administrative access.

How do you protect your own access to our systems?

Your provider's tools and accounts are a path into your environment. Ask how their staff sign in, who on their team has access, and how that access is removed when one of their own employees leaves.

What happens if we have a security incident?

Ask who leads the response, what is covered by the regular fee, and at what point outside specialists or your cyber insurer would be involved.

How are backups tested?

A backup that has never been restored is a hope, not a plan. Ask how often restores are tested and whether you will see the results.

Reporting and accountability

What will you report to us, and how often?

Regular reports should show what actually happened: ticket volumes and themes, patch status, backup health, security events and devices approaching end of life. Ask to see a sample report with client details removed.

Will we have regular business reviews?

A report tells you what happened. A review is a conversation about what it means and what to do next: budget, risks, upcoming renewals and growth plans. Ask how often reviews happen and who attends from their side.

People

Who will we actually talk to?

The person who sells to you is often not the person who supports you. Ask who your day-to-day contacts will be, who owns the relationship, and who you escalate to when something goes wrong. Ask to meet them before you sign.

Who helps us plan, not just fix?

Someone should be looking ahead with you: budgets, device refresh, licence renewals, end-of-life systems and the technology side of your growth plans. Ask who does that work, how often, and whether it is part of the regular fee or a separate engagement.

How do you keep knowledge of our environment?

Ask how your systems are documented and whether that documentation belongs to you. If one technician leaves their team, your support should not leave with them.

Offboarding

What happens if we leave?

It feels odd to discuss the breakup before the relationship starts, but this is where many agreements are weakest. Ask about the notice period, any termination fees, what transition help is included, and how quickly credentials and documentation are handed over. Ask whether any accounts, licences or domain names will be registered in their name rather than yours.

Who owns the documentation and configuration?

Your network diagrams, passwords and system documentation should belong to you. Get that in writing, not as a verbal assurance.

How to read the answers

A few patterns are worth noticing as you compare providers:

  • Specific answers with examples are a good sign. General reassurance is not.
  • A provider that volunteers its exclusions is one that expects a long relationship.
  • If the security answer is mostly a list of products rather than a process, dig deeper.
  • If nobody can tell you who your contact will be, that is the answer.
  • If offboarding questions make the conversation awkward, take note.

Frequently asked questions

How many managed services providers should we compare?

Two or three is usually enough. More than that and the comparisons start to blur. Use the same list of questions with each one so the answers are comparable.

Should we ask an MSP for references?

Yes. Ask to speak with a client of a similar size or industry, and ask them about the transition and how problems were handled, not just whether they are happy.

Is a longer contract term a red flag?

Not necessarily. A longer term can make sense when the provider invests heavily in onboarding or equipment. What matters is that the exit terms are clear and fair and that the service commitments are written down.

How Ceifa answers these questions

I would rather a prospective client asked us every question on this list than none of them. The short versions of our answers: critical issues get a response within 30 minutes during business hours. Support runs during business hours, with unlimited helpdesk for one flat monthly fee per user. Every managed client gets the same security baseline and a monthly report. And you know who you talk to: I own the client relationship, and our service delivery team owns the day-to-day work.

For everything else, including exclusions and offboarding terms, we will walk through the agreement with you line by line before you sign. Learn more about our managed IT services, or book a conversation and bring your list.

Clod Feijao

Partner and Director of Client Success, Ceifa IT Services

More about Clod →

Want IT that is simply handled?

Ceifa runs helpdesk, security and infrastructure for one flat monthly fee per user. Tell us what you have today and we will send you a quote.