KEY TAKEAWAYS

• Segment before you strategize: Product attachment, lifecycle stage, engagement model, health status — four inputs, and every row of the grid is a real situation to solve.
• Managed vs. scaled: Either an account has a named human or it doesn't. Pick the threshold, then design both sides.
• Red/yellow/green, not a health score: Sponsor, usage, sentiment, billing. One turns yellow, the account turns yellow — and you know what to go fix.
• Business requirements before playbooks: Ask leaders what should happen in each segment, not which system does it. Tools execute a plan; they don't replace one.
• Why CS platform deployments fail: The grid was never filled out. Teams buy a product hoping to get a strategy.
• Strategy is putting things in buckets: Rumelt's diagnosis, guiding policy, coherent action — one segment at a time. "Not strategic" usually means working hard without buckets.
• Bumpers, not scripts: A playbook keeps people in the lane. Word-for-word scripts belong in a contact center, not on the front line.
• Simple travels: The bigger the team, the worse the game of telephone. Simple to communicate is what actually spreads.
• Make the customer voice watchable: Jeff swapped text quotes in Slack for links to the recording — and the whole business started listening.
• Get executives back in the room: Exec sponsors, ride-alongs, 50 calls in 50 days. CFOs are the best execs to put on a customer call.

CHAPTERS

• 00:00 - Apex habits and why consistency compounds
• 03:23 - Jeff cheats on Claude and tries Codex
• 06:04 - Model vs. harness: the real lock-in problem
• 08:02 - Why enterprises can't move at personal-project speed
• 10:53 - 87 out of 100 people have never touched AI
• 11:44 - The skills AI doesn't replace: trust, transparency, relationships
• 12:39 - Turning customer quotes into watchable clips
• 14:29 - Ride-alongs, exec sponsors, and 50 calls in 50 days
• 18:51 - Inside the segmentation workshop
• 21:07 - Engagement model and the red/yellow/green grid
• 23:33 - Business requirements before playbooks
• 27:35 - Bumpers on a bowling lane, not word-for-word scripts
• 33:02 - Segmentation as a microcosm of strategy
• 37:25 - Why CS platform deployments fail

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

KEY TAKEAWAYS

• Design for agents, not humans: Stop forcing your knowledge into Notion or databases. Build in markdown files on GitHub—agents work natively on file structures, and your team gets a custom UI on top.
• The self-updating wiki: Three agents (writer, reviewer, verifier) continuously maintain your knowledge base by listening to Slack, support tickets, and email—so humans stop doing the updating.
• Build a learning loop: Jay logs what he edits vs. what the AI wrote, and the agent learns from the diff. That's the difference between a task tool and one that gets continuously smarter.
• One wiki powers everything: A live internal wiki can drive your CSM academy, customer-facing docs, and onboarding—without a dedicated writer for each output.
• The bottleneck has moved: AI eliminated engineering as the constraint. Now go-to-market teams and customers can't keep up with what's shipping. That's the new problem to solve.
• Feature velocity ≠ value: Shipping more faster can increase churn if customers can't absorb it and build an internal ROI story.
• Map usage to the P&L: Jay's framework—leading indicator → lagging indicator → KPI—connects product usage to financial outcomes a CFO can see.
• Pricing model literacy: The shift from seat-based to consumption or outcome-based pricing has real gross profit and AI inference cost implications CS leaders must understand.

CHAPTERS

• 00:00 - Welcome & Jay's CCO Summit trip to Boston
• 01:30 - Why in-person still matters for team chemistry
• 03:00 - Launching Uncommon community + vector databases
• 05:30 - The Claude-built CSM training academy
• 08:00 - Agent learning loops: the lessons-learned file
• 09:30 - The Karpathy-inspired agent-first internal wiki
• 13:00 - Designing for agents, not humans
• 15:30 - The autonomous CRM vision
• 17:00 - One wiki powering the whole org downstream
• 20:00 - Jobs aren't disappearing—they're shifting
• 21:00 - P&L literacy gap at the CCO Summit
• 24:00 - The new bottleneck: go-to-market teams
• 26:00 - Feature velocity vs. the 1-degree problem
• 29:00 - Teaser: consumption vs. outcome-based pricing
• 32:00 - Jay's leading → lagging → KPI framework

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

KEY TAKEAWAYS

