Operational ITAM Podcast

The project is finished. The invoice is lower. Six weeks later, someone asks for more licenses. What changed?

Bill Van Nort follows a fictional software service after its initial improvement has been verified. This episode separates legitimate growth, an outdated onboarding rule, and overdue temporary-access reviews, then shows how to preserve the result without blocking the service the business needs.

IN THIS EPISODE
• Keep purchased capacity, assignments and business requirements distinct.
• Check the process that creates new assignments as well as the current list.
• Set review triggers early enough to leave time for action.
• Treat missing evidence as unconfirmed.
• Reopen the decision when business needs change.
• Describe restored capacity without inventing another savings claim.

WATCH, LISTEN AND READ
https://www.operationalitam.com/pages/podcast-017-keep-the-result.html

PRACTICAL EXERCISE
Allow about an hour. Choose one completed technology change using authorized records. Record the verified outcome and date, a condition that could undermine it, the evidence that would reveal the change, its owner, the review trigger and the response deadline. Inspect a recent issue to see whether the cause was corrected and the result checked. If no example exists, mark the control untested.

CHAPTERS

• (00:00) - Keep the Result

Operational ITAM Podcast | Bill Van Nort | An EpicB Media LLC production.
https://www.operationalitam.com

An approved reduction is only the beginning. Bill Van Nort follows a fictional software subscription change from forecast through the signed agreement, implementation, invoices and a delayed credit. See why a $48,000 gross forecast becomes a $27,000 net calendar-year benefit—and how to explain every difference.

IN THIS EPISODE
• Agree the baseline, scope and reporting period.
• Distinguish assigned licenses from purchased commitments.
• Explain delayed implementation and retained capacity.
• Trace billing corrections to the affected service periods.
• Separate forecast, verified result and annualized run rate.
• Check that the service still meets the business requirement.

All case amounts are illustrative USD. The fictional supplier minimum and credit timing are not Microsoft or AWS terms. Finance determines your organization's recognition and accounting treatment.

YOUR NEXT STEP
Pick one completed technology change. Trace its estimate, agreed baseline, effective date, implemented quantity, invoices, credits and implementation costs. Explain material differences. State what is verified and what remains unresolved. Use records you are authorized to access and take the result to your finance partner.

WATCH, LISTEN & READ
https://www.operationalitam.com/pages/podcast-016-where-did-the-saving-go.html
Watch on YouTube: https://www.youtube.com/watch?v=WQgC5BoZD9g

PRACTICAL RESOURCE
F02 — Validate benefits and report business outcomes:
https://www.operationalitam.com/store/index.php?page=product&sku=F02
Bill's paid resource includes an editable procedure, flowchart and adoption/evidence checklist. Purchasing supports the show. The homework requires no purchase.

CHAPTERS

• (00:00) - Where did the saving go?

PRODUCTION
Written and hosted by Bill Van Nort. Voice production: ElevenLabs. Audio finishing: Adobe Audition. Production assistance: OpenAI Codex. Video assembly: FFmpeg. Show theme: Ten Second Pulse, created with Suno.

Operational ITAM covers practical IT asset management, software licensing, FinOps and evidence-led decisions. Website and resources: https://www.operationalitam.com/
An EpicB Media LLC production.

A renewal can pass through every department and still arrive at its deadline without a decision owner. Bill Van Nort works through a fictional customer-support renewal to show how ITAM, FinOps, procurement, finance, engineering, and the service owner can reach a defensible choice and verify what happens afterward.

The episode examines a lower-priced replacement, transition costs, a revised incumbent offer, and a delay scenario that reverses the cost ranking. Azure Hybrid Benefit and AWS Compute Savings Plans illustrate why licensing rights, consumption forecasts, and commercial commitments need a shared discussion.

The company, prices, and outcome in the central case are illustrative, not a client case study or savings benchmark.

