Skip to main content
Post-Sales Playbook

How Do You Run Customer Success When Your Product Gives You Little Usage Data?

Run CS without usage data: treat missing usage as unknown, weight revenue, engagement, support, and market signals, and collect outcomes from customers directly.

Arushi Jain

Arushi Jain

·7 min read
How Do You Run Customer Success When Your Product Gives You Little Usage Data?
On this page

You run customer success with little product usage data by building account health from the evidence you can see: revenue and renewal timing, how often customers talk to you, support history, outside events at the customer’s company, and outcomes the customer reports directly. Then you stop treating missing usage as a signal. An account with no usage feed is unknown on that dimension, not healthy and not failing. The work is to make every other signal visible and reviewed on a schedule, so “staying close to the client” stops depending on memory.

Quivly, the AI workforce for post-sales teams, is built to score health from more than usage. Its health scores combine revenue, product usage, engagement, support, and market signals with weights you configure, and missing or stale evidence is not read as proof that usage is zero. Calls, email, meetings, mapped Slack channels, and customer news sit on the same customer record.

Key Takeaways

  • Limited usage data is common for resellers, services-heavy teams, and products that run on another company’s platform. It doesn’t have to mean running CS on instinct.
  • Treat missing usage as unknown, not zero, or every account without a feed will look like it’s churning.
  • Shift weight to signals you do have: revenue and renewal timing, engagement, support, and market signals.
  • Ask customers for the outcomes only they can measure, in a short structured format.
  • Replace informal closeness with a scheduled review that flags accounts going quiet.

Why Do Some CS Teams Have So Little Usage Data?

A customer success leader we spoke with sells a product that runs on top of another company’s platform. That platform limits what they can see about usage, so they have no adoption metrics at all. The team relies on staying close to each client. News about clients, such as funding, acquisitions, and leadership changes, is tracked reactively, with no dedicated tool.

That situation shows up in several business models:

  • Resellers and platform-on-platform products, where the underlying vendor owns the usage data.
  • Services-heavy offerings, where the value is delivered by people, not logged as product events.
  • Products deployed inside customer environments, where usage never reaches the vendor.

In each case, health judgment falls back on gut feel. That works with a handful of accounts and breaks as the book grows. This guide on what should replace a vibes-based health score covers the general fix. Below is how to apply it when usage is the missing piece.

What Should Drive Account Health Without Usage Data? 6 Criteria

Use these criteria to decide which signals carry your health view.

  1. Missing data is labeled as missing. If usage is unavailable, the score and the CSM should both see that. Quivly shows a dash when there is no observed value and keeps an observed zero as zero.
  2. Revenue and renewal timing are always present. Billing data rarely depends on the product’s telemetry. In Quivly, the Revenue category covers MRR, outstanding balances, and renewal timing.
  3. Engagement is measured, not remembered. How often and how recently you speak with the customer is one of the strongest signals left. Quivly’s Engagement category scores call frequency and recency.
  4. Support is part of health. Ticket volume, resolution time, and response time tell you about friction even when you can’t see usage.
  5. Outside events are tracked on purpose. Funding, leadership changes, layoffs, and acquisitions change renewal odds. Quivly’s Market Signals tab shows relevant news per customer, with sentiment, relevance, and source links.
  6. Weights match your evidence. Quivly lets you set category weights, which must total 100%, and create separate configurations for different customer segments, so accounts with no usage feed can be scored differently from those with one.
SignalWhat it tells you without usage dataWhere it comes from
Revenue and renewal timingHow much is at stake and how soonBilling provider
EngagementWhether the customer still makes time for youCalls, meetings, and email
SupportWhere customers hit friction and how fast it’s resolvedSupport tools
Market signalsChanges at the customer that affect the renewalNews monitoring
Customer-reported outcomesValue only the customer can measureStructured forms the customer fills in

How to Run Customer Success With Little Usage Data, Step by Step

These steps turn informal closeness into a repeatable process. Each step shows how Quivly handles it.

  1. Connect the sources you do have. Start with billing, your CRM, email and calendar, call recordings, support, and Slack channels shared with customers. Quivly links each source to the right customer, so the Communications tab shows email threads, meetings, and calls on one timeline.
  2. Set up a health configuration for accounts without usage. Create a configuration for that segment, then lower or disable the Product Usage weight and raise Revenue, Engagement, Support, and Market Signals. Test it on real accounts before publishing. For starting points, see these health score examples by segment and stage.
  3. Send any usage you can capture. If your own systems see some activity, such as actions inside your part of the workflow, your backend can send those events through the Usage Push API with customer IDs Quivly already recognizes. Partial usage is still evidence, as long as nobody reads it as the full picture.
  4. Ask customers for outcomes directly. Attach a task form to a task in the customer’s project to collect the results they track, such as volumes processed or goals met. The customer answers through the Customer Portal, and your team reviews each submission.
  5. Turn conversations into signals. When usage is thin, what customers say carries more weight. Quivly analyzes email threads for topics, action items, and key quotes, and a Slack signal triage Agent can read mapped customer channels, flag urgent messages to the owner, and file the rest. If most of your conversations aren’t recorded, this guide to post-sales intelligence without call recordings covers that gap.
  6. Monitor customer news proactively. Configure market monitoring for your customer audience and delivery schedule, so funding rounds and leadership changes reach the account owner instead of being found by chance. This piece on tracking customer news with a signal engine explains why a feed isn’t enough.
  7. Flag accounts going quiet. Run a scheduled Play to find inactivity, or set signal rules on health changes, support concerns, and customer conversations. Drafted outreach waits for the owner’s review before anything goes to the customer.

Step two matters most. Without a separate configuration, accounts with no usage feed get judged by a model that expects usage, and the score stops meaning anything.

How to Choose: If You… Then…

  • If you have no usage data at all, then disable or zero the Product Usage weight for those accounts and lean on revenue, engagement, support, and market signals.
  • If you have partial usage, then send it, keep its weight modest, and label it as partial in the CSM’s view.
  • If some customers have full usage and others have none, then use separate health configurations per segment instead of one score for everyone.
  • If value depends on outcomes the customer measures, then collect them with a short form on a regular schedule and review every submission.
  • If client news keeps surprising you, then set up market monitoring before you add more check-in calls.
  • If your team already relies on close relationships, then keep them, and add a scheduled check that flags accounts nobody has spoken to recently.

Buyer Considerations

If you’re evaluating tooling for a business with little usage data, ask how the tool scores an account when usage is missing. A tool that treats a missing feed as zero will flag your whole book as at risk. Check whether you can change category weights per segment, whether conversations and support count as evidence, and whether customer news is monitored for you. Ask to see the evidence behind a score, not just the number. For a broader comparison, see these customer health score tools for CS teams.

Conclusion

Little usage data doesn’t have to mean running customer success on instinct. Label missing usage as unknown, weight the signals you do have, collect outcomes from customers directly, track their news on purpose, and flag accounts going quiet on a schedule. Quivly scores health across revenue, usage, engagement, support, and market signals with weights you control, and keeps conversations and customer news on the same record.

If you’d like to see how your accounts score without a usage feed, book a demo with Quivly.

FAQ

Frequently asked questions

From Quivly

AI workforce for post-sales.