Issue #24: The lifecycle blueprint I'd build first
Build With Me, Week Two
Welcome back to The Customer Continuum, Issue #24. You’re part of a small group of people who care about doing customer marketing well, and the fact that you open these is what makes building them worth the time. Thank you for being here.
On Friday afternoon I spent an hour with about thirty customer marketers in Mary Green’s Customer Marketing and Advocacy Weekly community. We walked through the agent blueprints I’ve been writing, the CLG Flywheel app, the copilot I gave away last week. The slides had numbers, screenshots, the works.
The most useful thing I told them wasn’t on any of those slides.
About halfway through, somewhere between explaining a build process and showing the next visual, I said the words “MD file” out loud. Mary jumped in right after to translate for someone in the room who hadn’t heard the term. Her advice was the cleanest version of the lesson I’ve heard anyone give: when you hear something you don’t recognize, jump past the “I don’t know how to do this” feeling and just go ask Claude. I followed her with the truth. A year ago I had no idea what a terminal was. I had no idea how to build anything technical. I just started from ground zero and asked questions.
The room thought I was advanced. The truth is I just started earlier than most of them. The capability gap that looks so wide right now is a willingness gap, and not really a knowledge gap. It’s the willingness to look stupid for ninety days while you figure out what an MD file is and why it matters.
Three signals from that afternoon pinned this down for me. Mary herself, who runs an entire community of customer marketers, admitted she opens the CLG Flywheel app and feels a little overwhelmed by how much there is to work through. Someone else in the room asked carefully whether companies are going to keep cutting these teams in half, and the honest answer is yes, with the survivors expected to vibe-code their way through what used to take a full ops team. A third asked whether companies are already expecting customer marketers to figure AI out without a tool budget, and that answer is also yes, it’s already here. The expectation is moving faster than the training is.
After the call ended, the thing that kept replaying in my head was how many of the people in the room walked away with energy but no first step. That's the gap I started this series to close. Every Thursday from here through the end of summer, a new piece of the Customer Continuum Copilot ships. Real files, real logic, fork it and run it. The point isn't to keep talking about building, I actually want you to build.
What I’m shipping this week
Since I’m asking you to start building, the only honest move is to start with you. Build With Me Week Two is the lifecycle pillar, the first of seven pillar modules that stack on top of the Customer Continuum Copilot base install from Week One. Each week of this series adds the next module. By the time we’ve shipped all seven, you’ll have a complete Copilot built in public, one pillar at a time. The file I’m dropping below is the agent blueprint I’d build first if I were starting a new customer marketing function tomorrow.
It names six lifecycle agents. Each watches specific signals and triggers specific actions. Together they replace the patchwork of manual onboarding nurtures, adoption nudges, save sequences, and renewal plays most teams stitch together by hand.
Onboarding Orchestrator designs and delivers a 90-day personalized journey for every new customer, segmented by persona, triggered by setup milestones. Customers who complete a structured journey hit value milestones about 30% faster than those outside one.
Adoption Signal Watcher continuously monitors product usage and flags adoption gaps before they turn into churn risks. This is the keystone. Every other agent in the blueprint reads from its output. Build it first.
Milestone Celebrator recognizes when a customer hits a value milestone and turns the moment into a story seed, an advocacy invite, or a referral. Most teams celebrate milestones at renewal time, by which point the customer has forgotten. Catching them in the moment compounds advocacy 3 to 4 times.
At-Risk Detector combines NPS, support escalations, login decline, and community signals into a single churn risk score and triggers a save sequence early. By the time most teams identify churn risk, the customer is already 90 days from non-renewal. This agent catches risk 60 to 90 days earlier.
Renewal Orchestrator manages the T-180, T-120, T-90, and T-30 sequence with value framing and risk sweeps. Renewals run on muscle memory in most companies, which is why GRR rarely improves over time. A structured orchestration with personalized value framing typically lifts GRR by 2 to 4 points.
Expansion Nudge detects expansion opportunities and surfaces them with peer-matched proof and an executive entry point. Expansion is where NRR lives. Most teams chase it through outbound, which converts poorly. The lifecycle approach surfaces customers already showing readiness signals and converts 3 to 5 times better.
The file linked below has the full detail for each agent: what it watches, what it triggers, where it pays back, and the order I’d build them in. The starter recommendation is the Adoption Signal Watcher first because it’s the foundation, then the At-Risk Detector second, because saving accounts has higher ROI than expanding them and most teams under-invest there.
One note on what you’re getting. The file below is the free starter version, structured to give you enough to start building. Paid Customer Continuum subscribers also get the Implementation Kit, which holds the operational depth: 20-plus lifecycle agents, JSON schemas, system-specific integration playbooks for Salesforce, Gainsight, Pendo, and ChurnZero, and 90-day rebuild templates. Both are real. The starter is enough to get things going; the kit is for teams ready to rebuild lifecycle end-to-end.
💎 For paid subscribers
The deeper file (01 - Lifecycle & Adoption.md) holds 20 lifecycle agents with full step-by-step build instructions, specific platform recommendations for Gainsight, Pendo, ChurnZero, and Salesforce, signal thresholds for each trigger, and the success metrics that prove it’s working. The free starter below is six of these in a tighter operational frame. Drive folder access details at the bottom of this issue. New paid subscriber? Reply to this email.
How to use it
The lifecycle.md file is designed to work three ways. As a Claude skill you drop into your Customer Continuum Copilot pack from last week. As a build spec you hand to your RevOps or go-to-market engineering team. As a benchmark you compare your existing programs against to find your gaps.
If you want to actually build something this weekend, here’s the shortest path:
Download the lifecycle.md file linked below.
Open Claude and paste the contents in as instructions, or add it to your skill folder alongside the copilot files from Week One.
Tell Claude which signals you actually have access to in your current stack: Salesforce, Gainsight or ChurnZero, Pendo or Mixpanel, your support tool, your community platform, your survey tool. Be honest about what you have and don’t have.
Ask Claude to rewrite the Adoption Signal Watcher logic using only the systems on your list. The blueprint is system-agnostic; the customized version is specific to your stack.
Take the customized version to your RevOps team as a requirements doc and ask what’s feasible in 30 days versus next quarter.
Build the smallest working version first. Ship one agent, validate it, then add the next.
Build With Me Week Three
Next Thursday is the Voice of Customer pillar. Seven pillars total, seven agent blueprints, all built in public over the next few months. By the end of the series you’ll have a complete Customer Continuum Copilot covering every pillar of customer-led growth, assembled module by module. The Voice of Customer drop stacks on top of the Copilot and the lifecycle file: it tells you what signals to surface that feed the Adoption Signal Watcher you’ll have built by then.
If you want to be ready for it, do one thing this weekend. Build the Adoption Signal Watcher in its simplest possible form. Ask Claude to write you a basic version that runs on a Google Sheet of customer accounts with three columns: last login date, feature adoption count, and most recent NPS score. That’s it. The fancy version comes later. Start ugly.
— Kevin
P.S. If this issue gave you something useful, forward it to one person who’s been waiting to start. That’s how this grows, one real reader at a time.
P.P.S. If you want the deeper paid version of what I’m building, the Implementation Kit holds the operational depth and ships to paid subscribers as each pillar drops. Subscribe at kevinkennethlau.substack.com.
The VP Accelerator is where I work one-on-one with customer marketers making the jump to the next level. If that’s where you’re headed, reply to this email and we’ll talk.
