EP023: From Vibe Coding to Enterprise AI
Failed to add items
Sorry, we are unable to add the item because your shopping cart is already at capacity.
Add to basket failed.
Please try again later
Add to wishlist failed.
Please try again later
Remove from wishlist failed.
Please try again later
Adding to library failed
Please try again
Follow podcast failed
Unfollow podcast failed
-
Narrated by:
-
By:
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
adbl_web_anon_alc_button_suppression_t1
No reviews yet