Good onboarding leaves you more informed about your own technology than when you started. Here's what the first 90 days should look like and what to push back on.
TL;DR: The first 90 days with a new IT company tell you almost everything you need to know about the relationship you're actually in. A provider doing this right moves through discovery, standardization, and planning in a way that's visible, communicative, and leaves you more informed about your own environment than you were before they arrived. A provider doing this poorly disappears into your systems for weeks, resurfaces with vague updates, and leaves you wondering whether anything actually changed. Knowing the difference before you're six months in is what this post is for.
Signing with a new IT company feels like progress. The sales process is behind you, the decision is made, and someone capable is finally taking responsibility for the technology your business runs on. That relief is real. What happens in the next ninety days will determine whether it was warranted.
Think of it like a movie director who casts an actor for an important role. The audition told you they could do the part. The first few weeks of rehearsal tell you whether they actually can. Do they show up prepared? Do they take direction or do their own thing regardless? Do they communicate when something isn't working or let problems fester until they affect everyone else? A good cast member makes the whole production better from day one. A bad one makes you wonder why you didn't catch it in the audition.
Onboarding with a new IT company works exactly the same way. The first ninety days aren't just setup. They're the audition results. And a lot of business owners don't realize they're allowed to have opinions about how it's going until they're already past it.
The IT onboarding process has become more standardized across the industry, but there's still significant variation in what good looks like versus what acceptable looks like versus what "this is going to be a problem" looks like. Most business owners don't know the difference because nobody told them what to expect.
This post does. And it tells you when to push back.
Good IT onboarding isn't dramatic. It's methodical, communicative, and leaves you feeling more informed about your own technology environment at the end of it than you were at the beginning. That last part is the real test: if you know less about what's running in your business after ninety days with a new IT provider than you did before they arrived, something went wrong.
A well-run onboarding moves through three phases in sequence. Discovery first: the provider learns your environment, documents what exists, and identifies what needs attention. Standardization second: they get your systems to their baseline, apply patches that have been waiting, close obvious gaps, and set up their monitoring tools. Planning third: they sit down with you, share what they found, and map out what the next six to twelve months should look like based on your actual environment and your actual goals.
The thing that separates good onboarding from average onboarding isn't the technical work. It's the communication around it. A provider doing this right keeps you informed at every stage: what they're finding, what they're fixing, what they're leaving for later and why. You shouldn't have to chase updates. Updates should come to you.
As we covered in, Managed IT, Decoded: A Guide for Owners Who Skipped Comp Sci, the difference between a vendor and a partner shows up earliest in how they bring you on. Onboarding is the first extended test of whether the relationship matches the sales conversation.
The first thirty days should feel like someone finally paying attention to your technology environment for the first time in a while. Not chaotic, not overwhelming, but active. Things getting documented, gaps getting identified, a clearer picture of where you actually stand starting to emerge.
What you should be seeing: your new provider working through a systematic discovery of your environment. Every device, every application, every user account, every vendor relationship that touches your systems. They're building the map that everything else depends on. If they skip this or rush it, the rest of the engagement runs on assumptions rather than facts, and assumptions in IT tend to be expensive.
What you should be hearing: regular updates in plain English. Not technical summaries that require a decoder ring, but honest assessments of what they're finding. "Here's what's in good shape, here's what needs attention, here's what we're prioritizing first and why." If the first month passes with minimal communication and a general sense that things are being handled, push back. You're entitled to know what's happening in your own environment.
What you should not be seeing: your provider making significant changes without explaining them first. Discovery is about learning, not fixing. A provider who starts reconfiguring things in week one without a conversation about why is running their process, not yours. Good onboarding is collaborative. You should feel like a participant, not a bystander.
If the first thirty days are about understanding what you have, days thirty to ninety are about making it better and building a plan for what comes next.
Stabilization happens first. This is where the gaps identified in discovery start getting closed: patches applied, outdated software addressed, security tools deployed, monitoring configured, and documentation completed. It's not glamorous work but it's the foundation everything else runs on. By the end of this phase, your environment should be cleaner, better documented, and more secure than when your new provider found it. If it isn't, ask why.
Strategic planning comes next, and this is where a lot of providers reveal whether they're vendors or partners. A vendor finishes the technical work and waits for tickets. A partner sits down with you around day sixty or seventy, shares what they found during discovery and stabilization, and starts a conversation about where your technology should be heading. What's aging out and when. What investments make sense given where your business is going. What risks remain and how to prioritize closing them.
That conversation should feel collaborative, not prescriptive. A good IT partner doesn't show up with a list of things you need to buy. They show up with a picture of your current environment, an honest assessment of what matters most, and a willingness to work within your reality rather than an idealized version of it. By day ninety, you should have a technology roadmap that actually reflects your business, not a generic template with your name on it.
Good onboarding has a particular feel to it. Here's what it looks like when things are going right.
You're hearing from them before you have to ask. Proactive communication is one of the clearest signals of a provider who takes the relationship seriously. Updates come to you. Problems get flagged before they become incidents. You find out something changed in your environment because they told you, not because you noticed something felt different.
They're asking good questions. A provider genuinely learning your business asks about your busiest seasons, your most critical systems, your growth plans, and what keeps you up at night. Those questions aren't small talk. They're how a real partner builds the context that makes every future recommendation more relevant and more useful.
Your team actually likes them. This one sounds soft, but it matters enormously. If your employees feel comfortable calling for help, report problems early, and walk away from interactions feeling more confident rather than more confused, your IT provider is doing the people part right. That's the whole foundation of Make IT Kind, and it shows up earliest in how onboarding feels to the people going through it.
They're honest about what they found. A provider who sugarcoats the discovery findings to avoid an uncomfortable conversation isn't a partner. A provider who tells you plainly that your backup hasn't been tested in two years, that three former employees still have active accounts, and that your firewall is running firmware from 2019 is one you can actually trust. Honest findings early means honest conversations later.
Bad onboarding also has a particular feel. Here's what it looks like when things aren't going right and what to do about it.
You're chasing updates. If you're the one initiating every check-in, asking what's happening, and waiting days for responses to basic questions, that pattern is not going to improve once onboarding ends. It's going to get worse once the novelty of the new relationship wears off. Address it directly and early: tell them what communication looks like for you and ask them to match it. If nothing changes, you have useful information.
They're making changes without explaining them. Changes to your environment should come with context. Not a technical dissertation, just enough that you understand what changed, why, and what to expect. A provider who reconfigures things without telling you isn't being efficient. They're treating your business like a ticket, not a relationship.
Your team is already frustrated. If employees are avoiding calling IT two months into a new relationship, that's not a personality conflict. That's a service problem. The same things that make onboarding feel good to your team, clear communication, respectful interactions, plain English explanations, are the same things that make the long-term relationship work. If those aren't present in the first ninety days they're unlikely to appear later.
The roadmap never materialized. If you're approaching the end of the onboarding window and nobody has sat down with you to talk about where your technology is headed, ask for that conversation explicitly. A provider who can't produce a technology roadmap after ninety days of working in your environment either hasn't been paying attention or doesn't see strategic planning as part of their job. Either way, worth knowing now.
Ninety days in, you have real information. Not a sales pitch, not a proposal, not a carefully managed first impression. You have actual experience of how this provider communicates, how they handle problems, how your team feels about picking up the phone, and whether the technology roadmap they promised materialized into something real. That's the data that matters, and it's the data you didn't have when you signed.
The broader truth about IT relationships is that the first ninety days are the easiest part. Your new provider is motivated, attentive, and trying to make a good impression. If things aren't working well now, they're unlikely to get better once the relationship settles into routine. And if things are working well, that's worth recognizing too. A provider who's communicating proactively, delivering on what they promised, and leaving your team feeling more supported than before is worth holding onto and worth telling people about.
We're based in Ann Arbor and we've been through this onboarding process with enough Michigan small businesses to know that it sets the tone for everything that follows. At Mann IT, we don't consider onboarding finished when the technical work is done. We consider it finished when you understand your own environment better than you did before we arrived, your team feels comfortable asking for help, and you have a roadmap that actually reflects where your business is going. That's the standard we hold ourselves to from day one.
If you're evaluating IT providers and want to know exactly what our onboarding process looks like, that's a conversation we're happy to have. Connect with Mann IT and let's talk through what the first ninety days would look like for your business.
1. How disruptive is IT onboarding to my team's normal workday?
A well-run onboarding is mostly invisible to your team. The discovery and monitoring setup happens in the background. The moments that require your team's involvement, like device enrollment or credential updates, should be scheduled, communicated in advance, and take minutes rather than hours. If your team is regularly interrupted or left waiting during onboarding, that's worth flagging. It's a preview of how the provider handles change management going forward.
2. What if we're switching from another IT company? Does that make onboarding harder?
It adds a step but it shouldn't derail the process. A good provider has handled transitions before and knows how to work through limited or missing documentation from a previous vendor. The bigger variable is how cooperative your outgoing provider is. Some transitions are smooth, some aren't. Either way, your new provider should have a clear plan for handling the transition and should communicate it to you upfront rather than discovering problems as they go.
3. What should I do if I'm unhappy with how onboarding is going but I've already signed a contract?
Say something directly and early. Most onboarding issues are fixable if they're raised before they become patterns. Ask for a meeting specifically about communication and process, not just a support call, and be specific about what's not working. A provider worth keeping will take that feedback seriously and adjust. One who gets defensive or dismissive is showing you something important about how they'll handle feedback for the rest of the relationship, and that's worth knowing now while your options are still open. Review your contract's termination terms, document the communication failures, and start evaluating alternatives. A bad IT relationship that starts poorly rarely improves on its own.