How MSP Discovery Reveals How Buyers Decide

Most MSP proposals fail not because they got the solution wrong.

They fail because they got the decision process wrong.

The rep understood the technical requirements. The scope was accurate. The pricing was competitive. The proposal was well-written. And it still went quiet — because nobody understood how this particular organization actually makes a purchase decision at this dollar level.

Discovery is supposed to answer that. Most of the time, it doesn't — because most Discovery processes are designed to surface requirements, not decision mechanics.

This post is part of the MSP Sales Discovery Masterclass, which covers the complete output-based Discovery framework for MSPs building scalable sales.

Requirements Don't Create Decisions

Here's the assumption that kills MSP proposals: if the buyer understands what they need and we can deliver it, they'll decide to buy.

That's not how organizational decisions work.

Organizations have requirements and they have decision processes. The two are related but not identical. A buyer can have a clear, acknowledged requirement for managed services — a real problem, a real budget, a real intention to solve it — and still not make a decision for six months because the decision process hasn't been navigated.

Decision processes involve people the rep has never spoken to. They involve approval cycles that the buyer's main contact may not have fully described. They involve competing priorities at the leadership level that the IT manager doesn't have visibility into. They involve internal consensus requirements that vary enormously between organizations.

A proposal that arrives without an understanding of all of that is being thrown over a wall.

Sometimes it lands on the right side. More often it lands in a pile of "things we need to get to eventually."

What Features and Proposals Can't Do

The instinct in MSP sales, once Discovery has identified a real requirement, is to build the best possible proposal and present it compellingly.

The proposal covers the solution, the scope, the pricing, the differentiators, the case studies, the onboarding process. It is thorough. It is professional. It is complete.

And it asks the buyer to do something the rep has never helped them prepare to do: take it through an internal process that the rep doesn't understand, to people the rep has never spoken with, for approval on a timeline nobody discussed.

That's not a proposal problem. That's a Discovery problem.

The proposal can only present information. It cannot navigate an organization's internal approval process. It cannot create champions who don't already exist. It cannot generate alignment between stakeholders who haven't been engaged.

All of that has to happen before the proposal is written — in Discovery.

What Discovery Must Uncover About Decision Mechanics

There are four dimensions of decision process that Discovery needs to surface before a proposal is worth writing.

Who is involved. Not just "who is the decision-maker" — the full picture of who has input, who has veto power, who needs to be informed, and who is a champion. In a small MSP customer, this might be the owner and a controller. In a larger organization, it could be a CEO, a CFO, a board member, and an IT lead, all with different levels of influence and different concerns.

How decisions at this level get made. Every organization has a process for approving significant expenditures. Some have formal procurement cycles. Some require board sign-off above a certain threshold. Some operate on annual budget cycles where anything not in this year's budget requires a budget amendment. Some are highly informal — the owner decides and that's it. You need to know which type you're dealing with.

What has to happen before a decision can be made. This is different from who's involved. It's the sequence. Does the IT manager present to the leadership team? Does the CFO need to run it by outside counsel? Is there an existing vendor relationship that requires a formal review process before switching? The sequence matters because it tells you how long this will actually take — and whether there are steps you can help the buyer navigate or anticipate.

What the internal timeline looks like. Not the timeline the buyer wants — the timeline their process actually creates. A buyer who says "we want to be up and running by September" but has a procurement cycle that requires sixty days of approvals and a board meeting in November doesn't have a September timeline. They have a conflict they haven't fully reckoned with yet. Surfacing that conflict in Discovery is more useful than agreeing to a timeline you'll never hit.

Stakeholders Who Never Appear in Early Meetings

One of the most common sources of late-stage surprises in MSP deals is a stakeholder who wasn't mentioned in Discovery and appears at the proposal stage with concerns that effectively restart the process.

The CFO who didn't know the engagement was this expensive. The operations director who has existing relationships with two of the vendors being displaced. The board member who tried a similar engagement at their last company and it failed.

These are not surprises that should exist if Discovery was thorough.

The question to ask directly, mid-Discovery, is: "When it comes time to make this decision, who needs to be involved that we haven't talked to yet?" That question surfaces stakeholders before the proposal, not after. It gives you the opportunity to engage those people — or at least understand their concerns — before the document is in their hands.

A follow-up worth asking: "Is there anyone who would need to approve this who might have reservations that we should understand?" That question is direct enough to feel slightly uncomfortable. It also produces some of the most useful intelligence in the entire sales process.

Timing and Decision Inertia

Organizational inertia is a real force.

Buyers who genuinely want to change providers, have budget, have internal alignment, and like your proposal still don't decide. Because deciding requires doing the thing — and doing the thing is disruptive, requires effort, and creates short-term risk in exchange for long-term benefit.

