# How to prepare an agency client review with an AI agent

> Tier: deep. Full contract: quantified decision rules and evidence requirements.

The monthly client pack for one account: results against target, what the agency changed and why, what comes next, every number traceable.

**Intent.** Assemble a client-ready narrative where every figure survives the client's own dashboard check.

## When to use

- Monthly or quarterly client reviews.
- Renewal conversations, where the changes-made list is the value story.

## When not to use

- Daily reporting: this is a narrative pack, not a dashboard.
- Accounts the agency has run for under a month: there is no story yet, say so rather than pad.

## Sources

Required: Google Ads, Meta Ads
Optional: TikTok Ads, Pinterest Ads, Google Analytics 4, Search Console

## Preconditions

- Only this client's accounts ticked in the workspace: scoping is the confidentiality mechanism.
- The client's target (CPA, ROAS, volume) stated, not assumed.

## Inputs

- `period`: The review period. Default: last full month.
- `target` (required): The number the client judges the account by.

## Procedure

1. Pull the period's results per platform, and the previous period for context. — tools: `google_ads_get_insights`, `meta_get_insights`, `tiktok_get_insights`, `pinterest_run_report`
2. Pull the change log for the period: what the agency actually did. — tools: `google_ads_get_change_events`, `meta_get_ad_activity`
   The changes-made list is the part clients cannot get from their own dashboard.
3. Add the site view if GA4 is connected, and organic context if Search Console is. — tools: `ga4_run_report`, `gsc_find_losses_gains`
4. Assemble: results vs target, work done, what it changed, next period's plan.

## Decision rules

- **When** The period includes a change whose effect is not yet measurable → **conclude** Present it as work done with results pending, dated; do not claim early credit.
- **When** Results missed target → **conclude** Lead with the miss and its diagnosed cause; a pack that buries the miss costs the renewal later. **Unless** The cause is still unknown; then say what is being investigated and by when.
- **When** A platform's self-reported win disagrees with GA4 → **conclude** Show the client both numbers with the mechanism; agencies lose accounts over discovered discrepancies, not disclosed ones.

## Evidence requirements

- Every headline figure carries platform, window and attribution basis.
- Every claimed action exists in the change log with its date.

## Human approval boundary

- The pack is a draft for the account lead: positioning, tone and commitments are theirs.
- Nothing in preparing the review writes to any account.

## Failure modes

- Cross-client leakage: a workspace with several clients' accounts ticked can mix data; verify scope before the first call.
- Claiming platform-attributed revenue as business revenue inflates the story and detonates at the CFO's desk.
- Month lengths differ; compare daily rates or same-length windows, not raw month totals.

## Output

- **Results vs target**: The number, the target, the gap, the trend.
- **Work done**: Dated changes from the log, each tied to intent.
- **Next period**: Planned moves, expected effect, measurement plan.

## Related

- Skill: [weekly-performance-review](https://www.getmcpads.com/skills/weekly-performance-review.md)
- Skill: [cross-platform-performance](https://www.getmcpads.com/skills/cross-platform-performance.md)
- Guide: [cross-platform-report](https://www.getmcpads.com/guides/cross-platform-report.md)