Challenge the Bill Before You Negotiate the Discount

Hey everybody, and welcome back to the Operational ITAM Podcast. I'm Bill Van Nort, and today we're going to do something deeply unreasonable. We're going to ask a software quote to explain itself, before the discount, before the account team brings in somebody with a more impressive title,

before anyone says, this offer expires Friday. Microsoft's July 1st, 2026 pricing changes are now meeting customers at renewal. Oracle has an October licensing transition planned for updates to Java 21, and a VMware renewal still requires you to understand exactly which physical

capacity you're buying. Those are different commercial situations. Treat them as one generic price increase, and you'll spend the meeting arguing about the wrong thing. The title today is Challenge the Bill Before You Negotiate the Discount.

Because a generous discount on a quantity you never needed is a very polished way to overspend. Good morning, good afternoon, or good evening, wherever you're listening from. This is the show where we take the unglamorous machinery of enterprise technology and make it make sense. Grab your coffee.

In episode 13, I promised the rate case. We've read the meter. We've looked at how to describe the bill in a common language. Today, we sit on the customer's side of the table and ask what we're actually being charged for. One limit on our grid analogy. Software publishers aren't regulated utilities,

and your renewal meeting doesn't come with a commission that can set their price. I would enjoy watching that meeting. But we have to work with the agreement we actually signed. So bring the agreement, the current quote, the last invoice, and your evidence of the estate.

The question is simple enough to say out loud. Can we explain the movement from what we paid to what we're being asked to pay? Let's start with Microsoft because the date on the announcement and the date on your bill may be different.

Microsoft's current pricing FAQ says existing customers see the July changes at their next renewal after July 1st. Existing multi-year agreements keep their current pricing until renewal. That distinction belongs in your forecast. Microsoft's published commercial

table puts Office 365 E3 with Teams at $26 per user per month, up from $23. Microsoft 365 E5 with Teams moves from $57 to $60. Those are published prices for those specific suites. Your negotiated price, currency, agreement, and billing arrangement still need their own check.

Here's how I'd work the quote. Start with the exact product on each line, with Teams or without, which tier, which add-ons, then reconcile the paid population to the people and service requirements that justify it. An inactive account is an investigation, not automatic permission to remove

a license. Somebody may be on leave. A retention or security requirement may depend on that assignment. Ask the owner, establish the requirement, and document the decision. Then check what the new suite includes. Microsoft's packaging announcement adds

security and management capabilities to selected plans. If you already buy overlapping functionality separately, there's a possible decision to make. Somebody still has to establish that the included capability meets the requirement and can replace the existing service.

An included feature has to survive contact with the people using it. And one near-term item, narrowly scoped. Microsoft's August partner announcement says an October 1, 2026 uplift of 5% applies to annual term software subscriptions billed monthly through its cloud solution provider channel,

including products such as Windows Server and SQL Server. Existing subscriptions are affected at renewal on or after that date. This is a separate software subscription billing change. Don't paste it onto every Microsoft 365 line.

At the end, you should be able to say how much changed because of price, how much because of quantity or product mix, and how much because of the terms. If the explanation is still, Microsoft went up, keep working. Now Broadcom. VMware's published transition announcement explains the move away from selling

perpetual licenses towards subscription offerings, but separate a new purchasing model from the rights you already hold. Broadcom's own support article on perpetual licenses says support expiration doesn't revoke the underlying entitlement or automatically shut down the licensed environment.

Access to support and new updates is a separate matter. That's a meaningful distinction, and it doesn't make unsupported production infrastructure a sensible long-term plan. For VMware Cloud Foundation and In vSphere Foundation, Broadcom's current core

counting guidance uses physical processor cores, with a minimum of 16 per physical processor. It also provides a counting tool. Here's a small illustration using that rule. A host has two processors with 12 physical cores each, 24 actual cores, but 32 cores for the minimum licensing calculation.

That's the floor applied separately to each processor. Now suppose you delete a virtual machine. Have you reduced the licensed physical core count? No, you've changed a workload. To change the subscription quantity, you need a supported change to the licensed physical footprint,

reflected in the commercial arrangement. That means the infrastructure team belongs in this conversation before procurement asks for a discount. Can workloads be consolidated safely? Can a host genuinely leave the license to state? What happens to recovery capacity, resilience, and peak demand?

An idle host might be waste. It might also be why payroll survives a hardware failure. I would like us to settle that question before we unplug it. Get the required cores, the proposed bundle, any separately chargeable storage capacity, and the subscription term onto the same page.

Reconcile the vendor's count to a dated export you can reproduce. Where the quote uses a minimum or condition you can't find, ask for the applicable document and version. You are allowed to ask what a number means. Calmly. More than once. For a current example of an alternative being developed, look at Tottenham Hotspur.

