Skip to content

Customer Success

How to introduce Usivity in a QBR

A script and slide framework for CSMs: show the value, bring the right numbers, and use Usivity as a retention and expansion lever at renewal.

Customer Success guide · 6 min read

Why the QBR matters

The QBR is your best chance to make Usivity visible. Most customers use it quietly: they personalize their views, send fewer tickets and stop asking for changes, without ever connecting that to what you gave them. The QBR closes that loop.

Done well, it turns a feature into a business outcome. You get a proof point for renewal, a story for expansion, and evidence that your team delivers value beyond the core product.

What you can show

  • Support ticket volume has changed since Usivity launched. Show the trend.
  • Feature requests have slowed. Show the backlog isn’t growing the same way.
  • Users are solving their own problems. Show what that looks like in practice.
  • Expansion is possible. Frame Usivity as a reason to roll out to more users.

Pre-meeting checklist

Five things to do before the QBR. None takes more than 15 minutes, and all of them matter.

01

Pull the account’s Usivity numbers

Personalizations created, what people used, how many users are active. This is your proof the product is working, even if the customer hasn’t noticed yet.

02

Pull your pre-launch support ticket baseline

You need a before and after. If you don’t have the pre-launch number, use the same window from last year.

03

Find one or two personalizations this account already made

Showing customers their own work beats a generic demo. It proves the tool is already part of how they work.

04

Prepare a 90-second live demo tied to their work

Pick something connected to a complaint they logged. The more specific the better; name the real request if you can.

05

Know the renewal date and health score before you walk in

Usivity is a retention and expansion lever. Know what you’re protecting and what you want to grow before the conversation starts.

Three ways to open the Usivity segment

Pick the frame that fits the account right now. The words matter less than the intent: you’re connecting something the product does to an outcome they care about.

The results frame

“I want to spend ten minutes on something where we’ve seen real movement. Since we turned on Usivity for your team, I’ve been watching your support ticket volume, and I want to walk you through what we’re seeing.”

Use it when: You have strong numbers and want to lead with the win.

The new capability frame

“I want to show you something your team has access to that I don’t think you’ve had a chance to explore yet. It handles the kind of request that tends to pile up in our backlog conversations.”

Use it when: Adoption has been low and you want to introduce it fresh.

The specific problem frame

“Remember the column reordering request your team sent six months ago? I want to show you what happened with it: not through engineering, but through something built for exactly this kind of problem.”

Use it when: There’s a specific logged complaint you can name.

The data slide

Four numbers make the case. Keep the slide simple: one before-and-after comparison is worth more than four percentages without context. If you have the ticket deflection number, lead with it.

NumberWhat it shows
Support tickets about how the product looks or works: before vs. afterYour strongest number. A visible drop is direct proof of deflection. Put it on a slide.
Personalizations createdEverything the account’s users have saved. Shows adoption and active use.
Feature requests this quarterCompare with the same period before Usivity. Fewer requests means a lighter backlog.
Users with at least one personalizationBreadth. Shows it isn’t one power user but a change in how the team works.

The live demo

Show something they recognize, not something generic.

  1. 1

    Start with their data

    Open their actual account in the product and show their own screens. Not a sandbox: their live environment.

  2. 2

    Name a real request

    Pull up a specific complaint or ticket they logged. Name it, and show that what they asked for is solvable right now, without a ticket.

  3. 3

    Let them try it

    Hand the screen to someone in the room. The first thing a user does on their own is more memorable than anything you show them.

Always end with a specific ask

A QBR with great numbers and no ask is a missed opportunity. Usivity gives you four natural next steps.

Expand to more teams or business units

If Usivity is live for one team, use the QBR numbers to make the case for more. The numbers do the selling.

Ask for a quote or a case study

A QBR where the customer is nodding at your data is the right moment. You have the numbers; they have the story.

Book a session with their power users

Ask for 30 minutes with the two or three heaviest Usivity users. These sessions surface insight and stories worth sharing.

Make Usivity part of the renewal

If Usivity started with limited access or as an add-on, use the QBR to fold it into the core renewal at a defined scope.

Your customers get a product that fits. Your roadmap stays yours.

In ten minutes we’ll show you what your customers can change on their own, and what your team never has to build.

Book a 10-minute demo

We reply within one business day.