DEV Community

Lisa Sakura
Lisa Sakura

Posted on

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

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:

  1. Access collection drags into week two
  2. Scope is fuzzier after the kickoff than before
  3. The onboarding checklist lives in someone's head
  4. Clients don't know what to expect or when
  5. 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.
Enter fullscreen mode Exit fullscreen mode

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.
Enter fullscreen mode Exit fullscreen mode

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.
Enter fullscreen mode Exit fullscreen mode

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.
Enter fullscreen mode Exit fullscreen mode

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.
Enter fullscreen mode Exit fullscreen mode

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:

  1. Client signs → automated intake form sent (30-second trigger)
  2. Intake responses come back → paste into Prompt 1 → kickoff brief generated in 90 seconds
  3. Kickoff call runs from the brief → scope decisions documented live
  4. Prompt 2 generates access email → sent same day
  5. 3-day follow-up via Prompt 2 variant if no response
  6. Prompt 3 flags any gaps → follow-up questions sent before day 5
  7. 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

Top comments (0)