Picture this.
You’ve got a decent inbound enquiry.
They’ve got a real business. Real users. Real risk.
You jump on the first call, do the polite dance, ask a few questions, explain what you do, and end with:
“Shall we book another call?”
They say, “Yeah, sounds good.”
And then you never hear from them again.
It’s not because your service is bad.
It’s because your discovery call felt like every other MSP discovery call.
And when switching IT support feels risky, “generic” doesn’t get a second meeting.
TL;DR
If your MSP discovery calls don’t convert, stop doing a feature tour. Use a simple structure: set the agenda, diagnose the real risk, quantify impact, agree what ‘good’ looks like, and offer a clear next step. The goal is to make the decision feel safe, not to impress them.
Definition
An MSP discovery call is the first structured conversation with a prospect to understand their current IT situation, risks, and priorities, and to agree the next step (usually an assessment or proposal call).
Why MSP discovery calls stall
Most MSPs think the first call is about proving competence.
So they:
- talk about tools
- list services
- explain their process
- try to sound “enterprise”
The prospect hears: “This is going to turn into a sales process.”
And if they’ve been burned before, that’s enough to go quiet.
A good discovery call does the opposite.
It reduces uncertainty.
It helps them feel like you understand their world.
And it gives them a next step that doesn’t feel like a trap.
The rule: a discovery call should create clarity, not excitement
Excitement is fragile.
Clarity sticks.
If the prospect leaves the call thinking:
- “They get it.”
- “They’re not going to waste my time.”
- “This feels controlled.”
You’ll get the next step.
A simple MSP discovery call structure (45 minutes)
Use this as a repeatable framework.
1) Open with a calm agenda (2 minutes)
You’re setting tone and safety.
Script:
“Thanks for making time. I’ll ask a few questions about what’s driving the change, what’s working, and what’s not. Then I’ll tell you what I’d check first and we’ll decide the best next step. Sound fair?”
2) Get the real reason they’re looking (10 minutes)
Don’t accept “we need better support” as the answer.
Ask:
- “What happened that made you take this seriously now?”
- “What’s the thing you’re trying to avoid?”
- “If nothing changes in the next 90 days, what breaks first?”
You’re looking for a trigger.
Incidents. Audit pressure. A board question. A key person leaving. A near miss.
3) Map the risk (10 minutes)
This is where MSPs win.
Ask:
- “What would be a career-limiting IT incident for you?”
- “Where do you feel exposed right now?”
- “If I spoke to your finance lead, what would they complain about?”
You’re not trying to scare them.
You’re trying to name what they already worry about.
4) Quantify impact (5 minutes)
This is how you stop the “we’ll think about it” loop.
Ask:
- “If email went down for half a day, what’s the cost in real terms?”
- “How many users are affected when tickets pile up?”
- “How often does IT distract your leadership team?”
You don’t need perfect numbers.
You need a believable range.
5) Define what ‘good’ looks like (8 minutes)
Most MSPs skip this and then wonder why the prospect compares on price.
Ask:
- “If we fast-forward 6 months, what has to be true for you to say this was worth it?”
- “What would you want to stop hearing from your team?”
- “What would you want to be confident about before the next audit?”
6) Offer a next step that feels safe (10 minutes)
The next step should be small, clear, and useful.
Example next step:
“Based on what you’ve said, the first thing I’d do is a quick review of your website and messaging, because it’s often the fastest way to improve lead quality and booked calls. It’s 30 minutes, you’ll get 3 quick wins, and if we’re not a fit I’ll tell you. Want to book that?”
Yes, it’s a marketing CTA.
But it works because it’s low friction and it gives them something concrete.
Copy/paste discovery call questions (MSP-friendly)
Use these as your “always ask” list.
- What triggered this search now?
- What’s the risk you’re trying to avoid?
- What’s currently working?
- What’s currently painful?
- What would make this a clear win in 6 months?
- Who else is involved in the decision?
- What’s the timeline?
- What would stop you moving forward?
Common MSP discovery call mistakes
- Turning it into a feature tour
- Asking lots of questions but never summarising
- Not naming risk
- Ending without a clear next step
- Sending a proposal when they’re still unclear
Key takeaways
- Discovery calls convert when they reduce uncertainty.
- Your job is to diagnose risk and define success.
- A safe, useful next step beats a vague “let’s chat again”.
Quick Q&A
How long should an MSP discovery call be?
45 minutes is a good default. Short enough to stay focused, long enough to get to the real issues.
Should you send a proposal after the first call?
Only if the prospect is clear on priorities, success criteria, and decision process. If not, you’re guessing.
What’s the best way to end a discovery call?
Summarise what you heard, confirm it’s accurate, then offer one clear next step with a defined outcome.
FAQ
What if the prospect won’t share details?
That’s data. They may be early-stage, or they may not trust you yet. Offer a smaller next step and earn it.
What if they want pricing immediately?
Give a range with assumptions, then bring it back to risk and scope. Price without context creates stalls.
A final thought
Most MSP discovery calls don’t fail because you said the wrong thing.
They fail because the prospect couldn’t see a safe decision.
Make the call about clarity, not performance.
If you want a second pair of eyes on your website and messaging, book a quick 15-minute call and I’ll give you 3 quick wins.
