More prospects are walking into sales calls with a checklist now. Some of it comes from bad experiences with a previous provider, some from articles telling business owners what to watch for. Either way, if you run an MSP, it’s worth knowing what’s actually being asked and why, because the questions have changed even if your pitch hasn’t.
This isn’t a list to memorise for the sake of sounding prepared. It’s a way to check whether your business would actually hold up if a sharp prospect pushed on each point.
Response times versus resolution times
Most MSPs quote a response time somewhere in their pitch. Prospects who’ve been burned before know that answering a ticket and fixing a problem are different things, and they’ll ask which one you’re actually promising.
If your response time is fast but your resolution time is vague, say so plainly. A client who has dealt with a provider that answered quickly and then sat on the actual fix for days will respect an honest answer more than a polished one that dodges the question.
What happens outside business hours
This question used to be about after-hours support. Now it’s more specific: what actually happens if something breaks at 11pm on a Saturday, who gets notified, and how long before a human is looking at it.
Prospects ask this because they’ve usually had at least one incident that started outside office hours and got worse because nobody noticed until Monday morning. If your monitoring genuinely catches these and your escalation path is real, walk through it in detail rather than summarising it. The specificity is what builds trust.
Where their data actually sits
Data residency questions used to be rare outside regulated industries. They’re common now, partly because clients have read enough about cloud outages and data breaches to want a plain answer about where backups live and who else can access them.
Be ready to explain, in non-technical language, where a client’s data is stored, who has access to it, and what separates their environment from any other client’s. If you can’t answer this cleanly for your own stack, that’s worth fixing before it costs you a deal.
How they leave, not just how they join
Onboarding gets a lot of attention in most MSP pitches. Offboarding gets almost none, and that’s exactly why prospects are starting to ask about it.
A client who has been through a bad exit from a previous provider — data held hostage, documentation missing, a slow handover that cost them weeks — will ask directly what happens if they decide to leave. The honest answer is that a clean, documented exit process is a selling point, not an admission of weakness. Providers who resist the question usually have something to hide.
Who actually does the work
Prospects have caught on that some MSPs subcontract technical work to third parties without saying so clearly. The question now is usually framed as