Customer Success Manager Self-Evaluation Examples

Customer success managers spend half their working time articulating value: what the customer is getting, what they could be getting, what the path looks like. Then self-evaluation season arrives and the same person who’ll spend an hour structuring a value retrospective for a renewal conversation writes “hit my retention number, built strong customer relationships” about their own work. The disconnect is real.

The fix isn’t writing yourself up like a top performer. It’s writing yourself up with the same specificity you’d apply to a QBR value retrospective. This is the CSM-side counterpart to performance review examples for customer success managers. The principles are the same; the voice is yours.

The prep step: a 45-minute book audit

Before you draft, build an evidence inventory. Open your CS platform and pull:

• Renewal outcomes during the period. Every renewal, every expansion, every churn. Named accounts, dollar amounts, the story behind each. The renewal that closed at a higher tier matters more in your self-eval than the one that closed at flat, but both deserve a sentence.
• Account health movement. Which accounts moved yellow-to-green during the period. Which stayed green that you specifically held. Which moved green-to-yellow and what you did about it.
• QBR count and quality. How many QBRs you ran. The two or three where the deck or the conversation was particularly sharp.
• Escalations you handled. Specifically the ones where you resolved them yourself rather than escalating to your manager. Time to resolution, the customer outcome.
• Voice-of-customer feedback. Specific feature requests you surfaced. Cases where you brought product into customer calls. Any feedback you formalised into team-level patterns.
• One thing you turned down or pushed back on. A scope discussion where you held a contractual line, a customer request you said no to, an internal ask you declined to make space for the retention work. CSMs under-credit themselves on this kind of work consistently.

Forty-five minutes of this gives you the raw material to handle every prompt with specifics.

Example responses to common self-eval prompts

“What was your biggest impact this period?”

Weak version: “Maintained strong relationships across my book and drove expansion through trusted advisor conversations.”

Better version:

The work I’m most proud of this half was the recovery on the Lyric Health account. Lyric came into the half flagged red after two months of declining usage and a difficult Q4 renewal at flat. Their executive sponsor had moved teams and the new sponsor was lukewarm on continuing the relationship at scale. I ran a strategic review with the new sponsor in week three, structured around three specific value commitments we could make in the first 90 days. Two of those commitments required product changes, which I surfaced to engineering as a packaged request rather than individual tickets. By month four, Lyric had moved from yellow to green health and signed an expansion to the multi-product tier worth $145k of additional ARR.

Notice what this does. It names the account. It names the starting state (yellow health, lukewarm new sponsor). It names the specific moves (strategic review with three value commitments, the product request packaging). It names the outcome with a number. A reader gets the headline if they skim; they get the case for promotion if they read.

“What didn’t go well? Where did you fall short?”

This is the CSM prompt that suffers most from generic modesty. “I could have been more proactive” teaches no one anything. Pick a specific account.

Better version:

The most honest miss this period was the Halton Logistics churn. Halton came onto my book in February and churned at their May renewal. Looking back, I misread the signal in their first QBR (low usage on the analytics module read to me as “they’re still ramping” when it was actually “they’re not getting value from this product”). I didn’t escalate the risk to my manager until week eight, by which point procurement was already comparing alternatives. The change I’ve made: any account showing 40% lower than expected adoption by week six gets surfaced in my 1:1 with the VP that week, regardless of how I’m reading the broader relationship. I’ve already applied this on two H2 accounts and both surfaced concerns that I’ve been able to action before they compounded.

This works because it names the account, the misread, the cost, and the specific behavioural rule the writer has already adopted. CSMs who can write a Halton-style loss honestly tend to clear promotion calibration more easily than CSMs who don’t name misses at all, which is counterintuitive but consistent across the reviews I’ve seen.

“What did you learn this period?”

Skip generic learning answers. Name the work that changed how you operate.

Better version:

Two things. First, the Lyric Health recovery taught me the value of packaging product feedback rather than surfacing it as individual tickets. When I bring engineering a structured request with three named customers asking for the same capability, the response is materially different from when I send three individual feature requests. I’m now doing this by default on any feedback that’s come up across more than one account. Second, the Halton miss taught me that the usage signal at week six is more reliable than my read of the relationship at the same point. I’m weighting the leading indicators more heavily in my own risk assessment than I was at the start of the year.

“What are your goals for the next period?”

The trap is metric-only goals (“hit 115% NRR”) or activity-only goals (“run more QBRs”) without the behaviour change that would produce them.

Better version:

Three goals for H2:

1. Run health-led QBRs on all 14 accounts twice during the half. Specifically, every QBR deck includes a value retrospective slide, a forward success plan with named commitments, and a usage signal review. The accounts where this has been spottiest this half (Carter Group, Mendel Software) are the immediate ones to address in weeks one to four.

2. Lead three escalations end-to-end during H2 without manager involvement on the call. I’ve been shadowing or running with backup; the next step is running the customer-facing communication and the internal coordination on my own, surfacing them to my manager only for awareness.

3. Formalise the packaged-feedback workflow with product. Specifically, run a monthly synthesis session where I bring three to five aggregated themes from across my book to the relevant PM. This worked well as an ad-hoc habit during H1 and I want to make it routine.

Specific enough that you can’t fake the outcome. Each goal has a behaviour change tied to it, not just a target metric.

Adjusting by tenure

Ramping CSMsshould anchor on the discipline that produces sustainable retention: QBR cadence, success plans, the shadowing you arranged on senior CSM calls. Hitting the retention target is secondary at this stage; demonstrating that you’re building the underlying habits is what counts.

Mid-level CSMs should focus on proactive book management and independent escalation handling. The case for senior is built here: can you run a book without your manager catching the early-warning signals before you do?

Senior CSMs and aboveshould focus on force-multiplier work. Mentorship of newer CSMs, contributions to playbooks and templates, strategic-account leadership, structured product-feedback workflows. The retention metric is assumed at this level; the conversation is about your impact on the team’s retention, not just your book’s.

The one-page template

• One sentence headline. Your book performance plus one composition detail.
• Three specific wins. Named accounts, dollar outcomes, the work that produced them.
• One honest miss or churn.Named account, what went wrong, what you’ve already changed.
• One thing you learned that changed how you work. A specific shift in habit, not a generic competency.
• Three specific goals for next period. Each with the behaviour change attached.

Five points, all specific. If you can write that, you’ll be in the top quarter of CSM self-evals your manager reads this cycle. For the manager-side framework, see how to write a performance review for a customer success manager. For the tactical tips on both sides, see performance review tips for customer success managers.