A simple freelance client onboarding checklist

TL;DR

• Day 0 is documents and money, not unpaid production. Capture the billing entity, write a brief a stranger could understand, and send a deposit with a calendar due date. Start when it clears. Kickoff is a decision meeting you recap the same day. Schedule the remaining invoices while you onboard, not when the project “feels done.”

Key takeaways

• Yes is permission to send documents. It is not a kickoff.
• The client record needs the payer, not just the person who said yes.
• Send the deposit immediately, with a real due date. Start when it clears.
• Collect only the access the brief needs. Move the timeline if access is late.
• Schedule the remaining invoices during onboarding.

This post is for a freelancer who just got a yes and wants a path to the first paid invoice. One client. One checklist. The question: what do you do between “yes” and work that is actually billed?

They said yes. Do you start the work?

No. Yes is permission to send the next documents.

Reply the same day. Confirm three things in one note:

• What you think they bought (one paragraph)
• What they will pay, and when the first payment is due
• What you need from them before you start

Then stop. Do not open Figma. Do not book a four-hour research block. Excitement is not a process.

If the “yes” is still fuzzy, you do not have a client. You have a conversation. Tighten it. Proposals that become invoices exist for this. The lines you sell should be the lines you bill.

What belongs in the client record?

Open a client record before you send anything official. Name, company, billing entity, email that finance actually reads, timezone, currency, how they pay.

Your Slack buddy is often not the payer. Ask: “Who should be on invoices, and do you need a PO?”

Write down:

• Legal or trading name
• Billing address if they need one on the invoice
• VAT or tax IDs only if they asked you to show them (this is not tax advice)
• Preferred payment method
• The person who approves work vs the person who releases money

In Brisk, that record sits next to the invoices. You are not hunting a year-old email for an IBAN. If you are still on a notes app, one page per client is enough. Just make it the only page.

What must be in the brief before you collect access?

A brief is the work in a form a stranger could understand.

Minimum:

• Outcome (what “done” looks like)
• In scope
• Out of scope
• Inputs they owe you (copy, brand files, logins, decisions)
• Dates that matter (their launch, not your vibe)
• How many rounds of revision
• Who signs off

If they cannot give you this, you write a draft brief and they mark it up. Silence is not approval. “Looks good” in chat is approval if you paste it back: “Great — I’ll treat this as the brief for invoice 1.”

Scope that grows later is scope creep). You stop it here by naming the edges.

You do not need a novel contract to start. You do need the commercial bits in writing. What to put in a longer agreement is covered in what every freelance contract should include. This checklist gets you to a first invoice without waiting for legal theater.

When do you send the deposit invoice?

Before kickoff, for a new client or a non-trivial project. Ask for a deposit). 30–50% is the usual band. Smaller jobs can be 100% upfront so you are not chasing two tiny payments.

Send it like a real invoice. Number. Date. Due date as a calendar day. Line item that matches the proposal. Payment details that do not require a reply.

Example line: “Deposit (50%) — homepage and three inner pages, as agreed 12 May 2026.”

Due date: soon. Not “when you can.” A deposit that is Net 30 is not a deposit. It is a hope.

Do not start until it clears. If they say it is urgent, they can pay faster. Urgency on your side only is unpaid overtime.

How to send the thing: how to send your first invoice. What belongs on it: freelance invoice template.

In Brisk the deposit is a live invoice page. Card, bank, Apple Pay, and Google Pay can sit on it. Multi-currency if they pay in theirs. Free covers three invoices a month. Pro is $6/mo if you need more, plus reminders and view tracking.

If they stall on the deposit, that is data. Better now than after you built the thing.

What access do you collect, and when?

After the deposit is paid (or at least sent, if you trust a repeat client), collect access.

Make a short list. Not “send me everything.”

Typical:

• Brand folder or a link that will not expire in two days
• Current site or product credentials, or a staging login
• Analytics only if the work needs it
• The people who will give feedback, with their roles

Put access in a place you control: a password manager shared item, not a screenshot in WhatsApp. When the project ends, you revoke what you can.

