Client delivery · Kit & File Field Notes
How to Onboard a New Client After They Say Yes
One welcome, one complete request, a 30-minute kickoff, and a dated first deliverable. A simple client onboarding checklist for small service businesses.
The client said yes. Now the files, logins, and questions arrive across a pile of email threads, the kickoff slips, and the first deliverable waits on something nobody sent. You don't need a portal for this. You need four steps, in order.
Start when the yes is real
Onboarding covers everything between the client's yes and the first real piece of work. I think of it as a fixed list of steps you run every time, from the yes to the point where work can actually start.
The yes to your proposal is real when two things are true:
- The scope of work is accepted in writing.
- The agreed payment terms are met, for example the deposit has cleared.
A "sounds good" on a call is a reason to send the paperwork. It's not a reason to start. Kit & File's services page uses the same order: written scope, acceptance in writing, then work after cleared payment.
Onboarding can't fix a vague scope. If the scope is unclear, fix that first.
Send the welcome and ask for everything once
Send the welcome the same day. Then make one complete request instead of a slow drip of questions. I'd argue the waiting usually happens on the client's side, so ask for the signature, payment, files, and access at the same time on day one, not one after another.
Welcome email skeleton
Hi [Name], thanks for confirming. Here's what happens next.
What we agreed: [one-line scope summary]. Full scope attached. Key dates: kickoff on [date], first deliverable by [date]. How we'll talk: [email / channel], with a short update every [day]. What I need from you: the list below, by [date].
The one request
Group it so nothing gets missed. Give each item an owner and a date.
- Information: goals in their words, constraints, and who makes the final call.
- Files and examples: existing materials, brand assets, and anything they like or dislike.
- Access: which accounts, who grants access, and by when.
When something's late, point back to this list. Don't write a new request.
Run a 30-minute kickoff
Book it once the inputs are in, and keep to an agenda:
- Confirm the goal, in the client's words.
- Walk the scope and the exclusions, line by line.
- Name who approves each deliverable.
- Agree the update rhythm. I'd settle the cadence during onboarding, so it's a commitment, not a favor. The weekly status update guide covers the format.
- Set the first deliverable and its date.
- Clear the open questions.
Agree at kickoff how out-of-scope requests get handled, so the first one isn't a surprise. The out-of-scope guide has the wording.
Send the recap the same day
Three short sections: what we agreed, who does what by when, and the first deliverable date.
Ship a small first deliverable early
Pick something real that shows the work has started, such as an outline, a first draft of one section, or an audit summary. It doesn't need to be impressive. It needs to arrive on the date you named.
The one-page onboarding packet
Copy this list and reuse it for every client:
- Confirm: scope accepted in writing, payment terms met, welcome sent.
- Collect: information, files, and examples requested in one message, each with an owner and a date.
- Access: every account listed, granted, and tested.
- Kickoff: agenda sent, call held, recap sent the same day.
- First deliverable: date agreed and met.
How long should it take?
As short as the client's inputs allow. Don't promise a number of days. Promise what you control: a same-day welcome, one complete request, and a kickoff once the inputs arrive.
Illustrative example (fictional)
A bookkeeper's first week: on Monday the deposit clears and the welcome goes out with one request for bank access, last year's reports, and the receipt folder. On Wednesday the access arrives. Thursday's kickoff confirms the cleanup scope and a Friday update rhythm. The following Tuesday she sends the first reconciled month.
Still looking for clients to onboard? The minimum sales pipeline guide covers that part. For writing the welcome and the recap, the Better Messages Kit has a message-writing guide and reusable prompts.
Onboarding should be the most predictable part of the project.
Questions
Frequently asked questions
What is client onboarding?
Everything between a client's yes and the first real piece of work: confirming the agreement, collecting information and access, holding a kickoff, and delivering something early.
When should onboarding start?
When the scope is accepted in writing and the agreed payment terms are met. A verbal yes is a reason to send the paperwork, not a reason to start work.
What should a client onboarding checklist include?
A same-day welcome, the scope and dates restated, one request for information, files, and access with owners and dates, a kickoff agenda, a written recap, and the first deliverable's date.
How do I get files and logins from clients without chasing?
Ask for everything in one message on day one, with each item's owner and due date. Then point back to that one list instead of sending new requests.
What should happen on a kickoff call?
Confirm the goal in the client's words, walk through scope and exclusions, agree who approves work and how often you'll update them, and name the first deliverable and its date. Send a recap the same day.
Do I need client onboarding software?
Not to start. A checklist, an email template, and a shared folder are enough for a small service business. Consider software only when several people run onboarding or you onboard many clients at once.
Put the guide to work
Better Messages Kit
The Better Messages Kit helps you write the welcome email, the one-message request, and the kickoff recap, with a message-writing guide, workbook, reusable prompts, and a quick-reference sheet.
See what is included →