What RIAs Should Know Before Evaluating Gainsight or ChurnZero

A client portal showing account balances and statements gets checked a handful of times a year by most clients, often just around tax season or a market downturn. That's not a rich enough usage pattern to build a trustworthy health score from, and login frequency itself is a poor proxy for satisfaction: a nervous client during volatile markets might check daily without being at any real risk of leaving, while a quietly dissatisfied client might not log in at all before moving assets elsewhere.

The stronger signals are relational: whether a scheduled review meeting got postponed or skipped, whether a client's life event (a job change, an inheritance, a divorce) went unaddressed in the advisor's outreach, whether a referral source (an estate attorney or CPA) has gone quiet, and whether recent performance conversations left the client visibly unsatisfied regardless of how markets actually performed. None of this shows up in portal usage.

Before any client data touches a third-party platform, confirm with your compliance function what's permissible under your firm's data-handling policies and any applicable regulatory requirements. Account-level financial detail is a different category of data than the aggregated activity metrics a typical SaaS health score relies on, and that distinction should be settled before evaluating either vendor, not discovered during implementation.

• Does your compliance function have a clear position on client data flowing into a third-party retention tool
• Is your client portal used often enough and by enough of your book to produce a meaningful usage pattern
• How many advisors manage client relationships, and would a shared relational tracker genuinely be too much to maintain by hand
• What's your current process for catching a skipped review meeting or an unaddressed life event, and where does it break today

If compliance hasn't weighed in, that's the first conversation, well before either vendor's demo.

A relational tracker, one row per household, with fields for last review date, next scheduled review, any recent life event and whether it's been addressed, and a note on referral-source engagement, covers most of what predicts attrition at an RIA. This can live in your CRM as custom fields, reviewed by each advisor on their own book monthly. Routing it through Salesforce, where many advisory practices already track households and accounts, keeps it next to the rest of the client record. Gong on review calls can help catch dissatisfaction that a client doesn't state directly but signals through tone or hesitation. See Gainsight vs ChurnZero vs Salesforce for how the platforms fit alongside a CRM more broadly.

Suppose a household's scheduled annual review gets postponed twice due to scheduling conflicts and quietly slips to eighteen months between meetings. During that gap, the client's adult child gets married, a life event that often prompts estate-planning and beneficiary conversations, but the advisor never hears about it because there was no review to surface it. The client, feeling somewhat unattended to, takes a referral from a friend and opens a second relationship with another advisor, testing the waters before eventually consolidating assets there.

A relational tracker flagging any household past its review-frequency target, combined with a habit of asking about life events directly rather than waiting for the client to volunteer them, would have caught this gap well before the client started looking elsewhere. Neither Gainsight nor ChurnZero would have seen any of it, since none of it involves portal usage at all.

The practical fix is a standing review-frequency target per household tier, say more frequent check-ins for larger or more complex households, tracked against actual last-review dates rather than assumed. A household sliding past its target should generate a flag automatically in your CRM's reporting, not depend on an advisor remembering how long it's been.