• Think critically before copying Palantir: Their FDEs are deep AI engineers on eight-figure deals with no real competition—not relabeled CSMs or sales engineers.
• Match the motion to the deal size: Eight-figure deals can afford dedicated FDEs. Everyone else should use engineering capacity to build tooling that scales.
• Deploy engineers against onboarding first: Jeff's solutions engineer sits in CS, aiming to cut five days off onboarding—and reach revenue faster.
• Optimize for time to first result: Architect onboarding around the first core outcome instead of throwing the whole platform at customers.
• Async agents can replace the validation call: A Slack agent validates contract and configuration details before kickoff, so the first meeting starts from momentum.
• Map the process before adding AI: A Google Sheet and Figma board came first. Once mapped, it's obvious where AI fits.
• The job today isn't the job in twelve months: Both hosts now say this in interviews—hire people who want to build the plane while flying it.
• Give the team an outlet to flag work that shouldn't exist: Turn "I shouldn't be doing this" into a cataloged, prioritizable ticket—then solve one thing per quarter.

CHAPTERS

• 00:00 - Charleston heat and offsite season
• 01:09 - The forward deployed engineer hype, revisited
• 02:08 - Why Palantir's FDE model doesn't map to your business
• 05:20 - Getting ingrained in the customer's business
• 07:12 - Cutting a week off onboarding with a deployed solutions engineer
• 12:39 - Time to first result over throwing everything at customers
• 13:34 - The onboarding agent and AI-first delivery at Balboa
• 16:17 - Google Sheets, Figma boards, and mapping before automating
• 20:00 - Blending AI into the service blueprint
• 21:10 - "The job today isn't the job in twelve months"
• 25:27 - Vision setting, rally cries, and the Kennedy moon speech
• 29:00 - The Wayne McCulloch open-document vision exercise
• 30:06 - Cataloging work your team shouldn't be doing
• 36:56 - Working Genius, activators, and galvanizers
• 38:12 - Community, Vistage, and relaunching Uncommon

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

KEY TAKEAWAYS

• Five Buckets: Jeff's team sorted last week's activities into keep/start/automate/delegate/cut. Only a small share landed in "keep it"—50-60% moved elsewhere.
• The Defensiveness Trap: CS teams over-claim "keep it" because giving something up feels like losing relevance. Anchoring to revenue cuts through that.
• Reverse Roadmap Reviews: Ask customers to share their roadmap instead of presenting yours. It surfaces product gaps and becomes a repeatable leading indicator.
• Cut the Check-In Call: Jeff's team is targeting a 50% cut of recurring check-ins that drifted into habit. Fix: give every call a purpose, start date, and end date.
• Field-Level Understanding: Palantir's "agent camp" echoes an old FLU playbook from Jay's consulting days—both build pre-sale conviction by mapping use cases with buyers.
• Pendulum Swings Back to Deterministic: Agent platforms are exciting, but many workflows need to run the same way every time—the win is blending agent judgment with deterministic code.
• Forecast Risk in Automation: An agent auto-moving a deal stage introduces risk into something reps must stand behind. Some steps still need a human check.
• Buzz as an Agent Harness: Jeff's self-hosting Block's open-source Buzz, where every channel is an agent he and Jay shape together—podcast producer, newsletter agent, and a content manager orchestrating both.

ABOUT 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

CHAPTERS