Website and transcripts: https://www.operationalitam.com/ · Operational ITAM Store: https://www.operationalitam.com/store/ · Roles & Operating Cadence: https://www.operationalitam.com/store/index.php?page=product&sku=CP-ROLES

The store contains Bill's paid resources. Today's homework requires no purchase.

Your homework
Choose one renewal. Record the decision, last useful decision date, authorized owner, options, missing evidence and its owners, the condition that would change your recommendation, implementation responsibility, and the post-approval check.

Discussion
Where does your renewal process stall: evidence, authority, migration readiness, or checking the result?

Chapters
00:00 The meeting that cannot decide
01:08 From a better bill to a better decision
02:44 The fictional renewal
04:32 Who comes to the table
06:40 When the evidence disagrees
09:16 A short break
10:24 Two real reasons the disciplines need each other
12:22 The offer changes
15:05 Make the decision executable
16:35 After the signature
18:23 The takeaway and the homework

Transcript
Click here to view the episode transcript.

FinOps Framework: https://www.finops.org/framework/
Intersecting Disciplines: https://www.finops.org/framework/capabilities/intersecting-disciplines/
ITAM and FinOps: planning and procurement: https://www.finops.org/wg/finops-itam-practical-scenarios-planning-procurement/
Microsoft SQL Server licensing: https://www.microsoft.com/licensing/guidance/SQL
Azure Hybrid Benefit: https://learn.microsoft.com/en-us/azure/azure-sql/azure-hybrid-benefit?view=azuresql
AWS Savings Plans FAQ: https://aws.amazon.com/savingsplans/faqs/
AWS Savings Plans returns: https://docs.aws.amazon.com/savingsplans/latest/userguide/return-sp.html
An EpicB Media LLC production.

Twenty percent off sounds like progress. Until the new bill is still twenty percent higher than last year—and nobody has checked whether you need everything on it.

In Episode 014 of the Operational ITAM Podcast, Bill Van Nort examines how quantities, licensing rights, product choices, and contract terms shape a renewal bill before the discount conversation begins.

Microsoft, Broadcom, and Oracle provide three different tests. Microsoft’s July 2026 pricing changes reach existing customers at renewal. VMware licensing requires a careful look at physical capacity and retained rights. Oracle’s Java subscription demands a precise understanding of the employee metric and the rights attached to specific releases and updates.

The question throughout: what can you substantiate, what can you challenge, and what must change operationally before a smaller commitment becomes possible?

In this episode

• Separate rate increases from changes in quantity, packaging, and terms.
• Check physical-core calculations without confusing fewer virtual machines with fewer licensing obligations.
• Examine Oracle’s employee-based metric and the planned October 2026 licensing transition for Oracle JDK 21 updates.
• Distinguish a correction to the bill from a concession you want to negotiate.
• Compare staying, switching, and bridging on the same cost horizon.
• Understand why savings against a quote differ from reductions against actual spending.
• Verify that an agreed concession appears on the first invoice.

A fictional renewal example makes the arithmetic concrete. Staying with the incumbent can be the right answer—but that decision deserves a clear owner and an explanation.

The principle: scrutiny

Before you ask how much the vendor can take off, establish what belongs on the bill.

Turn the episode into action

The Operational ITAM Store offers Bill’s paid procedures, toolkits, and decision resources to help make this work repeatable.

Explore the Operational ITAM Store.

For broader coverage, the Software, SaaS & Cloud toolkit includes procedures, publisher playbooks, and tools for licensing, renewals, audit response, and consumption management.

For a focused starting point, explore Plan renewals against the notice deadline, with an editable procedure, flowchart, and adoption checklist.

Review the previews and product descriptions to choose the scope that fits your team.

Your homework

Give it about an hour. Choose one upcoming renewal and gather the quote, current agreement, latest invoice, and quantity evidence.

Explain the change in cost on one page. Identify one line you cannot substantiate, then write down the question, the person who must answer it, and the deadline. Track the notice date separately from the renewal date.

