Skip to content
Menu

Buying Committee: Find Who Else Must Approve Your MSP Deal

Map the buying committee in an MSP deal with exact questions and replies. Confirm each reviewer’s concern and next step before sending the proposal.

MSP sales colleagues review a buying committee contact map and CRM record before preparing a proposal.

Start with: “Before I prepare the proposal, who else needs to check that this will work for your business, and what will they need from us?” Record that buying committee in the opportunity, with the question each person must resolve. Then agree how your current contact wants to involve them.

My view is that a stakeholder map earns its place only when it changes your next conversation. A collection of names from a website is a research list. Ask the buyer to confirm who influences the decision and who can actually approve the commitment.

Map the Decision With Your Current Contact

Say: “Which people need to review the proposal before it can be approved?” Ask how their responsibilities fit together at this business. A person may hold several of them, or another reviewer may need to be involved.

Follow with: “When you take this forward internally, what questions do you expect people to ask?” That helps you prepare information the contact can use. It doesn't require them to disclose confidential internal discussions or turn them into your unpaid salesperson.

Ask permission for an introduction rather than approaching another stakeholder behind the contact’s back. Try: “Would it help to discuss that with them together, so you don't have to relay the technical answer?” Give the contact a reason to include the person and agree the route.

The roles below are useful examples to check, rather than a mandatory organization chart. Plan the relevant conversation with whoever holds the responsibility. You can cover several roles in an agreed joint meeting if that suits the buyer.

Ask the Owner What They Are Approving

Use this opener: “What needs to be different for the business for you to consider this service worth approving?” Connect the answer to the scope your MSP can deliver. Keep their stated priority with the opportunity so the proposal answers it directly.

If the answer is “I just want IT handled,” ask: “Which decisions do you want us to take off your desk, and which do you want to keep?” A preference for less involvement still needs agreed authority. Don't translate it into permission for every change your technicians might recommend.

Then confirm the approval route: “Once the scope and cost are clear, what happens before someone can sign?” Record any further review the owner names. A job title doesn't tell you whether a board or another authorized person must also approve the agreement.

End with a specific next step: “I'll show you how this covers that priority. Who should review the operating details before we return to you?” That carries the business requirement into the next conversation without assuming approval has already been given.

Ask the Office Manager How the Service Must Work

Start with: “What happens when someone needs IT help today, and which part makes your work harder?” Let them describe the actual request path. Check the routine your MSP would need to support rather than arriving with a portal demonstration and calling it discovery.

Ask: “If we change that process, what will staff need to know before they can use it?” Confirm who can coordinate the communication and any training. The office manager may understand the practical obstacles while another person still owns the change decision.

For a proposed reply to a concern about disruption, say: “Let's find the step that would trip your team up. We can explain the transition for that part and check it with the person who would use it.” Have the delivery lead assess the answer before promising an effortless transition.

End by confirming the operating detail to include in the proposal. Use: “Have I understood the support route you need, and who else should check it?” Record the correction if their answer differs from the sales handoff you had prepared.

Ask Finance What It Needs to Review

Use this opener: “What information will you need to assess the continuing fee and any separate project cost?” Explain the price in the units the buyer needs to evaluate. Keep the internal seat calculation available without making finance reconstruct the whole monthly commitment from a rate alone.

Ask: “Is there a budget or approval condition we should understand before finalizing scope?” If they identify a gap, check whether it concerns the amount or what they believe the offer includes. A request for more detail isn't permission to assume that only a lower price will resolve it.

Know your commercial boundary before this discussion. The model’s US seat floor is $150, a danger line rather than the target price. Don't work backward from a late approval objection into a fee below the floor while leaving the same service commitment in place.

Confirm the next finance action in plain language: “I'll send the scope and cost breakdown we talked through. Who reviews that next, and what would stop it moving forward?” Keep the answer with the agreed decision route rather than treating an emailed price as a completed review.

Handle a Restricted Introduction Without Pressure

What do you say when your contact wants to handle every internal conversation? Say: “Understood. What should I give you to answer their questions, and when would you like us to check what is still unresolved?” Respect the route they choose and keep the next step explicit.

If the contact says, “I make the decision,” reply: “Thanks. Is there anyone who still needs to check implementation or the agreement before you can approve it?” If they confirm there's nobody else, record that as their answer. A later delay doesn't prove they were dishonest.

I don't buy generic sales advice to go around the person who can't sign. In an MSP deal, that person may be responsible for making the service work after signature. Bypassing them can leave their operating concerns unanswered even if you reach the budget owner.

Make the Opportunity Record Useful

Keep a short decision record in the CRM. The proposed fields are:

  • Name the confirmed stakeholder and the decision or review they own.
  • Record the concern in their own terms, with the evidence or answer they requested.
  • Name the MSP person responsible for providing that answer.
  • Record the agreed next action and its date.
  • Keep approval status separate from a meeting held or an email sent.

When concerns conflict, bring the difference back through the agreed buyer contact. A finance requirement for a lower commitment may conflict with an operating requirement for broader support. Ask the authorized buyer to resolve the priority rather than promising each person a different service.

Ray J. Green recommends distinguishing follow-up that obtains an explicit decision from deals that merely age into a lost status in the CRM. That is a practitioner measurement suggestion. Use a clear refusal to close the opportunity honestly, without treating every unanswered message as an objection you have decoded.

Before sending the next proposal, check who has confirmed the decision route and which question remains open. Arrange the relevant conversation through your contact or provide the answer they have asked to carry internally. Let the proposal reflect a service the buyer can evaluate and your MSP can deliver.

Written ByNatalie Brandt

Staff Writer, Sales. Natalie Brandt covers sales for MSP Outpost: prospecting, discovery, proposals and closing, written for people who sell managed services, not software.

More by Natalie

mspoutpost.com/articles/buying-committee-find-who-else-must-approve-your-msp-deal

Written by Natalie Brandt
MSP Outpost publishes information, not legal, financial, insurance, tax or compliance advice, and reading it creates no professional relationship. For decisions about your business, talk to a qualified professional.

Sources1
  1. Practitioner follow-up measure: Ray J. Green recommends examining how often follow-up obtains an explicit yes-or-no decision from a prospect, separately from deals that merely age into a CRM loss status. He treats a clear refusal as closure of the cotranscripts.captivate.fm

Welcome Back

Sign in to your MSP Outpost account.