MSP Customer Onboarding

The Phases of MSP Customer Onboarding

Phase 1: The Pre-Kickoff Audit

Before a single agent is installed, you need to understand the environment better than the client does. This starts with a deep dive into their existing infrastructure. The goal here is "no surprises." You are looking for the "skeleton in the closet"—the ancient server running a critical line-of-business app or the unsecured guest Wi-Fi that reaches the parking lot.

During this phase, gather all administrative credentials, ISP details, and third-party vendor contacts. If you wait until the first support ticket to ask for the firewall password, you have already failed. A structured audit ensures that your Security Reviews start from a position of authority rather than guesswork.

Phase 2: The Project Kickoff Meeting

This is a non-technical meeting for the client’s leadership. Its purpose is to manage expectations. You should clearly define what is happening over the next 30 days, who the points of contact are, and how the client should report issues.

Avoid jargon here. Instead of talking about "RMM deployment," talk about "installing the health monitoring software that allows us to fix problems before they interrupt your team."

Phase 3: Technical Deployment and Data Capture

This is the heavy lifting. Your team will deploy your stack:

RMM agents for monitoring and patching. Endpoint Detection and Response (EDR) or AV solutions. Backup and Disaster Recovery (BDR) agents. Password management and documentation tools (ITGlue, Hudu, etc.).

Crucially, this phase must include a security baseline assessment. Use this time to document every user, every device, and every cloud application. If a client has 50 users but only 40 are licensed, you need to flag this immediately. This isn't just about security; it's about commercial accuracy and ensuring you are getting paid for the value you provide.

Phase 4: The 30-Day Value Review

After the first month, meet with the client to show them what you've found and what you've fixed. This is often the first time the client sees the "invisible" work an MSP does. Show them the number of patches applied, the threats blocked, and the documentation created. This reinforces the decision they made to hire you.

Standardisation: The MSP’s Secret Weapon

One of the hardest lessons learned by Luis Navarro while scaling his MSP to over 150 clients was that customisation is the enemy of profit. If every client has a unique onboarding process, your engineering team will never become efficient. Every hour spent "figuring out" a new client's unique setup is an hour of lost margin.

Standardising your MSP customer onboarding means having a fixed "Stack" that every client must eventually move toward. If a new client uses a firewall you don't support, the onboarding project should include a quote to replace it. This might feel aggressive, but it is the only way to provide high-quality support at scale. It protects the client by ensuring your team are experts in the tools protecting them.

Why Standardisation Matters for Security

When your environment is standardised, identifying anomalies becomes easy. If every client uses the same MFA (Multi-Factor Authentication) configuration, a deviation is a clear red flag. During the MSP customer onboarding, your job is to align the client with your "Best Practices" framework. This creates a predictable environment for your helpdesk and a more secure one for the client.

Common Pitfalls in the Onboarding Process

1. The "Dump and Run" Approach

Some MSPs simply install their agents and tell the client, "We're live." This leaves the client feeling abandoned. Onboarding should be a high-touch experience. Even if the technical work is done, the relationship work is just beginning. Weekly updates during the transition are essential to ensure the client feels the "white-glove" service they were promised.

2. Neglecting Documentation

Technical teams love to "fix" but often hate to "file." If the onboarding ends and the documentation is incomplete, your helpdesk will be inefficient forever. Make "Documentation Completion" a mandatory gate that must be passed before the onboarding project is officially closed. This includes network diagrams, license keys, and site photos.

3. Ignoring the Human Element

Technology transitions are stressful for the client’s employees. If they don't know who to call or how to use the new ticket portal, they will perceive the new MSP as a burden. Providing a "Welcome Kit" for every end-user—a simple PDF or physical card explaining how to get help—drastically improves the perceived success of the MSP customer onboarding.

The Commercial Reality: From Onboarding to Upselling

A successful onboarding identifies gaps. These gaps are not "problems"; they are project opportunities. If the onboarding audit reveals that the client’s server is out of warranty or their backup hasn't run in six months, you have a duty to report this.

Luis Navarro often emphasises that he wasn't the "technical guy"—he was the guy who explained why the technology mattered to the business. During onboarding, your account managers should be looking for these commercial conversations. By presenting these findings in a clear Security Review, you turn a technical discovery into a business decision for the client.

The Onboarding Checklist for Success

Use the following checklist to ensure no step is missed during the transition period:

• Administrative Handover: Secure all master passwords and domain registrations.
• Security Baseline: Verify MFA is active on all critical accounts (Email, VPN, Finance).
• Asset Inventory: Create a full list of hardware, including age and warranty status.
• Communication Setup: Introduce the client to the primary account manager and support lead.
• Old Vendor Exit: Coordinate the removal of the previous MSP's tools to prevent software conflicts.
• Immediate Remediation: Fix critical security vulnerabilities discovered during the first 48 hours.