Jeff Breunsbach shipped three things in one week—a community platform, a Claude-built CSM training academy, and an agent-powered internal wiki. He and Jay Nathan unpack the Karpathy-inspired philosophy of designing knowledge systems for agents instead of humans, why the engineering bottleneck has moved to customer success, and how to map product usage to P&L outcomes a CFO can see.

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

Forward deployed engineers are the new hotness—but Palantir's model was built for eight-figure deals with zero competition. Jay and Jeff break down what your team actually needs instead, from onboarding agents that cut a week off time-to-value to cataloging work your CS team shouldn't be doing.

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

Jay Nathan and Jeff Breunsbach break down an exercise Jeff ran with his CS team offsite—sorting every activity into keep, start, automate, delegate, or cut. Plus reverse roadmap reviews, cutting 50% of check-in calls, and the self-hosted agent platform Jeff's building with Buzz.

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.