Blog
Seat counts, shelfware, and the true up trap
Seat counts, shelfware, and the true up trap are three parts of one problem: you commit to a seat number, fail to use all of it, and the contract still ratchets the count upward through true ups while never letting it fall. The buyer side fix is to measure real usage, reclaim the shelfware before renewal, and negotiate the true up clause so adjustment runs both ways instead of only up.
Key takeaways
- Seat count is the committed quantity you pay for, which is almost always higher than active use.
- Shelfware is the gap between seats bought and seats used, and it is the easiest saving in any renewal.
- A true up clause lets the vendor bill for seats added mid term, but rarely lets you reduce the count.
- The counter is a two way adjustment: reclaim shelfware, right size the commit, and win seat reduction rights.
How do seat counts, shelfware, and true ups connect?
They are three stages of the same ratchet. You commit to a seat count at signing, usually rounded up to cover hiring plans that may not happen. Over the term, real adoption lands below that number, and the difference between seats bought and seats used is shelfware. Then a true up clause lets the vendor bill you for any seats you add mid term, pushing the count higher, while the same clause almost never lets you bill the gap back down. The count only moves one way, and each renewal starts from the inflated number the last cycle left behind.
Seen separately, each piece looks minor. Seen together, they form a mechanism that inflates spend automatically unless the buyer intervenes. The seat count sets the base, shelfware proves the base is wrong, and the true up trap prevents the base from ever correcting. Breaking the ratchet means addressing all three at the renewal, the one moment you hold the right to reset the count.
What is a true up and why is it a trap?
A true up is a contractual reconciliation where the vendor counts the seats you have actually deployed and bills you for any that exceed your committed quantity. On its face it sounds fair: you used more, you pay more. The trap is the asymmetry. The clause adjusts upward when you exceed the commit but offers no matching right to adjust downward when you fall below it, so growth is billed instantly while waste is locked in for the term. A team that over committed and under used is charged for the seats it added and still pays for the seats it never touched.
The trap deepens at renewal. The vendor anchors the next term on the trued up count, which now includes the peak you reached mid term rather than your steady state need. Unless you reset it deliberately, you carry that peak forward as the new floor, and the cycle repeats from a higher number every year. The clause that looked like simple fairness becomes a one way escalator.
The asymmetry in plain terms
| Event | What the standard true up does | What the buyer should negotiate |
|---|---|---|
| You add seats mid term | Bills you at the agreed rate, sometimes at list | Pre agreed add on pricing at the same discount |
| You fall below the commit | No adjustment, you pay for the unused seats | Seat reduction rights at defined points in the term |
| The renewal arrives | Anchors on the highest trued up count | Reset the commit to measured steady state use |
| You forecast growth | You over commit to be safe and create shelfware | Commit to the floor and add via the agreed add on rate |
How do you measure your real seat count?
You pull at least 90 days of admin data and separate assigned seats from active ones. Every major platform exposes last login, active versus provisioned seats, and feature adoption. Take a full quarter so a quiet month does not flatter the picture, and the gap between provisioned and genuinely active is your shelfware number. That figure is the evidence for everything that follows, because a seat reduction the vendor will resist becomes hard to refuse when you present login data showing the seats were never used.
Reconcile that against your contract's committed quantity and any mid term true ups already billed. The difference between what you are committed to, what you have trued up to, and what you actually use is the full size of the trap. Most buyers are surprised by the spread. Documenting it before the renewal proposal arrives means you negotiate from measured reality rather than the vendor's preferred count.
How do you escape the true up trap at renewal?
You make adjustment run both ways and reset the base. First, reclaim the shelfware: right size the committed quantity to measured active use so the renewal is built on a real number rather than an inflated one. Second, negotiate seat reduction rights so a future drop in need produces a matching drop in cost, turning the one way ratchet into a two way adjustment. Third, lock add on pricing at the same discount as the base, so growth no longer means buying mid term seats at an unfavourable rate. Together these three moves dismantle the mechanism that the standard contract relies on.
Timing decides whether you can do any of it. Most agreements lock the committed quantity for the term, so a seat you fail to drop before signing is a seat you pay for until the next renewal. Start the conversation 6 or more months early, while you still hold the right to reduce, and bring the usage data so the reset is grounded in evidence. The 2026 backdrop raises the stakes: published analyses put AI driven renewal asks at 20 to 37 percent against a historical 3 to 9 percent annual uplift, and every unused seat you carry in is an aggressive uplift applied to waste.
A worked example of the reset
Consider a mid market buyer renewing a platform committed at 2,000 seats. Ninety days of admin data show 1,500 active users, and a mid term true up had pushed the billed count to 2,100 after a project ramped and then wound down. The vendor opens the renewal anchored on 2,100 seats with a 14 percent uplift. The buyer presents the login data, resets the commit to the 1,500 steady state, negotiates seat reduction rights and add on pricing at the base discount, and caps uplift at 3 to 5 percent indexed to CPI. Applied to the reset base, the renewal lands well below the prior year rather than above it. The figures here are indicative and shown to illustrate the mechanics.
What is the move before your next renewal?
Measure first, then reset the contract. Pull 90 days of usage, total your shelfware, document any true ups already billed, and bring that evidence to the renewal to right size the commit and win two way adjustment rights. This is detailed work where the order of moves matters, and getting the true up clause right protects you for the whole next term. The full method sits in the SaaS Negotiation Guide, and our buyer side team runs the reset alongside you when the stakes justify it.
Reset the count in your favour.
See how to start by cutting shelfware before the renewal and bring the same rigour to Microsoft 365 true up discipline. The full set of moves sits in the SaaS Negotiation Guide. When the contract is complex, our buyer side analysts run the reset with you.
Book a Strategy Call →Published market figures reflect 2026 SaaS pricing analyses and are labelled indicative where appropriate.