
How to choose a managed service provider: questions, red flags and contract terms
How to choose a managed service provider comes down to three checks: what they will own, how they protect their own access to your systems, and how easily you can leave. Write down your needs first, ask every candidate the same questions, get response and restore times, security duties and exit terms into the contract, and walk away from anyone who will not put their answers in writing.
How to choose a managed service provider: where do you start?
The first step in how to choose a managed service provider is your own list, not their brochure. Before the first sales call, write down every system the business depends on, who looks after it today, what has gone wrong in the last year, and what data you hold that a regulator cares about. That one page turns a sales conversation into an evaluation, because every candidate now has to answer the same questions about the same systems.
A managed service provider (MSP) is a company that runs part or all of your technology under an ongoing contract, usually with written service levels. Some cover laptops and the help desk. Some, like us, focus on what a business runs online: websites, applications, servers, hosting, backups and domain and email records. A managed security service provider (MSSP) focuses on security monitoring; our comparison of MSP vs MSSP covers the difference. Knowing which kind you need removes half the candidates before you start.
Then decide the model. Fully managed means the provider runs everything in scope. Co-managed means your own IT person keeps part of the work; our guide to co-managed IT services explains how that split is written. The questions below work for both.
What should you look for in an MSP?
Look for a provider that knows your kind of systems, answers in writing, and treats its own access to your business as a risk to manage. Friendly people and a good demo matter less than whether they can show you a real monthly report, a real incident record with names removed, and a contract you can read in one sitting.
Four traits separate providers in practice. They describe scope by system and task, not by vague tiers. They give response and restore targets by severity. They can explain how they would hand your systems to someone else. And their references have been clients for years, not months. We work with some clients on relationships that are 13+ years old, and the reason is boring: written commitments we keep.
What questions should you ask a potential MSP?
Ask every candidate the same questions, in writing, and compare the written answers side by side. This is the core of how to choose a managed service provider: a provider that answers clearly in a sales process tends to answer clearly during an outage. The table lists the questions we would ask, grouped by what they test, with what a good answer sounds like.
| Question | What it tests | A good answer sounds like |
|---|---|---|
| Which of our systems will you own, task by task? | Scope | A written list by system, with what is excluded |
| What are your response and restore targets for each severity level? | Service levels | Both numbers per level, plus after-hours terms in writing |
| Who will actually work on our systems, and how many people know them? | People and backup | Named roles, and more than one person who knows your setup |
| How do your staff log in to our systems? | Their access | Named accounts, MFA on every one, least privilege, logged |
| How fast do you apply security patches, and how do you report it? | Patching | A stated window for critical patches and a monthly report |
| How often do you test a restore, and will we see the result? | Backups | Scheduled restore tests with results shared |
| What do you log, for how long, and can we get the logs? | Logging | A retention period and a way for you or your responder to get them |
| How and when will you tell us about a suspected security incident? | Incident notice | A time limit and a named contact path in the contract |
| Who decides to shut something down during an incident? | Authority | A written authority path, including what happens at night |
| Do you use AI agents or automation on client systems, and what do they log? | Automation | Which actions, which approvals, and an audit log you can read |
| Which third parties do you rely on to serve us? | Supply chain | A list of key subcontractors and tools, and who is responsible for them |
| Who owns the passwords, documentation and configurations you create? | Ownership | You do, kept in systems you control |
| What does leaving look like, and how long does handover take? | Exit | A handover period, what is returned, and when access is removed |
| Can we speak to a client who has been with you for several years? | Track record | Yes, and a client in a business like yours |
Keep the answers. They become the starting point for the contract, and a provider that gave a confident answer in writing has a harder time walking it back when the agreement is drafted. If a candidate answers a question with a product name or a sales line instead of a process, ask it again in different words before you score it.
How do you check an MSP's own security?
Ask how they protect the access they hold to you, because a provider's remote tools reach every client at once. The joint advisory CISA AA22-131A from US, UK, Australian, Canadian and New Zealand cybersecurity authorities (May 11, 2022) tells MSP customers to require multifactor authentication on all MSP accounts, to have least privilege applied in both environments, and to have the contract say how and when the MSP notifies them of an incident.
The UK's National Cyber Security Centre guidance on choosing an MSP (published November 2025) adds concrete checks: it recommends software is patched within 14 days of an update being released, asks whether the MSP has a tested incident response and recovery plan, and asks if you have assessed the MSP's own supply chain risks. Those are fair questions for any provider, wherever it is based.
Automation is the newer question. If a provider's AI agents or scripts act on your systems, ask what each one may do, who approves risky actions, and if you can read the log. LTFI's guide to audit trails for AI agents lists what that log should prove.
What are the red flags when choosing an MSP?
The biggest red flag is a provider that will not put its answers in writing. The rest are variations: vague scope, response promises with no restore target, shared logins, and a contract that makes leaving expensive. Any one of these is a reason to ask again; two or three together are a reason to keep looking.
| Red flag | Why it matters | Ask instead |
|---|---|---|
| "Unlimited support" with no written scope | Unlimited usually means undefined, and undefined work gets dropped | Which systems and tasks are in scope, and which are not? |
| Response times with no restore targets | A one-hour response can still mean a two-day outage | What is the restore target for a severity 1 outage? |
| One shared admin login for their whole team | Nobody can tell who did what, and a leaked password reaches everything | Will every technician have a named account with MFA? |
| They keep your passwords in their own system only | Leaving means asking them for the keys to your business | Where are credentials stored, and do we hold a copy? |
| Auto-renewal with a long notice window and early-exit fees | You stay because leaving is costly, not because the work is good | What are the renewal, notice and termination terms? |
| No restore test results, ever | An untested backup is a hope | When was the last restore test, and can we see it? |
| They cannot name who will work on your systems | You are buying a queue, not a team that knows you | Who are the people, and who covers when they are out? |
| Security described only as product names | Tools are not a process | What do you do when an alert fires at 2 a.m. on a Saturday? |
What should an MSP contract say before you sign?
The contract should restate every answer that mattered: scope by system, service levels by severity, security duties, incident notice, ownership of what they create, and exit terms. NCSC puts the reason plainly: "Clear contracts define who is responsible for each aspect of an incident." NIST Cybersecurity Framework 2.0 frames the same idea as GV.SC-05, which calls for cybersecurity requirements to be integrated into contracts with suppliers, and GV.SC-10, which calls for plans covering what happens after a service agreement ends.
- Scope: a schedule listing each system and task, and what is excluded.
- Service levels: response and restore targets for each severity, after-hours terms, and how they are reported.
- Security duties: named accounts, MFA, least privilege, patch windows, logging and log access.
- Incident notice: how fast they tell you, through which channel, and who has authority to act.
- Backups: what is backed up, how often restores are tested, and who sees the results.
- Ownership: you own credentials, documentation, configurations and data, kept where you control them.
- Subcontractors: which third parties they use and who answers for them.
- Exit: notice period, handover steps and time, return of data, and confirmed removal of their access.
Two pieces by Amelia S. Gagne go deeper on the clauses buyers most often get wrong: what an MSP scope of work should actually say, and why an MSP SLA response time is not resolution time. Our own page on SLA response times explains severity levels in plain language. If you want a second pass over a long agreement, Qurtoo's prompt chain for pulling red flags out of vendor documents marks missing protections as missing instead of guessing; a person still makes the call.
What changes if you handle health, financial or resident data?
If you handle regulated data, how to choose a managed service provider is partly a legal question, and the law tells you what to check. In Massachusetts, 201 CMR 17.00 requires businesses that hold residents' personal information to oversee service providers by taking reasonable steps to select ones capable of appropriate security measures and requiring those measures by contract.
Businesses covered by the FTC's Safeguards Rule, which the FTC's own guide says includes mortgage brokers, payday lenders, collection agencies and tax preparation firms, have a third duty under 16 CFR 314.4(f): periodically assessing service providers based on the risk they present and the continued adequacy of their safeguards. Selection is not a one-time event.
Healthcare has its own rule. HHS guidance on HIPAA and cloud computing says a provider that creates, receives, maintains or transmits electronic protected health information for you is a business associate, even if it stores only encrypted data without the key, and a business associate agreement is required. An MSP that will not sign one is not an option for a practice. Our HIPAA compliance guide covers the rest.
How do you compare MSP pricing without being misled?
When people ask us how to choose a managed service provider on price, our answer is to compare scope first and price second. Two quotes are only comparable when they cover the same systems, the same service levels and the same security duties; a lower number often means fewer of those. Ask each provider to price against your one-page list, so the differences show up as line items instead of surprises.
Common models are per user, per device, tiered bundles, a flat retainer for a defined scope, and hourly or block time for projects. Each one shifts risk differently. Our guide to managed IT cost drivers explains what moves the number, and Brian S. Gagne's analysis of managed IT cost per user compares a per-user quote with the cost of an in-house hire.
How to choose a managed service provider in six steps
The process below for how to choose a managed service provider takes most small businesses a few weeks, and most of the time goes into step one. Skipping it is the most common reason buyers end up comparing brochures instead of answers.
- Write your one-page list: systems, current owners, last year's problems and regulated data.
- Decide the model (fully managed or co-managed) and the kind of provider (MSP, MSSP or both).
- Send every candidate the same written questions from the checklist above.
- Compare the written answers side by side, then call two long-standing references for each finalist.
- Turn the best answers into contract terms, including exit, and have someone read the agreement against your list.
- Plan the first 30 days with the winner: access moved into a vault, an inventory, and the first priorities written down.
What if you already have an MSP and want to change?
Most of how to choose a managed service provider applies again when you switch, and the first rule is to plan the exit before you announce it. Make sure you hold working administrator access to every system, domain registrar and email account; find the contract's notice period; and get current documentation before the relationship cools. Our note on switching IT providers without losing access lists the logins that most often go missing, and if your provider was recently bought by a larger group, our note on what to check when your IT provider gets acquired covers the contract questions that come up. Knowing who owns the website and its logins is usually the first one.
How does Kief Studio answer these questions?
We would rather be measured against this checklist than pitch around it. We run managed technology services for what a business runs online: websites, applications, Linux servers, hosting, backups, domain and email records, and security monitoring on what we host. We are not a laptop help desk, and if you have a good provider for that, keep them.
Our written SLAs set severity levels with response and restore targets, and after-hours response is written into the agreement when you need it: 3am is a retainer, not a default. Onboarding moves credentials into a vault and inventories every system before we change anything, and quarterly business reviews report what changed. We host on dedicated infrastructure, with no shared hosting. We are based in Shrewsbury, Massachusetts, and work across Worcester County and beyond. The MSP and MSSP services hub shows how the pieces fit.
Also read
How to choose a managed service provider: questions, red flags and contract terms: questions people ask
How to choose a managed service provider?
Write down your systems and needs first, then ask every candidate the same written questions about scope, response and restore times, how they secure their own access, backups, incident notice and exit. Compare the written answers, check long-standing references, and put the answers that mattered into the contract.How to find a good MSP?
Ask businesses like yours who they have used for several years, then test each candidate with the same written questions. A good MSP answers in writing, names the people who will work on your systems, shows a real report, and explains how you would leave without losing access.What to look for in an MSP?
Look for scope described by system and task, response and restore targets by severity, named accounts with MFA for their staff, tested backups, a clear incident notice path, and exit terms you can live with. References who have stayed for years say more than any certificate on a website.What questions should I ask a potential MSP?
Ask what they will own task by task, their response and restore targets, how their staff log in to your systems, how fast they patch, how often they test restores, how they notify you of incidents, who owns the documentation, and what leaving looks like. Get every answer in writing.What is an MSP contract?
An MSP contract, often a master services agreement with schedules, sets what a managed service provider will do for you, how fast, at what price, and under what terms either side can end it. The useful parts are the scope schedule, the service levels, the security duties and the exit terms.What are red flags on a sales contract?
In a managed IT contract, the red flags are undefined scope, auto-renewal with a long notice window, early-termination fees, response times without restore targets, no security duties for the provider, and no handover terms. Each one makes the provider's job easier and your exit harder.What are some red flags in procurement?
When buying IT services, watch for a vendor that will not answer in writing, pressure to sign before you have compared quotes, references that are all recent, pricing that cannot be tied to scope, and contract terms that differ from what the salesperson said. Slow down when you see two or more.How much does a managed service provider charge?
It depends on scope, the number of users and systems, the service levels you need, after-hours coverage, security duties and any compliance work. Providers price per user, per device, by tier, as a flat retainer or by the hour. Compare quotes against the same written scope.What is managed services in the IT industry?
Managed services means an outside provider runs part of your technology on an ongoing contract instead of fixing things only when they break. Typical work includes monitoring, patching, backups, security, hosting and planning, measured against written service levels and reviewed on a schedule.What questions should a CIO ask when evaluating a managed network provider?
Beyond scope and price, ask how the provider's staff access your network, what they log and for how long, how fast they patch network devices, who has authority to isolate a segment during an incident, which subcontractors they rely on, and how a handover to another provider would work.How to scope an MSP project?
List every system involved, the tasks for each, who owns them today, and what done looks like. Mark what is excluded as clearly as what is included. Attach that list to the contract as a schedule, so changes to scope become signed changes rather than remembered conversations.How do I change managed service provider?
Confirm you hold administrator access to every system, domain and email account, read the notice and termination terms, collect current documentation, and line up the new provider before giving notice. During handover, have the old provider's accounts removed and confirm they are gone.What are some examples of MSP?
Examples include a local firm that runs office laptops and the help desk, a provider that hosts and maintains a company's websites and applications, a cloud specialist that manages servers and backups, and a managed security service provider that watches for threats. Many businesses use more than one.
More in Support
- Managed Services
You run your business. We keep the technology running.
- Quarterly Business Review
Strategic check-ins, not status calls.
- Strategic Advisory
Technology decisions that make business sense, not just technical sense.