The Receipt Test: 5 Questions That Tell You If Your MSP Is Still the Right Fit

You don't need a vendor audit to know if your MSP is the right fit. You just need to send five questions — one each to five different people within your MSP — and see how each side of the house responds.

How not to trigger their alarm bells: if you fire all five questions at your account manager on a Tuesday afternoon, you're not doing diligence anymore. You're sending a signal. The account team escalates, the answers get lawyered, and you get back the version of the truth that's been through a sales filter.

So spread the questions out. Each one goes to a different stakeholder on the MSP side, and each one is the kind of routine question that stakeholder would normally field on a Tuesday. Done this way, the responses look like normal operations — which is exactly what you want to evaluate.

Question 1 → Your account executive: "What's our renewal date and notice window?"

This is a vanilla housekeeping question an AE should answer in a few hours without flinching. If they hedge, dodge, or take a week to come back, you've already learned something. A healthy account team has the answer at their fingertips because they're tracking the renewal in their own CRM.

What you're listening for: a precise date, a precise notice window (typically 60 or 90 days), and ideally a calendar invite for the conversation. What you don't want: "Let me circle back on that."

Question 2 → Their finance / billing contact: "Can you send me a YTD spend summary including all change orders and add-ons?"

This goes to the billing or AR contact, not your AE. Frame it as a finance request for your own internal reconciliation — totally normal, no alarm bells.

Compare the YTD number to your original contract headline. If the gap is more than 8-10%, that's quiet scope creep that nobody flagged for you. Billing transparency isn't about whether they invoice correctly. It's about whether they'd volunteer the variance.

Question 3 → Their service delivery manager or PMO: "Can you send me your documented P1 incident escalation path?"

Route this through service delivery, not sales. It's the kind of document an SDM should be able to attach in under an hour because they refer to it themselves. If the SDM forwards it to your AE first, that's its own data point — escalation paths shouldn't need sales approval.

What you're listening for: a real document with named roles and timeframes. What you don't want: a generic "we'll get back to you within X hours" boilerplate.

Question 4 → Your assigned engineer or technical lead: "Quick question — have you been with the company long? Wondering who to escalate to internally if you're out."

Frame this as an operations question, not an audit. The implied subtext ("how long until you leave?") is what you're actually measuring, but the framing makes it conversational.

What you're listening for: tenure of more than 18 months, ideally more than 3 years. The MSP industry runs 25-35% annual delivery-team turnover. If your named engineer started six months ago, the next 12 months will likely involve another transition.

Question 5 → Their CSM or relationship manager: "We're due for our quarterly review — can you send a deck or summary of the last 90 days plus what's coming up?"

This is a softball that a healthy CSM will swing at gladly. A struggling CSM will either improvise the deck on the call (translation: the QBR cadence has lapsed) or push it onto your AE (translation: there is no CSM relationship to speak of).

What you're listening for: a proactive, data-rich response that includes things you didn't ask about. What you don't want: a backward-looking summary with no forward plan, or a deck that looks 80% template.

Five questions, five different contacts, spread across two or three days. None of them is alarming in isolation. Together they paint a remarkably accurate picture of where the relationship actually is — without putting the MSP on the defensive.

If you'd like a second opinion on the answers you got, ITBluPrint does free 20-minute reviews of MSP responses. We've seen enough patterns across these five touchpoints to read the signal under the noise. Send us yours →