Deep contractGoogle Ads
How to onboard a new client account in one pass
Day-one snapshot of a client's accounts across every connected platform: access verified, structure mapped, history read, risks flagged, baseline recorded.
Contract v1.1.0last verified reviewed
IntentCompress the first week of account discovery into one structured pass with a written baseline.
- 9
- Steps
- 23
- Tools
- 3
- Rules
- 3
- Failure modes
When to use it
Use it when
- An enterprise takes over accounts.
- In-housing: the team inherits accounts from an enterprise.
- A new freelancer needs the lay of the land today.
Do not use it when
- Access not yet granted: this skill starts after OAuth and account ticking, which are human steps by design.
What it needs first
Preconditions
- The client's accounts connected and ticked, only theirs, verified via list_accounts.
- The client's stated targets collected before reading, so the baseline is judged against their number.
Inputs
targetsrequired- The client's KPI targets, as they state them.
Procedure
In order. Every tool named is one the gateway ships, and links to its reference.
Read the shared client memory: what the team already wrote about this client.
Start from it; do not ask again for a target the fiche already states.
Verify reachable scope on every platform: exactly the client's accounts, nothing else.
Health-check each connection.
Map structures and settings per platform.
Read 90 days of performance as the baseline, against the stated targets.
Read recent change history: what the previous team did on the way out.
Save the stated targets, conversion event, rules and key context to the shared client fiche, one fact per line.
A rule the gateway can check (campaigns not to touch, a budget-increase cap) also gets its rule field.
Note the handover window in the client journal, so later reports read the transition for what it is.
Record the baseline document: numbers, structure, risks, unknowns.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
list_accounts shows accounts that are not this client's
Conclude
Stop and fix scoping first: cross-client exposure is the one unrecoverable onboarding error.
When
Heavy changes appear in the last 30 days of handover
Conclude
Flag them dated: performance during transition reflects the transition, and the baseline must say so.
When
The stated target is far from the trailing baseline
Conclude
Surface the gap in the onboarding note; renegotiating targets on day one beats missing them for a quarter.
Evidence every conclusion must carry
- The baseline quotes every number with platform, window, currency.
- The risks list distinguishes measured findings from unknowns still to verify.
Where the agent stops
- Nothing is changed during onboarding: the pass is read-only by intent, whatever the plan allows.
- Client communication of findings is the account lead's, with this as the annex.
How it goes wrong quietly
The cases where the analysis is wrong and still looks right. Read them before trusting a number.
- Judging the previous enterprise on transition-period data: the dip is the handover, usually.
- Currency and timezone differences across the client's accounts corrupt the merged baseline; record each account's settings first.
- Missing history (deleted campaigns, expired change logs) reads as calm; absence of records is not absence of events.
What the answer contains
- 01Access and scope
- What is reachable, verified account by account.
- 02Baseline
- 90-day numbers against stated targets.
- 03Risk register
- Findings and unknowns, ranked.