To onboard a new client without your senior people, capture the client's context at kickoff, not their task list. Write down why they hired you, what success means, who approves what, their voice and their no-go list. Put it in one place your team and AI tools read. Then questions go to the doc, not the director.
Your senior people are not the bottleneck. They are the database.
Here is what most agency owners get wrong. They think seniors get pulled into onboarding because new clients are hard. So they try to train juniors harder.
That is not it. Seniors get pulled in because they are the only place the client context lives. They sat on the sales call. They heard what the founder really cares about. They know the last agency got fired for being too slow.
None of that made it into the kickoff deck. So every question routes back to them.
Your senior person is not a bottleneck. They are a database with no export button. The fix is not more training. It is an export.
Why every new client pulls them back in
It is not your team's fault. Most kickoffs are built to collect access and deadlines. Logins. Brand files. A launch date. That is the task list.
The task list is the easy part. The hard part is everything that makes this client different from the last 10. How they talk. What they will never approve. Which stakeholder can kill a campaign with 1 email.
That context gets shared out loud on calls. It lives in a director's notes, or nowhere. Then a designer asks a question, or an AI draft misses the tone, and the director gets pinged. Again.
I scaled a 25-person agency the hard way. The bigger it got, the less profitable it became. A big reason was this exact loop. Every new client was another week of seniors re-explaining. So I documented every single job. Then I rebuilt each one as AI.
What to capture at kickoff: the 6 kinds of context
Before the checklist, know what you are hunting for. Every kickoff should leave you with these 6 things written down.
- The why. Why they hired you now. What broke. What the last agency got wrong.
- The win. What success looks like in their words, and the 1 number they watch.
- The people. Who approves what. Who can veto. Who just needs to be cc'd.
- The voice. How they talk, words they love, words they hate.
- The no-go list. Claims you cannot make. Topics to avoid. Competitors never to name.
- The history. What they tried before, what worked and what flopped.
If your kickoff ends without all 6, it is not done. Someone senior will fill the gaps later, one Slack message at a time.
The kickoff checklist
Copy this. Any account manager can run it. The senior person reviews the output once, not the whole call.
Before the call
- Pull the sales call notes and recording into the client folder.
- Pre-fill what you already know from the proposal and the contract.
- Send the client a short form: approvers, brand files, logins, past reports.
- List the open questions the sales team could not answer.
On the call
- Ask: "Why did you hire us now, and not 6 months ago?"
- Ask: "What would make you renew in 12 months?"
- Ask: "What number do you check first every Monday?"
- Ask: "Who signs off on copy, on spend and on creative?"
- Ask: "Who can stop a campaign, even if they are not on this call?"
- Ask: "Show me 1 piece of work you loved and 1 you hated. Why?"
- Ask: "What words or claims should we never use?"
- Ask: "What did your last agency or hire get wrong?"
- Ask: "How fast do you expect replies, and on what channel?"
- Record the call. Quotes beat summaries.
After the call
- Fill in the client context doc the same day, while it is fresh.
- Paste their exact words for goals and voice. Do not paraphrase.
- Send the doc to the senior person for 1 review pass. They add what only they know.
- Send the "win" and the approval map back to the client to confirm.
- Connect the doc to the AI tools your team uses for this client.
- Book the first check in. Agenda item 1: "What did we get wrong about you?"
That last step matters. Clients correct you early if you ask. If you do not, they correct you later through revision rounds.
Who runs the kickoff
The account manager runs it. Not the founder. Not the director.
The senior person has 1 job: review the context doc once, within 24 hours. They add the things they heard on the sales call that did not make it into the notes. Then they step out.
This flips the order. Today, seniors stay close because the context is in their head. With the doc, the context is on the page. Seniors approve it once and move on.
This is the core of Portable Delivery Intelligence. Each client's strategy, rules, priorities and approvals sit in one place. That place connects to ChatGPT, Claude or Gemini, whichever your team already uses. The context travels with the work. Nobody re-briefs the AI. Nobody re-explains the client.
The first 30 days: the doc answers first
The kickoff only works if the team uses the doc. So set 1 rule for the first 30 days.
Every question goes to the doc first. If the answer is there, use it. If it is not, ask the account manager. If the account manager does not know, then ask the senior person.
And the second half of the rule: if a question gets asked twice, the answer goes in the doc. That is how the doc gets better every week without a big rewrite.
Track how often seniors get pulled in during month 1. That count is your onboarding score. It should fall as the doc fills in. If it does not, your kickoff is still missing one of the 6 kinds of context.
You can see how onboarding ties into total team load on our agency capacity page.
Why this matters past onboarding
Onboarding is where the leak starts. If context stays in heads on day 1, it stays there forever. Every handoff, every new freelancer and every AI draft pays the tax.
That tax is why 4 to 8 accounts per account manager is the common ceiling. 18 to 25 is our per-operator target with Portable Delivery Intelligence in place. The difference is not effort. It is where the client lives.
Hype is not a plan. Data is. Our "25 to 1" model comes from internal mapping: 1 operator plus the system carries the work a 25-person marketing team used to carry. The same delivery system has supported $7M in client revenue. We hold 42 verified Upwork reviews, 5.0, Top 1% Expert-Vetted. Clients include Bowen eBikes and Kajeet. The full proof is here.
FAQ
Should the founder still join the kickoff call?
They can join for 10 minutes to welcome the client. Then they hand off. Their real job is the 1 review pass on the context doc afterward.
What if the client will not answer the deeper questions?
Ask for examples instead. "Show me work you loved and work you hated" gets you voice and taste faster than any direct question.
How long should the client context doc be?
Long enough to answer the 6 kinds of context. Most of the value is in exact quotes and the no-go list, not in length.
Does this work if my team does not use AI yet?
Yes. The doc helps humans first. Connecting it to AI tools is the step that lets each person carry more accounts.
Bring one client account. We map where your team's time leaks and how many more accounts each person could carry. You keep the map either way. Book your mapping session here.