Podcast
CS SHIFT
Hosted by Nandi Dossou · EN
Welcome to CS Shift, the podcast that goes beyond retention with strategies for Customer Success that work in the new era.
I’m your host, Nandi Dossou, Customer Success executive, team builder, and passionate advocate for growth that’s both measurable and human.
On this show, we cut through the noise and focus on what actually works: how to lead your CS team from adoption to expansion, how to drive net revenue retention, and how to equip your people and yourself to thrive through it all.
Whether you're a CS leader under pressure to deliver growth, or an individual contributor ready to grow your impact, this is your space.
Let’s make the shift together.
12episodes
Episodes
Newest firstAll episodes
Sustaining Value of Digital Transformation Over Time
2w ago00:06:36Tap to summarize💡 Proving value once is good.Sustaining it over time? That’s where transformation becomes leadership.In the final episode of my series,🎙️ “From Promise to Proof: Sustaining Value Over Time,” I explore how to make value realization a living process — not a one-time project.You’ll learn how to:Track value over time with leading and lagging indicatorsEmbed governance and ownership to keep impact visible and accountableAnd build a culture of value where teams speak the language of outcomes, not activities
Transcribe →Turning Transformation Metrics into Financial Outcomes
3w ago00:09:20Tap to summarize📊 Strategy is inspiring. But numbers build credibility.In Episode 3 of my series on value realization, I share how to move from initiatives to impact by:Establishing credible baselines and defining realistic target outcomesTranslating performance metrics into financial impactBuilding a value and ROI model that earns executive trustI also share a real-world example of how to build your ROI model by the time you listen to the episode.When you can measure what matters, you don’t just talk about transformation — you prove it
Transcribe →Mapping, Measuring & Monetizing Value of Transformation
4w ago00:07:11Tap to summarizeIn this episode of my series: 🎙️ “From Promise to Proof: Mapping, Measuring & Monetizing Value”,I lay out the engine room of value realization:How to map initiatives to value drivers that matter to the businessHow to define baselines and target outcomes that are credible and actionableHow to build a solid ROI model that resonates with finance and leadershipIf Episode 1 set the stage, Episode 2 is where strategy turns into measurable impact.
Transcribe →A Practical Framework to Prove the Value of Digital Transformation
May 500:08:53Tap to summarize🚀 Digital transformation isn’t about adopting tools, it’s about delivering measurable business outcomes.In the first episode of my new podcast series,🎙️ “From Promise to Proof: A Practical Framework to Prove the Value of Digital Transformation”,I unpack:Why adoption ≠ valueThe common pitfalls teams face when trying to prove impactThe first two steps of a practical Value Realization Framework you can apply right awayIf you lead transformation, customer success, or enablement, this is for you.
Transcribe →Leading the Renewal Engine: Building a frictionless renewal motion
Apr 2400:07:57Tap to summarizeIn this episode, I share what I learned leading a CS organization where Customer Success owned the full customer relationship, renewal and expansion, while Sales focused entirely on new business. A deliberate organizational shift that changes everything about how you think about architecture.Based on my experience, I walk through four levers that make the system hold:Visibility that changes behavior. A consistent internal rhythm. Cross-functional clarity. Escalation that's designed, not improvised.The takeaway: when CS owns renewal and expansion, architecture isn't about managing handoffs. It's about giving CS the infrastructure to go the distance, and knowing exactly when to bring in support.
Transcribe →Leading the Renewal Engine: Start with People
Mar 1700:04:53Tap to summarizeHow do you actually build a renewal engine that grows retention and reduces churn?In this episode, I share how I approached it as a Director of Customer Success, starting with people, not process.From clarifying who leads renewals, to structuring the role of managers, building pipeline visibility, and defining escalation, this is a practical, experience-based approach to running enterprise renewals at scale.
Transcribe →NRR Is Broken Here’s How High-Performing CS Teams Fix It
Feb 2400:07:06Tap to summarizeNet Revenue Retention is one of the most important metrics in SaaS and one of the most discussed.It often sits with Customer Success.It’s influenced by many teams.And it’s rarely perfect.But at the end of the day, someone has to own the number.In this final episode of Rethinking Customer Success in High-Growth SaaS, I explore how high-performing CS organizations actually improve NRR , starting with a strong GRR foundation, designing expansion into the customer lifecycle, and using AI to make signals more visible and execution more consistent.If you want NRR to become predictable, not stressful, this episode is for you.🎧 Listen to Episode 4: NRR Is Broken Here’s How High-Performing CS Teams Fix It
Transcribe →From Chaos to Clarity: How to Structure a Scalable CS Organization
Jan 2900:11:30Tap to summarizeHow do you scale Customer Success without creating chaos?In high-growth SaaS companies, scaling Customer Success often leads to confusion, burnout, and inconsistent customer outcomes — not because teams lack effort, but because the operating model isn’t designed to scale.In this episode of CS Shift, part of the executive mini-series Rethinking Customer Success in High-Growth SaaS, I break down what a truly scalable Customer Success organization looks like and why hiring more CSMs too early often makes things worse, not better.You’ll learn:The 4 structural pillars every scalable CS organization needs before hiringWhen it actually makes sense to hire more CSMs — and when it doesn’tHow customer segmentation, role clarity, and lifecycle design drive repeatable performanceWhere CS Enablement fits, and why it’s a force multiplier at scaleThe leadership decisions that separate chaotic CS teams from predictable, high-performing onesIf you’re a CS leader, VP, or founder scaling a SaaS organization and wondering why growth feels harder than it should, this episode will help you move from reactive execution to structural clarity.🎧 Episode: From Chaos to Clarity: How to Structure a Scalable CS Organization
Transcribe →Fixing Churn : addressing the root causes and not the traditional diagnosis
Dec 1600:06:46Tap to summarizeLet me ask you something :When churn shows up…When renewals get defensive…When value realization slips…Is your first instinct to look at your CSMs?Because in high-growth SaaS, churn is almost never created by the CSM ; and it’s certainly not created solely by the CSM.In most cases, the CSM is simply the first person to see churn that was created much earlier in the lifecycle… or deeper in the organization.In Episode 2 of Rethinking Customer Success in High-Growth SaaS, I break down why traditional churn diagnosis fails, why blaming CSM performance is a leadership trap, and how fixing churn actually starts with fixing your operating system, not your people.If you want renewal cycles to stabilize and expansion to become predictable, this episode is essential.
Transcribe →CS Fragmentation: Why You’re Losing Customers Without Realizing It
Nov 2500:06:06Tap to summarizeIf churn is climbing…If adoption is unpredictable…If escalations feel personal instead of operational…Are you sure the problem is your customers?Because in most high-growth SaaS organizations, churn doesn’t start with the customer.It starts with fragmentation inside the Care & Success organization.In this first episode of Rethinking Customer Success in High-Growth SaaS, I break down the real cost of internal misalignment, how it impacts Net Retention, slows expansion, and burns out your teams and why fixing churn starts with fixing your operating system, not adding more CSMs.🎧 Listen to Episode 1: The Hidden Cost of CS Fragmentation
Transcribe →