Most "AI for agencies" advice stops at "use ChatGPT for your emails."
That's fine. But if you want to actually reduce the chaos at the start of a new client project, you need a specific workflow — not just vibes.
Here's the failure mode that made me build this: last year I kicked off a 3-month SEO project without Google Search Console access. We spent the first 11 days working from assumptions instead of data. Nobody noticed until the first delivery review. The client noticed immediately. Three days of rework, one awkward call, and a dent in trust that took weeks to repair. All of it preventable with a prompt that takes 4 minutes to run.
Here's the exact 5-prompt system I use to run client onboarding with minimal manual effort. All five prompts are copy-paste ready. All five have a clear trigger: when you run them, what goes in, what comes out.
Why most agencies don't automate onboarding
Three reasons:
Every client feels different. It seems like automation won't work because "it depends." But 80% of the work is the same every time: collect access, brief the team, generate the kickoff prep, send the welcome.
They use the wrong tools. Zapier-based automations break. Notion templates sit unused. The missing link is a conversational AI that can take your messy client intake and produce a clean deliverable.
They try to automate the whole thing at once. Five prompts, run manually, is better than a broken full automation. Start with prompts. Graduate to scheduled workflows when you have 3–5 clients running the same thing.
The 5-prompt onboarding system
Prompt 1 — Kickoff brief generator
When: After the client fills in your intake form, before the kickoff call.
What goes in: The client's answers to your intake questionnaire (paste them in).
What comes out: A 1-page internal brief your team reads before the call.
You are preparing an internal kickoff brief for a new client project.
Here is the raw intake form data:
[PASTE INTAKE FORM ANSWERS HERE]
Write a 1-page internal brief covering:
1. Client background and context (3–4 sentences)
2. Primary goal for this engagement (1 clear sentence)
3. What success looks like at 30 days and 90 days
4. Key risks or unknowns to flag in the kickoff call
5. Access items we need to collect before delivery starts
Keep it factual. Do not invent details not in the intake. Flag anything ambiguous with [UNCLEAR — ASK IN CALL].
Result: A brief your team can read in 3 minutes before the call. No more "wait, what are we actually doing for this client?"
Prompt 2 — Access request email generator
When: After the kickoff call. You now know what you need. Client hasn't sent anything yet.
What goes in: Service type + list of access items needed.
What comes out: A polite, clear email the client can actually respond to.
You are writing an access request email to a new client.
Service type: [e.g., SEO / web design / social media management]
Access items needed:
- [List each item, e.g., "Google Analytics view access"]
- [Google Search Console access]
- [WordPress admin login]
- [Brand asset folder link]
Write a professional email that:
- Opens with a brief context sentence (we're starting delivery next week)
- Lists each access item clearly with a one-line explanation of why we need it
- Sets a specific response deadline (use 3 business days from now)
- Closes with a clear next step
Do not use hollow phrases like "Hope this finds you well." Get to the point.
Result: A specific, action-driving email that clients actually respond to. Not a generic "we need access" dump.
Prompt 3 — Missing-input detector
When: 48 hours before delivery starts. Someone on your team should run this.
What goes in: The intake form + access log (what you've received so far).
What comes out: A list of gaps that will block delivery.
You are a project coordinator reviewing client onboarding completeness.
Intake form received:
[PASTE INTAKE FORM ANSWERS]
Access items received so far:
[PASTE ACCESS LOG OR LIST WHAT'S ARRIVED]
Check for:
1. Any service-specific access items missing (e.g., for an SEO project: GSC, GA, CMS)
2. Any ambiguities in the intake that weren't resolved in the kickoff call
3. Any scope items mentioned but not confirmed in writing
Output a numbered list of blockers. For each blocker, include:
- What's missing
- Why it blocks delivery
- Suggested action (e.g., "follow up email today", "ask in next call", "can proceed without — flag for later")
If nothing is blocking, say "Onboarding complete. No missing inputs detected."
Result: A clear pre-delivery checklist. Your team knows exactly what to chase before they start work.
Prompt 4 — Client welcome email
When: Within 24 hours of signing.
What goes in: Client name, service type, start date, main contact on your team.
What comes out: A warm but professional welcome that builds immediate trust.
You are writing a client welcome email from a small agency.
Client name: [First name]
Service: [e.g., "website redesign and SEO setup"]
Project start date: [date]
Their main contact at our agency: [name and role]
Write a welcome email that:
- Opens with a genuine welcome (1–2 sentences, not hollow)
- Confirms what they've signed up for and the start date
- Introduces their main contact at the agency
- Sets expectations for the first 2 weeks (intake form, kickoff call, access collection)
- Ends with an action step (e.g., "please complete the intake form by [date]")
Tone: warm, direct, professional. No "we're thrilled to have you on board" opener — find something more genuine.
Result: An email that makes clients feel like they chose the right agency — in the first 10 minutes after signing.
Prompt 5 — Week-1 status update
When: End of week 1 of the project.
What goes in: What actually happened in week 1 (honest bullet points).
What comes out: A client-facing update that manages expectations and builds trust.
You are writing a week-1 status update for a client.
What happened this week:
- [List actual completed items, e.g., "completed site audit"]
- [Started keyword research]
- [Waiting on GSC access — followed up twice]
Write a client email that:
- Summarizes what was done (factual, specific)
- Notes anything still pending from the client's side (without sounding like a blame)
- Sets expectations for week 2
- Ends on a forward-looking note (what they'll see/hear next from us)
Keep it under 200 words. Clients don't want a report; they want reassurance.
Result: A consistent weekly update that takes 3 minutes to generate. In our experience, clients who get proactive weekly updates send dramatically fewer reactive check-in emails — usually because there's nothing left to ask.
Making these prompts part of your workflow
The prompts above work best when:
You have a standard intake form. If every client fills in the same questions, Prompt 1 and Prompt 3 run identically every time. Start with the free intake form template if you don't have one.
You have an access tracker. Prompt 3 needs a running log of what's been sent. Even a simple Google Sheet column works.
You have a checklist to follow. The prompts fill in deliverables — but someone still needs to know when to run each one. Use this onboarding checklist as the trigger map.
The real value of this system
The five prompts above will not save your agency.
What they'll do is remove the three biggest first-week failure modes:
- Starting delivery without a clear brief (Prompt 1)
- Chasing access reactively instead of proactively (Prompts 2 + 3)
- Going silent after the signing email (Prompts 4 + 5)
Each one takes 3–5 minutes to run. Combined, they cover 80% of the chaos in the first two weeks.
If you want all five prompts plus a full onboarding system (folder templates, SOPs, scope management docs, access tracker), that's what the Agency Onboarding OS is — a complete kit instead of five scattered files.
But even just these five prompts, run manually, will make your first two weeks with every client noticeably cleaner.
Built these while running a digital agency and got tired of starting the same chaos every time. If you're at the stage where you're onboarding more than 2–3 clients a month, a system like this pays for itself in the first week.
Questions or variations? Drop them in the comments — happy to write additional prompts for specific service types.
Top comments (0)