onboard-clientlisted

# /onboard-client — First-30-Days Client Onboarding > **Purpose.** Convert a signed contract into an operational client subprofile. Run the foundations chain (voice → ICP → content engine → outbound engine) at client-scope so that by day 30 every client subprofile is ≥70% complete and weekly delivery can run without operator interruption. > > **Bar.** A client who completes onboarding has voice-validated content shipping by day 14 and qualified DM ops running by day 21. If either misses, onboarding failed and the engagement starts at a deficit no monthly report recovers. ## When to invoke - Acquisition FSM transitions `Closed → ClientOnboarding` (auto-trigger) - Operator manually invokes after a contract signs outside the standard pipeline (rare — direct referrals, partnership conversions) - Re-onboarding scenario: existing client renews into a re-scoped offer (treat as new onboarding for the new scope) ## Required inputs 1. Signed contract (`client.signed: true`) with offer scope confirmed 2. Client slug declared (`client_slug` — non-PII alias, kebab-case, used in every subprofile path per ENCODING.md) 3. Initial intake form submitted (12-18 questions: company stage, revenue tier, target outcome, content history, prior agency experiences, decision-makers, communication preferences, slack/notion/email channel) 4. Offer deliverable spec from `/design-retainer-offer` output (what we ship, at what cadence, with what revisions allowed) 5. Operator + AM availability for the k