The Chief Customer Officer Podcast

Most teams start with AI by listing what their people do and asking which tasks a bot can take over. Jay thinks that's backwards. Start with the work, let the agent own it, and have it pull in a human only where judgment matters.Jeff and Jay dig into what that means for planning next year. They cover why software companies need to sell the outcome instead of features, and why a SaaS tool you can clone in a weekend is worth zero. They also share Jeff's take on boiling the customer journey down to the five to seven moments that matter.In this episode00:00 Cold open00:18 Welcome00:55 Remembering Adam Robinson02:00 Planning next year when AI changes how the work gets done. Does token spend raise your cost to serve?04:58 Start with the problem you're actually solving, not the tools (Good Strategy Bad Strategy)09:44 Call recordings hold most of your customer context10:29 Most companies don't use enough tokens yet for cost to serve to matter12:13 Flip it inside out: the agent does the work and tags in the human. The Spawn example.16:31 A Figma product manager's agent that runs its own A/B tests and asks him to approve the merge18:59 Arca isn't a software company, it's a wealth manager. Gainsight sells renewals as a service.22:15 SaaS cut services to protect gross margin. Now the value flips back to the service.23:11 "I could clone our PSA tool in a weekend." SaaS is just a CRUD database.26:24 Data moats and action moats27:11 Can I vibe code it?28:32 Agents should ship with a data model, and open source starter kits have a big role to play29:46 The five to seven customer moments that matter, designed agent first31:22 Ops becomes the team that runs the agents32:00 Want your team to get good at AI? Teach them one tool.33:18 An AI build day in teams of twoKey takeawaysDefine the constraint first. Name the problem holding back growth, retention, or expansion before you pick a tool. Then plan by quarter or month, not just by year.Flip it inside out. Design the work so the agent runs it end to end and pulls in a human for judgment calls and direction changes.Sell the work, not the software. Customers want the renewal, the approved timesheet, the profitability report. If you don't have a data moat or an action moat, features alone won't hold up.Cut the journey to the moments that matter. Most teams overbuild customer touchpoints. Find the five to seven that count, and design each one so the agent does the work first.Teach one tool deeply. Skills learned in one agent platform carry over to the others.Mentioned in this episodeGood Strategy Bad Strategy by Richard Rumelt"How the most AI-pilled company in the world works," a podcast episode about Spawn [add link]How I AI with Claire Vo, the Figma product manager episode [add link]Latent Space with Aman Singh of Arca, on how agents run a wealth management firm [add link]Can I vibe code it? (canivibecode.com)Satya Nadella's "SaaS is just a CRUD database" remarkBalboa is working toward Anthropic certified partner status

Jay and Jeff dig into what happens when everyone in the business can build software. They get into internal "forward-deployed" builders, why chat can't be the interface for agents, the $30K Claude bill that has CFOs paying attention, and Jay's questions for a "CS Team of 2030" exec session.KEY TAKEAWAYSAI is the next Excel: Building tools is moving out of IT and into the hands of operators, as long as guardrails come first.Platform team + embedded builders: Central teams provide the secure "bowling lane"; loaned-out builders help each team ship what it needs.Reimagine, don't iterate: Ask whether the process needs to exist at all, but roll change out with care. Most people want consistency.Prototype to beat paralysis: "You can configure anything" doesn't land. A mock-up an hour later does.Chat isn't the agent UI: A process run 15 times a week needs a structured interface that steers human judgment.AI spend governance is coming: One mid-level manager ran up a $30K Claude bill in a month. Expect business cases and caps.Unused tokens are wasted capacity: Always-on agents and shared job queues could put idle subscription capacity to work.Humans stay accountable: When an agent goes off the rails, the person who deployed it owns the outcome.CHAPTERS00:00 - Halloween costumes and intro02:01 - Engineer with AI vs. domain expert with AI04:20 - Will companies build internal software teams?07:05 - Chief of staff models and internal forward-deployed engineers09:56 - Jeff's customer segmentation app11:45 - "AI is the next Excel" and rolling out Claude Code13:36 - Reimagining vs. iterating on processes15:52 - First principles and the human side of adoption18:57 - Real-time prototyping to beat configuration paralysis21:55 - Agent design sprints: one agent, many interfaces24:02 - Why chat can't be the interface for agents26:23 - The $30K Claude bill and AI spend governance28:15 - Unused tokens, always-on agents and a token marketplace35:01 - Why interfaces still matter: accountability and observability38:56 - The enterprise adoption gap and intelligence sovereignty44:19 - Lightning round: the CS team of 203046:53 - Letting non-engineers ship codeAbout the Show: Chief Customer Officer Podcast is a show about real strategies for customer-led growth in the AI era—from leaders actually executing, not just talking about it.Your Hosts:Jay Nathan – CEO of Balboa Solutions and Co-Founder of ChiefCustomerOfficer.ioJeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

