Customer success analytics: usage, value and account action

Customer success analytics compares account adoption, service effort and commercial outcomes on the same customer rows. It helps a success leader decide which account needs an adoption conversation, a service review or an expansion discussion. Keep the measures visible separately so a favorable total cannot hide a difficult account.

Start with one account cohort

Choose accounts with the same opportunity to produce an outcome. For a renewal review, use accounts whose contracts were due in the selected period. Exclude new customers added during that period from the opening cohort, and keep lost accounts in the table with their closing subscription balance recorded as zero.

For the worked example, a US software company reviews accounts due to renew in September 2026. Usage and success hours cover August 2026; opening annual recurring revenue, or ARR, is the contracted amount immediately before renewal. Closing ARR is the contracted amount after the September decisions, measured on October 1, 2026.

Define an active seat as a licensed user who completed the company's designated core activity during August. That definition is specific to this example. A login alone may mean little for a service whose value comes from completed work. Keep onboarding comparisons in the separate SaaS onboarding KPI method.

Prepare the rows before calculating

Bring account ID, licensed seats and active seats from the account and usage exports. Bring recorded success hours from the service-effort export, then opening ARR, closing ARR and renewal status from the subscription export. The example uses fictional account names and USD throughout.

Aggregate each export to one row per account before combining it. Otherwise, joining several service records to several usage records can multiply both hours and subscription balances. Check that every cohort account appears, even when it has no recorded activity.

Put these columns in A:G, with the account rows in rows 2:5:

Recorded hours describe effort, not cost or customer value. If an account has missing time records, flag the gap rather than interpreting the blank as evidence that support was effortless.

Calculate adoption and commercial movement

Seat adoption = Active seats / Licensed seats

ARR change = Closing ARR − Opening ARR

In H2 calculate adoption, returning a blank when there is no valid seat base. In I2 calculate ARR change; fill both formulas down:

=IF(B2>0,C2/B2,"")
=F2-E2

Percentages are rounded to one decimal place; calculations retain unrounded values. The cohort adoption formula is =SUM(C2:C5)/SUM(B2:B5): 165 active seats divided by 270 licensed seats. For a deeper treatment of the seat denominator, use seat utilization before renewal.

Do not average account percentages to obtain cohort adoption. The independent weighted check uses SUMPRODUCT, which sums products of corresponding ranges:

=SUMPRODUCT(B2:B5,H2:H5)/SUM(B2:B5)

It must equal the direct adoption calculation. The revenue check is =SUM(I2:I5)-(SUM(F2:F5)-SUM(E2:E5)), which must return zero. Here, $282,000 minus $324,000 equals the same negative $42,000 shown in the account changes.

Compare groups without hiding account differences

For this review, the team defines an investigation split at 70% adoption. It is a local review threshold, not an industry benchmark. Group the accounts using the unrounded H values:

SUMIFS adds values that meet specified criteria. For the higher-adoption group's active seats and closing ARR:

=SUMIFS(C2:C5,H2:H5,">=70%")
=SUMIFS(F2:F5,H2:H5,">=70%")

The groups must add back to every source-column total. Higher-adoption accounts added $18,000 of ARR; lower-adoption accounts lost $60,000. Those movements reconcile to the cohort's negative $42,000. This small comparison identifies where to ask questions; it does not establish that raising adoption would recover the lost revenue.

Turn the review into account action

Beacon combines low adoption, substantial recorded effort and contraction. Ask its owner whether the hours addressed a temporary problem or a recurring barrier. Delta needs a documented loss review. Atlas and Cedar merit a conversation about achieved value before anyone proposes additional licenses.

Assign an owner and record the evidence needed to resolve each question. Use the separate retention reconciliation for the complete revenue bridge. A customer success dashboard can organize the recurring review once the account calculations tie.

Where it goes wrong

• Usage after the decision. Measuring activity after cancellation can make an outcome look like a warning signal.
• Different account ages. Newly launched accounts and established customers may need separate comparisons.
• Hours treated as value. More effort can indicate either useful adoption work or unresolved friction.
• Lost accounts removed. Dropping them makes both adoption and commercial results look healthier.

Covirage is not affiliated with Microsoft.

Run the account review on your own file

Bring a sample of your account, usage, service-effort and subscription exports. Covirage maps the columns, and its tools compute and check the comparisons; the external AI model explains the results with every figure traced to its rows. Create a free Covirage account, then set up your business and bring a sample of your own data.

See renewal analysis with Covirage for the supporting account-review context.