<aside> 💡 Use case: these seven tools are the customer spine. They hold one profile per person and company, the content calendar, the brand files and the publish dates, so every agent works from the same record instead of its own copy.

</aside>

<aside> 🔗 How it connects: in a first build you do not need any of these connected. Export what you have (contacts, the calendar, the brand wiki) into the matching brand-os/ folder and the agents read it there. Once the loop works, swap an export for an API or MCP connection, one tool at a time. The agents still read and write the same files, so nothing else changes.

</aside>

HubSpot

<aside> 🤝 Its job here: the CRM. Every lead and customer has one record here, and new leads from chats and DMs are added to it.

Used by: Leads & conversations, and the "DM or lead at 11pm" playbook.

From its homepage: "HubSpot's customer platform includes all the marketing, sales, customer service, and CRM software you need to grow your business."

</aside>

HubSpot homepage

HubSpot homepage

Airtable

<aside> 🗓️ Its job here: the content calendar. Each row is one piece of content with its channel, due date and status, and the Content engine takes the next item marked ready.

Used by: Content engine, and the "Content calendar looks thin" playbook.

From its homepage: "Build Enterprise-ready AI Workflows, Apps & Agents"

</aside>

Airtable homepage

Airtable homepage

Google Drive

<aside> 📁 Its job here: the brand asset drive. Logos, photos, approved graphics and finished videos live here, so nobody has to ask where the latest file is.

Used by: Creative studio, through brand-os/creative/asset-library.md, which lists what is in the drive and where.

From its homepage: "Store and share files online"

</aside>

Google Drive homepage

Google Drive homepage

Notion

<aside> 📚 Its job here: the brand wiki. The long-form version of who you are, what you sell and how you talk about it.

Used by: every department that reads brand-os/brand-brain/: Market radar, Content engine, Creative studio, Reviews & reputation.

From its homepage: "Where teams and agents Think together."

</aside>

Notion homepage

Notion homepage

Segment

<aside> 🧬 Its job here: customer data. It collects what each customer does across your site and channels and joins it to one profile.

Used by: the orchestrator, as part of the customer spine.

From its homepage: "Collect, unify, and enrich customer data across any app or device with the Twilio Segment CDP, now available on Twilio.com."

</aside>

Segment homepage

Segment homepage

Supabase

<aside> 🗃️ Its job here: the unified store. The one database the agents read from and write to, where the profiles from HubSpot and Segment meet the content and results.

Used by: the orchestrator and every department, once you move past Markdown files.

From its homepage: "Build in a weekend Scale to millions"

</aside>

Supabase homepage

Supabase homepage