In September, HPE and the Club announced an infrastructure modernization involving networking, compute, storage, and Morpheus software. HPE's announcement describes consolidating eight locations into two core environments. That's the supplier's announcement, so treat it as a described customer project,

not an independent savings study. I'm deliberately not turning it into a percentage you should expect. What matters for our discussion is the scope. A virtualization alternative lives inside an operating environment.

Backup, recovery, skills, application support, and the migration schedule all come with it. Your credible alternative needs that work behind it, even if you ultimately decide to stay. Let's take a quick break because this is where I want to connect the show to something you can actually use.

The Operational ITAM Store is my collection of practical operating resources for the work we discuss here, covering hardware, software, and the AI estate. For this episode, start with the software, SaaS, and cloud toolkit. So you can join us for the next one. All right, Oracle.

This is where counting fewer installations can leave you paying exactly the same bill. Oracle's Java SE Universal subscription uses an employee-based metric. Oracle's published definition includes your full-time, part-time, and temporary employees, plus the specified personnel of agents,

contractors, outsourcers, and consultants supporting your internal operations. The quantity isn't limited to the people who use Java. That last sentence changes the investigation. An installation inventory tells you where the runtime is.

It doesn't, by itself, calculate an employee-based subscription. Oracle's price list also has volume bands. $15 per employee per month is the starting band, not a universal rate. Get the applicable population and band right before you multiply anything.

Have procurement and legal validate how the definition applies to your organization, including the relevant entities and third parties. Then step back. Do these installations actually require the subscription being proposed? Java is an ecosystem. Oracle JDK is a particular distribution,

and the version, update, license, and use matter. JDK means Java Development Kit. An inventory entry that just says Java hasn't answered the commercial question yet. Here's the timely part. In its August 14th announcement, Oracle says updates

to Oracle JDK 21, beginning with the October 2026 critical patch update, are planned to use its Oracle Technology Network license. That change concerns subsequent updates. It doesn't retroactively replace the license attached to a release you already received under the no-fee terms.

The decision is about the exact release you're using and the rights for the update you intend to deploy. Oracle also identifies uses and existing entitlements that can cover those updates. So please don't translate the announcement into, "everyone with Java 21 must buy a subscription."

That statement skips the actual licensing analysis. And please don't make Stop Patching the savings plan. Bring the application owner and security team into a supported decision before the update goes out. You might retain Oracle support. You might move to an appropriate newer Oracle

release under its applicable terms. You might validate another distribution, such as Eclipse Temurin. Adoptium publishes Temurin's Availability Roadmap and directs organizations needing contractual support commitments to commercial providers.

Whatever route you choose, test the application, establish who supports it, and prove what changed in production. A successful download is the beginning of a migration plan. It's a fairly small beginning. For an employee-based subscription, removing some Oracle installations may reduce

technical dependency without reducing the required employee quantity. And removing the last installation doesn't, by itself, cancel an agreement or resolve past obligations. Follow the contract and retain the evidence.

This is the effective license position from Episode 3, applied before the purchase. Establish what you have, what rights apply, and where the gap actually is. Then ask what it costs to close that gap. Reversing that order lets the proposed sale define the problem.

Now, I promised we'd look at where the customer's side has changed the outcome. Microsoft's Teams commitments provide a concrete example, although the mechanism was regulatory action, not a buyer asking nicely at quarter end. Microsoft's September 2025 announcement describes the commitments agreed with

the European Commission. The resulting changes include suite options without Teams at lower prices and additional switching and discount protections for customers in the European Economic Area. Microsoft's current licensing FAQ says eligible customers there on multi-year

contracts can switch at their anniversary while retaining their discounts. Geography and purchasing channel matter, so have the account team identify the provision that applies to your agreement. For everybody else, the purchasing lesson still holds. Ask for the configuration

you actually need and compare it with the cost of the services you'll retain or add. A suite without teams is only a useful alternative if the replacement collaboration arrangement works and the combined cost makes sense. The precedent shows packaging can change. It doesn't guarantee your preferred concession.

That's why we distinguish a documented option from something we'd like the vendor to offer. Let's bring this back to your next renewal meeting. I wouldn't walk in with a dramatic speech about vendor behavior, I'd walk in with a short explanation of the quote and the evidence behind each disputed line. The speech can wait. It usually isn't getting cheaper while we rehearse it.

Here's a deliberately fictional example, using round numbers so you can check it while the coffee's still warm. Last year, a service cost $100,000. This year's opening quote is $150,000. The account team offers 20% off.

