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 TAKEAWAYS You'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. CHAPTERS 00:00 - Six-and-a-half-minute podcast intros, and why we don't do them 01:26 - Building a CS platform at Junction, and what early users saw in it 02:50 - Running Claude and Codex against each other for checks and balances 05:21 - One prompt, seven screens: the project management mockup 10:23 - Dreamforce, and Jay's case that you're building a UI 13:50 - Permissions, field-level controls, and moving slower on purpose 16:39 - Working where your team works: the Slack problem 17:36 - Agents as employees: names, email addresses, Slack accounts 19:27 - Muse, personal agents, and Lightfield's agentic CRM 22: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 businesses 30:50 - Bending Spoons, Airtable, and the no-titles debate 38:41 - Superhuman acquires Fathom, and a very confusing product strategy 41:33 - A bank CTO's pragmatic AI adoption playbook 47:11 - Change management, prerequisites, and what most companies skip 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

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 TAKEAWAYS Skip 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. CHAPTERS 00:00 - Intro 00:45 - An NFL survivor pool tool and the Benedict Evans thread 02:08 - Spreadsheet, no-code, point solution, platform 04:54 - Do platforms need to open up customization? 07:16 - Junction's lab pricing app, built by a salesperson 09:59 - The test kit pricing tool 12:16 - Consolidating point solutions into one internal platform 12:41 - Creativity is the limitation, not the technology 14:51 - Instinct and Town: agents in your inbox 17:16 - Building a wiki for agents first 19:18 - One agent or many? The meta-agent pattern 26:13 - Shopify's River: an AI teammate in Slack 29:13 - Why CEO modeling drives adoption 31:47 - Tactical vs. strategic work 33:01 - Middle managers and bigger books of 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

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 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

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.

Jeff and Jay get honest about where the Chief Customer Officer podcast lost its spark—and what reignited it: a seven-capability framework for post-sale teams that cuts through the roles-and-titles noise. Support, onboarding, adoption, engagement, feedback, renewal, expansion. The fundamentals haven't changed. But how you build for them—and where AI fits in—has everything to do with what kind of CS org you'll have in two years. KEY TAKEAWAYS Capabilities beat titles : Whether you call them CSMs, TAMs, or revenue architects, what matters is which capability is being delivered—not what the role is named. AI amplifies, it doesn't shortcut : Jeff's team built an AI triage agent for support tickets using N8N and Claude—but only after mapping the underlying process first. CS is a cross-functional sport : Feedback loops involve product. Renewals involve finance. Onboarding involves engineering. The seven-capability frame makes it easier to pull other teams in. Customer journey ≠ your operational blueprint : Jay's key distinction: your internal capabilities are levers you control; the customer's maturity journey is theirs to own. Roles aren't disappearing : Gong now calls theirs "revenue architects." But support, onboarding, and expansion still need owners—the work hasn't gone away. Frank Slootman's warning : At Snowflake, he refused to name any team "customer success"—so every team stays accountable. It's a brilliant structural insight. CCO is looking for its next leader : Jeff and Jay want a young, energetic operator to help run this media company. Reach out if that's you. CHAPTERS 00:00 - What is this podcast even called? 01:08 - Why the podcast lost its spark 03:06 - Rebuilding for CS leaders in the AI era 08:20 - The 7 core capabilities framework 14:39 - Capabilities vs. titles: the real shift 18:20 - Comparing to Wayne McCulloch's Seven Pillars 21:18 - Customer journey vs. operational blueprint 25:04 - Feedback loops and cross-functional ownership 27:14 - Frank Slootman on CS accountability 30:43 - How Gong reinvented their post-sale team 33:29 - Guests, consistency, and podcast format 35:23 - What's next: newsletter, community, and AI About the Show: Chief Customer Officer Podcast is a show about real strategies for customer-led growth in the AI era—from leaders actually executing, not just talking about it. Your Hosts: Jay Nathan – CEO of Balboa Solutions and Co-Founder of ChiefCustomerOfficer.io Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

