Most client onboarding problems are actually process problems disguised as people problems.
The client who ghosts your access request isn't being difficult — you sent them a wall of text and no clear next step. The project that started two weeks late didn't stall because of scope — you never had a proper kickoff brief.
A working onboarding system does three things: it collects the right information before work starts, it gets access credentials without drama, and it creates shared context so everyone knows what day one looks like. Nothing more. Here's how to build one in 90 minutes.
Phase 1 — The Intake (30 minutes)
Before you build anything, write down the 8–12 questions you wish you'd asked every client before starting.
Here's the core set that works across most agency types:
About the project:
- What does success look like at the end of month one?
- What's already been tried and didn't work?
- Are there any internal stakeholders we'll need approval from?
- What's the hard deadline, and what's the consequence if we miss it?
About their setup:
- What tools do you currently use? (CRM, project management, design, comms)
- Who has admin access to those tools?
- Is there an existing brand guide, style guide, or previous deliverables we should know about?
About communication:
- Who's our main point of contact?
- What's your preferred communication channel and response time expectation?
- How do you prefer to give feedback — async or on calls?
Turn this into a single-page form. Google Forms works. A Notion form works. A simple email template works. The format doesn't matter; the consistency does. Every client gets the same intake before the kickoff meeting.
Actual tactic: fill in the form yourself for a recent past client before you send it to anyone new. This reveals the gaps in about 10 minutes.
Phase 2 — The Access Request Sequence (20 minutes)
Access collection is where 80% of onboarding delays happen. Most agencies send one email and wait. Then they send a follow-up. Then they're on a call and the client says "oh, I thought someone else was handling that."
Build three emails. Write them now, save them as templates.
Email 1 — Initial request (sent day after intake):
Subject: [Project Name] — Access needed before we start
Hi [Name],
To kick off [Project Name] on schedule, we need access to a few things before our first meeting. Here's exactly what we need and who typically has it:
- [Tool 1] — usually your IT admin or the account owner
- [Tool 2] — your marketing manager or whoever manages the account
- [Tool 3] — your team's Google/Microsoft admin
Can you send these over or loop in the right person by [date — 3 business days out]? Once we have them, we're ready to start.
[Your name]
Email 2 — Follow-up (day 3, if no response):
Subject: Re: [Project Name] — Access needed before we start
Quick nudge — still need the items from my last email. Start date is [date]. Forwarding to whoever holds these accounts works too.
Still outstanding: [list only what's missing]
Email 3 — Final flag (day 5):
Subject: Re: [Project Name] — Start date at risk
We're two days from [start date] and still waiting on [tools]. Without these, we'll need to push the start by [X] days. Happy to jump on a 10-minute call today if that's easier.
The escalation is intentional. Most clients aren't ignoring you — they just haven't prioritized it. A visible deadline changes that without being aggressive.
Phase 3 — The Kickoff Brief (20 minutes)
The kickoff meeting is expensive. Everyone's on it, attention is limited, and you only get one shot to establish how the project will run.
The kickoff brief is a one-page document you prepare before the meeting. You share it the day before so everyone arrives with context, not questions.
What goes in it:
- Project name and start/end dates
- What you'll deliver (stated in outcomes, not tasks)
- What you won't cover (the explicit exclusions)
- Who does what (roles for both your team and the client)
- The communication plan (how, where, and how often)
- The three things that could slow this down (be honest)
- What a good first week looks like
This document does two things: it surfaces misalignments before they become problems, and it gives the client something to reference when they're tempted to add scope.
Build the template once. Fill it in for each new client before the kickoff. Takes 15 minutes once you have the intake responses.
Phase 4a — Folder Structure (10 minutes)
Pick a structure and enforce it. Here's one that works across most agency types:
[Client Name]/
00_Admin/ ← contracts, invoices, SOW
01_Brief/ ← intake form, kickoff brief, notes
02_Assets/ ← logos, brand files, existing content
03_Working/ ← live work, versioned by date
04_Deliverables/ ← final files shared with client
05_Archive/ ← everything superseded
Create this on day one. Resist the urge to customize it per client. Consistency means any team member can pick up a project without a briefing.
Phase 4b — The Post-Onboarding Review (10 minutes)
At the end of week one, answer three questions:
- What information did we need that we didn't have at the start?
- What access took longer than it should have?
- What would have made the kickoff meeting more useful?
Update your intake form and kickoff template based on what you find. This is the only mechanism that makes the system better over time — without it, you repeat the same gaps on every project.
The honest shortcut
If you'd rather skip the build and start with a complete system — including 27-question intake form, 3 access email sequences, kickoff brief template, SOPs, and a folder structure — Agency Onboarding OS has the full package for €49. But the 90-minute version above works too.
The worst outcome is spending six more months with a broken process because fixing it felt like a project. It isn't.