Customer Success Manager

The ability to diagnose a churn without blaming the customer, the product or sales. Bonus: the candidate names an early signal they could have caught sooner (an unreported sponsor change, a usage decline over 6 weeks, an unescalated support ticket). Candidates who have never really lost an account are not telling the truth or have not carried a substantial portfolio.

The ability to map stakeholders (executive sponsor, daily user, purchasing decision-maker, IT) and to build an expansion business case together with the sponsor over several months. Concrete on duration and stages. Candidates who handle a complex expansion in 2 sentences actually waved through passive renewals, not active customer success.

The ability to deliver an uncomfortable message without damaging the relationship. Maturity toward the relationship cost of pushing a customer to self-correct. Candidates who have never disagreed with a customer show a too-accommodating service posture that translates into over-promising and churn 6 to 12 months later.

Prioritization: (1) identify the sponsor's successor and secure a meeting within 5 days, (2) map usage per user to distinguish a decline from an internal reorg vs. product rejection, (3) reset the contract value with the new sponsor based on concrete use cases. Bad sign: the candidate proposes a generic re-onboarding demo without understanding the cause of the decline.

A combination of reading data (usage health, ticket history, contract due dates) plus prioritized 1:1s with the 5-8 most strategic accounts plus reading the predecessor's notes. Candidates who jump straight to a generic introductory email to all accounts skip the diagnosis and lose trust from day one.

The ability to hold a position against a sales team pushing for a fast close. Diagnosis first: why does the customer perceive less value? Plan: back to the sponsor with a tangible value measurement (measured ROI, unused use cases, under-activated features) before negotiating on price. Candidates who accept the discount to avoid conflict show a weakness that translates into structural ARR erosion.

Decomposing NRR = (1 minus gross churn) plus expansion. Identifying the levers: reduce avoidable churn (stronger onboarding, usage alerts), increase expansion (cross-selling modules, tier upgrades, raising the number of licenses). The ability to name realistic orders of magnitude: from 95 % to 115 % in 12 months typically requires 5 points on churn AND 15 points on expansion. Candidates who only talk about serving customers better miss the customer math.

Explicit segmentation by value and risk: the top 5 accounts (60 to 70 % of the ARR) on a weekly or biweekly touch, the mid-tier 10-12 accounts on a monthly touch, the long-tail 8-10 accounts on a quarterly automated touch. Bonus: the candidate adjusts by risk signal (a mid-tier account with a usage decline moves up temporarily). Bad sign: an identical touch for all accounts or prioritization by CRM alphabet.

Diagnosis first: why are 70 % of the usage unused? Weak initial onboarding, unidentified use cases, a team change on the customer side, or a product mismatch. A sequenced plan: (1) a discovery workshop with the sponsor to reset the business concerns, (2) identifying the 2-3 most relevant uncovered use cases, (3) an activation plan with an identified internal champion. Candidates who propose a general demo of all features show a product-centric rather than customer-centric posture.

A healthy cadence: usage signals (login, key features, frequency) daily on at-risk accounts, portfolio health (NPS, open tickets, near contract due dates) weekly, NRR / gross churn / expansion monthly. A distinction between leading indicators (usage, satisfaction) vs. lagging indicators (signed churn, lost ARR). Candidates who watch only NPS or only monthly revenue miss the operational steering level.

A typical structure: 60-75 min, opening with a review of the customer's business goals updated since the last QBR (15 min), an account of usage and delivered value in numbers (20 min), a discussion of the product roadmap on our side and the projects on the customer side (15 min), commitments and next steps (10 min). The executive sponsor's presence on the customer side is mandatory, otherwise reschedule. Candidates who describe a QBR as a product demo or a ticket status report miss the point of the exercise.

A systemic method: documented onboarding standards (milestones at T+7, T+30, T+60), measurable exit criteria from onboarding (regular login, 2 key features activated, an identified champion), maintaining alignment with the sales lead on the handover. An understanding that onboarding is the output of a cross-functional mechanism, not an isolated CSM process. Candidates who jump to adding more steps without changing the underlying sales-to-CSM handover will fail.

Openness: the ability to separate the feedback from a personal judgment. Bonus: the candidate names a concrete example of changing behavior after uncomfortable feedback. Candidates who describe how they explained their own logic to the manager instead of listening are to be assessed with caution (this may point to a coachability weakness; the profession requires a lot of self-correction).

A partnership posture: a documented handover with the AE (sales context, promises made, identified sponsor), structured bidirectional feedback; the relationship with the PM as co-construction (structured feedback of needs with business context, not a bare demand ticket). Candidates who speak with frustration about product (they don't listen to customers) or with contempt about sales (they over-promise) show a teamwork weakness that manifests as operational silos.

Commercial maturity: the ability to defer an upsell when the customer is not ready, or to recommend a scope downgrade instead of pushing a module whose current usage is low. Concrete: the candidate names an amount, an account and the long-term retention impact. Candidates who have never decided against a short-term upsell show a transactional bias that causes problems in long cycles or in structural NRR.