Agency: one project per client
Keep each client’s rivals, sources, reports, and MCP scope in its own Project so landscapes never mix across accounts.
What is the operating model?
Create a Project named for the client. Add Your brand for the client company and their Rivals (plus Benchmarks if useful). Connect social, ads, and website sources, then finish the setup checklist for team access.
- Create a Project named for the client.
- Add Your brand for the client and their Rivals.
- Connect sources and leave daily scans on for primary rivals.
- Share weekly reports and battlecards per client project.
- Connect Claude or ChatGPT only to that client project when the account team needs MCP.
What is the weekly client loop?
After daily scans accumulate for the week, clear Signals, skim Compare, read the weekly report, and refresh battlecards before the client meeting. Use Refresh only for the rival you must brief today if the last daily scan is too old.
If a client needs answers inside Claude or ChatGPT, connect MCP scoped to that client project only — never reuse another client’s OAuth connection.
What goes wrong across clients?
Mixing rivals from two clients in one project breaks reports and MCP scope. If Home looks wrong, confirm you are in the correct project switcher entry. If MCP shows another client’s rivals, revoke and reconnect with the intended project on consent.
How do I hand off a client landscape?
Invite the account team from Settings → Team inside the client project’s organization. Share the weekly report link and approved battlecard PDFs rather than exporting raw Activity dumps.
When a client churns, pause Daily scans on secondary rivals to save usage, keep historical Activity, and revoke MCP connectors scoped to that project. Do not delete the project until finance confirms you no longer need the archive.
If two clients share a category rival, still keep separate projects — duplicate the rival rather than mixing landscapes — so reports and OAuth stay clean.