Table of Contents
Preface
Why I Wrote This Book
Introduction
Introduction: The Post-Sale Problem
Part I - From Function to System
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
Part II Introduction 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
Part III Introduction 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
Part IV Introduction 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
Conclusion
Running the System
Part I: From Function to System
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. 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.

Churn rarely begins at renewal. It begins much earlier, and it can start when:

The entry point differs. The pattern does not, because progression is cumulative.

Think about a piece of technology you've fully adopted, whether at work or at home. Chances are it solved a meaningful problem almost immediately, even if it was a small one. That early success gave you confidence to invest a little more time. You learned something new, solved the next problem, and gradually the product became part of how you worked.

That progression didn't begin when you experienced value. It began much earlier, the moment you believed you were understood, could see what success looked like, understood what was expected of you, and felt confident you were making the right decisions. Every meaningful step changed what you believed about the journey ahead.

Adoption rarely happens all at once. It builds through a series of small moments that strengthen belief. Each one creates just enough momentum to pull the customer toward the next. Break that momentum, and progression stalls.

That's when I realized something I had never been taught.

Customers don't progress primarily through activities. They progress through beliefs.

Of course, we can't directly observe belief. We observe behavior. But behavior is the outward expression of belief, and only a small number of behaviors actually matter, because they signal that something has changed in how the customer thinks about the relationship. Customers who believe they're making progress act differently than customers who are quietly losing confidence. They introduce new stakeholders, invest more of their own time, champion the initiative internally when you're not in the room. They prepare for procurement before you raise it, and plan what's next instead of waiting to be told. The tell is cost. These aren't things a customer does to be polite; they spend time, capital, or internal credibility they'd only spend if something had genuinely shifted. That's what separates a signal from noise. Those behaviors aren't the progression itself. They're the evidence that progression is happening.

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 became vulnerable.

Sales organizations already understand this way of thinking. Deals move through defined stages. Certain conditions must exist before opportunities advance, and recurring stall patterns are treated as structural signals rather than isolated anecdotes. Weak champions, missing economic buyers, delayed procurement engagement, and the absence of compelling events are all recognized as predictable reasons deals fail.

Post-sale organizations rarely operate with the same discipline. Churn is often explained retrospectively through narratives: the champion left, budgets changed, priorities shifted, adoption declined. Those explanations may be true, but they are usually 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.

The mechanics mirror what sales already does. Deals advance when defined activities are completed and inspected, and customers can advance the same way. And because the pipeline runs on execution the team already logs, not on usage telemetry, it works even in organizations convinced they don't have the data for it. The chapters ahead show exactly how.

And once progression becomes visible, everything changes.

Even AI fits differently into this model. Today, most AI in the post-sale is focused on acceleration: summarizing calls, drafting emails, automating tasks. Useful, but acceleration only makes the current way of working faster. AI struggles in undefined environments: without an explicit model of progression, it cannot tell whether a customer is advancing or stalling. Once progression becomes explicit, that changes. AI stops being a productivity layer and starts becoming an execution layer for the post-sale 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.

Reader Hub
Question on this chapter, or ran the play?

Ask me directly, or tell me what happened when you tried it. The best questions get answered in the open, and results from the field shape the next edition.

Ask or give feedback →
Next chapter
Chapter 1: From Churn Insurance to Revenue Engine