There's a format to the average MSP discovery call that's become so standard it's almost invisible. A few rapport-building questions. A broad ask about the current IT setup. A transition into the MSP's services and differentiators. A pricing range. A next steps ask.
This is a pitch with a questionnaire attached to the front. It feels like discovery. It isn't. And it closes at the rate of a pitch.
A pitch is a presentation of what the MSP offers, organized around what the MSP wants the prospect to know. A discovery call is a structured exploration of the prospect's specific situation, organized around understanding their world well enough to know whether and how the MSP can help.
The difference sounds subtle. The outcome difference is not. A prospect who has been genuinely heard — whose specific problems and concerns were surfaced and acknowledged before a single product feature was mentioned — is a fundamentally different sales conversation than one who received a presentation.
The pitch creates evaluation. The discovery creates connection. And connection closes.
Not "do they have IT needs" — everyone does. The questions that matter are: What is the most frustrating thing about the current IT situation? What happened recently that made them decide to have this conversation? What would need to be true for them to consider this a successful engagement twelve months from now? What's their biggest worry about switching providers?
These questions surface information genuinely useful for building a relevant proposal. And they give the prospect the experience of being understood — which most people never have with a vendor in the evaluation process, and which is therefore a significant competitive differentiator.
The follow-up questions matter as much as the initial ones. "You mentioned issues with response times — can you walk me through what that looks like when something goes wrong? What's the business impact?" Every good discovery answer contains three more questions. The MSP that follows the thread gets more information and builds more trust simultaneously.
Because pitching feels productive. It's forward motion. It's demonstrating knowledge and capability. Discovery, by contrast, can feel like delay — getting further from the close by asking questions instead of giving answers.
This intuition is almost perfectly backwards. The pitch that follows real discovery closes faster than the pitch that replaced it. Because it's shorter, more specific, and directly addresses the concerns actually surfaced. The prospect doesn't need to imagine how it applies to their situation. They already told you their situation. You told them what you'd do about it. The gap between that and a yes is much smaller.
What is the most common discovery call mistake MSPs make?
Treating discovery as an introduction to the pitch rather than a genuine exploration of the prospect's situation. The typical format collects just enough information to start talking about the MSP's services — not enough to understand the prospect's actual world.
What questions should a real discovery call answer?
What's the most frustrating thing about their current IT? What happened that made them have this conversation now? What would success look like in twelve months? What's their biggest worry about switching? These build both a relevant proposal and genuine connection.
Why does real discovery close at a higher rate than pitching?
Because the proposal that follows genuine discovery is shorter, more specific, and directly addresses the actual concerns surfaced. The prospect has experienced being understood — which is rare in vendor evaluations — and the distance to a signed agreement is significantly shorter.