Session #4291 · 25 min · Full · CSM final round

Coaching report

B2B SaaS · Customer Success Manager interview · April 28, 2026

/ 100

Overall

Solid

3 answered · 16 fillers

Strengths

·Clear commercial instinct on renewal risk: usage, champion loss, procurement, and exec alignment
·Strong executive-language moments on Q2: business outcome before product detail
·Composed pacing throughout — 139 wpm average, no rushing under pressure

What to fix

·Q1 missed the first 24-hour action plan — too much diagnosis before naming the next move
·Q2 needed a tighter CFO frame: cost, risk, adoption, and renewal impact
·Filler words spike on escalation follow-ups (7 "um"s in 80 seconds)

Next focus

Drill the save-plan opening: risk summary, stakeholder map, first executive touch, recovery metric. Your content is credible; the first 20 seconds need to sound more senior.

Pacing (words/minute)

Target: 130–170 wpm

137

141

134

Filler words

total · 9.3/min

<3/min reads polished. 3–6 is normal under pressure. 6+ distracts.

Answer-by-answer coaching

Question 1

A top account is 45 days from renewal. Usage is down 38%, your champion has gone quiet, and procurement just asked for a discount. Walk me through your save plan.

I would start by figuring out whether the risk is adoption, value, or relationship. Usage being down 38 percent tells me there is probably a value problem, but the champion going quiet means I also need to rebuild access. I would look at the health score, check which teams stopped using it, and then set up an executive meeting. I would not lead with a discount. I would try to show the business impact and create a recovery plan with the customer before procurement owns the whole conversation.

Clarity

7/10

Specificity

7/10

Structure

6/10

Pace

137 wpm · 4 fillers

One thing to fix

Name the first 24-hour action. You diagnosed correctly, but the panel still needs to hear what you do first.

Rewritten

I would treat this as both a value-risk and access-risk account. In the first 24 hours I would pull usage by team, identify the dropped workflow, and ask the executive sponsor for a 30-minute recovery call before procurement frames the renewal around price. I would not lead with a discount; I would lead with a save plan: target outcome, owner on each side, two adoption checkpoints, and a renewal decision date. If the customer still asks for a concession, I would tie any commercial give to a concrete recovery commitment, not a blanket price cut.

Question 2

You are presenting a QBR to a CFO who only cares about cost savings. How do you keep the conversation executive-level?

I would keep the product slides short and frame the QBR around financial outcomes. So I would start with what we agreed success looked like, then show where we reduced manual work, avoided support costs, or improved time to value. If I had adoption metrics, I would connect those to dollars instead of just saying logins went up. And if we are behind, I would be direct about that and show what we are changing before the next renewal checkpoint.

Clarity

8/10

Specificity

7/10

Structure

8/10

Pace

141 wpm · 5 fillers

One thing to fix

Good executive instinct. Add one example metric so this does not sound like generic QBR advice.

Rewritten

I would open with the CFO outcome, not the feature list: "Last quarter we agreed success meant reducing manual reconciliation time by 20 percent and cutting support escalations tied to billing errors." Then I would show three numbers: adoption of the workflow, hours saved, and risk remaining. If we are behind, I would say so plainly and bring a recovery plan with dates and owners. That keeps the QBR at the business level while still proving I understand the product behavior underneath.

Question 3

A customer is pushing hard for a roadmap feature and says they will not renew without it. Product says it will not ship this year. What do you do?

Um, I would not promise the feature. I would probably try to understand what problem they are trying to solve and see if there is a workaround. I would also talk to Product and explain the revenue impact, but if the answer is no then I would be honest with the customer. I think the key is to preserve trust and not overcommit just to save the renewal.

Clarity

7/10

Specificity

5/10

Structure

6/10

Pace

134 wpm · 7 fillers

One thing to fix

You chose the right principle. Now add the commercial path: quantify impact, document alternatives, and set a renewal decision plan.

Rewritten

I would not promise a roadmap item Product has already ruled out. I would first get precise on the business problem behind the feature, the revenue at risk, and whether an existing workflow can cover 70 to 80 percent of the need. Then I would bring Product the quantified impact and ask for a clear customer-facing position, not a vague maybe. With the customer, I would be direct: here is what will not ship this year, here is the workaround we can support, and here is the decision timeline for renewal. That protects trust while still giving Sales and Product a real commercial plan.