Jeff just shipped an internal CS platform to his team at Junction, imposter syndrome and all. He and Jay unpack what it means when software is effectively free: CS teams prototyping features before product gets to them, ops becoming the AI team, and why every agent needs an interface that isn't a chat window.KEY TAKEAWAYSShip before it's perfect: Get the tool in people's hands. Broken things surfaced fast, and cross-functional ideas followed.Software is the new spreadsheet: Nobody is self-conscious showing execs a spreadsheet. Custom apps are heading the same way.Prototype the roadmap gap: CS and a solutions engineer can get a deprioritized feature 70-80% built, then hand it to engineering.Every software company becomes an FDE org: As packaged software loses value, the edge is tailoring the last 20% to each customer.Make AI visible: A "How I AI" channel of real screenshots and skill files shows people what's possible.Ops is the AI team: Ops should run ahead, building tooling and data plumbing AI first.Less instruction, better outcomes: Clear intent beats over-specification with AI and with people.The Ship It list: If you do it more than once a week, it goes on the list. A Friday tiger team tries to ship one in an hour.Every agent needs an interface: Humans need a purpose-built harness to review agent output and act, with a high bar for what reaches them.CHAPTERS00:00 - Intro and the Q4 crunch00:55 - Jeff ships an internal CS platform03:34 - Is a custom app the new spreadsheet?04:15 - Building features product won't get to this quarter06:40 - Forward deployed engineering and "software is free"09:01 - Owning the last 20% for customers10:16 - An AI-first mindset and a "How I AI" channel12:42 - Why ops should be the AI team13:44 - Two-sentence prompts15:35 - Less instruction, better outcomes17:41 - The Ship It list and Friday tiger team19:05 - Every agent needs a custom interface23:03 - Raising the bar on what reaches humansAbout the Show: Chief Customer Officer Podcast is a show about real strategies for customer-led growth in the AI era—from leaders actually executing, not just talking about it.Your Hosts:Jay Nathan – CEO of Balboa Solutions and Co-Founder of ChiefCustomerOfficer.ioJeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

Most product companies don't have a shipping problem. They have a problem turning what they ship into money. In this solo episode, Jay Nathan, CEO of Balboa, breaks down product success: the loop that connects building, launching, adopting, and renewing, and the 5-step method his team uses with 200+ clients.KEY TAKEAWAYSGoals aren't strategy: "Grow 30%" is a goal. Good strategy has a diagnosis, a guiding policy, and coherent actions.Name the real problem: Year-one churn usually means customers never activated. Diagnose first, then act.Find your Herbie: Every system has one constraint. Improvements anywhere else are the illusion of progress.AI moved the constraint: Engineering is no longer the bottleneck. Adoption, enablement, and selling are.Product success is a loop: Market needs, launch and release, adoption, and customer lifecycle feed each other.Departments are the problem: The loop works when teams share one view of the customer and one strategy.Segment before you solve: A grid of segments by product turns "adoption is low" into a specific, fixable gap.Climb the measurement ladder: Signals feed leading indicators, then lagging indicators, then KPIs tied to the P&L.ABOUT YOUR HOSTJay Nathan is CEO of Balboa, which helps product, CS, and go-to-market teams turn product data into growth. He has led CS and go-to-market teams for 20+ years. Connect with Jay on LinkedInCHAPTERS00:00 - Why shipped software doesn't turn into money01:29 - Good Strategy, Bad Strategy primer02:24 - Four signs of bad strategy03:47 - The kernel of good strategy05:19 - Example: fixing year-one churn08:51 - Patterns from 200+ Balboa clients11:57 - The Goal and finding your Herbie15:59 - AI moved the constraint to adoption17:03 - Defining product success19:02 - The product success loop24:40 - Why departments are the problem25:20 - The Insights to Impact method26:45 - Step 1: Segmentation30:58 - Step 2: Prioritization33:59 - Step 3: Strategy definition35:57 - Step 4: The measurement ladder38:35 - Step 5: Deploy, measure, iterate40:16 - Beyond product analytics42:19 - This week's challengeAbout the Show: Chief Customer Officer Podcast is a show about real strategies for customer-led growth in the AI era—from leaders actually executing, not just talking about it.Your Hosts:Jay Nathan – CEO of Balboa Solutions and Co-Founder of ChiefCustomerOfficer.ioJeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

