The Chief Customer Officer Podcast

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

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 TAKEAWAYSDesign 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.CHAPTERS00:00 - Welcome & Jay's CCO Summit trip to Boston01:30 - Why in-person still matters for team chemistry03:00 - Launching Uncommon community + vector databases05:30 - The Claude-built CSM training academy08:00 - Agent learning loops: the lessons-learned file09:30 - The Karpathy-inspired agent-first internal wiki13:00 - Designing for agents, not humans15:30 - The autonomous CRM vision17:00 - One wiki powering the whole org downstream20:00 - Jobs aren't disappearing—they're shifting21:00 - P&L literacy gap at the CCO Summit24:00 - The new bottleneck: go-to-market teams26:00 - Feature velocity vs. the 1-degree problem29:00 - Teaser: consumption vs. outcome-based pricing32:00 - Jay's leading → lagging → KPI frameworkAbout 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

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 TAKEAWAYSThink 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.CHAPTERS00:00 - Charleston heat and offsite season01:09 - The forward deployed engineer hype, revisited02:08 - Why Palantir's FDE model doesn't map to your business05:20 - Getting ingrained in the customer's business07:12 - Cutting a week off onboarding with a deployed solutions engineer12:39 - Time to first result over throwing everything at customers13:34 - The onboarding agent and AI-first delivery at Balboa16:17 - Google Sheets, Figma boards, and mapping before automating20:00 - Blending AI into the service blueprint21:10 - "The job today isn't the job in twelve months"25:27 - Vision setting, rally cries, and the Kennedy moon speech29:00 - The Wayne McCulloch open-document vision exercise30:06 - Cataloging work your team shouldn't be doing36:56 - Working Genius, activators, and galvanizers38:12 - Community, Vistage, and relaunching UncommonAbout 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