The agency that closes a client confidently and then stumbles through the first two weeks has already started losing them. Clients form their lasting impression of you not from the proposal but from what happens after they sign. A structured, repeatable onboarding process turns that critical window into a trust deposit you collect for the entire engagement.
Why most agencies skip the process and pay for it later
Creative agencies tend to be great at delivering work and weak at delivering structure. When every onboarding is improvised, small things fall through: the brand asset folder never gets shared, the client’s billing contact is never confirmed, the project scope is buried in an email thread from three weeks ago. The client notices. They start sending check-in messages not because they are impatient but because they have no other way to know what is happening. Each of those messages is a signal that your process has a hole.
The fix is not a heavier contract or a longer kickoff call. It is a documented, templated sequence that runs the same way for every new account, regardless of who on your team handles it.
The kickoff access checklist
Before the kickoff call happens, send the client a short checklist of what you need from them. Doing this before the call, not during it, means you can spend the call on strategy rather than logistics. The checklist should cover every account and asset you will touch. Customize it per project type, but keep a master template as your baseline.
- Website and hosting. Admin login, FTP or hosting panel credentials, domain registrar access if DNS changes are expected.
- Brand assets. Logo files (SVG and PNG), brand guide or style tile, approved fonts, approved color hex codes.
- Analytics and ads. Google Analytics property access, Google Search Console, Meta Business Manager seat, ad account IDs.
- Social accounts. Admin or manager access to every platform you will post on, not just view access.
- Billing and legal. Accounts payable contact, billing email, signed contract on file, any NDAs required.
- Communication preferences. Primary contact name, preferred channel (email vs. Slack vs. PM tool), expected response-time window.
Send this checklist within 24 hours of the contract being signed. Use a shared document or a portal link, not an email thread, so nothing gets buried. Log which items are outstanding and follow up on day 3 and day 7 if anything is missing. Do not start billable work on a deliverable that depends on an asset you have not received.
Setting expectations and creating one source of truth
The kickoff call has one job: align on scope, timeline, and communication. Everything you agree to on that call should be written down in a single project brief that both sides sign off on. If it exists only in the meeting recording, it does not exist.
- Write a project brief, not just a scope of work The scope of work lists deliverables. The project brief adds context: the client’s business goal, the success metric for this engagement, the key constraints (budget, deadline, brand restrictions), and what is explicitly out of scope. Out-of-scope is as important as in-scope. When a client asks for “one small addition” six weeks in, this is the document you open together.
- Define a single communication home Pick one place for all project communication: a shared Slack channel, a client portal, or a project management space. Tell the client explicitly: “If you need something, message us here. If we email you outside this space it will be for time-sensitive items only.” This eliminates the scattered thread problem where decisions live in three different inboxes.
- Set a response-time expectation in writing Tell the client how long they should expect to wait for a response from your team (example: within one business day). Then tell them what you need from them: feedback turnaround times, approval windows. If feedback is not received within five business days, work may be paused to protect the timeline. Put this in the project brief.
- Schedule standing check-ins on day one Do not leave recurring calls as “we’ll figure it out.” Book the first four bi-weekly check-ins on the kickoff call itself. Clients who feel informed cancel far less often than clients who have to chase updates.
The first 30 days plan
The first 30 days determine whether the client tells other people about you. Break it into three 10-day windows.
| Window | Your goal | Client-facing milestone |
|---|---|---|
| Days 1 to 10 | Complete access gathering, audit existing assets, deliver discovery findings | Receive a written summary of what you found and what comes next |
| Days 11 to 20 | Deliver first tangible output (draft, wireframe, first content piece, strategy deck) | See something real for the first time, give first round of feedback |
| Days 21 to 30 | Incorporate feedback, show revised version, confirm month-two plan | Approve a deliverable or milestone, feel momentum building |
The principle: the client should never go more than 10 days without receiving something from you. Silence is interpreted as stalling. Even a brief “here is what we worked on this week and what is next” message counts. It keeps their confidence level above the anxiety threshold.
Collecting assets and approvals without chasing
The number one reason projects run late is not slow creative work. It is slow client response. You can engineer most of this out of your process.
- Set a decision deadline, not an open-ended ask. Instead of “let me know your thoughts,” say “please send feedback by Thursday EOD so we can hit next week’s milestone.” Specific beats open-ended every time.
- Limit revision rounds in the contract. Define the number of revision rounds included (typically two). After that, additional rounds are billed at an hourly rate. State this in the project brief. Clients who know there is a boundary use their revisions thoughtfully.
- Use an approval record. Every approved deliverable should have a written sign-off, even a one-line email reply or a task marked approved. This protects you if scope creep appears later and the client claims they never approved the direction.
- Build a 48-hour buffer into every deadline you quote. Quote the client a delivery date that is two days earlier than your internal deadline. The buffer absorbs late-arriving feedback without blowing the final date.
- Create a shared asset folder on day one. Give the client write access to a shared folder (Google Drive, Dropbox) labeled clearly. Ask them to drop all assets there rather than sending them by email. This eliminates the “I sent you the logo last month” back-and-forth.
Templating the whole thing so it scales
A process you rebuilt from scratch for every client is not a process. It is a hope. Templating means the next account gets the same quality as the first, even when you are slammed.
- Build a master onboarding template in your project workspace Create a template project with every standard task, due date formula (relative to contract date), and assigned role. When a new client signs, duplicate the template and adjust dates. Every task should have a clear owner and a clear output.
- Write fill-in-the-blank message templates The welcome email, the kickoff agenda, the “here is what we found” discovery email, the first-deliverable email, the 30-day check-in message. Write them once with [CLIENT NAME] and [PROJECT] placeholders. Personalize the first paragraph; keep the rest consistent. These save 20 to 40 minutes per client and eliminate the risk of forgetting a step.
- Document the process so anyone on your team can run it If only one person knows how to onboard a client, you have a bottleneck. Write a one-page internal SOP (standard operating procedure) that any account manager can follow. Include links to the templates, the access checklist, and the project brief format.
- Review and improve the template quarterly At the end of every quarter, look at which onboarding steps consistently generate client questions or delays. That is a signal the template has a gap. Update it before the next client signs. A living template gets better with every account.
Studio Craft is built around this model: client workspaces, onboarding task templates, asset libraries, and approval workflows live in one place so your team is not stitching together five different tools to run a single account.
Measuring whether your onboarding is working
Gut feel is not a metric. Track these numbers across every new account.
- Days to full access. How long from contract signing to receiving all required logins and assets? Under 7 days is good. Over 14 days is a process problem.
- First deliverable date. How many days between contract signing and the first tangible output? Aim for under 14 days on most engagements.
- Unsolicited check-in rate. Count how many times clients message to ask for a status update in the first 30 days. Zero is the goal. Each message is a process gap.
- 30-day retention. What percentage of clients are still active and enthusiastic at the 30-day mark? If any are expressing doubt this early, the onboarding did not land.
- 90-day referral rate. Clients who had a smooth onboarding refer others. Track how many referrals originate from accounts in their first 90 days.
Key takeaways
- Clients form their lasting impression of your agency in the first 30 days, not the proposal stage.
- Send the access checklist within 24 hours of signing, before the kickoff call, so the call can focus on strategy.
- A written project brief with out-of-scope items protects both sides when scope creep appears.
- Deliver something tangible every 10 days. Silence is interpreted as stalling.
- Template every message, every task list, every checklist. A duplicated template is a repeatable process.
- Track days to full access, first deliverable date, and unsolicited check-in rate to measure whether onboarding is actually working.
Common questions
What if the client is slow to send assets?
Document the request in writing, set a specific deadline (“please send by Friday so we can begin Monday”), and note in the project that a delay in asset delivery may push the project timeline. If assets are not received by the deadline, pause work on that deliverable and move to another. Send a brief note: “We’re holding [X] pending your brand files. We’ll resume as soon as they arrive.” This sets the right expectation without being adversarial.
How detailed should the project brief be?
One to two pages is sufficient for most engagements. It should cover: the client’s stated business goal, the deliverables and their formats, the timeline with milestone dates, the revision policy, the out-of-scope items, and the primary contact on each side. Longer is not better. A brief no one reads is not a brief.
Should every client get the same onboarding process?
The structure should be the same. The content adapts. A website project has different access requirements than a brand identity project. Maintain one master template and create project-type variants (website, branding, content, ads). The tasks differ; the timeline and communication rhythm stay consistent.
What if we inherit a client from another agency with messy history?
Run the same onboarding process anyway. Start with an audit: document what exists, what is missing, and what is broken. Deliver a brief written summary to the client. This sets a clean baseline and signals that you are organized, even if the prior agency was not. It also protects you legally if past work has issues.
How do I get the whole team to follow the process?
Put the template in the tool everyone already uses daily, not a separate wiki no one opens. Assign tasks from the template automatically when a new project is created. Make the process the path of least resistance, not an extra step. Review compliance quarterly and update the template when you find consistent gaps.
