Most MSP owners learn sales the hard way — by losing deals they thought were certain, sending proposals into silence, and eventually developing a gut feel for what works. The problem with gut feel is that it doesn't scale. When it's time to hire a salesperson or build a repeatable pipeline, instinct isn't enough.
The MSPs that close consistently have something the others don't: a process. Not a script — a structured approach to finding the right prospects, running conversations that surface real pain, and presenting solutions in a way that makes yes feel inevitable.
Most MSPs lose deals at stage two — discovery — because they treat it as a fact-finding call rather than a diagnostic conversation. The goal of discovery isn't to learn enough to write a proposal. It's to help the prospect understand the cost and consequence of their current situation in a way they haven't articulated before. A well-run discovery call doesn't just qualify the prospect — it creates the urgency to act.
Generic discovery questions ("What are your biggest IT challenges?") produce generic answers. The questions that move deals forward are specific, layered, and focused on consequence — not symptoms.
Start by establishing the current state: what does their environment look like today, and how long has it been that way? Then move to impact: what has the current situation actually cost them — in downtime, staff frustration, compliance exposure, or missed opportunity? Then future state: what would a well-functioning IT environment enable them to do that they can't do now?
The most powerful discovery question most MSPs never ask is: "What happens if this doesn't change in the next 12 months?" It forces the prospect to connect their current pain to a future consequence — and that connection is where buying motivation lives.
Most MSP proposals are feature lists with prices attached. The client opens them, skips to the bottom, and either flinches at the number or sends it to three competitors to compare. That's not a proposal — it's a quote.
Winning proposals are structured around the prospect's words, not your services. Open with a summary of their situation as you understood it from discovery — their pain, their risk, what it's costing them. Then present your solution as a response to that specific situation, not a catalogue of what you offer. Close with a clear next step, not an open-ended "let us know."
The format matters less than the sequence: problem → consequence → solution → investment → next step. If your proposal can be swapped in for another MSP's proposal by changing the logo, it isn't doing its job.
Sales in managed services is a trust business. Clients are handing over the keys to their infrastructure — they need to believe you understand their world before they'll let you into it. A strong process doesn't make you less human. It makes you more prepared to have the kind of conversation that earns that trust.