Table of Contents
Introduction
Introduction: The Post-Sale Problem
Part I - The 2026 CS Evolution
Ch 1: From Churn Insurance to Revenue Engine Ch 2: Post-Sale Unification Ch 3: The Role Evolution of the CSM
Part II - The Post-Sale Pipeline
Ch 4: Stage 1 - Identify Ch 5: Stage 2 - Align Ch 6: Stage 3 - Advocate Ch 7: Stage 4 - Intent Ch 8: Stage 5 - Net Revenue Close
Part III - Lifecycle Plays
Ch 9: Purchase and Welcome Play Ch 10: The Kickoff Play Ch 11: The Onboarding Play Ch 12: The First Value Play Ch 13: The Value Blocks Play Ch 14: The Sharing Insights Play Ch 15: The Alignment Meeting Play Ch 16: The Renew and Grow Play Ch 17: Supporting Plays
Part IV - Data, Automation and Scale
Ch 18: AI in CS - Judgment Over Templates Ch 19: Data Governance and One Data Spine Ch 20: Health Scoring That Actually Works Ch 21: Cross-Team Collaboration KPIs Ch 22: Proactive Capacity Planning
Part I: The 2026 CS Evolution
Introduction

The Post-Sale Problem

The post-sale problem hiding inside SaaS is not a lack of effort, intelligence, or tooling. It is the absence of an operating system.

For years, companies have invested heavily in the pre-sale motion. Sales organizations run with structure, rigor, and inspection. Marketing teams manage funnels, conversion rates, attribution models, and pipeline influence with precision. Product organizations use roadmaps, prioritization frameworks, release processes, and adoption analytics to guide execution. Every major function that drives growth operates inside a designed system.

Then the contract gets signed, and much of that operational discipline disappears.

The post-sale experience often becomes a collection of disconnected activities held together by the judgment and effort of individual people. Onboarding meetings happen. Training gets delivered. QBRs get scheduled. Health scores get updated. CSMs work incredibly hard to maintain relationships and keep customers engaged. Yet despite all of this activity, retention still feels unpredictable. Expansion remains inconsistent. Customers unexpectedly go dark. Executive teams struggle to forecast renewals confidently. Health scores frequently fail to match reality. Accounts that looked "green" suddenly churn.

Most organizations interpret these problems independently. One customer had onboarding issues. Another suffered from poor adoption. Another lacked an effective champion. Another was impacted by budget pressure or shifting priorities. Another simply was not a good fit.

But over time I began to realize these were not isolated operational failures. They were recurring patterns.

The same breakdowns appeared over and over again across completely different companies, customer segments, and products. Customers technically completed onboarding but never reached meaningful First Value. Champions loved the product but failed to align their own organization around it. Success criteria were discussed but never operationalized. Adoption plateaued after an initial burst of activity. QBRs reviewed historical usage but never created forward-looking alignment. Renewal conversations became reactive because the groundwork for strategic continuation had never actually been built.

What looked like unrelated customer problems were often manifestations of the same underlying issue: the customer was not progressing predictably through the post-sale journey.

That realization changed everything for me.

I stopped thinking about retention primarily as an outcome to measure after the fact and started thinking about it as a system of progression that must be intentionally designed, inspected, and managed long before renewal ever appears on a calendar.

Because churn rarely begins at renewal. It starts much earlier.

It starts in the messy first meeting after the deal closes when expectations are misaligned but nobody notices. It starts when onboarding focuses on task completion instead of customer momentum. It starts when technical go-live is mistaken for meaningful adoption. It starts when one enthusiastic champion is treated as organizational alignment. It starts when value is discussed abstractly but never operationalized into measurable outcomes that matter to the customer's business.

These moments matter because progression is cumulative.

A customer that reaches meaningful First Value builds confidence. Confidence creates momentum. Momentum encourages deeper adoption. Deeper adoption expands stakeholder engagement. Stakeholder expansion creates organizational alignment. Alignment builds executive relevance. Executive relevance transforms renewal from budget scrutiny into strategic continuation.

Each successful moment strengthens the next one. Each missed moment compounds downstream risk.

Activity is not execution. A CSM can log calls, update CRM records, complete tasks, and maintain a healthy relationship while the account quietly stalls underneath the surface.

The customer may still attend meetings. Usage may remain acceptable. Sentiment may appear positive. Yet critical progression moments never actually occurred.

And eventually the renewal becomes vulnerable.

Sales organizations already understand this way of thinking intuitively. They recognize that deals progress through stages. They understand that certain conditions must exist before opportunities advance. They inspect for recurring stall patterns. Weak champions, missing economic buyers, delayed procurement engagement, and lack of compelling events are treated as structural signals, not isolated anecdotes.

Nobody in sales says, "Every lost deal is unique." Patterns are expected. Pipeline inspection exists specifically to identify recurring progression breakdowns before opportunities are lost.

Post-sale organizations rarely operate this way today. Instead, churn is often analyzed narratively and retrospectively. The champion left. Budgets changed. Priorities shifted. Adoption declined. Implementation struggled. Those explanations are frequently true. But they are often the final expression of progression failures that began much earlier in the customer journey.

This book introduces a different way of thinking about the post-sale. It argues that retention behaves much more like a pipeline than most organizations realize.

Customers move through stages. There are required outcomes. There are critical inflection points that determine whether momentum strengthens or stalls. There are recurring progression failures that can be identified systematically. There are operational conditions that must consistently exist for renewal and growth to become predictable.

And once progression becomes visible, everything changes.

Even AI begins to fit differently into the model. Today, most AI applications in Customer Success are focused on acceleration — summarizing calls, drafting emails, improving note-taking, automating tasks. Those capabilities are useful, but they primarily make the current operating model faster. They do not fundamentally improve it. Because AI struggles in undefined environments. If there is no clear concept of what progression actually looks like, AI cannot meaningfully recognize whether a customer is advancing or stalling.

But once progression becomes explicit, AI becomes far more powerful. It can recognize when critical moments have not happened. It can identify accounts exhibiting recurring progression failure patterns. It can surface execution gaps long before renewal risk becomes visible. It can recommend next actions based on historical progression success. At that point, AI stops being merely a productivity layer and starts becoming an execution support system for the post-sale operating model itself.

Retention is not a department, a feeling, or a lagging metric. It is a system of customer progression that can be intentionally designed, operationalized, inspected, and improved.

This book is ultimately about creating that operating model. Not a collection of disconnected best practices. Not another playbook or health scoring methodology or framework that depends entirely on individual heroics. A system. One that creates clarity around what must happen after the sale, makes customer progression visible, and enables consistency, forecasting, coaching, and scale.

The chapters that follow move from foundational concepts into the mechanics of execution. Early sections explore why the modern post-sale model struggles to create predictability and why existing tools often fail to expose the real progression risks hiding beneath customer activity. From there, the book introduces the Post-Sale Pipeline and the critical inflection points that shape adoption, alignment, advocacy, renewal, and growth. As the framework becomes more concrete, the later chapters focus on the operational components required to scale the system: onboarding, First Value, alignment meetings, health scoring, forecasting, capacity planning, AI-assisted execution, and the organizational structure needed to make retention repeatable.

The goal is not simply to present ideas, but to offer a practical operating model that helps companies finally bring the same rigor, visibility, and predictability to the post-sale that already exists across the rest of the business.

Next chapter
Chapter 1: From Churn Insurance to Revenue Engine