Client Onboarding Checklist for Solo Businesses (With the Free Kit)

The first week of a project sets the tone for every week after it. A client who gets a clear, organised start — here's what's happening, here's the timeline, here's what I need from you — relaxes and trusts the process. A client whose first week is a scattered string of "wait, what did we agree on again?" messages spends the whole project a little on edge, second-guessing decisions that were actually fine.

Most solo businesses don't skip onboarding on purpose. It just doesn't get written down as a step, because when you're a one-person operation, the kickoff often happens in your head instead of on paper — and what's in your head doesn't automatically make it to the client's.

What a kickoff brief actually needs

A good kickoff document is short — most fit comfortably under 500 words — and covers six things, no more:

1. The goal. One or two sentences on what success looks like for this project, in the client's own terms, not yours.
2. What's included. The concrete scope, listed plainly.
3. What's not included. Just as important as the first list — the single most effective tool against scope creep later is having named the boundary in writing on day one.
4. Timeline. Real dates, not "a few weeks" — start, key milestones, delivery.
5. How we'll communicate. Weekly email, a call cadence, whatever it actually is — so the client isn't wondering when to expect an update.
6. What I need from you. Anything the client owes you to keep things moving — assets, approvals, access — named upfront instead of discovered mid-project as a blocker.

A short, neutral line about scope changes belongs here too: something like "if anything outside this scope comes up, I'll flag it and quote it separately before starting" — planting the flag before you ever need to use it.

Why this document does more than it looks like

It's tempting to think of a kickoff brief as paperwork — a formality between "they said yes" and "the actual work starts." In practice it does three jobs at once:

It answers questions before they're asked. Every item on that list is something a client would otherwise have to ask about individually, over several emails, in the first week. Answering it all at once, upfront, in one document, saves both sides a dozen small back-and-forths.

It's the reference point for every disagreement that doesn't happen. Six months in, if a client says "I thought this included X," a five-minute kickoff document you can point back to resolves it in one message instead of a tense negotiation from memory.

It's genuinely reassuring, in a way that's easy to underestimate. A new client doesn't yet know if you're organised. A clear, complete kickoff brief, sent on day one, is often the first real evidence they get — before any deliverable — that they hired someone who has their process together.

If you want to see this style of document before committing to anything, the free 10-minute kit gives you a real onboarding master prompt and template — the same style shown below, no card required. And once a project's kicked off, the late-payment reminder sequence is the piece that protects the payment terms this document quietly sets up. If a call happens during onboarding, meeting notes into actions makes sure nothing said on that first call gets lost before it's written down properly.

The copy-paste prompt

Paste this in with your project details — it builds the full six-part brief from what you already know.

You are a plainspoken assistant helping a freelancer or solo business owner write a client
kickoff brief. Keep it short, concrete, and free of filler.

Context:
- Client name / project: [CLIENT / PROJECT]
- What we agreed to do (the scope): [SCOPE]
- The goal, in the client's own words if possible: [GOAL]
- What's explicitly not included: [EXCLUSIONS, OR "NONE SPECIFIED — INFER FROM SCOPE"]
- Key dates: start, milestones, delivery: [DATES]
- How we'll communicate (call cadence, email updates, etc.): [COMMUNICATION PLAN]
- What I need from the client to keep this moving (assets, approvals, access): [NEEDS FROM
  CLIENT]

Task: write a kickoff brief with six sections — Goal, What's included, What's not included,
Timeline, How we'll communicate, What I need from you — plus a short neutral line on how
scope changes will be handled if they come up.

Constraints: under 500 words. No filler language ("we're excited to partner with you!").
State dates and deliverables plainly. If the goal or scope is missing, ask me one question
before writing rather than guessing.

What a finished brief looks like

Given the details for Renata, a copywriter in São Paulo, kicking off a five-page website copy project with two revision rounds, a goal of copy that sounds like the client and books more calls, dates from September 8 (start) to October 6 (final), weekly email updates plus a kickoff call, and exclusions of SEO keyword research and ongoing blog writing — the brief comes back fully populated, direct from the inputs, ending with:

If scope changes: If anything comes up outside this scope, I'll flag it and send a separate quote before starting on it — nothing extra gets added without you seeing the number first.

Every section traces straight back to something actually agreed — nothing invented, nothing vague. That's the whole standard for a good kickoff document: not impressive, just complete, sent before the client has to ask for it.

Want to try this exact style before you commit to anything? The free 10-minute kit includes a real onboarding prompt and template you can run right now.