The Monday Brief | Week of June 29, 2026

Things you should know to be good at your job this week.

Jun 29, 2026

Yes, I missed last Monday. I know. In my defense, I spent that week doing the exact same thing you did: trying to catch up on two weeks of procurement news while someone scheduled a meeting over my lunch and my phone was blowing up about a contract that should have closed in April. We are procurement people. Busy is our resting state. So, we are combining two weeks into one. Think of it as a value pack. Or a punishment. Depends on how your month is going.

TRADE POLICY

USMCA Review Starts Tomorrow. If You Source Anything From Canada or Mexico… This Is Your Problem.

Here is the plain version of what is happening. The US, Canada, and Mexico built a mandatory review into their trade agreement from the start. That review officially opens July 1st. The three countries now have to formally decide whether to extend USMCA for another 16 years or not. If they do not reach consensus, the agreement shifts to annual reviews until 2036. It does not expire tomorrow. But the uncertainty it creates is real, immediate, and expensive.

Why does this affect your week-to-week job? Because roughly $1.8 trillion in annual North American trade flows under USMCA. That is IT services from Canadian firms, marketing spend with Mexican agencies, packaging and components manufactured in both countries, staffing arrangements, logistics, chemicals, and practically every category of indirect spend that you have ever sourced from a North American supplier. USMCA compliance is what exempts those imports from the tariff stack. The 83.9% of Canadian and Mexican imports currently claiming USMCA exemption are doing so because it is the difference between paying zero additional tariffs and paying 10 to 35% on top of base rates.

A clean 16-year extension is unlikely. CSIS rates it as the least probable outcome. The more realistic scenario is a prolonged negotiation that stretches into late 2026 or 2027 while the core agreement stays in force. That sounds like a win, except that protracted negotiations mean rules of origin could tighten mid-negotiation, sector-specific concessions could disrupt specific supply lanes, and investment decisions that depend on North American sourcing stability get deferred. Your CFO is not going to green-light a 10-year supplier commitment while the trade framework governing that commitment is in active renegotiation.

Practical Move

Pull your top indirect and direct spend categories that have Canadian or Mexican suppliers. Ask your customs broker or trade counsel which of those are currently operating under USMCA preference claims. That list is your exposure map. You are not trying to panic. You are trying to not be the person who finds out in Q3 that a rule-of-origin change reclassified their most important supplier’s products.

Source: Convera: USMCA 2026 Review Analysis | CSIS: Six Scenarios for USMCA’s Future | Tax Foundation: USMCA Tariff Impact | BSI: USMCA Review What You Need to Know

AI + CONTRACTING

The Government Just Wrote AI Governance Into Contracts. Commercial Contracts Are Next. Here Is What It Means.

On June 17th, GSA published a proposed contract clause that will eventually land in every federal contract where an AI tool touches government data. GSAR clause 552.239-7001 requires contractors to disclose all AI systems being used to perform work within 120 days of starting a contract, report any data incident within 72 hours, and prohibit using government data to train or improve AI models without explicit authorization. It also requires prime contractors to flow those obligations down to their subcontractors and AI vendors.

I know what you are thinking. Government contracts are their own world. What does this have to do with me? Two things.

First, if your company sells anything to the federal government, or if any of your indirect suppliers do, this clause will eventually land in your contracts. The GSA schedule covers practically every professional services category. IT services, consulting, staffing, facilities management, and marketing are all on the schedule. When this clause gets finalized and applied to GSA vehicles, it flows to every contractor on those vehicles, including the ones you are buying from today.

Second, and this is the bigger story: commercial contracting follows government contracting. It’s just how things work. Liability standards, data protection requirements, cybersecurity clauses, and performance obligations that started in federal acquisition have found their way into commercial SaaS agreements, professional services contracts, and outsourcing agreements over the past two decades. The government is now writing the first detailed, enforceable AI governance language in contracts. Your procurement and legal teams should be reading this clause today, because it is a preview of what your enterprise clients are going to start demanding in your own contracts within the next 12 to 24 months.

