About

A health score should survive contact with the evidence.

Churnity started from a specific, recurring problem in enterprise customer success: accounts that scored healthy right up until they did not renew.

Last updated 17 November 2026

The problem

Churnity’s founder led enterprise customer success for UiPath across ANZ, where accounts under management reached 140%+ net revenue retention and 200%+ feature adoption. That work also surfaced a pattern worth building software around: a single health score can look reassuring while the underlying signals, usage, support tickets, NPS, billing, already disagree with it. By the time the score caught up, the renewal conversation was already harder than it needed to be.

Why cross-checking, not scoring

Most customer success platforms compute a single health number. Churnity’s position is that the number is not the useful part, the disagreement between signals is. A customer whose usage is falling while their NPS stays high is not “healthy”; they are a conversation waiting to happen. Churnity is built to find and surface exactly that kind of conflict, with the evidence attached, rather than averaging it away.

Where Churnity is today

Churnity is in private beta. The product connects to the systems that already hold your customer data, read-only, and checks them against each other for the kinds of conflicts described on the product page. See how we handle your data, or get in touch to join the waitlist. Follow along on LinkedIn.