The First 90 Days After MSP Go-Live (What Actually Matters)

Client onboarding is one of the most important processes for your MSP to master. I’ve talked about it a lot. But here’s the thing most MSPs miss: go-live isn’t the finish line. It’s the starting line.

What happens between go-live and day 90 is where you either build a relationship that lasts for years or set yourself up for a painful contract.

Let’s break it down.

Days 0–30: Understand What You Actually Inherited

The first 30 days aren’t about fixing everything. They’re about understanding what you actually walked into.

You spend a lot of time documenting during your onboarding process. The thing is, you won’t catch all of the nuances, so there’s some additional things to document. Also, reality moves fast, so things change.

Find your frequent flyers. Every client has them. Within a few weeks you’ll know who calls constantly, who’s highly self-sufficient, and who falls somewhere in between. This isn’t an annoyance. It’s intelligence. Frequent flyers often point directly to training gaps, workflow problems, or bad tooling that your onboarding process couldn’t surface.

Discover the shadow IT. Personal Dropbox folders. Random SaaS subscriptions. Automation scripts nobody mentioned. Free AI tools being used in ways they shouldn’t be. These things show up fast once you’re embedded in the environment. Document everything.

Watch your tickets. Your PSA is already telling a story. Recurring issues, misconfigured systems, bad line-of-business software. If you’re logging everything properly, you’ll start to see patterns emerge before the 30-day mark. If you’re not logging everything, I would start there. Logging these issues is the only way to understand the trends.

One strong recommendation for this phase: don’t change too much too quickly. Unless there’s a glaring security issue, resist the urge to overhaul the environment right away. Showing up and immediately changing things can erode the trust you just spent weeks building during onboarding.

Days 30–60: Start Solving the Right Problems

Now you have data. Use it.

The goal in this phase shifts from observation to targeted action. And the key word is targeted. You’re not trying to fix the whole environment. You’re solving the issues that create the most friction.

Address visible wins first. Login problems, VPN headaches, slow machines. These aren’t glamorous, but they’re what users remember. Knock them out early and your reputation with the end user base starts to build.

Lean into user education. This doesn’t have to be formal training. Consistent reinforcement on how to submit tickets, basic security habits, MFA expectations. The frequent flyers you identified in the first 30 days are your primary audience here. If you can reduce their call volume, you’ve done two things at once: improved their day and freed up your team.

Start cleaning up configuration drift. There are almost certainly systems that aren’t set up the way you’d set them up. This is the window to start addressing those gaps without disrupting the client. Do it carefully. Communicate changes before you make them.

A quick story: I have a friend who took over a client and switched out their firewall pretty quickly after go-live. Totally reasonable thing to do. But nobody told the users how to connect with the new VPN client. Everyone went home, tried to work remotely, and called the service desk. The entire workforce was dead in the water. You don’t want that to be you.

If you make a change that affects users, train the users first.

Days 60–90: Move From Support to Leadership

This is where good MSPs separate themselves from average ones.

By day 60, you know this client. You know their frequent flyers, their problem devices, their shadow IT habits, and the gaps in their environment. That’s a lot of valuable information. Now you need to do something with it.

Prepare your account manager. Before the day-90 business review, your account manager should be fully briefed. What were the key findings? What are the outstanding risks? What projects need to get scoped? Don’t walk into that meeting cold.

Present what you’ve learned. Clients love seeing that you’ve been paying attention. A clear summary of what you found and what you’ve addressed goes a long way toward building long-term trust. It also positions you as a partner, not just a vendor.

Introduce the roadmap. Day 90 is when you shift from reactive to proactive. Infrastructure upgrades, security improvements, lifecycle planning, budget expectations. This is the conversation where you go from “we’re fixing your tickets” to “we’re guiding your technology.”

Reset expectations if needed. Sometimes onboarding surfaces things that weren’t visible upfront. Old hardware. Underbudgeted IT. Internal processes that create more problems than they solve. Day 90 is the right time to have that conversation. Year two is too late.

I’m a big fan of doing a brief check-in right at go-live, setting expectations for what the first 90 days will look like, and then coming back at day 90 with a full business review. It gives the client a framework for what to expect and gives your team a clear milestone to work toward.

The Bigger Picture

Most MSPs treat onboarding as something that ends at go-live. It doesn’t.

Go-live is just the beginning. The first 90 days is where the relationship actually gets built. And how you handle that window determines whether this client becomes profitable and loyal or difficult and churned.

Get the first 30 days right by observing before you act. Get the 30–60 days right by solving problems systematically instead of one ticket at a time. Get the 60–90 days right by showing up as a technology leader, not just a help desk.

Do all three and you’ll have a client for a long time.