The 47-tab spreadsheet problem

Quarter start. The VP of Customer Success sits down to plan NRR for the next 90 days. Her CFO is asking for the number in two weeks. Her CEO is watching the board update on Q3 retention.

The CRO is grading her on the same metric.

Her inputs are scattered. The expansion pipeline lives in Salesforce.

The renewal forecast lives in a different sheet maintained by RevOps. Account health sits in Gainsight. The five accounts the team has been quietly working in recovery mode are in a Slack DM with the AE.

The board target landed in her inbox a week ago without much explanation of how Finance arrived at 115%.

What gets built is a 47-tab spreadsheet pulled together the night before the CFO sync. That spreadsheet is not a planning doc.

It is a reporting artifact written under duress, designed to survive the meeting where it gets presented, then discarded.

This post gives the VP-CS the planning doc that the spreadsheet was supposed to be.

A 4-tab NRR Bridge that maps the quarter’s expansion plan and at-risk renewals to a live NRR percentage, runs four sensitivity scenarios automatically, and produces the one-page summary her CFO actually wants to read.

Built to be filled in during a 60-minute working session. Built to hold up when the CFO starts asking which assumptions the plan depends on.

The free template is at the bottom of this post for new subscribers.

Why most NRR planning fails before quarter-end

Four reasons the typical NRR plan does not survive the quarter intact.

The expansion pipeline is treated as committed when it is mostly Discovery

A 40% expansion pipeline at discovery stage converts to a 12% expansion result.

The VP-CS who books all of it into next quarter’s plan ends the quarter with a gap between her plan and her actual delivered NRR.

The fix is structural: the planning tool has to distinguish Committed plays from Discovery plays, and the bridge math should only confidently count Committed.

At-risk renewals are not in the plan because they have not been officially named

Every VP-CS knows which 3 to 5 accounts are at risk for the quarter.

Few formal NRR plans name them. The risk does not disappear because it is not in the spreadsheet.

It just surprises everyone at quarter-end, when the CFO asks why the bridge missed by $400K and the answer is a Stark Industries renewal that nobody had formally tracked since week 2.

The plan is not sensitivity-tested

A 115% NRR plan that depends on every expansion play closing AND zero red-risk churn is not a plan.

It is a hope.

A real plan survives at least one missed expansion AND one red-risk loss. The bridge that shows you exactly where it breaks is the bridge the CFO trusts.

The bridge that hides its dependencies is the bridge that gets relitigated every two weeks for the rest of the quarter.

The plan is built for CS, not for Finance

The CFO does not want adoption metrics.

She does not want stakeholder maps. She does not want a Gainsight dashboard screenshot.

She wants the bridge: starting ARR, the additions, the subtractions, the ending ARR, the NRR percentage, the variance against target.

Anything else gets cut from the board deck before it lands in front of the CEO.

The VP-CS who builds the plan in CS-language ends up rebuilding it in finance-language anyway, on the day of the CFO sync.

The 4-section NRR Bridge Plan

This is the structure. Four tabs.

Each has a defined purpose, a defined audience, and a defined relationship to the bridge math. Cut any tab and the plan stops working as a CFO-readable doc.

Add a fifth tab and it stops being maintainable in 60 minutes.

Tab 1: NRR Bridge

This is the doc the CFO reads.

The math is unambiguous. Starting ARR comes from Finance and represents the existing customer base at quarter start (new business is excluded by design, because NRR is a same-cohort metric).

Expansion rolls up live from the Expansion Plan tab and only counts plays that are not cancelled. Churn rolls up live from the Risk Inventory tab and only counts confirmed losses.

Contraction (discounts, seat reductions) is manually entered because it surfaces during renewal negotiation and is rarely planned in advance. Ending ARR calculates.

NRR percentage calculates against starting ARR.

Below the main bridge sits a sensitivity table running four scenarios: plan as filed, expansion slips 20%, one top-3 red-risk account turns into churn, and worst case (both at once).

The CFO sees all four scenarios on one tab and asks the question every CFO asks: which scenario should we be planning against?

Tab 2: Expansion Plan

This is the working layer for the VP-CS and her AE counterparts.

Each row is a named expansion play: which account, what type of play (seat expansion, cross-sell module, tier upgrade), who owns it (CSM or AE), the expected uplift in dollars, the current status (Committed, Discovery, At risk, Cancelled, Closed), and the target close date.

Total expansion rolls up to the bridge with cancelled plays excluded automatically.

The status field is the discipline mechanism: a play at Discovery should not be modeled as a committed contribution. The conversation in the next leadership meeting becomes “which 3 Discovery plays need to move to Committed this month to protect the bridge.”

That conversation is operational.

The kind of conversation a QBR Operating System is built to drive when the QBR section on roadmap and expansion runs correctly.

Tab 3: Risk Inventory

Named at-risk renewals.

Each row: the account, the renewal date, the recovery plan owner, the ACV at risk, the current status (At risk, In recovery, Saved, Lost), and the severity (Red, Yellow, Green). Lost status feeds the churn line in the bridge automatically.

Active risk (At risk + In recovery) shows the dollar value still at stake. Red severity count surfaces how concentrated the risk is.

The Risk Inventory is the tab the VP-CS reviews with the renewal-risk recovery work her CSMs are running.

Each row of this tab should have a corresponding Renewal-Risk CS Plan maintained at the account level. The Bridge gets the headline. The recovery plan does the work.

Tab 4: README

The cadence.

When to build the bridge, when to update it, when to review it.

The 60-minute build at quarter start. The two-week refresh through the quarter. The lock at quarter end and the variance analysis that feeds next quarter’s plan.

The audience for each tab. The relationship between this template and the rest of the CS operating system.

How to build the bridge in 60 minutes

The VP-CS does not have a week to write the plan. She has an hour before the CFO sync.

Here is how the 60 minutes get spent.

15 minutes on Tab 2 (Expansion Plan)

Pull the current pipeline from Salesforce filtered to existing customers.

List the top 15 to 20 plays. For each, set the status field honestly. Committed is reserved for plays where the customer has verbally or contractually agreed and the timeline is in the next 90 days.

Discovery is everything else.

The temptation here is to round Discovery up to Committed because the AE is bullish. Resist it. The bridge gets stronger when the inputs are honest, not when they’re optimistic.

20 minutes on Tab 3 (Risk Inventory)

Name the 5 to 8 at-risk renewals from the next 90 days.

The list will be longer than the VP-CS wants.

Each row gets an ACV from the customer record, a severity from the red-yellow-green account health framework, and a named owner running the recovery plan.

If an account is in active recovery, the owner has a per-account renewal-risk plan she is working.

If the account is at risk but not in active recovery, the recovery plan is the first action item out of this exercise.

10 minutes on Tab 1 (NRR Bridge)

Set Starting ARR from Finance.

Set Contraction from the renewal forecast assumption (typically 1 to 3 percent of starting ARR for discount and downsell pressure).

