Groundwork ← Back Founder Operations   The cluster All guides
Groundwork
← Back All guides
Founder Operations

Client Onboarding Process: 7 Stages and a Copy-Paste Checklist

The seven stages of a client onboarding process for a business of one, what to send at each, the failure each one prevents, a copy-paste checklist, and the six mistakes that cost you the client.

Aziz Chaabane8 min read2 September 2026
Share
On this page
    Quick answer

    A client onboarding process is the fixed sequence you run between a signed contract and the first real piece of work, so that every client gets the same start rather than whatever you remembered that week. Seven stages cover it: confirm the sale in writing, collect payment, gather what you need to begin, set expectations about how you work, hold a kickoff, deliver something small and early, then check in before the first invoice. The checklist below is ready to copy or download. The single most valuable stage is the fourth, because most onboarding failures are not missed steps but mismatched expectations that nobody wrote down. If you fix one thing, put in writing how you communicate, how fast you reply, and how revisions work, before the work starts rather than after the first disagreement.

    Most advice on this topic is a list of best practices from companies with an onboarding team. If you are one person, that is not useful. What you need is a sequence short enough that you will actually run it every time, and specific enough that it prevents the problems that recur.

    The checklist below is that sequence. Seven stages, what to send at each, and the failure each one prevents.

    The Seven Stages, and What Each Prevents

    Every stage exists because of a specific failure. Read them as prevention rather than admin.

    1. Confirm the sale

    A signed agreement plus a plain-language summary of what was agreed. The summary matters more than it sounds: contracts are written to be enforceable, not to be understood, and the summary is what the client actually remembers. Our freelance contract template covers the agreement itself.

    2. Take payment

    Before work, not during. A deposit covers your early costs and filters out clients who were never going to pay. The reaction to a standard deposit is information: someone who negotiates hard on it is often the same person who is slow on every payment after. Our guide to payment milestones covers how to structure the rest.

    3. Collect what you need

    One form, sent once, covering every access credential, asset and contact you will need. The alternative is discovering on day nine that nobody knows who holds the domain login.

    4. Set expectations

    The stage that prevents the most damage and gets skipped the most. Put in writing how fast you reply, which channel the work lives in, how many revision rounds are included, and what happens beyond that. None of this is confrontational when it arrives as part of onboarding. All of it is confrontational when it arrives as a correction three weeks in.

    5. Kickoff

    A short call whose only jobs are confirming what done looks like and naming who has final say. Then a written summary within a day, including anything left undecided. Our meeting agenda template covers running it in half an hour rather than an hour.

    6. Deliver something early

    Anything real, in the first week. Not a progress report. The gap between kickoff and first delivery is where a client's confidence is most fragile, and a small real output closes it in a way that reassurance cannot.

    7. Check in before invoicing

    Ask what is not working while it is still cheap to fix. A concern raised in a check-in is feedback; the same concern raised when your invoice arrives is a dispute.

    The Client Onboarding Checklist

    Client onboarding
    How to use this

    Fill in

    • Every highlighted value. The rest is the sequence and stays as it is.
    • Set your reply window honestly. A promise you miss is worse than a slower one you keep.
    • Name a single channel. Work spread across email, WhatsApp and a portal is work you will lose.

    Check before you start

    • Payment has cleared, not been promised.
    • You have everything in stage 3. Chasing access mid-project costs days.
    • The client knows what done looks like for the first deliverable.

    What goes wrong

    • Starting work before the deposit clears, because the client seemed keen.
    • Leaving communication rules unsaid, then resenting the Sunday messages.
    • A long silence after the kickoff. The client fills it with doubt, not patience.
    Time to first delivery10 DAYS
    01Confirm the saleDay 0
    SendSigned agreement and a plain summary of what was agreedSame day
    PreventsTwo different memories of the scope
    02Take paymentBefore work
    SendDeposit invoice for 40%, due before the start dateDay 0
    PreventsFinancing the project yourself, and clients who were never going to pay
    03Collect what you needDay 1
    SendOne form covering ACCESS, ASSETS, BRAND FILES, KEY CONTACTSDay 1
    PreventsLosing a week to a login nobody could find
    04Set expectationsDay 1
    SendHow you work: reply within 1 BUSINESS DAY, channel is EMAILDay 1
    Send2 rounds of revisions included, extra rounds billed at RATE
    PreventsThe Sunday message, the endless revision loop, the resentment
    05KickoffDay 2 to 3
    Hold30 minute call: confirm what done looks like, name who decidesDay 2
    SendWritten summary within 24 hours, including anything not decidedDay 3
    PreventsBuilding the right thing for the wrong person's opinion
    06Deliver something earlyDay 5 to 7
    SendOne small real output, not a status updateDay 5
    PreventsThe silence after kickoff, which clients read as nothing happening
    07Check in before invoicingDay 10
    AskIs anything not working about how we are running thisDay 10
    PreventsA dispute arriving attached to an invoice

    Rules that make it work

    1. Nothing starts until the deposit has cleared.
    2. Every stage has a day attached, or it drifts.
    3. One channel for the work, agreed in stage 4 and used from then on.
    4. Anything decided on a call is confirmed in writing within 24 hours.
    5. The first real delivery lands inside the first week, however small.
    6. You ask how it is going before you ask to be paid.

    Replace every highlighted value. The days are a working default for a project of a few weeks; compress them for shorter work, but keep the order.

    Aziz's take: Stage four is the one I would defend hardest, and it is the one that feels most awkward to send. Writing down your reply times and revision limits feels like you are being difficult before the work has even started. It is the opposite. Every unspoken rule is one you will eventually enforce in the middle of a disagreement, when it looks like you are inventing it to win an argument. Sent on day one as part of a normal process, it reads as professionalism. Sent on day thirty, it reads as a defence.

    The Six Mistakes That Cost You the Client

    • Starting before payment clears. Not promised, not sent, cleared. This is the most common way freelancers work for free.
    • No written communication rules. You will get messages at eleven at night, and the fault will be that nobody said otherwise.
    • Silence after kickoff. A week of invisible work reads to a client as no work. Deliver something small, early.
    • Collecting access piecemeal. Every separate request is another wait. One form, day one.
    • Not naming who decides. Work approved by the wrong person gets rejected by the right one, and you rebuild it unpaid.
    • Treating onboarding as paperwork. It is the client's first experience of how you work, and it sets what they expect for the whole engagement.

    Making It Repeatable

    The process above is worth writing down once and reusing, because the version you improvise is always shorter than the version you designed. Turn it into a documented procedure and it survives being busy, which is exactly when onboarding gets skipped.

    Our standard operating procedure template covers how to write it up, and includes a worked client onboarding SOP you can adapt. This guide gives you the content of the process; that one gives you the format to keep it in. If onboarding is one of several things eating your week, outsourcing tasks as a small business owner covers what to hand off first, and scaling a service business covers what changes when several clients start at once.

    Frequently Asked Questions

    Seven, in order: confirm the sale in writing with a plain summary of what was agreed, take the deposit before any work starts, collect every access credential and asset in one form, set expectations about communication and revisions in writing, hold a short kickoff that confirms what done looks like and who decides, deliver something small and real inside the first week, then check in before the first invoice. The order matters more than the timings, which you can compress for shorter projects.
    Five-stage models usually run: welcome, information gathering, kickoff, first delivery, and review. That is a reasonable summary, but it hides the two stages where small businesses actually lose money, which are taking payment before starting and putting communication rules in writing. The seven-stage version above separates those out because they are where the recurring problems come from, not because more stages are better.
    The 5 C's come from employee onboarding rather than client work: compliance, clarification, culture, connection and check-back. They translate loosely, with clarification mapping to setting expectations and check-back to the review before invoicing. It is a useful memory aid but a poor checklist for client work, since it says nothing about payment or access collection, which are where client onboarding most often breaks down.
    For a project of a few weeks, about ten days from signature to the check-in, with the first real delivery inside the first week. For shorter work compress the timings but keep the order, since the sequence is what prevents the failures rather than the duration. What matters most is that the gap between kickoff and first delivery stays short. That silence is where client confidence drops fastest, and it is entirely within your control.
    Yes, and arguably more than a larger business does. A team has colleagues who notice when a step is skipped; working alone, the only thing preventing an improvised start is a written sequence. The process also does not need to be elaborate. Seven stages, each with one thing to send and a day attached, fits on a single page and takes minutes to run once it exists.
    Three things, ideally the same day: the countersigned agreement with a plain summary of what was agreed, the deposit invoice with its due date, and a short note saying what happens next and when. That last part is small and does a lot of work, because the period right after signing is when a client is most likely to wonder whether they made the right decision. The information-gathering form can follow the next day.