# Start Client Onboarding Note

> Prepares a First Client Onboarding Note, with a welcome in your own words, what happens in the first two weeks, what you need from them and by when, how and how often you will be in touch, how invoicing works and the first date in the calendar. Use for "run start-client-onboarding-note", "client onboarding", "my first client said yes now what", "kickoff note for a new client", "welcome email for a client", "how do I start an engagement", "first two weeks with a client", part of the Claude Guide for New Founders Pack by 90n.

- Skill: `polar-bear-org/start-client-onboarding-note` (Agent Skill)
- Install (CLI): `npx get-skill add polar-bear-org/start-client-onboarding-note`
- Raw SKILL.md: https://api.skillmd.com/api/skills/polar-bear-org/start-client-onboarding-note/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: polar-bear-org (https://skillmd.com/u/polar-bear-org)
- Updated: 2026-11-14
- Page: https://skillmd.com/skills/polar-bear-org/start-client-onboarding-note

---


# First Client Onboarding Note

## When To Use
They said yes, and you realise there is no process behind you any more. No account team, no kickoff template, no finance department to send the invoice. This answers: what does my client need to hear from me in the first days so that the work starts cleanly and they feel they chose well?

## When Not To Use
If the client is your former employer, write the Former Employer Engagement Plan first; this note then carries its boundaries. If nothing is agreed yet, you are still at First Client Proposal.

## Inputs
- The proposal or message they accepted: scope, option, fee, dates
- What you need from them to begin: access, documents, people, decisions
- How you prefer to work: channels, response times, the days you are available
If you have none of this, I start from what was agreed as you remember it and mark the output as a first draft.

## Approach
Public guides to a first consulting project agree on the opening moves: a welcome message, a kickoff conversation, expectations that go beyond the contract, a communication rhythm, and invoicing agreed at the start. The judgement is that the note follows a conversation; it does not replace one. For someone used to being an employee the risk is unspoken expectations: you assume a weekly call, they assume you are reachable all day. The failure it prevents is the first invoice arriving as a surprise to someone who did not know when, to whom or for what.

## Workflow
1. Ask at most three questions: what exactly they accepted, who your day-to-day contact is, and whether you have already spoken about how you will work together.
2. Give points for the welcome, two or three sentences you write yourself: glad to start, the outcome in their words, what happens first.
3. Lay out the first two weeks by day or by week: the kickoff conversation, what you will do, what they will see by the end of week two. Small, visible and true beats ambitious.
4. List what you need from them, each with an owner by role and a date: access, documents, people to meet, decisions. Say what slips if an item is late.
5. Set the rhythm: one channel, how often you update them, in what form, your response time and the days you are not available. These are yours to set; I do not suggest a standard.
6. State invoicing exactly as agreed: when invoices are sent, to whom, with which reference, and the payment terms from your agreement. Anything not yet agreed is listed as "to confirm at kickoff", never assumed. Tax and invoice wording: check with a qualified adviser.
7. Add what the contract does not say: how to raise a concern, how changes to scope are handled, the first date in the calendar. You edit and send the note after the kickoff conversation.

## Output Format
```markdown
# First Client Onboarding Note
Client: [name, role] | Agreed: [proposal, option, date] | Kickoff conversation: [date]
## Welcome (my words)
[two or three sentences]
## The first two weeks
| When | What happens | What you will see |
|---|---|---|
| [day or week] | [activity] | [output] |
## What I need from you
| Item | Who (role) | By when | If late |
|---|---|---|---|
| [access, document, person, decision] | [role] | [date] | [what slips] |
## How we stay in touch
- Channel: [one] | Updates: [how often, in what form] | I reply within: [my figure] | Not available: [days]
## Invoicing
- Sent: [when] | To: [role, address] | Terms: [as agreed] | To confirm at kickoff: [anything not yet agreed]
## If something changes
- A concern: [how to raise it] | A change to scope: [how we handle it] | First date in the calendar: [date, what for]
## Decision
[Your name] sends the note by [date], after the kickoff conversation; [client role] confirms the contact, the dates and the invoicing details.
```

## Done When
- Every item you need has an owner by role and a date.
- The first two weeks end with something the client can see.
- Invoicing matches what was agreed, with gaps marked "to confirm".
- A first date is in the calendar.

## Quality Bar
- Nothing in the note changes the scope, fee or terms that were agreed.
- No promise of results; only what you will do and when.
- Written as one person, in your voice, with no borrowed corporate language.
- The note follows a real conversation; it is never the first they hear of how you work.
- What was agreed and your own way of working, in your words; you edit it and send it yourself.

## Next
Run start-ninety-day-plan (90-Day Practice Plan) now, before delivery takes all your time.

## About the makers

This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).

