ITAM and ITSM

A publisher's audit letter arrives on short notice, and the license position depends on records nobody has reconciled. Your team runs the ITAM and ITSM tools. We make sure you buy the right ones, on terms you can defend, and renegotiate them each time they renew.

Book a conversation

What ITAM and ITSM Are, and When You Need the Tools

IT asset management (ITAM) manages the life cycle, cost and compliance of what you own: hardware, software, SaaS and cloud. Software asset management (SAM) is its software side, reconciling what is installed and used against what you are licensed for. IT service management (ITSM) manages how IT handles requests, incidents and changes. The two share data: a configuration management database (CMDB) links your assets to the services they support.

When dedicated tools make sense

  • You can't see your whole estate. Complete IT visibility has dropped to 36%, down from 43% in 2025Flexera 2026 State of ITAM
  • A software publisher makes its own measurement tool a condition of your license. Some server licensing terms require it, with regular signed reports, and charge for full capacity without it.
  • Your estate spans many publishers, server software licensed by core or capacity, and devices your endpoint tools don't manage.
  • Your team has no licensing specialist for its most complex publishers. A managed service can fill that gap.

When they do not

In our judgment, platform features and a maintained register may be enough when:

  • Your estate is small and stable, with few publishers, little server software licensed by core or capacity, and built-in inventory that works.

If what you already have is enough, keep it.

What to Get Right Before You Buy

The tool is the easy part. These decide whether it gives you a license position you can defend.

Discovery finds what's installed, not what you own

A license position comes from reconciling what discovery finds against what you are entitled to: contracts, purchase records and license keys. Entitlement data is usually the part that's missing, so decide who will gather it before the tool goes live.

No discovery method sees everything

Network scans miss devices that are off the network. Agents cover devices anywhere, but have to be installed and kept current on each one. Many IoT and operational technology devices take neither. Plan for more than one method.

The CMDB goes stale unless something feeds it

Configuration records go missing, duplicate and fall out of date. At least one leading platform scores CMDB health on completeness and correctness for that reason. Decide which sources feed it and who reconciles them.

Know what you're metered on

Many ITSM tools are licensed per named person who works tickets, with cheaper roles for approvers. Discovery modules can be metered by the items they find, so widening a scan raises the count. Model each metric against your growth before you sign.

Implementation is its own purchase

Integrations with your endpoint, cloud, identity and procurement systems decide what the tool is worth, and each one has to be built and maintained. Tie payments to milestones that pass agreed acceptance tests, not to delivery.

SaaS management overlaps with SAM

SaaS management platforms and SAM tools both discover software. Buying both without a clear split pays twice for the same discovery. Cloud and SaaS licensing is covered on our technology savings and cost optimization page.

Why the Tools Matter Beyond IT

For IT and asset management leaders: an estate you can see

  • Discovery methods that together reach devices off the network, not only the ones enrolled.
  • Payments for implementation milestones tied to acceptance tests that pass.
  • Tool renewals and licensing-metric terms negotiated by TREU, while your team runs the tools.

For finance: audits on terms you negotiated

  • Shortfalls priced at your negotiated rate, not list price, with settlement as the only remedy.
  • Tool fees fixed for the first term and capped at renewal.
  • Licensing metrics modeled against your growth before you sign, so a wider scan doesn't raise the count unnoticed.

What to Watch For in Audit Clauses and Tool Contracts

Two sets of terms matter here: the audit clauses in your software agreements, which these tools help you answer, and the terms of the tool contract itself.

  1. Audit notice and frequency.

    Standard publisher clauses can allow an audit on short notice. Negotiate a longer notice period, no more than one audit a year, business hours and a scope limited to the relevant systems.

  2. Who audits, and who sees the findings first.

    Some auditors work on contingency. Require any third-party auditor to sign your nondisclosure agreement, and see the findings before the publisher does.

  3. Shortfall pricing and cost shifting.

    Some agreements make you pay the audit costs and a premium over current price once a shortfall passes a threshold. Publishers often ask list price for a shortfall. Ask for your negotiated price, with settlement as the only remedy.

  4. Self-reports and scripts.

    You can negotiate a certified self-report on request in place of an audit. Treat scripts and portal data pulls as audits too, with the same protections.

  5. The tool's price at renewal.

    Fix fees for the first term and cap increases at renewal. Avoid terms that allow prevailing rates or increases at the supplier's discretion.

  6. Your data at exit.

    Make sure the contract says the asset register, CMDB and ticket history are yours, and set a window to export them in a standard format, with any export fees stated up front.

  7. Acceptance of the implementation.

    Watch for acceptance deemed on first production use. Set a realistic testing window, and what a rejection has to show.