Jeff is back from Junction's Portugal offsite with a reminder: most of your company knows far less about your customers than you think. Jay and Jeff dig into pushing customer insight into the business, why AI-built internal tools are now table stakes, and what Salesforce's reported $2B Listen Labs deal says about AI talking to customers.KEY TAKEAWAYSYour company doesn't know your customers: A half-day "who are our customers" session gave engineering a clearer view of how the product is actually used.Push beats pull: A Slack channel of customer quotes builds context but rarely drives action. Shadowing rotations, all-hands stories, and planning meetings do.Make insight capture a button press: Summarize calls daily and let CSMs approve what becomes a ticket, with a human in the loop.Internal tools are table stakes: Anyone can build them now. Alignment, strategy, and consistent communication from a leader are the differentiator.People stop reading AI: Jay cites a stat that 78% of readers quit when they detect AI, and most never come back. That includes agent-sent job applications.Weeks of work in minutes: Jeff built an interactive segmentation and account-transition tool in under 10 minutes. Rolling it out is still human work.Enterprise AI deployment is the opportunity: Agent-to-agent work gets complicated fast at scale, and public-company CEOs will soon face pressure to prove adoption.CHAPTERS00:00 - Intro and Jeff's Portugal offsite01:45 - A half day on "who are our customers"04:09 - Operationalizing customer insights05:10 - Call-to-ticket workflows and all-hands rituals07:32 - The customer quotes channel and finite attention10:10 - Push vs. pull and shadowing rotations12:07 - AI is just technology: the factory robot lesson13:38 - Junction's company-wide support rotation15:05 - Leadership is the differentiator17:49 - The 78% stat and agent-sent job applications20:32 - Building a segmentation model in minutes22:01 - The future of customer success23:24 - A tool for CSM-to-CSM account transitions25:37 - Salesforce acquires Listen Labs27:50 - The harness race and the work/home AI divide30:14 - What personal AI assistants actually cost32:15 - Would you talk to an AI moderator?33:44 - Agents as necessary friction34:53 - Agent-to-agent work and enterprise AI deployment37:04 - Wrap-up and The GoalAbout the Show: Chief Customer Officer Podcast is a show about real strategies for customer-led growth in the AI era—from leaders actually executing, not just talking about it.Your Hosts:Jay Nathan – CEO of Balboa Solutions and Co-Founder of ChiefCustomerOfficer.ioJeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

Ziv Peled, Chief Customer Officer and Chief AI Officer at AppsFlyer, joins Jay to unpack how a $500M+ ARR company moved everyone to Claude, built its own AI stack, and now measures every role by "AI leverage." Plus: why Salesforce should resell Claude, and why FDE really means net dollar retention.KEY TAKEAWAYSEveryone is a builder now: Building isn't writing software. It's workflows, skills, and automations, and leaders have to be hands-on to know what their teams need.Work 24/7 without working 24/7: Split work between you and AI, keep agents busy around the clock, and step in for a quick eval when a human is needed.Agents from a central place: AppsFlyer built an MCP, semantic layer, and data lake over 29 data sets so 800 people inherit agents instead of each building their own.Classifiers power automation: Fast, cheap, typed models make agent decisions like routing a customer request reliable in under a second.Build near the system of record: Own your Salesforce, NetSuite, and billing developers. Buy at the application layer.FDE is NDR: Forward-deployed engineering isn't professional services. It's about outcomes the customer judges, tied to retention.Measure AI leverage: If an SDR goes from 5 to 10 meetings a month, that's 100% leverage. Measure end-of-funnel, quality KPIs.ABOUT OUR GUESTZiv Peled is the Chief Customer Officer and Chief AI Officer at AppsFlyer, where he leads AI strategy across go-to-market while guiding a 170-person CS org. He previously served as VP Product and CCO at AppsFlyer. Connect with Ziv on LinkedInCHAPTERS00:00 - Catching up: Israel's tech moment06:08 - AppsFlyer's strategic investment from Meta, Google, Moloco, and Unity07:04 - From CCO to Chief AI Officer09:45 - Why every leader needs to be a builder10:13 - Assistants vs. automation and the new adoption curve13:24 - Multiplayer AI for teams15:14 - Inside AppsFlyer's internal AI stack19:56 - Splitting time between CAIO and CCO22:53 - The 24/7 mindset and human-in-the-loop evals25:44 - The AI budget equation27:01 - Teaching people to think like designers29:57 - Classifier models and go-to-market use cases34:59 - Build vs. buy39:08 - Salesforce, Anthropic, and the GRR play44:33 - The value era for customer success46:07 - The sewing machine story48:07 - FDE is net dollar retention52:25 - The AI leverage scorecard54:52 - Goodhart's Law and wrap-upAbout the Show: Chief Customer Officer Podcast is a show about real strategies for customer-led growth in the AI era—from leaders actually executing, not just talking about it.Your Hosts:Jay Nathan – CEO of Balboa Solutions and Co-Founder of ChiefCustomerOfficer.ioJeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

