MSP Standardization: Your Tech Stack Is Only Half the Job

Most MSPs think about standardization and immediately picture their tech stack. The firewall. The security tool. The backup solution. Get those locked in, get clients onboarded to them, and consider the job done.

Here’s the problem: that’s only half the job.

The support stack (how you actually support clients day to day) is just as important to your efficiency as the tools you deploy. Maybe more so. If you’re only standardizing the tech side, you’re leaving a significant amount of efficiency on the table. In managed services, efficiency is the name of the game. Everything you do under a fixed-fee agreement benefits directly from being more efficient. That efficiency benefits you, your team, and your clients.

Let me break down both sides.

The Tech Stack: Get It Done and Move On

Your tech standards exist to make your team faster and reduce risk. Every client exception costs you time. So your standards should be tight.

Here’s what mine looked like:

Security stack. One standard. Maybe a compliance add-on for clients who need it, but the base stack is the same for everyone, including break-fix clients. Simplify wherever you can.

Firewall. Every client needs your firewall at their office. This isn’t negotiable. A tech who’s fluent in WatchGuard and gets asked to make a change on a FortiGate is wasting time. Multiply that across your client base and you’re losing real money.

Identity and user management. Active Directory, Azure AD, G Suite — pick your standard and stick with it. Workgroup computers with individual user management at every machine is an efficiency nightmare. Don’t do it.

Backup. One backup product. Managing ten different backup solutions across your client base adds risk and overhead you don’t need.

Email. Microsoft 365 or Google Workspace. Hosted Exchange is dead. On-prem Exchange is dead. POP3 and IMAP are definitely dead. Supporting legacy email is where efficiency (and security) go to die.

When you onboard a new client, your job is to assess where they land against these standards, build a roadmap to get them compliant, and work that roadmap deliberately. You don’t need to do everything on day one, but you should know the gaps and have a plan. Most of the time, backups and firewalls should be the priority, because backups let you sleep at night.

Don’t overthink device brands or models. As long as workstations are current, functional, and under warranty, I’m not going to make a client replace everything on day one. But I will absolutely require them to replace a non-standard firewall or backup product, because those directly affect how efficiently I can support them. I also have another video about building a stack if I was just starting out. You can find that video here.

The Support Stack: The Part Most MSPs Skip

Here’s where things get more interesting, and honestly, more impactful.

Your support stack is how you deliver service. It’s the processes, access patterns, and workflows your team uses to support clients. If this isn’t standardized, you can’t scale. Your techs end up needing to know each client individually. They have to sift through tribal knowledge in everyone’s heads before they can solve anything. This creates process debt, and it compounds the same way technical debt does.

The three support standards I’d focus on first:

Remote access. With remote work being a permanent reality, this matters. Does your team connect the same way across clients? Do clients know how to work remotely when they need to? Whether it’s zero-trust VPN architecture or a standardized cloud access model, your answer should be the same for as many clients as possible. Clients who had this dialed in before the pandemic were in a much better position when everyone went home. Don’t wait for the next disruption to figure this out. Or, if you’re like me and a good chunk of the year is cold and snowy this becomes a reality every single year, even if you do work in an office.

File access. Where are the files? Is it a network drive? SharePoint? SharePoint mapped as a drive via OneDrive? Whatever you choose, it should be the same answer for every client. When it is, your backup solution can cover it consistently, your team knows exactly where to look, and onboarding new users at a client becomes repeatable.

Password resets. This is one of the highest-frequency support interactions you’ll have. If your team has to remember a different process for each client, that’s friction added to every single one of those tickets. Standardize it. Self-service resets, call-in verification, whatever works — just make it consistent.

Getting There With Existing Clients

If you’re reading this thinking about a backlog of existing clients who aren’t compliant with any of this, that’s okay. The right time to plant a tree was twenty years ago. The second-best time is today.

Pick the dependency that unlocks everything else and start there. Active Directory and identity management tends to be the first domino because file access, remote access, and password resets all tie back to it. From there, work the roadmap systematically.

You don’t have to do it all at once. Re-onboarding one client a month, or even one every two months, is real progress. You’ll chip away at the backlog, solve problems systematically, and free your team up in the process.

When clients push back, and occasionally they will, the conversation should start well before you’re presenting a project proposal. Stack compliance expectations belong in the sales conversation and in your contract. If a client agrees to the partnership, they’re agreeing to let you run the ship on these things. That framing makes the later conversations much easier.

The rare client who fundamentally refuses to standardize is probably a client worth re-evaluating. In my experience, the vast majority come around once they understand the business case. Frame every change around what it means for them: better productivity, lower risk of downtime, faster support when things go wrong.

Start Now, Whatever Stage You’re At

Whether you’re a solo MSP owner with twenty clients or a growing team trying to scale past a million in revenue, the same principle applies. The more consistent your tech and support stacks are, the more efficient your team becomes, and the more profitable your fixed-fee agreements get.

Build the tech standards. Build the support standards. Work them deliberately with every client, starting with the next one you onboard.

Efficiency isn’t just a number on a spreadsheet. It’s the thing that lets you grow without breaking.