The Customer Success Plan Template for Saving Renewals at Risk
When the kickoff plan stops working
The renewal date is 90 days out. The champion left the account three weeks ago. Adoption has been flat since February. The procurement contact is unknown.
The CSM opens her customer success plan, the one she wrote at kickoff, and finds 14 sections that do not help her.
The kickoff plan was written for a different account.
A healthy one. One with a champion in place, a roadmap aligned, and a renewal that was 18 months away. The document on her screen is comprehensive, accurate, and useless for the situation she is in.
She needs a different document.
This post gives you the template for the document she needs.
A focused four-section plan built backward from the renewal decision, designed to be written in 60 minutes between meetings, and built to be readable in 5 minutes by the customer’s exec.
It is the recovery doc that comes after the kickoff customer success plan, when the renewal is at risk and the time to save it is short.
The template is at the bottom of this post for new subscribers.
Why the kickoff CS plan stops working at 90 days out
If you have ever tried to use a comprehensive kickoff plan to save a renewal in trouble, you already know why it fails.
Here are the four reasons, named clearly.
1. The kickoff plan assumes a healthy account
Every section in a standard customer success plan is structured around forward momentum.
Goals to hit. Milestones to clear. Stakeholders to map.
None of that structure helps a CSM whose account just lost its champion. A renewal at risk needs a document that names what broke, not what to build.
2. The 14-point structure is built for breadth, not depth
Comprehensive is the right answer at kickoff because the CSM does not yet know which dimension of the account will become the renewal blocker.
At 90 days out, she knows.
The plan should now go deep on three or four things, not stay shallow across fourteen.
3. The kickoff plan’s audience is the CSM and her account team
The renewal-risk plan needs to be exec-readable.
The customer’s VP, who may or may not have ever seen the kickoff plan, has to be able to scan the recovery doc in 5 minutes and understand what is being asked of her team.
Fourteen sections of CSM-facing detail does not survive that scan.
4. The kickoff plan is time-agnostic
It is a working doc with no expiration.
The renewal-risk plan is time-boxed. Every action in it is anchored to the renewal date, with 30, 60, and 90 day windows.
Without that time structure, the plan reads as another status update rather than a recovery campaign.
The 4-section renewal-risk CS plan
This is the structure. Four sections.
Each one has a defined audience, a defined output, and a clear relationship to the renewal date.
Cut any section and the plan stops working. Add a fifth section and it stops being readable in 5 minutes by an exec.
Section 1: Risk diagnosis
Three risks, no more. Ranked by their direct impact on the renewal decision, not by their visibility or how recently they surfaced.
Each risk gets one sentence describing what it is, one sentence of evidence, and a severity rating from the red-yellow-green health framework.
The temptation here is to list every issue on the account. Resist it. Three risks is what an exec will read. Eight risks is what an exec will skip.
Section 2: Recovery actions (next 30 days)
Each of the three risks gets a named recovery action.
Each action has an owner on the customer side and an owner on the vendor side. Every action has a date inside the next 30 days.
The reason the window is 30 days, not 90, is that 90-day plans rarely get executed. 30-day plans get executed because the timeline forces accountability.
If a risk cannot be acted on in 30 days, it does not belong in this section. It belongs in a follow-up plan that gets built after the renewal closes.
Section 3: Value re-proof plan
This is the section most CSMs skip and most exec-attended renewal conversations end on.
The customer’s VP is being asked to renew a contract that has not visibly delivered value in the last quarter.
She needs evidence before the conversation, not during it.
The value re-proof plan names the two or three artifacts that will be produced and shared with the customer side before the procurement conversation starts => an updated ROI summary, a case example from a peer team, a quantified outcome from the recovery actions in Section 2.
The work in this section is what makes the renewal conversation winnable.
Without it, the CSM walks into pricing negotiations with no evidence and gets discounted to keep the account.
With it, net dollar retention stays defensible because the renewal closes at or near list.
Section 4: Renewal path
The operational layer.
Who is the procurement contact, when does the procurement process start, what are the decision criteria the customer’s team will use, what pricing is being previewed and how.
This is the section the AE owns and the CSM contributes to. The procurement contact has to be named by the time this section is filled in.
If it is not, the first 30-day action in Section 2 is to identify her. The pricing preview language gets drafted here, not in the procurement meeting.
How to build it in 60 minutes
The renewal-risk CS plan is a working doc, but it is also a time-boxed one.
A CSM with a portfolio does not have a week to write a recovery plan. She has an hour between her morning standup and her afternoon QBR.
Here is how to fill the four sections in that hour.
15 minutes on Section 1 (risk diagnosis)
Open the account health record.
List every yellow and red flag from the last 90 days. There will be more than three. Rank them by direct renewal impact, which is a different ranking than “most recently surfaced” or “most visible to the customer.”
The top three go in the plan. The rest go in a parking lot for the next quarter.
20 minutes on Section 2 (recovery actions)
Each of the three risks gets one recovery action.
The action should be specific enough that someone on the customer side can commit to it in a 30-minute meeting.
“Re-engage executive sponsor” is not specific enough.
“Schedule a 30-minute meeting between the customer VP and our VP-CS, by Friday” is.
Owners go on both sides. Dates go on every line.
15 minutes on Section 3 (value re-proof plan)
Name two or three artifacts that will land with the customer side before procurement opens.
ROI summary, peer case example, quantified outcome from one of the recovery actions. Date each one. Assign each one.
This section is the one most CSMs skip when they are short on time. It is the section that makes the renewal conversation winnable, so it is the section to protect.
10 minutes on Section 4 (renewal path)
Pull procurement contact name from the AE.
If unknown, the first action in Section 2 changes to “identify procurement contact.”
Note decision criteria, target renewal date, and pricing position. This section is the operational handoff to the AE and should match what the AE has in the CRM.
Sixty minutes total. The plan is ready to send to the customer exec the same day it is built.
How to present it to the customer
The renewal-risk CS plan is not a working doc you maintain alone.
It is a recovery doc you present to the customer. Three rules govern the conversation that comes after the plan is written.
The customer exec is in the room, or the conversation does not happen
This is not a director-level meeting.
The decision to commit recovery actions has to come from the customer side at the level that can actually commit them. If the customer VP cannot attend a 30-minute meeting in the next two weeks, the plan does not get presented.
It gets sent as a one-page summary with a request for the meeting to happen before the procurement conversation starts.
The document is one page
The four sections in this post compress to one page when each section is two or three lines.
Not a deck. Not a long-form doc.
One page that fits on a screen during a 30-minute call. The detail sits in the working tabs of the Excel template, not in the document the customer sees.
The conversation ends with two owned actions on the customer side
Two owned actions, not three. Not five. Two.
Each one with a name and a date. If the customer exec leaves the meeting without committing to two specific actions, the meeting did not produce a recovery plan. It produced another status update.
This is the same rule that governs the QBR decisions section, and it works the same way here.
5 mistakes that kill renewal-risk plans
A short checklist before sending the plan to the customer side.
1. The plan tries to fix everything
Fix: pick three risks.
The other risks get a parking lot. They get worked after the renewal closes, not during the recovery window.
2. The plan is written for the CSM, not the customer exec
Fix: one-page rule. The CSM-facing detail goes in the working tabs of the template, not on the page the customer reads.
3. There are no owned actions on the customer side
Fix: every recovery action has a named owner from the customer team. If the customer side does not commit, the plan is a vendor monologue and the renewal will not close on time.
4. The plan is treated as a status update
Fix: lead with the recovery actions and the value re-proof plan. The risk diagnosis section is context, not the headline. Status updates do not earn exec attention. Recovery plans do.
5. The plan is built when the renewal is 30 days out
Fix: 90 days out is the operational window. 30 days out is the procurement window. The recovery plan has to land before procurement opens or the conversation will be about price, not value.
If you only have 30 days, the renewal pricing playbook is the right reference, not this one.
Get the renewal-risk CS plan template
The Renewal-Risk template includes the four-section plan, a risk diagnosis worksheet that auto-ranks risks by renewal impact, and a one-page exec summary tab that pulls live from the working sections. Built to be filled in during a 60-minute working session and presented in a 30-minute exec conversation.
I publish one Customer Success operating system and one career-track post every week. Free to read, free to subscribe.
Hakan Ozturk | Founder, TheCScafe.com