The agency client onboarding process: everything between yes and the first deliverable

Type "agency onboarding" into Google and it finishes the phrase four ways: process, checklist, form, and "marketing agency client onboarding template." That was autocomplete on 10 October 2026.

Most of what ranks is a welcome-pack PDF with a logo on the cover.

The pack is the least important part. The order is what matters.

Here is the complication. A client who said yes on a call can still be a client who never pays, never sends the files, and never approves anything. Onboarding is where you find out which one you have, before you have spent a week of editor time finding out the expensive way.

So this is the sequence I would run for any agency in the VALORAE group, written as a method. No client stories, no numbers I cannot show you.

Step 1: Signature and first invoice before kickoff

Nothing gets scheduled until the agreement is signed and the first invoice is either paid or has a date on it.

That sounds cold. It is the opposite. A kickoff call before paperwork tells the client the paperwork is optional.

The agreement should name the deliverables, the start date, the payment terms and the end or review date. If it is a monthly arrangement, I covered what a retainer should and should not buy separately.

Payment terms need a date, not a trigger. "Paid when the client pays" is a trigger. Your editors should get the same courtesy, which is why I pay them on the agreed date whether or not the client has paid.

Step 2: Access through roles, never a password

The second thing you ask for is access. And the answer to "can I just send you my login?" is no.

Every major platform has a delegated role for this. Meta Business Suite, YouTube channel permissions, LinkedIn page admin roles, TikTok business roles. The client grants a named person a specific role, keeps their two-factor on, and can remove it in one click.

VALORAE Media's answer is the same, and the reasons are laid out in never give your agency your password. The short reason: a shared login has no audit trail, and when something goes wrong the agency becomes the suspect.

The client also keeps ownership. Accounts stay under their email and their recovery phone. If an account was set up under someone else's details, fixing that is the first task, before any content is made.

Step 3: One intake form, returned before the call

The intake form exists so the kickoff call is spent deciding things, not collecting them.

Send it the same day the agreement is signed. One page. If it runs longer, it does not come back.

The template is further down. What matters here is the rule: no form, no kickoff. A client who will not fill in one page will not approve a batch on time either. That is a useful signal to get early.

VALORAE Arc publishes its own version of this for podcast clipping, a post on what to send your clipper before the first episode. Master files, separate speaker tracks, brand files, a one-page brief and a do-not-clip list. Swap the trade and the shape holds.

Step 4: One kickoff call, three decisions

The kickoff is short and ends with three things written down.

Who approves. One named person, not "the team." Two approvers with different taste is how a first batch turns into a fourth round.

What the work is for. Growth, leads, a launch, the founder's profile. When two goals conflict, which one wins.

When the first deliverable lands. A date, agreed on the call, sized so you can hit it comfortably.

Then send a recap the same day. The recap is the record. If it is not in the recap, it was not agreed.

Step 5: Agree the approval loop before the first draft

Most onboarding guides skip this. It causes the most damage later.

Settle how drafts are sent, where feedback goes, how many revision rounds are included, and what happens if feedback does not arrive. Silence should have a default. A workable one: a batch with no feedback by the agreed date goes ahead as delivered.

Write it into the recap as well as the contract. Nobody rereads the contract.

Step 6: Ship a small first deliverable

The first deliverable is a test of the whole process, so keep it small.

A short batch, delivered on the date from the kickoff. It shows the client what a normal week looks like, and it shows you whether the files, access and approver all work.

Small beats impressive here. A huge first batch built on a misread brief costs the most to redo.

Step 7: The first-week check-in

Book it during the kickoff, for the end of week one. Fifteen minutes, three questions.

What landed. What missed. What do you need from us that you did not get.

Then fix the process along with the deliverable. If files arrived late, change the intake. If feedback came from two people, rename the approver.

This is the contrarian part. Onboarding never really ends.

The check-in is where it turns into the operating rhythm. Skip it and the first problem shows up as a cancellation instead of a comment.

The onboarding form (template)

This is a template, not a form any VALORAE venture sends word for word. Copy it, cut what your trade does not need, keep it to one page.

1. Who signs off on the work? One name, plus their preferred contact method.
2. What is this work for in the next three months? If goals conflict, which one wins?
3. Who is the audience, and what do they already know?
4. Which accounts will the work appear on? Links, please, not handles from memory.
5. Have you granted access through platform roles? (We do not accept passwords.)
6. Which brand files exist? Fonts, colour codes, logo files, any style guide.
7. Share two or three examples you like and two you dislike, with one line on why.
8. What must never be published? Topics, names, embargoed news, anything sensitive.
9. Who else has access to these accounts today?
10. How do you want feedback collected, and by when after each delivery?

Question 9 is the one people leave off. It tells you who else can post, and who to ask when something changes that you did not touch.

The short version

• Get the signature and first payment settled before any kickoff.
• Ask for platform roles, never a password, and keep accounts in the client's name.
• Send a one-page intake form and hold the kickoff only once it is back.
• Leave the kickoff with one approver, one goal and one delivery date.
• Write the approval loop, including what silence means, into the recap.
• Ship a small first batch, then hold the week-one check-in and fix the process.

I write operator notes like this at tgsidd.com.