Skip to main content

Command menu

Jump to a page or search the catalog

Client Onboarding Checklist: Kits for Freelancers

A client onboarding checklist for freelancers: intake, scope, contract, deposit, kickoff and access, plus what an onboarding kit should contain.

9 min read
1,648 words
Client Onboarding Checklist: Kits for Freelancers

A client onboarding checklist is the list of steps you run between "yes, let's work together" and the first real piece of work: intake questions, a written scope, a contract and deposit, a kickoff call, access to the client's tools and a payment schedule. Below is a complete checklist you can copy today, followed by what a paid onboarding kit should contain and how to check one before you buy it.

Why onboarding decides the whole project

Most freelance projects that go wrong were already wrong in week one. The scope was never written down. The deposit was "coming soon". Nobody knew who on the client side could approve a draft. A checklist does not make you more creative. It makes sure the boring questions get asked while both sides are still friendly.

A good onboarding flow does three things:

  • It turns a conversation into written facts: deliverables, dates, price, who approves.
  • It moves money before work: a deposit or a first milestone payment.
  • It sets the rules of contact: which channel, how fast you reply, when you are offline.

Run the same steps for every client, in the same order. Clients notice when a freelancer has a process, and they push back less on the parts that protect you.

The checklist, step by step

Use this as a starting point and cut what your work does not need. A logo designer and a bookkeeper will skip different lines, but the order holds for almost everyone.

1. Intake form (before the first call)

Send a short form before you talk. It saves a call and shows you who is serious. Ten questions are enough:

  1. Company name, website and the person who will be your main contact.
  2. Who else approves the work, and who has the final word.
  3. What problem the project should solve, in their words.
  4. What they have already tried, and what did not work.
  5. The deliverable they expect: files, pages, hours, a report.
  6. The deadline, and whether it is fixed (a launch, an event) or flexible.
  7. The budget range they have in mind.
  8. Examples they like and examples they dislike.
  9. Existing materials: brand guide, logins, previous files.
  10. How they prefer to communicate: email, a chat app, calls.

2. Scope and change requests

Write the scope as a short list a stranger could check. "Website redesign" is not a scope. "Five page templates, one round of revisions each, delivered as Figma files" is.

Scope itemWhat to write down
DeliverablesExact items, quantity and file format
RevisionsHow many rounds are included per deliverable
Out of scopeThe obvious next requests you are not doing (copywriting, hosting, ads)
Change requestsHow a new request is priced: hourly rate or a new quote, approved in writing before work starts
Client inputsWhat the client must send, and by when, for your dates to hold

The last row matters more than it looks. If your deadline depends on content the client has to deliver, write that dependency into the scope. Then a late delivery from their side moves your date, not your weekend.

3. Contract and deposit

  • Contract signed before work starts. Even a one-page agreement beats a chat thread.
  • Payment terms. Deposit size, milestone payments, due dates, late fees if you use them.
  • Ownership. When the rights in the work pass to the client, usually after the final payment.
  • Cancellation. What happens to the deposit and the finished work if the project stops.
  • Confidentiality. What you may show in your portfolio and what you may not.
  • Deposit received. Book the start date only when the money has arrived, not when it was promised.

Many freelancers ask for a share of the fee up front and the rest on delivery or in milestones. The exact split is your decision and depends on the project length. What matters is that it is written down and paid before the kickoff.

4. Kickoff call agenda

Keep the kickoff to about 45 minutes and send the agenda the day before:

  1. Introductions: who is on the call and what each person decides.
  2. Goals: what success looks like at the end of the project.
  3. Scope walk-through: read the deliverables list together.
  4. Timeline: milestones, review dates, the final delivery date.
  5. Feedback rules: one consolidated round of comments per draft, from one person.
  6. Open questions from both sides.
  7. Next steps: who sends what, by which date.

Send a written recap within a day. The recap is the document you will point to when a disagreement starts in week four.

5. Access and credentials

  • Ask for your own user account in their tools instead of a shared password.
  • If a password must be shared, use a password manager's sharing feature, never plain email or chat.
  • Keep a short access log: which systems you can reach, and since when.
  • Ask for the lowest permission level that lets you do the job.
  • At the end of the project, list every access you had and ask the client to remove it.

