What the VP CS Role Requires at Each ARR Stage
At under $10M ARR, the VP of Customer Success is primarily an individual contributor with management responsibility — they should be onboarding and managing customers directly while building the CS infrastructure and team. A purely strategic VP CS at this stage will be overqualified for the current problem and likely to leave when they realise the role requires more hands-on customer work than expected.
At $10M–$30M ARR, the VP CS transitions to managing a team of CSMs while owning the operational infrastructure — health scores, QBR cadences, expansion playbooks, and churn prediction. The role becomes more purely managerial, and candidates who resist moving away from direct customer work will become bottlenecks rather than multipliers.
At $30M ARR and beyond, the VP CS or CCO (Chief Customer Officer) role becomes fully strategic — setting the CS strategy, building the team, and representing customer health and expansion at the executive level. Candidates at this level typically have built CS organisations at comparable-stage companies and bring a repeatable playbook for the specific ARR stage the company is entering.
Evaluating VP Customer Success Candidates
NRR ownership. Ask VP CS candidates to describe the NRR they were accountable for in their last role, what the trend was during their tenure, and what specific actions they took to improve it. The specificity of this answer reveals whether they genuinely owned the metric or simply reported on it. Candidates who describe NRR improvement in terms of process changes and team actions rather than just favourable market conditions are demonstrating genuine accountability.
Churn root cause analysis. Ask candidates to describe the most significant churn event they experienced in their last role — the customer, why they left, and what the VP CS did in response. How they describe this situation reveals their analytical depth, their emotional intelligence, and whether they blame the product, the sales team, or the market rather than examining what the CS function could have done differently.
Expansion motion ownership. In the current SaaS environment, a VP CS who only focuses on churn prevention and not on expansion revenue is leaving significant value on the table. Evaluate candidates on their expansion playbooks — how they have built upsell and cross-sell motions within the CS function, and what the revenue impact was.
"41 days. A $275K search. Two firms failed in 60+ days. That's not luck — that's a different system."
— Majhi Group case study. Read the full case study →