Next: The Decision Table

Episode 015 brings ITAM, FinOps, procurement, finance, and service ownership into a working decision—with shared evidence, clear authority, and an owner for the next action.

Selected sources

• Microsoft 365 pricing and packaging FAQ
• Microsoft Partner Center: August 2026 announcements
• Broadcom: counting cores for VCF and VVF
• Broadcom: perpetual licenses after support expiration
• Oracle Java SE Universal Subscription FAQ
• Oracle: JDK 21 approaches the end of its permissive license
• Microsoft licensing FAQ on Teams

Research checked September 25, 2026. The renewal arithmetic example is fictional. Customer-specific licensing rights depend on the applicable agreements.

Visit Operational ITAM

© 2026 Operational ITAM · A brand of EpicB Media LLC. All Rights Reserved.

The FinOps people wrote the bill down as a standard and invited ITAM in. Here is how to speak FOCUS before your CFO asks.

On June fourth the FOCUS Steering Committee ratified version 1.4 of the FinOps Open Cost and Usage Specification: two new datasets, forty-seven new columns, and an Invoice Detail dataset that joins a consumption record to the physical invoice on one identifier. The same month the Linux Foundation announced Tokenomicon, a conference whose front page names tokenomics, FinOps, and ITAM practitioners in the same sentence. The meter readers built themselves a language. Then they walked across the building to our side, and put our name on the door.

Bill walks into the second room of the Grid, the standards body, and breaks down what FOCUS means for ITAM: the eight columns out of sixty-five you actually need, the handful of tests any standard has to pass before you bet a program on it, the ISO 19770-3 entitlement tag he has never once received from a publisher, and the five steps that get a SaaS and licensing estate speaking the language, including the one only ITAM can do. Along the way: what the State of FinOps 2026 survey says about who now reports on licensing and the data center, UnitedHealth Group expressing a VMware data center in FOCUS, and the 1904 Baltimore fire that explains why your vendor's billing format is a thread pitch.

Plus, a listener question from Angela in Madison: the cloud FinOps team told the CFO that cloud spend is FOCUS-reconciled, and the CFO wants to know why ITAM's SaaS and licensing numbers cannot be. What do you actually say?

IN THIS EPISODE

• FOCUS 1.4 explained for ITAM: the release history, the eight columns that matter, and how last week's effective rate became Effective Cost over Pricing Quantity
• The provider table as of this week: who ships 1.2, who ships 1.3, nobody ships 1.4, and why "conformant" currently means self-declared
• ISO 19770 held up against the same tests, and an opinion, clearly labeled: FOCUS will become the language ITAM reports cost in, and what it will never carry
• Five steps to speak FOCUS: ask which version, learn the columns, put your contract register in the Contract Commitment dataset, run it in parallel, and put the export in the contract
• What FOCUS 1.5 brings in December, the Great Baltimore Fire of 1904, and the one-hour homework that produces your first invoice in the language

CHAPTERS

• (00:03) - Standards Body Visit

TRANSCRIPT

Click here to view the episode transcript.

SOURCES & FURTHER READING

• Introducing FOCUS 1.4, FinOps Foundation (June 2026): https://www.finops.org/insights/introducing-focus-1-4/
• What is FOCUS, release history and license: https://focus.finops.org/what-is-focus/
• FOCUS provider support table: https://focus.finops.org/docs/implementation/get-started/get-started-with-focus-datasets/
• FOCUS 1.5 release scope: https://focus.finops.org/focus-1-5-release-scope/
• FOCUS practitioner stories, UnitedHealth Group and STMicroelectronics: https://focus.finops.org/adoption/finops-practitioners/
• Linux Foundation announces Tokenomicon (June 2026): https://www.linuxfoundation.org/press/linux-foundation-announces-tokenomicon-a-new-conference-for-the-economics-of-ai
• State of FinOps 2026, Linux Foundation / FinOps Foundation: https://www.linuxfoundation.org/press/state-of-finops-survey-ai-value-and-skills-top-priorities-as-finops-matures-across-technology-value-98-manage-ai-90-saas-64-licensing-48-data-center-1
• NISTIR 7158, Major U.S. Cities Using National Standard Fire Hydrants, One Century After the Great Baltimore Fire (NIST, 2004): https://tsapps.nist.gov/publication/get_pdf.cfm?pub_id=861321

