What's the single most-skipped onboarding step that causes problems later?

Confirming who actually approves and receives invoices on the client's side. Freelancers often assume the person they scoped the project with is also the invoicing contact, and at any company with a real finance process, that's frequently not true. Finding this out after the first invoice bounces costs you weeks, not days.

Should I start work before a deposit clears?

No. Starting on the assumption that a payment will land is exactly how freelancers end up doing a week of unpaid work when a payment fails, gets disputed, or simply takes longer than expected. Wait for confirmation the deposit has actually cleared, not just that it was sent.

Do I need a formal kickoff call for small projects?

Not always. A short written confirmation email that restates scope, timeline, and price, with a reply confirming agreement, does the same job as a call for small or simple jobs. Save the live call for projects with real complexity, multiple stakeholders, or a client who still seems unsettled on the details.

What if a client wants to skip the contract for a quick job?

Even a short written confirmation email counts as a contract if it states scope, price, and payment terms clearly and the client agrees to it in writing. What you want to avoid is a purely verbal agreement with nothing in writing at all, even for a job that feels too small to formalize; that's exactly the kind of job where a misremembered scope becomes a dispute.

Client onboarding checklist: contracts & deposits

By the Billebly team · Published 5 August 2026 · Last updated 23 August 2026

Most of the freelance problems that blow up mid-project were actually created in week one, before any work happened. A scope dispute in month two usually traces back to a scope that was never written down; a first invoice that takes three weeks to get paid usually traces back to nobody confirming who approves invoices on the client's side. A freelance client onboarding checklist closes off the five or six ways a new client relationship typically goes wrong, all easier to prevent before you start than to fix after. Here's the order that works.

1. Get the scope and contract signed

Nothing else on this list matters if this step is skipped: everything after it assumes there's a written document both sides agreed to. Verbal agreements and "I'll send something over later" are where scope disputes are born.

The contract doesn't need to be long, but it needs a specific, itemized scope: what's included, what's excluded, and how many revision rounds are covered. "Website redesign" is not a scope. "Homepage, About page, Contact page, desktop and mobile, two rounds of feedback" is. Freelance contract essentials covers the full list of clauses worth including; scope is the one that prevents the most arguments later.

Get it signed (an e-signature tool, a reply confirming agreement, anything that creates a record) before you schedule a single hour of work. If a client is stalling on signing, that's information, not just a delay.

2. Collect the deposit before work starts

A deposit does two things at once: it filters out clients who were never serious, and it means you're not floating 100% of the project's cost on trust alone. For most project-based work, 25-50% upfront is standard, with the number scaling based on project length and how well you know the client.

The mistake that costs freelancers the most time isn't asking for too little; it's starting work before the deposit clears. "I'll just get going while the payment processes" turns into a week of unpaid work if the payment falls through, gets disputed, or simply takes longer than expected to land. Deposits and upfront payments walks through how to size the ask and word it so it doesn't sound like you're questioning the client's ability to pay.

State it as policy, not a request

"My standard terms are a 30% deposit before work begins" reads as how you operate. "Would it be okay if I asked for something upfront?" reads as optional. Put the line in the same email as the scope, not as a separate, later ask.

3. Confirm payment terms and payment method

Scope and deposit cover the start of the relationship; payment terms cover everything after it, and it's the step most freelancers write vaguely, if they write it at all. Before work starts, both sides should know:

What document you're sending and when. A quote locks in a fixed price; an estimate gives a range that can move. Quote vs. estimate vs. invoice covers the difference; sending the wrong one is a common source of "but you said it would cost less" conversations.
The due date structure: due on receipt, Net 15, Net 30, or milestone-based, stated as an actual term, not "whenever works." Freelance payment terms explained breaks down which fits which kind of engagement.
How the client will actually pay: bank transfer, card, a payment link, confirmed now, not discovered when the first invoice bounces because their preferred method isn't one you accept.

