QNN SolutionsOnboarding

The first ninety days,
written down.

What happens after you sign, in what order, and how much of your time it costs. Onboarding is where most IT relationships are won or quietly lost.

Inventory firstDocumented handoverMonthly review from day 30

The plan

Take control, stabilise,
then improve.

In that order. Improving an estate nobody has inventoried is how providers end up surprised in month four.

Days 1–30
Take control

What happens
  • Full inventory: cloud tenants, servers, devices, licences, network kit, who has access to what
  • Access established through your process, with named accounts and MFA
  • Support route live — how your team raises things, and who answers
  • Fix-first list agreed from whatever the inventory turns up

Days 31–60
Stabilise

What happens
  • Failed backups, unpatched systems and shared admin accounts dealt with
  • Monitoring deployed and tuned to your environment, not a default template
  • Documentation written: run notes, recovery steps, supplier and licence records
  • First monthly report and review meeting

Days 61–90
Improve

What happens
  • Migration or project work starts, if that was in scope
  • Access review and a security baseline check
  • Improvement backlog prioritized with you, not presented to you
  • Quarterly plan agreed, with what we will not be doing stated as clearly as what we will

Your side of it

What we need
from you.

Any provider who tells you onboarding costs you nothing is either doing it badly or has not started yet. Here is the honest ask.

If that time is not available in the first month, say so at scoping. We will stretch the plan rather than run a transition nobody has capacity to support.

  • Week one

    Around 4 to 6 hours of someone senior's time — the inventory conversation, access approvals and introductions.

  • Weeks two to four

    An hour or two a week: decisions, approvals, and telling us which exceptions are deliberate.

  • Ongoing

    One hour a month for the review. More if a project is running.

Leaving your current provider

Handovers go wrong
in predictable ways.

Usually because nobody wrote down who holds what. We run the transition assuming the outgoing provider will be unhelpful, and are pleasantly surprised when they are not.

  • Nothing is switched off until its replacement is verified working
  • Domain, DNS, tenant and licence ownership transferred into your name, not ours
  • Credentials rotated on handover, with a record of what changed and when
  • An overlap period where both providers are live, agreed in advance
  • A rollback route for every cutover step
Day 30What you receive

Proof it actually happened.

  1. The inventoryEverything found, including whatever the last provider never mentioned.
  2. The fix-first listWhat is broken today, ordered by business impact.
  3. The responsibility tableSigned, so nobody is guessing who owns what.

Planning a switch?

Tell us roughly what you are running and when your current agreement ends. We will sketch the transition before you commit to anything.

  • 1
    We aim to reply within one working dayA person, not an autoresponder.
  • 2
    A 20-minute scoping callEnough to tell you whether we are the right fit.
  • 3
    A written scope and priceWith the exclusions stated, before anything starts.
No obligationNo lock-in contractsWe never ask for credentials

Or write to info@qnnsolutions.com

What is this about?
Helps us come back with something specific.

We use your details to respond to this enquiry. Privacy policy.