Standardizing the Tools Clients Run So You Stop Supporting a Zoo

Published by
Throne of Profit Editorial

Reviewed by
William Hassell
Founder & Chief Editor, Throne of Profit

Every MSP starts by saying yes. A new client runs a different antivirus, a different backup tool, a different remote-access agent, a different password manager — and to win the deal, you agree to support all of it. Do that a dozen times and you're no longer running a managed services business; you're running a museum of every vendor decision your clients ever made. The cost of supporting software doesn't add up client by client — it multiplies, because every different tool is another thing every tech has to learn, patch, troubleshoot, and keep in their head.

The trap is that each individual yes feels harmless. Supporting one more backup product seems like a small favor. But your team pays for that favor on every ticket, forever, because now they're context-switching across ten tools that do the same job instead of getting fast and deep on one. Standardization isn't about being rigid — it's about refusing to let your margin leak into a zoo you built one exception at a time.

   SUPPORT COST vs. TOOL SPRAWL

   standard stack   ▇▇                  → deep expertise, fast tickets
   some variance    ▇▇▇▇▇               → slower, more escalations
   full zoo         ▇▇▇▇▇▇▇▇▇▇▇▇▇▇      → every ticket is a first-time job
                    └─ each new tool multiplies, not adds

Owner symptoms

  • Techs spend as much time figuring out which tool a client uses as fixing the problem.

  • The same class of issue takes wildly different effort depending on which client called.

  • Only one or two people know how to handle certain clients' odd tools, and you dread when they're out.

Why this happens

Sprawl accumulates quietly through the sales process and inheritance. You onboard clients who already run whatever they bought before you showed up, and you agree to keep it to close the deal. Every "we'll support what you have" adds a permanent line to the list of things your team must master. Nobody ever decides to support fifteen backup products — it just happens one accommodating yes at a time, and because no single yes looks expensive, the total cost stays invisible until your techs are drowning in variety.

Common mistakes

  • Selling on flexibility — competing by promising to support anything the client already runs.

  • Never defining a standard stack, so there's nothing to converge toward.

  • Treating inherited tools as permanent, instead of as things to migrate off over time.

  • Grandfathering every exception forever rather than setting a sunset date.

  • Underpricing non-standard clients, so the extra support cost comes straight out of margin.

Business consequences

A sprawling stack quietly eats the thing an MSP sells: efficient, repeatable support. When every client runs different tools, your team can't build deep expertise, can't script common fixes, can't hand tickets off cleanly, and can't onboard new techs quickly — because there's no "the way we do it," only a hundred special cases. Tickets take longer, escalate more, and depend on a few people who happen to know a given client's setup. The MSP that converges its clients onto a standard stack gets the opposite: fast tickets, interchangeable techs, automatable fixes, and a support cost per client that actually goes down as the base grows instead of climbing with every new logo.

How experienced operators think about it

They treat the tool stack as a product decision, not a client preference. The mental model is leverage: one tool used across every client compounds — every hour spent mastering it, scripting it, or documenting it pays off on every account. Ten tools doing the same job compound nothing. So they define a standard stack deliberately, sell it as the offering rather than bending to whatever the client already owns, and treat inherited tools as a migration backlog, not a permanent obligation. They know the goal isn't zero exceptions — it's that every exception is a conscious, priced, time-boxed decision instead of an accident.

Practical actions

  1. Define your standard stack — one chosen tool per function (RMM, backup, antivirus, email security, password management) that every client runs by default.

  2. Sell the stack as the offering, not the client's existing tools. Your standardization is a feature; it's why your support is fast and reliable.

  3. Put inherited tools on a migration plan with target dates, so today's exception has a scheduled end instead of living forever.

  4. Price non-standard support to reflect its real cost, so clients who insist on their own tools cover the margin they consume.

  5. Make new exceptions a deliberate decision with an owner, a reason, and a sunset date — never a reflexive yes in the sales meeting.

Questions every owner should ask

  • If I listed every tool my clients run by function, how many do the same job?

  • Which of our inherited tools have a plan to migrate off — and which are just permanent?

  • Are we pricing non-standard clients for the extra support they actually cost us?

Frequently asked questions

Won't standardizing cost me deals with clients attached to their current tools?
Some, and that's usually fine. A client who insists on running their own patchwork and won't pay for the extra support it demands is often a margin drain you're better off without. For the rest, standardization is a selling point, not an obstacle — you're offering faster, more reliable support precisely because you've built deep expertise in a focused stack. Frame the migration as an upgrade you handle, not a demand you're making, and most reasonable clients come along.

How do I standardize clients I've already onboarded on a mess of different tools?
You don't rip and replace overnight. Define the standard stack first, then treat your existing base as a migration backlog — convert clients tool by tool during natural moments like renewals, hardware refreshes, or when an inherited tool hits end-of-life. Prioritize the tools that cause the most support pain. It's steady, deliberate work, but every client you converge lowers your ongoing cost, so it pays for itself as you go.

Related articles

Every business has more decisions than time

Whether you need help solving one problem, evaluating a major opportunity, or making a company-changing decision, Throne of Profit gives you consulting capacity on demand.

Purchase only the consulting capacity you need and use it across Weekly Focus, Strategic Focus, Financial Focus, and ThinkTank engagements.

Explore Throne of Profit

Previous
Previous

Building a Tier 1, 2, 3 Ladder Your Techs Can Climb

Next
Next

Writing Down How Your MSP Actually Delivers Service