The agency client onboarding checklist (the 30-day plan that actually ships)

TL;DR

A real agency client onboarding is 30 calendar days from kickoff to first-month-review, structured into four weeks: Week 1 = access + brief + audit (founder + senior on, junior shadows); Week 2 = tracking baseline + brand intake (specialists own, senior reviews); Week 3 = campaign foundations + reporting setup (specialists execute, account manager presents); Week 4 = launch + handoff + first measurement window (full team coordinates, account manager runs the review). Most onboardings drift to 6-8 weeks because three things are under-specified: who on the client side approves what, what "done" looks like at each milestone, and how tracking infrastructure gets verified. The checklist below names every artifact, every owner, and every approval gate per week. Steal it, adapt it, sign it as part of every new client SOW.

---

There's a quiet pattern in struggling agencies: every new client engagement starts with the same energy — kickoff call full of optimism, week 1 ships fast, momentum looks great. By week 3, it's stalled. By week 5, the client is asking "what's actually been delivered" and the agency is mid-internal-finger-pointing about whose fault it is the GTM container hasn't been touched yet.

The fix isn't more discipline. It's the same fix that works for almost any agency operations problem: a checklist with named owners, named artifacts, and explicit approval gates per milestone. Most agency owners know they should have one. Most don't, because writing it the first time is genuinely 8-12 hours of senior thinking, and there's always a more urgent thing.

Here's the version we use. Steal what fits. The four-week structure assumes a "standard" digital marketing engagement (some mix of paid media, SEO, tracking infrastructure, light creative). For pure-product engagements (e.g. social-only, web-design-only) you'd compress to 2 weeks; for enterprise engagements with 3-month discovery phases you'd extend to 8.

Week 1: access + brief + audit

Owners: Senior account lead + founder/principal (for executive alignment). Junior shadows for context.

Goal: by end of week 1, you have everything you need to do the first month's work without going back to the client for inputs. If you don't, week 2 stalls.

