The first 30 days with a new IT provider
Signing the contract is the easy part. The first month sets the tone for the whole partnership. It’s the period when a manager sees a new provider’s standards most clearly. Here’s what to expect in the first 30 days, and what it’s reasonable to ask for, whichever partner you choose.
Week 1: Inventory and access handover
A disciplined onboarding starts with a detailed inventory: what equipment exists, its condition, the active licenses, and each user’s access permissions. If there was an audit before signing, much of this stage is already done, and the data is simply completed and validated now. This is also when access is handed over from the previous provider or the in-house specialist. Critical passwords are changed straight away, drawing a clean line around the new responsibilities.
What to ask for: the inventory documented in writing, right from the start. It’s the foundational record the rest of the relationship rests on, and it belongs to your company alone, not the provider.
Weeks 2 and 3: Setup and rolling out monitoring
Next comes the less visible stage: installing monitoring agents on the equipment, applying outstanding updates, checking or configuring the backup setup, and documenting the new configurations. For companies used to the reactive model, this period can feel like pure paperwork. In practice, it’s the difference between a service you can verify through reports and one you have to take on faith.
This is also the phase where the less pleasant finds usually surface: expired licenses, active accounts belonging to former employees, or a backup that hasn’t run in months. These situations are normal, and they’re exactly why the inventory is done. The key point is that every vulnerability found comes with a proposed technical fix, not just a note that it exists.
Week 4: Stability becomes routine
Toward the end of the month, operations settle into a predictable rhythm. Issues are logged and resolved within the contractual terms (SLA), the monitoring catches the first incidents before they reach users, and your team knows exactly how to ask for help. This is the right moment for the first review: what we found, what we fixed, which actions stay a priority for the months ahead, and in what order.
What to ask for: a written report on the first month and a list of technical recommendations, each with clear costs. That way decisions get made rationally, on the numbers, with no commercial pressure.
Performance indicators: good signs and warning signs
The marks of a professional relationship are easy to spot: the documentation always stays with you, response times are met as a matter of course, and the provider takes an interest in how your team actually works, not just in the state of the servers. The warning signs are just as clear: passwords held by the provider alone, evasive answers when you ask about the month’s activity, and recommendations that invariably open with a new hardware purchase.
In our case, this first month actually begins before the contract is signed, with the free audit. So from day one of the contract, we start with a clear inventory and a list of priorities already agreed. If you’d like to see what this process looks like applied to your company, the audit is the first step.