Onboarding a new client after they say yes

A deal closes on a Friday afternoon and the next Monday feels like a different project.

The contract is signed, the deposit is in, and the client wrote back a cheerful "let's go". On Monday morning you open a fresh email and discover that you and they have slightly different ideas about what happens next. They think you have started. You are still looking for the file. The first week is where the misunderstanding costs the least to fix, and where, left alone, it costs the most.

This article is about the four things to send before the work starts, the one thing to refuse, and how the first round sets the tone for the rest of the job.

What the client thinks is happening

Most clients, when they say yes, do not picture the next two weeks. They picture the finished thing. The gap between "yes" and "starting" is the bit they never model, and a sizeable share of the friction of a job comes from this gap being left empty.

A client who has not been told what comes next will invent something. They will email on a Saturday because they have remembered something, they will write to your personal address because the work email does not seem right for "the next thing", and they will pull forward a deadline they had agreed to because, in their head, you are already working. None of these are bad faith. They are what an empty onboarding looks like.

The four things to send before work starts

All four go out together, in one message, on the day the deal closes. They are short on purpose: each one answers a question the client is about to ask anyway.

The single channel. Email, form, project page, your choice, but pick one and name it. The sentence to say is a simple one: one address, for everything about this job, where we both find it later. Without it, requests arrive by text on a Sunday within a fortnight, and you are following one job across three channels before you have had a chance to prevent it.

The first set of questions. Not the creative brief, which you already have. The questions about access, passwords, the name of the person who holds the login, the address of the staging server, the printer's contact, the asset library, the contact at the magazine. The things you cannot start without, gathered in one short list. Asking for them in a single message with a single reply is the first time the client sees how the rest of the job will run.

The calendar. Three dates, written down: when you start, when the first round lands, when the final delivery is expected. Not the polished version in the quote, the operational one. The polished version promised a window; this one gives a specific day for the next thing they will see.

The invoice reminder. Not a new invoice. A line that says: the deposit is due on this date, the balance on this date, and the delivery opens when the balance clears, as in deposit, balance, delivery. It is the one paragraph of the welcome message that does not read as warmth, and it is the one that prevents three months of chasing later.

The one thing to refuse

The client wants a kick-off call.

It is a reasonable request and it is a trap. A one-hour call on the Wednesday of the week that just started, with four people who have not yet read each other's emails, settles nothing that an email would not settle better. It produces an audio recording nobody listens to again, a shared document that drifts from the truth within a week, and a tone that gets set in the room rather than in the work.

What works better: the four messages above, sent together, and the offer of a fifteen-minute call on the second week, once the first round is in their hands. By then the call has something to discuss, and the fifteen minutes are enough.

If the client pushes, the honest version is: I would rather have something to look at together than talk about it first. Most clients accept this once they have heard it, because most clients have sat through a kick-off call that went nowhere and remember it.

The first round sets the tone

The first round of feedback is the part of the job the client remembers. It is what they describe to their partner, their colleague, their manager. It is also the round on which the rest of the rounds get modelled.

So three things, in this order.

Send something rough, early. A direction, not a finish. Three sketches, a first paragraph, a wireframe, a test render. The argument is the one in how many rounds of feedback to plan for: a round spent on direction costs an hour, a round spent on finished work costs a day. The first round, in particular, is the one to keep cheap.

Ask for remarks gathered in one go. The same sentence, in the message that goes with the work: take your time, send everything in one reply, including the small details. Without it, the first round arrives in three messages across two days, and three messages is what the rest of the rounds then look like.

Reply with a written note, not a fix. When the remarks come back, send a short reply that lists what you will change, what you will not change, and why. It is the document the client can refer back to in round three, when somebody has forgotten what was agreed in round one, and it is the document that turns a conversation into a paper trail.

What changes when onboarding goes well

A week in, the client stops writing to ask where things are. They have the date, they have the channel, they have the rough first pass. They know what the next thing is and roughly when it will arrive. The job feels calm to them, and a calm client is a client who does not generate rounds of feedback out of anxiety.

It also feels calm to you, which is the part the brief did not promise but which is, in the end, the only one that matters.

What Kalepio does with it

The first message after the signature is the one a studio writes once and sends to every new job: the channel, the access questions, the calendar, the payment dates. It lives at the same address as the brief, with the same branding, and the answers land in the same place the studio reads them.

The first round, when it comes, sits beside the brief and the contract. The client cannot lose it, you do not have to remind them where it is, and the next round opens with what the last one settled still in view.

For what comes before the yes, what a freelance quote needs; for what to ask before the work begins, what a brief form has to contain, trade by trade.

Frequently asked questions

How do you onboard a new client after signing?

Send one message, on the day the deal closes, with four things: the single channel for the job, the short list of access questions, the calendar with three dates, and the line about when each invoice is due. Each one answers a question the client is about to ask anyway.

Should you have a kick-off call with a new client?

Usually no. A kick-off call with nothing on the table settles nothing an email would not settle better, and it sets the tone in a room rather than in the work. Offer a short call in the second week, once the first round is in their hands.

What should the first round of feedback be?

Something rough, sent early: a direction, not a finish. A first round spent on direction costs an hour, a round spent on finished work costs a day, and the first round is the one that sets the tone for the rest of the job.

How do you stop a client writing in from three different places?

Name one channel in the first message and ask for everything about the job to go through it. Without it, requests arrive by text within a fortnight and the three-channel pattern takes root before you have had a chance to prevent it.

What do you do with the client's first round of remarks?

Reply with a short written note that lists what you will change, what you will not change, and why. It is the document the client can refer back to in round three, and it turns a conversation into a paper trail.