Set the NRR target from the board document. Expansion auto-pulls from Tab 2.

Churn auto-pulls from Tab 3. The Ending ARR calculates. The NRR percentage calculates.

The status against target (”At or above target” / “Below target”) calculates.

15 minutes on the sensitivity table at the bottom of Tab 1

Four scenarios run automatically: plan as filed, expansion slips 20%, one top-3 red-risk turns into churn, worst case.

Read across the four. The question to answer: which scenario should we be planning against?

The 60-minute output is not the final doc.

It is the working draft that gets reviewed in the next CS leadership meeting, refined with input from the AE side and the RevOps side, and locked at the end of week 2.

The locked version is what gets sent to the CFO.

The foundational customer success plan at the per-account level is what the Expansion Plan and Risk Inventory tabs roll up from.

Bridge planning works when the per-account plans underneath it are real.

How to present the bridge to the CFO

The Bridge is not a CS doc. It is a finance doc owned by CS.

3 rules govern how the CFO conversation goes.

1. Lead with the NRR percentage, then the variance against target, then the sensitivity scenario that breaks the bridge

The CFO reads top-down.

She wants to know what landed, what it means against target, and what could change it. The order matters because if she only has 5 minutes, those are the three things she needs to walk out with.

Adoption metrics and stakeholder maps belong in the QBR, not in the bridge conversation. The bridge conversation is short and dense by design.

2. Name the risks explicitly, including the ones that look bad

• Wayne Enterprises is in recovery.

• Stark Industries is at risk.

• Weyland-Yutani is lost.

The CFO already suspects which accounts are flagged because she sees the renewal dates and the ACV math.

Pretending the risks are not real is the fastest way to lose her trust. Naming them with the recovery plan attached is the fastest way to build it.

The Risk Inventory tab does this work directly.

3. End on the sensitivity scenario, not on the headline NRR number

“We are forecasting 114% NRR against a 115% target. If we miss the Globex expansion AND Stark Industries goes to churn, we land at 99%. Here is what we are doing in the next 30 days to protect against that scenario.”

This is what the CFO actually wants to know.

The plan that names its downside earns trust. The plan that does not gets relitigated every two weeks until quarter-end.

For the CFO who wants to understand the underlying NRR math in more depth, the methodology guide on net dollar retention covers the calculation and the benchmark context.

5 mistakes that kill NRR planning

A short checklist before sending the plan to the CFO.

1. Treating Discovery-stage expansion as committed

Fix: the status field in the Expansion Plan tab forces the call. Only Committed feeds the bridge confidently.

Discovery gets tracked separately as upside.

2. Leaving at-risk renewals out of the plan because they have not been officially flagged

Fix: the Risk Inventory tab forces them to be named with an ACV and an owner.

A risk without a name is a risk that surprises everyone at quarter-end.

3. Building a single-scenario plan.

Fix: the sensitivity table runs 4 scenarios automatically.

The right planning assumption is usually the worst case, not the headline plan. If the worst case is still above target, the plan is strong.

If it is below target, the next 30 days of CS work is what closes the gap.

4. Presenting NRR without the variance against target.

The CFO does not want a number, she wants the number, the variance, and the reason.

“114% NRR, 1 point below the 115% target, primary driver is Stark Industries downsell risk” is a 12-word summary that lands. “We expect 114% NRR” is a number with no story attached.

5.Reviewing the bridge once per quarter.

Fix: update it every two weeks.

The plan that goes stale at week 6 is useless at week 12. The sensitivity scenarios shift as expansion plays close, risks resolve or escalate, and Contraction assumptions get tested in real renewal negotiations.

A live bridge is a CFO-trusted bridge. A static one is a deck.

Get the NRR Bridge Plan template

The Bridge template includes the 4 working tabs (Bridge, Expansion Plan, Risk Inventory, README), the live sensitivity table that runs 4 scenarios automatically, and pre-built status validation and conditional formatting throughout.

Built to be filled in during a 60-minute working session and refreshed every two weeks.

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

Share The CS Café

The blank slide problem

Final round. A CSM loop with three people in the room: the hiring manager, a senior CS peer, and a Sales lead. You have a 30-minute slot to present.

The recruiter sent you the prompt three days ago: walk us through your first 90 days.

You open PowerPoint. You stare at a blank slide.

You search for “CSM interview presentation 30-60-90.” You find five blog posts that all say the same thing. Listen in the first 30. Learn in the next 30. Lead in the final 30.

You build a slide for each phase, fill it with bullets, and lose the loop.

The interview presentation that loses the loop is the one that treats the prompt as a writing assignment. The interview presentation that wins the loop is the one that treats it as a hiring decision document.

The hiring manager is not grading your slide design. She is deciding whether you can walk into a portfolio of accounts on Monday and start protecting revenue.

This post gives you the structure that wins the loop.

Seven slides. A 30-60-90 frame built around named, specific, executable actions tied to a real B2B SaaS scenario.

Three questions to ask the panel that demonstrate discovery instinct in 5 minutes. The slide most candidates get wrong, with the correct version written out.

The Google Slides template at the bottom of this post, free for new subscribers.

What hiring managers actually evaluate

Most candidates believe the presentation is graded on completeness.

The 30-60-90 frame, neat bullets, a tidy summary slide. Hiring managers are not grading completeness. They are grading three things, every time.

Pattern recognition

Did the candidate identify the real risk in the role within 30 minutes of reading the prompt? Or did she pattern-match to a generic CS playbook?

A generic playbook signals a CSM who will run the same plays at every company.

A specific read signals a CSM who reads the room.

Specificity

Are the actions named, dated, and tied to deliverables the hiring manager could imagine actually happening on a Tuesday afternoon?

Or are they categories that any candidate could write?

“Build relationships with customers” is a category. “Run a renewal-risk diagnostic on the top 10 ACV accounts and surface the 3 highest-risk renewals to the VP-CS by day 75” is a deliverable.

The difference is the difference between an offer and a polite rejection email.

Discovery instinct

Did the candidate ask the right questions during the presentation? Or did she present a monologue?

This is the differentiator and the section most candidates skip. The presentation is not a deliverable. It is a working session disguised as a deliverable.

The candidate who treats it as a working session, asks two or three sharp questions, and adjusts her plan in real time wins the loop in front of the panel.

The 27 best customer success manager interview questions post covers the question prep that comes before the loop. This post is about what happens once you are in it.

The 7-slide CSM interview presentation

Seven slides, not ten. Each slide has a time block, a content focus, and a hiring decision it influences.

Slide 1: Title + my read of the role

One slide. Your name, the company logo, and one sentence that names what you believe this role is actually about.

Not “Customer Success Manager candidate presentation.”

Something like “Protecting net retention in a portfolio that just lost two enterprise renewals.”

If you do not know what the role is actually about, the rest of the deck will be generic. Slide 1 forces you to commit.

Slide 2: What I learned about the business