ABOUT THE SHOW

Operational ITAM is a podcast about the unglamorous machinery of enterprise technology — hardware and software asset management, licensing, audit defense, SaaS governance, and the money quietly leaking out of all of them.

Bill Van Nort has led IT asset management, end-user computing, IT operations, and workplace technology at large organizations across banking, mortgage, and automotive. He has reclaimed millions in software spend and survived audits from the biggest publishers on the planet.

Consulting enquiries and listener case files: operationalitam.com

The Operational ITAM Podcast is an EpicB Media LLC production.

AI consumption pricing turned software cost into a meter. Here is how to read yours before the bill does.

Software used to be priced at the signature. Now it accrues at the meter. Ramp's payments data shows AI token spend up twenty point seven times in thirteen months, and the FinOps Foundation reports ninety-eight percent of practitioners now manage AI spend, up from thirty-one percent two years ago. A seat is a price you approved once. A meter is a price you discover every month.

Bill walks into the first room of the Grid, the meter room, and breaks down the four parts of every consumption agreement: the unit, the rate, the commitment, and the true-up. Along the way: why the median business pays two thousand dollars a month while the average pays one hundred forty thousand, how Coinbase cut its AI bill nearly in half while usage grew, the controller who found ten thousand dollars a month in a term he had never heard, and the arithmetic that turns any invoice into a meter reading.

Plus, a listener question from Elena in Cincinnati: finance wants next year's AI budget as one fixed number, and consumption pricing makes that feel impossible. What do you actually give them?

IN THIS EPISODE

• The anatomy of a meter: the unit, the rate, the commitment, and the true-up, and why you need all four named for every consumption agreement you own
• Ramp's April benchmarks: a sixty-times gap between median and average AI spend, and the twenty-times price difference decided by a model default
• How Coinbase halved AI spend while usage grew: better defaults, routing, and caching, not friction and spend alerts
• The AngelList controller who learned the phrase "prompt caching" from a spend briefing and recovered ten thousand dollars a month the same day
• The three numbers to hand finance instead of one fixed budget, and the one-hour homework that produces your first meter reading

CHAPTERS
 

• (00:15) - Meter Room Opens

TRANSCRIPT
 
Click here to view the episode transcript.

SOURCES & FURTHER READING

• Ramp, AI token spend controls launch (July 2026): https://www.prnewswire.com/news-releases/ramp-launches-ai-token-spend-controls-302827389.html
• Ramp, AI token cost benchmarks (April 2026 data): https://ramp.com/blog/ai-token-cost-for-businesses
• State of FinOps 2026, Linux Foundation / FinOps Foundation: https://www.linuxfoundation.org/press/state-of-finops-survey-ai-value-and-skills-top-priorities-as-finops-matures-across-technology-value-98-manage-ai-90-saas-64-licensing-48-data-center-1
• Coinbase CEO Brian Armstrong on cutting AI cost: https://finance.yahoo.com/markets/crypto/articles/coinbase-ceo-halved-ai-costs-130000536.html
• FOCUS 1.4, FinOps Foundation: https://www.finops.org/insights/introducing-focus-1-4/

ABOUT THE SHOW

Operational ITAM is a podcast about the unglamorous machinery of enterprise technology — hardware and software asset management, licensing, audit defense, SaaS governance, and the money quietly leaking out of all of them.

Bill Van Nort has led IT asset management, end-user computing, IT operations, and workplace technology at large organizations across banking, mortgage, and automotive. He has reclaimed millions in software spend and survived audits from the biggest publishers on the planet.

