How to Write a Performance Review for a Customer Success Manager

Customer success reviews are the hardest reviews to calibrate in a software business. The reason isn’t that the work is mysterious. It’s that the customer’s success and the CSM’s contribution are tangled together in every metric you can pull. A CSM with a 118% NRR book might have done outstanding expansion work, or might have inherited a strong cohort of customers and ridden the growth that was already in motion. A CSM with a 92% NRR book might have done outstanding work preventing what would otherwise have been a 70% catastrophe. The metric tells you the result; it doesn’t tell you the contribution.

This is a guide to writing CSM reviews that actually capture what the rep did. It’s manager-facing, written from the perspective of someone who’s reviewed customer success teams and watched plenty of reviews miss the work entirely.

Why CSM reviews are different from sales reviews

Three things distinguish them. First, the most valuable CSM work is invisible until it isn’t. The QBR that turned a wavering customer into a champion, the proactive enablement session that prevented a frustration spiral, the escalation that got resolved in 48 hours instead of two weeks. None of these show up on the retention dashboard until you stop doing them, at which point they show up as churn.

Second, the book composition matters as much as the attainment. A CSM whose book is mostly mid-market accounts with self-serve adoption is doing a fundamentally different job than a CSM whose book is six strategic accounts with $400k ARR each. A review that doesn’t name the book shape will be miscalibrated against on that basis by anyone in the calibration room.

Third, time-lag is real. The renewal a CSM closed in Q3 was often the product of work that happened in Q1. The QBR cadence and the success-plan quality during the early months of a relationship is what shows up as a clean renewal twelve months later, and the review needs to credit that even when the renewal itself happened on someone else’s watch.

What to pull before you write a word

The evidence collection for a CSM review takes about an hour. Block it before you draft. Here’s where to look:

• Book metrics by account. Net revenue retention, gross revenue retention, churn count and ARR, expansion count and ARR. Pull these at the account level, not just the book level, so you can spot the pattern (consistent expansion across the book versus one big expansion carrying the number).
• Renewal outcomes during the period.Which renewals were on the period’s book, which closed cleanly, which had at-risk flags resolved, which churned. Read the renewal notes if your team writes them.
• Health-score history. If your team runs a health-score system, pull the trend by account. Steady improvements on previously-yellow accounts are signal. Steady declines that nobody flagged are signal of a different kind.
• QBR cadence and quality. How many QBRs ran during the period. Spot-check 3 or 4 of the decks. A QBR that surfaces concrete value delivered, names risks openly, and ends with a mutual action plan is a different artefact than one that summarises usage stats.
• Escalations and how they resolved. Whatever ticketing or escalation log you use, pull the ones the CSM was on point for. Time to resolution, customer-facing communication during the incident, and whether the customer renewed afterwards.
• Expansion conversations and product feedback. Specific feature requests the CSM surfaced to product. Expansion seeds that opened (regardless of whether they closed this period). These are some of the strongest signals of strategic CS work.

At the end of the hour you have a list of specifics under each source. You can now write a review that names actual work instead of inventing adjectives to fit a metric.

The four-section framework

1. Book performance

The headline metrics. NRR, GRR, churn count and dollars, expansion count and dollars, renewal close rate. Lead with the strongest number and include one composition detail that anchors it. “Drove book NRR to 118% across 14 accounts, with expansion in 9 of them and zero churn” says more than “Strong retention performance.”

2. Health discipline

This is where you separate the lucky book from the well-managed one. QBR cadence (count plus quality), success-plan quality on new accounts, health-score accuracy, proactive escalation flagging. A CSM whose accounts trended yellow consistently and got rescued by the rep’s intervention has a different review than a CSM whose accounts trended yellow and the rep didn’t notice. Both might have similar book numbers; the work was different.

3. Customer outcomes

What did the customers actually achieve? Specific examples of value delivered. The expansion conversation that opened because the customer hit their adoption milestone. The renewal that closed at a higher tier because the CSM helped surface enterprise use cases. Tie the CSM’s work to a concrete customer outcome whenever you can.

4. Growth and influence

Where are they relative to where they were six months ago, and what’s the next step? Voice-of-customer feedback that landed in product roadmap. Mentorship of newer CSMs. Contributions to playbooks or templates. Cross-team work with sales on land-and-expand motions. These are the force-multiplier behaviours that separate a senior CSM from a strong mid-level one.