Three specific facts from your research, not five.

One on the product, one on the customer base, one on the company’s commercial position.

Examples that work: a recent earnings call mention of customer retention as a board priority, the named competitor that won a prominent logo last quarter, the size of the portfolio you would inherit if the role is open because the previous CSM left.

Each fact is a sentence. The hiring manager learns more from three precise facts than from twenty bullets.

Slide 3: My 3 questions for the panel

This is the slide that separates the candidate who gets the offer from the candidate who is “almost a fit.”

The full section below this table covers the three questions in depth. The key structural rule is that the questions slide is the third slide, not the last.

You ask the questions early because you want their answers to inform the rest of the presentation.

Slide 4: First 30 days, Listen

Three named actions. Stakeholder mapping with a target meeting count by week 4.

A portfolio audit using the foundational customer success plan as the structuring document. Joining the team’s existing rhythm of standups, QBRs, and pipeline reviews.

The trap on this slide is making it impressive.

Listening cannot be made impressive. Keep this slide the shortest of the three time-block slides.

Slide 5: First 60 days, Diagnose

Health scoring across the portfolio using a defined framework like red-yellow-green account health.

Naming the top three risks across the portfolio with the criteria you used to rank them. Building the first version of a recovery plan for each.

This slide demonstrates that you have a diagnostic methodology, not just instincts.

Slide 6: First 90 days, Act

The longest slide in the deck and the one most candidates get wrong.

Full treatment in the dedicated section below.

The short version: one named initiative, tied to a real risk surfaced in Slide 5, with deliverables and success criteria.

Slide 7: What I would need from you

Three specific asks of the hiring manager.

Examples: an introduction to the AE who owns the largest at-risk account in week one. The authority to run a 30-minute QBR with the top three accounts within the first 45 days.

Clarity on the renewal forecast methodology used by Finance.

The asks signal that you have already started thinking about how the role connects to the rest of the company.

The 3 questions to ask the panel

The questions slide is the most underused slide in CSM interview presentations.

Most candidates use it as a closing afterthought. The candidates who win the loop use it to do live discovery in front of the panel.

Three questions that work, with the reasoning for each.

1. “What does the CSM in this role need to deliver in the first 6 months that the current team isn’t able to deliver today?”

This surfaces the hidden hiring driver. Every CSM role has a stated description and an actual reason it is being filled. The stated description is on the job posting.

The actual reason is usually one of three things: a portfolio that lost its previous CSM and needs continuity, a strategic account that needs a stronger relationship owner, or a gap in the team’s operating capability (renewal forecasting, exec engagement, expansion motion).

The hiring manager’s answer to this question tells you which of the three you are walking into and lets you adjust your 90-day section in real time.

2. “If you had to predict where my first churn risk surfaces in this role, where would it come from?”

This question tests the hiring manager’s diagnostic instinct.

It also gives you your first actual risk to address. A hiring manager who answers with a specific account name, a specific renewal date, or a specific customer team has revealed where the work actually is.

A hiring manager who answers vaguely has revealed something else: that the role’s risk landscape is not yet well understood, which is itself useful information for how you should pitch your 90-day plan.

3. “What would make my first QBR a clear win in your eyes?”

This forces the hiring manager to articulate success criteria she may have not yet made explicit.

The answer also tells you what she means when she says “exec trust” or “strategic CSM,” because those words mean different things at different companies.

If you can build the QBR section of your 90-day plan around the actual criteria she just named, you have already done in 5 minutes what most CSMs take three months to figure out after they start.

Three questions. Five minutes.

The candidate who asks these has done more discovery than most CSMs do in their first 30 days.

The slide most candidates get wrong

Slide 6 (First 90 days, Act) is where most CSM interview presentations lose the loop.

The losing version reads something like: “Drive adoption across the portfolio. Run executive business reviews. Identify expansion opportunities.”

That answer is a list of categories. Any candidate could write it. The hiring manager has heard it from every other finalist this week. It does not earn the offer.

The winning version names one specific initiative, tied directly to a risk surfaced in Slide 5, with deliverables and success criteria.

Here is a worked example

The risk surfaced in Slide 5: three of the top ten accounts in the portfolio are flagged yellow on health, two of them have renewals within the next 6 months, and one of the renewals lost its executive sponsor last quarter.

The winning Slide 6: “Run a renewal-risk diagnostic on the top 10 ACV accounts in the portfolio.

• By day 60, identify the 3 highest-risk renewals using the framework from Slide 5.

• By day 75, build a renewal-risk recovery plan for each one in collaboration with the AE.

• By day 90, have the recovery plans reviewed in a working session with the VP-CS, with two committed customer-side actions for each.”

That answer is specific. It is dated. It is tied to a deliverable the hiring manager can imagine actually happening.

It demonstrates a candidate who already knows what an operating system for renewals looks like, which means she could start work on Monday with the structure already in mind.

Hiring managers want a CSM they can hire and stop thinking about. The Slide 6 above is what that CSM looks like on paper.

A second example, for an expansion-focused role

The risk: low expansion attach rate on the portfolio’s mid-market segment.

The winning Slide 6: “By day 60, complete an expansion audit on the 20 mid-market accounts in the portfolio. By day 75, identify the 5 accounts with the strongest expansion signal using usage data and stakeholder maps. By day 90, run a discovery call with 3 of the 5 alongside the AE, with a goal of at least one named expansion opportunity in the pipeline by end of quarter.”

Both examples follow the same structure.

Named initiative, time-boxed actions, deliverables that the hiring manager can imagine on a Tuesday afternoon.

The structure works for renewal-protection roles, expansion-driven roles, retention-focused roles, and anything in between.

Delivery rules during the live presentation

Five rules govern how the deck performs in front of the panel.

Start with Slide 3 if the panel is senior

A VP-CS and a Director of Sales in the room means the senior register is set high.

Lead with your three questions, get their answers, and walk the panel through the rest of the deck adjusted in real time.

Junior or peer-level panels prefer the standard slide order.

Do not read the slides

The panel can read.

Your job is to add what is not on the slide. The slides are scaffolding for the conversation, not the conversation itself.

Pause for 5 seconds after each question slide

Most candidates ask a question and immediately fill the silence.

Five seconds of silence after a question is what gives the panel space to answer it honestly. Practice the pause.

Keep one slide hidden in your appendix

Title it “what I would do if I lost my biggest account in my first month.”

Pull it out only if the panel asks the question, or if the conversation goes to risk during the live discussion.

The slide demonstrates that you have thought about failure modes, which is what differentiates a senior CSM from a mid-level one.

End on Slide 7 (What I would need from you), not on “thank you.”

Closing on your asks signals that you assume the offer is coming. Closing on thank-you signals that you are hoping for it.

The difference is small. The hiring manager hears it.

6 mistakes that kill CSM interview presentations

A short checklist before you walk into the loop.

1. The deck tries to look like the perfect CSM

