Customer Usage Report Template
Two documents and three sheets that report adoption by team instead of one blended number, so the champion can forward it as their own case.
Free download · No account needed
Bramwell Hospitality Group · 100-seat contract, March 2026
76% blended adoption. Two of four teams are nowhere near it.
| Team | Licensed | Active | Adoption | Flag |
|---|---|---|---|---|
| Front Desk Operations | 40 | 38 | 95.0% | Expansion watch |
| Revenue Management | 20 | 18 | 90.0% | Steady |
| Corporate Finance | 15 | 14 | 93.3% | Steady |
| Housekeeping Ops | 25 | 6 | 24.0% | Renewal watch |
Housekeeping's 19 idle seats cost $25,080 a year against $816 a year in value its six active users generate. Front Desk has 5 people waiting for a seat that doesn't exist. The 76% blended average sits between both and explains neither.
Every usage-report template on page one for this query assembles the same slide deck: usage telemetry, feature adoption, a value-realization section, sent quarterly through a QBR. Flexera's own State of ITAM survey puts underused SaaS spend at 33 percent industry-wide, and a single blended adoption percentage is precisely the number built to hide which team that 33 percent sits inside. None of the templates split adoption by team before it reaches the customer. They report the account's average and call it the usage story.
For one fictional 100-seat account, Bramwell Hospitality Group, blended adoption reads 76.0 percent this month, an unremarkable number. Broken out by team, Front Desk Operations sits at 95.0 percent with five people waitlisted for a seat that does not exist. Housekeeping Ops sits at 24.0 percent, 19 of 25 seats idle for 60 or more days, costing $25,080 a year, 19.0 percent of the account's $132,000 contract. Its six active users are generating $816 a year in measured value against that cost. Both facts were inside the same 76 percent the entire time.
The quarterly business review keeps the customer-facing deck and the internal renewal read as two separate artifacts. This report crosses that line on purpose. The same per-team number that tells a champion which team to defend at renewal also tells them which team to ask for more seats in, so one document carries both arguments into their own budget meeting. A team past the expansion threshold routes to the queue-based math behind the actual ask. A team past the renewal-risk threshold routes to a full portfolio read when more accounts need the same check.
What's in the pack
Report Adoption by Team, Flag on a Count
The method itself: adoption against licensed seats reported per team, never blended, and flagged only from a counted access request or a real inactive streak, not the percentage alone.
Usage by Team sheet
Active users, logins and top features per team for the reporting month, read from the usage export rather than guessed from job titles.
Adoption Against Licensed Seats sheet
Licensed against active seats by team, with idle seat cost stated in the contract's own dollars and the Renewal watch or Expansion watch flag on the row.
Value Metrics sheet
One usage-derived calculation per team with a clear automated task: time saved, multiplied by active users and the customer's own stated hourly rate.
Report Narrative doc
The monthly report itself, leading with the team rows and the flags, written so the champion can forward it into their own budget conversation without edits.
Recommendation Note doc
One concrete ask per flagged team, a specific seat count or a time-boxed adoption push, against the account's own renewal date when one is on file.
How it works
- 1
Send this month's usage export
By team if the export supports it, plus licensed seat counts and the contract's per-seat price.
- 2
River builds Usage by Team
Active users, logins, sessions per active user, and the top features actually used, per team.
- 3
Adoption gets joined against licensed seats
Idle seat cost in contract dollars, and a flag set from a counted access-request queue or a real inactive streak, not the percentage alone.
- 4
Get the report and the recommendation
A forwardable narrative leading with team rows, plus one concrete ask per flagged team on a separate note.
Frequently asked questions
Is this template free?
Yes. Two Word documents and three CSV sheets, downloaded as a zip, no signup. River is the optional half: it reads your usage export by team, licensed seat counts and per-seat price, then builds Usage by Team and flags each team on a counted fact rather than a percentage.
Why report adoption by team instead of one company-wide number?
Because the blended number is the one figure guaranteed to be true of no single team. Flexera's own survey puts underused SaaS spend at 33 percent industry-wide; reporting by team is what shows a champion which specific team that waste, or that unmet demand, sits inside.
Does a team need to cross a percentage threshold to get flagged?
No. Renewal watch needs sub-50-percent adoption plus a real 60-day-or-longer inactive streak on an idle seat. Expansion watch needs a dated, counted access request with no seat to assign, regardless of the percentage. A team can sit at 95 percent with nobody waiting and correctly get no flag at all.
Isn't a near-full team obviously ready for an expansion pitch?
Full is not, by itself, a reason to expand; a dated person waiting for a seat is. A team above the expansion threshold with an empty waitlist gets no recommendation here. The expansion and upsell brief is the deeper, queue-based read once a real waitlist exists.
How is this different from a quarterly business review or a health review?
The quarterly review grades value claims against evidence classes for one account's meeting. The health review decides which accounts in a whole book need attention this cycle. This pack reports one account's per-team adoption every month and is written to be forwarded, not presented.
What if the customer won't share an hourly rate for Value Metrics?
Then that team's row on Value Metrics stays blank rather than getting an estimated figure. The rule this pack runs on is no industry benchmark substitutes for a rate the customer has not confirmed; the adoption and idle-seat-cost numbers, which come from the contract itself, still get reported in full.
Report adoption by team before it ships blended
Send this month's usage export, licensed seat counts and per-seat price. Get adoption by team, a flag set from a counted fact, and a report the champion can forward as-is.
Edit with AI