The Monday Brief | Week of June 15, 2026

Lot's of things have happened this past week while you were busy working. Let's catch you up.

Jun 15, 2026

Welcome back to Monday, again. New week, new chaos to feed the need for dopamine.

Last week was the first Monday Brief. This week we have fresh stories across all the categories that actually matter to people doing this work. No repeats, no filler. The Hormuz situation just broke wide open overnight. CLM is having an identity crisis. Your AI spend is already out of control and your CFO has not caught up yet. And if you have Microsoft, AWS, Oracle, or Salesforce renewals coming, there are specific moves you should be making right now.

Let us get into it.

THIS WEEK MATTERS. HERE’S WHY…

The next seven days are not a normal week…. I know, I know… there are no normal weeks for us but this is going to be a bit different.

There are three categories of things happening simultaneously: hard regulatory deadlines with no extensions, vendor fiscal year pressure you can exploit right now, and market signals worth paying attention to. Here is each one and what it actually means for the work you do.

JUNE 22 | 11:59 PM EDT USTR Forced Labor Tariff Hearing Request Deadline

This is the use-it-or-lose-it deadline. June 22nd is the last day to formally request to appear before the USTR Section 301 Committee at the public hearing on proposed forced labor tariffs covering 60 countries including China, India, Vietnam, Canada, Mexico, the UK, and the EU. If your organization sources from any of these economies and you want to make a formal argument for product exclusions or a reduced tariff rate, you must file under docket USTR-2026-0266 by 11:59 PM EDT tonight. Miss this deadline and you are limited to written comments only. The proposed tariffs are 10% for 15 trading partners and 12.5% for the remaining 45. They are not in effect yet, but this is the moment to influence the final outcome. If you have not already spoken to your trade counsel about this, today is the day.

JUNE 30 | MICROSOFT PRICE LOCK Last Day to Lock In Pre-Increase M365 Pricing

Microsoft 365 prices increase July 1st. If your organization has M365 licenses renewing anytime in the next 12 months, renewing before June 30th locks in current rates for another year. This is not a rumor. Microsoft has confirmed the change. The window closes in 15 days. If you have not initiated this conversation with your account team yet, you have one business week to get it done. Frontline worker licenses are seeing the steepest percentage increases. Larger M365 deployments will see the biggest dollar impact. This is straightforward math: renewal now at current price versus renewal later at a higher price. There is no procurement strategy here. It is just a deadline.

JUNE 30 | MICROSOFT FISCAL YEAR CLOSE Maximum Quota Pressure on Microsoft Account Teams

June 30th is also the close of Microsoft’s fiscal year, which means every Microsoft account executive is in their highest-pressure 15 days of the year. This creates a real negotiating window that exists independently of the M365 price increase. Microsoft sales teams have end-of-year targets to hit. Buyers who are willing to close a deal before June 30th have leverage that simply will not exist on July 1st. This applies to Azure, Copilot, Dynamics, and the EA broadly, not just M365. If you have any Microsoft negotiation in progress or any renewal within the next six months, initiating or accelerating that conversation this week is not optional. It is the right procurement move.

JUNE 30 | FAR OVERHAUL PHASE 1 Federal Contracting Rule Changes Land

Phase 1 of the Revolutionary FAR Overhaul drops June 30th. The biggest change already in motion is the Executive Order directing all federal agencies to default to fixed-price contracts. OMB was required to issue implementation guidance to agencies by June 14th. The agencies themselves have until July 29th to review their 10 largest non-fixed-price contracts and begin renegotiating them to fixed-price or performance-based terms. If you are a supplier to the federal government, or a supplier to a supplier, this date starts the clock on renegotiation conversations you did not budget for. If you have time and materials contracts or cost-plus arrangements with federal agencies, now is the moment to understand your rights before a contracting officer comes to you with a modification request.

JUNE 30 | GENERAL MILLS FISCAL YEAR CLOSE A Large Buyer Finishing Their Year

General Mills closes its fiscal year on June 30th. This matters for anyone who supplies to them. Large companies in cost-control mode at fiscal year end slow approvals, tighten spend review, and sometimes push new purchase decisions to the next fiscal year. If you have open quotes, pending contract renewals, or new business discussions with General Mills, expect their procurement team to be heads-down right now. Timing your outreach for early July, when their new fiscal year begins with fresh budgets and renewed appetite to commit, is smarter than trying to close something in the next two weeks.

ALREADY IN EFFECT | JUNE 8 Section 232 Tariff Reductions on HVAC, Agricultural, and Industrial Equipment

