What Is Moving in Customer Success and CX, Week by Week
A hand-curated read on the shifts that matter: pricing models, operating patterns, tooling moves, and the discourse, each with one line on what I think it means. Updated weekly, archived permanently, so a claim made in October can be checked in March. No feeds, no automation deciding what matters.
Latest edition: October 9, 2026 · 1 edition archived
Outcome-based pricing moves from panel talk to order forms
Vendors are pricing AI agents per resolved ticket and per completed task. Once the invoice counts outcomes, Customer Success owns the number on it.
Outcome-based pricing, defined →Seat compression is becoming the renewal conversation
Accounts are renewing happier and smaller at the same time, because AI did the work of the seats that left. Retention math built on headcount stops telling the story.
Seat compression, defined →Champion job-change tracking goes mainstream
The tooling now watches your champions move companies. That is two signals at once: an account newly at risk, and a warm door opening somewhere else.
Champion tracking, defined →Support orgs are quietly deleting tier one
Shadow-mode pilots are flipping to autonomous for the password-reset class of contacts. The differentiator now is the handoff, not the deflection rate.
The handoff cliff →About the Radar
What is the CS/CX Radar? +
A weekly, hand-curated list of what is actually moving in Customer Success and CX: pricing model shifts, operating patterns, tooling moves, and the discourse, each with a one-line read on what it means. The homepage shows the current week; this page archives every edition permanently, so the calls can be checked against what happened.
How are the items chosen? +
By a person reading the space, not by a feed. Sources include the operator communities and newsletters, vendor announcements and pricing changes, hiring patterns, and what comes up in real customer and candidate conversations. Some weeks carry three items instead of five, because a padded radar is worse than a short one.
How often is it updated? +
Weekly, with the date shown taken from the data file itself rather than typed by hand, so the page can never claim freshness it does not have. If a week genuinely brings nothing worth your attention, the radar says so by staying short rather than inventing movement.
Why keep the old weeks? +
Because a trend call is only worth something if it can be checked later. The archive is the accountability: what was flagged in October is still here in March, right or wrong. It also turns the radar into a running record of how the CS and CX space actually shifted, quarter by quarter, in one place.