Consulting enquiries and listener case files: operationalitam.com

The Operational ITAM Podcast is an EpicB Media LLC production.

The EU AI Act's Article 50 transparency obligations began to apply on August 2, with penalties up to 15 million euros or 3 percent of worldwide annual turnover, whichever is higher. It is the first time in the history of this discipline that an asset class arrived with a regulator already attached, and most organizations cannot tell you what is in it. Flexera's 2026 State of ITAM Report puts accurate AI visibility at 31 percent, while the FinOps Foundation's State of FinOps 2026 found 98 percent of FinOps teams now manage AI spend and 73 percent blew through their AI cost plans. This episode delivers on the promise made at the end of Episode 10: defining the newest asset class in the estate.

Bill lays out the five forms AI takes on its way into your organization: embedded (AI switched on inside software you already own), subscribed (standalone AI SaaS), metered (consumption-priced APIs where spend scales with enthusiasm), hosted (models you run yourself), and hidden (all four, unrecorded). Then the four questions from Episode 1, pointed at the AI estate: what you have across five forms, where your data actually goes, what it costs across five different budget lines, and when it leaves, faster than any asset class ever tracked.

Then the regulator in practitioner terms: the four Article 50 situations, the December 2, 2026 marking transition, the honest note on Article 26's deferral to December 2, 2027, and why every transparency obligation presupposes an inventory. Plus a listener question from Priya in Ann Arbor on where a CIO-mandated AI inventory even starts, the library closing with full honors as the show moves into the grid, and a one-hour shadow AI census: expense data, SSO log, asset register, three numbers on one page.

Sources cited: EU AI Act Article 50 and European Commission implementation guidelines (July 20, 2026); EU Digital Omnibus; Flexera 2026 State of ITAM Report; FinOps Foundation State of FinOps 2026; IBM Cost of a Data Breach Report 2026; Zylo 2026 SaaS Management Index.

Case files wanted. One situation, one page, anonymized: what the constraint was, what you did, what happened. If you are the person who just got handed the AI inventory question, Bill especially wants yours. Details at https://www.operationalitam.com

Next episode: the meter room. Token-based pricing, GPU hours, and reading the meter before the invoice does.

Chapters:
 

• (00:02) - AI’s Regulator Arrives

Click here to view the episode transcript.

Operational ITAM Podcast · https://www.operationalitam.com · Bill Van Nort on LinkedIn: https://www.linkedin.com/in/billvannort/

Flexera's 2026 State of ITAM Report says complete visibility into the IT estate has dropped to 36 percent, down eleven points across three years, over the same stretch that organizations bought more asset management tooling than at any point in the discipline's history. We bought more and saw less. This episode explains why, and answers the question Mike from Columbus asked back in Episode 001: should we buy a tool, and how would we know?

Bill lays out the Readiness Test, five questions to answer honestly before any purchase order: Who owns the data? When two systems disagree, which one wins? Can you produce entitlements as documents? Does a lifecycle event change a record today, without a tool? Can someone write down what the tool is for, in one sentence, with a number in it? Fail any one and a platform makes your problems more expensive instead of more visible.

Then the case for tools, made fairly: what platforms genuinely do well according to Gartner's January 2026 Market Guide, the estate where the tool is a license term rather than a maturity choice (IBM sub-capacity and ILMT), the honest cost picture, and the four signals that it is actually time to buy. Plus, a listener question from Dana in Dayton on what to do when the platform is live and nobody trusts it, the catalog room in the library, and a one-hour homework assignment that will save some organizations two years.

Sources cited: Flexera 2026 State of ITAM Report; Gartner Market Guide for Software Asset Management Tools (January 2026); IBM Passport Advantage sub-capacity licensing terms; Forrester (2013); EU AI Act Article 50.

Case files wanted. One situation, one page, anonymized: what the constraint was, what you did, what happened. Details at https://www.operationalitam.com