Jay and Jeff dig into why Harvey went from SaaS to AI implementation, why agent infrastructure has to be a company-wide investment, and why the personal-agent wave is a platform war, not an app war. Then they get honest about AI writing: 78% of readers stop reading when they suspect AI wrote it.KEY TAKEAWAYSPaid AI is still niche: A16Z data shows only ~3% of US consumers pay for AI themselves, but the youngest buyers adopt at 4x the rate of the oldest.SaaS to AI implementation: Harvey went from app to harness to its own models, and now deploys that know-how inside clients as forward deployed engineering.Centralize agent infrastructure: When every department builds its own agents, context fragments. CS, support, product and engineering should share one customer brain.No plumbing, no agents: Messy CRMs and unused data warehouses mean you often have to build the infrastructure before agentic work pays off.Platform war, not app war: Most personal agents look the same. You'll buy into ecosystems (Meta, Amazon, Google, Apple) based on where your data lives.Don't use the words it suggests: LLMs write in magazine headlines and encourage your first-draft impulses. Readers sense you've become "artificially flavored."Readers punish AI writing: 78% stop reading suspected AI content and 71% avoid the author going forward.Use AI as researcher and editor: Let it gather sources, opposing views and data, then write yourself. Save generation for templated assets built from verified sources.CHAPTERS00:00 - Welcome and AI in high school01:38 - Only 3% of consumers pay for AI04:19 - Meta Muse negotiates on Facebook Marketplace06:30 - Harvey's shift from SaaS to AI implementation10:59 - Why agent infrastructure should be centralized13:19 - You're never that far behind14:11 - Selling agentic work without the plumbing14:53 - Tool FOMO: Instinct, Town and Muse17:27 - A platform war, not an app war20:01 - Jay goes back to writing on his own23:28 - Two rules for writing with LLMs25:38 - Readers abandon AI-written content28:03 - AI for research, not writing29:48 - AI slop in client presentations31:19 - Claude in Slack and trusting AI messages32:18 - Branded two-pagers in seven minutesAbout the Show: Chief Customer Officer Podcast is a show about real strategies for customer-led growth in the AI era—from leaders actually executing, not just talking about it.Your Hosts:Jay Nathan – CEO of Balboa Solutions and Co-Founder of ChiefCustomerOfficer.ioJeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

Jeff built seven screens of a customer success platform from one throwaway prompt, then sat in disbelief for three minutes. Jay argues he didn't build a platform at all — he built a UI, and that distinction may reshape who owns the CRM layer. Plus: the most pragmatic AI adoption playbook either host has seen, from a 700-person bank.KEY TAKEAWAYSYou're building a UI, not a platform: The data layer, permissions, and system of record still have to live somewhere. Generated interfaces sit on top — they don't replace it.Make models check each other: Jeff runs Claude and Codex against the same codebase and PRs. Trusting one model unchecked is how quiet mistakes ship.Bake permissions in on day one: Field-level controls are cheap to design now, expensive to retrofit after someone overwrites a CRM field.Agents are employees, automations are triggers: Jay's team gives agents names, email addresses, and Slack accounts, then scopes specific tasks to them.Meet people where they work: A great internal tool nobody opens loses to a mediocre one that lives in Slack.Native beats bolted-on: Lightfield builds call recording into an agentic CRM — raising whether platforms simply absorb point solutions like Gong and Fathom.The 20-year default is up for grabs: AI-native companies are re-evaluating Salesforce and HubSpot, and $10–30M niche software businesses look far more buildable.Adoption is change management: Licenses aren't a strategy. Training, champions, and executive time are.CHAPTERS00:00 - Six-and-a-half-minute podcast intros, and why we don't do them01:26 - Building a CS platform at Junction, and what early users saw in it02:50 - Running Claude and Codex against each other for checks and balances05:21 - One prompt, seven screens: the project management mockup10:23 - Dreamforce, and Jay's case that you're building a UI13:50 - Permissions, field-level controls, and moving slower on purpose16:39 - Working where your team works: the Slack problem17:36 - Agents as employees: names, email addresses, Slack accounts19:27 - Muse, personal agents, and Lightfield's agentic CRM22:16 - Do platforms eat point solutions like Gong and Fathom?24:02 - Would a new company pick Salesforce or HubSpot today?27:46 - Compound startups and the case for $10–30M software businesses30:50 - Bending Spoons, Airtable, and the no-titles debate38:41 - Superhuman acquires Fathom, and a very confusing product strategy41:33 - A bank CTO's pragmatic AI adoption playbook47:11 - Change management, prerequisites, and what most companies skipAbout the Show: Chief Customer Officer Podcast is a show about real strategies for customer-led growth in the AI era—from leaders actually executing, not just talking about it.Your Hosts:Jay Nathan – CEO of Balboa Solutions and Co-Founder of ChiefCustomerOfficer.ioJeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

