Blog

Overhead view of a pit crew in blue waiting around an empty pit box as a race car pulls in, beside the headline The First 10 Days of an IBM Audit for Decision-Makers and the LicenseHawk logo

The First 10 Days of an IBM Audit for Decision-Makers

When an IBM audit notice arrives, the early decisions belong to procurement and IT leadership. This post explains how to handle the first reply, put one owner and one channel in place, read the verification clause, bring finance and legal in early, and avoid the mistakes that widen scope before any data reaches IBM.

Airplane taking off down a lit runway at dusk beneath the headline Building the Business Case to Challenge an IBM Renewal, with the LicenseHawk logo in the corner

Building the Business Case to Challenge an IBM Renewal

Procurement teams can't push back on an IBM renewal without a documented business case, and the evidence behind one takes months to assemble. Here's what to gather, how to size the opportunity and cost the downside for finance, who has to approve the challenge internally, and how far ahead of your anniversary date the work should start.

How IBM software pricing works for procurement teams, with a clock mechanism and the LicenseHawk logo

How IBM Software Pricing Works for Procurement Teams

Procurement teams often start with the discount on an IBM quote, but IBM software pricing is set further upstream. The license metric on each line decides how many units you buy, and your Passport Advantage volume band sets the unit price. The article explains how PVU, VPC, and user metrics work, why sub-capacity pricing depends on ILMT, and how S&S renewals feed your volume band.

IBM license audit questions answered for SAM and procurement teams

IBM License Audits and the Questions Clients Ask Most

IBM doesn't always call an audit an audit. A license review, health check, verification, or CVA offer can all end with an unbudgeted bill. This guide answers the questions organizations ask most often when facing an IBM license audit, from why IBM picked you to how much data you need to provide and how settlements get negotiated.

Red Hat audit defense case study cover showing a reflective shield standing in desert sand dunes at sunrise, titled How an Enterprise Prepared for a Red Hat Audit

How an Enterprise Prepared for a Red Hat Audit

An organization running more than 1,000 servers brought in LicenseHawk when it suspected a Red Hat audit was coming. Before the notice arrived, LicenseHawk had built an independent Effective License Position and traced the largest shortfall to a retired counting metric. Third-party managed systems came out of scope, and the client challenged overstated figures in the auditor's draft from its own position.

An elephant wearing a small red hat breaks through a wall while a man in a suit looks on, beside the title How Red Hat compliance gaps build up

How Red Hat Compliance Gaps Build Up Before Anyone Notices

Red Hat compliance gaps usually build up well before an audit, through renewals that copy last year's quantities, virtual machines added without checking the subscription model, trials left open, and partner-held subscriptions nobody has traced. This article explains how each habit creates exposure and what Red Hat's own subscription guide and Enterprise Agreement say about correcting it.

A polished metal shield stands upright in a desert with light glowing along its center line, beneath the title Red Hat audit defense settles a $500,000 exposure

Red Hat Audit Defense Settles a $500,000 Exposure

An informal spreadsheet sent to an auditor gave Red Hat a $500,000 opening position before anyone commercial was involved. This case study shows how LicenseHawk rebuilt the license position from source data and defended it through the auditor's re-verification, leading to a settlement on corrected figures. It also covers the subscription changes that will lower forward costs with every system staying on Red Hat.

A small figure in a suit steps onto one end of a seesaw with a giant red hat on the other, beside the title What a Red Hat audit teaches procurement

What a Red Hat Audit Teaches Procurement

A Red Hat audit can cost more than the settlement figure suggests. Drawn from LicenseHawk's Red Hat engagements, these ten lessons show procurement teams how to check exposure figures before they reach the vendor, rebuild deployment history from installation dates, catch contract notice periods before they pass, confirm who holds the subscription account, and weigh future subscription costs alongside the historical claim.

A small figure in a suit stands in the desert facing a giant red hat, beside the title Checking a Red Hat audit report against your own numbers

Checking a Red Hat Audit Report Against Your Own Numbers

The count behind a Red Hat audit report can include finished trials and systems that aren't running Red Hat, or apply one figure across years of change. This article shows SAM and ITAM teams how to build an Effective License Position using Red Hat's counting rules and use it to test the auditor's draft finding by finding before anything is agreed.

Red Hat Audit Readiness Checklist with ten checks to complete before an audit notice arrives

A Red Hat Audit Readiness Checklist

This Red Hat audit readiness checklist pairs ten mistakes from Red Hat audit work with the step that prevents each one. It covers renewal checks, virtualization, open trials, and partner-held subscriptions before an audit, then response handling, deployment dates, draft reports, and review terms once one starts, so SAM and procurement teams know what to verify and when.