EP026: Building Your Company Brain

Jeff is back from paternity leave and building a company brain. Jay challenges him to think bigger: before you can run agents, you need a context layer. They dig into data architecture, call transcript intelligence, and what it actually takes to build enterprise-grade AI for customer success. KEY TAKEAWAYS Source data stays in source systems: Pull via API from your existing tools rather than duplicating data. The real question is whether to write enrichment back to the CRM or store it natively. Context layer first, agents second: Every account needs a living record — call summaries, sentiment, history — before an agent can act intelligently on its behalf. Company brain = ontology + continuous enrichment: Map your key entities (customers, contacts, contracts, products) and keep populating them from calls, emails, and Slack. Agents vs. deterministic workflows: Renewals have fixed steps. Inject AI where judgment matters — like building a personalized proposal using full account context. Call transcripts are gold: Extract from Fathom, store in Postgres, add a sentiment + sensitivity classifier, expose via MCP — then query your entire call history from Claude. Cowork is MVP, not enterprise: Jeff's scheduled Fathom summaries are a perfect first step, but they stop when his laptop closes. Enterprise agents need to run independently. Harnesses vs. models: Claude and ChatGPT are harnesses above the intelligence layer. What teams actually need is an enterprise harness that shares context company-wide. LLMs need precision, not volume: Models are "dumb" because they know everything. Give them exactly the context they need — and nothing more. CHAPTERS 00:00 - Welcome & intro 01:44 - Jeff's "Steve": building a custom CS platform 04:23 - Should you write data back to the CRM? 07:21 - Context layer vs. application layer 10:44 - Building a company brain & ontology 13:16 - Agents vs. deterministic workflows 16:40 - Renewals as the perfect AI use case 20:36 - MVP first, long-term vision 22:30 - LLMs need precision context 25:15 - Open source AI & why it matters 26:35 - The Fathom + Postgres + MCP stack 33:16 - Jeff's MVP: scheduled Fathom summaries in Cowork 35:17 - From prototype to enterprise agents 38:47 - What is a model harness? 41:31 - Enterprise context & shared team knowledge 45:19 - Wrap up About the Show: Chief Customer Officer Podcast is a show about real strategies for customer-led growth in the AI era—from leaders actually executing, not just talking about it. Your Hosts: Jay Nathan – CEO of Balboa Solutions and Co-Founder of ChiefCustomerOfficer.io Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io