| Category | Client Onboarding |
|---|---|
| Time to Run | 15 min |
| Difficulty | Deep Work |
| Output | |
| Client-Facing | Yes — goes directly to client |
A new client just signed the agreement. The deal is closed, the energy is high — and this is the exact moment where most solo consultants wing it. They send a quick “excited to get started!” email and figure the rest out later. The problem: the first 48 hours after signing set the tone for the entire engagement. A scattered onboarding creates a client who’s unsure what happens next, when, and what they’re supposed to do.
Run this immediately after a new client signs. Fifteen minutes now saves hours of clarifying emails and misaligned expectations over the first month.
This is the complete .md skill file. Copy the code block below, save it as client-onboarding-welcome-sequence-SKILL.md, and upload it to a Claude project for use.
---
name: client-onboarding-welcome-sequence
description: >
Generates a 3-email onboarding welcome sequence for new clients that sets
expectations, provides logistics, and establishes the working cadence.
Trigger: immediately after a new client signs the agreement.
metadata:
author: "Kathryn Brown, Practice Builders"
version: "1.0.0"
date: "2026-04-25"
---
# Client Onboarding Welcome Sequence
Generate a 3-email welcome sequence that transitions a new client from "just signed" to "fully oriented" within 48 hours. Sets expectations, provides logistics, and establishes the working relationship.
**Core Principle: Onboarding is not administration — it’s the first delivery experience. Every email must feel like working with you has already begun, not like you’re processing paperwork. The client should finish reading each email thinking "this person is organized and I’m in good hands" — never "this feels like a form letter."**
## What This Skill Does
**Job 1: Expectation Architecture.** It builds a clear picture of what happens when, who does what, and how communication works. The sequence eliminates the top three onboarding anxieties: "What happens next?", "What do I need to do?", and "How do I reach you?"
**Job 2: Logistics Delivery.** It provides all practical information — tools to access, meetings to schedule, documents to share — in a structured format that doesn’t overwhelm. Each email carries one primary action, not a checklist of twelve things.
**Job 3: Relationship Framing.** It establishes how you work together — communication cadence, response time expectations, and how decisions get made. This prevents the "I emailed you on Saturday, why didn’t you respond?" conversation that happens in month two.
## Section 1: Sequence Architecture
Design a 3-email sequence with specific timing:
**Email 1 — Welcome & What’s Next (send within 2 hours of signing)**
Purpose: Celebrate the start, confirm the engagement, and tell them exactly what happens in the next 48 hours. One action: confirm the kickoff meeting time.
**Email 2 — Logistics & Access (send 24 hours after Email 1)**
Purpose: Provide everything they need to be ready for the kickoff. Tools, access, pre-work. One action: complete any tool setup or share any required documents.
**Email 3 — Working Together (send 24 hours after Email 2, or morning of kickoff)**
Purpose: Set the communication cadence, response expectations, and decision-making process. One action: reply to confirm they’ve read and are ready.
Each email must be self-contained. If they only read one, they still get value.
## Section 2: Email 1 — Welcome & What’s Next
Structure:
- **Opening (2 sentences):** Personal, warm, names the specific engagement. Not generic "welcome aboard." Reference something specific from the sales conversation.
- **What’s happening (3–4 sentences):** Name the engagement type, start date, and first three milestones. Be concrete: "In our first two weeks, we’ll [specific deliverable 1] and [specific deliverable 2]."
- **Your one action (1–2 sentences):** "Please confirm the kickoff meeting for [date/time] works, or suggest an alternative."
- **Close (1 sentence):** Forward-looking, specific. Not "looking forward to working together" but "I’ll send the logistics email tomorrow so you’re fully set up before we start."
Target length: 120–180 words.
## Section 3: Email 2 — Logistics & Access
Structure:
- **Opening (1 sentence):** Quick, efficient. "Here’s everything you need to be ready for our kickoff."
- **Tools & access (bulleted list):** Each tool gets: name, what it’s for, and the specific action (create account, accept invite, bookmark link). Max 4 items.
- **Pre-work (if any, 2–3 sentences):** Anything you need them to do, prepare, or share before the kickoff. Be specific about format and deadline. If no pre-work, say "No prep needed — just show up."
- **Your one action (1 sentence):** "Reply to this email once you’ve completed the setup, or let me know if you hit any snags."
- **Close (1 sentence):** "Tomorrow I’ll send one more email about how we’ll communicate during the engagement."
Target length: 150–200 words.
## Section 4: Email 3 — Working Together
Structure:
- **Opening (1–2 sentences):** Frame this as "the last thing before we start." Position it as something that prevents friction, not bureaucracy.
- **Communication cadence (2–3 sentences):** How often you’ll meet, what channels to use for what (email for X, Slack for Y, calls for Z). Name response time expectations: "I respond to emails within [timeframe] on [days]."
- **How decisions get made (2–3 sentences):** Who approves what. What needs a meeting vs. an email. When to escalate vs. wait.
- **Boundaries (1–2 sentences):** Office hours, weekend policy, emergency protocol. Direct and unapologetic.
- **Your one action (1 sentence):** "Reply ‘Ready’ and we’re officially off and running."
- **Close (1 sentence):** Direct bridge to the kickoff — "See you [day] at [time]."
Target length: 150–220 words.
## Section 5: Personalization Requirements
Each email must include:
- The client’s preferred name (not "Dear Client")
- At least one reference to their specific engagement (deliverables, industry, or something from the sales conversation)
- The specific tools and platforms from the inputs (not generic placeholders)
- Actual dates and times derived from the start date
The sequence should feel written for this client, not pulled from a template library.
## Section 6: What to Skip / What to Watch For
**Leave alone:** Don’t include pricing, scope, or contract terms in the welcome sequence. That’s already signed. Restating it signals distrust. Also skip methodology explanations — they’ll experience it in the kickoff.
**Watch for:** If the client doesn’t reply to Email 1 within 24 hours, that’s an early signal. Don’t send Email 2 blindly — follow up with a brief "Just making sure this landed" message first. Silence at the start often means buyer’s remorse or a miscommunicated expectation.
## Quality Check (Internal — never shown to the user)
| Check | Question |
|-------|----------|
| Personal | Does each email include at least one client-specific detail, not just their name? |
| One action | Does each email have exactly one clear ask, not a multi-item to-do list? |
| Self-contained | If the client only reads one email, do they still know what’s happening? |
| Warm but efficient | Do the emails sound like a trusted professional, not a chatbot or a form letter? |
| Progressive | Does each email build on the last without repeating information? |
**Enforcement:** Run all five checks. Identify the weakest email. Rewrite it fully. Verify the rewrite is actually more personal and more specific than the first version. User sees only the finished sequence.
## Rules
- Each email must have exactly one call to action. Not two, not zero. One.
- Never use "Dear [Name]" — use "Hi [Name]" or the client’s preferred greeting.
- Never mention the contract, pricing, or payment terms in the welcome sequence.
- Keep each email under 220 words. Onboarding emails that are too long don’t get read.
- Include the engagement’s specific deliverables by name — not "your project" but "the client communication audit and the referral system build."
- Never promise specific outcomes in the welcome sequence. Promise process, structure, and access.
- Space emails 24 hours apart. Don’t send all three at once — it overwhelms.
- If the client needs to set up tools, provide direct links, not instructions to "go find" the tool.
## Output Format
Send: Within 2 hours of signing Subject: [Specific subject line]
Hi [Name],
[Body — 120–180 words]
[Signature]
Send: [Date — 24 hours after Email 1] Subject: [Specific subject line]
Hi [Name],
[Body — 150–200 words]
[Signature]
Send: [Date — 24 hours after Email 2] Subject: [Specific subject line]
Hi [Name],
[Body — 150–220 words]
[Signature]
**Signal-to-action traceability:**
- Email 1 → Signal: agreement signed, energy is high. Do this: channel that energy into forward momentum with a specific next step (confirm kickoff).
- Email 2 → Signal: kickoff is approaching. Do this: eliminate logistics friction so the first meeting is about work, not setup.
- Email 3 → Signal: engagement is about to begin. Do this: set communication rules before the first misunderstanding, not after.
## What Makes This Different
Most consultants send one welcome email that tries to do everything — celebrate, inform, instruct, and set expectations — and it does none of them well. This skill sequences the onboarding into three purpose-built emails, each with a single action, timed 24 hours apart. The result is a client who enters the kickoff meeting already knowing how you work, what’s expected, and what happens next. That’s not a nice touch — it’s a structural advantage that prevents the most common first-month friction points before they start.
---
Copyright (c) 2026 Kathryn Brown, Practice Builders
This skill is licensed for your personal and business use. You may run this skill inside your own practice and share the outputs it produces with your team and clients. "Your practice" includes employees and contractors engaged to perform work for your business under your direction — virtual assistants, operations support, bookkeepers, and similar team members.
You may not share, distribute, resell, or repackage the skill file itself — including this SKILL.md document, its prompts, frameworks, and structure — with anyone outside your practice. This includes peer practitioners, other consultants who would use it in their own client work, and anyone outside your operating team. Written permission from Kathryn Brown ([email protected]) is required for any redistribution.
This skill is provided "as is" without warranty of any kind, express or implied.