Create a Client Onboarding Sequence Automatically

You'll end up with: A repeatable client onboarding sequence—timeline, emails, intake, and kickoff prep—you can run for every new engagement

Overview
20–25 min
Intermediate
Free
2 tools
Cost breakdown
ClaudeFree
Google Docs (or Notion / Apple Notes)Free
TotalFree
Common mistake

Writing polished welcome emails before you have pinned trigger and cadence. You get beautiful copy that fires at the wrong time or duplicates steps. Fix: lock trigger and day offsets in Step 2, then do not let Step 4 change the timeline unless you explicitly revise Step 2's table first.

Before you start
  • Typical offer (retainer vs project)
  • Your real trigger (signed SOW, deposit received, or calendar hold—pick one)
  • Kickoff format (Zoom vs async)
  • One thing you always forget to send or ask
  • Claude open plus one doc surface (Google Docs, Notion, or Apple Notes)
1

Snapshot your current onboarding (honest inventory)

List what you actually do for new clients today—before writing a single email.

ClaudeFreeOpen Claude
Exact action

Start a NEW chat at https://claude.ai Paste the following block (fill the bracketed parts in your own words first): --- CONTEXT (fill in) - What I sell: [e.g. brand retainers / project-based web dev] - Typical engagement length: [weeks or months] - Kickoff format: [live Zoom / async] - Last client #1 onboarding (messy is fine): what emails you sent, links you shared, docs you created, when kickoff happened - Last client #2 onboarding: same INSTRUCTIONS FOR YOU (Claude) 1) Return a NUMBERED list of every onboarding touchpoint implied by the context (emails, forms, calendar links, invoices, Looms, Slack invites, etc.). 2) After each touchpoint, label it exactly one of: Necessary — Nice-to-have — Missing — Redundant 3) Do NOT write any client-facing wording, email drafts, or subject lines. Inventory and labels only. 4) If you cannot find at least one Missing or one Redundant touchpoint, say explicitly "none" for that category and justify in one sentence each. --- Send the message.

You see at least one Missing and one Redundant touchpoint (or explicit "none" with a one-sentence justification for each)—proof the inventory is not vanity.
Claude wrote email drafts, subject lines, or welcome copy already. Stop and re-send with: "Inventory only; zero client-facing wording."
2

Lock trigger, phases, and day offsets

Turn chaos into one trigger and a timeline table your sequence will follow.

ClaudeFreeOpen Claude
Exact action

In the SAME Claude chat as Step 1, send this as your next message: --- Using the numbered inventory you produced in your previous reply (do not restart the timeline from scratch): 1) I pick ONE primary trigger for this sequence (choose one only): [signed contract / deposit cleared / calendar hold confirmed — I will write which ONE in the next line]. My primary trigger is: ________________ 2) Produce a markdown table with columns exactly: Phase | Day offset from trigger | Channel (email / Loom / form / other) | Owner action (you vs client) | Exit criterion Phases must cover at least: Welcome / Intake / Prep / Kickoff (merge names if needed but keep four distinct rows minimum). 3) Every row needs a concrete day offset like "Day 0", "Same day", "Day +1", or "Day +3" — not "when ready". 4) If I listed two different triggers elsewhere, ignore the weaker one and pick one: default to "deposit cleared" if I was ambiguous. Reply with ONLY the table plus at most 3 sentences of clarification—no email copy yet. ---

Every row has a day offset or explicit "same day," and each phase has one exit criterion you could check off.
Two incompatible triggers or vague "when ready" timing. Re-prompt: "Pick one trigger; if ambiguous, default to deposit cleared."
3

Design the message skeleton (subjects + job-to-be-done)

Cap at six messages: titles, subjects, purpose, and send dependencies only.

ClaudeFreeOpen Claude
Exact action

In the SAME Claude chat, send: --- Using the markdown table from your last message: Design at most 6 client-facing messages for the whole onboarding. For each message provide: - Working title (internal) - Two subject line options - One sentence: what this message must accomplish (job-to-be-done) - Dependency line: what must be true before I send this (e.g. "only after intake form submitted") Rules: - No two messages may share the same job-to-be-done; merge duplicates. - If you proposed more than six, compress down to six and say what you merged. No full email bodies yet—outline only. ---

No two messages share the same job; dependencies read clearly (e.g. "Message 3 only after intake submitted").
Six or more micro-nudges or redundant messages. Reply: "Compress to six; merge reminders."
4

Generate the paste-ready pack (with placeholders)

Draft the full sequence with placeholders—same thread, no new timeline.

ClaudeFreeOpen Claude
Exact action

In the SAME Claude chat, send: --- Using the timeline table from earlier in this chat AND the message skeleton you just outlined: Write the full draft text for each message in send order, with these constraints: Allowed placeholders ONLY (use exactly these tokens, including braces): {{CLIENT_NAME}} {{PROJECT_NAME}} {{KICKOFF_DATETIME}} {{CALENDLY_OR_BOOKING_LINK}} {{INTAKE_LINK}} {{PORTAL_OR_DRIVE_LINK}} Content coverage across the pack (spread across messages, not repeated unnecessarily): - Welcome + boundaries: how to reach me, expected response times, what I need from them first - Intake: inline questions OR point them to {{INTAKE_LINK}} - Prep/homework before kickoff - One reminder message for ~24h before {{KICKOFF_DATETIME}} - Optional short "what happens next" after kickoff (only if it fits one of the six) Style: warm, direct, confident. Do NOT use these softeners anywhere: "I just", "Sorry to bother", "Totally understand if", "No worries", "Hope that's okay". Length: each email body max ~180 words unless you label a block as "call script bullets" instead. If the table referenced a link but you cannot draft without it, keep the placeholder and do not invent URLs. Do not change the day offsets from the table unless you explicitly flag a conflict in one sentence. ---

Each message is within the word limit (or clearly marked call-script bullets); placeholders are consistent; every link-type need from the table maps to an allowed placeholder.
Walls of text, invented URLs, or missing placeholders for something the table promised. Reply: "Rewrite shorter; add missing placeholders only."
5

Install: master doc + per-client duplication checklist

Move everything into one master doc another person could run without asking you.

Google DocsFreeOpen Google Docs
Exact action

1) Open https://docs.google.com and create a new Google Doc (or use Notion/Apple Notes with the same headings if you do not use Docs). 2) Title the doc: Client_Onboarding_Sequence_MASTER 3) Paste sections in this order: (A) Trigger + timeline — copy the markdown table from Claude (Step 2 output). (B) Intake question list — copy from Claude (from Step 4 where questions appeared, or extract a bullet list). (C) Messages — copy each full draft in send order with clear headings: Message 1, Message 2, … (D) Per-client checklist — numbered steps: duplicate this master → replace all placeholders → send Message 1 → track intake received → schedule kickoff → send reminder → archive or file the doc for the engagement. 4) Optional subsection (max 5 lines): "If I automate later (Zapier/Make)" — one line for a plausible trigger, one line for a plausible action. No setup tutorial. Save the doc.

A second person could run onboarding from the doc alone without asking you what happens on Day +1.
The doc is only pasted emails with no checklist or no trigger table. Add Sections (A) and (D) by copying from Claude and filling the checklist template above.

All done!

You now have: A repeatable client onboarding sequence—timeline, emails, intake, and kickoff prep—you can run for every new engagement

Explore more guides

Want this workflow built for your business?

Book a free audit