The clause has a comment window open through August 3rd. If your organization has federal contracts or significant AI in your commercial delivery chain, submitting comments is a “real” opportunity to shape how this language develops before it becomes final. GSA is also holding a public listening session on July 14th. Registration closes July 3rd. This is not a theoretical governance exercise. This is the rulemaking that becomes the standard clause language in contracts you will be signing in 2027.

Source: Federal Register: GSAR LLM Safeguarding Clause, June 17, 2026 | Singularity Capital Advisors: GSA AI Rule, June 2026 | Mondaq: GSA LLM Rewrite Analysis, June 23, 2026

TARIFFS + INDIRECT SOURCING

That $800 Duty-Free Threshold You Forgot About? The Government Just Made Sure You Cannot Get It Back.

The de minimis exemption is the rule that let packages valued under $800 enter the US without paying duties. Vendors used it heavily. Procurement teams relied on it for sample shipments, low-value MRO, lab supplies, and tail spend. The current administration suspended it. Courts pushed back, ruling that the IEEPA authority used to suspend it was unconstitutional.

Here is what happened on June 23rd: CBP published two new proposed rules using a completely different legal authority, specifically the Tariff Act of 1930, to justify keeping de minimis suspended permanently. The IEEPA-based suspension was vulnerable to the same legal challenge that killed the broader tariff regime. The Tariff Act of 1930 is not. CBP is basically inoculating the de minimis suspension against the court challenge that was most likely to work.

Here is what this means in plain English. If your sourcing model assumed the de minimis exemption would come back when the courts sorted things out, that assumption needs to be retired. Penn Wharton’s June 16th tariff rate update confirms the broader tariff landscape has settled at an average effective rate of 7% as of April. That is the floor. Plan from it.

PRACTICAL MOVE

If you have tail spend, samples, catalog purchases, or indirect supplier shipments that were coming in under the $800 threshold, you have been paying duties on them since August 2025 whether you realized it or not. Pull your customs data. Look for entries that were previously de minimis exempt and are now being assessed duties. Model that cost into your supplier pricing. And if any of your contracts have duty pass-through language that predates August 2025, check whether those clauses now entitle your supplier to pass de minimis duties to you.

Source: RVIA: Latest Tariff Developments, June 25, 2026 | Penn Wharton: Effective Tariff Rates June 16, 2026

INDIRECT AI SPEND

70% of Organizations Have Nobody In Charge of their SaaS Spend. Is One of Them Yours?

Let us start with the number that should be uncomfortable. Zylo’s 2026 SaaS Management Index found that only 31% of organizations have clearly defined ownership between FinOps, IT, and procurement for SaaS spend. That means at roughly 7 out of 10 companies, when something goes wrong with software costs, three departments all point at each other. Sound familiar to you, it does to me…

The average organization manages 305 SaaS applications and spends $55.7 million annually. Total SaaS spend rose 8% year over year. AI-native app spending inside large enterprises is up 393%. The average company adds nine new applications every month. And 46% of the applications in the average portfolio carry a poor or low security risk score, although most companies aren’t risk scoring at all. That last number is not a security team problem. It is a procurement problem. Every one of those applications was purchased by someone using a company card or a purchase order. Somebody approved that spend.

Here is what I want you to do this week.

Pull your corporate card data for any subscription charges. Filter for anything with the words AI, GPT, Copilot, Claude, Cursor, or Agent in the vendor name. Count them. Then check how many of those you can actually account for in a formal purchase record with a signed agreement and a documented business case. The gap between those two numbers is your shadow AI exposure. I guarantee it is larger than you think.

One specific development worth noting: Salesforce announced on June 15th that it is acquiring Fin, formerly known as Intercom, for $3.6 billion. Fin resolves an average of 76% of customer support volume end-to-end without human escalation. This is being folded into Agentforce. What does that mean for procurement? The next time your Salesforce account executive sits down with you, they are going to have a fully autonomous customer service agent to sell you. That agent runs on per-action consumption pricing. Given what we have all watched happen with AI token costs this year, that is a model you want to pilot with a spending cap, not commit to at scale.