The panel knows you do not yet work there. Name what you do not know. Specificity about gaps reads as confidence. Pretending you have no gaps reads as inexperience.

2. The deck uses generic CS frameworks

“Adopt, renew, expand.” “Stack rank by ACV.”

None of these wins the loop because every candidate uses them. The frameworks you reference should be specific operating systems, like the QBR structure in this post or the renewal-risk plan above.

3. The deck skips the questions slide

Or uses it as an afterthought at the end. The questions slide is your single biggest opportunity to demonstrate discovery instinct in front of the panel. Treat it as the third slide.

4. The deck over-details the 30-day section

Listening cannot be made impressive. Make 90 days the longest section of the deck, not 30.

5. The deck treats the presentation as a deliverable

The presentation is a working session disguised as a deliverable. The best CSM interview presentations end with 15 minutes of discussion that was not on the agenda, because the panel started engaging with the plan instead of evaluating the slides.

6. The deck closes on “thank you.”

Close on your three asks of the hiring manager. The thank you happens in the email after the loop.

Get the slide template

The slide template includes all 7 slides plus the appendix slide, pre-filled with example content for a fictional B2B SaaS scenario you can adapt. Speaker notes on each slide cover the talking points from this post.

Open in Google Slides, then File and Make a Copy to customize for your interview.

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

Share The CS Café

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

Share The CS Café

The reason most QBRs change nothing

Most QBRs end with the customer’s VP nodding politely while looking at her phone.

Two weeks later, the renewal conversation surfaces a blocker the CSM never heard about. The exec was never engaged. The meeting was a presentation, not a working session.

The agenda is the reason.

Build the QBR forward from the CSM’s deliverables and the meeting becomes a slide deck. Build it backward from the decisions the customer’s exec needs to make and the meeting becomes operational.

One produces nods. The other produces named owners with dates.

This post gives you the 60-minute agenda that works in real QBRs with real exec attendance.

Every section has a time block, an owner, and an outcome that must be reached before the next section starts.

• There is a decision tree for when the exec walks in 20 minutes late.

• There is a 48-hour prep checklist that runs in the background.

• And there is a downloadable template at the bottom that you can clone into your own account.

The same structure works whether you run two QBRs a quarter or twenty.

It does not require Gainsight, Catalyst, or any specific platform. It requires that you stop running QBRs the way most CSMs do.

4 signs your QBR agenda is built backwards

If three of these are true on your last QBR, the agenda is the problem.

1. The agenda opens with metrics, not with the outcome the customer’s exec said matters last time

Adoption numbers, login counts, support ticket volume.

None of that is what the customer’s VP came to the meeting for. The opening section should restate the priority her exec team committed to.

Everything that follows is evidence against that priority. When the agenda opens with your data, the conversation never gets to her data.

The customer success plan you wrote at kickoff is the document that should open the meeting.

2. There is no decision required from the customer side. Just updates from yours.

A QBR with no decisions is a status report. Status reports do not need 60 minutes of exec time.

If the agenda has no row where the customer has to commit to something (a resource, a date, an expansion conversation, a sign-off), the exec will not show up next quarter.

3. The “next steps” section is owned entirely by your team.

If every action item starts with the name of someone on your side, the customer learned nothing new and committed to nothing.

A working QBR ends with at least one owned action on the customer side. Usually two. Sometimes three.

4. You don’t know who from the customer side is attending until the calendar invite.

The pre-read, the agenda, and the priority ordering all change depending on who shows up.

A VP-attended QBR runs differently than a director-attended one.

If you confirm attendees 48 hours out, half the prep work is wrong.

The 60-minute QBR agenda

This is the structure that survives real exec attendance.

Every row has a time block, an owner, and an outcome that has to be reached before the next section starts. Cut any section, the rest still works.

Run it long, the decision tree below tells you what to drop.

0-5 min: Outcome reset

The customer exec speaks first. The CSM asks one question.

“When we agreed last quarter that the priority was X, that was the outcome you needed your team to hit. Is X still the priority, or has something replaced it?”

The answer determines what gets emphasized in the next 55 minutes.

Most CSMs skip this step and walk into a meeting where they are reporting on the wrong priority.

5-20 min: Business impact recap

This is where adoption metrics, ROI math, and case examples earn their place.

Tie every data point back to the priority from minute 5.

If the priority is reducing time-to-resolution for support tickets, do not lead with seat utilization. The outcome required is that the customer exec signs off, verbally, that the value is real.

If she pushes back, the agenda pauses. Do not move on. The risk section below is where the pushback gets resolved.

20-35 min: Risk and retention path

The CSM walks through the account health scoring with the customer ops lead in the room.

Yellow flags and red flags get owned in real time.

The exec hears them once, in this section, with a recovery path attached to each one. No surprises in the renewal conversation later.

The outcome required is that every surfaced risk has a name and a date attached, on the customer side and on yours.

35-50 min: Forward roadmap and expansion bets

The CSM presents two or three expansion plays that map to the priority from minute 5.

Not a pricing pitch.

A capability or a use case that extends the value already proven.

The customer exec picks one. The other two go on the parking lot for next quarter. This is where net dollar retention gets earned.

The outcome required is one expansion play identified, with a discovery call scheduled before the QBR ends.

50-60 min: Decisions and owners

The customer exec restates the three things her team will do before next quarter.

The CSM restates the three things her team will do. Each one has a name and a date.

The CSM sends the recap email within 24 hours, with the same names and dates verbatim.

The “exec walks in 20 minutes late” decision tree

The agenda above assumes everyone shows up on time.

Real QBRs do not work that way. The customer’s VP gets pulled into something at 2:55. She joins at 3:18. Now you have 42 minutes, not 60.

Here is what gets cut, what gets compressed, and what survives.

Scenario 1: Exec joins 15 minutes late.

Cut the business impact recap to 5 minutes.

Send the full deck as a follow-up. Keep risk, expansion, and decisions at full length. The outcome reset is the only section that cannot be skipped.

Run it the moment the exec joins. Everything that happened before she arrived was prep, not the QBR.

Scenario 2: Exec joins 25 minutes late.

Drop the business impact recap entirely.

Send a one-page summary in the follow-up. Move directly from outcome reset to risk. Compress expansion to 10 minutes. Protect the decisions section.

Do not let the meeting end without the three owned actions on her side.

Scenario 3: Exec drops off after 30 minutes.

This is the most common failure mode and the one to plan for.

If she has to leave, the agenda must already be at the decisions section. That means risk and expansion get compressed into 10 minutes combined.

The decisions section is owed to her, not to her team. Ask her to stay for the last 5 minutes specifically.

The rule across all three scenarios. The decisions section is non-negotiable. Everything else is variable.

Vendor QBR vs internal QBR

A vendor QBR is the one most CSMs run. You are the vendor. Your team is presenting. The customer’s team is reviewing.

An internal QBR is the one the customer’s CS team runs about your account. You are the topic, not the host.

