For customer success
The best account manager has the quietest quarter.
Customer success is measured on the number it can least control: renewal revenue, and on activity it can control but that means nothing. The work in between is where accounts are actually kept.
Get this wrong and it backfires
The trap: counting touches
The number every CRM hands a CS leader for free is activity: calls logged, emails sent, check-ins held. It is easy to count and it rewards exactly the wrong thing. A manager who books a fortnightly call with every account posts a wonderful month, and the account that quietly stopped logging in six weeks ago posts nothing at all, because nobody was talking to it.
Renewal revenue is the other free number, and it is real, but it arrives once a year and is mostly decided by product, price and the customer’s own budget. Ranking people on it ranks them on their book of business. The metrics worth ranking sit between the two: the risk flagged in month three, the expansion that was noticed rather than requested, the renewal that was saved because somebody moved before the customer did.
What a reward looks like
What a customer success board looks like here
Rank the team on renewals saved and expansions together over a quarter, with risks flagged shown beside the score. Weight the save higher than the expansion: an expansion is often the customer’s idea, a save almost never is. Show renewal revenue beside the score without counting it. It is visible, because the business runs on it, but not something an individual is ranked on, because they mostly cannot move it.
Keep it at team level by default. A CS team is usually small enough that everyone already knows who has the difficult accounts, and a personal ranking punishes whoever inherited the hardest book.
Rewarding the work that prevents the rescue
The save that everyone sees is the dramatic one: the executive call, the discount, the weekend. The save that matters more happened three months earlier, when somebody noticed usage dropping and asked why. That work produces no ticket and no revenue line and is invisible on every dashboard a CS team has.
Send it as an event, such as a risk flagged or an account moved out of red, and give it good odds of a card. The cards that fit this team are already in the Services deck: escalating before it burned, managing the expectation before it became a complaint, writing the handover. They were written for consultancies, and they describe customer success exactly.
Peer recognition covers the rest: the colleague who took the awkward call, the one who wrote the playbook everyone now uses. Capped daily, so it stays meaningful.
Getting it in
Most CRMs and CS platforms can send us a message when a field changes: a renewal stage, a health score, a risk flag. Send the account id and the change, the owner’s email so the credit reaches the right person, and the amount if there is one. Send the same change twice and it counts once, so a re-sync is safe.
It is an afternoon for whoever manages the CRM, and the free tier covers ten people indefinitely if you want to see it working first.
Questions
The ones that come up
What should you measure a customer success team on?
Renewals saved, expansions, and risks flagged early, with renewal revenue visible but not ranked, because individuals mostly cannot move it. Activity counts reward meetings, not outcomes.
Won’t ranking on saves reward people who let accounts get into trouble?
Only if saves are the sole metric. Pair them with risks flagged early and health improvements, so the person who prevents the crisis scores as well as the person who resolves it.
Our CS team is four people. Is a leaderboard even appropriate?
Keep it at team level and treat it as a shared scoreboard rather than a ranking. Four people already know who is fastest; what they lack is a record of the quiet work, and cards give them one.
Rank what this team actually does.
Free for your first 50 people. No card, no sales call.