The Chief Customer Officer Podcast

Jay Nathan & Jeff Breunsbach
  • 4.9 (9)
  • Management
  • Updated Weekly

Conversations about digital experience and AI. 

  1. 5d ago

    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 & intro01:44 - Jeff's "Steve": building a custom CS platform04:23 - Should you write data back to the CRM?07:21 - Context layer vs. application layer10:44 - Building a company brain & ontology13:16 - Agents vs. deterministic workflows16:40 - Renewals as the perfect AI use case20:36 - MVP first, long-term vision22:30 - LLMs need precision context25:15 - Open source AI & why it matters26:35 - The Fathom + Postgres + MCP stack33:16 - Jeff's MVP: scheduled Fathom summaries in Cowork35:17 - From prototype to enterprise agents38:47 - What is a model harness?41:31 - Enterprise context & shared team knowledge45: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.ioJeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

  2. Jul 16

    EP025 Personal AI Agents, Forward-Deployed Engineers, and the Skills That Matter Now

    Jay and Jeff dig into two very different but connected stories: Jeff's homegrown AI "chief operating officer" for his household, and the $10B forward-deployed engineer boom reshaping enterprise services. Along the way: why task automation isn't the same as agents, and the skill that will matter most in the age of AI. KEY TAKEAWAYS Personal agents teach real agent behavior: Jeff's household agent, Mr. Baxter, learns from ongoing texts instead of needing reprogramming — a preview of how enterprise agents should work.Task automation isn't agents: Jay's take: most companies are building automation, not agents. Real agents remember, evolve, and run without babysitting.Enterprises are building personal agents too: A $10B industrial services company Jay spoke with made personal agents for employees a pillar of its AI strategy.Lean into human relationships: Automate what doesn't need a human touch, then reinvest the saved time into surprising and delighting customers.Be maniacal about killing process: Borrowing from Elon Musk, map every step and ruthlessly ask if it should exist — and if so, human, agent, or gone.FDEs are the new consulting: Unlike consultants who parachute in and hand off a deck, forward-deployed engineers stay and build the agents that actually run the business.Pair domain experts with engineers: The real unlock is combining business context with technical build skill — or training subject matter experts directly on AI once the architecture exists.Intelligence sovereignty is the next worry: As IP questions grow, expect more interest in post-trained open-source models for cost and control. CHAPTERS 00:00 - Catching up: inbox zero and using Claude to triage email02:46 - Meet Mr. Baxter: building an AI COO for the household07:17 - Why personal agents preview enterprise AI strategy14:45 - Three priorities: human relationships, killing process, more joy22:38 - The $10B forward-deployed engineer boom30:03 - Pairing business operators with FDEs to close the last mile34:23 - Early adopters, intelligence sovereignty, and open source catching up41:10 - Wrap-up and a tease for next week's Starbucks story 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.ioJeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

  3. Jul 9

    EP024: The Shared Brain, Forward Deployed Engineers & AI at Home

    Jay and Jeff go deep on what's actually blocking enterprise AI adoption—and it's not the technology. They cover building a shared organizational brain from call transcripts, why Zapier banned Slack DMs, the $7.5B bet on forward-deployed engineers, and personal AI coaches that are already changing daily habits. KEY TAKEAWAYS Enterprise AI Blockers Are Legal and Cost, Not Tech: The technology is far ahead of adoption. Legal, IP, and data security fears—not capability—are slowing large organizations down.Single-Player AI Is the Real Bottleneck: Most teams are getting individual value but failing to share it. The shift from personal tools to team-based AI infrastructure is where the real gains live.Build a Shared Brain from Call Transcripts: Jay's "Balboa Brain" extracts an ontology from thousands of call transcripts—people, companies, engagements, best practices—and agents update it nightly.Public Channels Feed Better Agents: Zapier's Wade Foster raised internal public Slack usage from 33% to 46% via a transparency leaderboard. Private DMs destroy the context AI needs to do its job.Forward Deployed Engineers Are the New Gold: Amazon, OpenAI, and Anthropic have collectively invested $7.5B in FDE-style organizations—because the gap between AI capability and enterprise readiness is enormous.Amazon's 45-45-45 Methodology: 45 minutes to define the problem, 45 hours to build and validate, 45 days to productionalize. Fast but grounded.Systems Thinkers Win: James Clear: "You don't rise to the level of your goals, you fall to the level of your systems." This applies to AI adoption as much as any habit.Personal AI Agents Are Already Working: Jay's NanoClaw fitness coach "Jack" is tracking nutrition and workouts with measurable results after just one week. CHAPTERS 00:00 - Intro & Hot Summer in Charleston01:30 - Enterprise AI Adoption Barriers04:45 - Single-Player vs. Multiplayer AI07:15 - Zapier Bans DMs: Building AI Context in Slack11:30 - Building the Balboa Brain19:00 - From Files to a Vectorized Database23:00 - What Are Agents, Really?26:00 - Forward Deployed Engineers: $7.5B Bet30:00 - Amazon's 45-45-45 Methodology37:00 - Less Software, Better Outcomes41:00 - DesignJoy and the One-Person FDE Model44:00 - James Clear's Systems Quote45:30 - Teaching Non-Technical People to Use AI47:00 - Personal AI Fitness Coaches & NanoClaw50:30 - Cal AI's $30M Exit and the HackAbout 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.ioJeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

  4. Jun 25

    EP023: From Vibe Coding to Enterprise AI

    Jeff and Jay get into the gap between vibe coding your own AI tools and building something your whole team can rely on. From PRD skills to master customer data files to ClickUp's "foundry" model — this episode is about what it actually takes to move from single-player AI to enterprise AI, and why slowing down now might be the fastest path forward. KEY TAKEAWAYS PRDs as AI bumpers: A PRD skill forces you to define goals, non-goals, design constraints, and integrations before building — dramatically improving what AI produces.Single player vs. multiplayer AI: Personal tools tied to your Gmail account vanish when you leave. Enterprise AI requires shared data layers, authentication, and context.MCP vs. curated data: MCPs let you pull from systems in real time, but without a clean master data set, everyone queries the same raw sources and gets different answers.The master customer file: One canonical database table of active customers is more token-efficient and reliable than re-deriving data every time an agent runs.The foundry model: ClickUp's internal team builds core agentic infrastructure and proliferates learnings org-wide — more than a center of excellence, it actually ships.Embed, don't advise: A head of AI sitting in a room advising doesn't work. AI expertise has to work shoulder-to-shoulder with domain experts to build anything real.Slow down to speed up: Individual token spend gets you ~15% better. Enterprise data infrastructure + agents unlocks step-function improvement — but requires investing in the foundation first.Sell outcomes, not automation: The future is owning an end-to-end outcome (like Fin's "resolutions") and pricing on delivery — not just automating what already exists. CHAPTERS 00:01 - Welcome & World Cup check-in02:35 - The PRD idea: vibe coding needs structure05:59 - Vibe coding vs. production-ready engineering08:00 - Single player AI vs. enterprise multiplayer10:11 - MCP vs. curated data layers15:12 - Master customer data files and token efficiency18:25 - Jeff's PRD skill in action20:57 - Generating tasks from the PRD25:20 - How enterprises are structuring AI teams33:29 - ClickUp's foundry model36:36 - Why infrastructure beats individual token spend39:18 - The ROI problem with AI investment40:42 - AI-native services: selling outcomes43:29 - Wrap up & Uncommon AI community update 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.ioJeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

  5. Jun 18

    EP022: The Real AI Work: Agent Command Centers, AI Slop, and Building Systems That Save Time

    Jay and Jeff are back with a live build episode — two operators comparing notes on what's actually working with AI. From Jay's Agent Command Center at Balboa to Jeff's Linear task ingestion system and a viral VS Code ad hack, this one's packed with real examples. Plus: why the moat in AI is attention, not technology. KEY TAKEAWAYS AI slop is a real leadership problem: Unedited Claude output is hitting inboxes everywhere. Jeff catches CSM candidates submitting unmodified hiring exercises. Fix: build a "fingerprints on it" culture before anything leaves your hands.The Minto Pyramid cuts bloat: Conclusion first, arguments second, details last. Jeff built this as a Claude Cowork skill his team runs before any doc goes to leadership or a customer.Agent Command Center over vendor lock-in: Jay's team built their own agent studio instead of using Azure, AWS, or Google — to control business logic, stay model-agnostic, and keep company secret sauce off a vendor platform.Models are becoming commodities: The real value is the harness layer — business logic, data connections, process knowledge. Erratic model companies can't be your foundation.Agents fill the gap tools never could: Jeff's Claude Code system surfaces emails and Slacks, confirms tasks, and auto-creates Linear tickets — removing the capture burden entirely.Show and tell beats mandates: Friday demo sessions at Balboa where team members show what they built create pull, not push.Treat AI work like a product backlog: Groom a pipeline of AI projects, sequence by value and dependencies — don't just experiment randomly.Attention is the real moat: kickbacks.ai can be copied in hours. The founder's following and first-mover gravity can't be. CHAPTERS 00:00 - Intro & new baby update02:30 - kickbacks.ai: the VS Code ad hack09:00 - Attention is the moat, not the tech12:00 - Claude Cowork as a paternity leave to-do list16:30 - The AI slop problem hitting leadership inboxes19:00 - The CSM hiring fingerprints test21:30 - The Minto Pyramid as a team skill25:00 - True personalization vs. segmentation28:30 - Jeff's Linear task ingestion agent31:00 - Jay's Agent Command Center at Balboa37:00 - Build vs. buy: why they went custom39:30 - Models as commodities, harness layer as moat43:30 - Keeping AI momentum inside your team46:00 - AI work as a product backlog 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.ioJeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

  6. Jun 11

    EP021: Agent Sprawl

    Jay and Jeff kick off the show by getting into the real stuff: managing agent sprawl, why most teams aren't ready for multiplayer AI, and whether tech layoffs actually have anything to do with AI efficiency. Unfiltered and practical. KEY TAKEAWAYS Agent Sprawl Is Everyone's Problem: Agents are spinning up in every tool—Planhat, HubSpot, Gainsight, Claude. Without a team-level agent command center, you're burning tokens on experiments nobody's watching.Single Player vs. Multiplayer AI: Most teams are in single-player mode—each person in their own context window. The unlock is shared agents, shared data, and shared outputs.Verified Data Sets = Trust + Efficiency: If your team doubts an agent's output, they revert to manual work. Pre-aggregated data builds trust and cuts token costs.Jevons' Paradox in Real Time: Token prices are falling, but usage is exploding. Total AI spend is going up, not down.Model Matching Matters: Don't run a daily briefing on Opus. Use Haiku for simple tasks; save big models for high-value work.Rolling Out AI Right: Canva gave 5,000 employees a week to learn AI—they froze. Fix: verify tools and data before the hackathon, then let people explore.Layoffs Aren't What They Seem: Companies citing "AI efficiency" for cuts are mostly rationalizing. Engineering hiring is up.Every Job Is Changing: The highest-paid ops role will be the AI agent builder. Lean in or get left behind. CHAPTERS 00:00 - Intro & Jeff's baby is coming00:53 - NanoClaw: Secure open-source personal agents03:47 - Meet Maverick, Jay's AI podcast producer05:11 - Agent sprawl and the containment problem06:20 - Building a team-level agent command center13:44 - Token costs, Jevons' paradox & model matching17:07 - Data centers, energy, and the physical bottleneck20:44 - How to roll AI out to teams (the Canva lesson)22:58 - Verified data sets: Why trust and efficiency go together35:02 - Sierra AI: $15.8B valuation, 100x revenue38:35 - AI in customer support: Back-end before front-end41:16 - ClickUp layoffs and the 10x vs. 100x mindset42:18 - Tech layoffs: Is AI really the reason?45:19 - Every job is changing—lean into it 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.ioJeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

  7. Jun 4

    EP020: Building Uncommon: Claude Code, Retention-as-a-Service & the Player-Coach

    Jay and Jeff are joined by Jack Nathan — our "engineering manager" for Uncommon — to share what they've actually shipped in 48 hours using Claude Code. Plus: Gainsight's retention-as-a-service bet, N8N automations surfacing customer quotes in Slack, and why the player-coach is back. KEY TAKEAWAYS Non-engineers can ship now: Jeff (not a developer) built and deployed Uncommon features using Claude Code while Jack reviewed the code as engineering manager—the gatekeeper is gone.Linear + Claude Code = AI-powered PM: Connect Linear to Claude Code and ask "what did the team change in the last 24 hours?"—issues update automatically with zero manual tickets.Community members as contributors: Uncommon members may be able to submit pull requests or plugins to improve the community itself—members building the product they use.Customer quotes on autopilot: Jeff's N8N workflow scans Fathom transcripts for praise, extracts quotes, and pushes them to a Slack channel with a link to the exact call moment.Removing the CSM as middleman: Next: auto-extract product feature requests from calls into Slack with a one-click push to a Linear ticket—cutting out lossy human translation.Gainsight Atlas skepticism: Retention-as-a-service for the long tail is compelling in theory, but branding, change management, and escalation paths make execution hard.The player-coach is back: Coinbase's 5-layer org collapse mirrors where CS leadership is heading—leaders who set direction and build, not just manage.AI as objective coach: Jay built a Claude skill that reviews exec readouts against preset criteria before team meetings—cutting meeting time in half. CHAPTERS 00:00 - Intro & Baby Watch01:20 - Welcome Jack Nathan02:14 - Uncommon Community Update06:17 - Building with Claude Code Over the Weekend08:54 - Linear Integration & AI-Powered Project Management12:00 - Community Members Contributing via PRs14:02 - Spencer's Automated Feature Request Pipeline16:45 - N8N: Customer Quotes & Product Feedback Automations21:47 - Uncommon Launch Date Discussion24:12 - Gainsight Pulse & Atlas: Retention-as-a-Service31:51 - Decentralized Work & Company as Code39:20 - Coinbase's Org Collapse & the Player-Coach Model43:49 - The CS Leader Moment We Were Made For44:20 - 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.ioJeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

  8. May 28

    EP019: The AI Native Services Playbook w/ Jay Nathan

    Jay Nathan flies solo to break down Emergence Capital's AI Native Services Playbook — what it gets right, where it falls short, and what it completely misses. Using a recruiting firm as an end-to-end example, Jay walks through the shift from selling software to delivering outcomes, and why the founders who win in this space won't come from SaaS — they'll come from services. KEY TAKEAWAYS AI Native Services defined: A business that collapses software and services into a single system, delivering outcomes the customer never has to produce themselves. You sell a result; your company produces it.The recruiting firm example: Instead of selling recruiting software, you become an AI-native recruiting firm — sourcing, screening, scheduling, and delivering candidates. Pricing shifts from per-seat to per-placement.Domain credibility over everything: Without deep expertise in your vertical, you start every sales conversation with zero trust. Domain credibility is brand — and it comes first.Mirage PMF is a real trap: Revenue growth powered by headcount, not AI, is not product-market fit. Watch gross margin — if it's not expanding as you scale, automation isn't doing the work.Outcome-based pricing is the unlock: AI-native services firms own the delivery, so they own the attribution. Price on results, not hours.Skip the VC framing: These businesses can generate significant free cash flow without venture capital. Don't let a VC playbook push you into unnatural growth moves.Continuity beats handoffs: Switching from a "Navy SEAL" pilot team to a steady-state delivery team erodes trust and loses context. Keep the same team; embed a forward-deployed engineer from day one.Ecosystem position is the moat: The AI alone won't differentiate you. Partnerships, certifications, and community presence inside your vertical will. CHAPTERS 00:00 - Introduction & Episode Overview01:56 - What Is an AI Native Services Company?03:43 - The AI-Native Recruiting Firm Example08:10 - Where Emergence Gets It Right: Domain Credibility09:41 - Mirage Product-Market Fit11:14 - Outcome-Based Pricing13:11 - Pushback: The VC Framing Problem15:40 - Pushback: Don't Switch Pilot Teams17:28 - Pushback: The Product Development Trap19:47 - The Vertical Ecosystem Advantage23:30 - Connecting AI Native Services to Customer Success26:02 - The AI Recruiting Firm in 2026: What's Automated Now28:10 - Recap & What to Take With a Grain of Salt 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.ioJeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

See All (26)

4.9
out of 5
9 Ratings

About

Conversations about digital experience and AI. 

Information

  • Creator
    Jay Nathan & Jeff Breunsbach
  • Years Active
    2024 - 2026
  • Episodes
    26
  • Rating
    Clean
  • Copyright
    © 2026 Jay Nathan & Jeff Breunsbach
  • Show Website
    The Chief Customer Officer Podcast

You Might Also Like