This is also the moment to flag anything unusual: a client billing through a different entity than the one you spoke with, a currency mismatch, or a client who needs a PO number on every invoice before their AP department will process it. Finding that out after you've already sent an invoice means resending it and restarting the payment clock.

4. Exchange invoicing details and the right contact

This step gets skipped more than any other, and it's the one most likely to delay your first payment. "Who do I actually send the invoice to" sounds like a trivial question. At any company bigger than the person you've been emailing, it usually isn't.

Before you send a single invoice, confirm:

Who approves invoices, and whether that's the same person you've been talking to. At larger clients, it's often not; you might scope the project with a manager but invoice a separate finance inbox or accounts payable address.
Where the invoice should go: a specific email, a portal, a shared inbox, and who else needs to be copied for it to move through approval.
What billing details need to be on it. Legal entity name, billing address, VAT or tax ID, a PO number, a specific invoice numbering format some companies require. Ask once, upfront, instead of getting an invoice bounced back for a missing field.

A first invoice sent to the wrong inbox doesn't just get delayed; it often gets lost entirely, discovered three weeks later when you follow up on a payment nobody knew was pending.

5. Lock the scope with a kickoff call or written confirmation

Even with a signed contract, it's worth one more explicit confirmation before work actually starts: either a short kickoff call or a written recap email that both sides reply "confirmed" to. This isn't redundant with the contract: it's a check that what's in the document matches what both people have in their heads, right before work begins rather than three weeks in when a misunderstanding surfaces.

For anything with real complexity (a multi-phase build, a project with several stakeholders, a client who's clearly still deciding on details), a live kickoff call is worth the 20 minutes. It surfaces mismatches a written scope alone can miss: the client mentions a "quick integration" they assumed was included, or a stakeholder who needs to sign off that nobody mentioned before.

For small, simple jobs, a written confirmation does the same job faster: "Confirming we're doing X, Y, Z, starting Monday, due the 15th; reply to confirm" takes two minutes to send.

Get the paperwork moving as soon as the client says yes

Billebly lets you send a deposit invoice, confirm payment terms, and attach a payment link in the same step, so onboarding doesn't stall waiting on manual back-and-forth.

Start for free

6. Set up access and tools

The last step is purely logistical, but it quietly eats the first few days of a project if it isn't handled upfront. Before work begins, confirm access to:

Shared tools and platforms: project management software, a shared drive, a design file, a codebase, a CMS login. Request access the day the contract is signed, not the day you're ready to use it, since IT delays and permission approvals are often slower than expected.
Communication channels: a Slack channel, a shared email thread, whatever the client actually uses day to day, so questions don't get lost between two systems.
Any assets the client owes you: brand guidelines, existing content, credentials, prior work files. Ask for these as a specific list with a deadline, not an open-ended "send whatever you have," which produces nothing until you chase it.

None of this is complicated, but it's exactly what gets skipped when everyone's eager to start. A day lost to a missing login in week one is still a day lost; it's just less visible than a scope dispute or a late payment.

Frequently asked questions

: Confirming who actually approves and receives invoices on the client's side. Freelancers often assume the person they scoped the project with is also the invoicing contact, and at any company with a real finance process, that's frequently not true. Finding this out after the first invoice bounces costs you weeks, not days.
: No. Starting on the assumption that a payment will land is exactly how freelancers end up doing a week of unpaid work when a payment fails, gets disputed, or simply takes longer than expected. Wait for confirmation the deposit has actually cleared, not just that it was sent.
: Not always. A short written confirmation email that restates scope, timeline, and price, with a reply confirming agreement, does the same job as a call for small or simple jobs. Save the live call for projects with real complexity, multiple stakeholders, or a client who still seems unsettled on the details.
: Even a short written confirmation email counts as a contract if it states scope, price, and payment terms clearly and the client agrees to it in writing. What you want to avoid is a purely verbal agreement with nothing in writing at all, even for a job that feels too small to formalize; that's exactly the kind of job where a misremembered scope becomes a dispute.