I have led customer success or worked alongside it at four companies that take very different approaches to it, and the same pattern keeps appearing. The team is set up as a department, given retention and expansion targets, and then quietly handed responsibility for outcomes it does not control. The renewal slips, the team is blamed, and the fix usually involves changing the leader rather than the framing.
The framing is the actual problem. Customer success is not a department; it is an operational function that runs across sales, product, support and ops. When you treat it that way, the metrics change, the rituals change, and the team finally has the leverage it always needed.
Why the department framing breaks
A department owns its function. It hires for it, measures it, and gets rewarded for moving its number. The trouble is that the metrics customer success is measured on, retention and expansion, are produced by the entire customer journey, not by any one team. By the time the CS team meets the customer, the impressions formed in sales, the product fit decisions made in roadmap, and the support quality from week one have already loaded the dice.
If the CS team is held accountable for that outcome without the authority to shape the inputs, two things happen. They burn out chasing fires that started upstream. And the upstream teams stop owning customer outcomes because someone else is officially responsible. The structure produces exactly the wrong incentives.
What changes when you treat it as operations
Operational functions are different in kind from departments. They are responsible for an outcome that crosses teams, and their leverage comes from making the work of those teams visible and accountable, not from doing it themselves. Think of how a good operations function manages a manufacturing line: it does not build the product; it ensures the conditions for the product to be built well.
When CS is positioned this way, three shifts happen.
One: shared metrics
Retention is a company metric, not a CS metric. Sales gets a quality-of-fit number that affects their comp. Product gets time-to-value as a release metric. Support gets first-contact resolution. CS is the convener that watches the whole picture and escalates when the cross-team metric is at risk.
Two: ambient signal
The CS function is the eyes and ears. Their job is not just to save accounts; it is to make signal from customer reality flow to the teams who can act on it. The product team sees, every week, the three things customers most asked about. Sales sees, every week, the gap between what was promised and what landed. Support sees the patterns that keep coming back.
The best CS teams do not save accounts. They make the rest of the company so attentive that fewer accounts need saving.
Three: cross-functional rituals
The accounts that get saved are saved by the right person, often outside CS, intervening at the right moment. That only happens if there is a ritual that surfaces the right accounts to the right people on a cadence. A weekly cross-functional twenty-minute review of the at-risk accounts, with named owners from sales, product, support, and CS, will save more accounts than any number of CS-only QBRs.
What good metrics look like
The metrics shift to reflect the operational framing. The number we report up is not "CS-driven retention" because that number does not exist; everyone touched the customer. It is gross and net retention, broken down by cohort and by product, with the inputs that drive each made visible.
The inputs that consistently predict the output, in my experience, are time-to-first-value (how fast did the customer feel the product worked), product-quality-of-fit (do they use the parts of the product that matter for their use case), and contact-resolution-time on support tickets (do their problems get solved fast enough that they trust the company). Move those, retention follows. Try to move retention directly without moving them, you are doing theatre.
What this requires of leadership
For CS to operate this way, the CEO has to back the framing. The first time the head of sales says "that is a CS problem" about a renewal, leadership has to respond with "that is a company problem, here is what each team is going to change." Without that, the operational framing collapses back into the departmental one within a quarter.
I have seen this shift work most often when CS reports to the COO or directly to the CEO rather than to revenue. The reporting line matters because incentives follow it. CS reporting to revenue will, over time, start optimising for short-term renewals. CS reporting to operations will keep optimising for the inputs that produce durable retention.
One thing to try this week
If you only do one thing, start the cross-functional at-risk review. Twenty minutes, weekly, with sales, product, support, and CS in the room. The first one will be uncomfortable. By the fourth, you will start to see accounts saved by the right person at the right moment. That is what CS-as-operations looks like in practice.
The same thinking informs how we shape engagements at Cafiyn™ Biz: outcomes that cross teams need operational ownership, not departmental responsibility.