Client-Onboarding Kit

How a project starts largely determines how it goes. Sloppy onboarding — unclear scope, missing info, mismatched expectations — is where most client problems are born. A clean, repeatable onboarding process sets expectations, gathers what you need, and signals professionalism from day one. This builds that flow so every new client starts the same, smooth way.

What This Skill Produces

• A welcome & kickoff flow — the sequence from signed deal to project start (welcome, intake, kickoff, first steps)
• The intake — the exact information, access, and assets you need to begin (so you're not chasing it later)
• Expectation-setting — clear alignment on scope, communication norms, timeline, milestones, and payment terms
• A kickoff-meeting agenda — a structured first meeting that aligns everyone and builds confidence
• Reusable templates — the welcome message, intake form, and kickoff agenda to reuse every time
• Problem-prevention — the boundaries (scope, comms cadence, revisions) set now that prevent disputes later

Required Inputs

Ask for these if not provided:

• Your service — what you deliver and a typical project shape
• Client type — size/sophistication (tunes formality)
• Current process — what you do now (or nothing)
• Pain points — where projects usually go wrong (scope, comms, delays, payment)
• Tools — what you use for comms, files, contracts, payments

Framework: Set The Frame Before The Work

1. Welcome and reassure. A prompt, warm welcome after signing sets the tone and confirms they made the right choice.
2. Gather everything up front. A structured intake for the info, access, assets, and decisions you need — so the work isn't stalled chasing details.
3. Align expectations explicitly. Scope (and what's out of scope), communication channels and cadence, timeline/milestones, revisions, and payment terms — stated now, not assumed.
4. Run a real kickoff. A structured kickoff meeting confirms goals, roles, and the plan, and gives the client confidence.
5. Make it repeatable. Templatize the welcome, intake, and agenda so every client gets the same professional start with less effort each time.
6. Prevent the usual problems. The clarity set here (especially scope and comms) is what heads off scope creep and friction later.

Output Format

Client onboarding: [service] · client type [x]

Flow: signed → welcome → intake → kickoff → first steps. Welcome message: [warm, next-steps, what to expect]. Intake (gather up front): [info · access · assets · decisions needed]. Set expectations: scope (+ out of scope) · comms channel & cadence · timeline/milestones · revisions · payment terms. Kickoff agenda: [goals · roles · plan · Q&A · next steps]. Templates to reuse: [welcome · intake form · kickoff agenda].

Quality Checks

• Covers the full flow from signed to project start
• Includes a structured intake for everything needed to begin
• Sets explicit expectations on scope, comms, timeline, and payment
• Provides a kickoff-meeting agenda
• Produces reusable templates
• Ties the setup to preventing later scope/comms problems

Anti-Patterns

• Improvising onboarding differently each time.
• Starting work before gathering the needed info/access.
• Leaving scope and comms to assumption.
• No kickoff — diving in without alignment.
• One-off effort with nothing templatized.

Example Trigger Phrases

• "Help me create a client onboarding process."
• "Build me a welcome packet and kickoff flow for new clients."
• "What should I gather from a new client before starting?"
• "My projects start chaotically — help me onboard clients better."
• "Give me a kickoff meeting agenda for a new client project."