The Two-Week Rule: What Should Happen in Your First Fortnight With a New IT Provider
Signing with a new IT provider feels like the finish line after all the deciding and comparing. It is actually the starting line, and what happens in the two weeks that follow tells you almost everything about the relationship you have just bought. A strategic provider spends that fortnight understanding your business inside out. A transactional one flips a switch, points you at a support number, and waits for something to break. The difference is visible early, if you know what to look for.
Here is what a good first fortnight should contain, why each part matters, and what it means if none of it happened when you onboarded whoever you use today.
Why Do the First Two Weeks Matter So Much?
Because the character of the whole relationship is set in that window. The industry itself knows this: client dissatisfaction and churn concentrate heavily in the first ninety days, and a provider's reliability is judged by how the opening month goes rather than by anything in the sales pitch. When onboarding is vague and unstructured, the long-term service almost always turns out to be reactive, forever fixing rather than improving. When it is thorough and deliberate, you have bought a partner who will keep making your technology better.
There is a practical reason too. Everything you are paying for, the monitoring, the security cover, the fast support, the advice, depends entirely on the provider actually knowing your environment. They cannot protect, maintain or improve what they have never mapped. The first fortnight is when that knowledge is built, which is why a provider who skips it is quietly unable to deliver the rest.
What Should Happen in Your First Fortnight?
Five things, and you should be able to see evidence of each within the first two weeks.
A full asset audit. A proper provider catalogues everything you own and run: every computer, server, network device, cloud service and application, including the ones nobody remembered to mention. This is the baseline the whole relationship rests on. By the end of the first fortnight your entire estate should be visible in one place, not partially covered, because a dashboard showing everything as healthy while quietly missing several machines is worse than no dashboard at all.
A security posture review. Alongside the audit, they should assess where you are exposed and start closing the obvious gaps straight away, treating security as an immediate priority rather than a later project. In practice that means multi-factor authentication switched on, endpoint protection deployed on every device, and email security active, with a clear picture of your patching, backups and access taking shape.
A user and licence clean-up. Discovery almost always uncovers waste and risk hiding in plain sight: accounts still active for people who left long ago, mailboxes nobody has touched in years, and duplicate or unused software subscriptions quietly billing every month. A strategic provider finds these early and starts tidying them, which tightens your security and often saves real money at the same time.
Documentation of every system. The provider should be writing down how your technology is actually put together: a network diagram, an asset register, licence and renewal details, vendor contacts, and notes on how key systems are configured. This matters enormously, because it turns knowledge that previously lived in one person's head, or nowhere at all, into something the business owns and can rely on.
A written ninety-day improvement plan. The output of all the above should be a clear, dated plan setting out what they intend to fix and improve over the coming months, with owners and target dates. This is the single strongest signal of a strategic provider. It shows they have understood your environment and have a considered view of where it needs to go, rather than simply agreeing to answer the phone when something fails.
Why These Five, and Not Just "Support Is Live"?
Because there is a world of difference between a provider who takes over your support and one who takes on your business. Turning support on is easy and means little on its own. The five steps above are what separate a genuine technology partner from a help desk with your name on the contract. They are also, quietly, the foundation of everything you were promised. A written onboarding plan with milestones and owners is a standard mark of a serious provider, to the point that not having one by the end of the first month is itself recognised as a warning sign. If the work of understanding your environment is skipped, the SLAs and the proactive monitoring you are paying for have nothing solid to stand on.
What If None of This Happened When You Onboarded?
Then it is worth being honest with yourself about what you are probably getting. If your current provider came on board without auditing your systems, reviewing your security, cleaning up your accounts, documenting your setup or giving you any kind of forward plan, the likelihood is that you are on a reactive, transactional service rather than a strategic one. That is not a reflection on you. Most businesses do not know what a good onboarding looks like, which is exactly how thin ones pass unnoticed. The useful part is that recognising it gives you something concrete to ask for. You are entitled to request an asset audit, a security review and a documented plan from your existing provider at any time, and how they respond will tell you a great deal. A partner worth keeping will welcome the request. One that stalls or treats it as an imposition has answered a different, more important question for you.
What Should You, the Buyer, Do?
Set the expectation before you sign, not after. Ask any prospective provider to describe their onboarding in detail and to show you the written plan they will follow, with the milestones and dates. Expect a proper kickoff involving your leadership, a findings report once discovery is done, and a review meeting where they walk you through what they found and what they propose. During the first two weeks, watch for the five things above, and treat the written ninety-day plan as the deliverable that proves they mean business. If you are already with a provider and none of this ever happened, ask for it now. The standard we hold ourselves to on onboarding is set out in our managed IT and security service, and the mechanics of moving cleanly between providers are covered in our guide to the IT handover, if a change is on your mind.
The Bar, Set
A new IT relationship should open with a fortnight of the provider learning your business, not a fortnight of silence followed by an invoice. A full asset audit, a security review, a clean-up of users and licences, documentation of every system, and a written plan for the next ninety days are not premium extras. They are the baseline of a service that intends to improve your technology rather than merely keep it limping along. Hold your provider to that standard from day one, and you will know very quickly whether you have hired a partner or just another vendor. And if you look back at your last onboarding and see none of it, you already have your answer about what to expect next.
Because expectations and best practice keep moving, it is worth revisiting this standard each quarter so the bar you hold providers to stays current.
Comments