Jay Nathan and Jeff Breunsbach get into the foundational data problem most SaaS teams are ignoring — and why it's about to become a crisis. If your data is siloed, your AI agents will be siloed too.

Plus: Jay introduces "Company as Code," a markdown-in-GitHub system for building personalized outreach and landing pages at scale — and why the same playbook applies directly to customer success.

KEY TAKEAWAYS

• Start with a customer master record: Before any AI agent can help you, you need a deduplicated view of your customer outside your CRM. Jay spoke with companies from 150 to 3,500 people this week — they all have the same problem.
• Company as Code: Jay is documenting personas, ICP definitions, and outreach styles as markdown files in a GitHub repo — one canonical version that every AI tool pulls from, updated by anyone on the team via pull request.
• Siloed AI = siloed data with a new wrapper: If your sales AI only sees sales data and CS's AI only sees CS data, you've rebuilt your silos with an AI layer on top. Fix the data first.
• Personalization is now just token costs: Custom landing pages, personalized emails, interactive surveys — what used to require massive investment is now a few tokens.
• Existing customers need outbound too: Just because someone's a customer doesn't mean they understand your product. Use the same personalization playbook to re-engage and educate your base.
• ABM belongs in Customer Success: Jay shares the "Spreading the FLU" story — a field-level understanding program that educated every influencer at top accounts. CS teams should run the same play.
• AI-powered upsell prioritization: Use Fathom recordings, emails, and Slack signals to surface the top 10–20 customers most ready for a new product — before sending a rep in cold.
• The CSP question is getting louder: "It's 2026. Do you need a customer success platform anymore?" Jay is hosting a webinar with two practitioners who built in opposite directions.

CHAPTERS

• 00:01 - Weekend updates
• 03:45 - Unifying customer data at Junction with BigQuery and Metabase
• 07:00 - Building a customer master record outside your CRM
• 10:10 - Why siloed AI is just siloed data with a new wrapper
• 11:48 - Company as Code: markdown files in GitHub as a single source of truth
• 14:45 - Personalized landing pages for prospects — and customers
• 19:00 - The risk side: when custom-built tools fall short
• 23:45 - Using Claude Cowork to research private companies via public comparables
• 27:00 - Applying outbound personalization to your existing customer base
• 29:00 - AI-powered upsell prioritization using call recordings and signals
• 33:00 - Spreading the FLU: account-based marketing applied to CS
• 35:00 - QPR as an interactive landing page for top accounts
• 36:45 - Webinar preview: Do you still need a CSP in 2026?

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 another hosts-only episode — and Jay builds an AI vulnerability matrix live on the call. They cover how to stand out as an AI-first job candidate, the three biggest AI go-to-market mistakes leaders are making right now, and the heated debate over whether the CSM role is really being replaced or just transformed.

KEY TAKEAWAYS

• Prove you're AI-first before the interview: The best candidates aren't submitting resumes — they're building things. A candidate for Jay's team built an app in Lovable and sent it unprompted. That's how you get noticed. Loom videos, written walkthroughs, anything that shows you've done the work.
• Centralize AI where it touches systems of record; let everything else run organically: MCP-connected tools that touch your CRM or customer data need governance and controls. Departmental tools like Gamma don't. The mistake is treating all AI adoption the same.
• The three go-to-market AI mistakes: Automating bad processes at scale, building on generic best practices instead of your own call data, and prioritizing internal efficiency over the buyer experience. These aren't new problems — AI just makes them impossible to ignore.
• Know which quadrant you're in: Jay's AI Vulnerability Matrix maps companies by solution complexity vs. replicability. Sitting ducks (low complexity, easy to replicate) need to move fast. Fortresses (high complexity, hard to replicate) have time. Knowing your quadrant should drive your entire strategy.
• The $700K ARR per employee benchmark: AI-native companies are hitting $700K–$1M+ ARR per employee. The old benchmark was ~$200K. If you're still staffing like it's 2019, a competitor is already disrupting you.
• Humans stay in the CS loop — but the role changes: Agent-to-agent purchasing will happen first for simple products. For complex enterprise software, the relationship still matters. But the job shifts: less task management, more being so embedded in the customer's business that you know their next move before they do.

CHAPTERS

• 00:01 - Welcome + why Balboa runs a February fiscal year
• 02:34 - The job candidate who built an app to stand out
• 04:16 - Three ways to prove you're AI-first as a candidate
• 09:01 - Kyle Norton: centralize AI adoption or let it happen organically?
• 12:16 - Why you need both — and Jay's internal AI show-and-tell at Balboa
• 17:53 - Kyle Lacy's three go-to-market AI mistakes
• 21:50 - Your call recordings are your best practices
• 23:27 - Jay builds the AI Vulnerability Matrix live on the call
• 25:32 - The four quadrants: sitting ducks, protected niches, targets, fortresses
• 33:19 - What AI-first companies actually look like (Jason Lemkin)
• 35:00 - The shift from CSM to forward deployed engineer
• 36:12 - The $700K ARR per employee benchmark
• 36:40 - Jeff's counterpoint: humans stay in the buying loop longer than we think
• 41:15 - Agent-to-agent PLG is already happening
• 45:54 - 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

No guest this week — just Jay and Jeff getting into the weeds on what they're actually building with AI right now. From Block's layoffs (and why AI is mostly "air cover" for over-hiring) to MCPs, deal staging from call transcripts, and creating hundreds of renewal records in a single afternoon — this one is all about practitioners doing the work, not just talking about it.

KEY TAKEAWAYS

• AI layoffs are mostly "air cover": The Block cuts are less about AI replacing workers and more about correcting COVID-era over-hiring. Companies are using AI as PR cover for reductions that should have happened years ago.
• MCPs are the new API layer for CS teams: MCP servers let leaders query and update tools like HubSpot and PlanHat in plain English — no developer required. Jeff rebuilt his entire field mapping strategy between two platforms in a single Sunday afternoon using Claude Cowork.
• AI deal staging removes subjectivity from the pipeline: By running Fathom call transcripts through an AI model with defined stage criteria, Jeff's team gets consistent deal staging — notes, next action, and stage movement all updated automatically. CSMs validate rather than enter.
• You can build a renewal pipeline from scratch in an afternoon: Jeff used Claude Cowork and the HubSpot MCP to auto-generate hundreds of renewal records with ARR, products, and close dates — work that would have taken weeks manually.
• SaaS incumbents need a self-disruption pricing strategy: If AI is driving down the cost to build software, someone will undercut you on price. The winners will do it to themselves first — like Adobe's "swallowing the fish" move to SaaS. Your gross margin is someone else's opportunity.
• Customer journey ≠ service blueprint: The service blueprint is how you deliver your service. The customer journey is the customer's path to value — change management, adoption, transformation. Keeping them separate is the future of CS platform design.

CHAPTERS

• 00:01 - Welcome and personal updates
• 02:32 - Block's 4,000 layoffs: AI as cause or air cover?
• 07:32 - Small nimble teams and the Jack Dorsey thesis
• 09:00 - MCPs explained: querying HubSpot and PlanHat in plain English
• 15:27 - Token costs and natural language as the new interface
• 17:08 - Jay's SaaS self-disruption pricing thesis
• 22:39 - M&A in the AI era and the Palo Alto Networks acquisition playbook
• 27:12 - Jeff's AI build: deal staging from call transcripts via Fathom and PlanHat
• 32:37 - Creating hundreds of renewal records in one afternoon with Claude Cowork
• 39:41 - Customer journey vs. service blueprint — the clearest definition yet
• 42:10 - Wrap-up and preview of an upcoming guest

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