TL;DR: Onboarding decides whether a client renews or churns inside 90 days. The 14-day, 18-step checklist below is the one I run at Eximius Studio. It covers contract sign-off through first deliverable, names owners on both sides, and has prevented every onboarding disaster I used to live through. Build it once, ship it for every new client.
Day 21 of a $14,000 project. I still don't have the client's logo files in vector format. I don't have access to their domain registrar. The "decision-maker" I've been emailing turns out to be the marketing manager, and the actual decision-maker (the CEO) just saw the design direction for the first time and hates it. Three weeks gone. Zero deliverables shipped. The client is starting to wonder if they made a mistake hiring us.
That was my month four. I'm Sammie Oku, founder of Eximius Studio, a web design and dev agency in Tyler, TX. After two of those experiences I built the 14-day checklist below. The next ten engagements onboarded without drama. This post is the agency client onboarding checklist I actually use, day by day, step by step.
If you haven't read the pillar yet, how to run a web design agency covers the seven systems this fits inside. Client onboarding is System 3. This post is the full playbook for that system.
Why 47% of clients churn in the first 90 days (and why it's an onboarding problem)
47% of clients leave their agency within the first 90 days (Agency Simplifier). 20 to 40% of clients churn in year one (almcorp / DesignRush research). When you read the post-mortems on those engagements, the pattern is almost always the same: the first two weeks were chaotic, the client lost confidence early, and the rest of the engagement was an uphill rebuild that usually didn't recover. Churn at this stage shows up later in the agency margin leak numbers, but the cause is upstream in onboarding.
Onboarding is not a welcome email. It is the first real proof of your agency's competence. The client signs a contract believing you can deliver. The two weeks after signing are when they decide whether they were right.
The cost of bad onboarding compounds. A messy first two weeks doesn't just delay the project. It teaches the client that you're not organized, which means every later request becomes a confidence check instead of a normal handoff. Every revision feels like rework. Every Change Order feels like a money grab. Trust is cheap to build in week one and expensive to rebuild in week eight.
Three things a real onboarding system has to do:
- Mechanize the handoff. Sales to delivery is the most common point of trust loss. Make it a process, not a hope.
- Front-load asset collection. Most project delays come from waiting on the client. Asset collection has to start on day one, not week three.
- Set the relationship temperature. Communication norms, decision authority, response time expectations: lock these in writing during onboarding, not when something goes wrong in week six.
The 14-day checklist below does all three.
Days 1 to 3: Contract signed, internal handoff, account creation
Day 1: Welcome packet and deposit invoice
Within 4 hours of the contract being signed, the client gets a welcome email that does five things: thanks them, names their single point of contact on your side (one person, with email and phone), links to their Project Home page, lists the 14-day calendar, and asks them to sign the deposit invoice. Don't bury the calendar in a PDF. Put it in the email body so they can't miss it.
The deposit invoice is non-negotiable. Standard terms: 40% on signing, 30% at design approval, 30% at launch. Work does not start until the deposit clears. This is not about cash flow paranoia. It's about commitment signal. A client who hesitates on the deposit is a client who will hesitate on everything else. (For retainer engagements, the deposit terms live inside the retainer agreement clauses most agencies skip; structure the first month as upfront with NET 5 on subsequent months.)
Day 2: Internal handoff meeting
If you have a team, sales hands off to delivery in a 30-minute internal meeting. Sales walks delivery through what was promised, what was discussed but not promised, and any red flags from the discovery process. If you're solo, this is still worth doing for yourself: write a one-page "engagement brief" that captures everything you remember from sales conversations before it leaks out of your head.
Day 3: Project Home page goes live
Build a single Notion page (or ClickUp, Basecamp, whatever) per client that becomes the source of truth for the engagement. The page needs: project timeline with milestone dates, named contacts on both sides, the contract, the scope, the asset request list, the meeting notes archive, and any access credentials. Share the link with the client and tell them this is where everything lives.
The Project Home page is the single highest-leverage artifact in onboarding. Build it once, copy it for every future client. The full 4-database structure that holds this page together lives in agency project management in Notion.
What this looks like in practice:
- A "Welcome" email template that takes 5 minutes to customize per client
- A deposit invoice with NET 5 terms
- A "Project Home" Notion template that duplicates per engagement
Days 4 to 7: Discovery questionnaire, access collection, kickoff scheduling
Day 4: Send the post-contract discovery questionnaire
Even if you ran a discovery process during sales, send a second, narrower questionnaire after signing. This one is operational, not strategic. It covers: who has final approval authority, who else needs to be in the loop, brand guidelines location, content ownership (who's writing copy), photography availability, third-party tool access, launch timing constraints, and known stakeholder opinions.
The strategic discovery questionnaire you sent during sales answered "what do you need." This one answers "how do we work together to build it."
Day 5: Send the asset request list
This is where most agency engagements lose two weeks. The asset request list is a specific, itemized checklist of what you need from the client and by when. Generic "send us your brand assets" doesn't work. Specific does.
A real asset request list:
- Logo files in vector format (.ai, .svg, or .eps)
- Brand guidelines or style guide (if available)
- Brand colors with hex codes
- Brand typography (font names and weights)
- Photography (folder of approved images, or confirmation we're using stock)
- Existing copy for each page in the scope (Google Doc, one doc per page)
- Domain registrar login or DNS access (Cloudflare, Namecheap, etc.)
- Current hosting credentials (if migrating)
- Google Analytics access
- Google Search Console access
- Email service provider access (Mailchimp, ConvertKit, etc.) if integrating
- CRM access (HubSpot, Salesforce, etc.) if integrating
- Stripe or payment processor access if e-commerce
- Social media handles for footer links
Each item has a due date attached. The full list goes on the Project Home page as a checklist the client can tick off. You see what they've completed without having to ask.
Day 6: Schedule the kickoff meeting
Send a calendar invite for the kickoff (target: day 8 to 10) with the agenda attached. Don't show up to a kickoff without sending the agenda 24 hours ahead. Clients who see the agenda come prepared. Clients who don't, ramble.
Day 7: Internal preparation
Read everything the client has sent. Review the contract. Pull together a one-page kickoff brief that you'll walk through at the meeting. If you have a team, share it internally so everyone going into the kickoff knows the project before the client speaks.
Days 8 to 10: Kickoff meeting and roles
The kickoff is the single highest-leverage hour of the entire engagement. Get it right, get a project. Get it wrong, spend the next eight weeks fighting confusion. My kickoff meeting agenda is 50 minutes structured as:
- 0 to 10 min: Reintroductions and goal recap. Everyone on the call says their name and role. You recap the project goals as you understand them. The client confirms or corrects.
- 10 to 25 min: Scope walkthrough. Read the scope out loud. Yes, out loud. Confirm in/out for every deliverable. Confirm out-of-scope items so nobody is surprised in week six.
- 25 to 40 min: Roles, communication, decision authority. Who decides what on the client side? Who do we talk to for design decisions vs. technical decisions vs. content decisions? What's the communication channel (Slack, email, project tool)? What's the response time expectation on both sides?
- 40 to 55 min: Timeline, milestones, dependencies. Walk through the calendar. Confirm dependency dates. Flag risks.
- 55 to 60 min: Single next action and sign-off. What's the one thing each party owes the other by tomorrow?
Document the kickoff in a written summary you send within 4 hours of the meeting ending. The summary becomes the source of truth on what was agreed. If the client doesn't object to the summary, it stands.
The four phrases that prevent half of future disputes:
- "To confirm, this is in scope: [list]. This is out of scope: [list]."
- "You'll have feedback for us within [X] business days of every deliverable."
- "All requests outside the original scope go through a Change Order process."
- "Final design approval comes from [single named person], who has authority to sign off on behalf of the company."
That last one is the most underused phrase in agency onboarding. Most projects have a "decision committee" that nobody named explicitly. Force the client to name one person. If the CEO will be the actual gatekeeper, the CEO needs to be the named approver. The marketing manager being the "primary contact" while the CEO secretly has veto is the most common onboarding failure mode in agency history.
Days 11 to 14: First deliverable, communication cadence locked in
Day 11: First deliverable in client hands
Even if it's just a sitemap, wireframes, or a strategy doc, ship something tangible to the client by day 11. The point is not the deliverable itself. The point is to demonstrate that the engagement is moving and you're not going to disappear after the deposit cleared.
Pick a deliverable that's high signal, low effort. Sitemap. Information architecture diagram. Mood board. Brand audit. Anything that takes you 2 to 4 hours and gives the client something to react to. Reactions are how you calibrate before you've spent real design hours.
Day 12: Weekly cadence locked in
Set the weekly rhythm and write it into the Project Home page. Mine for a typical $15K to $30K build:
- Monday morning: Status update sent from us to client (3-bullet email or Loom video)
- Wednesday: 30-minute check-in call if there are open decisions
- Friday: End-of-week summary with what was shipped, what's coming next
That's it. No daily standups with the client. No constant Slack pings. A predictable rhythm builds more trust than constant availability.
Day 13: Define what "done" means
Walk through the QA process and the launch criteria explicitly. What does "approved" mean at each phase? What's the testing protocol? What's the rollback plan if something breaks at launch?
This sounds basic. It is. Most agencies skip it. Then in week 9 the client says "but I thought you were going to test on Internet Explorer," and you eat 8 hours of regression testing because the definition was never written down.
Day 14: Send the 14-day recap
A short email that recaps what was accomplished in the first two weeks: contract signed, deposit cleared, kickoff completed, assets received (or what's still outstanding), first deliverable shipped, weekly rhythm established. End with what's next.
That email does two things. It marks the end of onboarding so both sides know "we're now in delivery mode." And it documents that you ran a structured onboarding, which becomes evidence later if the relationship goes sideways.
The 9 questions every operational discovery questionnaire needs
Some of these will have been answered during sales. Confirm them in writing anyway. Memory is unreliable.
- Who has final approval authority on design decisions? Name one person.
- Who has final approval authority on technical decisions? Often a different person.
- Who has final approval authority on content? Usually the marketing or content lead.
- Who else needs to be in the loop but doesn't have approval authority? Identify so you're not blindsided.
- What's the launch date constraint, if any? Hard date vs. flexible.
- What's the budget constraint on the project beyond what's already in the contract? Reserves for stretch.
- What's the typical response time on your side? Sets expectation both ways.
- What's the preferred communication channel for daily work? Email, Slack, project tool.
- What's the worst-case scenario you want to avoid? This is the most underused question and the highest signal. Clients will tell you what they're afraid of if you ask. "We don't want to be surprised by extra fees" tells you to overcommunicate on scope. "We don't want it to feel like every other agency's website" tells you to push harder on design distinctiveness.
Red flags during onboarding that signal a problem client
Some clients reveal themselves in the first 14 days. If you see three or more of these, you have a problem client and you should adjust your project management accordingly (or, if it's bad enough, refund and walk):
- Missed asset deadlines without communication. Twice or more in the first two weeks. Predicts that they'll miss feedback deadlines in delivery.
- Decision authority keeps shifting. First the marketing manager, then the CEO, then "we need to loop in the board." Predicts indecision and rework.
- Pushback on the deposit terms after signing. Predicts payment issues later in the engagement.
- Multiple stakeholders weighing in unsolicited. The CEO's spouse "had some thoughts on the colors." Predicts design-by-committee.
- The kickoff meeting got rescheduled twice. Predicts that you're not a priority for them.
- "Quick question" emails on day two that are actually new scope. Predicts that scope creep is already starting.
- Insistence on changing communication channels mid-onboarding. "Actually, can we use Slack instead?" then "actually, can we use Teams?" Predicts that nothing will land in one place.
None of these alone is fatal. Three or more, in the first 14 days, is a signal worth taking seriously. The fix is usually to tighten your scope-change protocol (how to stop scope creep) and add a buffer to your timeline. Sometimes the fix is to politely terminate. Onboarding is when termination is cheapest. The full set of agency SOPs covers the offboarding protocol if that's where this is heading.
Building this from scratch is slow. The welcome email templates, the asset request list, the kickoff agenda, the operational discovery questionnaire, and the 14-day recap email are all inside Agency Operations OS. Deploys in an afternoon, $79. Link at the end.
What goes wrong when you skip onboarding
I've watched this movie three times in my own studio and twenty times across other agencies I've consulted with. The pattern is identical.
You skip the asset request list because the client "seems organized." Week three, you're still chasing logo files. The project is now late through no fault of yours, but the client experiences it as your delay.
You skip the named decision-maker question because the client said "I'm the main contact, just go through me." Week six, the CEO sees the design for the first time and rejects half of it. You rebuild. Margin tanks.
You skip the kickoff because you've worked with similar clients before and "it's basically the same thing." Week four, the client wants daily standups and a Slack channel and Loom videos every other day. None of that was in scope. You absorb it anyway because it's "just communication."
You skip the weekly rhythm because it feels rigid. Week five, the client is in your inbox every other day asking for updates. You spend 3 hours a week on unbilled communication.
Every one of those failures was preventable in week one. The 14-day checklist is the prevention.
Frequently asked questions
How long should agency client onboarding take?
Target 14 days from contract signing to first deliverable. Shorter than that and you're skipping critical setup. Longer than that and the client loses momentum. The 14-day window is enough to collect assets, run a proper kickoff, set communication norms, and ship something tangible. Larger enterprise engagements may extend to 21 days. Sub-$5,000 projects can compress to 7. The structure stays the same, only the pace changes.
What should be in an agency welcome packet?
A welcome packet has six things: a thank-you message naming the client by name, a single point of contact with phone and email, a link to the Project Home page, the 14-day calendar with milestones, the deposit invoice, and a "what we need from you in week one" summary. Keep it under one page. The goal is clarity, not impressive design. A clean Google Doc or Notion page works better than a heavy PDF most clients won't open.
Should I require a deposit before onboarding starts?
Yes. Standard terms: 40% deposit on contract signing, 30% at design approval, 30% at launch. Deposit must clear before work begins. This isn't paranoia, it's commitment signal. Clients who hesitate on a deposit hesitate on everything else. For retainer engagements, charge the first month upfront, with NET 5 payment terms on subsequent months. Late deposit on month one predicts late payment every month.
What's the difference between sales discovery and onboarding discovery?
Sales discovery answers "what do you need built." Onboarding discovery answers "how do we work together to build it." The first is strategic: goals, target audience, scope, success metrics. The second is operational: decision authority, communication channels, response time expectations, asset availability, stakeholder map. Skip operational discovery and you'll waste two weeks on logistics issues that should have been resolved in week one.
How do you handle a client who doesn't respond during onboarding?
Send a structured nudge on day 7 if they've missed deadlines: "Hi [name], wanted to flag that we're still waiting on [specific items] to keep the project on schedule. Could we have these by [date] to keep the launch date intact? If timing has shifted on your end, let me know and we'll adjust the timeline together." If no response by day 10, send a second nudge. If no response by day 14, pause the engagement in writing. Don't keep working blind. A client who can't engage in week two won't engage in week six.
The shortcut: Agency Operations OS
Building the welcome email, the operational discovery, the asset request list, the kickoff agenda, the 14-day recap, and the Project Home template from scratch takes a full weekend. The pieces themselves aren't complicated. The consistency is what kills people.
Agency Operations OS is the Notion template I use to run Eximius Studio. It includes:
- 7 core databases: Leads, Deals, Projects (with a built-in 14-day onboarding checklist per project), Retainers, Change Orders, Financials, and AR Aging.
- 5 dashboards including an Onboarding Health view that shows every active client's 14-day progress.
- 15 SOPs including the full onboarding sequence, the kickoff agenda, the asset request protocol, and the operational discovery process from this post.
- 5 bonus docs: Master Services Agreement, Retainer Agreement, Project Proposal template, Discovery Call script (sales + operational versions), and the 47-item Pre-Launch QA Checklist.
One template, deploys in an afternoon, $79.
The 18 steps above are the agency client onboarding checklist that turns the first 14 days from chaos into a process. Build it once, ship it for every future client, watch your 90-day churn drop. The next contract you sign should hit this sequence on day one.
For the bigger picture, the pillar guide on running a web design agency shows where onboarding fits into the full operating model, and the discovery questionnaire covers what to ask before you even get to the contract.