Source: Zylo: 2026 SaaS Statistics and Trends | Tropic: 2026 SaaS Procurement Predictions | TechnologyChecker: Salesforce Acquires Fin, June 15, 2026

DIRECT + SUPPLY CHAIN

DRAM Shortages Through 2030. PCB Lead Times Up. This Is Not a Cycle. It Is the New Baseline.

For everyone on the direct sourcing and supply chain side, here is the honest state of play. The Hormuz reopening helped freight. It did not fix materials.

Supplyframe’s supply chain intelligence published this week identified two structural problems that will not resolve this year or next. First, printed circuit board supply shortages created by the Iran conflict are persistent. Lead times are elevated through 2026 with only modest improvement projected in early 2027. Pricing is inflexible. If you have any electronics manufacturing, industrial controls, or hardware procurement in your category portfolio, your Q4 and Q1 numbers are going to reflect this whether your contracts acknowledge it or not.

Second, and this is the one that gets underreported: AI infrastructure is competing with your direct materials for the same components. DRAM, specialized resins, rare earth materials, and advanced semiconductors are all being consumed by data center buildout at a pace the supply chain was not designed to support. Industry experts are projecting the DRAM shortage lasts until 2030. Not 2026. Not 2027. 2030. If you are running just-in-time inventory models on components that sit in that supply chain, you need to have a frank conversation with your operations team about safety stock and dual sourcing.

The Thomson Reuters 2026 Global Trade Report found that 39% of organizations are now absorbing tariff costs rather than passing them to customers, up from 13% last year. If your suppliers are absorbing right now, they are building up cost pressure that has to go somewhere. It typically comes out in one of three places: the next contract renewal, a service level reduction, or a force majeure claim the moment they get one. Watch your key direct suppliers’ financial health the same way you watch their delivery performance.

Source: Supplyframe: 3 Biggest Supply Chain Risks in 2026 | Thomson Reuters: 2026 Supply Chain Challenge Report | Deloitte: 2026 Manufacturing Industry Outlook

CONTRACTING TIPS + CONTRACT REVIEW GUIDE

The Contract Review Section Nobody Gave You When You Started. You Are Welcome.

I am a attorney by training and a procurement guy by accident. I have reviewed and negotiated more contracts than I can count across technology, professional services, logistics, staffing, and manufacturing and the single most consistent problem I see across procurement organizations is not that people do not care about their contracts. It is that nobody gave them a framework for what to actually look for or, in some cases, if they did the framework is from 2001.

So here it is. Not a legal treatise. A practitioner’s guide. The questions to ask, the things to look for, and right now especially, what to do about AI language in contracts.

(I’m working on a full Contract Review Framework in my “free time.”)

BEFORE YOU SIGN ANYTHING: THE QUESTIONS MOST PEOPLE SKIP

Most contract review processes start at redlining clauses. They should start at understanding the actual commercial deal… I’ve talked about this before online… go read it. Before you open a contract to review, you should be able to answer these questions clearly:

What exactly are we buying and how is it measured? If you cannot define the deliverable in one sentence, the contract probably cannot either. Vague scope is how you end up in a dispute 18 months later about whether something was in scope.
What is the exit? How do you get out of this agreement if the vendor underperforms, gets acquired, raises prices dramatically, or you simply do not need the service anymore? Termination for convenience, notice periods, and automatic renewal clauses are where procurement value gets silently destroyed.
Who owns what was created? If a vendor is building something for you, developing code, creating content, designing a process, or producing deliverables of any kind, IP ownership needs to be explicit. Default contract law varies by state and by what was actually paid for. Do not assume you own it because you paid for it.
Where does liability actually sit? Most standard vendor agreements cap the vendor’s liability at one year of fees paid. On a $10 million annual contract, that is $10 million. On a $500K annual contract where a data breach causes $50 million in downstream damage, that cap is not going to cover you. Know what you are signing.
What data are you handing over and what can they do with it? Every SaaS agreement, every managed services contract, every staffing arrangement involves data moving somewhere. Understand what data leaves your environment, where it goes, who can access it, and whether the vendor can use it for anything beyond performing your contract.

