VP Customer Success: What the Role Demands

A VP of Customer Success is the executive accountable for ensuring customers achieve the outcomes they were promised, at a scale that makes the business commercially viable. The role sits at the intersection of revenue retention, product adoption, and long-term account growth, and it is one of the few leadership positions where failure shows up directly on the P&L without any ambiguity about who owns it.

Most companies hire for this role too late, define it too narrowly, or confuse it with a senior customer service function. None of those approaches work.

If you are building out your retention infrastructure, the broader thinking on customer retention is worth reading alongside this. The VP of CS role does not exist in isolation. It is one lever in a larger system, and understanding that system is what separates good hiring decisions from expensive ones.

What Does a VP of Customer Success Actually Own?

The title is common. The scope is not. Depending on the company, a VP of Customer Success might own onboarding, renewal conversations, expansion revenue, customer health monitoring, and CS operations. Or they might own a subset of those things with unclear boundaries around the rest. That ambiguity is where most CS leadership hires go wrong.

The clearest framing I have seen is this: the VP of CS owns net revenue retention. That means they are responsible not just for keeping customers from leaving, but for growing the revenue within the existing base. Renewals, upsells, and cross-sells that originate from CS activity all fall under their remit. If the number goes up, they contributed. If it goes down, they are accountable.

That framing changes everything about how you hire, how you measure, and how you structure the team beneath the role. A VP focused purely on satisfaction scores or NPS is managing inputs. A VP focused on net revenue retention is managing outcomes. There is a significant difference, and most job descriptions do not make it clear enough.

Understanding what actually drives customer loyalty matters here. Loyalty is not a byproduct of good service. It is a byproduct of customers achieving real outcomes. The VP of CS is the person responsible for making that happen at scale, which means they need to understand the product, the customer’s business model, and the commercial levers available to them.

The Commercial Framing Most Companies Get Wrong

I spent years watching agency leadership teams confuse activity with performance. We would hit our delivery targets, clients would say they were happy, and the account would still churn six months later because we had never connected our work to their actual business outcomes. The CS equivalent of this is a VP who runs high CSAT scores while net revenue retention quietly erodes.

The problem is structural. If you measure a VP of CS on satisfaction, they will optimise for satisfaction. If you measure them on retention rate in isolation, they will protect the base but not grow it. If you measure them on net revenue retention, they have to hold both things simultaneously: keeping customers and finding legitimate reasons to expand the relationship.

This is not a subtle distinction. A business that retains 90% of customers but sees average contract value decline by 8% year over year is losing ground, even if the retention rate looks healthy on a slide. I have seen this pattern in agency client portfolios more times than I can count. The apparent stability was masking a slow contraction, and no one wanted to say it out loud because the headline number looked fine.

A VP of CS who understands commercial reality will not let that slide. They will flag it, quantify it, and bring a plan to address it. That requires a different kind of leader than someone who is primarily motivated by customer empathy, though empathy is still table stakes for the role.

The Forrester research on cross-selling and upselling is useful context here. The conditions that make expansion revenue possible are not accidental. They are engineered, and the VP of CS is the person responsible for engineering them.

The Relationship Between CS and Sales at the VP Level

One of the most consequential decisions a company makes is where the boundary sits between Customer Success and Sales. Get it wrong and you get either a CS team that avoids commercial conversations because they feel like selling, or a Sales team that re-enters existing accounts and damages the trust CS has built.

The VP of CS needs to define this boundary clearly, negotiate it with the Sales leadership, and hold it consistently. That means deciding which expansion conversations belong to CS, which belong to Sales, and what the handoff process looks like when an opportunity crosses the threshold.

In most SaaS businesses I have observed, the cleaner model is to give CS ownership of expansion within the existing product footprint and give Sales ownership of new product lines or significant contract restructuring. But that model only works if the VP of CS has built a team that is comfortable with commercial conversations. A CS team that routes every upsell to Sales because they do not want to “ruin the relationship” is leaving revenue on the table and creating friction in the customer experience.

The strategic customer success model addresses this directly. When CS is positioned as a strategic partner rather than a support function, the commercial conversation becomes a natural part of the relationship rather than an awkward interruption.

What to Look for When Hiring a VP of Customer Success

Most hiring processes for this role over-index on industry experience and under-index on commercial judgment. I have watched companies hire a VP of CS from a well-known SaaS brand, assume the playbook transfers, and then discover six months later that the person cannot operate without the infrastructure they had at their previous employer.

The questions worth asking in a hiring process are not about what they have done. They are about how they think. Specifically:

How do they define success for the CS function? If the answer centres on satisfaction scores or qualitative customer feedback without any reference to revenue metrics, that tells you something. If they immediately talk about net revenue retention and how they have moved that number, that tells you something different.

How do they approach customer segmentation? A VP who treats all customers the same is not thinking commercially. Resources are finite. The question is always how to allocate them to maximise retention and growth across the portfolio. A candidate who has a clear view on how to segment and why will be more effective than one who defaults to equal treatment as a principle.

How do they handle a customer who is unhappy but not at risk of churning? This is a nuanced situation. The commercially naive response is to throw resources at the unhappy customer. The commercially grounded response is to understand whether the unhappiness is a signal of future churn risk or a manageable friction point, and then allocate accordingly.

A good customer success plan at the account level reflects this kind of thinking. It is not a list of activities. It is a structured view of where the customer is, where they need to get to, and what the CS team is doing to close that gap in a way that also protects and grows the contract value.

Building the Team Beneath the VP

