How to Choose an MSP: 12 Questions to Ask Before You Sign
12 questions to ask any managed service provider about support, security, backups, pricing and contracts, plus red flags to watch for before you sign.
The quote from the last IT provider looked great. A flat monthly price per user, "24/7 support" in bold on the first page, and a sales rep who answered every email within the hour. Six months later, the plant manager is waiting two days for a callback on a printer that runs the shipping labels, nobody can say when the firewall was last updated, and the contract has 30 more months on it with an early termination fee nobody noticed. If you're trying to figure out how to choose an MSP without ending up in that spot, you're asking the right question at the right time: before you sign.
I'm Harsha, one of the co-founders of SoftwarePac Technologies here in Roanoke. I've spent 15 years on the network and infrastructure side of IT, and my partner Mukesh has spent 25 years in cybersecurity. We sit on both sides of this conversation. We sell managed IT services, and we also get called in after another provider relationship has gone sideways.
This guide gives you 12 questions to ask any managed service provider (us included), what a good answer sounds like, and the red flags that should make you slow down. It's written for IT managers, CTOs and owners at small and mid-sized companies, especially manufacturers, who don't have time to become procurement experts.
In this guide
- Before you talk to anyone: know what you need
- How to choose an MSP: questions about support and response
- Questions about security, backups and compliance
- Questions about contracts, pricing and getting out
- Red flags that should slow you down
- How to compare MSPs side by side
- Frequently asked questions
Before you talk to anyone: know what you need
The biggest mistake I see is starting with sales calls. Every provider will tell you they do everything. If you don't know what you need, you can't tell a good fit from a good pitch.
Spend an hour writing down the basics first. It will make every conversation faster and every quote easier to compare.
Your one-page IT snapshot
- Users and devices: how many people, laptops, desktops, phones, and shared machines like shop-floor PCs.
- Locations: offices, plants, warehouses, and anyone who works remotely.
- Key systems: your ERP, accounting software, Microsoft 365 or Google Workspace, line-of-business apps, and anything on the plant floor that touches the network.
- Network gear: firewall, switches, wireless access points, and roughly how old they are.
- Compliance needs: CMMC or NIST 800-171 if you handle defense work, HIPAA if you touch patient data, and the security requirements on your cyber insurance application.
- Pain points: the three things that frustrate your team most today.
- What you keep in-house: if you have an IT person, what they'll keep doing and what you want off their plate.
If you're still deciding whether outsourcing is even the right move, I broke down the numbers in MSP vs. hiring a full-time IT person. It's worth reading before you start collecting quotes.
How to choose an MSP: questions about support and response
Support is what your employees feel every day. These questions tell you whether the provider can actually keep your people working.
1. What are your response and resolution times, and are they in the contract?
"We're fast" is not an answer. Ask for written response times by priority level, for example how quickly they respond when a whole site is down versus when one person needs a password reset.
A good answer separates response (someone is working on it) from resolution (it's fixed). Ask what happens if they miss those targets. Some providers offer service credits, many don't, and you should know which before you sign.
2. Who actually answers when we call?
Find out whether you'll reach a technician, a call center that takes a message, or a ticket portal. Ask where the help desk is staffed and during what hours.
"24/7 support" can mean very different things. Sometimes it means 24/7 monitoring with an on-call engineer for emergencies, and business-hours help desk for everything else. That can be perfectly fine, as long as you know it up front.
3. Can you support us on-site when needed?
Plenty of work can be done remotely. Some things can't, like a failed switch in a production building or a new wireless access point in a warehouse.
Ask how on-site visits work, how fast someone can get there, and whether visits are included or billed separately. For multi-site companies, ask how they cover locations that aren't near their office.
4. Will we have a named contact who knows our environment?
You want someone who understands your network, your key systems and your business, not a new face on every ticket. Ask who your primary technical contact will be and how often you'll meet to review tickets, projects and risks.
Regular business reviews (often quarterly) are a good sign. They're where a provider should bring you recommendations, not just a ticket count.
Questions about security, backups and compliance
This is where the gap between providers is widest. Mukesh likes to say that the security conversation tells you more about an MSP than anything else, because it shows whether they think ahead or just react.
5. What security is included, and what costs extra?
Get a clear list. At a minimum, I'd expect to discuss patching for operating systems and common applications, endpoint protection such as EDR, multi-factor authentication, email filtering, and firewall management.
Ask who watches the alerts. An EDR tool that nobody monitors at 2 a.m. is only doing part of its job. If they offer 24/7 monitoring, ask whether it's their own team or a partner, and what they do when something fires.
6. How do you handle backups, and when did you last test a restore?
Backups are easy to promise and easy to get wrong. Ask what gets backed up (servers, Microsoft 365 or Google Workspace data, key workstations), where copies are stored, and whether at least one copy is offline or immutable so ransomware can't reach it.
Then ask the question that matters most: how often do they test restores, and will they show you the results? A provider that tests regularly will have an answer ready.
7. What happens in the first hour of a security incident?
Ask them to walk you through it. Who calls whom, who can isolate a machine or disable an account, and at what point they bring in your cyber insurance carrier or an outside incident response firm.
A good provider will have a documented process and will want to agree on it with you before anything happens. If the answer is "we'd figure it out," keep looking.
8. Can you support our compliance requirements?
If you're a defense supplier, ask about their experience with NIST 800-171 and CMMC, and how they'd handle the parts of the work that touch your systems. If you're in healthcare, ask whether they'll sign a Business Associate Agreement.
Be careful with anyone who promises to "make you compliant" by themselves. Compliance is shared work between you and your provider, and the final word comes from your assessor, auditor or attorney. If CMMC is on your radar, our post on CMMC Level 1 vs. Level 2 is a good starting point.
Questions about contracts, pricing and getting out
A great provider with a bad contract can still leave you stuck. Read these parts of the agreement slowly.
9. What exactly is included in the monthly price?
Most MSPs price per user, per device, or a mix of both. Neither is right or wrong. What matters is knowing what's inside the number.
Ask for a written list of what's included and what isn't. Common gray areas are projects (like a server migration or office move), after-hours work, new user setup, hardware, software licensing, and on-site visits. If you want a feel for typical pricing, I covered it in managed IT services in Roanoke: what local businesses should expect.
10. How long is the contract, and how do we get out?
Contract terms commonly run one to three years. Longer terms can come with a better rate, but make sure there's a reasonable way out if service doesn't match what was promised.
Look for the notice period, any early termination fees, and whether the contract renews automatically. Auto-renewal is common; just put the date on your calendar.
11. Who owns our accounts, passwords and documentation?
This one gets skipped and causes real pain later. You should own your domain names, your Microsoft 365 or Google tenant, your firewall and your licenses. Your provider should have admin access, not sole ownership.
Ask how they store documentation and passwords, and whether you'll get a full copy on request. A well-run MSP keeps good records and isn't nervous about sharing them.
12. What does offboarding look like if we part ways?
It feels odd to ask about the breakup on the first date. Ask anyway. A good answer covers handing over credentials and documentation, transferring licenses, and helping the next provider get up to speed.
The way a provider answers this question tells you a lot about how they'll treat you while you're still a customer.
Red flags that should slow you down
None of these are automatic deal-breakers. Each one is a reason to ask more questions before you sign.
- No written response times. If it isn't in the agreement, it isn't a commitment.
- Vague "unlimited support" with no scope. Unlimited usually has limits. Find out what they are.
- They want to own your accounts. Your domain, cloud tenant and licenses should be in your company's name.
- No questions about your business. A provider who quotes before understanding your systems is guessing.
- Security is all add-ons. Basic patching, MFA and endpoint protection shouldn't be a surprise upsell.
- No references. Ask for two or three current customers of similar size, and actually call them.
- Pressure to sign fast. A good provider will give you time to read the contract.
How to compare MSPs side by side
Once you've talked to two or three providers, put their answers next to each other. A simple spreadsheet works fine.
- List the 12 questions down the left side and each provider across the top.
- Score each answer from 1 to 3: vague, acceptable, or clear and in writing.
- Add a row for total monthly cost and a row for one-time onboarding costs.
- Add a row for references, with a note from each call.
- Weight what matters most to you. For a manufacturer with a 24-hour plant, on-site response and network uptime may matter more than anything else.
The cheapest quote rarely wins this exercise, and the most expensive one doesn't automatically win either. You're looking for the provider whose answers are specific, written down, and match how your business actually runs.
If you're also weighing new systems or software as part of the switch, our guide on how to choose the right technology for your business pairs well with this one.
Frequently asked questions
What should I look for when choosing an MSP?
Look for written response times, a clear list of what's included, real security practices (patching, MFA, monitored endpoint protection, tested backups), and a fair contract you can exit. Just as important, the provider should ask you plenty of questions about your business before they quote.
How much does a managed service provider cost?
Pricing varies a lot by region, scope and security level. Most MSPs charge per user or per device each month, often with separate fees for onboarding and larger projects. The best way to compare is to get itemized quotes from two or three providers covering the same scope.
How long are typical MSP contracts?
One to three years is common, and many contracts renew automatically. Longer terms may lower the monthly rate, but check the notice period, early termination fees, and whether there's an exit option if service levels aren't met.
Should a small manufacturer use a local MSP or a national one?
Both can work. A local provider can usually get someone on-site faster, which matters when a production network goes down. A larger provider may offer more round-the-clock staffing. Ask each one how they handle on-site visits and after-hours emergencies, and decide based on what your plant actually needs.
What questions should I ask an MSP about cybersecurity?
Ask what security tools are included, who monitors alerts and when, how backups are protected and tested, and what their incident response process looks like in the first hour. If you have compliance requirements like CMMC or HIPAA, ask about their specific experience and how responsibilities are split.
Want a second opinion before you sign?
Choosing an MSP is a multi-year decision, and it's hard to judge a provider's security claims when you're not sure where your own gaps are. That's where a clear picture of your current environment helps.
We offer a free cybersecurity assessment for small businesses and manufacturers. We'll look at your network, endpoints, backups and key security controls, and give you a plain-English summary of what's working and what needs attention. You can use it to evaluate any provider, whether or not that's us.
Related reading
- MSP vs. Hiring a Full-Time IT Person: A Real Cost Breakdown
- Managed IT Services in Roanoke, VA: What Local Businesses Should Expect
- Cybersecurity for Roanoke Small Businesses: 10 Steps to Protect Your Company
Harsha is a co-founder of SoftwarePac Technologies in Roanoke, VA, and a network engineer with 15 years of experience.




