EP031: The Segmentation Grid Behind Every CS Strategy
Unable to add items
Sorry, we're unable to add the item because your cart is already full.
Add to basket failed.
Please try again later
Add to wishlist failed.
Please try again later
Failed to remove from Wish List.
Please try again later
Adding to library failed
Please try again
Unable to follow podcast
Unable to unfollow podcast
-
Narrated by:
-
By:
Jay walks through the customer segmentation workshop he ran this week — a deliberately simple grid of lifecycle stage, engagement model, and health status that gets leaders to say what should happen in the business before anyone argues about tools. Plus: what "harness lock-in" means for your AI stack, and why the customer quote you read never lands like the one you watch.
KEY TAKEAWAYS
- Segment before you strategize: Product attachment, lifecycle stage, engagement model, health status — four inputs, and every row of the grid is a real situation to solve.
- Managed vs. scaled: Either an account has a named human or it doesn't. Pick the threshold, then design both sides.
- Red/yellow/green, not a health score: Sponsor, usage, sentiment, billing. One turns yellow, the account turns yellow — and you know what to go fix.
- Business requirements before playbooks: Ask leaders what should happen in each segment, not which system does it. Tools execute a plan; they don't replace one.
- Why CS platform deployments fail: The grid was never filled out. Teams buy a product hoping to get a strategy.
- Strategy is putting things in buckets: Rumelt's diagnosis, guiding policy, coherent action — one segment at a time. "Not strategic" usually means working hard without buckets.
- Bumpers, not scripts: A playbook keeps people in the lane. Word-for-word scripts belong in a contact center, not on the front line.
- Simple travels: The bigger the team, the worse the game of telephone. Simple to communicate is what actually spreads.
- Make the customer voice watchable: Jeff swapped text quotes in Slack for links to the recording — and the whole business started listening.
- Get executives back in the room: Exec sponsors, ride-alongs, 50 calls in 50 days. CFOs are the best execs to put on a customer call.
CHAPTERS
- 00:00 - Apex habits and why consistency compounds
- 03:23 - Jeff cheats on Claude and tries Codex
- 06:04 - Model vs. harness: the real lock-in problem
- 08:02 - Why enterprises can't move at personal-project speed
- 10:53 - 87 out of 100 people have never touched AI
- 11:44 - The skills AI doesn't replace: trust, transparency, relationships
- 12:39 - Turning customer quotes into watchable clips
- 14:29 - Ride-alongs, exec sponsors, and 50 calls in 50 days
- 18:51 - Inside the segmentation workshop
- 21:07 - Engagement model and the red/yellow/green grid
- 23:33 - Business requirements before playbooks
- 27:35 - Bumpers on a bowling lane, not word-for-word scripts
- 33:02 - Segmentation as a microcosm of strategy
- 37:25 - Why CS platform deployments fail
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