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