How to Automate New-Client Onboarding for a Marketing or Design Agency

The first two weeks of a new engagement set the tone for the rest of it. A client who receives a folder, a schedule and a clear list of what you need from them behaves like a client who is being looked after. A client who receives silence starts checking in, and those check-ins turn into the meeting that eats your Thursday.

Agencies rarely have a bad onboarding process. They have a good one that only runs when somebody has the time to run it. This guide turns it into an automation that fires the moment a proposal is signed, so the good version happens in the busy months too.

Setup takes about half a day. After that, onboarding a new client means checking work that has already been done.

What you are building

One trigger and six actions. When a proposal is signed, the automation creates the project workspace, sends a welcome email with a single link, collects everything you need through one intake form, and turns the answers into a first-draft brief your team can argue with. You review the brief and the kickoff agenda. The rest happens without you.

Tools: whatever you send proposals in, a form tool, your project management board, your shared drive, an automation tool (Zapier, Make or n8n) and an AI assistant (ChatGPT or Claude).

Step 1: write down what actually happens now

Do not automate a process nobody has described. Take the last three clients you onboarded and list every message, file and meeting between the signature and the first piece of real work. You will find somewhere between twelve and twenty steps, three of which nobody can explain the reason for.

Cut those three, then sort what is left into two piles: things only a person can do, and things that are identical every time. The second pile is the automation. The first pile is the reason clients hire you instead of software.

Step 2: build one intake form that asks everything once

The biggest source of onboarding drag is asking for things in dribs and drabs. Build one form, ask for everything, and tell the client plainly that it is the only form.

• ·Who signs off, who attends meetings, and who should not be chased on a Friday.
• ·Access: domain, analytics, ad accounts, social profiles, CMS, whatever the work touches. Ask for the route in, not for passwords in a form field.
• ·Brand: logo files, fonts, colours, existing guidelines, and three examples of work they like from anyone at all.
• ·The commercial reality: what the work has to achieve, what has already been tried, and what is off the table.
• ·Deadlines they already have, including the ones that have nothing to do with you.

Fifteen to twenty questions is the right size. Put the awkward questions in the middle, where people are committed enough to answer them properly.

Step 3: turn the intake answers into a first-draft brief

This is the part that used to cost an account lead two hours. Feed the form responses to your AI assistant and ask for a working brief rather than a summary.

The instruction to mark gaps as OPEN QUESTION is what makes the output usable. A brief that quietly invents a target audience is worse than no brief at all, because somebody will design against it.

Step 4: wire the sequence

In your automation tool this is one scenario, triggered by a signed proposal.

1. 1Create the client folder in your shared drive from a template folder, so the subfolders and the naming convention are right from minute one.
2. 2Create the project on your board from a template, with the standard tasks and the standard owners already attached.
3. 3Send the welcome email. One email, one link, one clear ask: complete the intake form by a named date.
4. 4Wait for the form. When it arrives, drop the answers into the project as a card and into the folder as a document.
5. 5Call the AI assistant with the intake-to-brief prompt and save the result where your team works, clearly labelled as a draft.
6. 6Create the kickoff meeting invitation with the agenda attached, and tell the account lead there is a brief waiting to be reviewed.

Add one branch based on a delay: if the form has not been completed after four days, send a short reminder to the client and a note to the account lead. That branch is the whole reason to automate this instead of writing a checklist.

Two things should stay out of the scenario. Do not automate the introduction to the team, because a name inside an automated email is not an introduction. And do not automate the first phone call. Anything whose purpose is to show that a person has read the file has to be done by the person who read the file.

Step 5: write the two client-facing messages properly

Only two messages in this sequence are read by the client, so both are worth twenty minutes each.

The second message is the kickoff agenda, and the rule there is that it goes out before the call rather than after. A client who has read the agenda arrives with the decision-maker on the call, which is the single thing that makes a kickoff worth having.

What changes

The work does not get smaller. The variance does. Every client gets the same folder, the same form, the same first draft and the same kickoff, whether they signed in a quiet February or on the Friday before three deadlines.

Onboarding is one of the standard builds in Workflow 05: Build Automation Workflows, the AutomateFirst module about connecting the tools you already pay for so the repeatable half of the job runs itself. This guide is that build written out in full and free. The playbook has six more like it for $297, with a 30 day refund.