The Account Everyone Knows Is Already Gone
There is a bad-fit account on your list that everyone already knows is gone.
It was sold something your product does not do. It has needed custom work since the very beginning.
The success plan has never had traction, and no amount of relationship work will change any of that, because the mismatch was there on the day the contract was signed.
The CSM knows.
The support lead knows.
The engineer who built the third custom export knows.
It has been on that list for two quarters. It will be there next quarter, and the quarter after, unless somebody makes a call.
Meanwhile your strongest CSM spends their day on it. Then the next day. Then the escalation call that runs long and pushes the review of four healthy accounts to next week.
Everyone can see it. Nobody will decide it.
Today’s post is about how to price that account and make the call.
The Account Has Two Prices and You Only Track One
Open your CRM and look at that account. You will find a number. Annual contract value, renewal date, owner.
That number is what the account pays you.
Look for what the account costs you to hold. That figure exists nowhere in the system.
The hours, the custom builds, the escalations, the exec time, the roadmap slots it consumed on the way here. Your CRM was built to track revenue and it does so.
→ You are running portfolio decisions on half the ledger.
Why the Cost Stays Invisible
The cost is real. It splits across 4 budgets, and the split is what hides it:
1. CS pays in hours
Your CSM spends half a day every week vs. just a few hours on a comparable account.
In the system that time is logged as account management, identical to every other line, so the week reads normal.
What it costs shows up somewhere else.
Two healthy accounts got a rescheduled check-in. An expansion conversation slipped a month.
The CSM starts Monday already behind.
2. Engineering loses sprint capacity
The requests arrive one at a time, each one small, each one reasonable on its own.
A custom export in March.
A field mapping in May.
A webhook nobody else uses in July.
The manager approving the eleventh request sees one ticket rather than a pattern, so it gets a yes.
Two sprints later a feature hundreds of your other customers asked for slips to next quarter.
3. Support carries the escalation load
The tickets look like regular tickets with a similar level of priority like any other customer.
What the queue does not show is that:
This account raises 5 times what its peers raise,
Half those tickets are the product working as designed against a use case it was never built for,
Your two most experienced agents now handle them by default because nobody else knows the workarounds.
4. Product gives up roadmap slots
A build went to a feature one logo uses.
The features that lost that slot were wanted by tens of other customers. That trade never appears in a review, because the roadmap shows what shipped rather than what it displaced.
→ Each owner sees a rounding error and approves it, and the rounding errors all belong to the same account.
Nobody assembles the total, because assembling it is nobody’s job.
What Happens When the Total Is Missing
An account with no cost attached to it stays in save status by default.
Save status generates work. That work lands on the person closest to the customer, which means it lands on a CSM who cannot change product fit, pricing, or what Sales promised.
→ That CSM will do the work anyway.
They will build the recovery plan, run the extra sessions, chase the champion who stopped replying, and produce something that looks like effort to everyone watching.
A year later the account churns, inevitably.
The review asks what CS did. Your RYG scoring system already has a status for this.
Black covers accounts that were never the right fit.
Hardly any team uses it, because moving an account into Black means somebody has to defend the decision, and defending a decision requires a number.
The List You Cannot Produce
Every CS leader can name the 5 biggest accounts in the book from memory.
Almost none can name the 3 most expensive.
Those are different lists.
The first one shapes your forecast. The second one shapes your capacity, your team’s attrition, and how much of your best coverage reaches the accounts that would actually respond to it.
The second list is the one that decides your year, and it is the one you have never built.
→ Leaders who build it walk into the at-risk review already knowing which accounts to drop.
Here is how to build it.
Below: three steps and the Cost-to-Serve Workbook, a tab for each, yours with a paid subscription along with every workbook in the archive.