I’ve been working in RevOps for 10 years, and one pattern keeps showing up:
accounts don’t churn because of usage issues first, they churn because the champion drifts away.
Champion drift is silent.
No ticket. No alert. No one notices until renewal dies.
I wanted a small, code-first way to detect this earlier, so I built a tiny FastAPI service:
- You send a list of stakeholders, their roles, activity dates, and renewal date
- The API returns a risk score (0 to 1), a risk level, and the reasons
- It flags things like:
* Champion hasn't been seen in 60 to 90 days
* Champion left the company
* Renewal is approaching without an active internal owner
This is not a product. Just a minimal piece of logic that I think should exist in the world.
If you have ideas to make the scoring smarter or want to extend it, I’d love feedback.
bhaviav100•2mo ago
Champion drift is silent. No ticket. No alert. No one notices until renewal dies.
I wanted a small, code-first way to detect this earlier, so I built a tiny FastAPI service:
- You send a list of stakeholders, their roles, activity dates, and renewal date - The API returns a risk score (0 to 1), a risk level, and the reasons - It flags things like: * Champion hasn't been seen in 60 to 90 days * Champion left the company * Renewal is approaching without an active internal owner
Repository: https://github.com/malukutty/champion-drift-detector-api Interactive docs at /docs once you run it locally.
This is not a product. Just a minimal piece of logic that I think should exist in the world. If you have ideas to make the scoring smarter or want to extend it, I’d love feedback.