Customer Success Manager

When software was bought once and owned forever, signing the contract was the end of the story. The money had already arrived, so whether the customer opened the product again made no difference to revenue, and the salesperson moved on to the next deal.

Subscriptions inverted that arithmetic. The first year's payment is a fraction of what the account is worth, and if the customer doesn't sign again in year two, the cost of winning them in the first place never gets paid back. Yet for the twelve months between signing and renewal, nobody was watching what happened on the customer's side.

The gap usually announced itself in the final month, in a single email. It arrives about thirty days before expiry and it always says roughly the same thing: we rolled it out, only a handful of people on the team ended up using it, we won't be renewing. By then there is almost nothing to do. Eleven unused months can't be reversed in the thirty days that remain.

A customer success manager (CSM) is a person assigned to those twelve months. Rather than waiting for the customer to bring a problem, they reach out on a fixed rhythm, and when adoption starts slipping they show up in month two instead of month eleven. That's also why this is the first role to split off as a customer success team grows: answering inbound requests and initiating outbound conversations pull in opposite directions, and whoever is asked to do both ends up doing only the urgent one.

The day starts by opening the list of assigned accounts and sorting for the ones that look worse than last week. One person covers anywhere from twenty accounts to several hundred, which is too many to inspect daily, so a health score decides where to look first. It rolls signals like weekly active users, whether the core feature is being used, and recent ticket volume into a single green-to-red reading.

Four things repeat most days.

1. Reading signals. Finding the account whose weekly logins fell from 50 to 12, or the one that hasn't created a new document in two months. These surface here even when no complaint has been filed.
2. Time with the customer. A short call weekly, or a quarterly business review (QBR) every three months. A QBR is where the last quarter's results get assembled into numbers and put in front of whoever controls the budget.
3. Carrying things inward. Translating what a customer said into something the product team can act on, and routing technically stuck cases to technical support. Attaching which accounts and how many seats are affected is what gets an item onto a prioritization agenda.
4. Renewal work. A renewal doesn't start on the expiry date. Two or three months out, the evidence gets gathered, and this is also when room to add seats becomes visible.

Writing things down takes up about half the job. What was said on the call, what was promised as follow-up, who holds the decision inside the account — all of it goes into the record as it happens, so the customer never has to explain the same thing twice after a handoff.

On the customer's side there are at least two people in play at once: the practitioner who uses the product daily, and the person who decides whether to keep paying. The practitioner needs to know how a feature works; the decision maker needs to know whether the spend earned its keep. The same quarter gets described in two languages. Accounts where only the practitioner was ever satisfied are the ones that flip unexpectedly at renewal.

Inside the company, four seats interlock with this one.

1. Onboarding specialist — owns the first few weeks after signing: account setup, migrating existing material, the first training session. When that window closes the account transfers over, so the handoff is where unfinished items get identified.
2. Support agent — handles inbound tickets. When the same category of ticket comes from one account more than three times, it stops being a ticket problem and moves here.
3. Account manager (AM) — owns the contract and the upsell. Sometimes one person wears both hats; when the roles are split, they sync weekly on shared accounts.
4. The product team — the channel through which customer friction becomes a feature request. Requests aren't forwarded verbatim; they're forwarded with a count of how many accounts hit the same thing.

"Who's the CSM on that account? Logins have halved since last month."

Find the owner, check what's going on, and intervene.

"Renewal is two months out and we still haven't met the decision maker."

We've only been talking to practitioners, so we have no read on how the renewal will land.

"This isn't a ticket anymore — a CSM should take the account."

The same problem keeps recurring, so handle it at the account level rather than case by case.

At Pagedeck, Sofia covers forty enterprise accounts. Sorting Monday morning for accounts that turned red, she found one whose weekly active users had dropped from 60 to 20. Not a single ticket had been filed. On the call it turned out the team lead who had brought the product in had moved departments, and the people left behind had gone back to their old habits because nobody knew where documents were supposed to live.

Sofia ran another thirty-minute training for the remaining team that week and asked them to name a new internal owner. Two months later logins were back to 45. Had this surfaced a month before renewal, it would have ended differently.

The most common mistake is treating the role as support under another name. Both deal with customers who have already signed, so they look alike. What separates them is which direction the work starts from. Support begins when a ticket arrives and ends when it closes; a CSM moves while the customer is saying nothing at all. Collapse the two into one seat and urgent tickets always win, so the account that is quietly not using the product goes unexamined until its renewal date.

Reading the role as relationship maintenance is the other one. Frequent calls and quarterly visits make it look that way. But the numbers this seat is measured on are renewal rate and expansion revenue. Accounts on excellent terms decline to renew all the time. Mistake rapport for results and you spend your week with the customers who are pleasant to meet while the awkward accounts get postponed — and the risk usually sits in the awkward ones.