Land and Expand
Land and Expand
Podcast Description
Conversations about business, AI, and customer success.
Podcast Insights
Content Themes
The podcast explores themes related to customer success, AI integration, and retention strategies within SaaS businesses. Notable episodes include discussions on the Critical Customer Care framework for reducing churn, strategies to prevent burnout among customer success teams, and the significance of effective onboarding in product-led growth models. Topics also cover metrics such as ARR, Gross Retention, and nuances of private equity versus venture capital in the software industry.

Conversations about digital experience and AI.
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

Disclaimer
This podcast’s information is provided for general reference and was obtained from publicly accessible sources. The Podcast Collaborative neither produces nor verifies the content, accuracy, or suitability of this podcast. Views and opinions belong solely to the podcast creators and guests.
For a complete disclaimer, please see our Full Disclaimer on the archive page. The Podcast Collaborative bears no responsibility for the podcast’s themes, language, or overall content. Listener discretion is advised. Read our Terms of Use and Privacy Policy for more details.