• [00:01] - Intro and the CS team offsite
• [00:49] - The keep/start/automate/delegate/cut exercise
• [03:20] - Anchoring the exercise to revenue
• [04:41] - The change management payoff for the team
• [06:34] - Reverse roadmap reviews as a leading indicator
• [09:58] - The goal: cut 50% of check-in calls
• [12:37] - Transition calls and giving check-ins a purpose
• [14:57] - FLU and Palantir's agent camp model
• [18:31] - Why AI adoption stalls at the enterprise level
• [19:27] - Single-player vs. multiplayer agent platforms
• [22:35] - The pendulum swings back to deterministic workflows
• [25:57] - Forecast risk when agents move deal stages
• [27:11] - The missing embedded product manager
• [30:20] - Buzz: a self-hosted agent messaging harness
• [33:51] - Standing up a podcast producer and content manager agent
• [36:32] - Turning call transcripts into a customer quotes channel

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.

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

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

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

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

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

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

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

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

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

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

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 memories
• 01:40 - Introducing Uncommon and the May 27th Show & Tell
• 04:55 - The trap of forums and consultant lead-gen
• 06:43 - Why paying for a community actually works
• 08:50 - Moderation and curation agents
• 09:48 - Looping knowledge graphs from Karpathy to Balboa big brain
• 12:40 - Why people really join communities
• 14:15 - Uncommon Circles, matched groups of five
• 17:00 - Bespoke engagement nudges
• 20:18 - Communities for your customers
• 22:11 - The agent is your user now
• 24:07 - The translation layer between APIs and PMs
• 28:24 - Forward Deployed Engineers, Palantir-style
• 30:50 - Why FDEs alone aren't enough
• 32:14 - Hiring an FDE at Junction
• 35:00 - Reporting structure and engineering buy-in
• 37: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.io
• Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

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 chaos
• 02:32 - Why we ran an AI Show & Tell
• 04:30 - A custom CS platform built in Claude Code
• 08:20 - Data security, privacy, and the engineering layer
• 12:50 - Every department needs an ops person who can build
• 14:52 - The data layer as the real foundation
• 16:50 - An AI-powered sales reference agent
• 19:17 - Jeff's Fathom-to-PlanHat task automation
• 23:54 - A renewal workflow that adapts to health markers
• 27:27 - Skills, coaching, and enterprise-wide sharing
• 30:14 - Balboa OS: turning your company into code
• 33:20 - Why evals matter as models change
• 35:00 - Launching Uncommon for AI-forward CS leaders
• 42: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.io
• Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

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 incoming
• 02:43 - $750K agency quote vs. $1K AI video build
• 05:15 - Building exactly what you need: Jay's HubSpot pipeline dashboard
• 07:28 - The Mythical Man-Month and reducing communication layers with AI
• 09:15 - Paying for expertise, not pixel-pushing
• 10:24 - Jeff's AI content planner: built in 35 minutes on Cowork
• 15:56 - How the draft button and LinkedIn skill work together
• 17:46 - Hosting the planner: Cowork vs. Claude Code
• 21:12 - The CS cockpit idea: custom workflow hub for CSM teams
• 24:50 - Junction's interactive onboarding demo environment
• 25:53 - Why the CS platform category is stalling
• 31:41 - Service blueprint vs. customer journey
• 33:28 - Team AI day: CS team builds a weekly renewal digest
• 35:51 - "You just described Staircase AI" — and built it in a day
• 37:44 - Why PlanHat over HubSpot
• 40: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.io
• Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

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 hackathon
• 03:10 - Building a HubSpot dashboard in Claude Code
• 09:19 - BI tools, security, and Centers of Excellence
• 12:55 - Why Claude is eating the B2B market
• 20:41 - Killing the CSM: Chad Hornfeld, TAMs, and FDEs
• 23:18 - Hiring technically-minded CSMs at Junction
• 26:00 - Solutions engineer vs forward-deployed engineer
• 27:35 - Rebuilding onboarding around a patient journey
• 35: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.io
• Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

KEY TAKEAWAYS

- Call Intelligence Over Raw Transcripts: The real value comes from extracting transcripts into a structured, security-layered database with semantic search—so the entire team can query insights across all conversations, not just their own.
- The Context Harness Problem: Giving everyone Claude or ChatGPT isn’t enough. Without a centralized context repository, every team member operates in isolation. The winners are building shared knowledge infrastructure.
- Balboa OS: A central folder of Markdown files documenting everything—roles, processes, the employee handbook, team roster. It auto-distributes to every teammate and connects to Claude via Claude Cowork.
- Autonomous Agents That Self-Improve: Jay has an agent scanning call transcripts to update skills, surface best practices, and build a company wiki from thousands of calls—without anyone having to write a document.
- CSM Ratios Are Breaking: Companies are drawing lines at $100K–$250K ARR before assigning a dedicated CSM. The answer is digital CS and one-to-many engagement models that scale what CSMs know.
- The Agentic CX Loop: Leading teams are building autonomous loops that sense signals, decide on actions, execute, and learn—continuously improving how they engage customers without manual intervention.
- Data Mess Is the Real NRR Problem: At Pendo’s conference, nearly every SaaS leader said the same thing: our data is a mess. A simple product tenant-to-CRM mapping would put 90% of companies in a fundamentally better position.
- Onboarding Still Wins Retention: Jay’s team helped a $300M company improve retention over 10 points just by fixing a broken onboarding program. With consumption-based models, activation is now a direct revenue trigger.

CHAPTERS

- 00:00 - Intro (solo episode, Jeff on vacation)
- 01:27 - The Balboa call intelligence system
- 06:34 - MCP server and centralizing AI context for the team
- 08:06 - Claude skills + call data in practice
- 09:22 - Autonomous agents and the self-improving wiki
- 11:21 - Balboa OS: the company operating system
- 16:50 - 90 days of SaaS industry insights
- 17:34 - Theme 1: CSM ratios are broken
- 20:54 - Theme 2: AI sidekick vs. AI agent
- 21:45 - The autonomous agentic customer journey loop
- 24:12 - Theme 3: Data mess as the core NRR limiter
- 29:36 - Theme 4: Onboarding as the highest-leverage retention moment
- 30:08 - The $300M onboarding case study
- 35:06 - Wrap-up and Pulse conference

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

She shares how they did it, what went wrong when their AI agent Harper made promises it couldn't keep, and why the real value of AI isn't cost-cutting — it's creativity that was never possible before.

KEY TAKEAWAYS

