The fast answer: pull the agent list, match every seat to real ticket activity, reclassify request-only users as requesters, remove the inactive licenses, and put the reconciled number in place before SolarWinds quotes. Agents are the per-seat cost driver, so this is the single most reliable way to lower the bill without changing what your team can do. The tier you sit on sets the rate, covered in the SolarWinds Service Desk plan tiers comparison, and the count is what that rate multiplies. For the full cost picture, see the SolarWinds Service Desk pricing guide.
Book a contract negotiation review →Why do SolarWinds agent counts drift upward?
Agent counts grow for predictable reasons and almost never shrink on their own. People leave but their licenses stay assigned. Project staff get full agent access for a short engagement and keep it. Managers and stakeholders are given agent seats to view dashboards when a lighter access type would do. Each of these is a paid seat that nobody removes, and at renewal the vendor quotes off the total, treating the drift as your baseline. The job is to reverse the drift before the quote, not argue about it after.
Your move: set a recurring quarterly review of the agent list so drift is caught continuously, not once every renewal cycle under time pressure.
Agent or requester: who actually needs a paid seat?
The most valuable distinction is between an agent and a requester. An agent works tickets and consumes a paid license. A requester only raises and tracks their own requests and is generally not charged the same way. Across estates, a meaningful share of "agents" are people who have never resolved a ticket, only submitted them, which means they should be requesters. Reclassifying them removes the paid seat without removing their access to the service desk.
| Access pattern | What they do | Correct classification |
|---|---|---|
| Resolves and closes tickets | Works the queue daily or weekly | Paid agent (keep) |
| Only submits requests | Raises and tracks their own tickets | Requester (reclassify, stop paying) |
| Views dashboards or reports | Reads data, does not work tickets | Lighter access or reporting view, not a full agent |
| Left or changed role | No activity in the review window | Deactivate and reclaim the seat |
| Short-term project staff | Active for a fixed engagement | Time-box the seat and remove on exit |
Your move: run the agent list against this table and tag every seat in one of the five rows. The "reclassify" and "deactivate" rows are your immediate savings.
How do you right-size before renewal, step by step?
- Export the full agent list with last-activity data. You need each agent, their role, and when they last worked a ticket, not just the headcount the contract shows.
- Define the activity window. Use the last three to six months. Anyone with zero ticket-handling activity in that window is a candidate to reclassify or remove.
- Reclassify request-only users. Move anyone who only submits requests to requester status so they stop consuming a paid agent license.
- Deactivate leavers and stale seats. Remove agents who have left or changed role. This is reclamation, and the method generalizes in the pricing guide.
- Time-box temporary access. Put an end date on every project or contractor seat so it cannot drift into the next renewal.
- Lock the reconciled count in the order. Present the corrected number as the new baseline and get it written into the renewal, not just promised on a call.
Your move: finish steps one to four at least three months before renewal so the corrected count is the starting point of the negotiation, not a concession you have to extract.
What does right-sizing typically free up?
It varies by estate, so we do not quote a fixed percentage for a single product. What is consistent is the pattern: the seats that come back are leavers, request-only users misclassified as agents, and stakeholders who needed a report rather than a license. Because the saving is the seat count multiplied by the per-agent rate, every cycle, even a modest reduction compounds. Across 500+ ITSM engagements the firm averages a 30 percent reduction overall, and seat reconciliation is usually the first and cleanest contributor.
Your move: express the reclaimed seats as an annual figure, not a one-off, so finance sees the recurring value and backs holding the count down.
Our gated ITSM Shelfware Reclamation Toolkit includes the seat-reconciliation worksheet and the activity-window template behind this method.
Where right-sizing fits the negotiation
Seat count and tier are the two levers on this contract, and they multiply each other. Right-sizing lowers the count the tier rate applies to, so doing it first makes every other ask cheaper. We run it inside the full negotiation rather than as a standalone cleanup, because the reconciled count is also the evidence that anchors the price discussion. When you are ready to act, the commercial hub is the SolarWinds platform page and the engagement runs through our contract negotiation service on fixed fee or gainshare.
Frequently asked questions
- How do I right-size SolarWinds Service Desk agent counts?
- Pull the agent list with last-activity data, reclassify request-only users as requesters, deactivate leavers and stale seats, time-box temporary access, and lock the reconciled count in the renewal order before the vendor quotes.
- What is the difference between an agent and a requester?
- An agent works tickets and consumes a paid license. A requester only raises and tracks their own requests and is generally not charged the same way. Misclassification is a common source of overspend.
- When should I right-size before renewal?
- Three to six months out, so the reconciled count is in place before SolarWinds builds the quote off your current entitlement.
Reclaim the dead seats.
We reconcile the agent list, reclassify requesters, and lock the count before you sign. Fixed fee or gainshare.
Book a contract negotiation review →