---
title: "Buyer Loves Us but Users Do Not? Fix the Adoption Gap"
description: "Buyer loves us but users do not is a political split, not an adoption problem: two ratios expose it, and four steps close it once you have found the gap."
topic: "Retention & Churn"
author: "Raj Bheda, Co-founder, GainTrace"
audience: "Customer Success Manager, Head of Customer Success"
published: 2026-09-18
modified: 2026-09-18
source: https://gaintrace.com/explore/retention/buyer-loves-us-but-users-do-not
---

# What Do I Do When the Buyer Loves Us but Users Do Not?

*When the contract renews but the login numbers do not move*

**Short answer:** Buyer loves us but users do not means the renewal decision-maker and the daily user population have split into two different audiences with two different opinions, and only one of them signs the contract. Track adoption breadth across every licensed team, not champion sentiment alone, because a renewal built on one enthusiastic sponsor and a disengaged user base survives one cycle and rarely two.

**Key takeaways**

- Buyer loves us but users do not is a political split, not a single bad relationship: the buyer's view and the daily user population's experience are different, and only one shows up in a QBR.
- The second buyer, the end-user population that never signed the contract, does not vote on this year's renewal but decides whether the champion has anything to point to next year.
- Adoption breadth, the share of licensed teams with at least one active user, catches a risk that usage concentration alone hides: one healthy department can carry an account's average while five others sit dormant.
- Reach a dormant team through a champion introduction, not a cold outreach; a specific, champion-vouched request gets a reply where a general one gets ignored.
- An account survives a champion's departure only if adoption breadth was already wide before the champion left; fixing it after the departure is usually too late.

Buyer loves us but users do not is the gap between what a QBR deck shows and what the login data says, and it usually surfaces at the worst possible moment: the champion signs off enthusiastically, and three months later half the licensed seats have not opened the product in weeks. The relationship looks fine because the person you talk to is a genuine fan. The renewal is not fine, because the renewal depends on people you have never spoken to.
This page is for the CSM or Head of CS who has noticed the split and needs a way to act on it before it becomes a churn conversation. It covers who the second buyer is, the two ratios that expose the gap a satisfaction score hides, and the four steps that close it once you have found where the account is thin.

## What does it mean when buyer loves us but users do not?

Buyer loves us but users do not describes a specific split: the person who signed the contract, or renews it, reports satisfaction while the people who open the product every day barely open it at all. The two groups are not disagreeing about the same experience. They are having two different experiences, and only one of them is visible in the data a CSM normally watches.

> "One of the key challenges that any team faces is ensuring engagement with both daily users (Campions) and key decision-makers/buyers (Executive Sponsors)."
>
> — Director of Customer Success, small-business SaaS, public G2 review

The split is structural, not a personality problem with one champion. A buyer evaluates the product once, during a sales cycle built to sell them, and then experiences it mainly through dashboards, QBR decks and conversations with a CSM who is, correctly, putting the best version of the account in front of them. The daily user experiences none of that. They experience the product at its most ordinary: the tenth login of the week, the workflow that still takes four clicks too many.

> "When a vendor says they talk to customers, what they usually mean is they talk to the admin, the power user, and whoever shows up to the QBR. That is a handful of people per account, and they are a specific and unrepresentative slice: they chose the tool, they are invested in it working, and they have already learned their way around it."
>
> — r/CustomerSuccess, 2026

The pattern repeats up the org chart as well as down at the desk level. A sponsor who sends a delegate to the QBR and a user who has stopped logging in are the same signal measured at two different altitudes.

> "The exec sponsor shows up for 15 minutes and then leaves, and somehow we all agree things are going great even when the product adoption data says otherwise."
>
> — r/CustomerSuccess, 2026

| Touchpoint | What the buyer sees | What the daily user sees |
| --- | --- | --- |
| QBR deck | Curated usage charts and success metrics | Not present; rarely knows the meeting happened |
| CSM check-in | A relationship-focused call, positive by design | No direct contact most quarters |
| The product itself | Rarely opens it after the sales cycle ends | Opens it daily, feels every rough edge |

## Who is the second buyer in a software renewal?

> **The second buyer:** The second buyer is the end-user population that never signed the contract and cannot cancel it, but whose disengagement is what eventually changes the champion's mind, or hands the champion's successor a reason to switch. A renewal defended only to the first buyer is defended against half the risk.

The second buyer explains why an account can look safe for several renewals and then leave abruptly when nothing about the champion relationship seems to have changed. Usage decay in the second buyer builds quietly for a year or more before it reaches the first buyer as a complaint, a support escalation, or a straight refusal to renew at the next price point.

> "Champions are reachable and end users are not. Champions answer emails, join calls, and arrive with opinions ready."
>
> — r/CustomerSuccess, 2026

