The MSP Discovery Call Roadmap: Why Your Prospects Leave Confused About Price, Timeline, and Next Steps (And the 5-Question Framework That Fixes It)

You sent a proposal last week. Good meeting, solid fit, the prospect seemed genuinely interested. Now it's been five days and your follow-up email is sitting on read. You're telling yourself they're just busy — but you've been here before, and you already know how this ends.

The ghost didn't start when they stopped responding. It started on the discovery call, when they left without a clear picture of what working with you actually looks like — what it costs, how long onboarding takes, what happens after they sign. They filled in the blanks themselves, and whatever they imagined was worse than the reality you never explained.

This post is about fixing that. Not with a better proposal template, not with a smoother close — but with a discovery call structure that builds conviction while you're still on the call together. Five questions, asked in the right order, that turn a prospect from "I'll think about it" into someone who understands exactly why they should move forward and what happens next.

Why MSP Discovery Calls Break Down Before the Proposal Even Lands

Most MSP owners run discovery calls the same way they'd run a technical intake for a new client: gather information, identify the problem, go build a solution. That's the right instinct for a helpdesk ticket. It's the wrong instinct for a sales conversation.

When you spend the whole call in information-gathering mode — asking about their current setup, seat count, what PSA they're running, whether they've had any incidents — you're doing something that feels productive but isn't. You're collecting data without creating understanding. The prospect answers your questions, you take notes, and then you disappear to write a proposal. From their perspective, nothing happened. They don't know what you think of their situation, whether you've seen it before, or what you'd actually do about it.

The prospect needs to leave the discovery call having made a small decision — not just having answered your questions. That decision might be as simple as "yes, I want to see a proposal" with genuine enthusiasm rather than polite obligation. But if they can't articulate to themselves why your MSP is the right fit, what the engagement would look like, and roughly what it's going to cost, they're going to hit the first moment of friction — a competing priority, a spouse asking questions, a slightly lower quote from another MSP — and disappear.

The 5-Question Framework That Changes What Happens After the Call

These aren't five questions to ask in rapid succession. They're five turning points in the conversation — each one shifting the prospect from passive to engaged, from uncertain to convicted.

Question 1: "What's actually driving this conversation right now?"

Not "what are you looking for in an MSP" and not "what's your current setup." Those questions let a prospect describe their situation without revealing what's actually at stake for them.