The agenda structure stays the same. Three things change.

In a vendor QBR, the outcome reset opens with the priority the customer’s exec set.

The CSM facilitates.

In an internal QBR, the customer’s CS team owns the outcome reset and the CSM listens. Adapt by being prepared to hear a different priority than the one you tracked.

In a vendor QBR, the risk section names blockers the CSM sees from the outside. In an internal QBR, the customer’s team names blockers the CSM may never have seen. Adapt by bringing the recovery path framework, not the diagnosis.

• In a vendor QBR, the expansion section is led by the CSM.

• In an internal QBR, the expansion section is led by the customer if it happens at all.

Adapt by being ready to drop expansion entirely and double the time on retention.

The 48-hour pre-QBR prep checklist

Most QBR failure happens before the meeting starts. Here is the prep that the agenda assumes.

48 hours before

Confirm attendees on the customer side by name and title.

The deck for a VP-attended QBR is different from the deck for a director-attended one. Send the pre-read. One page.

Three sections: the priority from last quarter, the headline metrics, the two open questions for the exec.

Pull the account health scoring and write the recovery paths for any yellow or red flags. The risk section in the meeting is for surfacing, not for diagnosis.

The diagnosis happens now.

Walk the deck with whoever owns the account commercially on your side. AE, sales manager, or RevOps lead.

If the account ratio means this is one of your top 10 accounts, the deck gets two walkthroughs.

24 hours before

Confirm pre-read was opened.

Most pre-reads are not opened. If the customer exec has not seen it, the outcome reset section is the only place to recover. Plan accordingly.

Pull the renewal timeline and any pricing decisions that need to surface in the next 90 days. The QBR is where pricing gets previewed, not where it gets sprung.

Print the agenda. Have it physically on the desk during the meeting. The agenda is the document that holds the meeting together when the exec joins late.

2 hours before

Re-read the priority from last quarter. Memorize the one sentence that opens the outcome reset.

Check your account notes for any commitments your team made last quarter that did not get delivered. Anticipate the question. Have the answer ready before the exec asks.

5 common QBR agenda mistakes

A short checklist before publishing the meeting invite.

1. The agenda has no decision required from the customer side.

   Fix: add one row where the customer has to commit to something.

2. There is no time block for risks.

   Fix: 15 minutes minimum, named owners on both sides.

3. The customer exec receives the deck 5 minutes before the meeting.

   Fix: pre-read sent 48 hours out, confirmed opened 24 hours out.

4. No pre-read sent at all.

   Fix: one page, three sections, sent before the calendar reminder fires.

5. The agenda runs more than 60 minutes.

   Fix: cut the business impact recap before cutting anything else. The decisions section is non-negotiable.

Get the QBR template

The full QBR agenda template, the risk scoring tab, and the decisions tracker are bundled as a free download for newsletter subscribers.

The bundle includes:

• The 60-minute agenda template with time blocks, owners, and outcome columns

• A risk scoring tab that maps to the red/yellow/green health framework

• A decisions tracker that pre-fills the recap email format

I publish a Customer Success operating system and a career-track post every week. Free to read, free to subscribe.

Hakan Ozturk | Founder, TheCScafe.com

Share The CS Café

Today I'm sharing my complete "Response Arsenal"—13 proven templates that have generated meetings, opportunities, and job offers across 2,500+ real-world messages.

No fluff, no "hope you're doing well" generic lines. Just copy, customize, and watch your network grow.

Why LinkedIn Outreach Matters for CS Professionals

Your network directly impacts your career growth.

LinkedIn messages have an average 10-20% reply rate, which is about twice as high as traditional cold email (typically 5-10%).

A strong LinkedIn outreach strategy helps you:

• Connect with hiring managers at target companies

• Build relationships with industry leaders

• Discover new opportunities before they're posted

• Position yourself as a thought leader in CS

The 3-Part Formula for Messages That Get Responses

Every high-converting message follows this simple structure:

1. Personal connection: Show you've done your homework

2. Clear value: What's in it for them?

3. Easy response path: Ask one simple question they can answer quickly

Note: The templates I’m sharing below achieve 40-49% when: (1) highly personalized, (2) sent to researched prospects, (3) following my 3-part formula, and (4) using consistent follow-up. Even at half these rates, you'll still outperform standard outreach by 300%.

Check out my complete Customer Success Communication Skills Guide to master all aspects of customer communication.

Connection Requests vs. Direct Messages: A Key Distinction

Connection Requests (Limited to 200 Characters)

• Initial touchpoint with new contacts

• Must be brief and focus on establishing a compelling reason to connect

• Require different templates than regular messages

Direct Messages (After Connection)

• Sent after your connection is accepted

• No character limit restrictions

• Can include more detailed value propositions

• Where you can use most of the templates in this newsletter

Connection Request Templates (Keep Under 200 Characters)

• The Brief Value Add

  Hi, enjoyed your post about customer health scoring. I lead CS at ..and would love to connect about retention strategies.

• The Mutual Connection

  Hi, John suggested we connect. We both work in CS operations. Would love to exchange ideas on customer success metrics.

• The Event Follow-Up

  Hi, great meeting you at CS100 Summit. Would like to continue our chat about enterprise journey mapping.

Strategic Approach

1. Start with the connection request (68% of people prefer this approach - No InMail)

2. Wait for acceptance (typically 1-3 days)

3. Then send one of the detailed templates from the main collection

4. Follow up using the schedule I shared below.

3 Direct Message Templates You Can Use Today

1. The Content Connector (48% Response Rate)

Hi, your post about customer health metrics caught my eye. We are also in HR Tech. Any tips on implementing predictive indicators?

2. The Mutual Connection (45% Response Rate)

Hi, Sarah mentioned you're expert in customer onboarding strategies. What's one approach that's worked best for reducing time-to-value in your experience?

3. The Career Move (47% Response Rate)

Hi, your CS organization has impressive retention numbers. As I explore new leadership roles, what one quality do you value most in your CS leaders?

Best Times to Send LinkedIn Messages

For maximum response rates:

Peak Days & Times:

• Tuesday to Thursday (highest engagement)

• 9-11 AM and 1-2 PM in recipient's time zone

• Thursday for best replies (20.32% response rate)

• Monday for connection requests

When to Avoid:

• Weekends (Saturday: only 2.65% response rate)

• Holidays and after business hours

Schedule your outreach during mid-week business hours when people are in work mode. Draft weekend messages but save them to send Monday morning.

Basic Implementation Tips

• Do research before messaging

• Customize each template with specific details

• Follow up after 3-4 days if you don't get a response

• Track which templates work best for you

For more advanced strategies on building professional relationships, check out my Customer Relationship Revival Guide where I explore the principles that apply to LinkedIn outreach as well.

Need Help Securing Your Next Outreach On LinkedIn?

Get A Free Review From Me

I'll personally review one of your outreach approaches/challenges and provide specific feedback.

Here's what you'll get:

