EP023: From Vibe Coding to Enterprise AI  episode artwork

EPISODE · Jun 25, 2026 · 43 MIN

EP023: From Vibe Coding to Enterprise AI

from The Chief Customer Officer Podcast · host Jay Nathan & Jeff Breunsbach

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 TAKEAWAYSPRDs 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.CHAPTERS00:01 - Welcome & World Cup check-in02:35 - The PRD idea: vibe coding needs structure05:59 - Vibe coding vs. production-ready engineering08:00 - Single player AI vs. enterprise multiplayer10:11 - MCP vs. curated data layers15:12 - Master customer data files and token efficiency18:25 - Jeff's PRD skill in action20:57 - Generating tasks from the PRD25:20 - How enterprises are structuring AI teams33:29 - ClickUp's foundry model36:36 - Why infrastructure beats individual token spend39:18 - The ROI problem with AI investment40:42 - AI-native services: selling outcomes43:29 - Wrap up & Uncommon AI community updateAbout 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.ioJeff Breunsbach – Head of Customer Success at Junction and Co-Founder of ChiefCustomerOfficer.io

Episode metadata supplied by the publisher feed · Published Jun 25, 2026

Embed this episode

NOW PLAYING

EP023: From Vibe Coding to Enterprise AI

0:00 43:56

No transcript for this episode yet

We transcribe on demand. Request one and we'll notify you when it's ready — usually under 10 minutes.

No similar episodes found.

No similar podcasts found.

Frequently Asked Questions

How long is this episode of The Chief Customer Officer Podcast?

This episode is 43 minutes long.

When was this The Chief Customer Officer Podcast episode published?

This episode was published on June 25, 2026.

Can I download this The Chief Customer Officer Podcast episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.
URL copied to clipboard!