Use case · GTM team
Revenue

Revenue teams
on one graph.

Sales, RevOps, and enablement federate CRM, email, Slack, call recordings, and docs — pre-call briefs, deal narrative, and competitive intel with citations, not copy-paste.

All use cases
Federation path

GTM team joins
your full stack.

GTM team
Gyri graph
CRM + comms
How teams work

From signup to
live workspace.

01

Connect the revenue stack

HubSpot, Pipedrive, Gmail, Slack, Gong, and Notion indexed into one workspace graph.

02

Deal + account memory

Insights persist across reps, handoffs, and quarters — Claude and Cursor read the same company context.

03

Cited answers for the field

Pre-call briefs, objection handling, and exec summaries link back to CRM and comms sources.

04

GTM buildout

We ship default searches, deal insight types, and MCP playbooks for your ICP and motion.

Federated sources

Stack this team uses.

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

HubSpot CRM, marketing, sequences Native
Slack Team comms Native
Google Workspace Gmail, Calendar, Drive Native
Gong Call intelligence Native
Pipedrive CRM deals pipeline Native
Notion Wikis & project docs Native
Plan

Required tier

Free

Free covers a solo rep or RevOps eval with three integrations — enough for CRM + email + Slack federation.

Get started

Start free

Start free, connect CRM + Slack + email, and prep a GTM buildout on signup. Queue it with your first Claude MCP command after verify.

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

Related: Federated search for AI

Ready to build?

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

How it works