Budget season is when IT finally gets permission to cut things. The rest of the year, suggesting "we should reduce our Zendesk seats" gets met with "we might need them." In Q4, when the CFO is looking for savings targets, suddenly everyone wants to hear your ideas.
The problem is that most IT teams don't have the data ready when the window opens. You can't walk into a budget meeting and say "I think we're overpaying for Zendesk." You need numbers.
What the CFO wants to see
Three things: current spend, provable waste, and projected savings. That's it. No strategy decks, no vendor comparison matrices. Just "we pay X, we waste Y, we can save Z."
For Zendesk, this looks like:
| Metric | Number |
|---|---|
| Total agent seats | 85 |
| Active in last 90 days | 62 |
| Inactive 90+ days | 18 |
| Never logged in | 5 |
| Per-seat monthly cost | $115 |
| Monthly waste | $2,645 |
| Annual waste | $31,740 |
Those 23 idle seats cost more than most companies spend on their entire monitoring stack. That comparison lands well in budget meetings.
Where to get the data
Zendesk doesn't make this easy. The Admin Center shows agent counts but not login activity. You need to hit the API for last_login_at timestamps, then match agents to seat costs based on your plan.
LicenseTrim generates exactly this report. Connect your Zendesk, get the breakdown in two minutes, export it as a PDF or CSV for your budget presentation. The free scan is enough for the initial analysis.
If you have other SaaS tools with per-seat pricing (Salesforce, Jira, HubSpot), do the same analysis for each. The combined number is almost always more shocking than any individual tool.
Handling objections
The most common pushback is "but we're planning to hire." Fair enough. The question is whether you're planning to hire 23 agents in the next quarter. If the answer is no, you're still overpaying.
Zendesk lets you add seats mid-contract. The risk of cutting to your actual usage is almost zero, because you can always add back. What you can't do is remove seats mid-contract. So the time to right-size is at renewal.
Another objection: "it's only a few thousand dollars." Maybe in isolation. But when you add up idle seats across every SaaS tool, it's usually 5-10% of total SaaS spend. For a company spending $500K/year on SaaS, that's $25,000-$50,000. CFOs notice that.
Make it recurrant
The worst version of this is a one-time cleanup. You cut 20 seats, save $27,600/year, and everyone feels great. Then 12 months later the seat count has drifted back up because nobody tracked it.
Build the monitoring into your process. Monthly or quarterly agent reviews. Automated alerts when new seats go idle. Connect it to your offboarding process so departed employees automatically get flagged.
LicenseTrim handles the automated monitoring piece. But even if you do it manually, the key is doing it regularly. A calendar reminder is better than nothing.