The First 90 Days: How to Onboard a New Managed Services Client Without Losing Them
December 15th, 2026 by Brian Suerth
Onboarding Is the Sales Promise Under Test
Most clients who leave a managed services provider do not leave because the technology failed. They leave because the experience did not match what they were sold. The first ninety days are where that gap opens or closes. It is the period when the client is paying attention to every response time, every surprise invoice, every meeting that did not happen, and every promise that was made during the sales process.
That makes onboarding a retention function, not an implementation detail. The provider that treats it as a project to be survived will spend the rest of the relationship explaining why the relationship is not working. The provider that treats it as the first phase of delivery builds the trust that carries the account through the inevitable bad day.
Days 0-14: Set the Contract and the Relationship
The first two weeks are about clarity. The client needs to know who is responsible for what, how to ask for help, and what success will look like at day ninety.
- Hold a real kickoff. Not a sales call with a new logo on it. Bring the delivery lead, define the agenda, and leave time for the client to describe what has been going wrong before you arrived.
- Map the stakeholders. Identify the executive sponsor, the day-to-day contact, the people who can approve changes, and the people who will complain first. A single point of contact on both sides prevents most early confusion.
- Agree on success criteria. Write down what the client expects to be different in ninety days. This becomes the scorecard for every review that follows.
- Set the communication cadence. A weekly call during onboarding, a defined escalation path, and a clear answer to how urgent issues should be raised.
- Define the ticket intake. Where requests go, what information to include, and what happens after hours. Clients who do not know the path will invent one.
- Collect what you need. Asset inventory, credentials, vendor contacts, documentation, backup and licensing details, and the names of everyone who touches technology today.
The goal of week two is simple: the client should never wonder who to call or what happens next.
Days 15-30: Find the Risks and Land Quick Wins
By now the access is in place and the environment is visible. This is the period for an honest assessment, plus visible early wins that prove the relationship is already paying off.
Build the risk register. Backups that do not restore, unsupported software, missing patches, expired certificates, shared admin accounts, unprotected endpoints, undocumented line-of-business systems. Rank by likelihood and impact, and share the list with the client. The register is not a scare tactic; it is evidence that someone is now looking.
Land two or three quick wins. These should be cheap to deliver, visible to the client, and unrelated to the big remediation project. Faster ticket response, a cleaned-up alerting rule, a documented contact list, or a fixed problem the previous provider never closed. Quick wins buy patience for the work that takes longer.
Establish the baseline. Record the numbers the relationship will be judged on later: response time, ticket volume, open issues, backup success rate, patch compliance, and user satisfaction. Without a baseline, improvement is a claim instead of a measurement.
Hold the first service review. Short, specific, and focused on what was found, what was fixed, and what needs the client's decision. This is where the client learns what the relationship will feel like.
Days 31-60: Standardize and Train
The middle of the onboarding window is where the service model starts to become real. Standardizing the environment reduces the cost to serve, and training the users reduces the demand on the service desk.
- Align to your standard stack. Patch management, endpoint protection, backup, monitoring, and remote support. Exceptions should be documented and priced, not quietly absorbed.
- Close the highest risks from the register. Not every item will be resolved in month two, but the worst should be moving toward remediation with dates attached.
- Document the environment. Network diagrams, application owners, vendor accounts, onboarding and offboarding procedures. Documentation is what makes the service repeatable when a familiar technician is on vacation.
- Train the users. A short session on the service desk, security hygiene, and how to report a problem prevents a surprising share of future tickets. It also gives the account a face beyond the ticket queue.
- Review billing. Verify that the invoice matches the agreement, that licensing is accurate, and that the client understands what is included. Billing surprises are one of the most common reasons a new relationship sours.
Days 61-90: Prove the Value
The final month is the proof phase. The client should be able to see, in plain numbers, that the relationship is producing something.
Build the ninety-day scorecard. Compare the baseline to the current state: response time, open issues, backup and patch status, ticket trends, risks closed, and the success criteria agreed at kickoff. Present it in language the client's leadership uses, not in ticket categories.
Hold the first quarterly business review. Cover what changed, what is still open, and what the next ninety days will address. Ask the client what is working and what is not. A QBR that only reports activity is a missed opportunity; the point is to agree on priorities.
Set the roadmap. The client should leave the review knowing the next quarter's projects, the budget implications, and the decisions still outstanding. This is also the moment to revisit the agreement if the actual workload is different from what was sold.
Start the renewal conversation early. Not to sell, but to confirm the relationship is on track while there is still time to fix it. The best time to discover a problem is before the renewal date, not after.
The Failure Modes to Avoid
- The sales-to-delivery handoff gap. The client repeats their story because what was sold never reached the people who have to deliver it
- No named owner. Everyone is responsible for onboarding, so no one is
- Radio silence. Weeks pass without a status update, and the client fills the silence with worst-case assumptions
- Overpromising to win the deal. Every commitment made in sales becomes a delivery obligation, whether or not it was priced
- Hiding problems. A missed backup or a failed project surfaces later as a trust problem, not just a technical one
- Billing surprises. The first invoice does not match the client's understanding of the agreement
- A ticket backlog at cutover. Old issues arrive faster than the new process can absorb them, and the client judges the provider by the queue
- Treating onboarding as a one-time project. The checklist ends, the relationship is assumed to be fine, and the next ninety days get no attention at all
Metrics to Watch
Onboarding is easier to manage when it has numbers. Track first response time, average resolution time, reopened tickets, ticket volume per user, backup and patch compliance, open risks, and the percentage of the onboarding checklist that is complete. Compare each against the baseline recorded in month one. Beyond the operational metrics, ask the client directly at day thirty, sixty, and ninety whether the relationship is meeting expectations. A short survey catches the problem while it is still fixable.
Ticket volume deserves its own note. A spike after cutover is normal as users test the new provider and old issues surface. What matters is whether the volume settles as the environment stabilizes and training takes hold. If it does not, the service model or the client fit is wrong, and the earlier that is identified the cheaper it is to address. The same logic applies to clients who were never a good fit in the first place; the client fit question belongs in qualification, not in month nine.
Where TAG Fits
Onboarding improves when the team has seen the pattern before. TAG members compare service delivery metrics, onboarding practices, and client retention against peers who run similar businesses, which turns a checklist into a benchmark. The operations and financial management classes at TAG Bootcamp go deeper on service delivery, reporting, and the numbers behind a healthy account base.
If you want help designing an onboarding process that survives a busy quarter, or pressure-testing retention across the book, explore TAG's MSP business consulting or see what membership includes. Questions about fit? Contact us - the first ninety days are the cheapest place to earn a long relationship.
Posted in: MSP Business Strategy