Questions to Ask VP of Customer Success
Questions for an interview with a VP of Customer Success, useful whether you are hiring one or considering joining their team: retention numbers, coverage ratios, who owns renewals, how risk is spotted, and what they have decided not to do.
The questions
Open any question for the note
How do you define the job of your team: adoption, retention, revenue, or all three?
Why ask it
Customer success means very different things at different companies, and this answer sets up everything else. A leader who claims all three without describing tradeoffs has not had to choose yet, which usually means the team is stretched thin and measured on things it cannot control.
Which number are you held to, and where does it sit today?
Why ask it
Net revenue retention, gross churn, and logo retention tell different stories, and the honest answer includes the current figure rather than a target. Someone who cannot state their own retention number to a point or two is not running the function on data.
Does your team own renewals and expansion, or does sales?
Why ask it
This is the fault line in most customer success organizations. Owning the number gives the team leverage and a quota; not owning it makes them advisors whose warnings can be ignored. Either can work, but ask how conflicts with sales get resolved when they arise.
What is your coverage ratio per person, and how did you arrive at it?
Why ask it
Ask for accounts and recurring revenue per manager. The reasoning matters more than the number: a ratio derived from workload and touch model is a deliberate design, while a ratio inherited from a headcount budget means the team is covering whatever it can reach.
How is the customer base segmented, and what does a low-touch customer actually receive?
Why ask it
Everyone describes a tiered model. Fewer can say what the bottom tier really gets beyond automated email. Ask what proportion of revenue sits there and what its retention looks like, because that is often where quiet churn accumulates.
What happens in a customer's first ninety days?
Why ask it
Onboarding is where most churn is decided, well before the renewal. Look for a defined sequence with an owner, a definition of activation, and a measured time to first value. If onboarding belongs to whoever has capacity, expect inconsistent outcomes.
How do you know an account is in trouble before the renewal conversation?
Why ask it
Strong answers name leading signals: usage decline, a champion leaving, support ticket sentiment, an unpaid invoice, executives no longer joining calls. Weak answers describe quarterly business reviews, which surface problems too late to fix.
What goes into your health score, and how often is it wrong?
Why ask it
The second half is the real question. Every scoring model produces green accounts that churn, and a leader who has studied those misses will tell you what they learned. A team that treats the score as truth will keep getting surprised.
Tell me about a customer you expected to keep and lost.
Why ask it
You are listening for a specific account and a diagnosis that includes their own part in it: a missed signal, an onboarding gap, a promise sales made. If the story is entirely about the customer's budget or a reorganization, that pattern will repeat.
How much of your team's week goes on work a system should be doing?
Why ask it
Manual reporting, copying notes between tools, and building decks eat a large share of many customer success teams. Ask what they have automated and what they gave up trying to automate, which shows whether they invest in operations or just add headcount.
How are your people compensated, and what behavior does that produce?
Why ask it
Pay drives conduct more reliably than any playbook. A retention bonus can make people avoid hard conversations; expansion commission can push customers into purchases they will regret. A thoughtful leader will name the distortion their own plan creates.
What gets escalated to product, and what happens after it does?
Why ask it
Ask for the mechanism and a recent example that resulted in a shipped change. Customer success leaders who cannot point to one are being used as a complaint buffer, which is a hard job to keep good people in.
What do you do when something was sold that the product does not do?
Why ask it
This happens everywhere. The useful answer covers both the immediate handling with the customer and the upstream fix, whether that is joining deal reviews or a documented handover. Blaming sales without a process attached tells you the loop is not closed.
How do you hire for this team, and what do you screen out?
Why ask it
Listen for whether they hire for domain fluency, commercial instinct, or empathy, and what they consider disqualifying. Leaders who have hired badly once have a sharp answer here, usually about people who avoid confrontation or cannot hold a business conversation.
What does a career path on your team look like?
Why ask it
Ask where people have gone: into management, into product, into sales, out of the company. A team with no internal progression tends to churn its best people every two years, and the answer is a fair proxy for how they are developed.
How do you handle a customer who is unhappy but not going anywhere?
Why ask it
These accounts are easy to deprioritize and are the ones that quietly poison references and expansion. Ask what they do differently for a captive but frustrated customer, which reveals whether the team is managed by risk score alone.
What did you change your mind about in the past year?
Why ask it
Look for something operational and specific: a touch model that did not work, a tool they removed, a segment they stopped serving that way. An inability to name anything suggests either a very stable business or a leader not testing their own assumptions.
What have you decided not to do, even though customers keep asking?
Why ask it
Saying no is what makes a strategy real. A clear refusal, with the reasoning, shows a leader who protects their team's focus. A leader who accommodates every request produces a team that is busy, well liked, and ineffective.
When budgets are cut, how do you show what this team is worth?
Why ask it
Customer success is often first to be trimmed because its value is indirect. Ask what analysis they use, for example retention differences between covered and uncovered accounts. Someone who has survived a cut will have a concrete answer.
What is broken right now that you have not fixed yet?
Why ask it
Save this for last. The willingness to name an unresolved problem, and to say why it is not yet solved, separates a candid operator from a polished one. It also tells you exactly what you would be walking into.
Getting past the polished answers
Practical guidance for the conversation itself
How to press for substance
Ask for the number, then the definition
Retention figures are easy to flatter depending on whether they are gross or net, logo or revenue, and whether downgrades count. Ask how the metric is calculated before you form a view of whether it is good.
Ask about scale, not just experience
Running customer success for forty enterprise accounts and for forty thousand self-serve customers are different jobs with different skills. Establish which one they have actually done, and how recently.
Follow every claim with a for example
One follow-up separates a real practice from a description of one. Anyone can talk about proactive engagement; fewer can walk through the last account they saved and what they did on which day.
What a strong answer sounds like
- Numbers offered without being asked twice, including the unflattering ones.
- Clear ownership boundaries with sales, support, and product, described the same way each time it comes up.
- A named customer story with dates, people, and what they got wrong.
- An account of what the team stopped doing to make room for something else.
- Their own compensation plan described with its side effects, not just its intent.
Answers to be careful with
Churn explained entirely by outside forces
Budget cuts and reorganizations are real, and they are also the easiest place to put every loss. Ask what share of churn they consider preventable, and how they arrived at that split.
A team measured on activity
Reviews completed, calls made, and tickets closed are workload measures. If nobody is accountable for a retention or revenue outcome, the function is difficult to defend and easy to cut.
Tooling as the answer to everything
A new platform rarely fixes an unclear touch model or an unresolved boundary with sales. Ask what problem the tool solved and what it did not.
No unresolved problems
Every customer success organization has something broken: onboarding capacity, data quality, a segment nobody covers well. A leader who names none is either new to the role or managing the interview rather than answering it.