Days 1–30: establish the foundation
I begin by defining the customer lifecycle: Handoff, Onboarding, Adoption, Steady State, Renewal and Growth. Each stage needs an owner and a clear transition into the next one.
I then make the account context visible in a simple working record: account, segment, assigned CSM and current lifecycle stage. The point is to create a shared reference for the processes that follow.
Define first value
I name the first meaningful customer milestone in specific, measurable terms. The onboarding tracker then shows the milestones, ownership and expected timing needed to reach it.
Start the management cadence
I establish weekly CSM conversations and an operating review. Those meetings give handoff issues, stalled milestones and ownership gaps a place to surface.
At the end of the first month, I review what has happened in real accounts. I check that the handoff process is in use, refine unclear definitions and identify the data available for health scoring. The foundation is ready when the process can be used consistently.
Days 31–60: add measurement and renewal visibility
I begin KPI tracking with time to first value, product adoption and stakeholder engagement. I establish baselines for net revenue retention, gross revenue retention and logo retention from the available trailing 12-month data.
I introduce the health scorecard manually, with input definitions that can be discussed and calibrated. The weekly cadence now has a consistent way to inspect changing account risk.
Make the renewal calendar visible
I record contract end dates, identify accounts within 90 days of renewal and use the account evidence to establish the appropriate renewal path. The internal health review happens before the customer conversation.
Connect CS with Sales and Product
I establish reviews every two weeks with Sales and Product, then run the first monthly portfolio review. These discussions should move relevant account information to the people who can act on it.
By the end of this phase, the operating cadence should explain which accounts need attention, why and who owns the response.
Days 61–90: use the evidence in broader conversations
I prepare the first executive report using the data established in the earlier phases. I want leadership to see portfolio health, retention and growth outcomes, and the account-level drivers behind them.
I start business reviews with a small set of strategic accounts. The review sequence begins with customer priorities, then moves through evidence, blockers and recommendations to agreed next steps.
Recognize supported expansion signals
I look for usage approaching existing limits, interest from a new department, requests for additional capabilities, strong account health and executive plans that create a relevant use case. These signals start an investigation; the customer's priorities and value evidence determine the conversation.
I end the cycle with a retrospective. I review which processes are being used, where the definitions still cause confusion and what the next quarter should address.
Keep premature work out of the sequence
I make deferred work explicit so it does not compete with the foundations:
- Health automation: first run the model manually and inspect what the scores mean.
- Digital engagement: first understand the human-led motion and the moments it needs to support.
- Platform selection: first run the operating rhythm for a cycle so the requirements come from experience.
- Customer advisory work: first build the relationships and a functioning business review cadence.
- More elaborate value analysis: first gather customer outcome evidence through the reviews.
I revisit these decisions at the end of the cycle. Deferral needs a reason and a review point, so that the next step follows from what has been learned.
Use completion criteria to hold the sequence together
I treat each phase as a dependency for the next. The first phase creates ownership and a place to review the work. The second adds consistent evidence and a response to account changes. The third uses that evidence in executive, customer and growth conversations.
If a phase is not functioning, I address the gap before adding more process. Health scoring without a review cadence produces numbers without follow-through. Executive reporting without consistent definitions produces a presentation that cannot explain the accounts behind it.
The goal of the first cycle is a usable operating rhythm: clear ownership, visible customer progress, earlier risk discussions and decisions that carry through to the next review.
How does this connect to the problem you’re working on?
Start a conversation