Why 'Unused Seats' Is the Wrong Metric in 2026

A 200-person company's three biggest SaaS contracts cost $183,600 a year. Every legacy spend dashboard scores them "healthy" — login rates of 92% to 100%. Stack contracted-vs-engaged + AI-replaceable and the real ceiling is roughly $39,600/year of recoverable spend (about 22% of contract value), with $16,560/year defendable in year 1 once setup costs amortize and the realization discount lands. The legacy "unused seats" metric reports zero on this stack. The unused-seats metric counts logins. It does not count work, and it does not count what an AI agent could absorb at a fraction of the cost.

Try the free calculator — 15 seconds, no signup.

The metric every SaaS dashboard still ships with

Open any SaaS spend platform. The headline number is the same: "X% of your seats are unused." A seat is "unused" if the assigned user hasn't logged in for 30 days. Sometimes 60. Sometimes the threshold is configurable.

That definition was good enough in 2019. It is not good enough now. Three things changed.

First, login activity stopped correlating with productivity. SSO-driven workflows mean users authenticate into apps for tangential reasons all the time. A salesperson opens Salesforce because Slack pinged them with a deal alert that links into the CRM. They click through, glance at the record, leave. Login counted. Work performed: roughly zero.

Second, AI agents got cheap enough to absorb work in seats that are technically active. AiSDR replaces about 55% of Outreach SDR workflow. Sierra replaces about 60% of Zendesk Tier-1 ticket volume. Intercom Fin handles 50%+ of Zendesk Tier-1 deflection. The humans those agents help displace were logging in every day. They were "active" in the dashboard. Their work output now overlaps with an agent that costs less per unit.