"What's driving this conversation right now" does something different. It surfaces the trigger — the thing that made them pick up the phone or fill out your contact form. And in MSP sales, the trigger almost always falls into one of three categories: a recent incident (ransomware, data loss, a compliance scare), a growth event (acquisition, new location, headcount spike), or accumulated frustration (current provider isn't responsive, they've outgrown break-fix, they're tired of being the de facto IT person).

The trigger tells you two things: urgency and emotional stakes. A prospect who just got hit with a ransomware attack on 40 seats is in a completely different buying posture than one who's "just exploring options." You need to know which conversation you're in before you say anything else.

Concrete takeaway: If the prospect can't name a clear trigger, they're probably not a serious buyer yet. That doesn't mean disqualify them — it means calibrate your investment in the call accordingly.

Question 2: "What would have to be true for this to be a priority in the next 30 days?"

This question does something most MSP owners are afraid to do: it surfaces the real timeline without you having to guess.

Prospects will tell you they're "ready to move forward" when what they mean is "ready to keep talking." The gap between those two things is where proposals go to die. This question forces them to think concretely about what has to happen — budget approval, a board meeting, end of a current contract — before they can actually make a decision.

If they answer clearly ("our current contract is up October 1st, so we need something in place by then"), you have a real timeline to work backward from. If they can't answer it, that's equally useful information — it means the decision is softer than it seemed, and your proposal is going to a drawer, not a decision-maker.

Question 3: "Have you worked with an MSP before — and if so, what made you leave?"

This is the question most MSPs skip because it feels risky. It's actually the most valuable thing you can ask.

If they've had an MSP before, the answer tells you exactly what they're afraid of repeating. Maybe the last provider went dark for 48 hours during a critical outage. Maybe they felt nickel-and-dimed on every out-of-scope ticket. Maybe the onboarding was a disaster and they never felt like the MSP actually understood their environment. Whatever the answer is, that's the thing they need to hear you address directly — not in the proposal, but right now, in the conversation.

If they haven't worked with an MSP before, you're dealing with a different challenge: they don't know what good looks like, so they're going to default to comparing you on price. That means your job on this call is to teach them what questions to ask any MSP they're evaluating — and make sure your answers are the ones that stick.

What most MSPs get wrong here: They hear the answer and immediately pivot to "well, we're different because..." and list their differentiators. That's too fast. Sit with what they said. Ask one follow-up: "How did that affect the business day-to-day?" Let them feel heard before you respond. The prospect who feels genuinely understood is the one who shows up to the proposal meeting.

Question 4: "Here's roughly what an engagement like yours typically looks like — does that match what you were expecting?"

This is where you stop gathering and start leading.

By this point in the call, you know their trigger, their timeline, their baggage from previous providers, and their current environment. You have enough to give them a directional picture of what working with you would look like — not a proposal, but a framework. Something like:

"Based on what you've described — 35 seats, no current documentation, a compliance requirement you need to meet by Q2 — here's typically how we approach this. First 30 days is a full environment audit and onboarding. That's where we build out your documentation, get everything into our PSA, and identify the five to ten things that need immediate attention. Months two and three, we're stabilizing and getting your team trained on the new processes. By month four, you're in steady-state management. On pricing, an environment like yours typically runs in the $X to $Y range per month all-in. Does that match what you were thinking?"

That last question — "does that match what you were thinking?" — is doing a lot of work. It invites them to tell you if there's a gap between your reality and their expectations. Better to surface a budget mismatch on the call than after you've spent six hours writing a proposal.

This is also the moment where you stop being a vendor and start being an advisor. You're not selling them something — you're helping them understand what the right solution looks like. That shift in dynamic is what separates MSPs who close at 40% from ones who close at 15%.

Question 5: "What would make you confident this is the right decision?"

This is the close — but it doesn't feel like a close. It feels like a genuine question, because it is one.

The answers you get here are your proposal blueprint. If they say "I need to see references from businesses our size," you know to include a case study from a comparable client. If they say "I need to understand exactly what's included and what's not," you know your proposal needs a crystal-clear scope section. If they say "I need my operations manager to be comfortable with the transition plan," you know there's a second stakeholder you haven't met yet who's going to weigh in.

This question also tells you whether you're the decision-maker's only conversation. If they say "I just want to make sure we're comparing apples to apples with the other quotes we're getting," that's important context. You're in a competitive situation. Your proposal needs to do more than describe your service — it needs to make the comparison easy and make you the obvious choice.

What Most MSPs Get Wrong on Discovery Calls

The single biggest mistake I see is treating the discovery call as a precursor to the real sales conversation — as if the proposal is where the selling actually happens. It's not. By the time a prospect opens your proposal, the decision is mostly made. The proposal either confirms what they already believe or creates doubt. It almost never converts a skeptic.

MSP owners who run great discovery calls send proposals that land in receptive inboxes. The prospect has already mentally committed. The proposal is a formality — a document that lets them justify a decision they've already made. MSP owners who run information-gathering calls send proposals into a vacuum and wonder why no one responds.

The other thing I see constantly: MSPs who avoid talking about price on the discovery call because they're afraid of scaring the prospect off. This almost always backfires. When you don't give a directional number, the prospect fills in the blank — usually with whatever the last MSP quoted them, or whatever they've budgeted, or whatever they've heard from a peer. If your actual pricing is higher than what they imagined, the proposal is a shock. If you'd named a range on the call and they stayed in the conversation, you'd know they were ready to have that conversation.

How to Think About This for Your Situation

If you're under $1.5M ARR and doing most of your own selling, the most important thing you can do right now is record your next five discovery calls and listen back to the ratio of questions you asked versus information you shared. Most MSPs are shocked to find they spent 70% of the call asking and 30% leading. Flip that ratio and watch your close rate move.

If you're at $2M to $5M ARR and you've handed off some of the selling to a sales rep or vCIO, these five questions are the foundation of a repeatable sales process. You can't scale what isn't documented. Build this into your call structure, train it, and review calls against it.

If your discovery calls are going well but proposals are still going dark, the problem might not be the call itself — it might be that you're getting qualified leads who aren't actually ready to buy yet. That's a lead quality issue, not a sales process issue. We wrote about why MSPs lose proposals they should win — and a lot of it comes down to who you're talking to before the proposal ever gets written.

And if you're not getting enough discovery calls in the first place, that's a pipeline problem. The best sales framework in the world doesn't help if your calendar is empty. That's a different conversation — one worth having directly if you're at the point where you're ready to build a predictable lead source instead of waiting on referrals.

The Prospect Who Ghosts You Already Made a Decision

They just made it without enough information, and they defaulted to "no."

The five questions in this framework aren't magic — they're a structure for making sure that by the end of your discovery call, the prospect understands your process, has a realistic expectation of cost, knows what happens next, and has told you exactly what they need to feel confident. When all four of those things are true, you don't need to chase proposals. You need to write them.

If you're running a 5–30 seat shop and your close rate on proposals is under 30%, the discovery call is almost certainly where the deal is being lost. A 30-minute call with our team is usually enough to identify exactly where the conversation is breaking down — and what to change first.