Performance Review Examples for Customer Success Managers

Customer success reviews are notoriously easy to write badly. The retention metric is in your dashboard, the customer relationships are intangible, and the temptation to fall back on words like “trusted advisor” or “customer-first mindset” is strong because every CSM-review template you’ve ever seen uses them. The examples below try to do the opposite: name the actual work, the actual accounts, the actual outcomes.

The five scenarios that follow cover the situations CS leaders actually run into. Each is a worked review you can adapt to your CSM. The framework behind them is in how to write a performance review for a customer success manager.

Example 1: CSM at 122% NRR on clean expansion work

Scenario: Aisha, mid-market CSM, two years on the team. Carries a 14-account book at roughly $80k average ARR. Finished the half at 122% NRR with expansion in 9 of the 14 accounts and zero churn.

Aisha delivered 122% NRR across her book this half, with expansion in 9 of 14 accounts and zero churn or downgrade events. The composition is what makes the result a clean promotion case. The expansion was distributed (no single account drove more than 18% of the total expansion ARR), and the expansion conversations opened during routine QBRs rather than reactive escalations, which is the harder version of this work.

The QBR cadence Aisha ran during the period stands out. She held QBRs with all 14 accounts twice during the half, with success-plan reviews documented for each. The two cases I’d highlight: the Rivera Health account moved from yellow to green health on the back of an enablement plan she designed in February, and the upgrade to the Enterprise tier on Acme Foods came from a value conversation she structured during their March QBR. She also surfaced four feature requests to product, two of which made it into the Q3 roadmap. Aisha is operating squarely at senior level on this book; the natural next step is taking on a strategic-account segment, which we’ve already started planning for H2.

What this does well: the NRR headline is contextualised with composition detail (distributed expansion, no single-account dependency). The QBR cadence is named with numbers. Specific accounts are credited with the specific work that produced the outcome. Product feedback is treated as the contribution it is.

Example 2: CSM at 115% NRR carried by one strategic account

Scenario: Marco, mid-market CSM, three years on the team. Hit 115% NRR for the half but most of the expansion came from one large account that signed a multi-product upgrade. The rest of his book was flat.

Marco delivered 115% NRR this half, which on the headline is a strong number. The composition is what I want to be honest about in the review because it shapes the H2 conversation. The 115% was carried by the Northbridge account, which signed a multi-product upgrade in May for roughly $290k of additional ARR. Without Northbridge, book NRR was approximately 98%. Two of his other accounts renewed flat after expansion conversations that didn’t advance, and three accounts had QBRs that slipped from the original quarterly cadence to semi-annual.

The Northbridge work itself was strong. Marco identified the multi-product opportunity during a Q4 QBR last year, partnered with the AE on the expansion plan, and ran the executive sponsor relationship through procurement. That deserves credit. The H2 focus needs to be on the rest of the book. Specifically: re-establish the QBR cadence on the four accounts that slipped, run a structured expansion-readiness review on the two accounts that stalled at flat, and document the playbook he used on Northbridge so it’s replicable on similar accounts in his segment. The headline is solid; the underlying portfolio asks for more attention.

What this does well: the strategic-account camouflage trap gets named directly. Marco gets credit for the Northbridge work specifically (the QBR identification, the executive sponsor relationship) instead of getting broad credit for the whole number. The next-period direction is specific (the four accounts, the structured review, the playbook documentation).

Example 3: CSM at 94% NRR after rescuing an at-risk book

Scenario: Priya, mid-market CSM, took over a book mid-period when the previous CSM left. The book was inherited at roughly 70% projected NRR with three accounts flagged red. Closed the half at 94% NRR.

Priya finished H1 at 94% NRR, which is below the team target of 105%. The headline number is a miss; the work behind it is the strongest CSM work I’ve reviewed this cycle. Priya took over the book in March when Devon left. At handover, three accounts were flagged red (TerraCotta, Lyric Health, and Halton Logistics, with combined ARR of roughly $480k), and projected book NRR was around 70%. The risks on those three accounts had been accumulating for two quarters and the previous CSM hadn’t flagged them clearly.

Within six weeks of taking the book, Priya had run emergency strategic reviews with all three at-risk accounts, brought our VP of Customer Success into the TerraCotta conversation, and surfaced two specific product gaps to engineering that were blocking adoption. TerraCotta renewed at flat (no expansion but no downgrade either). Lyric Health renewed at a slight contraction, which was the right outcome given their team-size reduction. Halton Logistics churned. The 94% is what closing the book at 70% projected looks like when an experienced CSM runs the recovery well, and I’d argue this is a stronger half than most of the 110%+ halves on the team this period.

