Customer Success
Customer Success is the organisational function responsible for ensuring customers achieve their desired outcomes with a product, driving retention, expansion, and advocacy. Customer success (CS) emerged as a distinct discipline in the SaaS era because subscription business models require ongoing customer value delivery - a customer who doesn’t get value churns. CS teams own the ongoing relationship, typically from post-sale handoff through renewal, upgrades, and expansion.
What customer success teams do
Six common responsibilities:
Onboarding and activation. Guiding new customers through implementation to first value.
Ongoing relationship management. Regular check-ins, health monitoring, proactive outreach.
Product adoption. Ensuring customers use the features and workflows that correspond to their desired outcomes.
Expansion and upsell. Identifying growth opportunities and driving expansion revenue.
Renewal management. Preventing churn at the renewal moment; negotiating terms.
Advocacy and reference development. Turning satisfied customers into referenceable advocates.
The CS team structure
Four common models:
High-touch (dedicated CSMs). Each customer gets a specific Customer Success Manager. Common for enterprise and high-ARR customers. Expensive but effective.
Low-touch or pooled. A team handles many customers through scalable engagement - emails, webinars, community, automated playbooks. Common for mid-market SaaS.
Tech-touch. Primarily automated engagement. In-product messages, email sequences, documentation, community. Common for SMB and freemium SaaS.
Tiered. Different customer segments get different touch models. Enterprise high-touch, mid-market pooled, SMB tech-touch. Most mature programmes use this structure.
Customer-success metrics
Six metrics CS teams are judged on:
Net Revenue Retention (NRR). Most important. Tracks whether the existing customer base is growing (>100%) or shrinking.
Gross Revenue Retention (GRR). Strict churn measure, excludes expansion. Indicates how well CS prevents loss.
Churn rate. Customers or revenue lost.
Activation and adoption rates. Percentage of customers reaching defined value milestones.
Customer health scores. Composite metrics predicting retention likelihood.
Net Promoter Score (NPS). Customer satisfaction proxy.
Customer health scoring
Four components of most health scores:
Usage metrics. Feature adoption, session frequency, seat activation.
Engagement with CS. Responsive to outreach, attends QBRs, opens emails.
Support signals. Ticket volume, sentiment, escalation frequency.
Commercial signals. Payment status, contract term, multiple-year commitments.
A weighted composite produces a green/yellow/red classification that drives CS actions. Proactive intervention on yellow accounts prevents them from becoming red.
Customer-success common failures
Four patterns:
Reactive rather than proactive. CS only hears from customers when something is broken. By then, it’s often too late to save them.
No clear ownership of outcomes. Sales wants the renewal, Product wants adoption, CS wants both but owns neither. Organisational ambiguity kills effectiveness.
Over-reliance on relationship. CS managers who are friendly but don’t drive business outcomes. Customers like them; customers still churn.
Tool-driven instead of outcome-driven. CS teams optimising for Gainsight metrics or ChurnZero scores without connecting to real customer outcomes.
CS and the sales relationship
Three common handoff patterns:
Sales closes, CS takes over. Standard model. Sales-to-CS handoff is a critical moment.
Shared ownership. Sales and CS share the account throughout; neither owns renewal alone. Common in enterprise.
CS owns expansion. CS handles all post-sale revenue including new upsells. Sales only handles new logo acquisition.
The handoff pattern affects how CS is structured, compensated, and measured. Mismatched handoffs produce customer-experience problems and organisational friction.
How content supports customer success
Five content categories that directly support CS:
Onboarding content. Articles, videos, documentation that accelerate new-customer activation.
Feature-adoption content. Use-case libraries, tutorials, integration guides that drive deeper product use.
Customer stories. Case studies and testimonials that help customers see what’s possible with the product.
Community content. Forums, Slack groups, user-group events. The social reinforcement that compounds retention.
Power-user content. Advanced workflows, best-practice guides, expert content that turns satisfied customers into advocates.
We built Penfriend partly because CS content programmes - often the most retention-impactful content category - are typically under-produced because the budget goes to acquisition content. Penfriend makes the CS content category economically defensible at the scale that actually moves retention metrics.
Related terms
- Churn - what CS exists to reduce
- Customer Retention - the CS function’s primary output
- Onboarding - the CS activity
- Net Revenue Retention (NRR) - the headline CS metric
- Customer Experience (CX) - the broader discipline CS operates within