Day 1 — Kickoff call (60-90 min, async-prep'd)

• Pre-call: client filled out the intake form (services, goals, timeline, prior agency context, KPI definitions, internal-stakeholder list).
• On-call: agency walks through the 30-day plan, identifies named decision-makers on the client side per workstream, sets weekly cadence + meeting times, captures any topic the intake form missed.
• Output: signed SOW (if not already), shared kickoff notes, calendar invites for the next 3 weekly check-ins.

Day 2-3 — Access provisioning

The single biggest week-1 failure mode. Every access item below should be requested on day 1, not day 5. Most clients take 3-5 days to fully provision; if you wait until day 5 to ask, you're week-2 blocked.

• Ad platforms: Google Ads (MCC link request), Meta Business Manager (admin invite to your agency BM), TikTok Ads (admin invite), LinkedIn Campaign Manager, Microsoft Advertising. Track which ones you actually need per the SOW; don't request access to platforms you're not running.
• Analytics: GA4 admin access, Search Console verified-owner access, Looker Studio view access on existing dashboards.
• Tag management: GTM container admin access (web + server-side if applicable).
• Email + automation: Klaviyo, Mailchimp, HubSpot, etc. — only if in scope.
• Commerce: Shopify staff/collaborator access, Klaviyo source attribution.
• CMS / dev: WordPress admin or staging access, Webflow Editor access, GitHub repo access if dev work in scope.
• Cloud / hosting: Vercel team, Cloudflare zone access, AWS IAM — only if relevant.
• Internal client comms: invite your senior team to the client's Slack / Teams workspace if cross-team chat is in scope. (Beware data-privacy implications.)

Day 3-5 — Brand + product intake

• Brand guidelines (PDF + Figma if available)
• Logo files (SVG + PNG variants)
• Brand fonts (file or font-service access)
• Product catalog (Shopify product feed if e-comm, top 5-10 SKUs with descriptions if not)
• Existing creative library (last 30-90 days of ad creative, organic social, email designs)
• Customer-segment definitions (who is the buyer, what differentiates them, what's the typical purchase journey)

Day 4-5 — Initial audit pass

While access provisioning is in flight, the audit-eligible items get hit:

• Current GA4 setup audit: events configured, custom dimensions, audiences, conversion events vs key events, integration list.
• Current GTM container audit: tags, triggers, variables, version history, dead tags.
• Current ad-account audit: campaigns running, conversion actions configured, audience lists, customer-list uploads, tCPA/tROAS settings, recent quality-score / dataset-health metrics.
• Current site analytics (Search Console + indexed page count + Core Web Vitals + technical SEO baseline).

Approval gate (end of week 1): kickoff notes signed, all access provisioned (flagged blockers if not), audit doc draft circulated to the client.

Week 2: tracking baseline + brand-aware deliverables

Owners: Specialists per channel (PPC, SEO, social) execute; senior reviews; account manager coordinates.

Goal: by end of week 2, the tracking infrastructure map is documented + verified, and the team has all the brand-aware assets they need to start producing creative + content.

Day 6-8 — Tracking infrastructure map

This is the most-skipped step in agency onboarding and the one that costs the most when skipped. Per the hidden cost of broken tracking, every broken pixel + missing conversion event = real dollars on the table.

The minimum: document each of the 21 things every agency should track per client, verify each is firing correctly (pixel firing in browser dev tools, conversion event arriving in GA4 DebugView, dataset showing healthy quality score in Meta), and flag any breakage. The output is a typed graph of every node + a punchlist of what's broken or missing.

This week is when most agencies discover that the previous agency's "tracking is fine" claim is meaningfully wrong. Two-thirds of new client engagements find at least one broken pixel + at least one missing conversion event in week 2. Document it, surface it to the client, fix it before any new media spend goes through. (Otherwise: you're optimizing campaigns against bad data.)

Day 7-9 — Reporting setup

• Build the client's reporting dashboard (Looker Studio is the default; brand it lightly for client visibility). Pull GA4, ad platforms, Search Console.
• Define the KPIs: top-of-funnel (impressions, sessions), mid-funnel (engagement, form completions), bottom-funnel (conversions, revenue). One number per layer is enough; more than three KPIs and the dashboard becomes noise.
• Schedule the weekly + monthly cadences. Most clients want a weekly Slack/email digest + a monthly slide deck. The senior account manager owns the deck; the dashboard auto-pulls.

Day 8-10 — Brand-aware deliverables foundation

• Creative templates: for each ad platform in scope, build 2-3 templated ad units (Figma frames + the underlying components). New creative will iterate against these templates rather than starting from scratch every time.
• Content templates: if SEO/content is in scope, build the post template (header structure, image placement, internal-linking convention, schema markup).
• Email templates: if email is in scope, build 2 templates (announcement + nurture).

Approval gate (end of week 2): tracking map shared with the client + the punchlist signed off, reporting dashboard linked to the client, creative + content templates approved.

Week 3: campaign foundations + first deliverables

Owners: Specialists fully own; senior reviews exceptions; account manager presents externally.

Goal: by end of week 3, the first round of real client-facing deliverables has shipped — campaigns built (not yet live, but production-ready), content drafted, designs in review.

Day 11-13 — Campaign architecture

• PPC: account structure built per platform (campaigns + ad groups + audiences + assets). Bidding strategy chosen per campaign. Budget allocation across campaigns proposed. Conversion actions wired correctly (verified via conversion-tracking verification).
• SEO: quarterly punchlist drafted (15-30 items prioritized by traffic potential vs effort). Top 3 items moved into the week-3 production queue.
• Social: content calendar for the first 4 weeks, brand-aware. Approval workflow proposed.
• CRO: if in scope, first 2-3 hypothesis briefs drafted. Test platform configured.
• Web design: if in scope, project arc planned + sitemap proposed.

Day 13-15 — First deliverables shipped

• PPC: ads built into the platform (paused). Click-through QA on each ad. Landing-page check on each destination URL.
• SEO: first 1-2 content drafts written. Technical fixes shipped to staging if applicable.
• Social: first week's content drafted + designed.
• Email: first nurture campaign drafted (not sent).
• Reporting: first week's report ships, even if there's no media spend yet — establishes the cadence + trains the client to expect Mondays-with-the-deck.

Approval gate (end of week 3): all production-ready deliverables presented to the client; client signs off on what launches in week 4.

Week 4: launch + handoff + first measurement window

Owners: Full team coordinates; account manager runs the launch + the review.

Goal: ship live, measure the first week, run the 30-day review.

Day 16-19 — Launch

• PPC: campaigns activate. Real-time monitoring for the first 24 hours (anomaly detection: did spend pace correctly, did conversions fire, did the audience match expectations).
• SEO: first content batch publishes. Technical fixes deploy to production.
• Social: content goes live per the calendar. Community management goes hot.
• Email: first send (or schedule).
• Web design: if in scope, milestone-based ongoing.

Day 20-26 — First measurement window

• Daily monitoring per channel. Anomalies flagged + addressed within 24 hours.
• Weekly check-in with the client at the agreed cadence.
• Slack/email digest end of each day (high-spend clients) or end of each week (everyone else).

Day 27-30 — 30-day review

• Build the 30-day deck. What launched, what's working, what's not, what's queued for month 2.
• Recommendations for month 2 (which campaigns to scale, which to kill, which experiments to run).
• Reset expectations on what's measurable in 30 days vs 60 vs 90 (SEO impact rarely shows in 30; PPC is mostly visible by 30; social is visible immediately; CRO needs at least 60).
• 30-day review meeting with the client. Decisions made on month-2 plan. Updated SOW signed if scope shifted.

Final gate: 30-day review delivered, month-2 plan signed.

Three cross-cutting things that kill most onboardings

These show up in every department and are usually invisible until they're already breaking the engagement.

1. Unclear client-side decision-makers

The single biggest cause of week-3 drift. Symptoms: "I have to check with marketing" or "let me ask my CEO" or "I'm waiting on legal" — said for the third time in a row.

The fix: in the week-1 kickoff, capture named decision-makers per workstream. Not just "marketing approves" — "Sarah at marketing approves creative; Tom at CFO approves spend changes above $5K; Priya is the technical lead for tracking-infrastructure changes." Names + emails + approval thresholds. If the client can't provide named decision-makers in week 1, that's a flag worth raising before signing anything ambitious.

2. Mismatched expectations on cadence

Some clients expect daily Slack updates; some expect monthly decks. Some want every change run by them; some want full autonomy below a $X spend threshold. Mismatched expectations show up around week 4 ("I had no idea you'd already changed the bidding strategy on Campaign 7") and erode trust irreversibly.

The fix: explicit cadence agreement in week 1. What's daily, what's weekly, what's monthly. What's "we'll just do it and tell you Monday" vs "we'll get your approval first." Document it in the kickoff notes. If the client tries to change the cadence after the fact, refer back to the kickoff.

3. Tracking infrastructure under-allocated

The week-2 tracking-infrastructure step gets compressed because it doesn't feel as visible as creative or campaigns. Then week 4 launches with a broken pixel + a misfiring conversion event + an audience that hasn't synced. Three weeks later you discover the campaigns have been spending against bad data.

The fix: the tracking-infrastructure work is a hard week-2 dependency for everything else. Don't compress it. The tracking infrastructure map per client is the artifact that holds the state — once it exists, week-2 onboarding for the next client is 4 hours instead of 12.

What good onboarding looks like (and what most agencies have)

A 30-day onboarding that hits every gate on time, shipped using a documented checklist with named owners, costs you about 50-60 senior hours total. Without the checklist, the same engagement costs 90-120 senior hours and ships 2-3 weeks late.

The math: investing 8-12 hours of senior thinking into the checklist once + maintaining it quarterly costs ~15 hours per year. The savings: 30-60 senior hours per onboarding × 8-15 onboardings per year = 240-900 hours of recovered senior capacity. The ROI is absurd; the reason most agencies don't do it is the urgency tax — senior hours are always urgent enough that "step back and write the checklist" loses to "ship this week's deliverables."

Block 8 hours, write your version, ship it.

The Phloz angle

Phloz models per-client onboarding as a structured workflow: the tracking infrastructure map seeds in week 2 (each of the 21 nodes can be added empty + filled in as access provisions through), the client portal seeds in week 1 (so the client has one place to see status across departments), tasks live with department + client tags so the per-week checklist is filterable per role.

Crucially, Phloz doesn't impose a specific 30-day plan — every agency's plan is a little different, and the checklist above is meant to be adapted. What Phloz provides is the artifact layer underneath any plan: the typed objects (clients, tasks, tracking nodes, departments) so whichever checklist you run, the state lives somewhere durable.

Steal this checklist

The version above is the one we use, simplified for shareability. The real version per agency would name specific people in specific roles, specific tools the agency standardizes on, and specific deliverable templates per client tier. Adapt accordingly.

If your agency doesn't have a 30-day onboarding checklist documented, the highest-leverage thing you can do this quarter is write yours. Whatever shape it takes, the act of writing it forces the questions ("who actually owns the GTM audit?" "what's our SLA on access provisioning?") that drive the operational discipline that protects margin (see scale a marketing agency without losing margin).

Try Phloz free to see the structured per-client workflow + tracking map in action, or see pricing for the full breakdown.