DEV Community: Lisa Sakura

How Small Agencies Can Run AI-Native Client Onboarding (with 5 Real Prompts)

Lisa Sakura — Mon, 04 May 2026 07:47:44 +0000

Published by Agency Onboarding OS | agencyonboardingos.com

Most agency onboarding chaos isn't a people problem. It's a system problem.

Every time a new client signs, someone rebuilds the same folder structure, writes the same "can you send us access to…?" email, and runs the same kickoff call without a template. Then the client replies slowly, forgets to grant tool access, and week one is already behind before the first deliverable touches a doc.

We've seen this pattern in marketing agencies, SEO shops, web studios, and freelance consultants. Same five problems, every time:

Access collection drags into week two
Scope is fuzzier after the kickoff than before
The onboarding checklist lives in someone's head
Clients don't know what to expect or when
Nothing from this client's setup carries forward to the next

Here's how you can fix all five with a structured system and a handful of LLM prompts.

The 5-Phase SOP

Before AI makes anything smarter, you need a base operating procedure. Here's the structure we use:

Phase 1 — Pre-Kickoff (Days 0–3)

Confirm contract and deposit
Send intake form (27 questions across 6 categories: business context, brand, audience, tools, success metrics, communication preferences)
Set up client folder, project board, Slack/Teams channel
Draft kickoff agenda from intake responses

Phase 2 — Kickoff (Day of meeting)

Run the kickoff call with pre-built agenda
Record scope decisions explicitly
Set up access request tracker

Phase 3 — Access Collection (Days 1–5 post-kickoff)

Send structured access request email
Run 3-day and 7-day follow-ups if no response
Log received vs. outstanding in the tracker

Phase 4 — Delivery Setup (Days 3–7)

Brief delivery team from intake summary
Set 30-day timeline milestones
Share client-facing status update template

Phase 5 — Handover (Day 30)

Offboarding checklist
Archive deliverables
Request testimonial

That's the skeleton. Now here's where LLMs make each step faster and less error-prone.

5 Prompts That Save ~2 Hours Per Client

Prompt 1 — Kickoff Brief Generator

When to use: After the client fills your intake form, before the kickoff call.

You are an agency project manager preparing for a client kickoff call.

Here is the intake form the client filled in:
[paste intake form responses]

Write a kickoff meeting brief that includes:
1. A 3-sentence summary of what the client is trying to achieve
2. The 3 most important questions to get answered on the call
3. The scope risks most likely based on what they wrote (be specific)
4. A suggested meeting agenda (max 45 minutes)

Write it in plain language. Be direct. Flag anything unclear.

Output: A pre-meeting brief your team can scan in 5 minutes instead of rereading 10 intake fields.

Prompt 2 — Access Request Email Generator

When to use: At the start of Phase 3, when you need to collect 8–15 tool accesses.

You are writing a professional but warm email to a new client asking for tool access.

The client is: [client name]
The project is: [project type]
We need access to: [list tools, e.g. GA4, Search Console, CMS, Figma, Slack, social channels]

Write an email that:
- Opens with one warm sentence (no corporate boilerplate)
- Lists each tool as a numbered item with a clear action per item
- Ends with a specific reply deadline (3 business days)
- Feels like it's from a human who does this regularly, not a process robot

Max 180 words.

Output: An access email that gets replies, not polite silence.

Prompt 3 — Missing-Input Detector

When to use: After the intake form comes back, before kickoff.

You are reviewing a client intake form before a kickoff call.

Here is the intake form:
[paste intake form]

Identify every field that is:
- Blank or left as "TBD"
- Vague enough that you couldn't make a concrete decision from it
- Contradictory with another answer

For each gap, write one follow-up question to ask on the kickoff call or via email.
Be specific. Use the client's own words where possible.

Output: A pre-call checklist of the exact questions that will prevent scope drift later.

Prompt 4 — Status Update Draft

When to use: Whenever you need to send a weekly/biweekly client update.

You are writing a client status update email for a project in week [X].

