"What's the response time, and is it in the contract?"
If the SLA isn't written into the agreement, it isn't binding. Ask for specific numbers: first response, onsite response, after-hours definition. Then ask what happens if it's missed — credits, escalations, exits.
"Can you name every tool you're going to deploy?"
An MSP that can't list its own stack is selling you a black box. Real partners name their EDR, backup, RMM, email security, DNS filter, and SOC vendor in the first conversation. You can search every name. You should.
"What does my offboarding look like — in writing?"
Read the offboarding clause before you sign. Are configurations and recovery keys returned? At no charge? Within a fixed window? "At our discretion" is a future invoice waiting to happen.
"How do you bill for projects, hardware, and emergencies?"
Recurring is the easy part. Find out how non-recurring work is priced before you need it. Hardware markup, project rates, emergency premiums — all should be on the menu in writing.
"Who's my actual technician, and have I met them?"
If the answer is "a team" or "whoever's available," expect a different person every ticket. The right MSP assigns a primary engineer to your account who knows your network on day one of every call.
