How to Run an MSP Client Discovery Call

Share this post on:

A good MSP discovery call is a diagnostic conversation, not a pitch. Your goal is to learn how the business runs, where technology helps or hurts, and whether you are a fit. You should do most of the listening, leave with a clear picture of the client’s problems and priorities, and know whether to write a proposal at all.

Many MSPs waste their best chance to win a client by launching into a slide deck about their stack. Prospects do not buy stacks. They buy relief from a problem and confidence in the person who will solve it. This guide gives you a structure for discovery that builds trust, surfaces real needs, and produces better proposals.

What Discovery Is Really For

Discovery has three jobs. It uncovers what the prospect actually needs, which is often different from what they first asked for. It tells you whether the account is a fit for your services, your pricing, and your team. And it starts the relationship on the right footing, with you as an advisor rather than a salesperson. If you skip discovery and jump to quoting, you are guessing, and guesses lead to underpriced agreements and unhappy clients.

The vCIO mindset applies here too. The best discovery calls look like the first step of a roadmap, not the last step of a sales cycle. If you want to understand that mindset, start with what a vCIO is and why the role matters.

Before the Call: Prepare for Ten Minutes

You do not need hours of research. Spend ten minutes on the basics. Look at the company’s website, its size, its industry, and any public news. Note regulations that likely apply, such as healthcare, finance, or defense contracting. Check who you are meeting and their role. If the call was booked through a form, read what they wrote and note the exact words they used to describe their problem. Then write down three questions you want answered before the call ends.

Open With Their Story

Start by asking the prospect to tell you about the business and what prompted the call. Skip the tour of your company. Something like, “Tell me about what is going on with your technology and why now?” lets the prospect set the tone. Listen for the trigger: a bad outage, a departing IT person, a failed audit, growth, or a frustrating provider. The trigger tells you what matters and how urgent it is.

The Questions That Matter on an MSP Discovery Call

Organize your questions around six areas.

  • The business: What do you do, how many people work here, how many locations, and how is the company changing?
  • The current state: Who supports your technology today, what is working, and what is not?
  • The pain: When did technology last stop the business from working, and what did it cost?
  • The risk: Are there contracts, insurance policies, or regulations that require specific controls?
  • The people: Who makes decisions, who uses the systems, and who cares most about the outcome?
  • The plan: What would a good result look like in twelve months?

Follow each answer with “Tell me more about that.” The second answer is usually the useful one.

Quantify the Pain

Ask about the cost of problems in the prospect’s own terms. If a system was down for a day, how many people could not work? What did that cost in wages, missed orders, or delayed shipments? You are not building a sales argument. You are helping the prospect see the real stakes so they can decide how much to invest. When the cost of an hour of downtime is clear, a monthly service fee looks different.

Listen for Red Flags

Discovery is also your chance to decide whether you want the account. Warning signs include an owner who wants enterprise results at a bargain price, a history of switching providers every year, resistance to basic security requirements, and a refusal to give you access to information you need. It is better to walk away or set firm terms than to sign a client who will lose you money and morale. Your questions should reveal enough to make that call.

Handling Common Objections During Discovery

Prospects raise concerns early, and discovery is the right time to hear them. If they say the last provider overpromised, ask what specifically went wrong and what they would need to see to trust a new one. If they say they cannot afford a managed service, ask what one bad week of downtime would cost and what they spend now on break-fix. If they say they only need help with one thing, ask what happens to the rest of the environment while you fix it. You are not arguing. You are helping them think through the whole picture, and their answers show whether the relationship can work.

Be Honest About Fit

Tell the prospect what you do well and what you do not. If their needs fall outside your specialty, say so and, if you can, point them to someone better suited. This costs you one deal and earns you trust that often returns as a referral. Prospects notice when a provider is willing to say no.

Close the Call With a Clear Next Step

End by summarizing what you heard in a few sentences and asking whether you got it right. Then propose the next step, which may be a walkthrough of their environment, a technical assessment, or a written proposal. Give a date. Send a follow-up email within a day that repeats your summary and confirms the next step. A prospect who reads their own words back to them feels understood, and that feeling wins more deals than any feature list.

A Simple Note Template

Keep the same structure for every call so notes are easy to compare and hand off. Record the trigger, the current provider, the number of users and locations, key systems, compliance needs, the decision maker, the budget signal, the timeline, and two or three direct quotes from the prospect. Add a line for red flags and a line for the agreed next step. The quotes matter most, because they let you echo the prospect’s own words in the proposal and the follow-up.

Turn Discovery Notes Into a Better Proposal

Use the prospect’s language in your proposal. If they said they were tired of surprises, write about predictability. If they mentioned a customer security questionnaire, address it directly. Tie each part of your scope to a problem they described. A proposal built from discovery feels like a solution, not a price list, and it shortens the path to yes.

Common MSP Discovery Call Mistakes

  • Talking more than half the time.
  • Pitching tools before understanding the problem.
  • Meeting only with the person who booked the call and never the decision maker.
  • Failing to ask about budget and timing in a natural way.
  • Skipping written notes and forgetting the details later.

Discovery for Existing Clients

The same approach works inside a current relationship. Before a renewal or a major project, hold a short discovery session with the client to learn what changed. New leadership, new customers, and new regulations all shift what they need. A vCIO who does this every year keeps the relationship fresh and finds opportunities that clients value instead of resent.

Related Reading

For the advisory side of the story, see what a vCIO is and why the role matters and the vCIO services hub.

Frequently Asked Questions

How long should an MSP discovery call last?

Thirty to sixty minutes is typical. Shorter calls rarely go deep enough, and longer ones tire the prospect. Plan a follow-up if you need a technical walkthrough.

Who should attend a discovery call?

The person who decides on spending should attend, along with someone who understands daily operations. On your side, bring a person who can speak to both strategy and technical detail.

Should you talk about pricing in discovery?

Talk about budget expectations and what matters most, but hold detailed pricing for the proposal. Ask what range would feel reasonable so you can decide early if the account fits.

What questions should you ask a prospect?

Ask about the business, their current support, the last time technology caused pain, any regulatory needs, who makes decisions, and what success looks like in a year.

How do you know when to walk away from a prospect?

Walk away when expectations and budget cannot be reconciled, when the client refuses basic security or access requirements, or when the history suggests they will not value the relationship.

About Brent Lacy: Brent Lacy is a technology advisor and the voice behind Rewired MSP. He helps MSPs operate with greater maturity and helps business owners make IT choices that make them more secure and more efficient. He is the author of Out of Cycle: A Field Guide to Strategic IT Continuity, vCIO Rewired: Virtually Conquering IT Obstacles, and Near Miss: Preventable IT Failures Threatening Your Business Security.

Share this post on:

Author: Brent Lacy

Brent Lacy is the founder of Rewired MSP and author of three books on managed services, vCIO strategy, and cybersecurity. He helps MSP owners build trust-based, scalable businesses through documented processes, strategic leadership, and client-first culture.

View all posts by Brent Lacy >

Leave a Reply