Project context: [paste kickoff brief or project summary]
Completed this period: [list 3–5 bullet points]
In progress: [list what's underway]
Blocked / waiting on client: [list any blockers, if any]
Next steps: [what happens next]

Write an email that:
- Opens with the headline: what the client most needs to know right now
- Uses bullets, not paragraphs
- Explicitly calls out anything the client needs to act on
- Ends with a specific next touchpoint

Max 200 words. Don't pad.

Output: A weekly update that clients actually read, because it respects their time.

Prompt 5 — Escalation Draft

When to use: When scope is expanding, access is 10+ days overdue, or a deliverable is at risk.

You are a project manager writing a professional but firm escalation message to a client.

Situation: [describe what happened — late access, scope change request, missed deadline, etc.]
Impact: [what does this delay or change actually affect?]
What you need: [one clear, specific ask]
Deadline: [when you need it by]

Write a message that:
- States the situation plainly in one sentence
- Explains the impact clearly (no drama, just facts)
- Makes one clear ask with a deadline
- Maintains a professional, collaborative tone
- Is under 150 words

Don't soften the ask to the point of ambiguity.

Output: An escalation that gets read and gets a response, without burning the relationship.

What This Looks Like in Practice

A 10-person marketing agency using this system runs onboarding like this:

Client signs → automated intake form sent (30-second trigger)
Intake responses come back → paste into Prompt 1 → kickoff brief generated in 90 seconds
Kickoff call runs from the brief → scope decisions documented live
Prompt 2 generates access email → sent same day
3-day follow-up via Prompt 2 variant if no response
Prompt 3 flags any gaps → follow-up questions sent before day 5
Prompt 4 generates weekly updates → 10 minutes to review and send

That's 5–8 hours of chaotic, from-scratch work compressed into 45 minutes of structured execution.

No enterprise software. Works in ChatGPT, Claude, or any other LLM. Drops into whatever project management tool you already use.

The Full System

This article covers the AI-native upgrade path. The full Agency Onboarding OS includes:

30+ templates and docs (intake form, SOPs, checklists, access tracker, status templates, offboarding)
6 automation recipes for Zapier and Make
4 agency-specific variants (marketing, SEO, web design, freelance)
The 5 prompts above + full implementation guide

Free resources (no email required):

Full OS: agencyonboardingos.com — $49 one-time, founding batch pricing.

Built by Agency Onboarding OS. Questions → lisa@agencyonboardingos.com

The 7 Places Agency Client Onboarding Breaks (And How to Fix Them)

Lisa Sakura — Mon, 04 May 2026 07:39:57 +0000

1. The access collection black hole

You need Figma access, Google Analytics, WordPress admin, GitHub, and the client's Slack. You ask. They forward a password email from two years ago. You ask again. Their developer says they'll get back to you. Three days pass.

The fix: Send a single, complete access list on Day 1 — not "we'll need some access" but the exact list, with specifics for each tool, and a deadline. Include what happens if the deadline is missed. Framing it as "we start discovery without these, but integration builds are blocked until week 3" changes behavior fast.

A good intake form covers this before the project starts. Here's a free 27-question version if you need a starting point.

2. Scope drift that starts in the kickoff call

The sales call sets one expectation. The kickoff call assumes something slightly different. The project brief says something else. By week two, you're building features nobody explicitly agreed to.

The fix: Send a written kickoff summary within 24 hours of the kickoff call. Not meeting minutes — a plain-language document that says: "Here's what we're building. Here's what we're not building. Here's what triggers a scope change conversation."

Ask the client to confirm it explicitly. "Reply with OK or any corrections" clears ambiguity in a way that a call summary in Notion does not.

3. The assumption handoff from sales to delivery

Your salesperson knew the client's real pain point. The delivery team doesn't. So delivery builds to the spec, not to the problem.

The fix: A structured sales-to-delivery handoff doc. Ideally filled in by the salesperson while the memory is fresh, covering:

What problem the client actually wants solved
What they're worried about
What they mentioned off the record
Any political context (stakeholders, existing vendor relationships)

Five minutes of capture prevents hours of rework.

4. The "we'll figure it out" kickoff agenda

A kickoff call with no structure turns into a 60-minute relationship-building session that covers none of the questions you needed answered. You leave with good vibes and no information.

The fix: Send the kickoff agenda 48 hours before the call. Include the specific decisions you need to make, the access items you need, and the one question the client most needs to answer clearly. Clients who see the agenda in advance show up ready — you get twice as much done in the same time.

5. No follow-up system for client responses

You send three requests in the first week. One gets answered immediately. One gets a partial answer. One disappears.

You don't have a clean way to track which thread is outstanding, so you either let it drop or send an awkward "just following up" email that makes you feel like a debt collector.

The fix: A standard set of follow-up messages that escalate in specificity without escalating in tone. The first follow-up restates exactly what you need. The second ties it to a project impact ("we can't start X until we have this"). The third offers a simple alternative ("if this isn't available, here's our fallback").

This is tedious to write fresh every time — most agencies use 3-5 reusable templates for this.

6. Recreating the same structure every time

Every new client gets a new folder structure, a new project board, a new onboarding checklist. Your senior project manager does it from memory. Your junior does it slightly differently. By month three you have three inconsistent onboarding setups and no institutional knowledge.

The fix: A single canonical onboarding template. One folder structure. One project board template. One checklist. When something doesn't fit a client, you adapt the template — not invent something new.

This sounds obvious. Most agencies don't have it. If you build one folder structure and one checklist and use them exactly twice, you've already recouped the time spent.

7. The first deliverable that surprises the client

You build exactly what was in the brief. The client expected something different. Not because you did it wrong — because neither of you understood the gap between "what we agreed" and "what they were picturing."

The fix: A pre-delivery alignment check before you share the first real deliverable. Not "here's what we built" — "here's what we built, here's how it maps to the brief, here are two decisions we made that weren't covered in the spec."

Surface the choices before they become surprises. Clients who feel informed are forgiving. Clients who feel surprised are not.

The pattern

Every one of these breakpoints has the same root cause: information that exists somewhere didn't make it to the right person at the right time.

The solution isn't software. It's a repeatable system for capturing and transferring context — intake questions before the project starts, a kickoff structure that surfaces decisions, templates that remove the "rebuild from scratch" tax, and follow-up language that escalates without burning goodwill.

If you want a starting point, we put together two free resources:

10-step AI-native onboarding checklist — what to cover in the first two weeks
27-question client intake form — the questions to ask before work starts

Or if you want the full system — folder structure, SOP, email templates, automation recipes, kickoff brief generator — we bundled all of it into the Agency Onboarding OS (€49, founding batch).

What's the onboarding breakpoint that's cost you the most? Genuinely curious what the distribution looks like in practice.