• Build vs. buy is a real question: Off-the-shelf tools were bloated with features they didn't need and missing the ones they did — building from scratch gave them full control at lower cost.
• Start with one small thing: The chatbot led to the ticketing system, which led to email automation. One use case compounds into the next.
• Guardrails are the hardest part: Their agent Harper promised customers she could cancel orders — she couldn't. Too few guardrails and AI goes rogue; too many and you've just built a robot.
• AI enables proactive CX: With 50,000 orders/week, proactive outreach was impossible before. Now they're building toward monitoring every order and surfacing problems before customers call.
• Insight without action is noise: Aurelia doesn't want to be the "Chief Complaint Officer." Her job is to tie customer insights to company strategy and act — not just report.
• Maintaining AI is a full-time job: Agents need ongoing updates just like human employees — new policies, new products, new questions. The build is the easy part.

ABOUT OUR GUEST

Aurelia Pollet is the VP of Customer Experience at CarParts.com, a publicly traded e-commerce retailer shipping ~50,000 orders/week. A mechanical engineer by training, she spent 15 years in luxury goods before moving through B2B and nonprofit roles. She led CarParts.com's AI-native rebuild of its entire support infrastructure. Connect with Aurelia on LinkedIn

CHAPTERS

• 03:46 - Welcome and introduction
• 05:42 - Aurelia's background: from mechanical engineer to VP of CX
• 07:05 - What "end-to-end CX" means at CarParts.com
• 10:09 - Adding value at scale: the win-win framework
• 12:26 - Building an AI chatbot from scratch in 3 months
• 14:34 - From chatbot to full AI ticketing system
• 16:51 - How AI frees humans for empathy and complex cases
• 20:08 - Gathering customer insight across the journey
• 24:50 - Insight as action (avoiding the "Chief Complaint Officer" trap)
• 26:50 - The build vs. buy decision
• 32:57 - Hard lessons: Harper's promises and the guardrail problem
• 38:54 - What's next: stabilizing and scaling the AI stack
• 43:23 - Advice for leaders who haven't started yet

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 shares fresh takeaways from a Planhat-organized event in Boston, and Jay goes deep on the Claude skills his team has built to scale coaching, standardize deliverables, and rethink how prep calls even work. No hype, just real strategies in the field.

KEY TAKEAWAYS

• We're still in early adopter territory: Jeff attended an event with 60 CS leaders and walked away realizing that even among leaders who talk about AI daily, widespread team adoption is far behind what the tech echo chamber suggests. The majority of companies are still evaluating — not executing.
• You don't know your processes as well as you think: Before you can automate or augment a workflow with AI, you have to actually know what that workflow is. Jay and Jeff agree: most teams haven't documented or visualized their core processes, which is the real bottleneck to AI leverage.
• Top-down mandates don't drive AI adoption: "Just use AI" from the CEO doesn't work. Real adoption requires demonstrating behaviors at every layer of the org, giving teams specific problems to focus on, and creating regular show-and-tell moments where people can see and iterate on each other's work.
• Call transcripts are your most underutilized asset: Jay calls Fathom call recordings "the most valuable thing we have in our company."
• Claude skills as a team force multiplier: Jay built an executive readout coaching skill in Claude that replicates his own feedback patterns, so every team member starts their deck review at a higher baseline.
• The future CSM is a technical account manager: Multiple CS leaders at Jeff's event flagged this shift — the CSM role is evolving toward one that requires real technical curiosity.
• Forward deployed engineering is closer than you think: Jay makes the case that giving CSMs a local build of your product — and the ability to generate a feature-based pull request from a customer conversation — is entirely possible today.
• Build a center of excellence, not just a mandate: Sustainable AI adoption at the team level needs a few dedicated people vetting standard tools, scheduling engagement touchpoints, and measuring outcomes — not just an org-wide Slack message to "go use AI."

CHAPTERS

• 00:00 - Intro & Jay's flight back from Seattle
• 01:29 - Jeff's takeaways from a Planhat AI event in Boston
• 03:15 - Crossing the chasm: where is AI adoption actually at?
• 06:59 - We don't know our processes as well as we think
• 09:21 - Driving team-wide AI adoption: what actually works
• 11:43 - Measuring AI impact: KPIs and the multi-attribution problem
• 17:47 - Individual vs. team AI adoption — why standardization matters
• 18:39 - Jay's executive readout coaching skill in Claude
• 22:52 - Jeff's product marketing skill: Notion to branded one-pager
• 26:28 - Call transcripts as the ultimate knowledge source
• 27:15 - Automating product feedback with Fathom + Linear PRDs
• 29:42 - Forward deployed engineering and voice of customer at scale
• 33:28 - The future CSM is technically fluent
• 35:07 - What to look for when hiring CSMs right now
• 39:17 - Building a center of excellence for AI adoption
• 42:00 - Jay's website glossary and partner portal (show & tell)
• 46:08 - Wrap up