Next episode: the AI estate, the first asset class to arrive with a regulator attached.

Chapters:

• (00:03) - Tool Question Answered

Microsoft gave everyone seven months of warning. Almost nobody had a plan. The gap between the memo and the plan is the whole episode.

An audit arrives on somebody else's schedule. A settlement is negotiated from behind. Shadow IT happens whether you sanction it or not. Disposal's best possible outcome is that nothing happens to you. The renewal is different. It is the only recurring event in asset management where the date is known years in advance, where the other side needs something from you, and where you decide when the work begins. And we blow it consistently as a profession.

This one is the 18-month clock — four positions, each with exactly one job — and the five traps written into paper you have already signed. The thesis is not subtle: in a renewal, timing beats tactics. The clever negotiator who starts 60 days out loses to the mediocre one who started 18 months out. Every lever in this episode takes months to build and four seconds to deploy.

A listener in Indianapolis writes in six weeks from a renewal whose quote just doubled, and gets an honest answer rather than an encouraging one.

IN THIS EPISODE

- Why 61% of IT leaders cut a project or initiative to pay for unplanned software cost increases — renewals are now cancelling roadmap items, not headcount
- Flat application counts and 8% more money: the growth is not sprawl anymore, it is price
- The 18-month clock — count, decide, build, ask — and the 60-day cliff most programs are actually standing on
- The version of shelfware that survives every audit and fails every business case: deployed, assigned, compliant, and completely idle
- Why leverage is a documented, costed, credible answer to "and what if we don't" — and why it never has to be executed
- Broadcom/VMware and Oracle Java as live worked examples, including opening quotes that overstated the actual footprint by 20 to 40%
- Five traps: the notice window, the uplift clause, the co-term, the discount shell game, and the multi-year commitment
- Why you should never negotiate against list price, and the one discipline that catches more money than every other tactic combined
- The University of California walking away from Elsevier, and the single reason they could

CHAPTERS

• (00:03) - Renewal Power Plays

Microsoft 365 pricing and packaging updates — the official notice. Announced 4 December, effective 1 July 2026, covering Enterprise, Business, Frontline, and Government commercial equivalents. Office 365 E3 moves from $23 to $26 per user per month, Microsoft 365 E5 from $57 to $60, with Frontline plans rising as much as 43%.
https://www.microsoft.com/en-us/licensing/news/2026-m365-packaging-pricing-updates

Zylo 2026 SaaS Management Index — 305 applications and roughly $55.7M average annual SaaS spend, up about 8% year over year on a flat application count. Also the source for 54% average license utilization, 79% of IT leaders seeing a renewal price increase, 78% hit with unexpected consumption or AI charges, and 61% cutting a project to absorb unplanned software cost.
https://zylo.com/2026-saas-management-index

VMware distributor Arrow says minimum software subs set to jump from 16 to 72 cores — The Register, 28 March 2025. The primary reporting on the minimum core-count change and the 20% penalty for subscriptions not renewed by the anniversary date.
https://www.theregister.com/2025/03/28/arrow_vmware_licensing_change/

VMware Cloud Foundation — current product and licensing information
https://www.vmware.com/products/cloud-infrastructure/vmware-cloud-foundation

Oracle Java SE Universal Subscription — the per-employee licensing metric introduced in January 2023
https://www.oracle.com/java/java-se-subscription/

Organizations are parting ways with Oracle Java for open-source alternatives — IT Brew, 29 July 2025, reporting on the joint ITAM Forum and Azul survey of 500 IT and software asset management professionals, which found 79% of organizations have migrated away from Oracle Java or plan to.
https://www.itbrew.com/stories/2025/07/29/organizations-are-parting-ways-with-oracle-java-for-open-source-alternatives

OpenJDK distributions referenced in this episode: Eclipse Adoptium, Amazon Corretto, Azul Zulu, Red Hat build of OpenJDK, and the Microsoft Build of OpenJDK

