Choose an IBM compliance assessment provider on one criterion above all others: demonstrated command of sub-capacity licensing and its metering conditions, because the gap between sub-capacity and full-capacity counting is where most IBM exposure actually lives, and a provider who cannot audit your ILMT estate cannot tell you what you owe. This guide explains what an effective license position involves on an IBM estate, the traps specific to IBM's metrics, who sells compliance assessment work and on what terms, the questions and walk-aways for a shortlist, and how engagements are paid. It names no firms; see the firms that do this work →
Published 5 January 2026 · Last reviewed 30 March 2026
A compliance assessment produces an effective license position: everything you are entitled to run, reconciled against everything you actually run, expressed product by product in IBM's own counting conventions, with a remediation plan for the difference. Neither side of that reconciliation is trivial at IBM. Entitlements live in Passport Advantage records, but also in decades of acquisition history — products renamed, re-bundled and re-metricated as IBM absorbed the companies that built them — so part of the work is genuine archaeology through old agreements and proofs of entitlement. Deployment lives in discovery data that must then be converted into Processor Value Units under full- or sub-capacity rules, Virtual Processor Cores under Cloud Paks, Resource and User Value Units, and Authorized Users.
Buyers commission the work on triggers: an approaching renewal or major negotiation, audit-readiness when IBM's review cadence suggests a letter is coming, due diligence around an acquisition or divestiture, or simple board-level assurance after years of estate drift. The assessment is one of seven services in this directory and frequently feeds the others — a clean ELP is the opening position for a renewal, the foundation of an audit response, and the baseline for any optimization program.
This guide is general information about selecting an IBM compliance assessment provider, not legal advice and not a substitute for counsel where a dispute looms. It names no firms; the IBM firm directory lists providers with balanced pros and cons, listed, not ranked.
Sub-capacity eligibility, first and always. Sub-capacity licensing lets you pay for the virtual cores allocated to a workload rather than the full physical capacity of the hardware underneath it — but only while the conditions hold: an eligible metering tool such as the IBM License Metric Tool deployed across the estate, configured correctly, generating reports that are retained on schedule. Where the conditions fail, counting defaults to full capacity, and that recalculation across a virtualized estate is routinely the single largest line in an IBM compliance finding. A provider's first competence test is whether their methodology starts there.
Entitlement archaeology. The deployment side of an ELP is tooling; the entitlement side is history. Products acquired through IBM's many acquisitions carry legacy metrics and migration paths, bundled components carry restricted-use rights that look like full products to a discovery scan, and supporting programs ship inside other programs with their own limits. Providers without a research bench here systematically overstate exposure — which is exactly the error a later negotiation pays for.
Conversion math. Estates mid-way through moves into Cloud Paks or from perpetual to subscription hold mixed entitlements with conversion ratios that must be applied precisely; container platforms add per-namespace metering questions of their own. An assessor fluent only in classic PVU counting will misstate a modern IBM estate in both directions.
| PROVIDER TYPE | WHAT THEY BRING | WHAT TO WEIGH |
|---|---|---|
| Independent SAM boutique | Buyer-side only; ELP methodology refined across repeated IBM engagements; findings built to survive vendor challenge | Verify bench depth on your stack — mainframe, containers and legacy acquisitions are specialisms, not defaults |
| Big 4 / large audit practice | Scale, methodology, global reach; comfort for boards that want a recognized letterhead | The same houses are engaged by vendors to run compliance reviews of customers; ask directly whether the firm performs vendor-commissioned IBM work and how the wall is built |
| Vendor-sanctioned SAM provider | Deep familiarity with IBM's processes and expectations; standing with the vendor | Holds an ongoing commercial relationship with the party your exposure concerns; understand what flows back to IBM and when |
| Reseller-attached practice | Transaction history on your account; convenient route from finding to fix | The fix it proposes is also the product it sells; remediation-by-purchase deserves a second opinion |
| SAM tool vendor services arm | Strongest at deployment data quality and ILMT/discovery hygiene | An ELP is judgment on top of data; confirm the entitlement-research and metric-interpretation bench exists |
| Law firm | Privilege over findings; contract interpretation where entitlement language is disputed | Rarely runs tooling or builds the ELP itself; typically directs a technical provider rather than replacing one |
The conflict question is sharper here than anywhere else in the seven services: the deliverable is a number that one side of a future negotiation would like to be large. Apply the independence test — who else pays this firm, and does any of it depend on IBM or on what the finding turns into? — and put the answer in the engagement letter. The vendor-wide selection problem is covered in how to choose an IBM licensing partner; if a review letter has already arrived, the calculus changes and how to choose an IBM audit defense firm is the page you want.
1. Walk us through how you would verify our sub-capacity eligibility — tool coverage, configuration, report retention — and what you do when you find a gap that cannot be repaired retroactively.
2. Our entitlements include products IBM acquired and re-bundled years ago. How do you reconstruct entitlement positions where the paper trail crosses acquisitions and metric migrations?
3. Show us an anonymized ELP you delivered for an estate like ours. How was it structured, and how did it hold up when the vendor or its auditors challenged it?
4. Which discovery sources do you accept as inputs, how do you validate their completeness, and where does ILMT data end and your judgment begin?
5. If our position turns out to be short, who designs the remediation — and do you or any affiliate earn anything from the licenses we might then buy?
6. Have you delivered assessments under legal privilege, and how does your workflow change when counsel directs the engagement?
7. Does your firm perform compliance work commissioned by IBM or any other software publisher — and if so, how are buyer-side engagements separated?
Concrete, dated, anonymized answers are the pass mark. The broader script lives in 20 questions to ask a licensing consultant.
Walk away from a provider whose methodology never mentions sub-capacity conditions — on a virtualized IBM estate that is not an oversight, it is the whole liability. Walk away from "free" or vendor-funded assessments offered as a door-opener: an ELP whose economics depend on what you buy afterwards is a sales instrument, and the same logic applies to assessments that arrive bundled with a pre-built remediation quote. Be equally wary of a firm that cannot say, plainly, whether it also works for software publishers; the answer may be acceptable, but the inability to answer is not. And treat any promise that a finding will be "kept informal" with IBM as a misunderstanding of how compliance information travels.
The engagement itself is usually fixed-fee, scoped by estate size, product families and entitlement complexity, and that is the cleanest structure: the deliverable is a defensible number, and the fee should not move with the number's direction. Day rates appear for narrow scopes — a single product family, a pre-renewal spot check. Gain-share is rare here and should stay rare; a fee tied to exposure reduced or shelfware found puts the assessor's economics inside the finding. The structures and their incentives are dissected in the fee models guide. We publish no prices anywhere on this site.
Expect four to ten weeks for a first full ELP on a large estate, with data collection — not analysis — the usual bottleneck. The output worth paying for is three things: the position itself, the evidence chain behind every line, and a remediation sequence you control the timing of.
An effective license position (ELP) is a reconciliation of everything you are entitled to run against everything you actually run, computed per product in the vendor's own metrics. On an IBM estate that means entitlements drawn from Passport Advantage records and legacy acquisition paperwork, deployment drawn from discovery tooling, and the gap expressed in PVUs, VPCs, RVUs, UVUs and Authorized Users — with a remediation plan for whatever the reconciliation surfaces.
Because sub-capacity licensing — paying for the virtual cores you allocate rather than the full physical capacity of the hardware — is conditional. IBM requires an eligible metering tool such as ILMT to be deployed, correctly configured and generating retained quarterly reports. Where the condition fails, licensing defaults to full capacity, and that single recalculation is routinely the largest number in an IBM compliance finding; the full-capacity vs sub-capacity explainer works through the arithmetic. Verifying and repairing sub-capacity eligibility is therefore the heart of any serious IBM assessment.
It is a relationship to understand rather than a label to trust or dismiss. Firms in vendor-sanctioned SAM programs gain process knowledge and a degree of standing with IBM, but they also hold an ongoing commercial relationship with the vendor whose exposure they are measuring for you. Ask how the relationship is compensated, what is reported to IBM and under what circumstances, and decide with that on the table.
If the result could plausibly end up in a dispute, an audit response or a settlement negotiation, many buyers route the engagement through counsel so the findings are produced for legal advice rather than as a freestanding report. That is a question for your lawyers, not a consultancy sales point — but a provider who has never worked under privilege, or who shrugs at the question, has not operated at the sharp end. The lawyer-or-consultant decision more broadly is covered in licensing lawyer vs licensing consultant.
Treat the first assessment as a baseline and refresh on triggers rather than a fixed calendar: before a renewal or major negotiation, after significant virtualization or container-platform change, after an acquisition or divestiture, and when audit activity is signalled. Estates with mature SAM operations fold the reconciliation into continuous practice — that is the managed-SAM service, and the IBM SAM page lists the firms that run it.
In neutral alphabetical order with balanced pros and cons, never ranked. Independence is shown as a pro; reseller, Big-Four or vendor-side ties are shown as a con — both stated as factual trade-offs for you to weigh.
Firm-agnostic guides — when you are ready to compare actual firms, the IBM directory lists them with balanced pros and cons.
Why ILMT decides the number →
Selection once a review is live →
What the ratios really change →
Who your advisor really works for →
See the firms that do this work →
Every field guide on the site →
Tell us what your IBM estate looks like and what is driving the assessment — renewal, audit signal, M&A or assurance — and we will route your brief to firms that build defensible IBM license positions. The directory and matching are free for buyers, no vendor ever sees your brief, and we add no markup.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.