Switching IT support? Here’s what should happen in the first 90 days with a new provider, from onboarding and documentation to security and service improvements.
What Happens in the First 90 Days With a New IT Support Provider?
Changing IT support providers is a significant decision for any SME. Even when the current relationship is no longer working, many businesses still delay the move because they worry about disruption. They worry about downtime, confusion, lost knowledge, awkward handovers, and the possibility that the new provider will simply create a different set of frustrations. Those concerns are understandable. A provider change affects not just the IT team, but the wider business. If it is handled badly, it can unsettle users and expose gaps that have been hidden for years.
That is exactly why the first 90 days matter so much. A good IT support provider does not just “take over tickets.” They use the first three months to understand the environment properly, stabilise risk, improve visibility, and start building trust with the people who rely on the service every day. In many ways, those first 90 days reveal whether the relationship is going to be reactive and transactional, or proactive and genuinely valuable.
Amazing Support is a multi-award winning, Microsoft Partner and Cyber Essentials certified provider supporting SMEs across London, Greater London and Manchester. For businesses in the 50–200 user range especially, the onboarding and early-service period is where a provider proves whether they can combine structure, communication, and technical depth without creating unnecessary disruption.
The short answer is this: in the first 90 days, a strong IT support provider should document the environment, secure access, identify risks, stabilise support, improve user confidence, and create a clear roadmap for what comes next. If those things are not happening, the onboarding is probably too shallow.
Why the first 90 days matter more than the contract
A lot of providers talk well during the sales process. They promise responsiveness, proactive support, strategic input, and smooth onboarding. But the real test begins once the agreement is signed.
The first 90 days are where the provider has to move from promise to proof. It is the period where they inherit the reality of the environment, not the polished version described in a proposal. They discover whether documentation is complete, whether access is tidy, whether devices are consistently managed, and whether the previous provider has left the business with strong foundations or hidden fragility.
For the client, this period is equally important. It is when leadership decides whether they feel reassured. It is when users decide whether the new support team is approachable and competent. It is when the business starts to see whether the provider is simply reacting to tickets or actively improving the environment.
Days 1–30: discovery, access, and stabilisation
The first month should be focused on understanding and securing the environment.
That usually includes:
- gathering documentation and credentials
- reviewing user accounts and permissions
- checking backup coverage
- assessing device management and patching
- understanding line-of-business systems
- identifying urgent security or operational risks
- introducing the support process to users
This stage is not glamorous, but it is essential. Without proper discovery, the provider is effectively working blind. And when a provider works blind, problems get missed.
This is also the point where many businesses realise how much knowledge was sitting informally with the previous provider. Admin access may be unclear. Asset lists may be incomplete. Shared accounts may still exist. Old devices may still be active. The first 30 days should bring those issues into the open.
Days 31–60: tightening risk and improving service experience
Once the provider has a clearer picture, the second month should focus on tightening obvious gaps and improving the day-to-day support experience.
That often means:
- cleaning up accounts and permissions
- enforcing MFA more consistently
- improving endpoint visibility
- reviewing ticket trends
- fixing recurring issues
- clarifying escalation paths
- refining the onboarding experience for users
This is also when the provider should start demonstrating proactive value. If the same issues keep recurring, they should not just keep closing tickets. They should be identifying root causes. If users are confused about how to get help, the provider should improve communication. If security gaps are obvious, they should be prioritised rather than left sitting in a report.
Days 61–90: roadmap, reporting, and confidence building
By the third month, the provider should be moving beyond stabilisation and into partnership.
That means the business should start to see:
- clearer reporting
- a summary of risks and priorities
- recommendations for improvement
- a roadmap for projects or upgrades
- regular service review conversations
- more confidence from users and leadership
This is where the relationship starts to feel different. The provider is no longer just “the new team.” They are beginning to show how they think, how they communicate, and how they plan ahead.
For leadership, this is often the point where the value becomes clearer. Instead of just seeing tickets handled, they start to see structure, accountability, and direction.
What good onboarding feels like for the client
A strong first 90 days should feel:
- organised rather than chaotic
- communicative rather than vague
- reassuring rather than disruptive
- proactive rather than passive
Users should know how to get help. Leadership should know what is being reviewed. Risks should be visible. Priorities should be explained. The provider should feel present and accountable, not distant and mysterious.
Common warning signs in the first 90 days
There are a few red flags businesses should watch for:
1. Little or no documentation effort
If the provider is not investing in understanding the environment, they are building on weak foundations.
2. No clear security review
A provider should be checking access, MFA, patching, backups, and device posture early on.
3. Users are confused about support
If staff do not know how to log issues or what to expect, onboarding has not been handled properly.
4. No service review or roadmap
If the provider is only reacting to tickets after two or three months, the relationship may be too reactive.
FAQ
How disruptive should switching providers be?
With a structured onboarding process, disruption should be minimal. The goal is controlled transition, not chaos.
How long does it take before value becomes visible?
Usually within the first 60–90 days, if the provider is proactive and communicative.
Should security be reviewed immediately?
Yes. Access, MFA, backups, and device management should be reviewed early.
What if the previous provider left poor documentation?
A good new provider should help rebuild it as part of discovery and onboarding.
What should leadership expect by day 90?
Clearer visibility, reduced uncertainty, early improvements, and a roadmap for what comes next.
If you are considering an
IT support provider change, we can help you understand what a well-run first 90 days should look like and how to make the transition feel structured, secure, and commercially sensible.
