How to Onboard a New Client — Checklist + Email Templates

Most freelancer-client disasters don't happen at the end of the project. They happen in the first week. The client who expects three rounds of revisions when you offered two. The client who doesn't know when they'll be billed. The client who treats your inbox like a 24/7 hotline. None of that is bad luck — it's onboarding that never happened.

Onboarding is the process of taking a signed contract and turning it into a working project with rules, tools, and expectations — before the first deliverable exists. It takes one day of your time and it prevents 80% of the headaches that kill freelance projects. Here's the complete checklist, with the exact emails to send. The contract is the foundation this process builds on — if you haven't locked down your terms yet, start with freelance contract essentials.

Step 1: The welcome email (within 24 hours of signing)

The welcome email does three jobs: it confirms what was agreed, it tells the client what happens next, and it requests the first thing you need. Speed matters — a welcome email sent the same day sets the tone for the whole project. A client who waits a week for a response has already learned that your project will move slowly.

Notice the structure: confirm, schedule, delegate a tiny task. The tiny task matters more than it looks — a client who fills in a brief before the call is a client who's already participating in the project, not spectating it.

Step 2: The kickoff call agenda

The kickoff call is where you install the operating rules. Keep it under 30 minutes and run the same agenda every time — consistency makes you faster and makes clients feel like they're working with a process, not a person winging it.

After the call, send a written summary within 24 hours: decisions made, dates confirmed, access needed. That summary is your single best defense against scope disagreements later — when the client says “I thought revisions were unlimited,” the summary says otherwise. It's the same principle as a contract, applied to the operating details.

Step 3: Information gathering

Nothing delays a project like waiting on the client. The fix is a short, structured brief sent before the kickoff call — five questions max — plus a list of the assets you need. Most clients will fill in a good brief; the ones who won't are telling you something about the project early, which is information you want.

• The five-question brief: (1) What does success look like for this project? (2) Who is it for? (3) What have you already tried? (4) What are the must-haves vs. nice-to-haves? (5) What's the deadline, and what happens if we miss it?
• The asset list: brand files, content, logins, examples, current versions of anything we're replacing. Ask for everything at once with a deadline (“by Friday, please”) — piecemeal requests turn you into the project's memory.
• The decision-maker question: “Who approves the final work?” If the answer is “my team,” find out who the single approver is. Projects with multiple approvers and no hierarchy eat weeks.

Step 4: Setting expectations

Expectations are rules the client agreed to before they needed them. Set them in the kickoff call and repeat them in the summary email, and most future conflict evaporates:

• Revisions: “Two rounds of revisions per deliverable are included. Additional rounds are billed at $95/hour.” A client who knows the price of a third round rarely needs one.
• Communication: “I check email twice a day, Monday-Friday, and reply within 24 hours. Urgent issues go by phone.” Set the channel and the response time before the first “can you take a quick look?” at 9pm.
• Turnaround: “I need feedback within 5 business days of delivery, or the schedule shifts.” This one sentence stops the two-week feedback gap that silently doubles your timeline.
• Definition of done: “Done means you approve the deliverable in writing.” Projects don't end when work stops; they end when approval happens — write that down before it matters.

These four rules are also your scope-creep defenses. Our scope creep guide shows how they play out mid-project.

Step 5: Tool access and project setup

Get the technical housekeeping done in the first week so it never blocks the project again: a shared folder or board with a clear structure, access to the client's systems (or a plan for who creates what), and a single feedback channel. Two practical rules. First, one place for everything — if files live in three tools, someone loses something. Second, log access requests with deadlines: “I need staging access by Wednesday to hit the launch date” — that turns a favor into part of the plan.

Step 6: First invoice timing

Your first invoice should already be in motion the day the contract is signed: the deposit. “Work begins after the deposit is received” is a contract clause, and onboarding is where it gets enforced — you can't start a kickoff call on a project you haven't been paid to start. After the deposit, the first milestone invoice goes out on the date in the contract, not when you remember. If you set the payment rhythm in the first week — invoice on schedule, follow up on schedule — clients internalize that rhythm. If you set a loose rhythm, they internalize that too. The full escalation system for the invoices that go late lives in how to ask a client for payment.

The trial period concept

For new clients who want a big, ongoing relationship, run a trial project first. A small, well-defined engagement — a landing page, an audit, a single article — before you commit to a retainer or a multi-month project. The trial answers three questions cheaply: do they pay on time? Do they communicate the way they promised? Do you enjoy working with them? A painful small project tells you everything a painful big project would, at one-tenth the cost.

The trial also works in reverse: it gives the client proof of how you work before they commit to a large budget. “Let's do the first piece at a project rate, and if you like how it goes, we move to the retainer” — that sentence has converted more skeptics than any sales pitch, because it lets the work do the selling. Frame the trial explicitly: “this is an interview for both of us.” Professionals respect that framing.

Three onboarding mistakes to avoid

Onboarding fails in three predictable ways, and they're all fixable:

• 1. Skipping the kickoff call on “small” projects. The call is where expectations get installed — revisions, feedback windows, who approves. Without it, a $600 project can burn the same hours as a $6,000 one. If the client is genuinely too busy for a call, run the same agenda as an email with numbered questions and require written answers before you start.
• 2. Assuming the client read the contract. Almost nobody reads contracts. That's why the kickoff call and summary email repeat the three terms that matter most: the deposit, the revision limit, and the feedback window. Saying them out loud turns fine print into agreed expectations — and prevents the “I didn't see that in the contract” conversation later.
• 3. Starting work before the deposit lands. “I'll invoice you next week” sounds friendly and costs you everything if the client vanishes. The deposit is part of onboarding, not a formality — the welcome email confirms it, and work starts when it clears. Clients who push back on this are telling you early how payment will feel for the whole project.

The complete onboarding checklist

Run this checklist and you'll notice something: the projects that follow it rarely have payment problems, rarely have revision wars, and rarely have “I thought” conversations. That's not coincidence. It's the first week doing its job.