Remote heads of customer success own the post-sale customer relationship at the organisational level — building the team, the processes, and the playbooks that turn new customers into renewing, expanding accounts while keeping churn below the thresholds that determine whether a SaaS business grows or stalls. The role is where customer relationship management becomes revenue strategy.
What they do
Heads of customer success build and lead the customer success team — hiring CSMs, team leads, and customer success operations specialists; structuring the team by segment, industry, or customer lifecycle stage; and setting the capacity model that determines how many accounts each CSM can carry at the required engagement level. They own the metrics that define CS health: net revenue retention (NRR), gross revenue retention (GRR), customer health scores, time-to-value, and expansion revenue from upsell and cross-sell. They design the customer journey from onboarding through adoption, expansion, and renewal — defining the engagement model, building the QBR and executive business review cadence, and creating the escalation processes for at-risk accounts. They partner with sales on expansion motions, with product on customer feedback loops, and with marketing on customer advocacy and reference programmes. They report to the CEO or CRO and are accountable for the retention and expansion revenue that make up the majority of ARR at mature SaaS companies.
Required skills
Proven track record of building and scaling a customer success organisation — managing a team, defining hiring plans, and creating the processes and playbooks that allow the CS function to scale without the head of CS being the primary relationship holder for every account — is the foundational leadership requirement. Deep understanding of SaaS customer success metrics and how they connect to the P&L (NRR, GRR, LTV, CAC payback, expansion MRR) is required for operating as a business leader rather than a senior CSM. Experience designing and executing customer onboarding, adoption, and renewal programmes at scale — with documented outcomes in retention and expansion rates — demonstrates operational depth. Strong cross-functional influence skills for aligning product, sales, and marketing around customer outcomes are essential.
Nice-to-have skills
Experience with CS platforms (Gainsight, Totango, ChurnZero, Catalyst) at an administrative level — building health score models, automating engagement triggers, and reporting on portfolio health across a large account base — is required at mature CS organisations with data-driven engagement models. Background in PLG (product-led growth) environments — where the CS motion is lighter-touch for low-ACV accounts and high-touch for strategic accounts — is valued at companies with hybrid sales motions. Revenue operations expertise for designing the CS compensation model, territory structure, and capacity planning that align CS team incentives with retention and expansion outcomes.
Remote work considerations
Customer success leadership is compatible with remote work — team management, strategy development, cross-functional partnership, and board-level reporting are all async-compatible. The relationship-critical dimension — executive sponsorship at strategic accounts, high-stakes renewal negotiations, and in-person QBRs — requires periodic travel, typically 2–4 days per quarter per strategic account cluster. Remote heads of CS invest deliberately in team cohesion for distributed CS teams, building shared playbooks, regular team rituals, and clear escalation paths that function without physical co-location. Managing a distributed CS team across timezones requires structured async communication standards and explicit coverage models for accounts in multiple geographies.
Salary
Remote heads of customer success earn $160,000–$240,000 USD in total compensation (base + variable) at mid-to-senior level in the US market, with VP of Customer Success at enterprise SaaS companies reaching $260,000–$350,000+ including equity. European remote salaries range €100,000–€170,000. Enterprise SaaS companies with high ACV and complex customer implementations, companies with NRR above 120% where CS is a primary growth lever, and Series B+ companies scaling from founder-led CS to a managed function pay at the upper end.
Career progression
Senior customer success managers, CS team leads, and account management leaders with demonstrated retention and expansion outcomes move into head of CS roles. From head of CS, the path runs to VP of Customer Success, Chief Customer Officer (CCO), and CRO at companies where CS owns expansion revenue. Some heads of CS move into GM roles for specific customer segments, product leadership roles focused on adoption, or CS consulting and advisory.
Industries
SaaS companies across all verticals (where recurring subscription revenue makes retention and expansion the primary growth levers), enterprise software companies with complex implementations and long sales cycles, marketplace businesses with supply-side customer success requirements, and fintech companies with compliance-sensitive customer relationships are the primary employers. The function is most developed at Series B and beyond, where the cost of unmanaged churn exceeds the cost of building a structured CS organisation.
How to stand out
Demonstrating specific NRR and GRR improvements you drove — the retention programme that reduced churn from X% to Y%, the expansion motion that increased NRR from 105% to 118% — positions CS leadership as a revenue function with measurable business impact. Being specific about the team you built — how many CSMs, how structured by segment, what the coverage ratio was — shows organisational depth. Remote candidates who demonstrate experience building distributed CS teams with documented playbooks, health scoring models, and engagement cadences that scale beyond the leader's direct involvement show the systems-thinking required for leading a CS organisation that functions without micromanagement.
FAQ
What is the difference between net revenue retention and gross revenue retention? Net revenue retention (NRR) measures the percentage of revenue retained from existing customers including expansions (upsell and cross-sell) — an NRR above 100% means the existing customer base is growing even without new customers, which is the defining characteristic of a compounding SaaS business. Gross revenue retention (GRR) measures the percentage of revenue retained from existing customers excluding expansions — it captures only churn and contraction, with a theoretical ceiling of 100%. NRR is the primary CS success metric at growth-stage SaaS companies; GRR is more useful for understanding the raw churn rate independently of expansion. A company with 85% GRR and 115% NRR has significant churn but is compensating with strong expansion — the CS team needs to both fix the churn problem and protect the expansion motion.
How does a head of customer success structure a CS team? The most common structures are by customer segment (enterprise, mid-market, SMB — with different engagement models and CSM ratios for each), by product line (where customers use different products requiring different expertise), or by customer lifecycle stage (onboarding, adoption, renewal — with handoffs between specialists). Segment-based structure is most common: enterprise accounts get dedicated high-touch CSMs at 1:10–1:30 ratios; mid-market accounts get pooled or scaled CSMs at 1:50–1:100 ratios; SMB and digital accounts get a tech-touch model with automated engagement and no dedicated CSM. The structure choice determines hiring plans, cost models, and the engagement experience each customer segment receives.
What is a customer health score and how is it built? A customer health score is a composite metric that predicts the probability of a customer renewing, expanding, or churning — typically displayed as a red/yellow/green indicator in a CS platform. It is built from signals across product engagement (login frequency, feature adoption, API usage), support activity (ticket volume, escalation history, time-to-resolution), relationship health (executive sponsor engagement, NPS/CSAT responses, QBR attendance), and commercial signals (contract utilisation, invoice history). The weights for each signal are calibrated against historical churn and renewal data — signals that were strong predictors of churn in the past get higher weights. Health scores are imperfect leading indicators; the best CS organisations use them as triggers for human intervention, not as a substitute for relationship-based risk assessment.