The questions an IT or MSP rep asks on the first call shape most of what follows: who gets looped in, what gets proposed, and whether the prospect can justify switching internally. This guide covers the diagnostic questions worth practicing and the follow-up habit most reps skip. It is written for MSP sales leaders and the reps who run discovery.
Why discovery quality decides the rest of an MSP deal
Discovery quality decides far more than the discovery call. In a long-cycle MSP sale, everything downstream, who gets looped in, what gets proposed, whether the prospect can justify switching internally, rests on what surfaces in that first conversation. Most MSP purchases involve several stakeholders, and none of them were on it.
Weak discovery doesn’t just waste that first call. It sets the whole deal up on the wrong foundation.
Diagnostic discovery, questions built to expose real gaps in a prospect’s current environment rather than confirm what they already believe, is the specific skill this depends on. Reps who ask surface-level questions get surface-level answers, and surface-level answers don’t justify a switch to anyone in the buying group who wasn’t on the call.
The discovery questions worth practicing
Good discovery in an IT or MSP sale usually covers the same set of gaps. How often has the business had downtime, and what did it cost? What security weaknesses exist, and how were they found? How do response times compare with what the incumbent delivers? Which scaling limits will the prospect hit soon? Each question should surface a gap the prospect feels, not one they simply agree with.
The harder skill is the follow-up. A first question that gets a vague answer needs a specific follow-up that turns a general statement, “we’ve had some downtime issues”, into a quantified business cost. That follow-up instinct is what most reps haven’t practiced enough to execute reliably live.
Why reading a discovery framework isn’t the same as running one
A list of discovery questions is easy to write and hard to use in a real call, where the prospect is guarded, short on time, or gives a vague answer that needs a sharper follow-up. AI roleplay lets reps practice exactly that, against a persona built on your real ICPs.
Those personas cover the people reps face: business owners, IT leads, CFOs. Feedback arrives after each attempt. The product tour covers how personas are generated and how difficulty and mood adjust as a rep’s discovery skill improves.
With FunnelX, a rep can run the same discovery call again and again, with the prospect answering differently each time. That repetition turns a discovery framework from a document reps look up into questions they ask without thinking. It also builds the follow-up habit for when the first answer gives them little to work with.
What the broader data says about discovery quality
Discovery isn’t a soft precursor to the real selling; it’s frequently the deciding factor. Win-loss research from Thirdside found that 65% of lost B2B deals involved buyers saying sales didn’t do enough discovery, not price or product fit. In a long-cycle MSP sale where the first discovery call sets the trajectory for a multi-month process, that gap compounds every time it’s repeated across a pipeline.
Gong’s own analysis of over 500,000 discovery calls found top reps ask 11 to 14 questions per call, about twice as many as average reps, spread through the conversation rather than bunched at the start. The number matters less than what it allows. Reps who ask more questions get more chances to follow up on a vague answer instead of moving on, and that is the habit MSP discovery depends on.
How this connects to the buying committee reps are navigating
MSP prospects rarely decide alone. Gartner puts the average enterprise buying committee at 6 to 10 people, each with different priorities. An IT lead worries about migration risk. A CFO focuses on total cost. A business owner cares most about downtime.
Diagnostic discovery is what tells a rep which of those concerns is live in this specific deal. That’s the information that should shape everything from who else gets looped into the sales process to how the eventual proposal gets framed.
The follow-up is where most reps fall short
Reviews of lost deals keep finding the same pattern. The rep asks a good first question, the prospect gives a partial or vague answer, and the rep moves straight on instead of following up on what was just said.
A prospect who says “we’ve had some downtime issues” has handed the rep an opening. A rep who doesn’t follow up with “how much did that cost you, in hours or dollars” has let a diagnosable gap go unquantified.
This same instinct, treating a vague answer as unfinished business rather than a checked box, is what makes the 24-scenario objection framework effective. Objections and discovery gaps are the same underlying skill applied at different points in the call.
That instinct is the specific behavior worth practicing repeatedly, not the initial question list, which most reps already have memorized.
What happens once reps are asking these questions live
Even well-practiced reps hit discovery calls where a prospect’s answer opens up a gap no scenario fully anticipated. FunnelX’s live call coaching, Co-Pilot, flags discovery gaps in real time during the actual conversation, keeping discovery moving with suggestions grounded in your sales methodology. Post-call, reps can review the conversation with an AI coach and see, scenario by scenario, which discovery questions landed and which need more practice.
Frequently asked questions
A diagnostic question is built to expose a gap the prospect hasn’t fully quantified, downtime cost, security exposure, response time gaps, rather than confirm information the prospect already states openly.
Enough that the follow-up instinct, not just the initial question, feels automatic. Most reps need repeated practice across different prospect personas and moods to build that instinct reliably.
Yes. AI buyer personas and discovery scenarios are built from your company’s actual ICPs and knowledge base, so reps practice questions relevant to your specific managed services, not generic IT discovery.
Co-Pilot supports discovery calls directly, flagging discovery gaps and keeping the conversation moving with suggestions grounded in your methodology, in addition to later-stage coaching.
Win-loss research shows 65% of lost B2B deals involved buyers saying sales didn’t do enough discovery, ahead of price or product fit as a loss reason.
Not following up on a vague or partial answer. A prospect’s incomplete response is usually an invitation to dig deeper, and reps who move straight to the next question instead leave the actual gap unquantified.
Keep reading
How AI roleplay helps MSPs sell managed services instead of just price, Ramping new IT and MSP account executives without burning out senior reps, and 12 MSP and IT roleplay scenarios.