Third, contract terms got more punitive. Auto-renewal windows shrank from 90 days to 60 at most enterprise vendors. (Vendr's missed-cancellation playbook details what actually happens when the window closes on you.) If your renewal calendar is wrong by a week, you owe another year. Measuring "unused" two months too late costs you the whole renewal cycle.

I've watched this pattern across the dashboards we've built for mid-market customers. The "unused seats" number is almost always under 5%. The actual waste — once you stack contracted-minus-engaged with AI-replaceable — is closer to 20–35%. Two different numbers, same stack.

What the 2026 metric actually is

Drop "unused seats." Replace it with two numbers stacked on top of each other.

Layer 1: contracted seats minus actively engaged seats. "Engaged" is not "logged in." Engaged means the user performed a value-creating action in the system in the last 30 days — created a record, completed a workflow, submitted a ticket. Most modern apps expose this via API; the data is just buried under the login metric the legacy platforms surface by default.

Layer 2: engaged seats whose workflow an AI agent can absorb. This is the layer none of the legacy SaaS spend platforms model. (We compared them in detail.) The reason isn't ignorance — it's that their pricing model is a percentage of tracked spend, so they make more money when the spend stays high.

Stack the two and you get the actual savings ceiling. Layer 1 is renegotiation. Layer 2 is replacement. In a typical mid-market stack with at least one agent-eligible category (sales SDR, tier-1 support, internal knowledge), Layer 2 is roughly the same dollar magnitude as Layer 1 — sometimes larger. That is the math the legacy platforms are not showing you.

This is the contrarian take that bothers procurement teams: a Salesforce deployment with 100% login rate can still have 30%+ wasted spend. The seats are "active." The work being done in those seats is read-only lookup, status checking, dashboard staring — all of it now handled cheaper by an agent or a Slackbot at a fraction of the per-seat cost.

The math, with real prices

Take a 200-person SaaS company in 2026. Sales team of 60. Customer support team of 25. Marketing team of 18. Three contracts up for renewal in the next six months. We use the per-seat prices our calculator models against — these are negotiated mid-market rates, not the higher list prices vendors quote to companies that don't ask.

Salesforce. 80 contracted seats at $100/seat/month (the typical mid-market negotiated rate; Salesforce list price is $165 and you should be nowhere near it). Annual spend: $96,000. Login rate: 92%. By the legacy metric, this stack is "healthy" — only 8% unused. Now look at engaged usage. Of the 74 logged-in seats, only 44 are creating records, advancing pipeline, or running reports. The other 30 are reading dashboards and pulling account history.

• Layer 1 waste: 6 unused seats × $100 × 12 = $7,200/yr.
• Layer 2 waste: the 30 read-only seats can be served by an enterprise AI search agent (Glean is the canonical example, ~$60/seat/mo at scale) or a lighter Slack-integrated lookup pattern at ~$30/seat/mo. Modeled at the lighter $30/seat agent: net Layer 2 saving = 30 × ($100 − $30) × 12 = $25,200/yr.

Outreach. 50 SDR seats at $100/seat/month (catalog mid-market rate; list is $130). Annual spend: $60,000. Login rate: 100% — SDRs live in Outreach. Engaged: also 100%. Legacy metric says zero waste.

Now run the AiSDR overlay. AiSDR is $900/mo flat-fee. Its catalog compression on Outreach is 55% (per-tool, not blended across the rest of the SDR stack — that distinction matters). Math at 50 SDRs:

• Gross monthly savings: 50 × 0.55 × $100 = $2,750/mo, or $33,000/yr.
• Year-1 cost with the $15K services-overhead default for flat-fee agents: $25,800.
• Year-1 net: $33,000 − $25,800 = $7,200/yr (above unlock at this scale).
• Apply the 0.4 year-1 realization discount the dashboard bakes in: $2,880/yr defendable in year 1; the steady-state ceiling once the setup amortizes is $33,000 − $10,800 = $22,200/yr. Both numbers beat the legacy "unused seats" dashboard, which surfaces zero on this row.

Note the dashboard's realization formula: it applies the 0.4 factor to year-1 net (which already includes setup), not to the steady-state number. That matters because a sub-scale deployment (say 25 SDRs here) would produce a negative year-1 net and the dashboard would honestly report $0 defendable in year 1, even though the steady-state math would still pencil. We use the engine's formula so this post matches what the calculator outputs.

Zendesk. 20 support seats at $115/seat/month (Suite Professional). Annual spend: $27,600. Login rate: 100%. Engaged: 100%.

Sierra's catalog cost is $6,000/mo + $35,000 one-time setup. Year-1 cost: $107K. Steady-state cost: $72K/yr. At 60% compression on Zendesk, gross savings is 20 × 0.60 × $115 × 12 = $16,560/yr. The math is −$90,440 year-1, −$55,440 steady-state. Sierra doesn't pencil at this scale — its honest year-1 unlock is around 130 Zendesk seats (steady-state ~87). At 20 seats, the answer isn't "renegotiate Zendesk down to active count" — Zendesk is at 100% engagement here, there's nothing to renegotiate. The honest answer is wait until support headcount triples or the vendor offers a smaller tier.

Total ceiling across the three (year-1 net of positive items): $7,200 (SF Layer 1) + $25,200 (SF Layer 2 net of the $30/seat AI lookup agent — 30 × ($100 − $30) × 12) + $7,200 (Outreach AiSDR year-1 net) = $39,600/yr. Sierra correctly excluded.

Total year-1 realistic per engine math (Layer 1 × 0.5 renegotiate, Layer 2 + AiSDR × 0.4 deploy_agent applied to year-1 net): $3,600 + $10,080 + $2,880 = $16,560/yr — 9.0% of contracted spend, on three contracts the legacy "unused seats" dashboard scored as 92–100% utilized. That is the gap. Steady-state ceilings are higher again as agent setup costs amortize beyond year 1.

Try the free calculator — 15 seconds, no signup. Plug in your three biggest contracts and see both numbers.

Why the legacy platforms can't fix this themselves

Zylo, Productiv, and Vendr were built around a 2019 thesis: "if we ingest your SSO logs and your contracts, we'll show you which seats are unused." That thesis is still true. It is also no longer enough.

Three structural reasons they are slow to adapt.

The first is incentive misalignment. SaaS spend management platforms typically charge 1.5–3% of tracked spend. If their dashboard helps you eliminate $200K of waste, their next-year revenue from you drops. AI-agent replacement is the largest single source of waste they could surface, and it would cannibalize their revenue most of all.

The second is technical debt. Their engagement metric is "logged in last 30 days" because that is the universal field every SaaS vendor exposes. Adding "performed a value-creating action" requires per-vendor API integration work — Salesforce's REST API gives you record-create events, Zendesk's gives you ticket-touch events, Outreach's gives you sequence events, and they're all different. Cheaper for a platform to ship the lowest-common-denominator metric and call it a day.

The third is positioning. The legacy platforms sell to procurement. Procurement's job is to track contracts, not to model AI replacement. The buyer doesn't ask for the second metric, so the product doesn't ship the second metric. CFOs do ask for it — but CFOs aren't the buyer for those tools.

This is why we built SeatCompress around the AI-replacement layer first. The contract-vs-engaged layer is table stakes. The agent layer is the new line item.

How to apply this in your next renewal

Three concrete steps. You can run the first two this quarter.

Step 1: Pick the three biggest contracts on your renewal calendar in the next 6 months. Not all of them. The three with the highest annual spend. (For most mid-market companies that's some combination of Salesforce, Zoom, Slack, Outreach, Zendesk, Workday — pick yours.)

Step 2: Pull two numbers per contract, not one. From the vendor admin console, get the engaged-user count — users who created a record, closed a ticket, sent a campaign, etc. in the last 30 days. From your IdP, get the assigned-user count. Contracted minus engaged is your Layer 1 number. That alone usually justifies a 15–25% renegotiation ask. (If you've never done this, the shelfware audit playbook walks through it tool by tool.)

Step 3: Run the AI-agent overlay. For the engaged seats remaining, ask: is there a credible agent in the category? Sales SDR work — AiSDR, 11x. Tier-1 support — Sierra, Decagon, Intercom Fin (and only above their unlock thresholds). Internal IT helpdesk — Moveworks, Aisera. Read-only CRM lookup — Glean, Slack-integrated agents. Run the unlock math: agent cost (including setup for flat-fee agents) versus engaged seats × per-tool compression × per-seat cost. Some will pencil. Some won't. Sierra at 20 Zendesk seats doesn't pencil; Sierra at 130 does.

The output of those three steps is a renewal binder with two numbers per vendor: the renegotiation ask (Layer 1) and the replacement plan (Layer 2). Walk into the renewal call with both. Most vendors will give you 30–40% of Layer 1 to keep you from shopping the contract. Layer 2 you execute over the next 6–12 months. (Watch the auto-renewal clauses — those will eat your timeline if you don't.)

This won't work for every company. Companies under 50 employees can rarely hit AI-agent unlock thresholds; the per-user math fails before the flat-fee math has scale to matter. Companies over 5,000 employees usually have a procurement team running this already, just slower than they think. The 200–2,000 employee band is where this is the largest underexplored line item on the P&L.

The bottom line

Your dashboard's "unused seats" number is the floor of your waste, not the ceiling. The ceiling is contracted minus engaged minus AI-replaceable, and in the median mid-market stack that ceiling is multiples of what the floor metric shows. The CFOs who win this cycle are the ones running the second math before procurement brings them their first AI-agent contract.

Try the free calculator — 15 seconds, no signup. Plug in headcount, pick the tools you actually pay for, and see both numbers — the renegotiation ask and the agent replacement number — side by side. If the gap is under $25K, the legacy platforms are fine for you. If it's larger, you have a renewal calendar problem worth solving this quarter.