Part I made the argument that retention behaves like a pipeline. Part II defined that pipeline — five stages, fixed probability weights, stage advancement triggered by play completion at defined inflection points. What Part II deliberately left abstract was the work itself. The plays were referenced as the engine that moves the pipeline, but they were not yet unpacked.
Part III unpacks them.
The lifecycle plays are the operational core of the post-sale operating system. They are the motions a team executes with customers — not because the pipeline demands it, but because the customer needs it. The pipeline captures the result. The play creates it.
Most post-sale teams already do some version of the work these plays describe. They run kickoffs. They onboard customers. They share usage reports. They hold quarterly reviews. They manage renewals. The activity is not new.
What is usually missing is the design.
A meeting can be good or bad depending on who runs it. A play can be designed, taught, supported, measured, and improved regardless of who runs it. The difference is not effort — it is architecture. A well-designed play defines the trigger that starts it, the sequence of motions inside it, the assets that support it, the outcome it is supposed to produce, and the way the team knows whether it worked. When a play has that structure, it becomes coachable, inspectable, and repeatable. When it does not, it depends on the memory, energy, and seniority of whoever happens to own the account that week.
Every play in Part III follows the same operating structure. Each chapter defines the canonical play — the designed motion, the critical assets, the AI layer that reduces friction, and the measurement standard that makes execution visible. The structure is consistent so the team can learn one play and apply the pattern to the next.
This is the mechanic that connects Part III to Part II. Every time a play is completed and the result is logged, two things happen simultaneously. The customer moves closer to the outcome they care about — a successful onboarding, a first meaningful win, a stronger alignment with their own organization, a confident path to renewal and growth. And the pipeline records that movement as a stage change, a probability update, and a forecasting signal.
The CSM does not run the play for the pipeline. The CSM runs the play for the customer. But if the play is designed well and the result is captured, the pipeline takes care of itself.
The plays are not performed for the pipeline. The pipeline reads from the plays. That is why design matters more than documentation. A play that creates the right customer outcome but is never logged produces value for the customer and nothing for the forecast. A play that is logged but poorly executed produces a pipeline signal that cannot be trusted. Both halves have to work.
The eight plays in Part III are sequenced around the customer lifecycle — from the moment of purchase through renewal and growth. But the sequence is not rigid. Some plays repeat. Some run in parallel. Some overlap. The Sharing Insights play does not wait for onboarding to finish. Value Blocks may begin before First Value is formally achieved. Alignment Meetings may accelerate or slow depending on the customer's pace and the complexity of the engagement.
The lifecycle is a designed progression, not a conveyor belt. The plays create a path through the relationship that is intentional without being inflexible. What matters is that every inflection point in the customer journey has a designed motion behind it — and that motion is supported by structure, assets, measurement, and an AI layer that reduces the friction of doing it well.
Every play chapter includes an AI layer. This is deliberate. The plays were designed for a world where AI is a working tool, not a future possibility. But the AI layer is not about automation for its own sake. It is about removing the friction that keeps plays from running consistently across the full book of business.
AI can turn handoff notes into a personalized welcome before the CSM has read the full file. It can draft a kickoff brief from scattered CRM data. It can right-size a First Value target from a broad customer goal. It can surface the most meaningful insight to share this week. It can prepare a renewal readiness scan from a year of accumulated evidence. In every case, the CSM still owns the judgment. AI reduces the preparation time so that judgment can be applied more consistently, to more customers, at more moments.
The pattern is the same in every chapter: AI handles the synthesis and the starting point. The CSM handles the relationship and the decision.
The chapters that follow move through the lifecycle in sequence. They begin with the Purchase & Welcome play — the moment the pipeline opens — and progress through Kickoff, Onboarding, First Value, Value Blocks, Sharing Insights, Alignment Meetings, and Renew & Grow. A final chapter covers the supporting plays — Key Contact Change and Offboarding — that protect the lifecycle when the relationship changes shape. Each chapter is designed to be read in order but used independently. The structure is consistent. The execution adapts to the customer in front of you.
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.