Decision inertia is why "not now" is the most common deal outcome in MSP sales. Not "no." Not "we chose someone else." Just: not now.

Discovery cannot eliminate inertia. But it can identify whether it's present and address it directly.

The urgency question — "if nothing changes in the next twelve months, what does that look like for your business?" — is partly a pain question and partly an inertia question. A buyer who can articulate real business consequence to inaction is a buyer with a reason to decide. A buyer who says "we'd probably just keep managing it ourselves" is telling you the inertia is strong and there's no cost to delay.

That's critical information. And it's information that only exists if Discovery asks for it directly.

How Proposals Fail Without Decision Intelligence

A proposal built without decision process intelligence is guessing.

It's guessing about who will read it. It's guessing about what objections will arise. It's guessing about whether the buyer has the internal capacity to push it through approval right now. It's guessing about what competing priorities might create friction.

Sometimes the guesses are right. When they're wrong, the deal stalls and nobody knows why.

Decision process intelligence changes the proposal from a guess into a document built for a specific journey.

If you know the CFO is the final approver and they care primarily about risk and cost of ownership, you write the proposal differently than if the owner is the approver and they care primarily about reliability and responsiveness. If you know approval requires a board presentation, you prepare supporting materials for that presentation. If you know the timeline is constrained, you build an onboarding schedule that shows how it fits.

None of that is possible without Discovery having surfaced the decision mechanics.

What Clear Decision Paths Enable

When Discovery produces a full picture of how the buyer decides, the proposal becomes the beginning of a managed close process — not the end of a Discovery process.

You know who needs to be reached before the presentation. You've already scheduled the CFO meeting, not just the IT manager meeting. You've identified the internal champion and equipped them with what they need to advocate internally. You've acknowledged the competing priority from six weeks ago and confirmed its status.

The proposal presentation is not a surprise for anyone in the room. Everyone involved has already been engaged. The document reflects what those conversations established.

That is a fundamentally different sales experience from "send the proposal and hope." And it produces fundamentally different results.

Owners who have been running Discovery at this level for years do this intuitively. They know to ask for access to the CFO. They know to inquire about the approval process early. They know that a deal where they've only ever talked to the IT manager is a deal with structural risk.

Making that intuition into a repeatable process — something a rep can execute consistently — requires defining it explicitly in the Discovery stage.

How to Build This Into Your Process

The changes needed are not complicated. They are just specific.

Add three questions to your Discovery stage that must be answered before a deal advances to Proposal:

First: "Who else needs to be part of the decision?" and document all names and roles.

Second: "How does your organization approve spending at this level? Walk me through the process."

Third: "What has to happen between today and a signed agreement? What's your internal sequence?"

These questions feel direct. They are direct. That directness signals that you take the buyer's time and your own seriously — you're not going to write a proposal and disappear. You're going to help them get from interest to decision.

Buyers who are serious about making a decision respond well to that framing. Buyers who aren't serious often reveal their lack of readiness when faced with it. Either way, you've learned something important before investing in a proposal.

Book a Discovery Review if your team is sending proposals that go quiet and you want a clear picture of what Discovery needs to produce before the next one goes out.

Frequently Asked Questions

What should MSP Discovery uncover about the buyer's decision process? Discovery needs to surface four dimensions of decision mechanics before a proposal is written: who is involved in the decision (including stakeholders who haven't appeared yet), how the organization approves spending at this level, what sequence of steps must occur before a decision can be made, and what the realistic internal timeline looks like given those steps. Without this intelligence, a proposal is guessing at the journey rather than being built for it.

Why do MSP proposals go quiet after being sent? Post-proposal silence usually indicates that Discovery didn't surface decision process information. The proposal arrived at an organization without an internal champion prepared to advocate for it, without key approvers having been engaged, or without alignment on a timeline that the organization's actual process can support. The proposal is sitting in a stack of "things to get to" because there's no internal momentum to move it forward.

How do MSPs find out who makes the buying decision? The most direct approach is to ask mid-Discovery: "When it comes time to make this decision, who needs to be involved that we haven't spoken with yet?" and "Is there anyone who would need to approve this who might have reservations we should understand?" These questions feel slightly uncomfortable — which is exactly why they're effective. Buyers who are serious about moving forward will answer them. Buyers who aren't will deflect, which is also useful information.

What is decision inertia in MSP sales? Decision inertia is the organizational tendency to maintain the status quo even when the buyer genuinely wants to change. It explains "not now" as the most common deal outcome in MSP sales. Buyers who can articulate real business consequence to inaction — "if this doesn't change in twelve months, here's what it costs us" — have a reason to overcome inertia. Buyers who say "we'd just keep managing it" are telling you inertia is strong and there's no cost to delay. Discovery surfaces this before a proposal is written.