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 II: The Post-Sale Pipeline
Introduction

How the Post-Sale Pipeline Works

The pipeline does not require new data. It requires the discipline to capture what the plays are already producing.

Part I established that retention behaves like a pipeline: customers move through stages, and progression can be designed, inspected, and managed. Part II makes that pipeline concrete. It defines the five stages of Identify, Align, Advocate, Intent, and Net Revenue Close, and explains what must happen inside each one for an opportunity to advance.

Before the chapters that follow unpack each stage, three ideas need to be established clearly. They are the operating logic of the pipeline, and they will shape how every stage, every play, and every probability weight should be understood.

The plays serve the customer, not the pipeline.

The lifecycle plays exist because customers need them. Purchase & Welcome, Kickoff, Onboarding, First Value, Value Blocks, Sharing Insights, Alignment Meetings, and Renew & Grow all guide the customer from the moment of purchase toward the outcomes they bought. They create alignment, build confidence, deliver evidence of progress, and deepen the relationship over time. The plays are the operating work of Customer Success.

The pipeline is a byproduct of that work. When a CSM completes a play and logs the result, two things happen at once: the customer moves closer to the outcome they care about, and the pipeline captures that movement as a stage change, a probability update, and a forecasting signal. The plays are not performed for the pipeline. The pipeline reads from the plays.

This is exactly how a sales pipeline works. A sales rep does not hold a discovery call in order to move a deal from Stage 1 to Stage 2. The rep holds the call because the prospect needs it. The pipeline advances as a consequence. The same logic applies here. The CSM runs the play because the customer needs it. The pipeline records the result.

The renewal is the first opportunity in the pipeline. Expansion opportunities join it.

This distinction matters because it defines how the post-sale pipeline creates revenue, and how the two kinds of revenue move through the same stages differently.

Every account enters the pipeline with a renewal already in it. The renewal is guaranteed to exist from day one. It carries a fixed close date: the end of the contract. Its value is the current ARR. It is the floor. And it does not need its own commercial motion, because the lifecycle plays are its motion. When the plays execute consistently, the renewal advances through the stages as a byproduct of work already underway. The customer reaches First Value. Value Blocks create evidence of progress. Alignment Meetings keep the relationship pointed at the right outcomes. Renew & Grow brings the accumulated evidence together. The renewal is secured by the system, and the pipeline shows exactly where that work stands.

Expansion opportunities are different. They are new revenue. An upsell identified during a Sharing Insights play. A cross-sell that surfaces in an Alignment Meeting. A new business unit that appears when a champion introduces a peer. Each of these is a distinct opportunity that enters the pipeline at Identify whenever it emerges and moves through Align, Advocate, Intent, and Net Revenue Close on the strength of its own logged play completions.

Speed is not a property of the opportunity type. It is a property of how many stage conditions the account has already satisfied. A first-term renewal is often the slowest opportunity in the pipeline, advancing in lockstep with the customer's own progression across the term. A repeat-cycle renewal often moves quickly, because it inherits what the relationship has already built. Alignment, advocates, and evidence carry forward, and the early stages clear almost immediately. Expansion opportunities move at whatever pace the account's existing conditions allow.

A single customer may have one renewal and two or three expansion opportunities moving through the pipeline at once. The renewal is the floor. The expansion opportunities are the growth. The pipeline tracks both. The plays advance both.

Probability weights are fixed per stage. What varies is the play sequence.

The pipeline's forecasting model stays simple because the math does not change by account tier, segment, or complexity. An opportunity in Align carries the same probability weight whether it belongs to a high-touch enterprise customer or a digital SMB account. The difference is operational, not mathematical. A high-touch account may require a formal Alignment Meeting with executive stakeholders to advance. A low-touch account may advance through a self-service milestone or an automated check-in. The plays change. The stages do not. The probabilities do not.

This is what makes the model defensible to a CRO. The pipeline is not a custom scoring system that needs to be explained differently for every segment. It is a shared structure with consistent definitions and consistent math, delivered through segment-appropriate motions.

The chapters that follow make the pipeline concrete. They move through the five stages in order, from Identify through Net Revenue Close, and define what must happen inside each one for an opportunity to advance. Each stage is built around the same mechanic: play completion at a defined inflection point triggers the stage change, updates the probability, and creates the forecasting signal. The work that moves the customer forward is the same work that moves the pipeline forward.

As the stages progress, the relationship deepens. Early chapters focus on the foundational work: confirming the reason for purchase, guiding the customer toward First Value, and establishing the evidence that the solution is creating real progress. Later chapters explore how that evidence becomes organizational momentum, how momentum converts into commercial intent, and how intent becomes committed revenue. Along the way, expansion opportunities surface naturally, not because the team is hunting for upsells, but because the plays are creating the conditions where growth becomes the customer's own next logical step.

The goal is not to add a forecasting layer on top of Customer Success. It is to show that the operating work CS already does, when designed well and logged consistently, is the forecasting layer. The pipeline does not require new data. It requires the discipline to capture what the plays are already producing.

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 4: Stage 1 — Identify