As an MSP, ask yourself: Would your business—and your clients’ businesses—be better off with a higher level of standardization?

Industry expert Gary Pica says the answer is almost unanimously ‘yes’ when he poses that question. Yet, not everyone does something about it. Why?

Many times, it’s a matter of the tools and resources required to make it happen. In part four of his series 5 Qualities of a World-Class MSP, Gary shares clear and easily doable steps for what he dubs “the process for the process.”

ConnectWise TV 1280 by 769 brightcove player size. Aspect Ratio of 16 by 9 screen. This fits a 1280 by 720 pixels video


He begins with these pointers for leveraging process to deliver superior business results:

  • Establish a culture of process that involves your entire team; let them be part of deciding best practices and delivering on them.
  • Be sure the processes are ‘alive’ or improvable as necessary.
  • Institutionalize your process knowledge with documentation that is kept current.
  • Regularly train employees on processes.

Gary advises that, to begin a process for standardizing implementation across your company base, you must ‘build your company way’ in four basic delivery areas: centralized services, reactive support, vCIO, and network administration.

Define Standards

Most MSPs have a definition of their standards, but they’re not organized in a way to deliver consistently. Ask yourself how the technology or environment should be configured for your clients, why you’re setting that standard and what’s the risk to the client if those standards aren’t met.

Think in terms of a hierarchy: topline areas where you’d like to set standards and then break down the details, which often entails thousands of specific questions.

Align Clients

Technical alignment is the objective analysis of aligning your clients’ technology against your company standards. Typically, this task is performed by Network Administration. Remember, this is a time to align, not fix or make changes. Try to be direct with yes/no questions during this process. For example, one question may be: Are complex passwords turned on or off?

Determine Business Impact

Once you know where clients fall within your standardization guidelines, it’s time for the consulting process. The vCIO looks at what’s out of alignment—as well as the business impact it might have on the customer— and makes recommendations.

Take the above example of complex passwords being on or off. In some businesses, like a flower shop, standardization may have no real impact. But in the case of legal or medical clients, the impact could be huge.

Develop Client Strategy

The vCIO uses this impact information to create and propose long-term strategies for clients, a key step in building an MSP’s position of value. Avoid presenting an overwhelming stack of reports or tickets supporting your findings. Instead, provide summary information that lets your customer know where they’re exposed and what business decisions should be considered.

The benefits of process-driven standardization pay off quickly in more predictable IT operations and less reactive service. Providing consistent delivery of your knowledge and experience to every client creates profitable results both of you can bank on.

Learn more proven methods for becoming a world-class MSP from Gary Pica, Founder & CEO of TruMethods, an MSP training company.

The Insider’s Guide to Sales Transformation

You don’t have to be a multi-million dollar company to run a powerful sales machine. Learn the easy steps for transforming your sales process, so that everybody wins.

Get the eBook

Mark Sokol

Mark Sokol

Mark is the VP of Product Marketing and Branding at ConnectWise. He has over 20 years of experience with software and technology companies, helping them grow business and improve bottom-line performance. He has successfully developed...

View Full Profile | Mark Sokol's LinkedIn

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>