Agencies

Agency accounts have their own navigation, separate from the per-brand sidebar:

• Dashboard — total clients, monthly revenue, active campaigns, average ROAS, pending approvals, top-performing clients, recent activity, and campaign distribution by client.
• Clients — the client roster, with search, status, and plan tier.
• Campaigns and Analytics — activity and performance read across the book of business rather than one brand at a time.
• Approvals — one queue for agent actions awaiting a decision across all client accounts.
• Team, Usage, Workflows, Reports, and Settings.

These screens are gated to agency accounts. Opening the Usage dashboard on a non-agency account returns an access-denied message rather than an empty page.

Where a single-brand account shows a brand selector in the header, an agency account shows a client switcher. It lists every client you have access to, plus an entry back to the Agency Dashboard for managing all clients at once. Selecting a client scopes the whole platform — Audience, Campaigns, Funnels, Content Studio, Agent Workflows, and Integrations — to that client's data only. Nothing about one client's audience segments, campaign history, or connected accounts is visible from another client's Brand Space, and switching does not ask you to authenticate again.

Each Brand Space has its own audience data, its own connected integrations (a client's Klaviyo or ad-platform connection belongs to that Brand Space, not to your agency account), and its own campaign and funnel history. Disconnecting or reconfiguring an integration for one client never touches another client's connections. The same scoping carries into the agent canvas: the Agent Suite signs you in with a session that names the tenant, workspace, and brand you currently have selected, so a workflow you build is bound to that context.

Agency Approvals collects agent actions that need a human decision from every client in one queue. Each request carries enough context to decide without opening the client:

• What is being asked — publishing a campaign, raising a budget, allocating spend, publishing or modifying content, connecting or disconnecting an integration, deploying or changing an agent, or exporting data.
• A risk level of low, medium, high, or critical, plus estimated cost and estimated reach where they apply.
• Who requested it, who it is assigned to, and an SLA deadline — requests past that deadline are flagged as breached.

Approving takes optional comments; rejecting requires a reason, which is returned to the requesting agent. Requests can also expire, be cancelled, or be escalated. Campaign-level approvals additionally surface on each client's own Campaigns screen and Dashboard.

The Usage dashboard is the agency-only view of what the platform is costing you, by billing period (current month or any of the previous three):

• Total LLM tokens and the API call count behind them.
• LLM cost for the period.
• BigQuery storage across all clients.
• How many clients had any usage at all, plus a per-client table breaking each figure down.

Each client can also hold its own LLM API keys on the client detail screen, added per provider with an optional monthly token limit and monthly cost limit. That is how you put a client's model spend on the client's own key and cap it, rather than pooling it.

Client Comparison, under Analytics, is the one screen that deliberately puts clients side by side: tick the clients you want, and it returns a table of active campaigns, total spend, total revenue, and ROI, one column per client. Reports covers cross-client performance over time, including a monthly revenue trend and a client-performance breakdown. Both read the same underlying numbers as each client's own analytics, so a figure you quote in a report matches what the client sees in their Brand Space.

Onboarding is the same every time:

1. Add the client from Clients — name, URL slug, plan tier (Starter, Growth, or Enterprise), and an admin email for their side.
2. Complete the brand-onboarding wizard for the client's Brand Space: basic info, industry and company size, contact details, settings, then confirm.
3. Connect the integrations that client already runs, so audience intelligence syncs both directions from day one.
4. Add their LLM API key and set monthly token and cost limits, if you are keeping model spend on the client's own account.
5. Assign the team. Agency team members are managed under Team; access can also be granted per client workspace.
6. Build the client's first audience segments, then hand off — or keep running — Campaigns, Funnels, and Agent Workflows scoped to that client alone.

Agency Settings holds your own profile and branding — agency name, slug, contact email, website, and primary and secondary colors.