Your MSP Sales Rep Is Asking Questions but Never Finding Pain

Updated

Originally published

Listen to this article

Browser text-to-speech

AuthorCarrie Richardson, Co-Founder, Fox & Crow Group

If your rep leaves an MSP sales discovery call with pages of notes but cannot explain what the problem costs the prospect in time, money, customers, or risk, discovery failed. Most weak discovery calls break at the same moment: the rep gets a useful answer and moves on before the business consequence is clear.

This is Problem #4 in our MSP Sales Coaching series: weak discovery and failure to monetize pain. The CRM can fill with notes while the rep still cannot explain why the prospect would spend money to change the current situation.

That gap is visible in the call. It is also coachable.

Video: Why Your MSP Sales Rep Keeps Missing the Real Problem

Watch how to coach an MSP sales rep who moves on after a prospect describes a real problem. Review the moment the rep changes subjects, then practice the follow-up questions that uncover the business consequence.

Watch this MSP sales discovery video on YouTube.

MSP Sales Discovery Contents

MSP Discovery Fails When the Rep Keeps Moving

Newer reps often treat discovery like a tour of the prospect's environment. They ask about the help desk, backups, cloud applications, hardware, security, and projects. The prospect answers. The rep writes it down and moves to the next topic.

The call can cover a lot of ground without uncovering a reason to buy.

If the prospect says the current provider is slow when something serious breaks, your rep does not need another topic yet. They need to know what happened the last time support was slow, how long the problem lasted, who could not work, and what that interruption prevented those people from doing.

The technical complaint is only the starting point. The coaching job is to help the rep stay with it until the buyer can describe the business consequence.

One MSP Buyer Pain Thread Is Enough if Your Rep Follows It

A pain thread starts with something the prospect already said. Once your rep hears a real problem, they should stop surveying the environment and follow that problem.

Start with the most recent incident:

"That sounds important -- tell me the most recent time it happened."

Then establish frequency and duration:

"How often does that happen? And how long does it last each time?"

Then find out who is affected:

"Who on your team has to stop work when this happens? How many people?"

Those answers tell your rep whether the problem is occasional background irritation or something the business keeps paying for in lost time, delayed work, risk, or missed revenue.

One pain thread is enough if the buyer cares about it and the rep follows it far enough to understand the consequence.

Turn the MSP Buyer's Technical Problem into Business Cost

The next question should come from the answer the prospect already gave. Your rep should not read a pain script at them.

When the prospect describes an interruption, ask:

"What does that interruption prevent them from doing? Give me one concrete example of revenue, billable hours, or a customer outcome that was lost because of it."

If the prospect can support a financial measure, keep going:

"Rough ballpark -- what's the average revenue per affected deal or customer?"

If staff time is the clearer measure:

"What's the average hourly rate of the people pulled off revenue work?"

The rep can also follow business risk or opportunity cost when that is what the buyer cares about. The source of the math has to be the prospect. Do not manufacture an annual loss because the proposal needs a bigger number.

When the prospect can support both sides of the comparison, the rep can ask:

"So your annual loss from this is roughly $X. We can solve it for about $Y/year -- does that math make sense to you?"

If the prospect cannot support a dollar figure, keep the consequence in terms they can support. Lost staff time, delayed customer work, business risk, or work the team could not complete still gives the buyer a reason to decide whether the problem is worth fixing.

The MSP CRM Should Show Why the Prospect Would Change

After discovery, you should be able to open the CRM and understand the business problem without asking the rep to retell the whole meeting.

The record should show:

  • the pain the prospect described;
  • the most recent example;
  • frequency and duration where known;
  • the people or business functions affected;
  • supported dollars lost, risk, or opportunity cost;
  • the buyer's reason to change, or the reason the current pain is not enough to justify a change;
  • the next step and who needs to attend it.

A CRM note that says "slow support," "security concerns," or "unhappy with current provider" does not give you enough information to coach the deal. You need the event, the consequence, and the buyer's own reason to care.

In Fox & Crow's operating model, the account becomes an opportunity after the first-time appointment has happened, the decision-maker is identified and engaged, and environment, pain, timing, and fit are confirmed. If discovery supports moving forward, the next step should include the person who can approve the spend.

MSP Discovery Checklist: Did Your Rep Find Pain or Collect Trivia?

Pull the recording and inspect what the rep did after the prospect mentioned a real problem.

  • Did the rep jump to a new topic?
  • Did they ask for the most recent example?
  • Did they establish frequency and duration?
  • Did they learn who was affected?
  • Did they connect the problem to hours, dollars, lost customers, risk, or opportunity cost using information the prospect could support?
  • Did they calculate the business impact in the room when the numbers were available?
  • Could the rep explain why the prospect would spend money to change the situation?

The first missing piece is the coaching target.

Telling a rep to "ask better discovery questions" gives them nothing specific to practice. Find the exact moment where they left the pain thread and coach that behavior instead.

What to Coach Your MSP Sales Rep on Tomorrow

Choose one recording where the prospect mentioned a real problem and the rep changed topics too soon. Play the call until that moment and pause it.

Ask the rep, "What did you hear?" Then ask, "What could you have done differently?"

Role-play the same moment. You play the prospect. The rep has to stay on that issue until they can establish the recent example, frequency or duration, who is affected, and one supported business consequence.

Then give the rep a next-call test:

On the next discovery call, when the prospect gives a real pain signal, stay on that one thread until those four pieces of evidence are clear before changing topics.

After the call, inspect the recording and the CRM. The recording should show whether the rep stayed with the pain. The CRM should show what the rep learned.

If the evidence improved, keep the behavior. If it did not, replay the miss and run the same drill again. The rep owns the next attempt; you own the review.

MSP Sales Process includes AI call auditing, call scoring, auto-assigned learning paths, and weekly coaching focus from call scores. Call evidence can surface the moment the rep left the pain thread. You still decide which behavior gets coached next.

Schedule your free MSP Sales Diagnostic.

MSP Sales Discovery FAQs

What is MSP sales discovery supposed to accomplish?

MSP sales discovery should establish what business problem exists, what happened the last time it occurred, how often it happens, who it affects, and what consequence the prospect can support. The rep should leave able to explain why the prospect would spend money to change the current situation.

Why do surface-level discovery questions lose MSP deals?

Surface-level discovery questions collect facts without giving the buyer a business reason to change. If the rep keeps moving after a painful answer, the meeting may cover plenty of technical ground while leaving the cost, risk, or lost opportunity unexplored.

How deep should an MSP sales rep follow one pain thread?

An MSP sales rep should follow one pain thread until the recent example, frequency or duration, affected people, and business consequence are clear. If the prospect can support a financial measure, the rep can quantify the impact in hours or dollars. If not, keep the consequence in the buyer's own measurable terms.

How should an MSP sales rep quantify business pain?

Use numbers the prospect can support: staff hours, billable time, delayed customer work, lost revenue, business risk, or opportunity cost. Keep the assumptions visible. Do not invent a dollar figure to make the proposal look stronger.

What should an MSP owner coach after a weak discovery call?

Find the first pain signal the rep abandoned. Replay that moment, ask what the rep heard, role-play the follow-up, and make the next discovery call the test. The rep should stay on one pain thread until the business consequence is clear, then document the evidence in the CRM.