Plus: Jay introduces "Company as Code," a markdown-in-GitHub system for building personalized outreach and landing pages at scale — and why the same playbook applies directly to customer success.

KEY TAKEAWAYS

• Start with a customer master record: Before any AI agent can help you, you need a deduplicated view of your customer outside your CRM. Jay spoke with companies from 150 to 3,500 people this week — they all have the same problem.
• Company as Code: Jay is documenting personas, ICP definitions, and outreach styles as markdown files in a GitHub repo — one canonical version that every AI tool pulls from, updated by anyone on the team via pull request.
• Siloed AI = siloed data with a new wrapper: If your sales AI only sees sales data and CS's AI only sees CS data, you've rebuilt your silos with an AI layer on top. Fix the data first.
• Personalization is now just token costs: Custom landing pages, personalized emails, interactive surveys — what used to require massive investment is now a few tokens.
• Existing customers need outbound too: Just because someone's a customer doesn't mean they understand your product. Use the same personalization playbook to re-engage and educate your base.
• ABM belongs in Customer Success: Jay shares the "Spreading the FLU" story — a field-level understanding program that educated every influencer at top accounts. CS teams should run the same play.
• AI-powered upsell prioritization: Use Fathom recordings, emails, and Slack signals to surface the top 10–20 customers most ready for a new product — before sending a rep in cold.
• The CSP question is getting louder: "It's 2026. Do you need a customer success platform anymore?" Jay is hosting a webinar with two practitioners who built in opposite directions.

CHAPTERS

• 00:01 - Weekend updates
• 03:45 - Unifying customer data at Junction with BigQuery and Metabase
• 07:00 - Building a customer master record outside your CRM
• 10:10 - Why siloed AI is just siloed data with a new wrapper
• 11:48 - Company as Code: markdown files in GitHub as a single source of truth
• 14:45 - Personalized landing pages for prospects — and customers
• 19:00 - The risk side: when custom-built tools fall short
• 23:45 - Using Claude Cowork to research private companies via public comparables
• 27:00 - Applying outbound personalization to your existing customer base
• 29:00 - AI-powered upsell prioritization using call recordings and signals
• 33:00 - Spreading the FLU: account-based marketing applied to CS
• 35:00 - QPR as an interactive landing page for top accounts
• 36:45 - Webinar preview: Do you still need a CSP in 2026?

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

KEY TAKEAWAYS

• Prove you're AI-first before the interview: The best candidates aren't submitting resumes — they're building things. A candidate for Jay's team built an app in Lovable and sent it unprompted. That's how you get noticed. Loom videos, written walkthroughs, anything that shows you've done the work.
• Centralize AI where it touches systems of record; let everything else run organically: MCP-connected tools that touch your CRM or customer data need governance and controls. Departmental tools like Gamma don't. The mistake is treating all AI adoption the same.
• The three go-to-market AI mistakes: Automating bad processes at scale, building on generic best practices instead of your own call data, and prioritizing internal efficiency over the buyer experience. These aren't new problems — AI just makes them impossible to ignore.
• Know which quadrant you're in: Jay's AI Vulnerability Matrix maps companies by solution complexity vs. replicability. Sitting ducks (low complexity, easy to replicate) need to move fast. Fortresses (high complexity, hard to replicate) have time. Knowing your quadrant should drive your entire strategy.
• The $700K ARR per employee benchmark: AI-native companies are hitting $700K–$1M+ ARR per employee. The old benchmark was ~$200K. If you're still staffing like it's 2019, a competitor is already disrupting you.
• Humans stay in the CS loop — but the role changes: Agent-to-agent purchasing will happen first for simple products. For complex enterprise software, the relationship still matters. But the job shifts: less task management, more being so embedded in the customer's business that you know their next move before they do.

CHAPTERS

• 00:01 - Welcome + why Balboa runs a February fiscal year
• 02:34 - The job candidate who built an app to stand out
• 04:16 - Three ways to prove you're AI-first as a candidate
• 09:01 - Kyle Norton: centralize AI adoption or let it happen organically?
• 12:16 - Why you need both — and Jay's internal AI show-and-tell at Balboa
• 17:53 - Kyle Lacy's three go-to-market AI mistakes
• 21:50 - Your call recordings are your best practices
• 23:27 - Jay builds the AI Vulnerability Matrix live on the call
• 25:32 - The four quadrants: sitting ducks, protected niches, targets, fortresses
• 33:19 - What AI-first companies actually look like (Jason Lemkin)
• 35:00 - The shift from CSM to forward deployed engineer
• 36:12 - The $700K ARR per employee benchmark
• 36:40 - Jeff's counterpoint: humans stay in the buying loop longer than we think
• 41:15 - Agent-to-agent PLG is already happening
• 45:54 - 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

