Start with a baseline
You can’t measure improvement without a starting point. The most common mistake is pulling data after launch with nothing to compare it to. Before you switch Usivity on for any account, spend 30 minutes on four numbers.
| Baseline | How to get it |
|---|---|
| Support tickets about how the product looks or works | Pull the last 90 days. Tag or filter for tickets about display, layout, formatting, column changes or label edits. This is your deflection baseline. |
| Feature requests about display or presentation | Count the open backlog items an engineer would call cosmetic or presentational. This is your opportunity. |
| NPS in the accounts that go first | Pull the latest NPS for the accounts where you launch first. You need it now: without a baseline, a 90-day comparison means nothing. |
| CSM hours spent on these requests | Estimate the weekly hours your team spends logging, relaying and following up on requests that won’t make this sprint. Rough is fine; you need a direction. |
These numbers shape your story at 30 days, 90 days and every QBR after. Without them you have usage data, but no impact data.
Four primary metrics
Not every number moves for every account. Focus on the ones with the clearest before-and-after for your situation.
Ticket deflection rate
The drop in support tickets about how the product looks or works, against your pre-launch baseline. Measure monthly.
How: compare tickets tagged UI, layout or display with the same window before launch. Count only requests to change how the product looks or behaves, not broken functionality.
Feature request deflection
Fewer new requests of this kind per sprint or month. Fewer new submissions means users are solving problems themselves instead of queuing them.
How: compare new requests of this kind in the sprint before launch with each sprint after. Count new submissions, not total backlog size.
NPS in active accounts
NPS in accounts that actively use Usivity, 90 days after launch against the baseline. Usivity alone doesn’t move NPS, but frustration with how the product works holds it down, and removing it shows up downstream.
How: split NPS by accounts with and without Usivity use. The comparison group gives you a signal that’s hard to get otherwise.
Engagement depth
The share of users who have made at least one personalization. It shows whether Usivity is how a team works, or one power user’s curiosity.
How: pull it from Usivity’s reports monthly. In a healthy account it grows steadily as colleagues show each other.
Secondary signals
The primary metrics are the proof. These signals are the narrative, and leadership presentations and QBRs need both.
CSM time reclaimed per week
Re-estimate the hours your team spends on these requests after launch and compare with the baseline. Time freed is real capacity.
At-risk account movement
Count the accounts with open complaints that moved from red or yellow to green after Usivity was switched on. This is your strongest retention story.
Time to resolve a complaint
Before Usivity: weeks to months. After: the same session. Write up two or three real examples; stories make the data land.
Renewals where Usivity came up
Ask CSMs to tag renewals where Usivity was a factor, for better or worse. Over time this builds the case for expansion.
Reporting cadence
Reported too early, data has no context; too late, it has lost its moment. This cadence follows the natural rhythm of a B2B software evaluation.
- 1
First usage report
Share early adoption numbers with leadership and the accounts taking part. Don’t wait for the data to be perfect.
- 2
Before and after
Ticket volume, feature request count, engagement depth. This is your proof-of-concept moment.
- 3
NPS and account health
NPS for the accounts taking part, at-risk movement, CSM time. This is the data that opens expansion conversations.
- 4
Renewals and expansion
Which accounts using Usivity renewed cleanly? Which expanded? This is the board-level story.
Bringing these numbers to a customer? See introducing Usivity in a QBR.