THE RENEWAL — Client Retention OS Brain
THE RENEWAL — Client Retention OS Brain
For keeping the accounts you already won. One orchestrator plus ten specialists that score churn risk against observable signals, rebuild the value story in the client's own numbers, and get you multi-threaded before the sponsor leaves.
Most retention work starts about six weeks too late, when someone senses the mood has changed. By then the client has already run a comparison. This ships a scoring script that takes fourteen observable signals — sponsor tenure, meeting cadence drift, invoice query rate, breadth of contacts, months since the last value conversation — and returns a number plus the specific signal dragging it down. A number can be argued with in a pipeline review. A feeling cannot. The rest of the brain works on whatever the score exposes, which is usually that you are single-threaded into one person who is about to be promoted.
renewal_risk.py
Takes 14 account signals, returns a 0–100 churn score plus the single worst-contributing signal and its weight. Same inputs, same answer, every time — so two people can disagree about the account and still agree about the number. Every OS Brain in this drop carries its own executable component, so the judgement calls stay with you and the arithmetic stops being a matter of opinion. Runs anywhere Python runs, and the specialists still work on their own if you never open it.
Say it in plain words — it works out the rest
Inside · orchestrator + 10 specialists
Where it refuses to skip ahead
- No plan without a score — "I think we're fine" is how accounts get lost in the quarter nobody was watching.
- No value story without a baseline — if you cannot say what their number was before you, you cannot claim the delta.
- No discount before a diagnosis — price is rarely the actual problem, and dropping it first removes your only lever.
- No account left single-threaded — one sponsor is one resignation away from a competitive review.