KEY TAKEAWAYS

• AI layoffs are mostly "air cover": The Block cuts are less about AI replacing workers and more about correcting COVID-era over-hiring. Companies are using AI as PR cover for reductions that should have happened years ago.
• MCPs are the new API layer for CS teams: MCP servers let leaders query and update tools like HubSpot and PlanHat in plain English — no developer required. Jeff rebuilt his entire field mapping strategy between two platforms in a single Sunday afternoon using Claude Cowork.
• AI deal staging removes subjectivity from the pipeline: By running Fathom call transcripts through an AI model with defined stage criteria, Jeff's team gets consistent deal staging — notes, next action, and stage movement all updated automatically. CSMs validate rather than enter.
• You can build a renewal pipeline from scratch in an afternoon: Jeff used Claude Cowork and the HubSpot MCP to auto-generate hundreds of renewal records with ARR, products, and close dates — work that would have taken weeks manually.
• SaaS incumbents need a self-disruption pricing strategy: If AI is driving down the cost to build software, someone will undercut you on price. The winners will do it to themselves first — like Adobe's "swallowing the fish" move to SaaS. Your gross margin is someone else's opportunity.
• Customer journey ≠ service blueprint: The service blueprint is how you deliver your service. The customer journey is the customer's path to value — change management, adoption, transformation. Keeping them separate is the future of CS platform design.

CHAPTERS

• 00:01 - Welcome and personal updates
• 02:32 - Block's 4,000 layoffs: AI as cause or air cover?
• 07:32 - Small nimble teams and the Jack Dorsey thesis
• 09:00 - MCPs explained: querying HubSpot and PlanHat in plain English
• 15:27 - Token costs and natural language as the new interface
• 17:08 - Jay's SaaS self-disruption pricing thesis
• 22:39 - M&A in the AI era and the Palo Alto Networks acquisition playbook
• 27:12 - Jeff's AI build: deal staging from call transcripts via Fathom and PlanHat
• 32:37 - Creating hundreds of renewal records in one afternoon with Claude Cowork
• 39:41 - Customer journey vs. service blueprint — the clearest definition yet
• 42:10 - Wrap-up and preview of an upcoming guest

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

Jon argues that the law department's job isn't to say no — it's to pave the road so the business can move fast.

Then the conversation turns to AI: how Blackbaud built an AI council to accelerate adoption, why law is uniquely suited for disruption by LLMs, and what it looks like when AI stops being a cost-saver and starts driving top-line revenue.

KEY TAKEAWAYS

• Law is a revenue function: Jon reframes what legal teams are for — not compliance gatekeepers, but deal enablers whose job is to help the business move forward. If there's no revenue, every other legal issue becomes irrelevant.
• The "ultimate backstage pass": Legal touches 80–90% of company accomplishments every quarter — commercial deals, international expansion, M&A, partnerships. That cross-functional visibility makes CLOs uniquely positioned to see the whole business.
• Say "yes, but" not "no": Jon coaches his team to never just say no. Instead, surface the risks, propose a path forward, and find the creative structure that gets the deal done. The Uber example: every legal concern was real, but the right answer wasn't "stick with taxis."
• The Minto Pyramid in practice: Jeff shares a communication framework — lead with the conclusion (what the customer wants), then support it. Jon applies the same inverted pyramid when coaching law students: state your position first, then build the argument underneath. Both are fighting the instinct to bury the lead.
• Blackbaud's AI council as a speed accelerator: When ChatGPT arrived, Blackbaud didn't lock AI down — they built a structured intake process. The result: use cases flow in faster, cross-functional ideas get shared, and the company moves more rapidly because guardrails are clear.
• AI in law today vs. tomorrow: Today, AI can redline a 100-page contract against a standard playbook in 2–3 minutes instead of hours. Tomorrow, it will analyze thousands of historical contracts, surface negotiation patterns, and flag when a jurisdiction is no longer favorable — moving from paralegal to institutional memory to expert system.
• AI's real P&L opportunity is top-line, not just cost savings: Most companies are capturing efficiency gains. The bigger prize is revenue growth — using AI to find underpriced customers, tailor offerings, enable dynamic pricing, and unlock new value from existing contract data.
• Jevons Paradox and AI: New technology creates more demand, not less. The calculator didn't reduce accountants — there are more now than ever. Jon believes AI will expand productivity, create new categories of work, and ultimately generate more jobs, even as individual tasks get automated.

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