UC terminates subscriptions with the world's largest scientific publisher in push for open access — University of California, 2019. The Elsevier walk-away referenced in the library segment.
https://www.universityofcalifornia.edu/press-room/uc-terminates-subscriptions-worlds-largest-scientific-publisher-push-open-access

A note on evidence: settlement terms and negotiated pricing are almost universally covered by non-disclosure, so no public dataset of renewal outcomes exists. The advisory-firm figures on VMware settlement ranges and quote overstatement are reported observations rather than published research, and the negotiation guidance in this episode reflects thirty years on the customer side of the table. It is offered as practitioner knowledge, not as study findings.

THE COMPANION TOOL

The 90-Day Pre-Renewal Readiness Checklist executes what this episode describes — 57 checks across intake, waste signal analysis, business owner validation, and negotiation preparation, with an owner and an evidence artefact named for every item. Free, no email required.
https://www.operationalitam.com/pages/resources.html

RELATED EPISODES

Episode 003 — Software Asset Management: Proving What You Own
Episode 004 — Surviving a Software Audit, Part One: The Letter Lands
Episode 005 — Surviving a Software Audit, Part Two: The Settlement

LISTENER CASE FILES

Got a renewal you cannot justify, or a notice window closing faster than your data is coming together? Send it over — anonymized, sanitized, no company names. Just the situation, what you did, and what happened.
https://www.operationalitam.com/pages/podcast-ask.html

ABOUT THE SHOW

Operational ITAM is a podcast about the unglamorous machinery of enterprise technology — hardware and software asset management, licensing, audit defense, SaaS governance, and the money quietly leaking out of all of them.

Bill Van Nort has led IT asset management, end-user computing, IT operations, and workplace technology at large organizations across banking, mortgage, and automotive. He has reclaimed millions in software spend and survived audits from the biggest publishers on the planet.

Consulting enquiries and listener case files: operationalitam.com

Thirty years in enterprise IT, distilled into four questions every asset program has to answer.

The pilot episode. Host Bill Van Nort opens the series with three decades of enterprise IT leadership behind him — banking, mortgage, automotive — and a straightforward thesis: buried inside a boring-sounding phrase are millions of dollars, real career leverage, and some of the best war stories in enterprise technology.

This episode establishes the four fundamentals every program must answer: know what you have, know where it is, know what it costs, know when it leaves. Bill explains why asset management is ultimately a trust discipline rather than an inventory discipline, states his biases up front — evidence over enthusiasm, customer over publisher, simple over clever — and previews the season ahead.

Plus: a listener question from Mike in Columbus on what to do when leadership says an ITAM tool isn't in the budget.

IN THIS EPISODE

- Why nobody notices asset management until it's broken
- The four fundamentals: know what you have, where it is, what it costs, when it leaves
- Why IT asset management is really about trust, not assets
- How the same fifteen questions wear two hundred different outfits
- Starting an ITAM program with no tool and no budget
- What license compliance actually costs when nobody is keeping score
- The show's format, biases, and what's coming this season

CHAPTERS

• (00:23) - Podcast Opening

ISO/IEC 19770-1 — IT Asset Management Systems standard
https://www.iso.org/standard/68531.html

IAITAM — International Association of IT Asset Managers
https://www.iaitam.org

LISTENER CASE FILES

Got a situation you'd like worked on air? Send it over — anonymized, sanitized, no company names. Real constraints, real politics, real budgets. operationalitam.com

ABOUT THE SHOW

Operational ITAM is a podcast about the unglamorous machinery of enterprise technology — hardware and software asset management, licensing, audit defense, SaaS governance, and the money quietly leaking out of all of them.

Bill Van Nort has led IT asset management, end-user computing, IT operations, and workplace technology at large organizations across banking, mortgage, and automotive. He has reclaimed millions in software spend and survived audits from the biggest publishers on the planet.

Consulting enquiries and listener case files: operationalitam.com