Jeff is back from paternity leave and building a company brain. Jay challenges him to think bigger: before you can run agents, you need a context layer. They dig into data architecture, call transcript intelligence, and what it actually takes to build enterprise-grade AI for customer success. KEY TAKEAWAYS Source data stays in source systems : Pull via API from your existing tools rather than duplicating data. The real question is whether to write enrichment back to the CRM or store it natively. Context layer first, agents second : Every account needs a living record — call summaries, sentiment, history — before an agent can act intelligently on its behalf. Company brain = ontology + continuous enrichment : Map your key entities (customers, contacts, contracts, products) and keep populating them from calls, emails, and Slack. Agents vs. deterministic workflows : Renewals have fixed steps. Inject AI where judgment matters — like building a personalized proposal using full account context. Call transcripts are gold : Extract from Fathom, store in Postgres, add a sentiment + sensitivity classifier, expose via MCP — then query your entire call history from Claude. Cowork is MVP, not enterprise : Jeff's scheduled Fathom summaries are a perfect first step, but they stop when his laptop closes. Enterprise agents need to run independently. Harnesses vs. models : Claude and ChatGPT are harnesses above the intelligence layer. What teams actually need is an enterprise harness that shares context company-wide. LLMs need precision, not volume : Models are "dumb" because they know everything. Give them exactly the context they need — and nothing more. CHAPTERS 00:00 - Welcome & intro 01:44 - Jeff's "Steve": building a custom CS platform 04:23 - Should you write data back to the CRM? 07:21 - Context layer vs. application layer 10:44 - Building a company brain & ontology 13:16 - Agents vs. deterministic workflows 16:40 - Renewals as the perfect AI use case 20:36 - MVP first, long-term vision 22:30 - LLMs need precision context 25:15 - Open source AI & why it matters 26:35 - The Fathom + Postgres + MCP stack 33:16 - Jeff's MVP: scheduled Fathom summaries in Cowork 35:17 - From prototype to enterprise agents 38:47 - What is a model harness? 41:31 - Enterprise context & shared team knowledge 45:19 - Wrap up About the Show: Chief Customer Officer Podcast is a show about real strategies for customer-led growth in the AI era—from leaders actually executing, not just talking about it. Your Hosts: Jay Nathan – CEO of Balboa Solutions and Co-Founder of ChiefCustomerOfficer.io Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

Jay and Jeff dig into two very different but connected stories: Jeff's homegrown AI "chief operating officer" for his household, and the $10B forward-deployed engineer boom reshaping enterprise services. Along the way: why task automation isn't the same as agents, and the skill that will matter most in the age of AI. KEY TAKEAWAYS Personal agents teach real agent behavior: Jeff's household agent, Mr. Baxter, learns from ongoing texts instead of needing reprogramming — a preview of how enterprise agents should work. Task automation isn't agents: Jay's take: most companies are building automation, not agents. Real agents remember, evolve, and run without babysitting. Enterprises are building personal agents too: A $10B industrial services company Jay spoke with made personal agents for employees a pillar of its AI strategy. Lean into human relationships: Automate what doesn't need a human touch, then reinvest the saved time into surprising and delighting customers. Be maniacal about killing process: Borrowing from Elon Musk, map every step and ruthlessly ask if it should exist — and if so, human, agent, or gone. FDEs are the new consulting: Unlike consultants who parachute in and hand off a deck, forward-deployed engineers stay and build the agents that actually run the business. Pair domain experts with engineers: The real unlock is combining business context with technical build skill — or training subject matter experts directly on AI once the architecture exists. Intelligence sovereignty is the next worry: As IP questions grow, expect more interest in post-trained open-source models for cost and control. CHAPTERS 00:00 - Catching up: inbox zero and using Claude to triage email 02:46 - Meet Mr. Baxter: building an AI COO for the household 07:17 - Why personal agents preview enterprise AI strategy 14:45 - Three priorities: human relationships, killing process, more joy 22:38 - The $10B forward-deployed engineer boom 30:03 - Pairing business operators with FDEs to close the last mile 34:23 - Early adopters, intelligence sovereignty, and open source catching up 41:10 - Wrap-up and a tease for next week's Starbucks story About the Show: Chief Customer Officer Podcast is a show about real strategies for customer-led growth in the AI era—from leaders actually executing, not just talking about it. Your Hosts: Jay Nathan – CEO of Balboa Solutions and Co-Founder of ChiefCustomerOfficer.io Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