Just a real conversation about what they've each been building with Claude Code and Claude Cowork over the past few weeks, and what it's revealing about the future of software, teams, and CS.

Plus a take on Jason Lemkin's SaaS doom post — and why they're not totally buying the narrative.

KEY TAKEAWAYS

• Get Hands-On or You Won't Get It: If you're in a leadership role and not personally using AI tools like Claude Code or Cursor, you're not fully grasping what's happening right now. Pay the $150 for a month. Just do it.
• Enabling Your Team Is a Different Problem: Discovering an AI tool, getting excited about it, then "schlepping it over the fence" to your team isn't enabling them — it's abdicating. Change management still applies. Help them get on the curve.
• Established SaaS Companies Aren't Dead: Brand trust, enterprise security certifications, and multi-year contracts with durable cash flow give companies like Salesforce and Workday real staying power. The question is whether they'll actually act on it.
• Point Solutions Are Most at Risk: CFOs will start asking whether they need a $40K screen recording tool when it can be vibe-coded in an afternoon. Systems of record with billing, forecasting, and compliance dependencies are much harder to rip out.
• The Juice Is Now Worth the Squeeze: AI lets teams do things they always wanted to do but couldn't justify. Jay built an interactive RACI builder and a conversational applicant tracking system — on a weekend, without writing a line of code.
• It's a Context Problem: The real moat isn't the AI model — it's who can pull together all the Slack threads, call transcripts, emails, and product usage data into one accessible place. That's where the advantage lives.
• Skills Democratize Expertise Across the Team: When any CSM can run the product marketing skill and generate a feature guide on their own, you've removed a bottleneck — not a person. Speed compounds when the whole team can move.
• Token Costs Need a Line Item in Your Budget: Some engineering teams are already capping AI spend at $100K per engineer per year.

CHAPTERS

• 00:00 - Intro and technical issues
• 00:09 - Getting hands-on with AI: why leadership can't just delegate it
• 02:48 - The SaaS market landscape: Jason Lemkin's take
• 08:36 - Why established SaaS companies still have real advantages
• 12:09 - Point solutions at risk; systems of record are defensible
• 16:17 - Jeff's product marketing skill in Claude Cowork
• 20:29 - Democratizing documentation: any CSM can now create the guide
• 22:48 - Feeding source code as context; building a chatbot on your own codebase
• 25:28 - QPR, playbook, and onboarding skill ideas
• 27:19 - Managing token costs and what it means for team budgets
• 28:38 - Jay's interactive RACI builder built with Claude Code
• 34:20 - Balboa GPT: client-contextual AI with shared conversation history

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

In this episode, Justin Chappell, Head of Digital Strategy at OneTrust, breaks down the evolution of customer success from reactive firefighting to predictive, AI-powered engagement. Whether you're building your first digital CS motion or looking to integrate AI agents into your customer journey, this conversation offers actionable insights.

KEY TAKEAWAYS

• The CS Evolution Framework: Why moving from reactive → proactive → predictive requires fundamentally different thinking (and why proactive is closer to reactive than you might think)
• The 3 Pillars of World-Class Digital CX: Personalized, Predictive, and Digital-First—and how to operationalize each
• Dirty Data Isn't a Blocker: How predictive models can actually help you identify which data matters while learning from what's usable
• The Power of Simply Asking: Why the best renewal signal is giving customers three options—Yes, No, or Undecided—and how to act on each
• Onboarding That Works: The pilot process that cut first-time-to-value from 44 days to 8 days (and the customer feedback that made it possible)
• The Future CS Team Structure: New roles like AI Architect, Knowledge & AI Readiness Specialist, and Business Value Architect
• Monetizing Customer Success: How success packages create recurring revenue while delivering differentiated experiences

ABOUT OUR GUEST

Justin Chappell is the Head of Digital Strategy at OneTrust, where he oversees digital customer experience for 93% of the company's customer base. He's known for keeping things simple and saying what others are thinking.

Connect with Justin on LinkedIn

CHAPTERS

