Agency client onboarding SOP template
By The Onbo team · Updated
Short answer
A client onboarding SOP writes down how your agency starts every project: each step's trigger, owner, actions and definition of done, from the accepted proposal to the brief in your project tool. Keep it to a page or two, store it where the team works, and review it after every few projects so it matches what you actually do.
In a small agency, onboarding usually lives in the founder’s head. That works until the founder is on holiday, a new account manager joins, or two projects start in the same week. A short standard operating procedure turns “how we usually do it” into something anyone on the team can follow, and makes every client’s first week consistent.
What makes an SOP useful?
A useful SOP is short, specific and kept current. It says what triggers each step, so nobody has to decide when to start. It names an owner, so nothing falls between two people. It defines done, so everyone knows when to move on. And it links to the templates used, so nobody rewrites the welcome email from memory. An SOP that’s long, vague or out of date gets ignored within a month.
The onboarding SOP template
Purpose: Start every new client the same way, from accepted proposal to delivery.
Owner of this SOP: [name] · Last reviewed: [date]
| # | Step | Trigger | Owner | Actions | Done when | Template |
|---|---|---|---|---|---|---|
| 1 | Welcome | Proposal accepted | Account lead | Send welcome message with onboarding link | Client has the link | Welcome email |
| 2 | Agreement | Link sent | Account lead | Follow up if not accepted in [n] days | Agreement accepted | Agreement |
| 3 | Deposit | Agreement accepted | Account lead | Confirm payment when it arrives | Deposit recorded | Invoice |
| 4 | Questionnaire | Deposit paid | Project lead | Review answers the day they arrive | Answers in, gaps listed | Questionnaire |
| 5 | Files | Questionnaire done | Project lead | Check formats on arrival | Files in client folder | File list |
| 6 | Internal kickoff | Answers and files in | Project lead | Agree roles, risks, plan | Plan agreed | Kickoff agenda |
| 7 | Client kickoff | Internal kickoff done | Project lead | Run call; record decisions | Decisions recorded | Agenda |
| 8 | Brief and hand-off | Client kickoff done | Project lead | Write brief; confirm with client | Brief in project tool | Brief template |
Common problems and fixes
| Problem | Fix |
|---|---|
| Client hasn’t accepted after reminders | Account lead calls to ask what’s unclear |
| Files arrive in the wrong format | Reply the same day with the format needed |
| Decision maker missing from kickoff | Reschedule rather than proceed without them |
How do you write it?
Start by writing down what happened on your last two projects, step by step, then turn that into the table. Use your real tools and templates rather than ideal ones; you can improve the process once it’s written. Keep each action to a line. Where judgment is needed, say who makes the call rather than trying to cover every case. And put the SOP where the team already works, linked from your project template, not in a folder nobody opens.
For example, a seven-person creative agency might write its SOP after noticing that two account managers onboarded clients in completely different ways. The table takes an afternoon to agree. Within a month, new projects reach the internal kickoff in a predictable number of days, and the newest team member runs onboarding alone after shadowing it once.
How do you keep it current?
Review it after every few projects, or whenever someone works around it. A workaround usually means the SOP is wrong, not the person. Note the review date at the top, and change one thing at a time so you can tell what helped. When you change a template, update the link in the SOP the same day.
An SOP checklist
- Purpose stated in one line
- Every step has a trigger
- Every step has one owner
- Every step has a definition of done
- Templates linked, not described
- Common problems and fixes listed
- One to two pages long
- Stored where the team works
- Review date at the top
- Reviewed after every few projects
The workflow behind this SOP is explained in the agency project kickoff workflow, and the brief at step 8 in the project hand-off brief template.
Where Onbo fits
Onbo automates steps 1 to 5 of this SOP. One link takes each client through your agreement, the deposit through your own payment link, your questionnaire and file uploads into your Google Drive, in order, with reminders for anything unfinished. When it’s all in, Onbo produces a Markdown hand-off brief for steps 6 to 8. Up to 5 people share an account. Try it free for 30 days; see pricing.
Questions
How do I document our client onboarding process?
Write each step with what triggers it, who owns it, the actions involved and what 'done' looks like. Keep it short, store it where the team works and review it regularly.
What should an onboarding SOP include?
The steps from accepted proposal to delivery start, with triggers, owners, actions, definitions of done, templates used and common problems with their fixes.
How long should an SOP be?
As short as it can be while still being followed without questions, usually one or two pages for client onboarding.