The gap nobody plans for
There's a stretch between a client saying yes and you actually starting work. Most freelancers have no process for it, so it becomes a scramble: a scope written at 11pm, a deposit invoice sent three days late, logins chased over four separate emails.
That stretch sets the tone for everything after it. A client who experiences a calm, ordered start treats the project as professional. A client whose first week is chaotic learns that deadlines here are approximate — and behaves accordingly.
Seven steps. Roughly ninety minutes of work, most of which is reusing documents you wrote once.
The seven steps, in order
Step 1 — Confirm in writing, same day
A short email restating what you agreed verbally: the deliverables, the fee, the rough timeline. Not the formal scope yet — just a record, sent while the conversation is fresh.
This exists because memories diverge within about a week, and the version written down first tends to become the agreed one.
Step 2 — Send the scope of work and contract together
Within two working days. Together, not separately — sending them a week apart makes the second one feel like an addition rather than part of the same package.
The scope covers deliverables, exclusions, timeline and revisions. The contract covers payment, ownership, cancellation and liability.
Step 3 — Get explicit approval
A signature, or a reply that clearly says yes to those specific documents. "Looks good" on a thread with three attachments is not approval of anything in particular.
Step 4 — Invoice the deposit and wait for it
Send the deposit invoice the moment the documents are signed. Then — and this is the step most freelancers skip — actually wait for it to clear before starting.
Starting early feels helpful. What it teaches the client is that your payment terms are aspirational.
Step 5 — Collect everything you need, in one request
One message, one list, one deadline: brand assets, copy, logins, examples, the named contact. Chasing items individually over two weeks trains the client that each request is optional.
Say what happens if materials are late — the delivery date moves back by the same number of days. It's already in the scope; repeating it here makes it real.
Step 6 — Send a kickoff message
Short. What happens first, when they'll next hear from you, and how to reach you. This is where you set communication expectations — including that you answer within one working day rather than instantly.
Step 7 — Diarise the mid-project check-in
Before you start, put a date in the calendar roughly halfway through. Four questions, two minutes, and it catches scope drift while it's still a conversation rather than a delivery-day argument.
The kickoff email
Copy this and adjust. It's step 6, and it does more work than its length suggests.
Subject: We're all set — here's what happens next
Hi [name],
Everything's in place and I'm starting on [date]. Here's how the next few weeks look:
- [First milestone] — you'll have this by [date]
- I'll send a short check-in around [midpoint date]
- Final delivery: [date]
A couple of practical things. I'll send feedback requests to you directly — if others need to weigh in, could you gather their comments and send them as one set? It keeps things moving and avoids conflicting notes.
I answer emails within one working day. If something's genuinely urgent, [phone / preferred channel] is quickest.
Looking forward to it.
[Your name]
Why the consolidated-feedback line matters: contradictory feedback from three people is one of the most common causes of a project doubling in length, and it's almost always accidental. Asking for it once, politely, at the start prevents it far more effectively than objecting later.
How long the whole thing takes
From "yes" to starting work: two to five working days, most of which is waiting for signatures and the deposit. Your own effort is closer to an hour once the documents exist.
The reason it feels slower the first time is that you're writing the scope and contract from scratch. After that, sections on exclusions, revisions and payment barely change between clients — only the deliverables and dates do.
Three ways onboarding goes wrong
Starting before the deposit clears. Every incentive says do it — you're keen, they seem fine, the deadline is tight. It's still the single most common way freelancers end up doing unpaid work, and it undermines every payment term you set afterwards.
Letting the paperwork drift. A scope sent nine days after the verbal yes arrives into a different context. The client has moved on mentally, and terms that were obvious in conversation now feel like new conditions.
Not naming a single point of contact. Without one, you get feedback from whoever happens to be looking, and no one is accountable for resolving contradictions between them. It's a one-line fix made at the start, or a recurring problem for the whole project.
Common questions
How long should client onboarding take?
Two to five working days from the client agreeing to you starting work, most of which is waiting for a signature and a deposit to clear. Your own effort is closer to an hour once your scope and contract templates exist, because only the deliverables and dates change between clients.
Should I start work before the deposit clears?
No, and the reasons for making an exception are always persuasive in the moment. Starting early transfers the financial risk entirely to you, and it teaches the client that your payment terms are negotiable — which affects every invoice that follows, not just the first.
What should I ask the client for before starting?
Everything, in one message with one deadline: brand assets, copy, logins and access, reference examples, and the name of the single person responsible for approving work. Requesting items one at a time over two weeks trains the client to treat each request as optional.
Do I need a separate contract and scope of work?
They do different jobs, so ideally yes, sent together. The contract covers payment, ownership, cancellation and liability. The scope covers what is being delivered, by when, and what is excluded. For a small project with a repeat client, a single combined document is reasonable.
What is a single point of contact and why does it matter?
One named person on the client side who gathers everyone's feedback and sends it as a consolidated set. Without it you receive contradictory notes from several people, none of whom knows what the others said, and resolving them becomes your unpaid problem. Naming one person at the start costs a sentence.