The Chief Customer Officer Podcast

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

Conversations about digital experience and AI. 

  1. 2d ago

    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

    43 min

  2. 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

    40 min

  3. 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

    31 min

  4. May 21

    EP018 Aim Small, Miss Small: Picking AI Use Cases That Pay Off w/ Neil Erickson

    Neil Erickson, Founder and CEO of Owner Enable and former SVP, Global Platforms at Equifax, joins Jay and Jeff to unpack why so many CS and small business leaders feel stuck with AI. The conversation moves from Jeff's live renewal-automation build to context engineering, token economics, and why fundamentals beat shiny objects. KEY TAKEAWAYS Most teams are less mature than they think: Jay's read of 50 CS leaders — solo operators, constant hallucinations, no shared context, some buying their own Claude licenses.Context is the unlock: Pointing AI at your whole SharePoint produces nonsense. Curate the directory, files, and MCPs you load so agents stay skilled, not polluted.Memory turns reps into shortcuts: Teach the model "next time, use the Playwright MCP" and stop fumbling through 12 iterations on the same task.Aim small, miss small: Pick two or three use cases, put a dollar value on them, then prove feasibility by mapping the exact data the LLM needs.The juice has to be worth the squeeze: Token costs are not dropping. Energy and compute constraints make intelligence a real line item.Renewals are a perfect first target: Jeff is rebuilding his renewal motion with AI-drafted proposals — roughly 20 hours a week back across the team.Information management is the boring work that matters: KISS, clean inputs, governed access, real APIs — table stakes most companies skipped.The great role collapse is here: A dollar of ARR is worth 2–3x, not 10x. Account teams of 10 become teams of 1.5, and AI fluency is the new baseline. ABOUT OUR GUEST Neil Erickson is Founder and CEO of Owner Enable, helping small business owners use AI to make more money and save time by connecting the tools they already have. He's also a Partner at PeerCxO, advising mid-market and PE-backed executives. Neil spent seven years at Equifax, most recently as SVP, Global Platforms, with prior leadership roles at Travelport, IHG, and Starwood. CHAPTERS 00:00 - Welcome and Neil's enterprise background03:52 - Jeff's renewal automation build06:00 - Templated proposals, Playwright, and MCPs13:27 - 50 CS leaders, hopelessness, and missing context17:53 - Context and memory, explained simply22:35 - Why every AI lab is launching services25:00 - Anthropic for small business and the partner gap30:30 - Where to actually start: KISS and information mgmt36:00 - Token costs and the juice vs. the squeeze40:00 - The great role collapse44:21 - New skill sets for an AI-native workforce46:30 - Inside Owner Enable 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

    45 min

  5. May 14

    EP017 Uncommon Circles, Moderation Agents & The Rise of the Forward Deployed Engineer

    Jay and Jeff get into the weeds on two of the biggest questions in CS right now: how to build a community that doesn't devolve into spam and consultant pitches, and how the Forward Deployed Engineer role is reshaping who actually sits in front of customers. Plus what Junction is learning about building a product for agents, not just humans. KEY TAKEAWAYS Charge for the community. Paying members self-filter out the people trying to mine the network for leads and consulting work.Moderation should be agentic. A moderation agent plus a content-curation agent replaces the old volunteer-mod model.Looping knowledge graphs compound. Balboa's "big brain" updates a markdown knowledge base after every call. That corpus gets exponentially more valuable over time.Uncommon Circles. After 60 days, members get matched into a group of five, deliberately diverse on industry and stage.The agent is your end user. If you sell a developer product, the code is being written by Claude. CLIs, MCPs, and clean API docs matter more than slick UI.CSM + FDE, not CSM-as-FDE. Don't commandeer "forward deployed" for CS. CSM owns relationship and commercials; FDE owns the technical solution.Hire FDEs engineering-first. Palantir's formula: 20% sales, 30% product, 50% engineering. Customer-facing polish is last. CHAPTERS 00:00 - Cold open and Omaha memories01:40 - Introducing Uncommon and the May 27th Show & Tell04:55 - The trap of forums and consultant lead-gen06:43 - Why paying for a community actually works08:50 - Moderation and curation agents09:48 - Looping knowledge graphs from Karpathy to Balboa big brain12:40 - Why people really join communities14:15 - Uncommon Circles, matched groups of five17:00 - Bespoke engagement nudges20:18 - Communities for your customers22:11 - The agent is your user now24:07 - The translation layer between APIs and PMs28:24 - Forward Deployed Engineers, Palantir-style30:50 - Why FDEs alone aren't enough32:14 - Hiring an FDE at Junction35:00 - Reporting structure and engineering buy-in37:22 - Scaling the role, engineering-first 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

    38 min

  6. May 7

    EP016: Launching Uncommon

    Jay and Jeff debrief last week's AI Show & Tell — 150 customer leaders watching four real builds in production. A custom CS platform in Claude Code. A sales reference agent. Renewal workflows that adapt to customer health. Plus the launch of Uncommon, a new community for AI-forward customer leaders: https://www.chiefcustomerofficer.io/uncommon Join us live for AI Demo Day on May 27 at 2pm ET: https://luma.com/i3kbo9m2 KEY TAKEAWAYS Build, don't buy: A CS leader stood up her own CS platform in Claude Code in two weeks. Her token costs are already lower than the SaaS subscriptions she replaced.The data layer is the moat: Whether you centralize via a data lake or wire connectors through MCP, your data architecture is the foundation everything else stands on.Every department needs a builder: Instead of departmental software, every team needs an ops person — or a manager — who can build with AI.From soft to hard agents: Most early use cases just surface information. The real lift comes from agents that draft, schedule, and act on your behalf.Renewal workflows that adapt: A 90-day renewal flow that reshuffles tasks based on customer health markers beats any generic checklist.Skills belong at the team level: Stop emailing markdown files around. Treat skills like internal products with owners, evals, and version control.Company-as-code: Balboa OS lives in markdown, distributed via GitHub to OneDrive to every team member's machine. Update once, push to all.Humans are still a moat: Automate the prep, but human relationships and judgment are not getting commoditized any time soon. CHAPTERS 00:00 - Welcome and morning chaos02:32 - Why we ran an AI Show & Tell04:30 - A custom CS platform built in Claude Code08:20 - Data security, privacy, and the engineering layer12:50 - Every department needs an ops person who can build14:52 - The data layer as the real foundation16:50 - An AI-powered sales reference agent19:17 - Jeff's Fathom-to-PlanHat task automation23:54 - A renewal workflow that adapts to health markers27:27 - Skills, coaching, and enterprise-wide sharing30:14 - Balboa OS: turning your company into code33:20 - Why evals matter as models change35:00 - Launching Uncommon for AI-forward CS leaders42:10 - Why "Uncommon"? Bold decisions create the advantage 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

    42 min

  7. Apr 30

    EP015: Why CS Teams Are Building Their Own Stack

    Jay and Jeff swap real examples of building custom AI tools instead of buying software — a $1K brand video that beat $750K agency quotes, a content planner built in 35 minutes, and a renewal digest that surfaces customer context weekly with zero manual effort. Plus: why the CS platform category is stalling, and the difference between a service blueprint and a customer journey. KEY TAKEAWAYS AI collapses the agency middle layer: A CEO got $500K–$750K quotes for a brand video, spent $1K in AI credits instead, and got 70% of what he wanted in a weekend. The agencies only offered 10–20% discounts when asked to use AI themselves. Fewer people = faster output: The Mythical Man-Month principle applied to AI: every person you add to a project adds communication overhead. The real superpower of these tools is reducing the number of people in the middle of a problem. Build your content system, not just content: Jeff built an AI-powered content planner in 35 minutes — 9 posts/week, post-type by day, 40-idea backlog, status tracking, and a draft button that fires his LinkedIn writing skill. MVP in a morning. CS cockpit over CS platform: The question isn't which CS tool to buy — it's whether you can build exactly what your team needs. Jeff's team built a weekly renewal digest from support tickets, emails, Slack, and call recordings in one day. The CS platform category is stalling: The layer of workflows that's truly common across software companies is thinner than vendors want to admit. Domain-specific, product-specific nuance is where the real work lives — and that can't be bought off the shelf. Service blueprint vs. customer journey: Service blueprint = what you need to do to interact with a company. Customer journey = how customers mature and get value. CEOs want to hear about the journey. CSMs need to stop confusing the two. CHAPTERS 00:01 - Raleigh, end of quarter, baby incoming02:43 - $750K agency quote vs. $1K AI video build05:15 - Building exactly what you need: Jay's HubSpot pipeline dashboard07:28 - The Mythical Man-Month and reducing communication layers with AI09:15 - Paying for expertise, not pixel-pushing10:24 - Jeff's AI content planner: built in 35 minutes on Cowork15:56 - How the draft button and LinkedIn skill work together17:46 - Hosting the planner: Cowork vs. Claude Code21:12 - The CS cockpit idea: custom workflow hub for CSM teams24:50 - Junction's interactive onboarding demo environment25:53 - Why the CS platform category is stalling31:41 - Service blueprint vs. customer journey33:28 - Team AI day: CS team builds a weekly renewal digest35:51 - "You just described Staircase AI" — and built it in a day37:44 - Why PlanHat over HubSpot40:59 - Slack account pulse bot: ping for an AI-written account summary 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

    41 min

  8. Apr 23

    EP014 Killing the CSM Role: TAMs, Forward-Deployed Engineers, and more

    Is the CSM role actually dead? Jay and Jeff unpack Chad Hornfeld's viral Avoca post on replacing CSMs with Technical Account Managers and forward-deployed engineers — and what it means for how Jeff is hiring at Junction right now. Plus: Jay's weekend-built HubSpot dashboard, why Claude is winning B2B, and rebuilding onboarding around the patient journey. KEY TAKEAWAYS The CSM role is splitting in two: The emerging model pairs a Technical Account Manager with a forward-deployed engineer. Commercial motion moves elsewhere — deep technical fluency and account growth are hard to do well in one seat.Hire for technical aptitude, not claims: Jeff is screening CSM candidates on what they've actually built with AI and whether they've read Junction's public API docs before the interview. Reciting the tagline is the wrong answer.Onboarding should follow the customer's journey, not the product: Junction is flipping onboarding around the patient journey — mapping when customers should hit specific endpoints to prevent misconfigurations that quietly generate support tickets downstream.Internal apps are replacing dashboards: Jay built a live, two-way HubSpot pipeline dashboard in a weekend with Claude Code — no incremental HubSpot spend, no BI tool. The open question: how do you deploy these safely across a team?Security is still engineering: Roughly 45% of code written by Claude ships with significant security vulnerabilities. A central "AI center of excellence" isn't optional — it's how you put guardrails on what everyone is suddenly building.Claude is winning B2B: Clear naming (Chat, Cowork, Code) maps to different user types, and early investment in Claude Code made it the default for technical work. OpenAI is optimized for B2C scale and running on investment, not flywheel.Jevons Paradox vs. doomerism: Telephone operators vanished — but long-distance unlocked a much bigger economy. Expect AI to open product and engineering roles in non-technical industries that never justified them before. CHAPTERS 00:00 - Kickoff and a Friday AI hackathon03:10 - Building a HubSpot dashboard in Claude Code09:19 - BI tools, security, and Centers of Excellence12:55 - Why Claude is eating the B2B market20:41 - Killing the CSM: Chad Hornfeld, TAMs, and FDEs23:18 - Hiring technically-minded CSMs at Junction26:00 - Solutions engineer vs forward-deployed engineer27:35 - Rebuilding onboarding around a patient journey35:04 - Monthly hackathons and AI show-and-tells 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

    37 min
See All (21)

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
    21
  • Rating
    Clean
  • Copyright
    © 2026 Jay Nathan & Jeff Breunsbach
  • Show Website
    The Chief Customer Officer Podcast

You Might Also Like