EP015: Why CS Teams Are Building Their Own Stack cover art

EP015: Why CS Teams Are Building Their Own Stack

EP015: Why CS Teams Are Building Their Own Stack

Listen for free

View show details

Summary

Jay and Jeff swap real examples of building custom AI tools instead of buying software — a $1K brand video that beat $750K agency quotes, a content planner built in 35 minutes, and a renewal digest that surfaces customer context weekly with zero manual effort. Plus: why the CS platform category is stalling, and the difference between a service blueprint and a customer journey.

KEY TAKEAWAYS


  • AI collapses the agency middle layer: A CEO got $500K–$750K quotes for a brand video, spent $1K in AI credits instead, and got 70% of what he wanted in a weekend. The agencies only offered 10–20% discounts when asked to use AI themselves.


  • Fewer people = faster output: The Mythical Man-Month principle applied to AI: every person you add to a project adds communication overhead. The real superpower of these tools is reducing the number of people in the middle of a problem.


  • Build your content system, not just content: Jeff built an AI-powered content planner in 35 minutes — 9 posts/week, post-type by day, 40-idea backlog, status tracking, and a draft button that fires his LinkedIn writing skill. MVP in a morning.


  • CS cockpit over CS platform: The question isn't which CS tool to buy — it's whether you can build exactly what your team needs. Jeff's team built a weekly renewal digest from support tickets, emails, Slack, and call recordings in one day.


  • The CS platform category is stalling: The layer of workflows that's truly common across software companies is thinner than vendors want to admit. Domain-specific, product-specific nuance is where the real work lives — and that can't be bought off the shelf.


  • Service blueprint vs. customer journey: Service blueprint = what you need to do to interact with a company. Customer journey = how customers mature and get value. CEOs want to hear about the journey. CSMs need to stop confusing the two.

CHAPTERS

  • 00:01 - Raleigh, end of quarter, baby incoming
  • 02:43 - $750K agency quote vs. $1K AI video build
  • 05:15 - Building exactly what you need: Jay's HubSpot pipeline dashboard
  • 07:28 - The Mythical Man-Month and reducing communication layers with AI
  • 09:15 - Paying for expertise, not pixel-pushing
  • 10:24 - Jeff's AI content planner: built in 35 minutes on Cowork
  • 15:56 - How the draft button and LinkedIn skill work together
  • 17:46 - Hosting the planner: Cowork vs. Claude Code
  • 21:12 - The CS cockpit idea: custom workflow hub for CSM teams
  • 24:50 - Junction's interactive onboarding demo environment
  • 25:53 - Why the CS platform category is stalling
  • 31:41 - Service blueprint vs. customer journey
  • 33:28 - Team AI day: CS team builds a weekly renewal digest
  • 35:51 - "You just described Staircase AI" — and built it in a day
  • 37:44 - Why PlanHat over HubSpot
  • 40:59 - Slack account pulse bot: ping for an AI-written account summary


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_c
No reviews yet
In the spirit of reconciliation, Audible acknowledges the Traditional Custodians of country throughout Australia and their connections to land, sea and community. We pay our respect to their elders past and present and extend that respect to all Aboriginal and Torres Strait Islander peoples today.