How to prepare an enterprise client review with an AI agent

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

Deep contract, Google Ads, Meta AdsContract v1.1.0last verified 2026-10-02reviewed

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

When to use it

Use it when

Do not use it when

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

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.

Evidence every conclusion must carry

Every headline figure carries platform, window and attribution basis.
Every claimed action exists in the change log or the client journal with its date, and its reason when one was recorded.

Inputs
Input	Required	What it is
`period`		The review period.Default: last full month.
`target`	required	The number the client judges the account by.

In order. Every tool named is one the gateway ships, and links to its reference.

Steps

Pull the period's results per platform, and the previous period for context.google_ads_get_insightsmeta_get_insightstiktok_get_insightspinterest_run_report
Read the client journal for the period: changes made with their reasons, events noted by the team, and changes archived from Meta and Google.get_client_memoryThe journal keeps the why, and Google history beyond its 30-day limit.
Pull the change log for the period: what the enterprise actually did.google_ads_get_change_eventsmeta_get_ad_activityThe changes-made list is the part clients cannot get from their own dashboard.
Add the site view if GA4 is connected, and organic context if Search Console is.ga4_run_reportgsc_find_losses_gains
Assemble: results vs target, work done, what it changed, next period's plan.

The observable condition, what it lets you conclude, and what takes the conclusion back.

When The period includes a change whose effect is not yet measurableConclude Present it as work done with results pending, dated; do not claim early credit.
When Results missed targetConclude 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 GA4Conclude Show the client both numbers with the mechanism; agencies lose accounts over discovered discrepancies, not disclosed ones.

The pack is a draft for the account lead: positioning, tone and commitments are theirs.

Nothing in preparing the review writes to any account.

The cases where the analysis is wrong and still looks right. Read them before trusting a number.

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.

What Enterprise client review returns
Section	What it holds
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.