Discovery is the real close

“What do I say when they tell me they’re not ready?”

I get some version of that question constantly from MSP sellers. They want the silver bullet: the line that works on “it’s more than I thought,” “I need to run it by my partner” and “we’re stuck in a contract.”

My answer is the same every time: whatever the prospect already told you in discovery. That answer gets me plenty of pushback and I understand why. How you close and how you handle objections at the end of the process matter. I’m not telling anyone to skip that work.

But I’ve reviewed thousands of sales calls, and most MSP deals are decided long before the proposal. They’re won or lost in discovery. When discovery is strong, the close feels almost anticlimactic. When it’s weak, that’s where the pipeline leaks, whether you’re running the deals yourself or you have reps running them for you.

Predictable objections are discovery problems

Listen to enough proposal calls and you notice something. When a rep asks for the sale, the objection that comes back is almost never a surprise. “It’s not the right time.” “It’s more than I expected.” “I need to check with my partner.” “We’re locked into a contract with our current provider.” You could write those on a whiteboard before the call starts. I’ve heard every one of them hundreds of times and so have you.

If an objection is that predictable, it was never a proposal-stage problem. It surfaced at the end because nobody dealt with it at the beginning. In most MSP sales processes, it goes unaddressed because discovery is spent on server counts, user counts, the current stack, the current provider and other details. Useful information, but none of it tells you why this person will or won’t sign, who else has a say or what it’s going to take to get a decision.

What discovery is actually for

Every question you ask in discovery should do one of five jobs: uncover pain, clarify the gap between where they are and where they want to be, establish urgency, map the buying process or gauge price sensitivity.

Do that well and you walk out of discovery with two lists. The first is every reason this deal will close: what’s driving them, what they want, how solving this moves their business forward. The second is every reason it won’t: the obstacles, the objections, the people who haven’t been in the room yet.

Most sellers never build the second list, and it’s the one that wins deals. When you surface an objection early, the prospect’s own answer becomes your rebuttal later. You’re using the front of the process to build everything you’ll need at the back of it.

Turn the objection into a question

Take “we’re not ready yet.” It comes up all the time. The prospect wants to change and has reasons to change, but the pain isn’t acute enough to act on. You get to the end of the proposal and hear, “This all sounds good, but we’re not ready to make a move.”

What could you have asked in the first meeting to handle that in the last one?

Try this: “What makes this a now conversation? Why not six months from now? Why not six months ago?”

You want them to say out loud why they’re in this process today. If the answer is that their current provider dropped the ball (slow response times, a client issue, a productivity hit) you now have ammunition. Write it down.

Then, when “we’re not ready” shows up at the end, you have something better than a canned comeback:

“I hear you. I’m a little confused, though. Earlier you mentioned response times were a problem, that it was distracting your team and a client got caught in the middle of it. You said those were priorities. Has something changed?”

Your best rebuttal is their own words, but you have to ask the question that produces them.

The cheapest time to have a hard conversation

It’s human nature to avoid tension, and most sellers do. They dodge the price conversation, skip the question about who else needs to sign off and push every uncomfortable topic to the end of the process and hope it doesn’t come up.

That’s expensive in two ways. A lot of the time, you never hear the real objection. The prospect ghosts you or says no without an explanation, and you don’t get the chance to address what actually killed the deal. When you do hear it, it’s often after the decision has already been made. They’ve met internally and talked it over. By the time they tell you, the conversation is a courtesy. You’re fighting from your back.

Compare that to discovery. The prospect is in Q&A mode. They’re sharing freely because you’re learning about their business and nobody has said a number yet. That’s the optimal moment in the sales process to put the uncomfortable stuff on the table because their guard is down and nothing has been decided. That window closes once they’ve seen the price and you’ve asked for the money,.

How to engineer it into your process

This takes four steps, and none of them requires a new methodology.

1. Write down your top five objections

Pull your lost and stalled deals. Read the transcripts. The same handful shows up for almost every MSP: price higher than expected, another decision-maker who needs to weigh in, timing, an existing contract.

2. Reverse-engineer each one into a discovery question

The objection you keep hearing at the end tells you exactly what to ask at the beginning.

For price: “What are you investing in IT today? Have you thought through what happens if solving this takes more than that?”

For the decision-maker who shows up at the eleventh hour: “When you’re working through challenges like this internally, who’s usually part of that conversation?”

For timing, the “why now” question above.

3. Ask them and capture the answers

Put the answers somewhere you can pull them up word for word six weeks later (your notes, the CRM, the deal file). Memory doesn’t count.

4. Recap before you leave discovery

Summarize what you heard: the challenges, the priorities, the stakeholders, the timeline. Ask them to confirm it. That recap is a trial close. You’re building agreement on the problem before you ever show them the solution.

The technical seller trap

This is where it breaks down for many MSP owners and engineers who sell. You already know the answers before you ask the questions. You know why they’re having outages, and you can probably guess what the current provider is doing wrong. The discovery work gets skipped, or it turns into a technical audit.

Worse, you start solving mid-conversation. The prospect mentions an outage and you’re already into licensing, cost savings and how you’d architect it differently. That’s prescribing before the diagnosis is done and it shuts the prospect up right when you need them talking.

Discovery is for finding problems, which means pulling information out of the prospect rather than pushing your expertise at them. The technical details will still be there next week. You can run a scan for specs. You can’t scan for why someone will or won’t sign.

What it looks like when discovery is done right

You get to the end of the presentation and ask if there’s any reason not to move forward. If something comes up, you’re answering with what they told you in the first meeting: the pain, the priorities, the words they used. There’s no silver bullet because you don’t need one.

When you do get blindsided, treat it as data. I’m always tweaking my own discovery process. Any time I hear an objection two or three times that I wasn’t prepared for, a question gets added to the front of the process.

Your action step this week

Pull the last five deals that stalled or died at the proposal stage. For each one, write down the objection that killed it, in the prospect’s words if you have them.

Then ask one question about each: “What could I have asked in discovery that would have surfaced this on day one?”

Those answers are your new discovery questions. Add them to the front of your process, and you’ll stop looking for a silver bullet at the end of it.

Related: Stop chasing dead deals: How to read your MSP prospects before they ghost you.