Use case · Marketing agency
Agency

Campaign context
across every client.

Agencies unify CRM, ad platforms, analytics, creative tools, and client comms — so strategists, creatives, and account leads share cited answers instead of siloed decks and Slack threads.

All use cases
Federation path

Marketing agency joins
your full stack.

Marketing agency
Gyri graph
Ads + creative
How teams work

From signup to
live workspace.

01

Per-client workspaces

Isolate client data with workspace-scoped auth while reusing agency playbooks and benchmarks.

02

Federate GTM + creative stack

HubSpot, Google Ads, Meta Ads, analytics, Figma/Canva, and Slack feed one searchable graph.

03

Cited reporting & briefs

Pull performance, creative, and CRM context into audit-ready answers for clients and internal standups.

04

Agency buildout

We configure client templates, campaign insight types, and starter dashboards for your pod structure.

Federated sources

Stack this team uses.

Typical connectors for this team — swap for your stack during signup.

HubSpot CRM, marketing, sequences Native
Google Ads Paid search metrics Native
Meta Ads Facebook & Instagram ads Native
Google Analytics Web & app traffic Native
Slack Team comms Native
Figma Design files & comments Native
Plan

Required tier

Pro

Pro covers multiple integrations per client workspace, workflows, and agent runs for campaign ops at scale.

Get started

Start free

Start free with three connectors on a pilot client workspace. Prep your agency buildout at signup; production multi-client setup typically lands on Pro.

Your buildout request is saved at signup and queues after you verify email and send your first command through Claude MCP.

Related: Connect CRM, Slack & docs

Ready to build?

Edit the prepopulated buildout request on signup — we start when Claude MCP connects.

How it works