THE AI LANGUAGE SECTION: WHAT TO ASK FOR RIGHT NOW

This is the most time-sensitive part of this section. Your existing vendor contracts almost certainly say nothing about AI. They were drafted before AI tools were a standard part of service delivery. That silence is now a liability.

Here is the scenario that keeps us attorneys up at night. Your vendor is using an AI tool to deliver your contract. The AI makes an error. The error causes you financial harm. You go to enforce your contract. Your contract says nothing about AI. The vendor argues it just used commercially reasonable tools to perform the work. You argue the AI output constitutes a deliverable under the contract. The indemnification clause was written for software bugs, not autonomous decision-making. Nothing about this is quick or cheap.

The four AI questions every contract negotiation needs right now:

Is the vendor using AI tools to perform any part of this contract? If yes, which ones? This should be a mandatory disclosure, not a voluntary one. Require a schedule of AI systems used in contract performance and require written notice before any changes to that schedule.
What data will be processed by those AI tools? Specifically: will any data you provide, including prompts, inputs, outputs, or metadata, be used to train, fine-tune, or improve the vendor’s AI models? The answer should be no. Get that in writing. Many vendor AI tools have model improvement clauses buried in their terms of service. Your contract should supersede those.
Who is liable when the AI makes a decision that causes harm? The vendor’s position will be that AI outputs are tools, not deliverables, and liability sits with the human who acted on them. Your position should be that the vendor is responsible for the quality and accuracy of AI-assisted work product delivered under the contract. These are reconcilable positions. But you have to have the conversation during formation, not after a problem.
What happens when the AI tool changes? Model updates, vendor changes, architecture shifts, and capability degradations can all change the quality of AI-assisted deliverables without triggering a contract modification. Require notification of material changes to AI systems used in contract performance and include a right to re-evaluate SLAs if those changes affect output quality.

A practical tip from someone who has been in this room

The fastest way to get AI language into a contract with a vendor who is resisting is to frame it not as a limitation but as a disclosure requirement. Most vendors will agree to disclose what AI tools they use, agree not to train on your data, and agree to notify you of material AI system changes. That is not a radical ask. It is basic transparency. And it gives you a foundation to build on when the industry eventually standardizes this language.

One more thing worth saying. The GSA clause we covered in Story 2 defines government data broadly to include user prompts and query outputs. That is more expansive than most commercial contracts contemplate. Before you dismiss it as a government contracts issue, ask yourself: how would you feel if your most sensitive business data ended up in a vendor’s training set? That is the risk the clause is designed to prevent. It is not a bad model to adapt for your own vendor agreements.

IT SOURCING + INDIRECT HARDWARE

Your IT Hardware Budget Was Built for a Memory Market That No Longer Exists.

Gartner’s research director said it plainly: “The speed at which the memory pricing has increased has shocked everybody.” That is not a vendor trying to upsell you. That is an analyst describing what is happening to every IT hardware budget on the planet right now.

Here is the situation in plain terms. The three companies that control 95% of global DRAM production, Samsung, SK Hynix, and Micron, have made a rational business decision to redirect their manufacturing capacity toward high-bandwidth memory for AI infrastructure. HBM is more profitable. AI customers pay more and commit earlier. IDC confirmed it: every wafer allocated to an HBM stack for an AI GPU is a wafer denied to the conventional DRAM used in your enterprise servers, laptops, and storage systems. This is a zero-sum game and right now the AI buildout is winning.

The numbers are not subtle. TrendForce reported conventional DRAM contract prices rose 90 to 95% quarter over quarter in Q1 2026. The largest quarterly increase on record. Server DRAM is up more than 60% quarter over quarter as cloud providers lock in capacity through long-term agreements. HP reported in its Q1 earnings call that memory now accounts for 35% of the cost to build a PC, up from 15 to 18% previously. One component. 35% of the build cost.