This list is a starting point for your review. TREU is not a law firm. Your counsel gives the legal advice.

Your Options, Compared Fairly

Your Options, Compared Fairly
Built-in platform featuresDedicated ITAM, SAM or ITSM toolsA managed serviceThrough TREU
Strength Already licensed; inventory of the devices they manageDiscovery, reconciliation, a CMDB and workflowSpecialists run the tools and keep license positions currentThe right tools and providers, on negotiated terms, renegotiated at each renewal
Limit Sees only what is enrolled; no license positionData quality and integrations take ongoing workAnother contract, with its own scope, price and exit termsDoes not run asset management or a service desk; your team or a provider does
Cost to you Included in what you already payA subscription, plus implementationA service feeTREU is paid by the supplier you select, never by you.

How TREU Buys and Renews Your ITAM and ITSM Tools

See how we work
  1. Supplier identification

    We take your requirements to ITAM, SAM and ITSM tools and managed providers across the market, and check what your existing platforms already cover.

  2. Buying cycle

    We compare options on the metrics you will pay on, the discovery coverage you need and the implementation each requires, then negotiate price caps, acceptance and exit terms with your legal team.

  3. Implementation oversight and accountability

    We hold the provider to the implementation milestones and acceptance tests it agreed to, and check the first invoice against the contract.

  4. Client and supplier lifecycle management

    We join your reviews with the tool or service provider, track its renewal date, and renegotiate metrics and price before the notice deadline, for the life of the agreement.

Questions Buyers Ask About ITAM and ITSM

What is the difference between ITAM and ITSM?

ITAM manages the life cycle, cost and compliance of what you own: hardware, software, SaaS and cloud. ITSM manages how IT handles requests, incidents and changes. They share data through the configuration management database, which links assets to the services they support.

Is software asset management different from ITAM?

SAM is the software side of ITAM. It reconciles what is installed and used against what you are licensed for, which is the position you need when a publisher audits you.

What happens in a software license audit?

The publisher, or an auditor it appoints, checks your deployments against your licenses under the audit clause in your agreement. If it finds a shortfall, you buy the missing licenses, and some agreements add the audit costs or a premium price above a threshold.

Can audit terms be negotiated?

Often, at signature or renewal. Notice periods, how often audits can happen, who the auditor is, who sees findings first, self-reports instead of audits and the price of any shortfall are all common points of negotiation.

Do we need a dedicated tool, or are built-in features enough?

Built-in endpoint and identity tools see the devices and apps they manage, but they don't know what you are licensed for. A small, stable estate may manage with them and a maintained register. Complex server licensing, many publishers or frequent audits usually call for dedicated tools.

Do we need both a SaaS management platform and a SAM tool?

They overlap on discovery. Decide which tool owns SaaS before you buy, so you don't pay twice for the same discovery. Cloud and SaaS licensing is covered on our technology savings and cost optimization page.

Does TREU run our asset management or service desk?

No. We source the ITAM and ITSM tools and providers that do, and renegotiate them at renewal. Your team, or the provider you choose, runs them.

Name the Tools Coming Up for Renewal

Name the tools and the dates they renew. We'll show you what your current tools cover, where their terms leave you exposed and which renewal to start first.

Book a conversation

TREU is paid by the supplier you select, never by you.

2001 Timberloch Place, Suite 500
The Woodlands, Texas 77380

Phone (346) 275-2400

Email info@treupartners.com

LinkedIn linkedin.com/company/treupartners