• 01:17 - The Evolution of Customer Success: Reactive to Proactive to Predictive
• 04:11 - What "Predictive" Really Means (And Why It's Different from Proactive)
• 08:44 - Dirty Data Isn't a Blocker: How Predictive Models Actually Work
• 12:09 - The Truth About NPS Response Rates and Vanity Metrics
• 20:49 - Starting from Zero: Implementing AI at OneTrust
• 23:30 - The 3 Pillars of World-Class Digital Customer Experience
• 31:10 - Lessons Learned: Roles, Timing, and Relevance
• 35:39 - Building the Digital Tech Stack: CRM, CSP, and Community
• 42:15 - Customer-Facing AI Agents: The Agentic CSM
• 46:10 - The Future CS Team: AI Architect, BVA & New Roles
• 53:38 - Managing AI Agents Like You'd Manage Your Best CSM
• 59:24 - How AI Changes the CSM Role (Hint: They Can Handle More)

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

The conversation highlights the significance of creating effective customer success plans and the necessity of aligning customer success efforts with overall business goals.

Takeaways

AI tools are transforming how we approach customer success. Customer success metrics are often poorly defined across organizations. Gross revenue retention is becoming a critical focus for investors. The structure of customer success teams can impact their effectiveness. Compensation for customer success roles needs to reflect their contributions to revenue. Early-stage companies must prioritize customer success to drive growth. Separation of roles within customer success can lead to better outcomes. Customer success should be a company-wide initiative, not just a team effort. Creating autonomy for customer success teams can enhance performance. Defining clear success plans is essential for customer retention.

Chapters

00:00 Website Redesign and AI Integration

02:50 The Evolution of AI Tools

05:28 Customer Success Metrics and Reporting

08:18 The Role of Customer Success in Revenue Generation

11:09 Compensation Structures in Customer Success

14:06 Strategic Decisions in Customer Success

16:51 Navigating Growth in Early-Stage Companies

26:40 Sales Strategy and Market Share Growth

28:21 Customer Success and Implementation Challenges

30:06 Specialization in Customer Success Roles

32:14 Creating Autonomy and Predictability in Sales

34:51 Understanding Private Equity and Its Impact

37:37 The Importance of Gross Revenue Retention

40:16 The Role of Customer Success in Retention

43:07 Innovative Approaches to Customer Success Plans

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

In this episode of the Chief Customer Officer Podcast, Jay Nathan and Jeff Breunsbach peel back the layers on the practical application of AI in Customer Success. They start with a reality check: before you can build sophisticated AI agents, you often have to do the manual "grunt work" first — like physically reviewing contracts to clean up renewal data.

The conversation shifts to a critical debate on organizational structure, specifically the move away from the traditional "Coverage Model" (assigning accounts based on ARR) toward a "Predictive Model" that relies on real-time data signals rather than arbitrary check-ins.

Finally, Jay and Jeff geek out on the concept of "Vibe Coding" — using AI to build internal tools and websites without writing a line of code — and discuss why leaders need to get their hands dirty with these tools to truly understand them.

Chapters

00:00 Introduction & Dropping the ".io"

01:07 The Reality of Renewals: Manual Work Before AI 04:49 Why You Should Hire Ops Before Your Next CSM 09:49 The Death of the Coverage Model

13:49 Erroneous Signals vs. Predictive Data

17:44 The Evangelism Role & Fixing QBRs

25:36 The "Stay Conversation": 3 Questions to Retain Your Team

27:42 "Vibe Coding" & Building Software with AI

33:25 How Jeff Built the New Website (Without Code)

42:34 Preview: Sierra AI & Next Week

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

The conversation delves into the development of granular AI agents to enhance customer interactions and the balance between workflow and AI capabilities. They also emphasize the significance of understanding customer business contexts and choosing the right tools for effective AI implementation.

The episode concludes with thoughts on standardizing AI use across teams and the future directions of AI in customer success.

Chapters

00:00 Introduction to the Chief Customer Officer Podcast 02:58 The Role of AI in Customer Success

05:58 Building a Renewal Function with AI

08:49 Identifying Key Information for Renewals

12:08 Mapping Out the Renewal Process

15:09 Creating Operational Agents for Efficiency

18:10 The Future of AI in Customer Engagement

22:09 Optimizing Workflow with AI Agents

24:18 Personalization in Customer Interactions

26:11 The Importance of Real-Time Data

28:00 Exploring Tools for AI Integration

30:04 Categories of Agentic Tools

35:50 Empowering Business Users with Agent Development 39:04 Real-World Applications of AI in Business

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

The conversation transitions into a broader discussion about the future of enterprise software, highlighting the need for reliable systems that can integrate AI capabilities while maintaining deterministic workflows.  

The hosts also explore the implications of AI on job security and enterprise software, countering the prevailing narrative of doom and gloom. They argue that rather than replacing jobs, AI can enhance productivity by automating mundane tasks, allowing teams to focus on customer interactions. The episode wraps up with recommendations for AI-related resources and discussions on the potential for AI to personalize customer experiences, ultimately leading to more tailored and effective service delivery.    

Chapters  

00:00 Introduction and Weekend AI Experiments

02:37 The Importance of Context in AI

04:51 AI's Impact on Enterprise Software

08:57 Balancing Deterministic Workflows with AI

11:15 Personalization and Customer Experience

16:38 AI in Developer Tools and Integration

21:32 Recommended Resources and Closing Thoughts

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