If they cannot get you access in a week, the timeline moves. Say that once, in writing. “Kickoff slides to the Monday after I have the brand folder and CMS access.”

What happens in kickoff?

A kickoff is a decision meeting, not a tour of your process. 30–45 minutes. Then a written recap.

Agenda:

1. Confirm the brief out loud. Fix mismatches now.
2. Confirm dates and who is slow (legal, brand, their boss).
3. Confirm how feedback arrives. One thread. One owner. Not five Slack DMs.
4. Confirm the remaining payment schedule. Deposit, milestone, final.
5. Confirm what “first draft” means so they do not expect final polish on pass one.

Same day, send a recap. Bullet points. “If I have this wrong, reply by Friday.” That recap is the working agreement until something changes.

If they want a weekly status call forever, price the time or fold it into a retainer. Status meetings are work.

When is onboarding actually done?

When they have seen you move and you have seen them respond.

Ship something small and dated in the first working week. A sitemap. A research note. A first section. Whatever matches the brief.

You are testing their feedback loop. If they vanish here, you still have the deposit. You also know not to staff the rest of the month on their optimism.

Log decisions. “We dropped the blog index from v1.” Future you will invoice extras against this log, not against memory.

When do you schedule the rest of the invoices?

Now. Do not wait until “the project feels done.” Done is a feeling. An invoice is a date.

On day 0 you already know:

• Deposit (sent)
• Midpoint, if the project is long enough to need one
• Final, on delivery of the agreed scope, not on their internal launch

Put those invoices on your calendar the day you onboard. Draft them if you can. Change the date if the work slips. Do not invent the final invoice from scratch at 11pm.

Payment terms belong in the first pack. Freelance payment terms is the longer version. For onboarding you only need: deposit due [date], balance due [date], method, and what happens if they add scope.

What is the one-page checklist?

Before kickoff

• Written yes + one-paragraph scope
• Client record (billing name, payer, currency, method)
• Brief with in/out of scope and revision rounds
• Deposit invoice sent with a calendar due date
• Deposit paid (or a written exception you chose on purpose)
• Access list sent and received
• Kickoff booked

At kickoff

• Brief confirmed
• Feedback owner named
• Remaining invoice dates named
• Recap sent the same day

After kickoff

• First visible deliverable dated
• Decisions logged
• Next invoice already drafted or scheduled

If a box is empty, you are not “being flexible.” You are carrying risk they declined to share.

What can you skip?

You can skip the 12-page welcome PDF. You can skip a custom microsite. You can skip a gift box.

You cannot skip who pays, what they bought, and when the first money moves.

You can skip a deposit for a client who has already paid you on time, more than once. That is a choice. Write it down so you do not “be nice” by accident to a stranger.

A €400 job does not need a 45-minute kickoff. It needs a clear line item and a due date. A three-month build needs every box. The cost of skipping is a final invoice that finance does not recognize.

If you use Brisk, create the client, send the deposit as a live invoice page, and keep the rest of the schedule in the same place. If you do not, run the checklist on paper. The tool is optional. The order is not.

FAQ

What is a freelance client onboarding checklist?

A short path from “yes” to a paid, scoped start: client record, brief, deposit invoice, access, kickoff recap, and the remaining invoice dates.

Should I start freelance work before the deposit is paid?

No, not for a new client or a non-trivial project. Urgency on their side is a reason for them to pay faster, not for you to start unpaid.

What information do I need before I send the first invoice?

Billing entity, payer email, currency, payment method, a line item that matches the brief, and a calendar due date.

When should I collect logins and brand files?

After the deposit is paid, or sent if you trust a repeat client. Only what the brief needs. Late access moves the timeline.

What should happen in a freelance kickoff call?

Confirm brief, dates, feedback owner, remaining invoice dates, and what “first draft” means. Recap the same day in writing.

Can I skip onboarding on a small job?

Shorten it. You still need a record, a one-page brief, an invoice, and a due date. You do not get “no list.”

Key insights

Onboarding is how you get paid without a chase later. The first invoice is part of the welcome, not a chore after the work.