EP030: Agent-First Customer Teams
カートのアイテムが多すぎます
ご購入は五十タイトルがカートに入っている場合のみです。
カートに追加できませんでした。
しばらく経ってから再度お試しください。
ウィッシュリストに追加できませんでした。
しばらく経ってから再度お試しください。
ほしい物リストの削除に失敗しました。
しばらく経ってから再度お試しください。
ポッドキャストのフォローに失敗しました
ポッドキャストのフォロー解除に失敗しました
-
ナレーター:
-
著者:
Jeff Breunsbach shipped three things in one week—a community platform, a Claude-built CSM training academy, and an agent-powered internal wiki. He and Jay Nathan unpack the Karpathy-inspired philosophy of designing knowledge systems for agents instead of humans, why the engineering bottleneck has moved to customer success, and how to map product usage to P&L outcomes a CFO can see.
KEY TAKEAWAYS
- Design for agents, not humans: Stop forcing your knowledge into Notion or databases. Build in markdown files on GitHub—agents work natively on file structures, and your team gets a custom UI on top.
- The self-updating wiki: Three agents (writer, reviewer, verifier) continuously maintain your knowledge base by listening to Slack, support tickets, and email—so humans stop doing the updating.
- Build a learning loop: Jay logs what he edits vs. what the AI wrote, and the agent learns from the diff. That's the difference between a task tool and one that gets continuously smarter.
- One wiki powers everything: A live internal wiki can drive your CSM academy, customer-facing docs, and onboarding—without a dedicated writer for each output.
- The bottleneck has moved: AI eliminated engineering as the constraint. Now go-to-market teams and customers can't keep up with what's shipping. That's the new problem to solve.
- Feature velocity ≠ value: Shipping more faster can increase churn if customers can't absorb it and build an internal ROI story.
- Map usage to the P&L: Jay's framework—leading indicator → lagging indicator → KPI—connects product usage to financial outcomes a CFO can see.
- Pricing model literacy: The shift from seat-based to consumption or outcome-based pricing has real gross profit and AI inference cost implications CS leaders must understand.
CHAPTERS
- 00:00 - Welcome & Jay's CCO Summit trip to Boston
- 01:30 - Why in-person still matters for team chemistry
- 03:00 - Launching Uncommon community + vector databases
- 05:30 - The Claude-built CSM training academy
- 08:00 - Agent learning loops: the lessons-learned file
- 09:30 - The Karpathy-inspired agent-first internal wiki
- 13:00 - Designing for agents, not humans
- 15:30 - The autonomous CRM vision
- 17:00 - One wiki powering the whole org downstream
- 20:00 - Jobs aren't disappearing—they're shifting
- 21:00 - P&L literacy gap at the CCO Summit
- 24:00 - The new bottleneck: go-to-market teams
- 26:00 - Feature velocity vs. the 1-degree problem
- 29:00 - Teaser: consumption vs. outcome-based pricing
- 32:00 - Jay's leading → lagging → KPI framework
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
まだレビューはありません