This one already happened and most procurement teams have not caught up with it. On June 8th, a White House proclamation reduced Section 232 tariffs from 25% to 15% on agricultural equipment, certain residential HVAC systems and components, and mobile industrial equipment including bulldozers and forklifts imported from select countries. These reductions run through December 31, 2027. The category list is specific and requires HTS code-level review to confirm applicability. If you have any indirect spend in these categories, pull your customs entries from June 8th forward and verify you are being assessed at the correct rate. Overpayment on tariffs is recoverable but requires prompt action. If you are not sure whether your products qualify, your customs broker can confirm against the updated Annex III and Annex I-C product lists.

WHO ACTUALLY CLOSES JUNE 30

There are a few vendors worth calling attention to that will close their books for the year on June 30 and that matters if you are looking to renew a contract.

Microsoft
General Mills
Micron Technology

Despite a post I saw on LinkedIn the other day, Oracle closed May 31st. Their Q4 is already over.

Nike closed May 31st.

FedEx just changed its fiscal year-end to December 31st, effective this month.

Accenture closes August 31st.

Salesforce closes January 31st.

AWS closes December 31st.

The reason this matters: vendor fiscal year timing is one of the few structural negotiating levers that is entirely predictable. But it only works if you know the actual date. Applying Q4 urgency pressure to a vendor whose Q4 ended three weeks ago is not a strategy. It is a waste of a conversation.

The vendors with real urgency on the table right now are Microsoft, because their fiscal year and their M365 price increase both land June 30th. Use that window. For everyone else, do the calendar math before you walk into the room.

Source: Microsoft Q3 FY2026 Earnings Call: Fiscal Year Guidance | Oracle FY2026 Annual Results, June 10, 2026 | Accenture Investor FAQ: Fiscal Year End August 31

GLOBAL SUPPLY CHAIN

The Strait of Hormuz Just Reopened. Your Contracts Are Still Broken.

This one landed yesterday and it is big. On June 14th, President Trump announced a peace deal with Iran is “now complete” and ordered an immediate end to the US naval blockade of Iranian ports in exchange for toll-free shipping through the Strait of Hormuz. Iran’s deputy Foreign Minister confirmed the agreement on Sunday. The G7 is discussing long-term implementation in Evian, France today.

To understand why this matters for us procurement professionals specifically, you need to understand what the last three and a half months actually did to your supply base.

The Strait has been effectively closed since the US and Israel launched strikes on Iran on February 28th. It carries roughly 20% of global oil trade. When it closed, crude oil and fertilizer prices spiked sharply, maritime insurance premiums went through the roof, hundreds of tankers were stranded or rerouted around the Cape of Good Hope, and energy feedstock costs hit plastics, chemicals, and packaging up and down the indirect supply chain. So, frankly… it’s caused a landslide of chaos that hit just about everything we touch.

Here is the procurement reality even now that a deal is struck: your contracts did not fix themselves overnight. If you have force majeure claims in flight, they do not automatically unwind. If your supplier repriced based on energy cost escalation, that new price is now your baseline unless your contract has a de-escalation mechanism. If you extended lead times and changed supplier commitments to compensate, those changes need to be formally addressed.

The reopening of the Strait is good news for markets and your 401k . It is not a reason to stop the contract housekeeping that the last three months forced onto your desk. If anything, it is the moment to lock in favorable terms before the urgency fades and your counterparties remember they have leverage again.

The G7’s stated goal is a “lasting reopening” with full freedom of navigation. Macron confirmed that today’s summit will address long-term Hormuz governance. That is a 60 to 90 day negotiation window at minimum. Plan accordingly.

Source: Al Jazeera: US-Iran Ceasefire Deal, June 14, 2026 | Axios: US-Iran Framework Agreement, June 14, 2026 | CSIS: The Strait of Hormuz in 8 Charts, June 11, 2026

CONTRACTING BEST PRACTICES

You Do Not Know How to Contract for an AI That Acts on Your Behalf. Nobody Does.

For two decades, software contracts were about access. You paid per seat. You got uptime guarantees and a liability cap. The software did not do anything unless a human touched it. That model made legal risk manageable because humans were still the ones pulling the trigger.

Agentic AI just blew that model up. PYMNTS put the problem clearly: these systems approve refunds, reconcile invoices, negotiate with suppliers, trigger payments, and move data across systems. They do not wait for a human but your existing SaaS contract language was written for software that waited.