> "Is there a case for not bothering? If the champion is the buyer and signs the renewal, maybe their view is the one that actually matters commercially."
>
> — r/CustomerSuccess, 2026

The champion's view is what signs this year's renewal. It is not what signs next year's, once the champion changes role, leaves, or gets asked by their own boss whether the tool is worth the line item. The second buyer does not vote on this year's contract. It votes on whether the champion has anything to point to when someone eventually asks.

## What two ratios measure the gap between buyer and user?

Two ratios expose the gap a QBR deck usually hides. Usage concentration shows how much of the licensed seat count is active. Adoption breadth shows how many of the licensed teams or departments have anyone active at all, since a healthy usage concentration number can still hide a single department carrying the whole account.

Core feature adoption sits at 24.3% for product-led SaaS and 26.7% for sales-led SaaS, in Userpilot's 2024 analysis of its own product-analytics data across 547 SaaS companies; the report does not state whether the figure is a mean or a median. Whichever it is, roughly three-quarters of licensed users are not touching the product's core workflow at a typical company, which is the raw material the buyer-user gap is built from.

**Usage concentration**

```
Usage concentration = Weekly active users ÷ Licensed seats × 100
```

Where:
- Weekly active users: distinct logins in the trailing 7 days, not a monthly figure that hides weekly drop-off
- What good looks like: a concentration falling while the champion's renewal sentiment stays flat or positive is the earliest version of this gap; do not wait for the number itself to look bad

**Adoption breadth**

```
Adoption breadth = Licensed teams with at least one active user ÷ Licensed teams on the contract × 100
```

Where:
- Active user: logged in and took at least one action in the trailing 30 days
- What good looks like: breadth above 70% on a multi-department contract; below that, the account is one department's tool wearing a company-wide contract

> **Worked example:** A 200-seat account has 90 weekly active users, a 45% usage concentration that looks merely average. Broken down by department, 85 of those 90 sit in one team of 95 licensed seats, and the other five licensed teams, 105 seats between them, have four active users total. Usage concentration alone reads as a mediocre account. Adoption breadth reads as one healthy department and five that never started. The renewal conversation with the champion, who sits in the healthy department, will not surface the other five unless someone asks the breadth question directly. These figures are illustrative; run both ratios on your own accounts.

| Shape | Usage concentration | Adoption breadth | Renewal risk |
| --- | --- | --- | --- |
| Broad and steady | 50% | 90% | Low: the second buyer is engaged across the account |
| Deep in one team | 50% | 20% | High: one champion's team masks four dormant ones |
| Thin everywhere | 50% | 100% | Medium: nobody is disengaged, but nobody is deep either |

## What four steps close the gap once I find it?

Closing the gap starts with the department the data shows as dormant, not the one the champion already loves. A second training session for the team that already uses the product daily wastes an hour a dormant team badly needs instead. Route the fix to where the breadth number is lowest.

1. **Name the dormant team to the champion directly.** Bring the breadth number, not a vague concern. Most champions have not seen a department-level breakdown and will treat it as new information, not criticism.
2. **Ask the champion to introduce one contact in the dormant team.** A CSM reaching a dormant department cold gets ignored. A champion-introduced contact gets fifteen minutes.
3. **Run a narrow re-onboarding, not a repeat of the original training.** The dormant team's blocker is rarely the same as what the original rollout covered. Ask what stopped them before building a session.
4. **Reset the breadth number at the next QBR, not the usage total.** Report the department count that is now active, not a raw login number. It is the metric that predicts the risk this page is about.

**Before you call the account healthy**
- [ ] Usage concentration is calculated on weekly, not monthly, activity.
- [ ] Adoption breadth is calculated per licensed team or department, not per seat.
- [ ] At least one contact outside the champion's own team has been reached this renewal cycle.
- [ ] The QBR deck shows the department breakdown, not only the account-level total.
- [ ] A dormant team has a named next action attached to it, not a flag sitting alone on a dashboard.

## What happens to the account when the champion leaves?

An account with a wide adoption breadth survives a champion's departure; an account with a narrow one does not. The successor inherits a tool with proof it works across the team, or a tool that only the previous champion seemed to like, and the second case is a coin flip on the next renewal even if the outgoing champion leaves on good terms.

> "Champion has left. Team of 15 not using software."
>
> — r/CustomerSuccess, 2025

> "The execs we wanted in the room often sent a delegate. Felt like we were the only ones who thought the meeting mattered."
>
> — r/CustomerSuccess, 2026

Both quotes describe the same failure from opposite ends. A champion going quiet is the first buyer disengaging; a delegate showing up instead of the exec is the same signal one level up the chain. Neither is fixed by trying harder with the person currently in the room. Both are fixed by having reached the second buyer already, so the account does not depend on one relationship surviving a reorg.

## Is it ever fine to renew on the champion's word alone?

> "It helps me understand and create targeted campaigns to power users, while also identifying inactive or disengaged ones."
>
> — Small-Business reviewer, public G2 review

