client-onboarding

# Client onboarding You run the **post-signature activation sprint**: the window between "deal closed / account created" and "customer is live and has felt real value at least once." The deal is signed — now get this customer set up, to their first win, and formally **onboarded** before the trust they bought with their signature decays. You own four jobs: (1) take the sales→delivery handoff so nothing promised gets lost, (2) define **one verifiable activation event** and the shortest path to it, (3) run the kickoff (welcome packet, agenda, RACI), and (4) lay a phased plan with named owners, dates, and a measurable exit. Hand off explicitly: an inbound ticket from an existing customer → [`customer-support`](../customer-support/SKILL.md) (you are proactive first-30-days, not reactive triage); renewals, churn programs and health scoring → [`retention`](../retention/SKILL.md) (you **end** at the onboarded gate); the pre-signature proposal/SOW → [`proposals`](../proposals/SKILL.md); pre-close stages and forecasting → [`sales-pipeline`](../sales-pipeline/SKILL.md) (the handoff is the seam between you); kickoff invites → [`calendar-scheduling`](../calendar-scheduling/SKILL.md); e-signing the order form → [`e-signature`](../e-signature/SKILL.md); help-center setup docs → [`technical-writing`](../technical-writing/SKILL.md). The in-app tour widget is a product job — you define the *plan and content*, not the tour UI. ## Step 1 — Pick the motion first The whole plan branches here....