Jay and Jeff go deep on what's actually blocking enterprise AI adoption—and it's not the technology. They cover building a shared organizational brain from call transcripts, why Zapier banned Slack DMs, the $7.5B bet on forward-deployed engineers, and personal AI coaches that are already changing daily habits. KEY TAKEAWAYS Enterprise AI Blockers Are Legal and Cost, Not Tech : The technology is far ahead of adoption. Legal, IP, and data security fears—not capability—are slowing large organizations down. Single-Player AI Is the Real Bottleneck : Most teams are getting individual value but failing to share it. The shift from personal tools to team-based AI infrastructure is where the real gains live. Build a Shared Brain from Call Transcripts : Jay's "Balboa Brain" extracts an ontology from thousands of call transcripts—people, companies, engagements, best practices—and agents update it nightly. Public Channels Feed Better Agents : Zapier's Wade Foster raised internal public Slack usage from 33% to 46% via a transparency leaderboard. Private DMs destroy the context AI needs to do its job. Forward Deployed Engineers Are the New Gold : Amazon, OpenAI, and Anthropic have collectively invested $7.5B in FDE-style organizations—because the gap between AI capability and enterprise readiness is enormous. Amazon's 45-45-45 Methodology : 45 minutes to define the problem, 45 hours to build and validate, 45 days to productionalize. Fast but grounded. Systems Thinkers Win : James Clear: "You don't rise to the level of your goals, you fall to the level of your systems." This applies to AI adoption as much as any habit. Personal AI Agents Are Already Working : Jay's NanoClaw fitness coach "Jack" is tracking nutrition and workouts with measurable results after just one week. CHAPTERS 00:00 - Intro & Hot Summer in Charleston 01:30 - Enterprise AI Adoption Barriers 04:45 - Single-Player vs. Multiplayer AI 07:15 - Zapier Bans DMs: Building AI Context in Slack 11:30 - Building the Balboa Brain 19:00 - From Files to a Vectorized Database 23:00 - What Are Agents, Really? 26:00 - Forward Deployed Engineers: $7.5B Bet 30:00 - Amazon's 45-45-45 Methodology 37:00 - Less Software, Better Outcomes 41:00 - DesignJoy and the One-Person FDE Model 44:00 - James Clear's Systems Quote 45:30 - Teaching Non-Technical People to Use AI 47:00 - Personal AI Fitness Coaches & NanoClaw 50:30 - Cal AI's $30M Exit and the Hack About the Show: Chief Customer Officer Podcast is a show about real strategies for customer-led growth in the AI era—from leaders actually executing, not just talking about it. Your Hosts: Jay Nathan – CEO of Balboa Solutions and Co-Founder of ChiefCustomerOfficer.io Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