• Custom advice on how to boost your message and open rates

• Specific wording suggestions based on your target contact

• Proven tips to increase response rate by 20-30%

This is the same review process I use with my coaching clients who land $120K+ roles.

Just email me your draft message with the subject line "Outreach Review" and your context - I'll get back to you within 48 hours with a plan you can implement right away.

Limited to 3 reviews per week, first comes first served - so send yours today!

Want to master LinkedIn outreach and land those $120K+ roles?

The templates above are just the beginning.

Our premium members get access to my complete "Response Arsenal" below with:

• All 13 high-converting templates (including ones with 40-50% response rates)

• Advanced follow-up sequences that turn initial connections into meetings

• Situation-specific scripts for different career stages and goals

• Step-by-step customization guides with real examples

Last month, a CS pro I’ve been coaching used my premium templates to land connections with 3 VPs at her dream company. Two weeks later, she was interviewing for a Senior CS role paying $175K.

If you’re serious about landing high-paying roles, combine these outreach strategies with my CSM Interview Questions Guide to prepare for the interviews your successful outreach will generate.

Need personalized guidance with these templates? Try my email-based coaching service where I'll review and suggest powerful customizations, and help you land your next dream $120K-$200K role. CS pros who use my email coaching see 40% higher response rates within two weeks.

→ Get Email Coaching Support

If you've recently experienced a layoff, these templates can be especially valuable when paired with my Layoff Recovery Strategy Guide to turn your network into your next opportunity.

The Complete Response Arsenal: All 13 High-Converting Templates

…

Read more

After analyzing 18 small teams (including the 5-person squad that scaled to 500 clients), we discovered a pattern:

Traditional OKRs fail teams under 10.

Here’s how you can adapt my practical CS Sprint Goal Framework to:

✅ Reduce CSM burnout by 22%
✅ Improve onboarding speed by 18%
✅ Maintain 99%+ retention (even during hypergrowth)

Why Annual OKRs Crash and Burn for Small Teams

(And What Works Instead)

Problem:

• 68% of small teams abandon OKRs within 3 months (CS Collective Data)

• Quarterly goals become irrelevant amid daily fires

Solution:

CS Sprint Goal Framework Cycle:

1. 2-Week Sprint → One measurable improvement

2. Tiny Tactics → Automations, templates, process tweaks

3. Retrospective → Keep/Adjust/Abandon

Real-World Example:

“We used this template to cut onboarding time from 14 to 8 days – without hiring.” – Ruth D., CS Lead @ 6-person HRtech startup

Inside the Template: 3 Components That Actually Work

1. The Priority Matrix

(From my lean tech stack guide)

2. The Retrospective Grid

Track what’s working (and what’s not) in 15-minute weekly syncs.

Case Study: How Healthtech Startup “MedFlow” Scaled

Challenge:

• 5 CSMs, 300 clients, 18hrs/week spent on scheduling

CS Sprint Goal Framework:

1. Focus: Reduce scheduling time

2. Tactics:

   • SavvyCal for client self-booking

   • Loom video templates for FAQs

3. Result: 7hrs/week reclaimed per CSM

Your 4-Step CS Sprint Goal Framework Launch Plan

1. 🔓 Access the Template

We’ve pre-filled it with:

✅ Example OKRs from scaling teams
✅ Automation code snippets
✅ Retrospective checklist

“Saved 3 hours of setup time – worth subscribing alone.” – Lina T., CS Lead @ 8-person Fintech

2. Run Your First 2-Week Sprint

Tactical substeps:

1. Choose 1 pain point (e.g., ticket backlog)

2. Steal our hack:

• Week 1: Implement SavvyCal (15 mins)

• Week 2: Build Loom template library (30 mins)

3. Track → Use column 4 of the template

3. Scale → Repeat → Celebrate

Cheat code:

Every 3 sprints → Review Column 5 Archive what’s not working

Saves 8hrs/quarter in wasted efforts

“But What If We’re Already Overwhelmed?”

Here’s your cheat code:

Monday Small Hack:

• 9:00 AM → Review health scores (15 mins)

• 9:15 AM → Update ONE template field (5 mins)

• 9:20 AM → Back to firefighting

Small steps > perfect plans.

P.S. Forward this to one CS leader stuck in planning paralysis – they’ll owe you lunch!

P.P.S. Want the full scaling playbook? Start here.

Hakan,

Founder - The Weekly Customer Success Café Newsletter

TheCScafe.com

These metrics matter for sure.

Just like I covered in my Ultimate Guide to Success Metrics for Business and CS Leaders, recent research shows that 61% of customers will pay at least 5% more when they receive value beyond basic product functionality.

The Evolution of Customer Success

Traditional CS focuses heavily on demonstrating value through numbers:

• Login counts,

• Feature adoption,

• and engagement metrics.

However, a groundbreaking Forrester study reveals that companies taking a more strategic approach to customer success achieve a 107% ROI within three years.

The Breakthrough Insight

The truth is great CS is more than just proving value.

You must help your customers uncover value they didn't know existed.

And this is transformative.

Companies that implement frameworks that are based on value see a 5% increase in customer retention and a 6% boost in revenue per account.

Want to learn more about transforming customer relationships? Check out my guide on Enterprise Customer Success Management for additional insights.

Want to move beyond basic value metrics and become a strategic value creator for your customers?

Here's what's keeping most CS pros stuck:

• Inability to identify hidden value opportunities

• Lack of structured frameworks for value discovery

• Missing tools to quantify and communicate newfound value

• Uncertainty about how to turn insights into action

As I discussed in my guide on How to Build Customer Health Scores, measuring the right metrics is key but not sufficient.

In the premium section below, I share my battle-tested playbook that has helped CS teams:

• Increase customer retention by 37%

• Boost new revenue opportunities by 15-20%

• Cut training costs by 30%

• Increase customer satisfaction by 20%

• Transform routine check-ins into value discovery goldmines

You'll get:

• An exclusive 4-step Value Discovery Framework with an implementation guide

• My Value Blind Spots Framework with specific fixes

• 4 proven conversation templates:

  • The 15-Minute Check-In

  • The Problem-to-Value Chat

  • The Future-Looking Talk

  • The Money Talk

  —worth $5,000-10,000 in total value per session

• An 8-week implementation roadmap

• Stakeholder mapping toolkit with detailed personas and what they care about

• Step-by-step session guide with timing breakdowns

• Real case studies showing $50,000/year savings

Plus actual results from CS teams achieving:

• 20% increase in customer satisfaction

• 40% fewer support issues

• Happier customers with scores up 25%

• $2,000-5,000 monthly savings per customer

• 5-10 hours saved per team weekly

PLUS: The complete Value Tracking Dashboard that top CS teams use to monitor and maximize customer value creation.

👉 Upgrade to Premium now to access the full playbook

Join 100+ CS Leaders today and transform how you create and capture customer value.

Special Offer: Get immediate access for less than a coffee per week