Here is the number that should make you stop scrolling. DDR4 spot prices have now hit $2.10 per gigabit, which exceeds advanced HBM3e at $1.70 per gigabit. The old commodity memory costs more than the cutting-edge AI memory. When the legacy product is more expensive than the premium product, you are not in a normal supply cycle. You are in a structurally distorted market and your budget assumptions are probably wrong.

I know… it’s a lot of numbers that really mean much other than costs went up but there’s more…

WHY THIS HITS IT SOURCING SPECIFICALLY RIGHT NOW

Two problems are compounding at the same time and they are landing on the same desk.

Problem one: the Windows 10 end-of-life in October 2025 triggered enterprise refresh cycles that are now running directly into the shortage. Your organization may have already committed to a PC refresh wave this year with a budget built on Q3 2025 hardware pricing. Lenovo, Dell, HP, Acer, and ASUS have all warned of 15 to 20% PC price increases for 2026, with some reports noting increases as high as 30% as the shortage deepens. The refresh budget your team approved six months ago is likely already underwater. This is not a small variance. It is a material budget gap that needs to be in front of your finance team now, not at year-end review.

Problem two: lead times for larger DRAM orders have extended beyond 40 weeks. Not four weeks. Forty weeks. That makes many standard configurations unworkable for fiscal year 2026 planning. If you have a data center expansion, server refresh, or infrastructure project planned for Q3 or Q4 of this year, the memory you need to complete it may simply not be available on your timeline regardless of what you are willing to pay. That is not a price problem. That is an availability problem, and price alone cannot solve it.

STRUCTURAL, NOT CYCLICAL. THE DISTINCTION MATTERS.

Every time there is a supply crunch, the instinct is to wait it out. That instinct is wrong this time. IDC is explicit: this is not a cyclical shortage driven by a temporary demand spike or a logistics disruption. It is a potentially permanent strategic reallocation of global silicon wafer capacity. The manufacturers made a deliberate choice. They are not going to un-make it until AI infrastructure demand moderates or new fab capacity comes online.

New fab capacity does not arrive until 2027 at the earliest. Micron’s CEO has stated supply tightness will continue into 2027. Samsung’s next major HBM fab does not reach volume production until 2028. The gap between what the market needs and what it can produce is not closing this year. Organizations that are waiting for normalization to make hardware decisions are going to be waiting for a long time while paying elevated prices the entire time.

One more wrinkle worth knowing. Gartner projects a 130% year-over-year DRAM price rise for 2026 overall. IDC projects the PC market will shrink 11.3% as a result. That contraction means OEMs have less volume to spread fixed costs across, which puts additional upward pressure on the per-unit price you pay. The shortage is creating a reinforcing cycle and the enterprise IT buyer is sitting in the middle of it.

For all your parents or parents of gamers out there, this is why certain video games are no longer being produced in physical formats (CDs or whatever you call those cards that goes in the Switch.)

Four moves to make this week.

First, pull every IT hardware quote from Q3 and Q4 2025 and reprice it at current market rates. The gap between what you budgeted and what you will actually pay is your exposure and your finance team needs to see it before it shows up as a surprise variance. Second, for any hardware you do not urgently need in the next 90 days, delay the purchase toward H2 2026 when analysts project some pricing softness as inventory builds. Third, for anything you need urgently, engage your VAR or distributor today about locking in pricing and availability commitments in writing. Quote validity windows are already shortening to 48 to 72 hours at some OEMs. A verbal quote is not a commitment. Fourth, look hard at your device refresh cycle assumptions. Extending non-critical endpoints from a 4-year to a 5-year refresh cycle is defensible in any budget conversation right now and keeps you out of the market at peak pricing.

Source: Insight: 2026 RAM Shortage Enterprise Guide | SHI: What Is Driving the Global RAM Shortage | IDC: Global Memory Shortage Crisis Market Analysis | SoftwareSeni: DRAM Prices in 2026 Have Doubled | SHI: Impact of Memory Shortage on Data Center Buyers

