Customer SuccessSomeone owning accounts at a company selling annual contracts

When I have sixty accounts and time for about ten, I want to know where to spend the effort, so it goes where it can still change the outcome.

Khi tôi có sáu mươi khách và thời gian cho khoảng mười, tôi muốn biết nên dồn công vào ai, để công sức của tôi đi vào chỗ nó còn đổi được kết quả.

Job context

Who: An owner with a book far larger than their hours
When: At the start of each week when choosing what to do
Trigger: A large account lapsing while a month went to a small, loud one
Situation: The loudest account absorbs the attention, and it is rarely the most important one
Constraints: Hours cannot grow, and every account believes it is the priority

The loudest accounts take the time
High
Attention is allocated by volume rather than by value or risk.
Root cause: Requests arrive by push; priorities must be pulled
Cannot tell if the effort changes anything
High
Some renew whatever you do; others leave whatever you do.
Root cause: One's own impact cannot be separated from the account's own trajectory
Large revenue does not mean high priority
Medium
A large stable account needs less than a mid-sized wobbling one.
Root cause: Books are sorted by revenue because it is the only number available
Cannot say no to a customer
Medium
Refusing a small request creates immediate risk; neglecting another account shows nothing.
Root cause: The cost of refusing is immediate; the cost of neglect appears months later
The book changes and the allocation does not
Medium
Attention habits formed last quarter keep running this quarter.
Root cause: No cadence forces a re-look at allocation

A solution is not the same thing as a product — a customer can hire a behaviour or a workaround too.

Tier accounts by revenue
Product
The commonest allocation, ignoring risk entirely.
Automated health-score ranking
Product
Produces an order and says nothing about whether effort can change it.
One-to-many programmes
Service
The only way to serve the long tail of the book.
A weekly list of five accounts to watch
Workaround
Owners build the allocation mechanism the tools lack.
Ask a manager who to prioritise
Behaviour
Escalates the decision, and the answer usually comes back as revenue anyway.

Books are sorted by revenue because it is the number at hand, while the real question is where effort changes the outcome.
Why existing solutions fail: Revenue exists in every system; influenceability is a judgement about the future, and no system stores judgements.
Potential opportunity: Recording the influenceability judgement at allocation time and checking it back a quarter later.
The cost of refusing shows immediately while the cost of neglect appears months later and is attributed to nobody.
Why existing solutions fail: Every system records requests handled; a neglected account creates no record until it leaves, by which point the cause is too distant to connect.
Potential opportunity: Recording the accounts not touched in a period, so neglect gets a number.