For thirty years we bought software off the shelf and reshaped our processes to fit it. Jay and Jeff argue that era is ending: at Junction, a salesperson and an ops leader each shipped their own internal pricing app, and Shopify's River agent now authors one in eight pull requests merged into the main monorepo. This episode is about what happens when building beats buying — and where those agents should actually live.KEY TAKEAWAYSSkip the spreadsheet: The old path was spreadsheet, no-code, point solution, platform. Now you build the personal point solution first.Configurability becomes table stakes: If your platform can't be customized, customers will build around you or find a vendor who lets them.Business people are the builders: Junction's lab pricing tool came from a salesperson, the test kit tool from an ops leader — not engineering.Back-burner problems finally get built: Pricing lookups were always real friction, never big enough for an engineering sprint. Now they take a weekend.Go to fewer places, not more: Agents should meet your team in the inbox or Slack, not add another app to the switching tax.Systems of record go headless: Jeff's internal wiki lives in a GitHub repo as markdown, built for agents to read first and humans second.One meta-agent, many specialists: A central agent that delegates beats one agent holding every context — and it can query a teammate's agent for what it doesn't know.Modeling behavior drives adoption: Shopify's CEO works with River in an open Slack channel. 5,983 employees followed across 4,450 channels.The middle is thinning: Everybody's a builder. CS coverage moves from 50 named accounts per CSM toward 150.CHAPTERS00:00 - Intro00:45 - An NFL survivor pool tool and the Benedict Evans thread02:08 - Spreadsheet, no-code, point solution, platform04:54 - Do platforms need to open up customization?07:16 - Junction's lab pricing app, built by a salesperson09:59 - The test kit pricing tool12:16 - Consolidating point solutions into one internal platform12:41 - Creativity is the limitation, not the technology14:51 - Instinct and Town: agents in your inbox17:16 - Building a wiki for agents first19:18 - One agent or many? The meta-agent pattern26:13 - Shopify's River: an AI teammate in Slack29:13 - Why CEO modeling drives adoption31:47 - Tactical vs. strategic work33:01 - Middle managers and bigger books of businessAbout the Show: Chief Customer Officer Podcast is a show about real strategies for customer-led growth in the AI era—from leaders actually executing, not just talking about it.Your Hosts:Jay Nathan – CEO of Balboa Solutions and Co-Founder of ChiefCustomerOfficer.ioJeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

Jay walks through the customer segmentation workshop he ran this week — a deliberately simple grid of lifecycle stage, engagement model, and health status that gets leaders to say what should happen in the business before anyone argues about tools. Plus: what "harness lock-in" means for your AI stack, and why the customer quote you read never lands like the one you watch.KEY TAKEAWAYSSegment 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.CHAPTERS00:00 - Apex habits and why consistency compounds03:23 - Jeff cheats on Claude and tries Codex06:04 - Model vs. harness: the real lock-in problem08:02 - Why enterprises can't move at personal-project speed10:53 - 87 out of 100 people have never touched AI11:44 - The skills AI doesn't replace: trust, transparency, relationships12:39 - Turning customer quotes into watchable clips14:29 - Ride-alongs, exec sponsors, and 50 calls in 50 days18:51 - Inside the segmentation workshop21:07 - Engagement model and the red/yellow/green grid23:33 - Business requirements before playbooks27:35 - Bumpers on a bowling lane, not word-for-word scripts33:02 - Segmentation as a microcosm of strategy37:25 - Why CS platform deployments failAbout the Show: Chief Customer Officer Podcast is a show about real strategies for customer-led growth in the AI era—from leaders actually executing, not just talking about it.Your Hosts:Jay Nathan – CEO of Balboa Solutions and Co-Founder of ChiefCustomerOfficer.ioJeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io