The first 30 days of a new client: onboarding as a runbook, not a scramble

New-client onboarding is the highest-stakes, lowest-systematized month in most MSP operations. The contract is signed, goodwill is at its peak, and what happens next is often a scramble reconstructed from memory: deploy agents, inventory devices, collect credentials, document the network, meet the stakeholders — in whatever order the week allows, with whatever gets forgotten staying forgotten until it bites.

The cost of a ragged onboarding isn't just the rework. It's that everything discovered late — the unmanaged switch, the server nobody mentioned, the software the previous provider left half-licensed — arrives as a surprise attached to a bill, which is the worst possible framing for a relationship that is thirty days old.

What belongs in the first-30-days runbook

• Week one — access and visibility: agent deployment, network discovery, and a first-pass inventory, so the conversation shifts from "what did the last provider leave us" to a device list you can both look at.
• Week two — documentation and credentials: every credential into a vault with scoped access, network topology and vendor contacts recorded against the client, not in a tech's notes.
• Week three — baselines: patch posture, backup coverage, security gaps, all measured and written down. This is the "before" picture every future QBR is measured against.
• Week four — the review meeting: findings, priorities, and a plan, delivered from the data collected in weeks one through three rather than from first impressions.

Runbooks are only real if they live where the work does

Every mature MSP has some version of this checklist in a wiki. The failure mode is that the wiki is not where the work happens, so the checklist and reality drift apart by the third onboarding. This is why onboarding runbooks in Nexus are designed as working objects in the platform — steps tied to the client record, progress visible, the agentic layer drafting the checklist walk-through and flagging what stalled — with a human working the list, as ever.

A new client should experience your onboarding as the most organized month of the relationship — because it is the month they decide what working with you is going to feel like.

The onboarding-runbook capability sits inside the broader platform build-out and, like everything here, ships in the open — the roadmap page shows the sequencing, and the design-partner cohort is who gets to shape what the week-by-week template actually contains.