In May, LinkSquares launched what it calls the first all-agentic CLM platform, designed to draft, redline, and manage contracts autonomously… which is scary on so many levels. Microsoft’s Copilot Legal Agent for Word is doing clause-by-clause contract review. CLOC 2026 made clear that the features CLMs have charged premium pricing for are being absorbed by horizontal AI platforms that already live inside your document workflows.

If you are buying an AI tool that takes autonomous action inside your procurement or contracting process, your standard SaaS agreement is probably the wrong contract. You need indemnification language that accounts for autonomous decisions, clear definitions of what the system is authorized to do without human approval, audit trail requirements, and liability terms that reflect who bears the risk when the agent makes a bad call. Your legal team and your CLM vendor are almost certainly not aligned on this yet.

The practical move is to build an internal list of every AI tool in your stack that takes autonomous action… not just your CLM. Your AP automation. Your sourcing bots. Your intake platforms. Then ask one question about each: when this system acts without a human approving the specific action, who is liable for the outcome? If you cannot answer that from your current contract, you have work to do.

Source: PYMNTS: Contracting for Agentic AI, February 2026 | LinkSquares PR Newswire: All-Agentic CLM Launch, May 5, 2026 | Pramata: CLOC 2026 Recap, June 2026 | PwC: Agentic AI in Procurement, June 2026

CONTRACT MANAGEMENT BEST PRACTICES

You Are Losing 11% of Contract Value After Signature. Stop Pretending Otherwise.

The 2026 Contracting Benchmark Report, cited by Ironclad, puts a number on something procurement and contracting teams know in their gut but rarely quantify: organizations lose an average of 11% of contract value after signature through missed obligations, revenue leakage, and costs nobody is watching.

That number is not a technology problem. It is a process and attention problem. Most procurement teams negotiate hard to get a contract signed and then treat it like a filing event. Meanwhile, the SLA credits your vendor owes you go unclaimed. The volume discounts you negotiated only apply if you actually consolidate volume. The benchmarking rights that let you challenge pricing every 18 months sit unused because nobody remembered they existed.

The highest ROI thing most contract management teams can do right now costs nothing. Pull your top 20 contracts by spend value. Read the post-signature obligations section of each one. List every right, credit, or discount that requires your team to take affirmative action to use. Then check when you last did any of it. …I’ll wait.

The same benchmark data notes that 95% of organizations are now using AI in some form for contract lifecycle management, but only 38% have reached full integration maturity. Which means most organizations have AI that can find the clause, but not a process that ensures anyone acts on it. Buying the CLM was the easy part. Building the post-signature discipline is the actual job.

Source: Ironclad: 2026 Contracting Benchmark Report | Procurement Magazine: AI and CLM Webinar Findings, June 9, 2026

The Token Bill Just Arrived. Corporate America Is Doing a Double Take.

Here is the story that has been building quietly since January and finally broke into the mainstream this month.

TechCrunch reported on June 5th: Uber blew through its entire 2026 AI coding budget by April.

Microsoft revoked its developers’ Claude Code licenses months after enabling them over cost.

A Priceline employee told TechCrunch that a routine Cursor contract renewal came back 4 to 5 times more expensive.

Let’s all be shocked….

The headline number that should make every procurement and finance leader stop scrolling: one company reportedly racked up a $500 million AI bill after failing to enact usage caps for employees. One. Company. Half a billion dollars. Per Elvex’s enterprise token cost analysis, a healthcare enterprise consumed 1 trillion tokens over six months, generating over $6 million in unplanned costs before the finance team even understood what was driving it.

OpenAI CEO Sam Altman said it plainly on stage: “People are really saying, you know, it’s kind of a meme now, but ‘My company spent my entire 2026 budget in Q1. Can you make this more efficient?’ That went from, at the beginning of this year, an issue that never came up, to all of a sudden, a huge issue.”

The structural problem is this: per-token prices have actually fallen. But agentic AI tools burn tokens in chains, not single queries. One autonomous agent completing a sourcing task can fire 40 sequential model calls where a chatbot would fire one. Token consumption scales geometrically with agentic adoption, not linearly. Your 2026 AI budget was probably built on 2025 consumption math. That math is outdated and now wrong.

This is what happens when we plan for something we don’t really understand yet….

If you have agentic AI tools deployed and your finance team is not receiving weekly consumption reports broken down by tool, team, and use case, you are flying blind at altitude. The governance muscle for AI spend is not a future capability. It is a now capability. Token budgets, usage caps per team, and approval workflows for new AI tool rollouts belong in your indirect procurement policy today.

