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