In Part 1 of this series, we covered how the shift to consumption-based pricing is forcing a fundamental rethinking of what customer success means — moving from reactive to proactive, rebuilding segmentation around usage signals, and evolving the metrics that actually matter.
In Part 2, we go deeper on the operational changes required to actually execute a modern CS motion in a consumption model.
The CS Team Structure Is Changing
The traditional CS team structure — a CSM owns a book of accounts and is responsible for everything from onboarding to renewal — doesn't scale well in a consumption model. Here's why:
When you have hundreds or thousands of customers consuming your product continuously, you can't rely on scheduled touchpoints to catch problems. You need a team structure that enables continuous monitoring and automated intervention at scale.
The teams we're seeing succeed have moved to a tiered model:
Digital CS tier: Automated, system-driven engagement for all accounts. Usage-triggered workflows, automated health score nudges, self-serve success resources. No human involvement unless a threshold is crossed.
Scaled CS tier: Human engagement for accounts that cross a usage or revenue threshold, or that show signals requiring intervention. One CSM covering 50-100 accounts with automated signal routing.
Strategic CS tier: High-touch engagement for the largest, most complex accounts. One CSM covering 10-20 accounts with deep relationship management.
The key is that movement between tiers is driven by signals, not by scheduled cadence. An account that starts in the digital tier can be automatically escalated to scaled CS when its health score drops, and then deprioritized back to digital when it recovers.
The Technology Stack for Consumption CS
Most CS platforms were built for seat-based SaaS. They're optimized for QBR management, renewal pipelines, and relationship tracking. They're not built for real-time usage monitoring and signal-based engagement.
The CS teams that are succeeding in consumption models have built or bought:
Usage intelligence layer: Direct integration with product usage data that gives CS visibility into what every customer is doing in real time. Not a nightly export — live data.
Health scoring engine: A model that takes usage signals, support data, CRM data, and billing data and produces a composite health score for every account. The score should predict churn risk and expansion opportunity, not just reflect historical usage.
Workflow automation: When a health score drops below a threshold, the right action should happen automatically — whether that's an email to the customer, a task for the CSM, or an alert to the account executive.
Expansion signal detection: Separate from churn risk, you need systems that identify when an account is ready for an expansion conversation. High usage growth, new team members joining, expansion into new use cases — these are all signals that should trigger action.
The CSM Role Is Evolving
The skills required to succeed as a CSM in a consumption model are different from traditional SaaS. The best CSMs we're seeing in consumption businesses are:
Data-literate: They can read a usage health dashboard and draw actionable conclusions. They understand what the data is telling them about customer health and expansion opportunity.
Proactive communicators: They reach out based on signals, not schedules. When a customer's usage drops, they're in touch immediately — not at the next QBR.
Commercially oriented: They understand that expansion is part of their job and are comfortable having commercial conversations with customers. They know how to identify expansion opportunity and when to bring in account executives.
Product experts: They can speak to how customers should be using the product and can diagnose adoption issues. They're part consultant, part technical advisor.
Measuring CS Performance in Consumption Models
The KPIs that matter for CS in consumption models are different from traditional SaaS:
Net Revenue Retention: The ultimate measure. Are you growing revenue from existing customers?
Churn rate by usage cohort: Not just overall churn rate, but churn rate broken down by usage behavior. This tells you which segments you're retaining and which you're not.
Expansion rate: How much new revenue are you generating from existing customers? In a healthy consumption business, this should be growing.
Time to value: How quickly do new customers get to their first meaningful usage milestone? This predicts long-term retention better than any other metric.
Health score accuracy: Is your health score actually predicting churn? Track the correlation between health scores and actual retention outcomes, and refine your model accordingly.
What Comes Next
The CS function in consumption-based SaaS is still evolving. The teams that are getting it right are investing in the data infrastructure, the tooling, and the organizational changes required to operate effectively.
The teams that are falling behind are the ones trying to apply traditional CS playbooks to a fundamentally different business model. They're doing quarterly reviews when they should be monitoring daily signals. They're staffing for relationship management when they should be investing in automation.
The shift is inevitable. The question is whether your CS team is ahead of it or catching up.