J.R. Storment, executive director of the FinOps Foundation, said companies started calling in April saying they were already three times over their entire 2026 token budget. The whole conversation shifted, in his words, from “tokenmaxxing and ‘go fast’“ to “we need guardrails, how do we control this.” That is the moment indirect procurement walks back into the room. Someone has to own this spend category. It should be you.

Source: TechCrunch: The Token Bill Comes Due, June 5, 2026 | Yahoo Finance / Axios: Companies Evaluate Aggressive AI Spending | Tom’s Hardware: Sam Altman on AI Token Costs, June 2026 | Elvex: AI Token Cost Enterprise Budget Control

VENDOR NEGOTIATION TIPS

Contracts Coming Up? Here Is What to Know About the Vendors You Actually Deal With.

This week hands you specific leverage with four of the biggest indirect spend vendors most of us deal with. Here is what is happening with each of them and how to use it.

MICROSOFT

Microsoft 365 prices increase July 1, 2026. If you renew before June 30, you can lock in current rates for one year. That is 15 days away. If your renewal is anywhere in the next 12 months, this is worth a conversation with your account team right now.

Separately, GitHub Copilot just moved from per-seat to usage-based billing with AI credit overages. This means your GitHub Copilot costs now have a variable tail that sits on your Azure bill separately from your EA. If you have developers using Copilot Studio or building agents, a single M365 Copilot license at $30 per month can generate $85 or more in additional Azure consumption on top depending on agent traffic. Those costs show up in two different places. You need to look at both.

Tip 1: Microsoft’s fiscal year closes June 30. That is this month. Q4 is the highest-pressure quarter for their sales teams. Buyers who time negotiations to this window consistently see better outcomes. If you are anywhere near a Microsoft renewal, initiate the conversation this week, not next month.

Tip 2: Negotiate Unified Support separately from your EA. Vendr data shows buyers who negotiate support independently reduce those costs by 15 to 30%. It is priced as a percentage of your total Microsoft spend, not based on what you actually use. There is room there.

Tip 3: Before June 30, run a license audit. Copilot Chat enhancements are being added to multiple M365 suites starting this month, which means more users will touch AI features by default. Make sure you are not paying for licenses that are not being used before locking in another year at those quantities.

Source: AppDirect: Microsoft 365 Price Change Advisory, June 2026 | LicenseQ: Microsoft Licensing Update June 2026 | SAMexpert: Microsoft AI Costs Licensing vs Azure

AWS

AWS’s Enterprise Discount Program has been rebranded as the Private Pricing Agreement but the commercial structure is identical. AWS’s fiscal year closes December 31, which means you are currently in the middle of the lowest-pressure quarter of their year. That cuts both ways: AWS is less motivated to concede right now, but you are not in a rushed position either. Use Q2 and Q3 to build your leverage case. Do not wait until November.

The AI spend crisis described above creates a specific AWS angle. If you have been over-consuming AI services on AWS and want to renegotiate your commitment, the 60th to 70th percentile of expected consumption is the right sizing posture for your EDP. Optimistic sizing at the 90th percentile creates shortfall risk that AWS will hold against you. Optimize your workloads before you commit, not after.

Tip 1: AWS support is negotiable even though they present it as fixed. Enterprise Support is a revenue line for AWS and is included in EDP negotiations at accounts with meaningful leverage. Always ask. Bundling support into your EDP conversation can save 12 to 18% on the support tier versus negotiating it separately.

Tip 2: Rollover provisions are not in AWS’s default PPA template but are routinely available at signing for buyers who raise them. A rollover converts unused first-year commitment into second-year capacity. If your consumption is uncertain, this provision is worth asking for explicitly.

Tip 3: At $5 million or more in annual AWS spend, mentioning Azure or GCP benchmarks opens doors. Get a real competing quote before your negotiation, not a hypothetical. A documented alternative changes the conversation.

Source: Redress Compliance: AWS EDP Negotiation Guide 2026 | The Negotiation Experts: AWS EDP Discount Tiers and Tactics

ORACLE

Oracle is the vendor most procurement teams dread, and for good reason. They audit aggressively, their licensing rules are intentionally complex, and they have a long institutional memory for customers who tried to walk away. But there are real levers.

The most important thing Oracle does not want you to know is that cross-cloud pricing benchmarks are your most effective negotiation tool. If you are negotiating Oracle Cloud Infrastructure or Oracle SaaS, get a detailed cost estimate from AWS or Azure for equivalent services first. A documented statement that says your analysis shows running equivalent workloads on AWS costs $X and Oracle’s quote is $Y creates a conversation that vague complaints about being overpriced do not.