6. Communication rules

RuleExample wording
Main channel"Project questions go by email; the chat is for quick logistics."
Reply time"I reply within one working day."
Working hours"I work Monday to Friday, 9 to 17 in my time zone."
Status updates"A short update every Friday: done, next, blocked."
Urgent issues"For a live site that is down, call me."

7. Payment schedule and invoices

  • Invoice dates tied to milestones, not to your mood at the end of the month.
  • Who receives invoices on the client side, and whether they need a purchase order number.
  • Currency, payment method and who pays transfer fees.
  • Payment term, for example 14 days, written on every invoice.
  • A polite reminder template ready for the day after the due date.

8. First-week milestones

Plan something visible in the first five working days. It reassures the client that the deposit was a good decision, and it gives you early feedback before you build too much.

  • Day 1: welcome email with the recap, the timeline and the contact rules.
  • Day 2: all access confirmed, materials received or chased.
  • Day 3 to 4: first small deliverable, a moodboard, outline or audit.
  • Day 5: first Friday update.

9. Offboarding, planned from the start

Onboarding is easier when you already know how the project ends. Decide now what the handover contains: final files, source files, a short guide, a last invoice and the access removal list. Mention it in the kickoff. Clients like knowing there is a clean finish.

What a paid onboarding kit should contain

You can build all of this yourself. A kit saves you the first few evenings of drafting and gives you documents that already look consistent. On Getly, we measured the shelf on 6 November 2026. The CRM templates, business and finance, and guides and tutorials categories together hold 787 listings, with a median price of $12; the middle half costs between $6 and $19, and 2.2% are free.

The part of that shelf whose listing name contains "onboarding" is small: 7 listings, measured the same day. Their median price is $17, the middle half sits between $14.50 and $19, and none of them is free. By licence, 28.6% state a commercial licence, 14.3% a personal one and 28.6% state none.

A complete kit usually has these parts:

DocumentWhat it should do
Intake questionnaireEditable form or document with the questions above
Proposal or scope templateDeliverables, revisions, out of scope, price
Contract templatePayment terms, ownership, cancellation, confidentiality
Welcome packetHow you work, contact rules, timeline, what the client sends
Kickoff agenda and recapThe meeting structure and a recap email
Invoice and reminder templatesMilestone invoices and a polite overdue note
TrackerA sheet or board to see each client's onboarding status
Offboarding checklistHandover, final invoice, access removal, feedback request

Checks before you buy a kit

  • Editable formats. Look for .docx, Google Docs, Notion, Canva or spreadsheet files in the file list. A PDF alone is fine to read and hard to send to a client with your name on it.
  • Licence for client use. You will send these documents to clients. A personal licence may not cover that. If the listing states no licence, ask the seller before you pay.
  • Contract templates are a starting point. A template written for one country may not fit another. It is not legal advice. For large projects, have a local lawyer read your final version once.
  • Your niche. A kit built for designers has revision rounds; one for bookkeepers has document lists and deadlines. Read the preview images and pick the one closest to your work.
  • Brandable. Check that fonts and colours can be changed, so the welcome packet looks like you, not like the template's author.
  • Price against the shelf. Onboarding-named listings sit around $17 at the median. A kit far above that should show clearly why: more documents, a tracker, a guide.

Where to look on Getly

Browse CRM templates for client trackers and pipelines, Business and finance for contracts, proposals and invoice templates, and Guides and tutorials for written guides on running a freelance practice. Search the shelf for "onboarding" to see the kits by name, and open the file list on each product page before you decide.

Paying and downloading

You can pay by card, with Apple Pay or Google Pay where your device supports it, or with USDT or USDC stablecoins. PayPal is not accepted. You do not need an account to buy. Card orders deliver the files right after payment, and crypto orders right after the payment is confirmed on the network. If a kit is not what the listing described, you can request a refund within the 30-day refund window, and our team reviews the request.

Whatever you buy or build, the checklist is the part that protects you. Run it for the next client, adjust it after the project, and run it again.

Ready to start selling?

Independent marketplace for digital creators. Keep 80–90% of every sale. Accept cards and stablecoins.