⚡ Price increases on December 1st - Lock in current rate now.

✓ Money-back guarantee.

✓ No commitment required

✓ Cancel anytime

Read more

Kapta spoke with senior executives about vendor QBRs. Only 28% said they’re a valuable use of time.

That is the real problem: when execs think your “strategic review” is a time tax, you don’t just lose a meeting. You lose the room at renewal.

The traditional QBR model is facing a key inflection point in SaaS.

More execs are treating QBRs like a ceremony instead of a decision forum.

As Jack Maguire (National Debt Relief) put it: “These meetings have devolved into corporate karaoke.”

The Current Crisis in QBRs (and why execs tune out)

Clientshare asked 200 senior stakeholders involved in QBRs. 88% said business reviews lack evidence of value and innovation, and 82% said they’ve cancelled a contract due to poor QBRs.

What poor QBRs cost you (even before renewal)

Poor QBR execution shows up in three predictable places: renewals slip later, exec trust drops, and expansion conversations stop happening because nobody agrees on outcomes.

For more about how QBRs impact enterprise customers, check out my Ultimate Guide to Executive Business Reviews for CSMs

The Evolution of Strategic Reviews

The Amazon Framework

What the best teams borrow from Amazon is the cadence and the writing:

• One annual alignment moment (joint plan)

• Monthly scorecard-style reviews for inputs

• Quarterly reviews only when there are decisions to make

The point is simple: reviews exist to drive decisions, not to replay dashboards.

Learn more about transforming traditional reviews in my guide on How to Turn Boring QBRs into Growth Rockets

The Modern Alternative

Real-Time Engagement

The modern shift is not “more analytics.” It’s faster synthesis.

Teams are using AI to turn messy account signals (usage, tickets, emails, notes) into a short, decision-ready brief before the meeting.

Example: Custify announced an AI suite that generates account summaries and helps prep QBR talking points from account history, threads, and notes.

Best Practices for Success

A practical benchmark: aim to listen more than you talk. Call analysis in sales consistently shows better outcomes when talk time stays below average.

Customer-centric QBRs win for one reason: they make the customer’s plan the agenda, and your product the supporting actor.

For more insights on measuring success, explore my Top 5 Customer Success Metrics for SaaS Performance Insights

QBR agenda (executive-ready)

Use this agenda when you want exec attendance and renewal control:

If the people who control the budget are not in the room, you are running a customer meeting, not a renewal-protection meeting.

Here’s the structure that consistently works:

1) Pre-read (sent 48 hours before): 1 page, outcomes only

2) 5-minute executive recap: what changed since last review

3) 15 minutes on value: business outcomes, not product activity

4) 15 minutes on risk: what breaks renewal if ignored

5) 15 minutes on decisions: what you need from them, what they need from you

6) Close with owners + dates: next steps that survive the meeting

The Future of Customer Reviews

Emerging Trends

What’s clearly happening already: CS platforms are shipping AI features that compress QBR prep time (summaries, talking points, risk flags) so humans can spend the meeting on alignment and decisions, not data narration.

So, the traditional QBR isn't just dying.

It's evolving into a more dynamic, valuable, and customer-centric process.

Companies that adapt to this evolution will build stronger relationships and drive better outcomes.

And those sticking to outdated practices risk becoming irrelevant soon.

Industry leaders are already implementing the next generation of strategic reviews.

Here’s what they do differently:

• They send a 1-page pre-read

• They show outcomes and risk in exec language

• They leave with decisions, owners, and dates

The Stakes Are Higher Than Ever

Existing-customer growth is the priority, and CS leaders are being measured on it.

Gartner’s signal is clear: existing-customer growth is now the priority. In a Gartner survey, 73% of CSOs said they’re prioritizing growth from existing customers for 2025.

Yet many organizations still struggle to deliver meaningful value in their QBRs.

So, which side of this divide will you be on?

The Cost of Inaction

Every bad QBR does the same damage: it teaches the exec team that your time together produces no decisions. That’s how you lose executive air cover before renewal.

Your Next 90 Days: Transform or Get Left Behind

Here’s how industry leaders are setting up proven frameworks that consistently deliver results:

If you want a repeatable operating system for renewals, QBRs, and exec trust, that’s what I publish in The Customer Success Café (templates included).

Start with the QBR template that matches your account, then run the meeting as a decision forum instead of a slide show.

Transform Your QBRs Now

Don't let another quarter go by watching competitors win with better customer engagement.

Give your team the tools they need to deliver exceptional value in every interaction.

For enterprise customers, check out my detailed guide on Enterprise vs SMB Customer Success

1. Strategic Frameworks & Templates

a. 7 Customizable QBR Templates For Different Scenarios

Here are the 7 QBR templates you can download and customize to fit your needs:

…

Read more

Over the years, I've developed and refined a comprehensive set of templates that have significantly improved my work and outcomes for both my team and our customers.

Recognizing the value these templates could bring to other CS professionals, I decided to compile them into "The Ultimate Customer Success Templates Collection."

This resource is designed to help CS teams of all sizes work more efficiently and deliver exceptional customer experiences.

Why Customer Success Templates Are Essential

Customer success templates provide a structured framework for managing the entire customer journey.

Here's why they're invaluable:

• Consistency: Ensure standardized, high-quality interactions across all customer touchpoints.

• Efficiency: Save time and focus on strategic tasks instead of reinventing the wheel.

• Best Practices: Incorporate industry-proven strategies into your CS processes.

• Scalability: Maintain service quality as your customer base grows.

• Onboarding: Accelerate new team member integration and reduce learning curves.

According to a study by Forrester*, companies that excel at customer experience grow revenue 5.1 times faster than their competitors.

This highlights the importance of having a solid customer success strategy in place.

Key Areas Where Templates Excel

My templates cover critical stages of the customer lifecycle:

• Onboarding: Improve new customer onboardingRegular

• Check-ins: Maintain proactive communication

• Quarterly Business Reviews (QBRs): Run powerful business reviews

• Renewal Processes: Maximize customer retention rates

• Upsell and Cross-sell: Identify expansion opportunities

As Nick Mehta, CEO of Gainsight, says, "The success of your business is inherently linked to the success of your customers."

I designed these templates to help you ensure success at every stage.

Impact on Customer Success Metrics

Implementing my template collection can boost your key performance indicators:

• Higher Customer Satisfaction (CSAT) scores

• Reduced Time-to-Value (TTV)

• Increased Net Promoter Score (NPS)

• Greater Customer Lifetime Value (CLV)

• Lower churn rates

Research by Bain & Company* found that increasing customer retention rates by just 5% can increase profits by 25% to 95%.

This highlights the significant impact that effective customer success strategies can have on your bottom line.

Implementing Templates in Your CS Strategy

To best use these customer success templates:

1. Customize to fit your specific business needs

2. Update them regularly based on feedback and market changes

3. Train your team on using them in an effective way

