Full Health-Score Coverage Across Every Account: Lessons From Hyperspell and Union AI

Most customer success teams have a health score. Far fewer have a health score that covers every account. The strategic customers get watched closely, the accounts with loud champions get attention, and everyone else sits in a grey zone where health is a guess based on the last conversation someone remembers.

That grey zone is where surprises come from. A pilot that never really started, a live customer whose errors keep climbing, a major customer whose internal priorities have shifted: none of these show up if the account is not being scored or watched in the first place.

This guide explains what full health-score coverage means, why partial coverage is so common and how to close the gap. It uses two Quivly customer stories as examples: Hyperspell, which reports 100% account health coverage, and Union AI, which uses market signals to stay ahead of changes at its customers.

What Full Health-Score Coverage Means

Full coverage means every account in your book has a current, explainable health assessment, not just the ones someone has time to look at. In practice it has three parts:

• Every account is scored. Pilots, newly onboarded customers, long-tail accounts and strategic customers all get the same baseline treatment.
• Every score uses more than one signal. Product usage, conversations, support and market changes are read together rather than one at a time.
• Every score leads somewhere. When health moves, the right person hears about it and knows what to do next.

Coverage is different from accuracy. A highly tuned score that only covers your top 20 accounts still leaves most of the book unmonitored. A broad score that every account receives, with room to tune over time, catches more of the problems that matter.

Why Health Coverage Usually Stops Short

Partial coverage is rarely a decision. It happens because building and maintaining a health score is manual work, and manual work gets rationed. Common reasons include:

1. Data lives in too many places. Usage sits in a warehouse, conversations in email and chat, commitments in meeting notes and project status in a separate tracker.
2. Pilots fall outside the model. Many scores are built for paying customers, so pilots and early-stage accounts are not scored at all.
3. External changes are invisible. A score built only on internal data misses reorganisations, strategy shifts and hiring changes at the customer.
4. Updating the score takes time. If health is refreshed by hand before a review, it is out of date most of the time.

Hyperspell's story describes the core version of this problem well. Customer conversations, project progress and product usage all inform the next step, and bringing that information together takes time. The team needed a consistent way to track commitments, identify issues and prioritise support across accounts.

Lesson From Hyperspell: Cover Pilots and Live Accounts the Same Way

Hyperspell builds Company Brain, a self-updating company wiki powered by a context graph. Its post-sales team manages both pilots and live customers, and each account needs preparation, follow-through and a clear view of adoption.

With Quivly, Hyperspell can assess account health alongside product usage and customer conversations, across pilots and live accounts. That is what its 100% account health coverage refers to. A few details from the story are worth borrowing:

• Track the usage signals that reflect real adoption. For live customers, Quivly tracks user invitations, query volume and errors.
• Use health to set priority. Health metrics help the team identify which accounts are encountering the most issues and need attention first.
• Treat onboarding as part of health. Projects track each onboarding journey, keeping responsibilities and progress visible, so a pilot that stalls is visible early.

The point is not that every account gets the same amount of attention. It is that every account gets assessed, so attention goes where it is needed rather than where it is habitual.

Lesson From Union AI: Look Beyond Your Own Data

Union AI is the AI development infrastructure company and the largest contributor to the open-source workflow orchestration platform Flyte. Before Quivly, its Customer Solutions team was at risk of being caught off guard by customer priority shifts that could affect renewals or expansions, and the basic tools it used to track online mentions required maintenance and overhead.

Union AI deployed Quivly as a proactive signal intelligence engine that tracks customer market signals and relevant job postings to deliver daily, actionable insights. In its first 4 weeks, Union AI reports:

• 163 new insights discovered across customers and tracked keywords.
• 52 signals (32%) identified as highly relevant to Union AI.
• 34 distinct companies, including 25 new logos, uncovered that were hiring for roles mentioning Flyte open-source software.

In one case, Quivly surfaced news about a major customer's internal priority shift, which allowed the CS team to be prepared. That kind of change never appears in product usage data until it is too late. External signals are what turn a usage score into a full picture. Our guide to market signals in customer success covers which ones to watch.

Union AI is also working with Quivly on a deterministic, data-driven health score linked to internal usage metrics such as compute and node hours, designed to give leadership a bird's-eye view for identifying expansion opportunities.

Build a Score That Combines Every Signal

Put the two lessons together and a pattern appears: full coverage needs internal signals and external signals in the same score. Quivly's Health Score turns CRM, product, support, billing and market signals into a single weighted score per account, recomputed every minute and explained in plain English. It weights five categories: revenue, support, market signals, product usage and engagement.

When you design your own model, keep these principles in mind:

• Weight categories for your business. A usage-heavy product and a services-heavy product should not score health the same way.
• Choose metrics carefully. Pick the specific usage metrics that reflect value, such as queries, executions or compute hours, rather than logins alone.
• Explain every score. A number without a reason gets ignored. Quivly generates risk and growth signals as natural-language narratives, with each claim cited back to its data source.
• Test before you switch. Quivly lets teams test new weights against historical data, and every config change is versioned.

For a step-by-step approach to weighting, see our guide to building a weighted customer health score.

Turn Coverage Into Daily Action

Coverage only pays off if it changes what the team does each day. Both stories show the same habit: the signals come to the team, rather than the team going to look for them.

At Hyperspell, automations bring proactive alerts into a dedicated CS Slack channel, helping the team triage issues and assign owners. At Union AI, Head of Customer Solutions Engineering Shalabh Chaudhri says: "We look at Quivly notifications every day. Quivly has become a core part of our customer intelligence stack."

To build the same rhythm:

1. Route alerts to where the team already works. A shared channel makes ownership visible and stops alerts from getting lost in one inbox.
2. Assign an owner to every alert. Triage is only complete when someone has the next step.
3. Bring health into call prep. Hyperspell uses Quivly to prepare account context before customer calls and capture takeaways, action items and the next agenda afterward.
4. Review by priority, not by recency. Start with the accounts that need attention first, as health metrics show.

What Full Coverage Gives Back to the Team

The obvious benefit of full coverage is fewer surprises. The less obvious one is time. When account context is gathered automatically, the team stops spending hours assembling it by hand.

Hyperspell reports 8+ hours saved across post-sales each week and 85% less time spent on call prep and follow-ups. The team uses that time to guide customers through onboarding, support adoption and keep engagements moving. As Idit Oryon, Head of GTM at Hyperspell, puts it: "We spend less time pulling context together and more time getting customers to value."

Want every account in your book scored, explained and routed to the right owner? See how Quivly's Health Score gives your team full coverage across pilots, live customers and the long tail.