When Customer Success Becomes Too Much Admin
How I think about account coverage, where to spend the team's time, and what to do when keeping plans up to date starts crowding out customer work.
I’ve built and managed customer success teams using the familiar tools: quarterly reviews, health scores, and success plans. I still think they can be useful. I get less enthusiastic when keeping them up to date becomes a large part of the job.
A success plan takes time to maintain. So does a review deck. Multiply that by the accounts each person looks after, and you have to make choices about what deserves the attention.
I don’t think there’s a magic account count where the model stops working. A customer getting started with a complicated rollout may need much more help than a larger customer whose team already knows what it’s doing.
Where we’re putting the time
At Wiz, I’ve put systems and tools in place to prioritise 80% of our work on the 20% of customers who need us most.
That leaves an important question: how do we know who needs us? Revenue is part of the picture, but it can’t answer that on its own. I’d also look at what the customer is trying to do, what’s blocking them, and whether our involvement could help.
The group needing that attention should change. A customer working through a difficult rollout this month may be comfortable next month. Another might hit a problem we weren’t expecting. I’d be wary of turning the 20% into a permanent list of favourite accounts.
The remaining customers still need a way to get help, useful guidance, and someone paying attention when their situation changes. The point of prioritising is to make room for the work that needs more of us, without making everyone else fend for themselves.
Don’t wait for the next review
A quarterly review is too late to be your first sign that a customer is struggling.
Changes in usage, unresolved support issues, and missed rollout steps can all prompt a closer look. They aren’t diagnoses. A drop in activity might mean a team is stuck, or it might mean they’ve finished the task they came to do. Someone needs to check.
I’d use those signals to decide when to reach out, rather than wait for the next date in the calendar. I’d still keep a scheduled review when the customer finds it useful, especially when several teams need time together to make a decision.
Before preparing a deck, I’d want to know what we need to discuss. If neither side has much to say, a short update may be enough.
Some problems need another team
An account manager can explain a product limitation very well and still be unable to fix it.
Part of leading a customer team is making sure those problems reach someone who can act on them. That means being clear about who owns the next step, what information they need, and how the customer will hear back. Otherwise, the account team becomes a place where everyone else’s unfinished work collects.
We’ve consistently grown our NRR quarter-over-quarter. I’m pleased with that, but I wouldn’t claim a single process change explains it. I want to keep checking whether the way we spend our time is helping customers, rather than just making our internal reporting look tidy.
The question I’d ask of any playbook is fairly ordinary: does this help someone do the work, or have we given them another thing to maintain?