Performance Review Tips for Customer Success Managers

Customer success reviews are different from sales reviews because the metric you care about (retention) is one to two quarters behind the work that produced it. A CSM who ran a tight ship in Q1 sees their renewal numbers in Q2. A CSM who let things drift in Q1 sees the churn in Q3. The tips below are mostly about closing that gap: getting leading indicators into the review process, so neither side is calibrating against a number that no longer reflects what’s happening.

Three sections: tactics for CS leaders, tactics for CSMs, and the moves both sides should get right. For the underlying framework, see how to write a performance review for a customer success manager.

Tips for CS leaders

1. Pull book composition before you write a word

Two CSMs at 110% NRR on different books are not the same CSM. Account count, average ARR, churn-risk distribution at the start of the period, segment mix. These shape the review more than the headline number. The CSM whose 110% came from 12 distributed expansions is doing different work than the one whose 110% came from one big multi-product upgrade and three flat renewals.

2. Spot-check 3 QBR decks before review week

Twenty minutes per deck, sixty minutes total per CSM. The QBR is where most of the strategic CS work happens, and the decks are usually the strongest qualitative artefact of the period. You’re looking for value retrospectives, mutual action plans, expansion conversations woven into the structure. A CSM whose QBR decks have all of those is operating at a different level than one whose decks are usage-stat summaries.

3. Don’t deliver new feedback in the review

If a CSM is hearing a piece of feedback for the first time in writing, the weekly 1:1 cadence has slipped. The review should formalise conversations you’ve been having for months, not introduce them. CSMs in particular track patience and trust closely; surprises in review season erode both.

4. Credit work that doesn’t show in metrics

Voice-of-customer feedback that landed in roadmap. Playbook contributions. Mentorship of newer CSMs. Cross-team work with AEs on land-and-expand. Strategic sponsor relationships built quietly over months. These are the force-multiplier behaviours that distinguish senior CSMs, and they’re invisible in the retention dashboard. Naming them is half the work of a strong CSM review.

5. Time the review window to ownership, not the calendar

If a CSM took over a book mid-period, the review window is the months they actually owned the book, not the full period. Reviewing them on inherited work rewards the handover rather than the contribution. Spell out the ownership timeline in the review explicitly and assess the work within it.

6. Make the loss section part of the review

Every CSM had at least one churn or contraction this period (or, if they didn’t, you should be checking whether the book is too easy). The strong reviews talk about one of them: what happened, what was tried, what was learned. Reviews that only discuss expansions read as highlight reels and don’t help anyone develop.

Tips for customer success managers

7. Build your evidence inventory in week 1 of the cycle

Forty-five minutes at the start of the cycle, pulling renewals, churn events, health movement, QBR count, and the named-account stories from the period. The full prep list is in customer success manager self-evaluation examples. Doing this in week 1 instead of the night before makes the actual writing trivial.

8. Lead with composition, not just NRR

Your manager and the calibration room are looking at NRR already. The first sentence of your self-eval should anchor the number with composition: how many accounts, what the expansion versus retention split was, whether churn was contained. Composition signals you understand your own book the way your VP does.

9. Name one specific churn or save

On the harder prompts (what didn’t go well, what you learned), name an account and tell the story end to end. Volunteering “could be more proactive” is worth nothing. A named-account post-mortem with a specific behaviour change you’ve already adopted strengthens your case noticeably.

10. Surface the work that didn’t hit metrics

The packaged feedback you brought to product. The playbook update you wrote. The new-CSM you shadowed through their first escalation. These don’t show up on the retention dashboard and they’re where senior CSMs get their force-multiplier credit. If you did this work and didn’t write it into your self-eval, the calibration room doesn’t see it.

11. Frame goals as behaviour changes

“Hit 115% NRR” is a hope, not a goal. “Run health-led QBRs on all 14 accounts twice during the half, with value retrospective and forward success plan in every deck” is a goal. Each H2 goal you set should have a specific behaviour change attached, not just a target metric.

12. Run a mid-period self-check

Forty-five minutes in week six of the period, on your own, walking your book the way your VP would. Which accounts have you not QBR’d? Which have usage signals you haven’t actioned? Which renewals are coming up in the next 90 days that you haven’t prepped for? Doing this twice per period changes how you write self-evals (you have the data fresh) and changes how you work (you catch the drift before it compounds).

Tips for both sides

13. Have a pre-review conversation

Two weeks before the review, schedule 30 minutes specifically to compare notes on what each of you is going to write. The point isn’t to synchronise documents; it’s to surface disconnects. If the manager thinks the half’s defining work was the Lyric Health recovery and the CSM thinks it was the Acme expansion, you want that conversation early.

14. Account for time-lag explicitly

Some of this period’s retention numbers were produced by work that happened last period or earlier. Some of this period’s work will show up in next period’s renewals. Both sides should acknowledge the time-lag in writing and not treat the period’s metric snapshot as a complete picture of the work that happened in the period.

15. Treat the review as the start of the next cycle

The most important conversation is the one that happens after the document is delivered. Agree on two or three specific things to do differently in H2. Write them down somewhere you’ll see again in 30 days. Return to them in 1:1s. A review that doesn’t change behaviour was a retention-dashboard recap, not a development tool.

The shape of a CSM review that ages well

Twelve months from now, read the review and ask whether you could picture the period it was written about. The strong reviews pass. They have named accounts, specific QBR moments, specific recovery stories, specific churn autopsies. The weak reviews don’t. They could have been written about any CSM in any quarter at any company.

Everything in this article is in service of that test. The rest of the cluster covers the underlying framework, the worked examples, and the CSM-side counterpart:

• How to write a performance review for a customer success manager for the four-section framework and the 75-minute drafting flow.
• Performance review examples for customer success managers for five worked examples covering different retention scenarios.
• Customer success manager self-evaluation examples for the CSM-side version.