VENDOR FISCAL YEAR CALENDAR: NOW THROUGH SEPTEMBER

Your Vendors Are On a Clock. Make Sure You Are On It Too.

Vendor fiscal year pressure is one of the few structural negotiating levers in procurement that is entirely predictable. Sales teams chasing quota close faster and more creatively than sales teams who just made their number. Here is the accurate calendar through end of September, with the vendors you are most likely negotiating.

CLOSING TODAY: MICROSOFT | FISCAL YEAR END JUNE 30

Today is the last day of Microsoft’s fiscal year. The M365 price increase goes live tomorrow, July 1st. These two things together, fiscal year close and price lock deadline, create the highest-pressure negotiating window in Microsoft’s calendar. If you have not already started a conversation, it is not too late to call your account executive today. Not email. Call.
What to do: If you have any Microsoft renewal in the next 12 months, ask today about accelerating it to lock in current pricing. Ask about bundling Unified Support into your EA separately. Ask for a license utilization report before you commit to quantities. The AI add-ons are expanding across M365 suites automatically starting this month. Do not renew at last year’s seat count without auditing actual usage first.
Source: SAMexpert: Microsoft AI Costs, Licensing vs Azure | AppDirect: Microsoft 365 Price Change Advisory, June 2026

JULY 31 | PALO ALTO NETWORKS FISCAL YEAR END

Q3 results released June 2nd showed 31% revenue growth, driven partly by the CyberArk acquisition. Their platformization strategy, consolidating customers onto fewer security products, means account teams are rewarded for expanding existing relationships in Q4. The urgency is real. Their Q4 is right now through July 31st.
What to do: If you have any Palo Alto Networks renewal in the next 12 months, start the conversation before July 31st. Their Q4 close combined with CyberArk integration complexity creates room for consolidation deals that bundle Prisma, Cortex, and CyberArk capabilities at better economics than you would see in August. Come in with documented competitive alternatives from CrowdStrike or Cisco. A verbal threat does not move Palo Alto. A documented quote does.
Source: Palo Alto Networks Q3 FY2026 Earnings, June 2, 2026

APPROXIMATELY JULY 26 | CISCO FISCAL YEAR END

Cisco Q3 earnings confirmed they are tracking toward their strongest full year ever with FY2026 guidance raised to $62.8 to $63 billion in revenue. A confident company, but Q4 quota pressure is still Q4 quota pressure. Cisco’s fiscal year closes on the last Saturday of July, approximately July 26th. Their account teams are in maximum push mode right now.
What to do: Cisco’s primary vulnerability right now is competition from cloud-native networking and the Microsoft-CrowdStrike partnership eating into their security business. If you have campus networking, Webex, or security renewals coming, document a competitive quote from a credible alternative before you negotiate. Cisco responds to documented alternatives far more than to theoretical ones.
Source: Cisco Q3 FY2026 Earnings Report, May 2026

JULY 31 | SALESFORCE Q2 CLOSE (FISCAL YEAR ENDS JANUARY 31)

Salesforce’s full fiscal year ends January 31st, but July 31st closes their Q2, which is a real pressure point. Their account teams are being pushed to hit mid-year targets. The Fin acquisition at $3.6 billion means they are actively trying to validate Agentforce’s commercial value. That creates a window where they need your commitment more than usual.
What to do: Use the Fin acquisition as leverage in any current Salesforce negotiation. Ask for an extended Agentforce pilot at no cost as part of your renewal terms. Commit to Agentforce consumption pricing only after you have real usage data, not projected usage data. The companies burning through AI budgets right now are the ones who committed to consumption volume before they knew what they were actually going to consume.
Source: Everest Group: Nine Tactics for Salesforce Negotiation | TechnologyChecker: Salesforce Fin Acquisition, June 15, 2026

AUGUST 31 | ACCENTURE FISCAL YEAR END