4. Use templates as a starting point, allowing for flexibility

Customer Success Story

Sarah T., a CS Manager at a growing SaaS company, shared her experience with implementing customer success templates:

"Before adopting a comprehensive set of templates, our team struggled with inconsistent processes and lengthy onboarding times. After implementing standardized templates for onboarding, QBRs, and customer health checks, we saw a 30% reduction in time-to-value and a 25% increase in customer retention within just six months. These templates have become our CS bible, saving us countless hours and helping us deliver better results for our customers."

"An absolute must-have for anyone serious about customer success. Worth every penny!" - Mike R., Director of Customer Experience

Transform Your Customer Success Approach

My templates help CS teams deliver consistent, high-quality service that drives business growth.

Level up your customer success strategy today.

Lincoln Murphy, a renowned Customer Success Consultant, advises:

"Focus on outcomes, not just product usage. Understand what success looks like for each customer and help them achieve it."

Boost Your Customer Success Strategy

Get "The Ultimate Customer Success Templates Collection" now!

This comprehensive toolkit includes:

• 150 pages of actionable, expert-curated content

• Over 50 customizable templates covering every aspect of the customer lifecycle

• Best practices for each stage of the customer journey

Click here to get your copy and start optimizing your CS processes today!

-Hakan

Sources: *Forrester Research, "The ROI of CX Transformation"
*Bain & Company, "Prescription for Cutting Costs"

A smooth onboarding makes or breaks the experience.

It’s a fundamental step for customer success and long-term retention.

Here’s a quick-start checklist that will help you hit the ground running.

🔐Quick Start Customer Onboarding Checklist:

Read more

The problem is structure. A plan that only covers goals and timelines gives you nothing to work from when adoption stalls, a champion leaves, or a renewal conversation turns uncomfortable. It looks complete but it has no operational weight.

This template fixes that.

It is a 14-section account operating system designed for CSMs running B2B SaaS accounts across SMB, Mid-Market, and Enterprise. Every section maps to a real moment in the account lifecycle: onboarding, QBR prep, risk escalation, renewal.

What’s inside the template

Section 1: Account Snapshot

The full account context in one table: company, ARR, segment, product tier, health score, and renewal date. Any stakeholder should be able to read this and understand the account in under 60 seconds.

Section 2: Stakeholder Map

Name, title, influence level, last contact date, and risk notes for every person who touches the renewal. Covers champions, economic buyers, end users, internal allies, and detractors.

Section 3: Customer Business Objectives

Three to five stated goals the customer is working toward this year, connected explicitly to your product. This is the anchor for every exec conversation and QBR narrative.

Section 4: Agreed Success Metrics (KPIs)

A baseline-to-current-to-target table covering adoption rate, time-to-value, active users, support volume, NPS, and custom KPIs. Bring this to every QBR.

Section 5: Onboarding & Adoption Milestones

Phase-by-phase checklist from kickoff through renewal readiness, with status tracking (Complete / In Progress / At Risk) across four adoption phases.

Section 6: Value Realization Summary

ROI delivered to date across efficiency, revenue impact, cost reduction, and risk reduction. Pull from this section when building a renewal business case or writing an exec update.

Section 7: Health Score Breakdown

Weighted scoring across four dimensions: product usage, stakeholder engagement, customer sentiment, and support volume. Includes a risk tier guide (Green / Yellow / Red) with score thresholds.

Section 8: Risk Indicators & Mitigation Plan

A risk register with severity ratings, trigger signals, mitigation actions, owners, and due dates. Pre-loaded with the most common risk signals: low adoption, champion departure, budget freeze, competitor evaluation.

Section 9: QBR Schedule & Agenda Framework

Cadence, next QBR date, format, and a standard 60-minute agenda structure covering objectives review, metrics, risk, roadmap, and next steps.

Section 10: Renewal Plan

Renewal date, ARR at stake, probability, blockers, required actions, and a 90-day trigger checklist. Start this section 90 days before renewal.

Section 11: Expansion Opportunities

Upsell and cross-sell tracker with readiness signals, timing, and estimated ARR impact. Structured so expansion stays visible throughout the year, not just at renewal.

Section 12: Communication Cadence

Meeting types, frequency, format, owner, and escalation path. Covers EBRs, working sessions, technical reviews, renewal planning calls, and async exec updates.

Section 13: 90-Day Action Plan

30/60/90 milestones with action, owner, and due date. The operational commit that closes every plan review and keeps both teams accountable.

Section 14: Worked Example (Case Study)

A fully completed version of Sections 1–13 using a fictional Mid-Market FinTech account. Shows exactly how a CSM would populate each field on a real account, including an active risk scenario and recovery plan.

The template also includes a customization guide with segment-specific notes for Startup, Mid-Market, Enterprise, B2B SaaS, and E-commerce accounts.

Who this is for

This template is built for CSMs and CS leaders managing recurring revenue accounts in B2B SaaS. It works across segments. The customization guide inside the template tells you which sections to prioritize based on your account type.

If you are running renewals, preparing QBRs, or managing executive relationships in complex accounts, this gives you a repeatable system to work from rather than rebuilding your approach every cycle.

How to use it

1. Download the template from the welcome email you receive after subscribing

2. Start with the Account Snapshot and Stakeholder Map for one active account

3. Use the worked example in Section 14 as a reference for first-time setup

4. Update the Health Score and Risk sections before every QBR and renewal conversation

5. Share Sections 3, 6, and 10 with executive stakeholders. These three sections carry the renewal narrative

Get the template

Subscribe free below.

The template arrives in your welcome email as a downloadable PDF. No separate opt-in, no follow-up sequence.

Along with the template, you will get one weekly CS insight covering what is creating churn risk right now, what to prioritize first, and how to frame it in exec language.

Have questions after downloading? Hit reply on the welcome email. I read every one.

— Hakan Ozturk, Founder, The CS Café

Share The CS Cafe Newsletter

An Executive Business Review (EBR) is a strategic meeting between a company and its key customers, typically involving executive-level stakeholders from both sides.

This high-level interaction is key for maintaining strong business relationships and driving long-term success.

Key Objectives of an EBR:

1. Demonstrate value…

Read more

A well-crafted Customer Success Playbook is fundamental.

Here’s how you can create a practical, easy-to-use playbook that will help you deliver exceptional customer experiences across the entire customer lifecycle in 5 easy steps:

1. Define Your Customer Success Vision and Goals

The first step in cre…

Read more

A well-designed customer feedback survey can help you identify your strengths, pinpoint areas for enhancement, and deliver a better overall experience.

Introducing the Customer Feedback Survey Template

To help you gather meaningful insights, I’ve created a comprehensive cu…

Read more

A well-made Voice of the Customer (VoC) report can be a powerful tool for aligning your whole organization around customer needs and priorities.

Here’s how you can build one in 5 easy steps:

Key Elements of an Effective VoC Report

A thorough VoC report typicall…

Read more