What problem does it solve? Ending a managed services client relationship without a structured process risks legal liability, data disputes, and reputation damage. This Skill provides a complete offboarding runbook so every client exit follows the signed MSA terms, preserves service quality through the last day, and leaves documented evidence of a clean handoff. ## Core Features & Use Cases - 48-Hour Response Protocol: Read the signed MSA and Order, acknowledge notice in writing, freeze scope, brief the team, and log the churn reason in the PSA. - Sequenced Transition Runbook: Assemble the documentation package, transfer control with client-confirmed break-glass access, then remove RMM agents, endpoint protection, and admin accounts in a defined order. - Data Retention and Final Billing: Apply a 60-day post-exit retention default with written deletion confirmation, DPA overrides, and a no-surprises final invoice. - Ready-to-Send Templates: Acknowledgment and closure letters that attest to every removal step, serving as the liability shield. - Use Case: A client gives notice they are switching providers. Use this Skill to confirm the notice period from their Order, deliver the documentation package, coordinate access transfer with the successor, and send the closure letter attesting to completed removals. ## Quick Start Ask Claude to start the client offboarding runbook for a client who just gave notice, including the acknowledgment letter and transition checklist.