Accenture closes August 31st. Their commercial account teams are in Q4 right now. And they have a specific motivation this year beyond normal quota pressure: DOGE-related federal contract cancellations hit Accenture Federal Services directly. GSA placed them on the review list. Federal revenue pressure means their commercial teams are being pushed harder than usual to make up the gap.
What to do: If you have consulting, managed services, or IT outsourcing work with Accenture, their federal exposure is your negotiating context. They need to replace revenue. Use July and August to renegotiate rate cards, introduce performance-based pricing into statement-of-work language, or exchange term extensions for pricing concessions. Come with market benchmarks. Accenture has their own benchmarks and will use them against you if you come without data.
Source: Accenture Investor FAQ: Fiscal Year End August 31

DATES YOU SHOULD HAVE IN YOUR CALENDAR

Coming Up. All Explained. No Filler.

TODAY | JUNE 30 FAR Overhaul Phase 1 Live

Fixed-price contracting is now the federal default. If you have federal contracts or suppliers who do, the compliance clock is running.

JULY 1 USMCA Joint Review Opens

The first mandatory review of the US-Mexico-Canada trade agreement begins today. A clean extension is unlikely. Map your North American sourcing exposure before the negotiation creates uncertainty about your specific categories.

JULY 3 GSA AI Listening Session Registration Closes

If you want to present at GSA’s July 14th session on the LLM safeguarding clause, you must register by today. Virtual attendance is also available.

JULY 6 Section 301 Forced Labor Tariff Comments Close

The last day to submit written comments on the proposed 10% and 12.5% tariffs on 60 countries. If your supply chain touches any of those economies, this is your last formal opportunity to influence the outcome.

JULY 14 GSA AI Listening Session | GW Law School + Virtual

GSA’s public session on GSAR clause 552.239-7001. The AI governance language being debated here will eventually land in commercial contracts. Worth following even if you have no federal exposure.

JULY 26-31 Cisco + Palo Alto Networks + Salesforce Q2 Close Windows

Multiple fiscal year-end events in one week. Have your proposals and competitive documentation ready before this window, not during it.

JULY 29 Agency Deadline: Renegotiate Top 10 Federal Non-Fixed-Price Contracts

Every federal agency must have begun renegotiating its largest cost-reimbursement contracts to fixed-price terms. If you are a supplier on any of those, the call is coming.

AUGUST 3 GSA LLM Safeguarding Clause Comments Due

Last day for written comments. If your organization delivers services using AI tools and has any federal contract exposure, this is the last opportunity to formally shape how this clause develops.

AUGUST 31 Accenture Fiscal Year End

Maximum commercial pressure on Accenture account teams. If you have consulting or managed services work with them, the first two weeks of August are your negotiating window.

That is two weeks. Plus a contracting guide.

Seven stories, a full contracting section with actual questions to ask, and a vendor calendar through August. The USMCA story is the one that most indirect teams will underestimate because it feels like someone else’s problem until it suddenly is not. The AI contract language section exists because I have spent enough years in contract negotiations to know that the people who get burned are almost always the ones who assumed the other side was going to bring it up first.

They are not going to bring it up. You have to.

Drop a comment. Push back. Tell me what I got wrong. That is the whole point of this thing. I want to push a newsletter worth reading… something that helps you be better at your job. I want this to be a tool that makes you sound extra smart in that meeting. Help me build that.

SOURCES

1. Convera: USMCA 2026 Review Analysis

2. CSIS: USMCA Review 2026 Six Scenarios

3. Tax Foundation: USMCA Tariff Trade Agreement

4. BSI: USMCA Review What You Need to Know

5. Federal Register: GSAR LLM Safeguarding Clause, June 17, 2026

6. Singularity Capital Advisors: GSA AI Rule, June 2026

7. Mondaq: GSA LLM Rewrite, June 23, 2026

8. RVIA: Latest Tariff Developments, June 25, 2026

9. Penn Wharton: Effective Tariff Rates, June 16, 2026

10. Zylo: 2026 SaaS Statistics and Trends

11. Tropic: 2026 SaaS Procurement Predictions