That's $120,000, which is still 20% more than last year for the assumed unchanged scope. Now suppose your verified requirement can be met by 800 units instead of the quoted 1,000, and the offer permits that reduction. At the same net rate of $120 per unit for the year, the recurring charge becomes $96,000.

Against the opening quote, you've avoided $54,000. Against last year's actual spend, the recurring reduction is $4,000, before any transition costs. Those are different comparisons. Finance deserves to know which one you're reporting. And that calculation only works because the fictional contract allows those units to come out.

A minimum commitment, an employee metric, or a physical core floor could change it. That's the point of doing the contract work before celebrating the spreadsheet. Keep the alternatives on the same time horizon. Include implementation, overlapping subscriptions, retained services, internal effort,

and the recurring cost after any introductory offer ends. Ask finance how to account for them. A cheaper first invoice can still buy a more expensive decision. My opinion, clearly labeled. A renewal team should be able to explain why staying

is the right decision as clearly as it can explain why leaving would be difficult. The counter-argument is fair. Sometimes the incumbent is operationally excellent, the alternative would consume scarce people, and the business needs stability more than a lower line item.

Fine. Put that rationale in the decision. Staying can be a good answer. It needs an owner and an explanation. What if you can't get the evidence before the deadline? Then describe the uncertainty honestly. Identify the disputed scope, the missing records, and the consequence of delay.

Ask whether a short extension or bridge arrangement is available, and compare its full cost in terms. You might not get one. Don't promise a migration date the delivery team hasn't accepted just to make the negotiation sound stronger.

This is why Episode 9's 18-month clock starts so early. Finding an alternative and being ready to use it are separate milestones. When you take the position to procurement, make the ask specific. Correct this quantity. Explain this charge. Price this configuration. Preserve this right.

Confirm when we can reduce the commitment. Some items are corrections to the bill. Others are changes you'd like negotiated. Label them accurately. An unused feature might be a reason to seek another bundle. It doesn't automatically

make a properly contracted charge invalid. And keep the tone civil. The person receiving the spreadsheet may be the person who helps get it fixed. Give them something they can take into their own organization without having to translate your frustration first.

One last step after the signature. Compare the first invoice with the final order. Did the corrected quantity reach the billing system? Did the agreed credit appear? Did the old subscription stop or have you accidentally funded both? Keep the signed change, the implementation evidence, and the invoice together.

Then check the following billing period if the correction depends on timing. That's how an agreed concession becomes an observed result. Until then, you have a promise in a document. A useful promise, hopefully, but I'd still like to see it on the bill.

Which brings us to today's principle, scrutiny. Scrutiny means being curious enough to examine the calculation, and disciplined enough to accept the answer when the evidence supports it. Sometimes your count is wrong. Sometimes the charge is valid.

Better to establish that while you're preparing than discover it in front of everyone who approved your position. The habit I want you to take away is this. Before you ask how much the vendor can take off, establish what belongs on the bill.

Class dismissed. Here's your homework. Give this about an hour, using the records you already have permission to access. Pick one upcoming renewal. Find the latest quote, the current agreement, the last invoice, and the best available quantity evidence.

On one page, explain the movement from the old total to the new total. Separate the rate change from the quantity change, then identify anything caused by packaging or terms. Pick one line you can't substantiate. Write the exact question that would resolve

it, who needs to answer, and the date you need the answer. Record the notice deadline separately from the renewal date. Date your page, put your name on it, and take it to the person who owns the decision. You can do that exercise without buying anything. If you want procedures and

tools to help make it repeatable, visit the Operational ITAM store at operationalitam.com slash store. Start with the renewal procedure, or the software, SaaS, and cloud toolkit. The product links are in the show notes. And with that, we're heading out of the grid. We've spent enough time looking

at how the machinery works. The next question is, who gets together and decides what to do about it? Episode 15 begins, The Decision Table. I promised we'd get to the control room and the operating model connecting ITAM and FinOps.

We're keeping that promise and bringing it into an actual working meeting. FinOps is the practice of managing technology value and cost through collaboration between technology, finance, and business teams. We'll put that practice beside asset management, procurement,

and the service owner. Then work through a decision they can't responsibly make alone. Who brings the usage evidence? Who validates the rights? Who accepts the operational risk? And who has the authority to say yes? We'll build a meeting that ends with an owner, an action, and a date.

I think we've all attended enough of the other kind. The case files are open too. One situation, one page. The constraint, what you did, and what happened. Remove company names and sensitive details before you send it through the website.

Send me one worth working, and I'll build an episode around it. I'm Bill Van Nort. This is the operational ITAM Podcast. Check the quantity, read the terms. Bring a position you can defend. I'll talk to you next week. Take care.