Part I made the argument that retention behaves like a pipeline. Part II defined that pipeline: five stages, default probability weights, and stage advancement based on evidence that meets each stage's exit criteria. What Part II deliberately left abstract was the work itself. The plays were referenced as the work that helps create that evidence, 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 play creates the conditions for progress. The evidence shows whether the customer actually progressed.
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.
An inflection point is a moment in time when you have an opportunity to either build or block loyalty. Some happen in a meeting. Many happen when you are not in the room: a customer hits a wall in the product, has an aha, or quietly wonders whether the purchase was worth it. Recognizing these moments is your responsibility, not the customer’s.
What happens at an inflection point either blocks loyalty or builds it. A loyalty blocker is a barrier between your offering and the value the customer wants. It can be a deal breaker, but far more often it is a small annoyance that adds up over time: death by a thousand paper cuts. A loyalty builder is either a best practice someone on your team already uses or a response you design to counter a blocker. Every play in Part III is designed around the inflection point it serves, the blockers that show up there, and the builders that answer them.
At each inflection point, the design work has the same shape: decide what should change for the customer, design the play that helps create that change, decide how the team will know whether it happened, and decide what happens next based on what the evidence shows. The Post-Sale Journey Map lays out all eight inflection points and that model in one place.
This is the mechanic that connects Part III to Part II. When a play does its job and the customer makes the intended progress, they move 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. The evidence of that progress is what the pipeline can read. When it meets the exit criteria for an opportunity's next stage, the stage changes, the probability updates, and the forecast updates. When it doesn't, the play still served the customer, but the pipeline doesn't move.
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 its evidence is captured, the pipeline has something real to read.
The plays are not performed for the pipeline. The pipeline reads from the evidence the plays produce. That is why design matters more than documentation. A play that helps create 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 record that looks like evidence but cannot be trusted. And a play that is completed but does not create its intended outcome has not moved the customer at all, no matter what the checklist says. Both halves have to work.
The eight plays follow the customer lifecycle, but the lifecycle does not run in a straight line from purchase to renewal and stop. It moves through three phases, and one of them repeats.
The first phase is Align, a lifecycle phase, not the Align stage of the pipeline in Part II. Purchase & Welcome, Kickoff, Onboarding, and First Value happen once, at the start of the relationship. Their job is to launch the customer: confirm the decision, align on outcomes, get the solution ready, and produce the first meaningful win.
The second phase is Engage, and it is a loop. Value Blocks, Sharing Insights, and Alignment Meetings work together through the messy middle between First Value and renewal. An Alignment Meeting sets the next objective. Value Blocks break it into achievable steps. Insights steer the customer, recognize progress, and celebrate outcomes along the way. Then the next Alignment Meeting checks what changed and sets the next objective. A healthy customer moves through that loop several times a year.
The third phase is Achieve. Renew & Grow confirms the value the loop produced and turns it into the next commitment, and the anniversary is a moment to celebrate it. Then the customer goes back into the Engage loop for year two, and year three, and beyond. Year two does not repeat onboarding. It runs the loop with everything year one built: a known definition of success, proven Value Blocks, engaged stakeholders, and evidence. That is why a repeat renewal often moves faster than the first one.
How many times a customer moves through the loop, and how much of it involves people, depends on what they bought. A complex, higher-cost offering may cycle through the loop several times a year, with live Alignment Meetings, CSM-led Value Blocks, and insights tailored to each stakeholder. A narrower or lower-ACV offering may go around once or a few times a year, with much of the work automated or AI-assisted: a personalized video in place of a meeting, guided in-product steps in place of a working session, insights triggered by usage. The delivery changes. The motions do not. Every customer still needs a way to align on what they are trying to achieve, see what is working, and keep making progress toward value.
The plays are not rigid inside this structure. Sharing Insights does not wait for onboarding to finish. Value Blocks may begin before First Value is formally achieved. The cadence of Alignment Meetings flexes with the customer’s pace and complexity. What matters is that every inflection point has a designed motion behind it, and that the relationship keeps cycling instead of drifting.
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 draft for the CSM to review. 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 brief 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.