Jeff and Jay get into the gap between vibe coding your own AI tools and building something your whole team can rely on. From PRD skills to master customer data files to ClickUp's "foundry" model — this episode is about what it actually takes to move from single-player AI to enterprise AI, and why slowing down now might be the fastest path forward. KEY TAKEAWAYS PRDs as AI bumpers : A PRD skill forces you to define goals, non-goals, design constraints, and integrations before building — dramatically improving what AI produces. Single player vs. multiplayer AI : Personal tools tied to your Gmail account vanish when you leave. Enterprise AI requires shared data layers, authentication, and context. MCP vs. curated data : MCPs let you pull from systems in real time, but without a clean master data set, everyone queries the same raw sources and gets different answers. The master customer file : One canonical database table of active customers is more token-efficient and reliable than re-deriving data every time an agent runs. The foundry model : ClickUp's internal team builds core agentic infrastructure and proliferates learnings org-wide — more than a center of excellence, it actually ships. Embed, don't advise : A head of AI sitting in a room advising doesn't work. AI expertise has to work shoulder-to-shoulder with domain experts to build anything real. Slow down to speed up : Individual token spend gets you ~15% better. Enterprise data infrastructure + agents unlocks step-function improvement — but requires investing in the foundation first. Sell outcomes, not automation : The future is owning an end-to-end outcome (like Fin's "resolutions") and pricing on delivery — not just automating what already exists. CHAPTERS 00:01 - Welcome & World Cup check-in 02:35 - The PRD idea: vibe coding needs structure 05:59 - Vibe coding vs. production-ready engineering 08:00 - Single player AI vs. enterprise multiplayer 10:11 - MCP vs. curated data layers 15:12 - Master customer data files and token efficiency 18:25 - Jeff's PRD skill in action 20:57 - Generating tasks from the PRD 25:20 - How enterprises are structuring AI teams 33:29 - ClickUp's foundry model 36:36 - Why infrastructure beats individual token spend 39:18 - The ROI problem with AI investment 40:42 - AI-native services: selling outcomes 43:29 - Wrap up & Uncommon AI community update About the Show: Chief Customer Officer Podcast is a show about real strategies for customer-led growth in the AI era—from leaders actually executing, not just talking about it. Your Hosts: Jay Nathan – CEO of Balboa Solutions and Co-Founder of ChiefCustomerOfficer.io Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

Jay and Jeff are back with a live build episode — two operators comparing notes on what's actually working with AI. From Jay's Agent Command Center at Balboa to Jeff's Linear task ingestion system and a viral VS Code ad hack, this one's packed with real examples. Plus: why the moat in AI is attention, not technology. KEY TAKEAWAYS AI slop is a real leadership problem : Unedited Claude output is hitting inboxes everywhere. Jeff catches CSM candidates submitting unmodified hiring exercises. Fix: build a "fingerprints on it" culture before anything leaves your hands. The Minto Pyramid cuts bloat : Conclusion first, arguments second, details last. Jeff built this as a Claude Cowork skill his team runs before any doc goes to leadership or a customer. Agent Command Center over vendor lock-in : Jay's team built their own agent studio instead of using Azure, AWS, or Google — to control business logic, stay model-agnostic, and keep company secret sauce off a vendor platform. Models are becoming commodities : The real value is the harness layer — business logic, data connections, process knowledge. Erratic model companies can't be your foundation. Agents fill the gap tools never could : Jeff's Claude Code system surfaces emails and Slacks, confirms tasks, and auto-creates Linear tickets — removing the capture burden entirely. Show and tell beats mandates : Friday demo sessions at Balboa where team members show what they built create pull, not push. Treat AI work like a product backlog : Groom a pipeline of AI projects, sequence by value and dependencies — don't just experiment randomly. Attention is the real moat : kickbacks.ai can be copied in hours. The founder's following and first-mover gravity can't be. CHAPTERS 00:00 - Intro & new baby update 02:30 - kickbacks.ai : the VS Code ad hack 09:00 - Attention is the moat, not the tech 12:00 - Claude Cowork as a paternity leave to-do list 16:30 - The AI slop problem hitting leadership inboxes 19:00 - The CSM hiring fingerprints test 21:30 - The Minto Pyramid as a team skill 25:00 - True personalization vs. segmentation 28:30 - Jeff's Linear task ingestion agent 31:00 - Jay's Agent Command Center at Balboa 37:00 - Build vs. buy: why they went custom 39:30 - Models as commodities, harness layer as moat 43:30 - Keeping AI momentum inside your team 46:00 - AI work as a product backlog About the Show: Chief Customer Officer Podcast is a show about real strategies for customer-led growth in the AI era—from leaders actually executing, not just talking about it. Your Hosts: Jay Nathan – CEO of Balboa Solutions and Co-Founder of ChiefCustomerOfficer.io Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

Jay and Jeff kick off the show by getting into the real stuff: managing agent sprawl, why most teams aren't ready for multiplayer AI, and whether tech layoffs actually have anything to do with AI efficiency. Unfiltered and practical. KEY TAKEAWAYS Agent Sprawl Is Everyone's Problem : Agents are spinning up in every tool—Planhat, HubSpot, Gainsight, Claude. Without a team-level agent command center, you're burning tokens on experiments nobody's watching. Single Player vs. Multiplayer AI : Most teams are in single-player mode—each person in their own context window. The unlock is shared agents, shared data, and shared outputs. Verified Data Sets = Trust + Efficiency : If your team doubts an agent's output, they revert to manual work. Pre-aggregated data builds trust and cuts token costs. Jevons' Paradox in Real Time : Token prices are falling, but usage is exploding. Total AI spend is going up, not down. Model Matching Matters : Don't run a daily briefing on Opus. Use Haiku for simple tasks; save big models for high-value work. Rolling Out AI Right : Canva gave 5,000 employees a week to learn AI—they froze. Fix: verify tools and data before the hackathon, then let people explore. Layoffs Aren't What They Seem : Companies citing "AI efficiency" for cuts are mostly rationalizing. Engineering hiring is up. Every Job Is Changing : The highest-paid ops role will be the AI agent builder. Lean in or get left behind. CHAPTERS 00:00 - Intro & Jeff's baby is coming 00:53 - NanoClaw: Secure open-source personal agents 03:47 - Meet Maverick, Jay's AI podcast producer 05:11 - Agent sprawl and the containment problem 06:20 - Building a team-level agent command center 13:44 - Token costs, Jevons' paradox & model matching 17:07 - Data centers, energy, and the physical bottleneck 20:44 - How to roll AI out to teams (the Canva lesson) 22:58 - Verified data sets: Why trust and efficiency go together 35:02 - Sierra AI: $15.8B valuation, 100x revenue 38:35 - AI in customer support: Back-end before front-end 41:16 - ClickUp layoffs and the 10x vs. 100x mindset 42:18 - Tech layoffs: Is AI really the reason? 45:19 - Every job is changing—lean into it About the Show: Chief Customer Officer Podcast is a show about real strategies for customer-led growth in the AI era—from leaders actually executing, not just talking about it. Your Hosts: Jay Nathan – CEO of Balboa Solutions and Co-Founder of ChiefCustomerOfficer.io Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

Jay and Jeff are joined by Jack Nathan — our "engineering manager" for Uncommon — to share what they've actually shipped in 48 hours using Claude Code. Plus: Gainsight's retention-as-a-service bet, N8N automations surfacing customer quotes in Slack, and why the player-coach is back. KEY TAKEAWAYS Non-engineers can ship now : Jeff (not a developer) built and deployed Uncommon features using Claude Code while Jack reviewed the code as engineering manager—the gatekeeper is gone. Linear + Claude Code = AI-powered PM : Connect Linear to Claude Code and ask "what did the team change in the last 24 hours?"—issues update automatically with zero manual tickets. Community members as contributors : Uncommon members may be able to submit pull requests or plugins to improve the community itself—members building the product they use. Customer quotes on autopilot : Jeff's N8N workflow scans Fathom transcripts for praise, extracts quotes, and pushes them to a Slack channel with a link to the exact call moment. Removing the CSM as middleman : Next: auto-extract product feature requests from calls into Slack with a one-click push to a Linear ticket—cutting out lossy human translation. Gainsight Atlas skepticism : Retention-as-a-service for the long tail is compelling in theory, but branding, change management, and escalation paths make execution hard. The player-coach is back : Coinbase's 5-layer org collapse mirrors where CS leadership is heading—leaders who set direction and build, not just manage. AI as objective coach : Jay built a Claude skill that reviews exec readouts against preset criteria before team meetings—cutting meeting time in half. CHAPTERS 00:00 - Intro & Baby Watch 01:20 - Welcome Jack Nathan 02:14 - Uncommon Community Update 06:17 - Building with Claude Code Over the Weekend 08:54 - Linear Integration & AI-Powered Project Management 12:00 - Community Members Contributing via PRs 14:02 - Spencer's Automated Feature Request Pipeline 16:45 - N8N: Customer Quotes & Product Feedback Automations 21:47 - Uncommon Launch Date Discussion 24:12 - Gainsight Pulse & Atlas: Retention-as-a-Service 31:51 - Decentralized Work & Company as Code 39:20 - Coinbase's Org Collapse & the Player-Coach Model 43:49 - The CS Leader Moment We Were Made For 44:20 - Wrap Up About the Show: Chief Customer Officer Podcast is a show about real strategies for customer-led growth in the AI era—from leaders actually executing, not just talking about it. Your Hosts: Jay Nathan – CEO of Balboa Solutions and Co-Founder of ChiefCustomerOfficer.io Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

Jay Nathan flies solo to break down Emergence Capital's AI Native Services Playbook — what it gets right, where it falls short, and what it completely misses. Using a recruiting firm as an end-to-end example, Jay walks through the shift from selling software to delivering outcomes, and why the founders who win in this space won't come from SaaS — they'll come from services. KEY TAKEAWAYS AI Native Services defined : A business that collapses software and services into a single system, delivering outcomes the customer never has to produce themselves. You sell a result; your company produces it. The recruiting firm example : Instead of selling recruiting software, you become an AI-native recruiting firm — sourcing, screening, scheduling, and delivering candidates. Pricing shifts from per-seat to per-placement. Domain credibility over everything : Without deep expertise in your vertical, you start every sales conversation with zero trust. Domain credibility is brand — and it comes first. Mirage PMF is a real trap : Revenue growth powered by headcount, not AI, is not product-market fit. Watch gross margin — if it's not expanding as you scale, automation isn't doing the work. Outcome-based pricing is the unlock : AI-native services firms own the delivery, so they own the attribution. Price on results, not hours. Skip the VC framing : These businesses can generate significant free cash flow without venture capital. Don't let a VC playbook push you into unnatural growth moves. Continuity beats handoffs : Switching from a "Navy SEAL" pilot team to a steady-state delivery team erodes trust and loses context. Keep the same team; embed a forward-deployed engineer from day one. Ecosystem position is the moat : The AI alone won't differentiate you. Partnerships, certifications, and community presence inside your vertical will. CHAPTERS 00:00 - Introduction & Episode Overview 01:56 - What Is an AI Native Services Company? 03:43 - The AI-Native Recruiting Firm Example 08:10 - Where Emergence Gets It Right: Domain Credibility 09:41 - Mirage Product-Market Fit 11:14 - Outcome-Based Pricing 13:11 - Pushback: The VC Framing Problem 15:40 - Pushback: Don't Switch Pilot Teams 17:28 - Pushback: The Product Development Trap 19:47 - The Vertical Ecosystem Advantage 23:30 - Connecting AI Native Services to Customer Success 26:02 - The AI Recruiting Firm in 2026: What's Automated Now 28:10 - Recap & What to Take With a Grain of Salt About the Show: Chief Customer Officer Podcast is a show about real strategies for customer-led growth in the AI era—from leaders actually executing, not just talking about it. Your Hosts: Jay Nathan – CEO of Balboa Solutions and Co-Founder of ChiefCustomerOfficer.io Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

Neil Erickson, Founder and CEO of Owner Enable and former SVP, Global Platforms at Equifax, joins Jay and Jeff to unpack why so many CS and small business leaders feel stuck with AI. The conversation moves from Jeff's live renewal-automation build to context engineering, token economics, and why fundamentals beat shiny objects. KEY TAKEAWAYS Most teams are less mature than they think: Jay's read of 50 CS leaders — solo operators, constant hallucinations, no shared context, some buying their own Claude licenses. Context is the unlock: Pointing AI at your whole SharePoint produces nonsense. Curate the directory, files, and MCPs you load so agents stay skilled, not polluted. Memory turns reps into shortcuts: Teach the model "next time, use the Playwright MCP" and stop fumbling through 12 iterations on the same task. Aim small, miss small: Pick two or three use cases, put a dollar value on them, then prove feasibility by mapping the exact data the LLM needs. The juice has to be worth the squeeze: Token costs are not dropping. Energy and compute constraints make intelligence a real line item. Renewals are a perfect first target: Jeff is rebuilding his renewal motion with AI-drafted proposals — roughly 20 hours a week back across the team. Information management is the boring work that matters: KISS, clean inputs, governed access, real APIs — table stakes most companies skipped. The great role collapse is here: A dollar of ARR is worth 2–3x, not 10x. Account teams of 10 become teams of 1.5, and AI fluency is the new baseline. ABOUT OUR GUEST Neil Erickson is Founder and CEO of Owner Enable, helping small business owners use AI to make more money and save time by connecting the tools they already have. He's also a Partner at PeerCxO, advising mid-market and PE-backed executives. Neil spent seven years at Equifax, most recently as SVP, Global Platforms, with prior leadership roles at Travelport, IHG, and Starwood. CHAPTERS 00:00 - Welcome and Neil's enterprise background 03:52 - Jeff's renewal automation build 06:00 - Templated proposals, Playwright, and MCPs 13:27 - 50 CS leaders, hopelessness, and missing context 17:53 - Context and memory, explained simply 22:35 - Why every AI lab is launching services 25:00 - Anthropic for small business and the partner gap 30:30 - Where to actually start: KISS and information mgmt 36:00 - Token costs and the juice vs. the squeeze 40:00 - The great role collapse 44:21 - New skill sets for an AI-native workforce 46:30 - Inside Owner Enable About the Show: Chief Customer Officer Podcast is a show about real strategies for customer-led growth in the AI era—from leaders actually executing, not just talking about it. Your Hosts: Jay Nathan – CEO of Balboa Solutions and Co-Founder of ChiefCustomerOfficer.io Jeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

Jay and Jeff get into the weeds on two of the biggest questions in CS right now: how to build a community that doesn't devolve into spam and consultant pitches, and how the Forward Deployed Engineer role is reshaping who actually sits in front of customers. Plus what Junction is learning about building a product for agents, not just humans. 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

Jay and Jeff debrief last week's AI Show & Tell — 150 customer leaders watching four real builds in production. A custom CS platform in Claude Code. A sales reference agent. Renewal workflows that adapt to customer health. 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

Jay and Jeff swap real examples of building custom AI tools instead of buying software — a $1K brand video that beat $750K agency quotes, a content planner built in 35 minutes, and a renewal digest that surfaces customer context weekly with zero manual effort. Plus: why the CS platform category is stalling, and the difference between a service blueprint and a customer journey. 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

Is the CSM role actually dead? Jay and Jeff unpack Chad Hornfeld's viral Avoca post on replacing CSMs with Technical Account Managers and forward-deployed engineers — and what it means for how Jeff is hiring at Junction right now. Plus: Jay's weekend-built HubSpot dashboard, why Claude is winning B2B, and rebuilding onboarding around the patient journey. 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