The moment a client accepts your proposal is the moment most freelancers relax. The sale is done; now the work can start. But the stretch between "yes" and the first real deliverable is where a surprising number of projects go wrong: the deposit is late, access to their systems takes two weeks, nobody is sure who gives final approval, and the timeline slips before you have done anything.
A repeatable onboarding process fixes this. It is not complicated, and once it exists, client number ten gets the same smooth start as client number one.
TL;DR
Good onboarding runs in a fixed order: confirm the accepted proposal, get the contract signed, invoice and receive the deposit, collect everything you need through one intake step, set up the project and tasks, agree how you will communicate, and then hold a short kickoff call. Do not start delivery work until the contract is signed and the deposit is paid. Write the sequence down once and reuse it for every client.
Step 1: Confirm the accepted proposal
Before anything else, make sure there is one clear, accepted version of the scope. If there were revisions to the proposal, confirm which version the client agreed to and archive the rest.
Send a short confirmation message: "Thanks for accepting the Recommended option. Next, I will send the contract and deposit invoice. Here is what happens after that." Setting out the sequence up front stops the client wondering what comes next, and it signals that you run a structured process. The post on how to write a freelance proposal that wins covers getting to this point.
Step 2: Send the contract
Send the contract promptly, while the client's enthusiasm is high. It should reference the accepted scope, payment terms, revision limits, change-request process, IP terms and termination. The freelance contract checklist lists what to confirm is covered.
Have a clear rule: no delivery work starts before the contract is signed. You can schedule the kickoff, but you do not open the design file.
Step 3: Invoice the deposit
Send the deposit invoice at the same time as the contract, or immediately after signing. Treat the deposit as the start signal. When it clears, the project officially begins.
This is also the point to confirm billing details: the client's legal name, billing address, any purchase order number, and who receives invoices. Collecting this now saves a delay on every invoice that follows.
Step 4: Collect everything you need, once
Few things stall a project like chasing assets one email at a time. Send a single intake request that lists everything you need, with a due date.
A typical intake list for a website project might include:
- brand assets (logo files, colors, fonts)
- existing copy, or confirmation of who is writing it
- access to the current site, hosting and domain
- examples of sites they like and dislike, with reasons
- the names and roles of everyone who will review work
- who gives final approval
- any dates that cannot move (launches, events, campaigns)
The "who gives final approval" question matters more than it looks. A project with three reviewers and no clear decision-maker is a project with unlimited revisions in practice.
Make the intake due date part of the timeline. If the client supplies assets late, the timeline moves, and your contract should say so.
Step 5: Set up the project
With the scope agreed and the intake underway, set up the project so the work is ready to begin:
- create the project with milestones that match the proposal
- break each milestone into tasks with owners and due dates
- separate client-billable tasks from internal ones (setup, admin) so you can see the true cost
- add time estimates so you can track actual hours against them
In COLO, the client, the accepted proposal, the signed contract and the project with its tasks sit together, and tasks carry time tracking and can be marked billable or non-billable. The post on billable vs non-billable hours explains why that split is worth setting up from day one.
Step 6: Agree how you will communicate
Decide this before the kickoff call, then confirm it on the call:
- Where messages go. One channel, not email plus three chat apps.
- Response times. For example, replies within one working day, and what counts as urgent.
- Status updates. How often, and in what form.
- Feedback format. Consolidated feedback per round, from the agreed reviewer.
- Meeting cadence. A weekly check-in, or milestone reviews only.
Giving clients somewhere to see status for themselves reduces the volume of "any update?" messages. In COLO, clients see their projects in the client portal, the same place they approved the proposal and signed the contract.
Step 7: Hold the kickoff call
The kickoff is short, usually 30 to 45 minutes, and it has a fixed agenda:
- Restate the goal of the project in one or two sentences.
- Walk through the scope, including what is excluded.
- Confirm the timeline and the first milestone date.
- Confirm who reviews and who approves.
- Confirm communication rules.
- Agree the immediate next steps on both sides.
Send a written summary afterwards with the decisions and dates. That summary is the reference point if anything is questioned later.
Write it down once
The value of a process comes from repeating it. Turn these seven steps into a checklist and use it for every new client. The client onboarding checklist template and the client onboarding guide are good starting points, and you can adapt them for your type of work.
FAQ
How long should onboarding take?
It depends on the project and how quickly the client responds. For small projects, many freelancers aim to go from accepted proposal to kickoff within a week or two. The bigger factor is usually how fast the client returns the contract, deposit and intake.
What if the client wants to start before the contract is signed?
Politely hold the line. Offer to schedule the kickoff for the day after signing, so they can see the start date is close. Starting without a signed contract leaves your work unprotected.
Should I charge for onboarding time?
On fixed-fee work, onboarding time is part of your estimate. On hourly work, it is normal to bill kickoff and setup like any other project time, as long as the client knows in advance.
Do repeat clients need full onboarding?
Not all of it. You will usually skip the intake questions you already have answers to, but still confirm the scope, sign a contract or change order for the new work, and take a deposit where appropriate.
A good start is a repeatable start
Onboarding is where you set the tone for the whole relationship. A client who experiences a clear, well-ordered start expects a clear, well-ordered project, and is more likely to follow the process you put in front of them. Build the sequence once, then run it every time.