Common traps to avoid

The inherited-book trap

A CSM takes over a book mid-period and the NRR for the period reflects work the previous rep did. Writing the review around the NRR number rewards the inheritance, not the contribution. The fix: name the time window of the CSM’s actual ownership and assess the work within it. If the renewal closed in month two of their ownership, credit the previous rep’s setup work explicitly.

The strategic-account-camouflage trap

A book with one $800k strategic account that’s genuinely thriving will produce attractive NRR numbers almost regardless of what the CSM does on the rest of the book. The review needs to assess the work across the book, not just the work on the strategic account. A CSM who let three smaller accounts churn while the big one carried the numbers has a different review than one who held the smaller accounts steady.

The proactive-work-invisibility trap

The QBR that turned a wavering relationship around, the success plan that aligned expectations with a new executive sponsor, the early escalation that prevented an executive complaint. These show up in retention but not in any individual metric. The fix: when you spot them during evidence collection, write them into the review by name. Otherwise the CSM’s best work goes uncredited.

The “great customer relationships” trap

Universal CSM-review prose: “built strong customer relationships,” “trusted advisor,” “customer-first mindset.” These flatter no one and evidence nothing. Replace with the specific outcome that resulted from the relationship: a renewal at a higher tier, a customer reference that closed an adjacent deal, a product feedback session that shaped a roadmap call.

The 75-minute drafting flow

CSM reviews take a touch longer than AE reviews because the evidence is in more places. Plan for 75 minutes.

Minutes 0–25. Metric collection. Pull book-level retention numbers, account-level NRR breakdown, renewals during the period, churn events, expansion events. Note the time-window of the CSM’s actual ownership if there’s been any book rebalancing.

Minutes 25–55. Qualitative evidence. Read 3 or 4 QBR decks the CSM ran. Read the renewal notes for the largest 3 accounts that closed during the period. Read 1 escalation log if there was a meaningful one. Read product feedback they surfaced. Note specific moments of strong work.

Minutes 55–75. Draft and sharpen. Write each section in five to six sentences, leading with the strongest evidence. Cut anything generic on the review pass. If you wrote “trusted advisor” or “strong relationships,” replace with the specific outcome those produced.

What to do when you’re stuck

Three common stuck-points for CSM reviews.

“The numbers are bad but I think the CSM is doing the right work.”Write that explicitly. Name the headline number, name the contextual factors (book health when they took it on, churn drivers outside the CSM’s control like product gaps or pricing changes), and name the leading indicators that suggest the work is sound (QBR cadence, success-plan quality, proactive escalation flagging). A short-term metric miss with strong process discipline is a different story than a metric miss with thin process, and the review should say which one it is.

“The numbers are good but the work feels thin.”The strategic-account-camouflage trap. Write the review around the work across the full book, with the strategic account credited but not carrying the whole assessment. Name the accounts where the work was light, and what next period’s focus should be.

“They’ve grown but I can’t name what changed.’ Growth in CSM work often shows up as the absence of previous failure modes. The CSM who used to escalate every customer complaint to you and now resolves them directly. The CSM who used to run usage-recap QBRs and now runs strategic-value QBRs. The CSM who used to need scripts for renewal conversations and now negotiates them confidently. Write the before-state and after-state next to each other.

Don’t let the drafting itself be the bottleneck

Most of the work above is the thinking: pulling the metrics, reading the qualitative artefacts, separating the rep’s contribution from the customer’s trajectory. The actual writing is maybe 25 minutes per CSM if you’ve done the prep. If you want to skip that 25 minutes per CSM across a team of six, this is exactly what Crestento is built for. The customer success manager system prompt is calibrated to retention work, the four sections map onto the structured input, and the AI won’t fabricate an account name or a metric you didn’t give it.

For the rest of the cluster on writing and receiving CSM reviews:

• Performance review examples for customer success managers covers five worked examples (clean over-attainment, NRR carried by one account, principled retention miss, rescued at-risk book, ramping CSM).
• Customer success manager self-evaluation examples is the CSM-side version: what to write in your own self-eval to advocate for the proactive work that doesn’t show on a dashboard.
• Performance review tips for customer success managers collects tactical tips for both sides.