How to Onboard a New Client in 5 Days: The Creative Agency Checklist
86% of clients are more likely to stay loyal to agencies that invest in onboarding. The first five days set the expectation for every working week that follows. Here's the day-by-day checklist that turns contract-signed into production-ready.
- Why the handoff from sales to delivery is the most dangerous moment in a new client relationship
- The five-day sequence that covers every essential onboarding step without overwhelming the client
- The one deliverable that closes the onboarding phase and signals the start of real production
The First Five Days Are the Whole Relationship in Miniature
A Wyzowl study found that 86% of clients stay loyal to companies that invest in onboarding. Precursive identified poor onboarding as the third most common reason for client churn across B2B service businesses. The data is consistent: the onboarding period is when clients form the operating assumption about how organized, responsive, and competent the agency is — and that assumption persists long after onboarding ends.
The failure pattern is predictable. Teams that don't run onboarding from a checklist tend to improvise. The kickoff call happens before the team is briefed. The scope of work isn't finalized before production questions arise. The client is asked to repeat information they gave during the sales process. Access requests trickle in over two weeks because nobody tracked them as tasks. By week three, the client is questioning whether they made the right decision before the agency has produced a single deliverable.
A five-day onboarding checklist doesn't prevent complexity — it structures the response to it. Every client relationship starts with some version of the same 25 tasks. Building a repeatable system for those tasks is what turns a chaotic first week into a professional first impression.
Day 1: Internal Alignment Before the Client Sees Anything
The most dangerous moment in a new client relationship is the handoff from the person who sold the work to the person who delivers it. A 15-minute internal handoff call between sales and the delivery team should happen before the welcome email goes out. Cover: what was promised, what the client cares about most, any commitments made during the sales process that aren't in the signed scope, and any red flags from the sales conversations that the delivery team needs to know about.
Day 1 checklist (internal):
- Sales-to-delivery handoff call completed: scope confirmed, commitments noted, client context transferred
- Contract countersigned and filed; first invoice sent; billing contact confirmed
- Internal team briefed: creative lead, account manager, and project manager assigned
- Project workspace created (project management tool, shared folder structure, communication channel)
- Access tracker created: a live document listing every credential, account, and asset the agency needs, with owner, status, and required-by date
The access tracker is not optional. Collecting access is the step agencies most often underestimate — it's the step most likely to create a one-to-two-week delay in the first production cycle. Building the tracker on Day 1, assigning someone to chase it, and defining the date by which each access item is needed prevents the delay from happening silently.
Day 1 checklist (client-facing):
- Welcome email sent within 24 hours of contract signing: warm tone, named point of contact on each side, preview of what happens next
- Onboarding questionnaire sent (pre-filled with information from the sales process — never ask the client to repeat what they already told you)
- Kickoff meeting scheduled within 72 hours
Day 2: Kickoff Meeting
The kickoff meeting is 30 to 45 minutes, has a set agenda, and ends with the client knowing three things: what's happening this week, who to contact for what, and when the first deliverable will be ready.
The kickoff agenda covers: team introductions (60 seconds per person, role-specific), confirmation of scope and deliverables (walk through the signed scope, confirm mutual understanding, flag any ambiguities), communication protocol (primary channel, expected response times, escalation path), access status (review the access tracker, set dates for outstanding items), and first-30-days plan (what the client will see and when, with specific dates).
The most valuable 10 minutes of the kickoff is the scope walkthrough. Agencies that don't do this in the first week discover misaligned expectations in week four. The signed document defines the legal scope; the kickoff conversation aligns the operational understanding of what that scope means in practice.
After the kickoff: send a written summary within 24 hours. The summary includes every decision made, every open item with a named owner and a date, and confirmation of the communication protocol. This document becomes the operating agreement for the first 30 days.
Day 3: Asset and Access Collection
Day 3 is owned by the project manager. The goal is to have every access item and brand asset required for production collected, verified, and organized before Day 5.
Access collection checklist:
- Marketing platforms: analytics, advertising accounts, CMS, social profiles (request admin-level access for each relevant platform)
- Brand assets: logos in all variants (SVG, PNG, full color, mono, reversed), approved color codes, typography files, brand guidelines document
- Existing creative: approved campaign assets, previous deliverables, any work the agency should reference or build from
- Technical: any platform-specific credentials, API keys, or integration access required for the engagement
Never ask clients to email passwords. Use a shared credential manager or, for access grants, platform-specific invitation flows. Building the access collection process around platform invitation workflows (Meta Business Manager partner access, Google Analytics user grants, ad account MCC connections) eliminates the security risk of password sharing and creates a cleaner audit trail.
The access tracker built on Day 1 should be updated in real-time on Day 3. Any item not received by Day 3 gets a follow-up sent immediately with a specific "we need this by [date] to start production on [deliverable]" message. Vague access requests don't move. Specific requests with production consequences do.
Day 4: Internal Production Setup
Day 4 completes the infrastructure setup so production can begin on Day 5 with everything in place. This is an internal day — no client-facing deliverables.
Day 4 checklist:
- Project workspace fully configured: all access installed, brand assets uploaded to the shared library, scope of work imported into the project management tool with milestone dates
- First brief drafted by the account manager and reviewed by the creative lead: the first deliverable should be briefed and ready for production by end of Day 4
- Reporting template prepared: the first status report should go to the client by Day 7, and the template should be ready before production begins
- RACI updated: confirm who approves each deliverable type on the client side (the approval authority mapping that prevents revision loops later)
The RACI update on Day 4 is the most commonly skipped step — and the one that creates the most problems in weeks 2 through 4. "Who approves the copy?" and "whose feedback is mandatory vs. advisory?" are questions with one right answer per deliverable type. Getting them answered on Day 4, before the first revision cycle, is what prevents them from becoming conflict points during production.
Day 5: First Deliverable and Rhythm Establishment
Day 5 is when the relationship shifts from onboarding to delivery. The goal is to have something tangible to show the client — a draft, a strategy document, an initial audit — that confirms the agency is already working and knows what it's doing.
Delivering something inside the first 10 days matters more than it might seem. It's the first evidence the client gets that signing was a good decision. For a creative production retainer, this typically means the first brief moving through production — the first hero asset in review, the first campaign concept for feedback, the first adaptation delivered for approval.
Day 5 also establishes the ongoing communication rhythm. Recurring check-in scheduled: weekly for the first month, then adjusted based on the client's preference. First status report due date confirmed. Feedback loop question asked: "Is the communication cadence working for your team? Too much? Too little?" This question, asked explicitly in the first week, sets a precedent for direct communication about the working relationship that prevents the build-up of unaddressed friction later.
The onboarding phase closes when the engagement has a normal rhythm: the first deliverable has shipped, the reporting cadence is running, and both sides know where to look for status. That transition — from onboarding mode to delivery mode — is what the five-day checklist is designed to create.
FAQ
What's the most common reason the five-day onboarding timeline slips? Access collection. Clients don't prioritize access grants because they don't understand the production dependency. Building the production dependency explicitly into access requests — "we need Google Analytics access by Thursday to complete the audit that's on the Day 7 deliverable" — creates urgency that abstract requests don't. Track every access item on the Day 1 tracker and follow up with specific production consequences.
Should the five-day checklist be adjusted for larger or more complex clients? Yes, in duration and not in sequence. Complex clients may need 10 to 14 days for the same tasks — more stakeholders, more access items, more complex scope. The sequence (internal alignment before client contact, access collection before production setup, first deliverable before month one closes) remains the same regardless of scale.
How do you handle a client who is slow to return the onboarding questionnaire? Pre-fill everything you already know from the sales process. The questionnaire should only ask for what's genuinely new. When a client sees that most questions are already answered and they're being asked to confirm rather than answer from scratch, response rates and response quality both improve significantly.
What should the first status report include for a client in their first week? The format is simple: what we did this week (with specific deliverable references), what's happening next week (with specific dates), and what we need from you (specific requests with specific dates). The first status report is a trust-building document — it proves the agency is organized and thinking ahead. Keep it to one page.
How do you prevent the onboarding handoff problem, where sales promises things delivery can't deliver? The Day 1 handoff call is the structural solution. Make it mandatory, not optional. Give sales a handoff template with required fields: scope confirmed, commitments noted, pricing discussed, client expectations about timeline and communication frequency. If sales made a commitment the delivery team can't fulfill, the handoff call is where that gets resolved — before the client relationship starts, not during it.