What this does well: the headline miss is named honestly. The handover context is laid out so the reader understands what the starting point was. The recovery work is specific (six weeks, named accounts, the VP escalation, the product-gap surfacing). The closing line makes the calibration case directly: this 94% is better work than many of the over-attaining halves.

Example 4: CSM at 100% NRR with thin proactive work

Scenario: Dani, mid-market CSM, three years on the team. Hit exactly 100% NRR this half. QBR cadence has slipped, success plans haven’t been updated, and several accounts are showing usage-decline signals that haven’t been actioned.

Dani delivered 100% NRR this half, which by the comp plan is on-target. The review I’m writing isn’t about the metric. It’s about the underlying process signals, which have been drifting in a direction I want to address before they show up as churn in H2.

Specifically, QBR cadence dropped from the team standard of twice-per-half to once-per-half on 6 of her 12 accounts, with 2 accounts not receiving a QBR this period at all. Success plans haven’t been updated on 8 of the 12 accounts since handover or initial rollout. Three accounts (Carter Group, Mendel Software, and Brixley Health) have shown declining usage over the past 90 days without a documented intervention plan. None of these are catastrophic, but they’re the early indicators of a book trending toward red. The 100% is largely the renewal timing of accounts that signed strong contracts twelve months ago, which won’t protect H2.

I’ve been part of letting this drift; I haven’t named it sharply enough in our 1:1s. The H2 reset is going to be weekly book reviews until QBR cadence is back to twice-per-half across the book, mandatory success-plan updates on the three usage-decline accounts within four weeks, and a paired account-health audit with me on the Carter Group situation specifically. The headline NRR is fine; the underlying signals are flashing.

What this does well:the manager owns part of the gap (“I haven’t named it sharply enough”), which keeps the feedback from feeling like a verdict. The specific accounts are named so there’s no ambiguity about which book health signals are at issue. The forward plan is concrete and time-bound.

Example 5: New CSM, eight months in

Scenario: Sam, mid-market CSM, joined the company eight months ago. They’re in their first full performance period. Their book was set up at handover with mostly green accounts and clear success plans. Finished the half at 108% NRR.

Sam is eight months in and operating at the level I’d expect at this point of ramp. They closed H1 at 108% NRR across a 9-account book with no churn and expansion in 4 accounts. The book they inherited was in good shape (most accounts green at handover, success plans in place), so the bigger question for this review is how Sam’s own work is shaping up beyond riding the starting position.

Two things stand out. First, the QBR quality has stepped up noticeably across the period. Sam’s first QBRs in months two and three were usage-recap heavy, which is the right starting point. By month seven, the QBRs they’re running include explicit value retrospectives, mutual action plans, and expansion conversations where appropriate. The Acme Hospitality QBR in May is the strongest CSM-led QBR deck I’ve reviewed this half across the whole team, including from more tenured CSMs. Second, Sam has been proactive about shadowing senior CSMs on escalation calls and has documented two patterns from those sessions in the team playbook, which is unusual at this tenure.

The area for H2 focus is independent escalation handling. So far Sam has shadowed escalations rather than led them, which is the right ramp shape. The next step is to lead one or two during H2 with me as backup rather than primary. Sam is tracking exactly where I’d want a mid-level CSM to be at eight months.

What this does well: ramp gets its own framing rather than being measured against full-tenure expectations. The QBR-quality progression is specific (named months, specific deck called out). The force-multiplier behaviour (playbook contribution) gets credited. The forward area is concrete and matched to ramp stage.

What these examples have in common

• Composition over headline. Every example unpacks the NRR number with at least one composition detail (account count, distribution, churn versus expansion balance).
• Proactive work named explicitly. QBR cadence, success-plan quality, voice-of-customer contribution. These are the signals that distinguish sustainable retention from numbers that happen to land well for one period.
• Time-lag accounted for. The reviews credit work done during the period even when the outcome lands later, and they account for inherited context when relevant (example 3).
• The manager shows up.Lines like “I’ve been part of letting this drift” carry a point of view. They make the feedback land as a conversation rather than a judgement.

For the CSM-side counterpart (what to write in your own self-eval), see customer success manager self-evaluation examples. For the tactical tips on both sides, see performance review tips for customer success managers.