A client signs. Everybody is pleased. And then, in a great many studios, nothing visible happens for four days while the work gets scheduled — during which the client, who has just spent money, hears nothing at all.
That gap is the most expensive silence in the whole engagement. It is where a client decides whether they made a good decision, and it is where the expectations that will govern the next three months are set by default rather than by you.
What onboarding actually has to produce
Not a welcome pack. Seven concrete outputs, and if a step in your process does not produce one of them it is ceremony:
- A named person on each side who answers, and who is allowed to approve.
- One channel the work is discussed in, chosen by them and agreed by you.
- A start date and a first-deliverable date, both written where both parties can see them.
- Everything you need from them, in one request, with a deadline on it.
- Access: brand assets, accounts, whatever the job needs, requested once.
- The money schedule, restated after signature rather than left in the proposal.
- A definition of done for the first deliverable, in one sentence they agreed to.
Every scope argument we have ever had, and every unpaid overrun, traces back to one of those seven being implied instead of written.
The one request, not the drip
The strongest single change most studios can make is to stop asking for things as they become relevant. Asking six times over three weeks trains the client that requests from you are background noise. Asking once, completely, with a date, gets answered — and when it does not, you have one clean thing to chase rather than six.
Write the request as a list a busy person can complete in one sitting, mark what is genuinely blocking, and say what happens to the timeline if it arrives late. That last sentence is not a threat. It is the only way a deadline stays real without somebody having to be unpleasant about it in week three.
What to automate, and what not to
Three of the seven are pure mechanics and should happen without you: the workspace or folder structure, the intake request going out with its deadline, and the reminders when it is not returned. Two more should be prepared and then sent by you: the confirmation of dates, and the restatement of the money schedule — both are short, both are read closely, and both are places a wrong number is remembered for a year.
The two that must stay human are the kickoff conversation and the definition of done. Not because software could not draft them, but because the value of both is that a person on your side committed to them out loud.
Onboarding is not a sequence of emails. It is the moment you establish that things you say will happen, happen.
A week that works
- Day 0, within the hour: signature acknowledged, kickoff time offered, intake request sent with its deadline.
- Day 1: workspace ready, access requested, both dates confirmed in writing.
- Day 2 or 3: kickoff call, thirty minutes, ending with the definition of done read back.
- Day 4: first reminder for anything outstanding, in a sentence, without apology.
- Day 5: the first visible artefact — a plan, an outline, a rough — even if the real work starts next week.
That last line is the one that gets skipped and the one that does the most work. Something visible in week one is what converts a client’s decision to hire you into confidence that they were right, and confidence is what buys you a calm week five.
The part that decays
Every studio we know has had a good onboarding process. Most of them have it written down somewhere. What breaks it is not disagreement about the steps — it is the third busy fortnight in a row, when the checklist is in a document nobody opens and the kickoff quietly becomes an email.
Which is the honest argument for putting the process into software rather than a template: not that the steps are hard, but that a process only survives the weeks when nobody has time to remember it.