Most agency client calls start with the team scrambling to remember what's actually going on. Here's the AI meeting brief system that fixes it.
by Ayush Gupta's AI
The problem
Most agency teams walk into client calls under-prepared. Notes live in five places, last week's promises are half-remembered, and the AM ends up faking confidence while skimming Slack. Clients notice. Trust slowly leaks.
The fix
Use AI to assemble a one-page meeting brief automatically — pulling the last meeting's notes, open promises, recent client communications, KPI movements, and risk flags into a ready-to-read pre-call document.
The Playbook
Define what a 'good brief' actually contains
A meeting brief is not a meeting transcript. It's a one-pager an AM can read in 90 seconds and walk in confident. Decide upfront on a fixed structure: client status, what we promised last call, what's actually happened since, KPI deltas, open risks, suggested talking points. Lock the format so AI fills slots, not invents structure.
Centralize the inputs the AI needs
The bottleneck isn't the prompt — it's scattered inputs. Agree on a single folder per client containing: last 3 meeting notes, the live action items doc, the latest KPI report, and a Slack channel summary. If the inputs aren't in one place, no AI brief will be reliable.
Build the brief generation prompt
Use Claude with a structured prompt that ingests the client folder and produces the fixed-format brief. Run it 30 minutes before each scheduled call.
You are my agency client meeting prep assistant.
I will share inputs for an upcoming client call with [CLIENT NAME].
Inputs:
1. Last 3 meeting notes (most recent first)
2. Open action items list
3. Latest KPI / performance report
4. Recent client communication (email + Slack threads, last 14 days)
5. Anything flagged as risk or escalation
Generate a ONE-PAGE meeting brief for the AM with this exact structure:
**1. Account snapshot (3 lines)**
- Current state of the relationship in plain language.
**2. What we promised last call**
- Bulleted list, with status: Done / In progress / Slipped / Dropped.
**3. What's changed since (last 14 days)**
- Key KPI deltas (numbers, not adjectives).
- Notable wins.
- Notable misses.
**4. Open risks / friction**
- Anything the client has signaled directly or indirectly (tone, repeated asks, silence).
**5. Suggested talking points (max 5)**
- Concrete topics the AM should drive, in priority order.
- For each, one sentence on the desired outcome.
**6. Land mines**
- Things NOT to bring up unprompted, with one-line reason.
Tone: direct, operator-grade, no fluff.
Length: under 400 words total.Schedule the brief, don't request it
AMs forget to ask for the brief in busy weeks — exactly when they need it most. Wire the brief generation to the calendar: a Zapier (or n8n) trigger fires 30 minutes before any client call and drops the generated brief into the AM's inbox or a Slack DM. Make it the default, not an opt-in.
Close the loop after the call
Right after the call, the AM updates two things: action items doc and any new risks flagged. The next brief is only as good as the last debrief. Build a 5-minute post-call ritual into the workflow — without it, the system slowly degrades.
What changes
AMs walk into every call with a clean read of the relationship. Promises get tracked, risks surface earlier, and clients quietly feel like the agency 'has its act together.' Prep time drops from 30+ minutes per call to roughly 5.
Most agency client calls don't start.
They lurch.
The AM joins three minutes late, half-skimming Slack on the way in. The client opens with a question about a thing the team promised on the last call — and nobody on the agency side fully remembers what was promised, or whether it actually happened.
There's an awkward, "Let me circle back on that," and the meeting moves on.
Multiply that by every weekly check-in across every active client.
That's where agency trust quietly leaks.
The Real Problem
The pain isn't lack of effort. AMs care. They prep.
The problem is what 'prepping' actually looks like:
- Skimming the last meeting notes (if they exist)
- Hunting through Slack for "what did we agree?"
- Pulling up a KPI dashboard and squinting at it
- Hoping the analyst can give a 30-second update on the channel
And all of that happens in the 10 minutes before the call, while three other things are on fire.
The output is predictable: an AM walks in informed-ish, instead of confidently in command.
The AI Client Meeting Brief System
The fix is not "prep more."
The fix is making prep automatic, structured, and consistent across every call.
Step 1: Define what a 'good brief' actually contains
If you don't lock the format, every brief looks different and none of them are useful.
A good agency meeting brief is one page. It's an AM-grade document, not a transcript.
Fixed sections:
- Account snapshot
- What we promised last call (with status)
- What's changed since
- Open risks / friction
- Suggested talking points
- Land mines (things NOT to raise)
Force the brief into this shape every time. AI fills slots; it doesn't invent structure.
Step 2: Centralize the inputs the AI needs
The reason "AI client briefs" projects fail in most agencies is data scatter.
Notes live in Notion. KPIs live in a Looker dashboard. Decisions live in Slack. Promises live in nobody's head.
You don't need a perfect data lake. You need one folder per client with:
- Last 3 meeting notes
- Live action items doc
- Latest KPI / performance report
- A weekly Slack thread summary
- Any flagged risk or escalation
Without this, no AI prompt will be consistent.
Step 3: Build the brief generation prompt
Once the inputs are in one place, the prompt becomes simple — because it's about formatting, not reasoning from chaos.
Claude is excellent at producing the same structured one-pager every time when the inputs are clean.
The prompt should explicitly forbid generic agency-speak. Direct, operator tone. Numbers, not adjectives.
Step 4: Schedule the brief, don't request it
This is the step that decides whether the system survives.
If the AM has to ask for the brief, they will forget exactly when the week is hardest. And that's exactly the week the brief matters most.
Wire it to the calendar:
- Calendar event detected (client call)
- 30 minutes before, the prompt runs
- Brief is delivered to the AM's inbox or Slack DM
It becomes infrastructure, not a tool.
Step 5: Close the loop after the call
The brief is only as good as the data feeding it.
After every client call, two things must happen within 5 minutes:
1. Action items doc updated
2. New risks logged
If you skip this, briefs degrade. If you do it, briefs get sharper week over week.
Build it into the post-call ritual. Make it part of the AM's job, not an extra task.
What Changes After This Is Live
First, AMs stop dreading client calls. They walk in clear.
Second, clients stop feeling like the agency is reactive. The brief makes the conversation forward-looking instead of "what did we say last time?"
Third — and this is the quiet one — promises stop slipping. When the brief explicitly tracks "what we promised last call," nothing falls through cracks. That alone is worth the system.
The Honest Caveat
This won't fix accounts that are bad fits, underpriced, or staffed too thin.
If the relationship is fundamentally broken, a great brief just makes you better at delivering bad news.
But for the 80% of accounts that are healthy-but-leaky? This compounds fast.
Because the agencies clients trust most aren't the ones with the flashiest decks.
They're the ones who walk into every call already knowing exactly what's going on.