For agencies
When the client forwards a ChatGPT screenshot, you already have the file.
Citations, competitor prompts, and a punch list of fixes—kept in one workspace per brand. Export the PDF with your layout when the QBR lands.
What you are looking at
Watch window
30-day lookback
Enough length to catch a slide before the client notices it in leads.
Single workspace
12 brands (example)
Not twelve logins—one portfolio view, then drill into whoever is noisy this week.
Ship weekly
Friday export
Re-use the same snapshot structure so AMs are not re-explaining the method each time.
What rank trackers politely ignore
- Keyword positions do not tell you which answer snippet stole the click, or which doc the model cited instead of the homepage.
- By the time organic traffic blinks, your client already has a screenshot. You want the trail: prompt, URL, timestamp.
- AVOP is basically that trail plus the diff—who jumped you, on what question, and the smallest fix with leverage.
How shops run it
- 1
Kickoff audit
Free pass to test the story, claim it into their workspace, then run the deep baseline once they pay attention.
- 2
Monthly client pack
Same sections every month—citations, competitor movement, fixes—so nobody rebuilds the deck from scratch.
- 3
Who needs love this week
Sort the roster by worst trend. Spend Monday on the two brands sliding, not the ten that are flat.
For teams stuck in QBR prep
The uncomfortable moment is the slide where someone asks “what changed in ChatGPT?” If your answer is still a shrug, this is the tab you open first.
Notes from early teams
“We stopped duct-taping Screaming Frog exports into slides labeled ‘AI readiness.’”
“Account leads finally walk in with one link instead of twelve tabs.”
What lands after kickoff
- One ranked backlog per client—schema, copy, crawl quirks—no mystery priorities
- Side-by-side citations for the assistants your client actually names on calls
- A PDF that matches your template; monitoring emails only when something moved
What the strip looks like
Fabricated numbers—only the layout is real.
Retail client — week 1
Score & proof
GEO 72, five fixes ordered by effort vs impact
Competitors
#2 of eight on “near me + pricing” style prompts
Do this next
Ship Organization JSON-LD; About page still reads like a brochure
Two SaaS logos dipping
Score & proof
Net citations up 14% (demo math)
Competitors
Perplexity quietly dropped both on commercial asks
Do this next
Refresh llms.txt + patch the FAQ that answers “vs Competitor X”
Friday drop to AM
Score & proof
PDF + methodology footnote in the footer
Competitors
A single table with six providers — no screenshot collage
Do this next
Paste summary into Notion, file Jira tickets straight from the findings list
Your assumptions
Back-of-napkin pipeline
Multiply the lead count and deal size you already use internally. We annualise it—no magic, no promised lift.
Leads × deal size × 12 months — tweak either field and the total follows.
If those numbers held all year
This is arithmetic, not a model of AI traffic. Use it to sanity-check whether the problem is worth your time.
Agency FAQ
Multiple clients?
Yes—that is the point of the Agency tier. Separate workspaces, shared muscle memory.
Client-facing PDFs?
Paid plans export. Agency keeps your cover page, not ours.
Does this replace Ahrefs?
No. It answers assistant citations—your SEO stack still owns links.
Ship the uncomfortable slide before someone else does
Run a baseline, pick three fixes, repeat next month with the same structure.