Week 1 · Bound the project
Confirm authority, exclusions, decision owners, access requests, a representative pilot customer, and measurable exit criteria.
6 weeks · 30 milestones · Public CSV · No signup
Turn a six-week MSP onboarding contract into a controlled handoff.
Six weeks is enough for one bounded pilot—not for discovering and rebuilding an entire MSP by assumption. Establish authority and access first, write SOPs from observed work, prove the operating model on one representative customer, then train and hand off with exceptions visible.
Download the project planOpen the onboarding evidence registerAssign RMM and PSA implementation workChoose an RMM for a new MSPUse the full onboarding guide
Week 2 · Observe before prescribing
Shadow the real workflow, reconcile inventory and access, draft the SOP in parallel, and keep unknowns in a decision register.
Week 3 · Prove the design safely
Validate tenant mapping, endpoint lifecycle, alert-to-ticket routing, patch exceptions, recovery, remote support, and rollback on controlled systems.
Week 4 · Run one controlled pilot
Use go/no-go approval, waves, checkpoints, stop conditions, communications, and an exception log rather than a bulk rollout.
Week 5 · Reconcile and teach
Close coverage gaps, review audit and access quality, prove removal, publish owned documentation, and turn pilot evidence into NOC exercises.
Week 6 · Test the handoff
Have the NOC operate without the project lead, review evidence with decision owners, transfer recurring work, and publish residual risk before closeout.