Tip 1: For Oracle applications like Fusion ERP or HCM, obtain competing proposals from SAP S/4HANA or Workday before you negotiate. You do not have to intend to switch. You need to credibly demonstrate you evaluated alternatives. Oracle responds to documented competitive pressure far more than to verbal negotiating positions.

Tip 2: Oracle’s fiscal year ends May 31. You just missed the highest-leverage window, which means Oracle account teams have already made their numbers and have less urgency to deal right now. Use Q1 of their fiscal year (June to August) to set the terms of a Q4 negotiation, not to close one.

Tip 3: If you are a cloud customer, watch your Processor License Set definitions carefully. Oracle has been aggressive about claiming that virtualized environments require additional licensing. Get written confirmation of your license positions before any infrastructure changes, not after.

Source: Redress Compliance: Oracle Pricing Benchmarks and Negotiation Leverage, May 2026

SALESFORCE

Salesforce’s fiscal year closes January 31, which means you are entering the period when their Q1 numbers matter and the pressure to sell is moderate but real. The current environment also gives you a specific angle: Salesforce’s Agentforce product is priced at $2 per agent action resolution. That is a consumption model sitting on top of your existing seat-based contracts. Before you add Agentforce to your estate, understand exactly how actions are metered.

The broader Salesforce negotiation dynamic is that the biggest discounts come at the point of most leverage, which is the beginning of the relationship or a major expansion, not renewal. At renewal, your best moves are usage-based: document what you actually consumed versus what you paid for, and build your negotiating position from that data.

Tip 1: Consolidate your Salesforce portfolio into a single negotiation event. If you have Sales Cloud, Service Cloud, Marketing Cloud, Tableau, MuleSoft, and Slack all under different agreements and different account reps, you are losing aggregation leverage. Ask for a single point of contact and a master agreement.

Tip 2: Marketing Cloud renewals are usage negotiations, not seat negotiations. Contact volume and super messages drive the bill. Measure your actual consumption against your contracted tier before you renew. Unused credits in your current contract are your strongest negotiating data point.

Tip 3: For AI products like Agentforce and Einstein, ask for a pilot period with capped consumption before signing a volume commitment. The companies blowing their AI budgets this quarter are the ones who committed to volume before they had real consumption data. Do not be that company.

Source: Everest Group: Nine Tactics for Salesforce Contract Negotiation | Redress Compliance: Salesforce Marketing Cloud Negotiation, June 2026 | Zylo: Salesforce Enterprise License Agreement Guide

DATES TO PUT IN YOUR CALENDAR

Today, June 15 G7 Summit in Evian: Long-term Hormuz governance and nuclear framework talks

June 22 USTR hearing request deadline on Section 301 forced labor tariffs

June 29 Global Procurement Awards AND Global Supply Chain Awards entries close

June 30 Microsoft M365 price lock deadline AND FAR Overhaul Phase 1 changes land

July 6 Written comments close on Section 301 forced labor tariff proposals

July 7 USTR public hearing on forced labor tariffs

July 29 Agency deadline to renegotiate top 10 non-fixed-price federal contracts

That is your week.

The Hormuz deal is the headline but the contract cleanup it requires is the actual work. Agentic AI contracting is the slow-moving problem that will surprise everyone who ignored it. DOGE’s downstream effect on your indirect vendors is underappreciated. Post-signature value leakage is the thing most teams know is real and almost none have a process to address. The token bill crisis is what happens when procurement is not in the room when AI tools get deployed. And the vendor tips section exists because knowing the vendor’s calendar and their pain points is just as important as knowing your own.

Drop a comment.

Tell me where you disagree. Procurement deserves conversations that are honest, not comfortable.

SOURCES

1. Al Jazeera: US-Iran Ceasefire Deal, June 14, 2026

2. Axios: US-Iran Framework Agreement, June 14, 2026

3. CSIS: The Strait of Hormuz in 8 Charts, June 11, 2026

4. PYMNTS: Contracting for Agentic AI Looks Like Outsourcing, February 2026

5. LinkSquares PR Newswire: All-Agentic CLM Launch, May 5, 2026

6. Pramata: CLOC 2026 Recap on Contract Intelligence, June 2026

7. PwC: Agentic AI in Procurement, June 2026

8. Fed-Spend: DOGE Spending Cuts by Agency Tracker, March 2026

9. PBS NewsHour: 40% of DOGE Cancellations Produce No Savings