InvGate Agent and Node-Based Licensing Explained

I spent years on the sell side, and the cleanest way to keep an account paying too much is to let the two meters blur together. One total, one renewal, one shrug. The buyer who separates agents from nodes and audits each list is the buyer who pays for what they use. The full pricing context is in the InvGate Service Management pricing guide for 2026; this piece is about the two meters and how to control each.

What does InvGate charge for: agents or nodes?

Both, on different products. InvGate Service Management licenses per agent. An agent is someone who works the queue: resolves tickets, manages change, runs problem records. End users who only raise requests are not paid agent seats. InvGate Asset Management licenses by node. A node is a managed asset, a workstation, server, network device or other tracked item, and you pay on the count under management. If you own both products, you are settling two counts, not one.

How do you right-size the agent count?

Pull the agent list and test every seat against actual queue activity over the last quarter. Anyone who only approves, reads dashboards, or raises the occasional request is a candidate to move off a paid agent seat. The pattern is identical across ITSM tools: the vendor quotes off your current entitlement, and the entitlement is almost always padded with people who never touch a ticket. The full method is in how to right-size InvGate agent counts.

How do you control the node count?

Audit the asset inventory before renewal, not after. Remove decommissioned devices, merge duplicate records, and confirm your discovery is not double-counting the same machine. The cost drivers specific to the asset product are in InvGate Asset Management pricing and cost drivers. A clean node count going into a renewal is leverage; a dirty one is a gift to the vendor.

What should you negotiate, not just count?

Counting is half the job. Once the agent and node numbers are clean, benchmark each rate against deals of similar size using how to benchmark an InvGate contract, then lock the terms. Cap the annual uplift so a clean count today is not eroded next cycle. Where you run both products, push for blended commercial terms rather than two independent renewals that drift on different dates. And keep a costed alternative in view, because InvGate competes hard against Freshservice and ManageEngine on price, which is leverage you can use.

The firm has run this sequence across more than 500 engagements and $420M+ in ITSM contract value, averaging a 30% reduction. The discipline behind it, map then benchmark then leverage then close, is in our guide to ITSM renewal negotiation.

How do the two meters trip buyers up at renewal?

The classic failure is treating the combined invoice as one number to discount. You ask for ten percent off the total, the vendor obliges, and you walk away pleased, having never noticed that a third of your nodes are retired devices and a fifth of your agents are coordinators who only approve. A discount on an inflated count is still an inflated bill. The discipline is to clean each meter first, then negotiate the rate, because the count correction is almost always larger than any percentage the vendor will volunteer.

The second failure is the renewal date itself. When the two products share one date you can negotiate them together; when they drift onto separate dates you lose the leverage of the larger combined commitment and end up in two weaker conversations. If your InvGate dates have separated, co-terminating them at the next renewal is worth more than it looks, because it restores the single negotiation and lets you trade the full spend for better terms.

What proof do you bring to an InvGate negotiation?

Evidence, not assertions. For the agent side, bring queue-activity data showing who actually works tickets versus who only logs in. For the node side, bring the reconciled inventory with retired and duplicate devices flagged and removed. For the rate, bring benchmark data on what comparable estates pay. A vendor can wave away a request for a better price; it cannot easily wave away a reconciled count and market data sitting on the table.

This is the same buyer-side stance the firm takes on every platform, and it is why preparation beats persuasion. The fuller method, including how InvGate stacks up against Freshservice and ManageEngine on cost, is worth reading alongside this, because a credible alternative is part of the evidence that moves a vendor.

What to do next

Separate the agent list from the node list, audit each, and benchmark both rates before the renewal quote arrives. When you are ready to run it, the engagement goes through our contract negotiation service on fixed fee or gainshare, and the broader pricing picture is in the InvGate pricing guide.

Frequently asked questions

How does InvGate license its service management product?

Service Management is per agent, the people who work tickets; end users who only request are not charged. Asset Management is by nodes, the devices under management. Running both means two meters. Rates vary by deal size, so confirm against your quote.

What is a node in InvGate Asset Management?

A managed asset such as a workstation, server or network device. You pay on the count under management, so retired or duplicate assets keep inflating the bill until you clean the inventory.

What inflates an InvGate bill most often?

Agent seats held by people who only request or approve, and a node count padded with stale or duplicate devices. Reconcile both before the vendor sets a baseline; we average a 30% reduction.