The VP of CS is only as effective as the team they build. That team typically includes Customer Success Managers at various levels, a CS Operations function, and in larger organisations, a dedicated renewals team. The VP’s job is to structure this in a way that matches the customer base, not in a way that mirrors what they have seen at previous employers.

One of the more common structural mistakes is building a flat CS team where every CSM handles the same mix of accounts regardless of size or complexity. This creates coverage problems. Enterprise accounts need dedicated, senior attention. SMB accounts need efficient, scalable processes. Trying to serve both with the same model means you are either over-investing in SMB or under-investing in enterprise, and usually both.

The VP needs to design coverage models that reflect the commercial reality of the customer base. That means understanding the revenue distribution across the portfolio, the churn risk profile by segment, and the expansion potential in each tier. B2B customer loyalty operates differently across segments. What drives retention in an enterprise account is not the same as what drives retention in a mid-market account, and the team structure should reflect that.

There is also the question of when to build versus when to buy capacity. Some companies at early stages of CS maturity are better served by customer success outsourcing for specific segments or functions while they build internal capability. The VP needs to be honest about this rather than defaulting to headcount as the solution to every coverage problem.

The Metrics a VP of CS Should Be Held To

When I was running agencies, I learned quickly that the metrics you report externally and the metrics you actually manage the business by are often different things. The external metrics tell a story. The internal metrics tell the truth. A VP of CS needs to be clear about which is which.

The metrics that matter for this role are:

Net Revenue Retention. This is the primary commercial metric. It captures both churn and expansion in a single number. A NRR above 100% means the existing customer base is growing even without new customer acquisition. Below 100% means the base is contracting. The VP owns this number.

Gross Revenue Retention. This strips out expansion and isolates pure churn. It tells you whether you are keeping customers, independent of whether you are growing them. Both numbers matter, and a VP who only reports NRR can mask a churn problem behind strong upsell performance.

Time to Value. How quickly do new customers reach the outcome they were sold? This is a leading indicator of long-term retention. Customers who take too long to see value are at risk before they have even completed their first contract period. HubSpot’s analysis on reducing churn consistently points to early value realisation as one of the strongest predictors of long-term retention.

Customer Health Score Distribution. Not the average health score, which can hide a bimodal distribution. The VP should be looking at how many accounts are in each health tier and whether that distribution is shifting over time. A rising average driven by a handful of very healthy accounts while the middle of the portfolio deteriorates is a warning sign, not a success story.

Expansion Revenue from CS Activity. Separate from Sales-led expansion, this measures the commercial contribution of the CS team directly. If the VP is claiming that CS drives expansion, this number should be trackable and growing.

Understanding customer lifetime value sits underneath all of these metrics. The VP of CS is, in effect, the person responsible for maximising CLV across the existing customer base. Every structural decision, every resource allocation, every process they build should be oriented around that outcome.

The Churn Signal Problem

Most churn is predictable. The signals are there. The problem is that most CS teams either do not collect them systematically or do not act on them quickly enough. The VP of CS is responsible for building a function that is genuinely predictive rather than reactive.

This requires investment in data infrastructure, clear health scoring methodology, and a culture of early intervention. A CSM who waits until a customer raises a formal complaint before flagging a risk is operating too late. By the time a customer is unhappy enough to complain, the decision to leave is often already forming.

The VP needs to build habits and processes that surface risk earlier. That means monitoring product usage data, tracking engagement with communications, watching support ticket patterns, and using tools like churn surveys to understand the reasons behind attrition when it does happen. You cannot prevent the churn you do not understand.

One pattern I saw repeatedly in agency client relationships was what I would call “polite churn.” The client never complained. They were always pleasant on calls. And then one day the renewal conversation revealed that they had been quietly evaluating alternatives for six months. We had mistaken the absence of complaints for the presence of satisfaction. Those are not the same thing, and a VP of CS who builds a team culture around that confusion will consistently be surprised by attrition they should have seen coming.

Loyalty programs, when structured well, can surface engagement signals that predict retention. The mechanics of wallet-based loyalty programs are one example of how engagement data and retention incentives can be combined in a way that gives CS teams earlier visibility into customer intent.

When the VP of CS Becomes a Strategic Voice in the Business

The most effective VPs of Customer Success I have observed do not just manage their function well. They become a source of intelligence for the wider business. They bring product teams the patterns they see in customer feedback. They bring Marketing the language customers use to describe value. They bring the executive team early warning signals about market shifts that show up in customer behaviour before they show up in revenue numbers.

This is the version of the role that justifies the VP title. Not just running a team that keeps customers from leaving, but being the person in the room who understands the customer base better than anyone else and can translate that understanding into decisions that make the whole business stronger.

Getting there requires the VP to build credibility outside their own function. That means showing up to commercial conversations with data, not just customer stories. It means being willing to say when a product gap is driving churn, even if that is an uncomfortable message for the product team. It means being the person who connects retention performance to revenue forecasting in a way that Finance can work with.

The broader work on retention optimisation through testing is relevant here. A VP who brings an analytical, iterative mindset to retention, rather than relying on intuition and relationship management alone, will build a function that compounds over time rather than plateauing.

If you are working through the broader architecture of customer retention across your business, the resources at The Marketing Juice’s customer retention hub cover the full picture, from loyalty mechanics to CS operations to the commercial logic of retention investment.

About the Author

Keith Lacy is a marketing strategist and former agency CEO with 20+ years of experience across agency leadership, performance marketing, and commercial strategy. He writes The Marketing Juice to cut through the noise and share what works.

Frequently Asked Questions