A DAY IN THIS LIFE
Six accounts were drifting, and Uma knew before they did
Uma · Customer success manager at a supply chain SaaS in Raleigh, North Carolina
One new email sat at the top of Uma's inbox, and it knew her book of business better than she did. Six accounts quietly drifting, each flagged with a likely why and a save play drafted, personal. One account silent for 24 days had a revival email built around the one feature they never used. Uma read it with her first coffee in Raleigh and remembered how she used to find out.
Rewind a year. Eighty four accounts, about $4M in renewals, one spreadsheet of health scores she updated when she had time, which was never. She learned a champion had left when his LinkedIn said "excited to announce," three weeks late. She learned an account was churning when the cancellation email arrived, polite and final. QBR weeks meant building decks until midnight while the rest of the book went unwatched. Her calendar was full of check ins that checked nothing.
Read the whole story →
The switch
Her VP forwarded a link with "look into this?" Uma was skeptical. CS is relationships, and she didn't want a robot emailing her customers. But the trial was a free first 24 hours, so she gave it one mission and nothing else: sweep all 84 accounts, flag usage drops, and tell me why, don't send anything. Setup was three clicks, no code, read access to the CRM and the usage dashboard. She kicked it off at 8:40, before her first check in call, expecting a list of numbers she already had.
The first mission
08:52, the sweep finished: 84 accounts, 6 usage drops, 3 champion exits detected, one she didn't know about because the molted had checked LinkedIn in its browser like a person would. 09:07, each risk annotated with the likely why: logins fell after an admin left, an open ticket sat 11 days, a weekly export job silently stopped. 09:18, save plays drafted per account, each one specific, none of them templates. 09:26, two expansion signals she'd missed: new seats being added at accounts she'd marked stable. 09:31, the report landed, risks named, plays queued, nothing sent.
The report
It read like a handoff note from a colleague who'd done a month of homework in fifty minutes, not a dashboard export. The champion exit stung: at her old pace she'd have discovered it at renewal. She typed "send the top two, hold the rest" and it did. Her ten o'clock turned into a save call she was actually prepared for. She called her mother on the drive home, because for the first time in months the evening belonged to her.
Months later
The health sweep runs itself now, every single day. The silent accounts get revival emails built around unused features, with a call task scheduled if nobody replies in seven days. QBR decks draft themselves six days early, ROI computed from the customer's actual numbers. Renewals are prepped ninety days out with an expansion option attached. Her book grew from 84 accounts to 130, and the VP quietly paused the req for a second CSM. Gross retention went from 88 to 94. Uma spends her days in real conversations, walking in with the homework already done.
The silence that used to become a cancellation now becomes a phone call.
“I used to find out an account was leaving when the cancellation email arrived. Now I know weeks before they do.”
Uma is fictional. The workload is not.
