Jeff and Jay get honest about where the Chief Customer Officer podcast lost its spark—and what reignited it: a seven-capability framework for post-sale teams that cuts through the roles-and-titles noise. Support, onboarding, adoption, engagement, feedback, renewal, expansion. The fundamentals haven't changed. But how you build for them—and where AI fits in—has everything to do with what kind of CS org you'll have in two years.

KEY TAKEAWAYS

• Capabilities beat titles: Whether you call them CSMs, TAMs, or revenue architects, what matters is which capability is being delivered—not what the role is named.
• AI amplifies, it doesn't shortcut: Jeff's team built an AI triage agent for support tickets using N8N and Claude—but only after mapping the underlying process first.
• CS is a cross-functional sport: Feedback loops involve product. Renewals involve finance. Onboarding involves engineering. The seven-capability frame makes it easier to pull other teams in.
• Customer journey ≠ your operational blueprint: Jay's key distinction: your internal capabilities are levers you control; the customer's maturity journey is theirs to own.
• Roles aren't disappearing: Gong now calls theirs "revenue architects." But support, onboarding, and expansion still need owners—the work hasn't gone away.
• Frank Slootman's warning: At Snowflake, he refused to name any team "customer success"—so every team stays accountable. It's a brilliant structural insight.
• CCO is looking for its next leader: Jeff and Jay want a young, energetic operator to help run this media company. Reach out if that's you.

CHAPTERS

• 00:00 - What is this podcast even called?
• 01:08 - Why the podcast lost its spark
• 03:06 - Rebuilding for CS leaders in the AI era
• 08:20 - The 7 core capabilities framework
• 14:39 - Capabilities vs. titles: the real shift
• 18:20 - Comparing to Wayne McCulloch's Seven Pillars
• 21:18 - Customer journey vs. operational blueprint
• 25:04 - Feedback loops and cross-functional ownership
• 27:14 - Frank Slootman on CS accountability
• 30:43 - How Gong reinvented their post-sale team
• 33:29 - Guests, consistency, and podcast format
• 35:23 - What's next: newsletter, community, and AI

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

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

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 email
• 02:46 - Meet Mr. Baxter: building an AI COO for the household
• 07:17 - Why personal agents preview enterprise AI strategy
• 14:45 - Three priorities: human relationships, killing process, more joy
• 22:38 - The $10B forward-deployed engineer boom
• 30:03 - Pairing business operators with FDEs to close the last mile
• 34:23 - Early adopters, intelligence sovereignty, and open source catching up
• 41: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.io
• Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

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 Charleston
• 01:30 - Enterprise AI Adoption Barriers
• 04:45 - Single-Player vs. Multiplayer AI
• 07:15 - Zapier Bans DMs: Building AI Context in Slack
• 11:30 - Building the Balboa Brain
• 19:00 - From Files to a Vectorized Database
• 23:00 - What Are Agents, Really?
• 26:00 - Forward Deployed Engineers: $7.5B Bet
• 30:00 - Amazon's 45-45-45 Methodology
• 37:00 - Less Software, Better Outcomes
• 41:00 - DesignJoy and the One-Person FDE Model
• 44:00 - James Clear's Systems Quote
• 45:30 - Teaching Non-Technical People to Use AI
• 47:00 - Personal AI Fitness Coaches & NanoClaw
• 50:30 - Cal AI's $30M Exit and the Hack

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

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-in
• 02:35 - The PRD idea: vibe coding needs structure
• 05:59 - Vibe coding vs. production-ready engineering
• 08:00 - Single player AI vs. enterprise multiplayer
• 10:11 - MCP vs. curated data layers
• 15:12 - Master customer data files and token efficiency
• 18:25 - Jeff's PRD skill in action
• 20:57 - Generating tasks from the PRD
• 25:20 - How enterprises are structuring AI teams
• 33:29 - ClickUp's foundry model
• 36:36 - Why infrastructure beats individual token spend
• 39:18 - The ROI problem with AI investment
• 40:42 - AI-native services: selling outcomes
• 43: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.io
• Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

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 update
• 02:30 - kickbacks.ai: the VS Code ad hack
• 09:00 - Attention is the moat, not the tech
• 12:00 - Claude Cowork as a paternity leave to-do list
• 16:30 - The AI slop problem hitting leadership inboxes
• 19:00 - The CSM hiring fingerprints test
• 21:30 - The Minto Pyramid as a team skill
• 25:00 - True personalization vs. segmentation
• 28:30 - Jeff's Linear task ingestion agent
• 31:00 - Jay's Agent Command Center at Balboa
• 37:00 - Build vs. buy: why they went custom
• 39:30 - Models as commodities, harness layer as moat
• 43:30 - Keeping AI momentum inside your team
• 46: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.io
• Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

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 coming
• 00:53 - NanoClaw: Secure open-source personal agents
• 03:47 - Meet Maverick, Jay's AI podcast producer
• 05:11 - Agent sprawl and the containment problem
• 06:20 - Building a team-level agent command center
• 13:44 - Token costs, Jevons' paradox & model matching
• 17:07 - Data centers, energy, and the physical bottleneck
• 20:44 - How to roll AI out to teams (the Canva lesson)
• 22:58 - Verified data sets: Why trust and efficiency go together
• 35:02 - Sierra AI: $15.8B valuation, 100x revenue
• 38:35 - AI in customer support: Back-end before front-end
• 41:16 - ClickUp layoffs and the 10x vs. 100x mindset
• 42: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.io
• Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

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 Watch
• 01:20 - Welcome Jack Nathan
• 02:14 - Uncommon Community Update
• 06:17 - Building with Claude Code Over the Weekend
• 08:54 - Linear Integration & AI-Powered Project Management
• 12:00 - Community Members Contributing via PRs
• 14:02 - Spencer's Automated Feature Request Pipeline
• 16:45 - N8N: Customer Quotes & Product Feedback Automations
• 21:47 - Uncommon Launch Date Discussion
• 24:12 - Gainsight Pulse & Atlas: Retention-as-a-Service
• 31:51 - Decentralized Work & Company as Code
• 39:20 - Coinbase's Org Collapse & the Player-Coach Model
• 43:49 - The CS Leader Moment We Were Made For
• 44: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.io
• Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

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 Overview
• 01:56 - What Is an AI Native Services Company?
• 03:43 - The AI-Native Recruiting Firm Example
• 08:10 - Where Emergence Gets It Right: Domain Credibility
• 09:41 - Mirage Product-Market Fit
• 11:14 - Outcome-Based Pricing
• 13:11 - Pushback: The VC Framing Problem
• 15:40 - Pushback: Don't Switch Pilot Teams
• 17:28 - Pushback: The Product Development Trap
• 19:47 - The Vertical Ecosystem Advantage
• 23:30 - Connecting AI Native Services to Customer Success
• 26:02 - The AI Recruiting Firm in 2026: What's Automated Now
• 28: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.io
• Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

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 background
• 03:52 - Jeff's renewal automation build
• 06:00 - Templated proposals, Playwright, and MCPs
• 13:27 - 50 CS leaders, hopelessness, and missing context
• 17:53 - Context and memory, explained simply
• 22:35 - Why every AI lab is launching services
• 25:00 - Anthropic for small business and the partner gap
• 30:30 - Where to actually start: KISS and information mgmt
• 36:00 - Token costs and the juice vs. the squeeze
• 40:00 - The great role collapse
• 44:21 - New skill sets for an AI-native workforce
• 46: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.io
• Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io