Renewing on the champion's word alone is fine exactly once: the first renewal, before enough usage history exists to measure breadth properly. Every renewal after that should carry a breadth number, because the cost of checking is one report and the cost of not checking is a renewal that looked safe until the champion changed jobs.

Small accounts with a single licensed team are the other legitimate exception, since there is no second department to lose track of. The risk this page describes is specific to accounts with more than one team, more than one location, or more than one product line on a single contract, where the buyer's visibility and the user population's reality can diverge for months without either side noticing.

| Account shape | Buyer's visibility into daily use | Safe to renew on champion's word? |
| --- | --- | --- |
| Single team, one location | Buyer often is the daily user population | Yes, for most renewals |
| Multiple teams, one product | Buyer sees their own team's usage only | No: check adoption breadth first |
| Multiple products or business units | Buyer sees the product they use, not the others | No: check breadth per product |

## How does GainTrace show the buyer-user gap before renewal?

GainTrace tracks adoption breadth by team alongside the champion relationship, so a renewal built on one enthusiastic sponsor and a dormant department shows up on the account record before the QBR, not after the champion changes jobs. [Customer health signals](https://gaintrace.com/platform/customer-health) break usage down by department rather than a single account-level score, and [account management](https://gaintrace.com/solutions/account-management) surfaces the dormant teams a CSM should reach before the next renewal conversation.

## Frequently asked questions

### What does it mean when the buyer loves us but the users do not?

It means the renewal decision-maker and the daily user population have split into two audiences with two different experiences of the product, and only the buyer's view is visible in a typical QBR. Track adoption breadth by team, rather than champion sentiment alone, since a renewal built on one enthusiastic sponsor and a disengaged user base survives one cycle and rarely two.

### How do I find out if end users actually adopted the product, not the champion?

Calculate adoption breadth: the share of licensed teams or departments with at least one active user in the last 30 days. A high overall usage number can still hide four dormant departments behind one department that uses the product constantly, and the champion is almost always sitting in the department that uses it.

### Is a happy champion enough to renew safely?

Only on the first renewal, before enough usage history exists to check adoption breadth. After that, renewing on the champion's word alone is safe only for single-team accounts; anywhere with more than one department, location or product line, the buyer's visibility and the user population's reality can diverge for months without either side noticing.

### What happens to a renewal when the champion who loved the product leaves?

An account with wide adoption breadth survives the departure because the successor inherits proof the tool works across the team. An account where only the champion was ever engaged becomes a coin flip: the successor inherits a tool nobody else can vouch for, and a disengaged user base gives them every reason to consider an alternative.

### How do I reach end users when the champion controls access to them?

Ask the champion to introduce a named contact in the team with the lowest adoption breadth, rather than requesting broad access to the user base. A CSM reaching a dormant department cold usually gets ignored; a champion-introduced contact usually gets a reply, because the request is specific and the champion has already vouched for it.

### Should CSMs talk to end users directly instead of only the champion?

Yes, at least once a renewal cycle, and to someone outside the champion's own team. Vendors who say they talk to customers usually mean they talk to the admin and the power user, a small and unrepresentative slice that already chose the tool. The rest of the license count is the population whose disengagement eventually changes the champion's mind.

## How this was researched

We searched 33,600 r/CustomerSuccess, r/SaaS, r/sales and r/startups posts for champion, end user, executive sponsor and power user language; 88 posts mention a champion. We read 15 of 4,978 G2 reviews of the three most-reviewed customer success platforms that mention a champion by name and 12 that mention power users. Core feature adoption figures are Userpilot's 2024 analysis of its own product-analytics data across 547 SaaS companies; the report does not disclose whether its figures are means or medians. The second-buyer framing, the two adoption ratios and the four-step close are our own framework; the worked example uses illustrative figures.

## Sources

- [r/CustomerSuccess: How many actual end users has your team talked to this quarter, vs champions and admins?](https://reddit.com/r/CustomerSuccess/comments/1w4ywli/)
- [r/CustomerSuccess: Silent customer, big churn risk, what would you do?](https://reddit.com/r/CustomerSuccess/comments/1llpl9i/)
- [r/CustomerSuccess: Stopped running QBRs and our renewals went up](https://reddit.com/r/CustomerSuccess/comments/1ta189g/)
- [r/CustomerSuccess: When did QBRs stop being useful and how do you actually fix them](https://reddit.com/r/CustomerSuccess/comments/1uw5t55/)
- [Userpilot: Product Metrics Benchmark Report 2024](https://userpilot.com/blog/product-metrics-benchmark-report/)

## Next steps

Calculate adoption breadth on your next three renewals before the QBR, and ask the champion for one introduction into the team with the lowest score. [Start free](https://app.gaintrace.com/auth/login) or [book a demo](https://gaintrace.com/booking).