Explorez tous les épisodes du podcast YPO Technology Network AI Brief

On 21 September Shopify announced agentic checkout with Meta's new personal agent, Muse, "on all Shopify stores." Shopify's own help pages show how: a setting called "Allow Shopify to manage for me" is on by default, direct checkout for Meta is activated by default for eligible stores in the US, Canada and Mexico, stores are "auto-enrolled in new agentic storefronts channels," and "if you do not wish to participate, it is your responsibility to disable the features." The same evening Amazon blocked Muse. Third-party marketing pixels do not fire on these orders. A week later Shopify opened its checkout to any browser-based agent.

This weekend edition asks who the customer is when a machine does the buying, how Meta and OpenAI get paid, what the agents weigh when they choose, and why a number-three player should be glad. It then walks one buyer, a factory manager with a failing pump, through four moves for the front of the house.

In this episode, Stephen Forte covers:

• The default. What Shopify switched on, the six clicks to switch it off, no fees for the channel, and why the store remains the seller.
• Who the customer is. Sixty-word prompts against three-and-a-half-word searches, and an agent that remembers.
• The money. Muse's ad carve-out and training opt-out, and Meta's Business Agent at $2 per million tokens, used by more than a million businesses a week.
• The shelf keeps moving. OpenAI's checkout fee and ranking language of 2025, its pullback in March, and today's ranking factors. Sponsored Agents and Google's Direct Offers.
• What agents weigh. Columbia and Yale's simulated store, a hotel study, and G2's software buyers.
• The challenger's opening. Dell passing Compaq in 2001, and why incumbents still have advantages.
• Four moves. Choose the buying occasion, give the claim a witness, make the next decision easy, follow the sale through. Then a thirty-day trial with one owner.

Sources:

• Shopify Help Center, Selling on Meta and Managing agentic storefronts; Agentic Storefronts Supplemental Terms; developer changelog, WebMCP support for checkout (28 Sept 2026)
• Meta newsroom: Introducing Muse (8 Sept 2026); Meta Business Agent (3 June 2026); Meta Enterprise Platform (28 Sept 2026); Q2 2026 earnings call
• Amazon's block of Muse, as reported by Quartz and Bloomberg, 21 Sept 2026
• OpenAI: Buy it in ChatGPT (29 Sept 2025); Shopping with ChatGPT Search help page (updated 1 Oct 2026); Modern Retail, 12 March 2026
• Google, Direct Offers (11 Jan 2026); Allouah et al., arXiv 2508.02630; Wadi and Ma, arXiv 2608.22697
• G2 (15 April and 22 July 2026); Bain (7 April 2026); Gartner (21 Oct 2025); Visa (18 Dec 2025); PYMNTS and Visa merchant survey (June 2026); Similarweb

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

Accenture reported fiscal 2026 on 1 October: $74.2 billion in revenue, up 5 percent in local currency, $84.5 billion in new bookings, and about 814,000 people. The shares jumped by double digits. On the call, CEO Julie Sweet said clients "remain at very different stages of readiness" and "many are just starting their AI journey," with more than 400 clients starting their first advanced AI work this year. She said "in Q4, we saw lower pricing in many areas of our business." The CFO said fixed price work, including work paid on results, is now over 65 percent of bookings. And next year Accenture will hire "at a lower rate, in part due to AI."

When the biggest seller of AI transformation reports its year, it is also telling you about its buyers. This episode reads Accenture's results as a briefing for the people who buy from firms like it.

In this episode, Stephen Forte covers:

• Most clients are just starting. Accenture's own words, Deloitte's August survey of 501 US leaders (only 16 percent say their processes are prepared), and a CIO's admission about counting agents.
• The price came down. Lower pricing in many areas, continued intense competition, and two of every three dollars booked no longer sold by the hour.
• Who keeps the saved hours. Why a flat price lets a faster seller keep its savings, and what to ask for at your next renewal.
• AI inside the software you already pay for. Faster implementations, and why your next proposal should not look like the last one.
• The people line. Headcount up, hiring slowing, entry-level hiring continuing, and revenue per person as the number to track in your own company.
• What the seller bought. $4.9 billion of acquisitions toward businesses that do not bill by the hour, a billion dollars of retraining, and an AI risk factor in its own filing.

Sources:

• Accenture 8-K exhibit 99.1, fourth quarter and fiscal 2026 results, 1 October 2026: https://www.sec.gov/Archives/edgar/data/1467373/000146737326000037/q4fy26earnings8-kexhibit.htm
• Accenture Q4 fiscal 2026 earnings call transcript, 1 October 2026 (Investing.com): https://www.investing.com/news/transcripts/earnings-call-transcript-accenture-tops-q4-2026-forecasts-shares-jump-178-93CH-4927565
• Deloitte Insights, "The path to agentic transformation," 12 August 2026: https://www.deloitte.com/us/en/insights/industry/technology/path-to-agentic-transformation.html
• Fortune, "Agentic AI early adopters have failed, pivoted, and learned these 3 lessons," 29 September 2026: https://fortune.com/2026/09/29/how-adobe-salesforce-kyndryl-freeport-use-ai-agents/

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

Connecticut's Public Act 26-15 takes effect today. Three sections reach ordinary companies: employers filing a federal layoff notice must tell the state whether the layoffs relate to their use of artificial intelligence; using an automated employment decision tool "shall not be a defense" against a discrimination complaint, though evidence of anti-bias testing may be weighed; and anyone selling an AI subscription to a Connecticut resident needs written notice of the terms and written acceptance before charging a fee. The heavier developer and deployer duties do not start until October 2027.

Last night California's governor signed 13 AI bills before the deadline, including SB 947 (no relying only on AI to discipline or fire, a near-identical bill was vetoed last year) and SB 951 (layoff notices must say whether an AI system caused the cuts), plus an executive order that state agencies will keep calling artificial intelligence "Artificial Intelligence," the day after Washington's order renaming it "Super Intelligence." The regulator's question is no longer whether you use AI. It is who decided, and can you show it.

In this episode, Stephen Forte covers:

• Who this reaches. The rules follow the worker and the customer, not the head office.
• Connecticut's layoff question. The new disclosure on federal layoff notices, the act's broad definition of AI, and why the hard part is knowing the answer.
• The no-defense rule. What counts as an automated employment decision tool, what is excluded, and the credit Hartford earns for saying in advance what good anti-bias evidence looks like.
• AI subscriptions. Written terms, written acceptance, disclosed limits and discretion, renewals, and attorney general enforcement only.
• What does not start today. Developer and deployer duties (October 2027), companion chatbots (January), youth social media (2028).
• California's thirteen. SB 947 and SB 951 in plain words, and one breath each for surveillance, doctors, watermarks, digital replicas, lawyers and the rest.
• Two orders on a name. Washington's "Super Intelligence" order and Sacramento's reply, "further informed by common sense."
• The close. Could the person who signs your layoff notice and the person who approved your last hiring tool both say whether a machine made the call? Would their answers match?

Sources:

• Connecticut Public Act 26-15 (Substitute Senate Bill 5), approved 27 May 2026, enrolled text: https://www.cga.ct.gov/2026/ACT/PA/PDF/2026PA-00015-R00SB-00005-PA.PDF
• Governor of California, signing release of 30 September 2026 (13 bills, listed by number): https://www.gov.ca.gov/2026/09/30/californias-nation-leading-ai-framework-just-got-stronger-governor-newsom-signs-more-first-in-the-nation-worker-protections-and-more/ ; Executive Order N-10-26: https://www.gov.ca.gov/wp-content/uploads/2026/09/SIGNED_EO-N-10-26_9.30.26.pdf
• Associated Press, "California Gov. Gavin Newsom signs laws to protect workers from AI risks," 30 September 2026
• The White House, "Inaugurating The Era Of Super Intelligence," 29 September 2026: https://www.whitehouse.gov/presidential-actions/2026/09/inaugurating-the-era-of-super-intelligence/

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

Reuters reported on 29 September that McDonald's runs a pricing engine that analyzes millions of daily transactions across nearly 14,000 restaurants and generates what the company calls "the optimal price" for each item at each location, using among other things an estimate of how much local customers are willing to pay. Two company-run stores in Fresno, two miles apart, sell the Big Mac at $5.69 and $6.89. Five franchisees described pressure to follow the recommendations, a June document shows deviations are tracked, and the portal warns owners they "may be competitors." McDonald's calls it "a tool, not a mandate."

The same week, California signed AB 1609: companies over $500 million in revenue must disclose when customer service is a chatbot and connect a human within 15 minutes, with penalties of $5,000 and $10,000. And CarMax told investors that AI voice now answers 100 percent of its inbound calls while its pricing algorithms are retuned monthly, both under one executive. The two things a customer meets first, the price and the phone, are now machines, and the rules arrived in the same week.

In this episode, Stephen Forte covers:

• The pricing engine. How McDonald's machine sets "the optimal price," what the owner's portal shows, the Fresno gap as an observed difference, and how recommendations are tracked and followed up.
• Both sides. A former owner: "You don't really have much of a choice anymore." McDonald's: "a tool, not a mandate." A former FTC commissioner on the antitrust warning in the portal's terms.
• The regulators. The FTC's proposed enforcement policy on personalized pricing (comments closed 25 September) and New York's on-screen disclosure line.
• The phone gets a clock. California AB 1609: who it covers, the disclosure, the 15-minute human, the hold caps, the penalties, effective in January. Why the number will follow companies under the threshold.
• SB 947. The governor's deadline on automated decisions in discipline and firing.
• CarMax. AI voice on every inbound call since May, pricing algorithms evolved monthly, and strategy, data science, AI and pricing under one senior vice president. "Every vehicle is an individual SKU."
• The close. Who sets the price the customer sees, who decides when the machine hands the call to a person, and whether those two people have met. The law caught up with the phone first. The price is next.

Sources:

• Reuters, "Inside McDonald's push to have AI price your Big Mac," 29 September 2026 (via Investing.com): https://www.investing.com/news/stock-market-news/inside-mcdonalds-push-to-have-ai-price-your-big-mac-4921983
• California AB 1609 text and the Governor's signing release of 28 September 2026: https://www.gov.ca.gov/2026/09/28/governor-newsom-signs-commonsense-legislation-to-make-your-life-easier/ ; SB 947 status at leginfo.legislature.ca.gov
• CarMax Q2 fiscal 2027 results and call, 29 September 2026: https://investors.carmax.com/news-and-events/news/news-details/2026/CarMax-Reports-Second-Quarter-Fiscal-2027-Results/default.aspx ; CarMax and Sierra, 6 August 2026
• FTC, Proposed Enforcement Policy Statement Regarding Personalized Pricing, 19 August 2026; New York Algorithmic Pricing Disclosure Act

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

On its 24 September earnings call Costco's CFO said traffic from AI search grew triple digits for a second consecutive quarter, converts better than any other source, and sells the membership itself. He named Gemini, Anthropic and OpenAI as the sources, and said teams are cleaning up product data and pages so that Costco's value shows up correctly in the large language models. In May the CEO explained why: regular search never showed the all-in price; the models do.

Then the map. Amazon's robots file names 101 automated visitors and turns away every AI agent, including the ones that answer a live question. Costco, Walmart, Target, Home Depot, IKEA, Carrefour, Etsy and McMaster-Carr have no AI rule at all; Best Buy lets the answering agents in and shuts out the training crawlers. And the honest counterweight: Walmart's checkout inside ChatGPT converted at one third the rate of sending the shopper to its own site, so the winning posture is discover in the assistant, buy on your site.

In this episode, Stephen Forte covers:

• The call. Triple digits twice, highest conversion of all site traffic, the membership among the top items, the three companies named, and the product-page work behind it.
• The industry number. Adobe's data, as reported: AI-referred retail traffic up 138 percent in a year, converting 54 percent better; half of the average grocery page unreadable to a machine.
• The map. Amazon's 101 no's and its Perplexity lawsuit, turned back by the Ninth Circuit on 4 August. Why blocking is a luxury of the company that is already the destination.
• Walmart's lesson. One third the conversion inside the chat; OpenAI's pivot to discovery.
• Five moves. One: find out whether you are letting them in (answering agents versus training crawlers; Cloudflare's 15 September default; the Google-Extended myth). Two: put the price and the facts in the page the server sends, not in a script, and put the all-in price on it. Three: feed them directly and keep the feed current (OpenAI's nine required fields). Four: ask the three assistants what they say about you, then build the analytics channel. Five: keep the checkout.
• What not to buy. An llms.txt file: none of the three vendors' crawler documentation mentions it.
• The broken metric. Your search ranking is a score in a contest the customer is starting to stop watching. The customer did not search. She asked. And the answer had somebody's price in it.

Sources:

• Costco Q4 FY2026 earnings call, 24 September 2026 (transcripts via Webull and Investing.com); Q3 FY2026 call, 28 May 2026; press release: https://www.sec.gov/Archives/edgar/data/0000909832/000090983226000084/costex9918-k92426.htm
• Amazon.com Services v. Perplexity AI, Ninth Circuit opinion, 4 August 2026: https://cdn.ca9.uscourts.gov/datastore/opinions/2026/08/04/26-1444.pdf
• robots.txt files of amazon.com, costco.com, walmart.com, target.com, homedepot.com, bestbuy.com and others, fetched 27 September 2026
• Search Engine Land, 20 March 2026; Digital Commerce 360, 24 March and 17 June 2026 (Adobe data)
• Cloudflare, new AI traffic options, 1 July 2026: https://blog.cloudflare.com/content-independence-day-ai-options/
• OpenAI crawler documentation and product feed specification; Anthropic crawler documentation (7 April 2026); Google crawler documentation (3 March 2026) and Merchant Center structured data help

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

On Friday 25 September Microsoft rebuilt Copilot into one app with three tabs: Home, Code and Autopilot. Home puts Word, Excel and PowerPoint inside the assistant and adds a Today panel across mail, calendar, Teams and tasks. Code lets anyone build an app or workflow by describing it, hosted in the company's own tenant. Autopilot is a standing agent with, in Microsoft's words, its own identity, memory, computer and workspace, that colleagues can @mention like a coworker. Nothing is broadly available yet: Home and Code reach the Frontier early-access program in the coming weeks; Autopilot enters private preview at month end.

The same day Microsoft split the bill. Everyday AI stays on the per-user seat, with OpenAI and Anthropic models included. Cowork, Code, Autopilot and the frontier models run on a usage meter, which for enterprise customers stays off until an admin writes a spending policy. New small-business licenses bought through resellers get the meter on by default from 2 November.

In this episode, Stephen Forte covers:

• What was announced, and what is actually available. Three tabs, Office inside Copilot, Today, Code, Autopilot. Frontier program, private preview, no general availability date.
• How it looks on the desktop. Office in Copilot rather than Copilot in Office; a model menu offering GPT, Anthropic's Opus and Auto; the demo agent Dot that found a shipment problem across eighteen stores without being asked.
• Three layers of operational change. The assistant becomes the front door to Office; every department can build hosted software, with a plugin registry IT approves; and a colleague who is not a person gets a badge and an audit trail. Andreou: autonomy is "absolutely terrifying to an IT admin." Nadella: "Every agent has to have an identity."
• The bill. Seat plus meter, Microsoft's plug-in hybrid. "Some vendors put everyday AI work on a meter. We think that's the wrong deal." Enterprise meter off by default; reseller default on from 2 November; no price published on Friday; Opus 5 "with limits" and no limit stated.
• Is it a replacement for Claude? Anthropic's models are inside Copilot, so the question is the harness and the fence, not the brain. Microsoft's own chart (thirty dollars versus eighty-four for fifteen everyday tasks; seventy-three versus one hundred forty-nine for an advanced user) and the fine print that priced the rival on its most expensive model throughout. The host's read as an operator whose company runs on Claude and pays Microsoft too.
• What Microsoft did with its own product. Rivals on the menu at the flat price; its own meter off by default; its own executive calling it terrifying. Microsoft put its rivals on the menu. What it is charging for is the building.

Sources:

• Microsoft, Introducing the new Copilot with Home, Code and Autopilot (Jared Spataro, 25 September 2026): https://blogs.microsoft.com/blog/2026/09/25/introducing-the-new-copilot-with-home-code-and-autopilot/
• Microsoft Tech Community, Evolution of the Copilot pricing model (Nicole Herskowitz, 25 September 2026): https://techcommunity.microsoft.com/blog/microsoft-copilot-blog/evolution-of-the-copilot-pricing-model/4559416
• Microsoft Partner Center, September 2026 announcements: https://learn.microsoft.com/en-us/partner-center/announcements/2026-september
• GeekWire, 25 September 2026: https://www.geekwire.com/2026/microsoft-unveils-all-in-one-copilot-app-taking-on-anthropic-and-openai-in-new-push-to-boost-adoption/

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

Every product a company makes has a bill of materials: every part, its cost, its supplier. The company that makes those products has no equivalent document for the work its people do. This weekend edition is about that missing document, the bill of work, why almost nobody has one, and how to build one for a single department in about three weeks.

Nobody has done the counting: the Census Bureau finds 85 percent of US firms using generative AI use it for writing and editing, and nearly 65 percent confine it to three tasks or fewer. More than seven thousand annual reports filed with the SEC since January 2025 mention AI; one states a cost per task.

In this episode, Stephen Forte covers:

• The bill of materials, and the teardown. Munro and Associates in Auburn Hills, Michigan, takes a competitor's car to pieces and prices every part at plus or minus eight percent. There are two kinds of teardown; the second kind points inward.
• Why the org chart cannot see it. A map of authority, not a map of work. One task wearing three costumes, each five percent of someone's week, each correctly filed as a rounding error by its own department.
• The lens. The unit of AI is the task family, not the department. Organized by department, bought by the person, measured by headcount, becomes the task family, the completed task, cost per completion.
• Five steps to a bill of work. Take one department apart on cards. Sort by shape, not owner (the illustrative five accountants: eight shapes, eight shared agents). Cost the biggest pile three ways, including what is queued behind it. One agent, owned by the person who knows the work, baseline written first, ninety days. Decide what the freed capacity is for before it exists.
• Why the number is capacity, not cash. Danish payroll data: workers report saving about three percent of hours; hours and earnings do not move. The three conversions: velocity, growth not hired for, consolidation through attrition.
• The honest section. The US General Services Administration published 240,000 hours reclaimed; its own Inspector General found nine of the ten biggest bots off their forecasts and two credited with 15,000 hours after being switched off. Goldratt's constraint objection, amended, not repealed. Why "pick three workflows" and "map everything" both miss the pile.
• The question. If someone handed you a price list on Monday for the ten most common tasks in your company, could you tell whether it was a good price? Do you know which ten they are?

A note on the arithmetic: the five accountants are illustrative and are said so on air; every other figure is from a primary source listed below. The Swedish payments firm is one filing, not a case study.

Sources:

• US Census Bureau, Center for Economic Studies working paper CES-WP-26-25 (April 2026), generative AI use by task among US firms.
• SEC EDGAR full-text search, 10-K and 20-F filings mentioning artificial intelligence, 1 January 2025 to 12 September 2026; Klarna Form 20-F for fiscal 2025.
• Kaplan and Anderson, Time-Driven Activity-Based Costing, Harvard Business Review, November 2004.
• Humlum and Vestergaard, NBER Working Paper 33777 (revised March 2026), large language models and labor market outcomes in Denmark.
• US General Services Administration, Office of Inspector General, report A210057/B/5/F24001, 30 November 2023.
• Goldratt, The Goal (1984); C.H. Robinson second-quarter 2026 results; Munro and Associates published teardown reports.

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

On 30 September, Italy's implementing decree for the EU AI Act takes effect, and it reads less like a compliance rulebook than a set of courtroom rules. In any damages claim involving an AI system, a judge can order the company to hand over the system's logs, its risk-management file, its technical documentation and its human-oversight settings. If the company cannot produce them without justified reason, the court treats the claimant's version of the facts as admitted. Once an AI Act obligation has been breached, causation is presumed. And conformity with the AI Act, even certified conformity, does not by itself exclude liability.

Brussels pushed the EU-wide high-risk paperwork deadline to December 2027 this summer. Rome did not wait for it.

In this episode, Stephen Forte covers:

• The dates. Italy's national AI law of September 2025; the liability decree signed 9 September 2026, published 15 September, in force 30 September; the AI Omnibus delay of high-risk obligations to 2 December 2027.
• Access to evidence. Article 17: the four documents a judge can demand, and the sentence that treats missing documentation as an admission.
• Causation and the certificate. Article 18 presumes the causal link once a rule is breached. Article 19 says certified conformity is not, on its own, a defense.
• The insurer. Article 20: thirty days to name your liability insurer when asked, and a direct action against it up to the policy limit.
• The criminal side. New Article 437-bis of the Italian criminal code: one to five years for omitted safety or oversight measures on high-risk systems, and the paragraph that reaches the professional user who switched the system on. Corporate fines under Italy's corporate-crime statute of roughly 155,000 to 1.55 million euros, plus bans on public contracts, licenses, subsidies and advertising.
• Why it matters outside Italy. The four documents an Italian judge can demand are the four the AI Act will require of every high-risk system in the Union from December 2027, and the four your insurer, your board and your next plaintiff will ask for regardless.
• The one question. If a judge asked tomorrow, could you hand over what your AI system did, and who was watching it, for every decision since the day it was switched on.

A note on the sources: every provision was read in the official consolidated text at normattiva.it; the translations are the host's own. The Brescia manufacturer in the episode is invented to make the shape clear.

Also in this episode: a short note on why the show went quiet for three days.

Sources:

• Italy, Legislative Decree 9 September 2026, n. 160 (Gazzetta Ufficiale n. 214, 15 September 2026): https://www.normattiva.it/uri-res/N2Ls?urn:nir:stato:decreto.legislativo:2026-09-09;160
• European Commission, AI Act regulatory framework and AI Omnibus timeline: https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai
• EU AI Act implementation timeline: https://artificialintelligenceact.eu/implementation-timeline/

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

In one week, Salesforce and HubSpot both showed the mid-market what an AI agent will cost, and the answer is a second meter running next to the seats you already pay for. Salesforce shipped its own reasoning model, Koa, to pilot customers with general availability months away and no price. It paired user seats with preset credit allowances and gave its agents first names. A Salesforce plug-in opened to every paid plan of a frontier lab's assistant, with no combined price. HubSpot did the one thing Salesforce did not: it published a price list, by the action, in credits.

Then two analysts asked twenty Salesforce customers what agents do to the bill. Three in four of those who had modelled it expected their Salesforce spending to rise. Fourteen were asked where the money came from. Not one said the old bill.

In this episode, Stephen Forte covers:

• What shipped at Dreamforce. Koa, trained on twenty-seven years of Salesforce CRM intelligence, in pilot now, general availability expected winter 2026 in US regions, unpriced. Seat bundles with preset credits. Piper, Hunter and Fin.
• Two vendors, two meters, one workflow. A Salesforce plug-in on every paid Claude plan, thirty-seven prebuilt sales skills, seven thousand sellers already on it, and no mention of pricing.
• HubSpot's price list. Nine US dollars per thousand credits on the annual rate. A thousand credits per content piece, five hundred per invoice chased, ten per nurture email, fifty per resolved service conversation. Arithmetic a CEO can do in the car.
• The twenty interviews. Five to fifteen percent of Salesforce spend going to agents. None of fourteen shifting existing budget. Seventy-five percent expecting the bill to rise under headless access.
• The reframe. The seat was a ceiling: you knew the worst case on the first of the month. The meter is a floor with no natural top except the work itself. A rental car and a taxi both get you to the meeting; only one keeps counting in traffic.
• The close. Walk into the next renewal with two numbers, what the seats cost and what the meter will run. If the vendor can only give you the first, that is the answer.

A note on the customer figures: they come from twenty in-depth interviews conducted over five business days, not a statistical survey, and are aired exactly as the analysts printed them.

Sources:

• Salesforce, Koa press release, 15 September 2026: https://www.salesforce.com/news/press-releases/2026/09/15/koa-reasoning-model/
• Moor Insights and Strategy, Dreamforce 2026 field notes, 18 September 2026: https://moorinsightsstrategy.com/field-notes/at-dreamforce-2026-salesforce-goes-all-in-on-agentic-ai/
• Anthropic, Salesforce in Claude, 15 September 2026: https://claude.com/blog/salesforce-in-claude
• HubSpot pricing page (credits): https://www.hubspot.com/pricing/suite
• SiliconANGLE, Dave Vellante and George Gilbert, Salesforce after Dreamforce, 19 September 2026: https://siliconangle.com/2026/09/19/salesforce-after-dreamforce-how-the-crm-giant-can-grow-beyond-its-own-interface/

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

Weekend edition. For those who have been plumbing their own systems, this one is for you. Once a quarter, Stephen Forte's company reviews the systems it runs itself: the code, the logs all the way down, the mechanical parts, the memory systems, and every bill divided by what actually shipped. This quarter it was the turn of three digital employees behind the morning client briefing. Nothing was broken, and nobody made a mistake. The systems had drifted, which is what agents do when nobody is looking.

A credentials script that made nineteen trips to the vault for eighteen keys and said "loaded" whether or not it had. An engagement memory that answered every write with "probably" and filed a correction underneath the thing it corrected. A drafting loop that wrote eleven versions of every brief and handed in one. Three employees, none of them people, none of them ever reviewed.

In this episode, Stephen Forte covers:

• The quarterly review as a practice. AI systems do not break the way software breaks. They drift, settle into habits, and keep saying yes while the yes slowly means less. Why that is not a defect, and why the review is the only thing that catches it.
• The most agreeable intern. The vault script finished every shift with "environment loaded," including the night several keys came back blank. Nineteen trips for eighteen keys, twelve seconds a load, fourteen loads a night. The fix took an evening. The fix had been written down twice before, and a backlog only promotes what is on fire.
• The brilliant colleague with a filing problem. Twenty-four facts written in one day, twenty-four answers of "probably." A changed approver recorded properly on the day, and the old name still ranking first and second. What drift actually looks like, and why only a review sees the order a memory remembers in.
• The smoke detector with the speaker removed. A nightly review that flagged two thousand four hundred and seventy-two of twenty-five thousand memories, and whose last reader had opened it five weeks earlier.
• The anxious intern. Eleven drafts to hand in one, and two quality checks that had drifted into impossible. A check that is wrong does not waste one draft; it rounds every draft to zero.
• Four questions that make up a digital employee's performance review. Does it fail loudly? Does it confirm, or does it say probably? What does one unit of output actually cost? Who opens the report it produces?
• The task master. One more digital employee whose whole job is a daily pass over what the others produce that no human reads, one paragraph a day, a human on Friday. And the cadence that fits each role: quarterly, monthly, weekly, daily.
• The close. Every digital employee reports success by default. A dashboard that cannot go down is not a metric. It is a greeting.

A note on specifics: every number in this episode is a real measurement from the review of Stephen's own company's systems on 17 September 2026. No client is named, described or identifiable; no vendor or product is named for any tool.

Sources:

• Internal quarterly systems review, 17 September 2026: credentials loader call counts, timings and failure behaviour, with the two-call replacement verified against the original; the memory system's write log, session hydration and search rankings; the nightly consolidation report; generation counts against shipped briefings.
• The daily review agent ("the task master") over hidden output, added 18 September 2026, with a weekly human read.

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

On Tuesday the Supreme Court of Tasmania threw out a parole condition because the document justifying it cited case law that does not exist. The Parole Board has conceded its own secretary wrote that document with AI. Tasmania already had a twenty-page AI policy, approved two years and two days before the ruling, and it had warned that inappropriate use of AI in decision making could expose a decision to judicial review for being unreasonable or denying procedural fairness. Those are the court's grounds.

In the same week in Los Angeles, a lawyer defending the insurer State Farm was fined $999.99 over briefs with fabricated citations, and her own apology to the court referenced her firm's generative-AI policy. Two continents, two written policies, two documents of invented law that reached the person who signs. The policy was in the binder. The work was in the room.

In this episode, Stephen Forte covers:

• Hobart. The board's rationale cited fictitious cases and, in counsel's words, "argued forcefully." The board withdrew the condition in August and declined to say why. The court found it legally unreasonable and a denial of procedural fairness.
• The policy that predicted it. Approved 13 September 2024 for every agency in the state, it told officials to critically examine AI outputs and warned that inappropriate use "may expose the decision to the risk of legal challenge, including judicial review," for being "improper, unreasonable" or denying "procedural fairness."
• The remedy. The Attorney-General is writing to the board's chair, wants assurances, and has told the justice department to remind every employee to comply with the policy. Told the policy had not worked, the state reminded everyone about the policy.
• Los Angeles, the control case. The lawyer accepted responsibility in her own words and listed three mechanical steps: retrieve every authority from a real database, check every quotation against the opinion, audit citations before filing. Her firm had a policy too.
• Policy versus control. A policy is a letter addressed to people who were already going to behave. Every company has a fire policy in a binder; the sprinkler in the ceiling has never consulted it.
• The mirror. When the board asks whether AI is under control, you will reach for a document. Reach for the check: what has to happen before a confident, well-formatted, completely invented paragraph reaches the person who signs.

A note on specifics: no individual is named; the Tasmanian document is guidance in form and is what the state calls its AI policy; nothing here is a view on the underlying conviction, which the woman concerned has always contested.

Sources:

• ABC News, 15 September 2026. Report
• ABC News, 16 September 2026. Report
• Tasmanian Government AI guidance, approved 13 September 2024. PDF
• ABA Journal, 15 September 2026. Report

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

Spain's data protection agency has received the first notification of a personal-data breach in which the intruder was an AI agent rather than a person. By the notifying company's account, the agent searched for vulnerabilities, achieved a valid login, explored the application on its own, altered personal data and accessed invoices. The regulator's response is not a new rule but four changes to how every company must think about risk, response time, credentials and human oversight, with its own caveat that AI creates no new threats; it removes the time you had to respond to the old ones.

In the same week, two London bodies retired the other two point-in-time assumptions: give AI a learner's permit and monitor it for life, and stop passing liability from the companies that build AI to the companies that use it.

In this episode, Stephen Forte covers:

• Madrid, the incident. The AEPD published the notification on 14 September: an agent built on "a well-known language model" chained the phases of the attack without a person steering each step. The regulator's caveats air with it: the account comes from the notifying organisation; the model and its provider are not implied compromised; one case is not a trend.
• The sentence that matters. "AI does not create new threats. It increases the speed, scale and adaptability of known malicious techniques, reducing the time available to detect and contain them."
• Four sentences that could be your risk committee's agenda. Write AI-executed attack into the risk analysis explicitly; assume response plans built for a human attacker are too slow; treat an over-permissioned account, key or token as a door that opens at machine speed; keep human oversight, resting on detection and response that can keep up.
• London, approval. The MHRA-established commission recommends staged authorisations for AI medical devices, "similar to 'L-plates' for learner drivers," and continuous monitoring "throughout their working life." A recommendation, not yet a rule.
• London, liability. Parliament's Joint Committee on Human Rights: "far too much freedom" for the companies that develop AI systems "to pass on liability to those who deploy them"; "responsibility to prevent harm should sit with those who are best able to do so." It calls for a dedicated AI Bill and a new regulator.
• The close. Nothing on the regulator's list of fundamentals is new. What changed this week is that you no longer have time to do it later.

A note on specifics: "first" means the first notification to the Spanish regulator, of one case; the model and the affected organisation are not named because the regulator did not name them; the London reports are recommendations to government, not law.

Sources:

• Agencia Española de Protección de Datos, blog, 14 September 2026 (in Spanish). AEPD statement
• GOV.UK, National Commission into the Regulation of AI in Healthcare, 10 September 2026. Press release and report
• Joint Committee on Human Rights, "Human Rights and the Regulation of AI," HC 160, 14 September 2026. Report

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

A free piece of software from DeepSeek, the Chinese AI lab, is now one of the fastest-growing projects GitHub has ever hosted: published on 13 August, past 225,000 stars and nearly 27,000 forks by mid-September. It is not a model. It is an agent harness, the software that decides what an AI model is allowed to touch, and its architecture is the reason for the growth: every layer of it is a swappable plugin.

Its own safety notice says it has not been audited and must not be treated as production-ready, and its own engineers write that the default credential store cannot keep a secret from the AI it serves.

In this episode, Stephen Forte covers:

• The number. 225,223 stars and 26,799 forks in 33 days, under an MIT license, with a new release the same week. The projects at the top of GitHub's all-time list took years to get there, most of them the better part of a decade.
• The architecture. The model, the filesystem and shell, storage, the scheduler and even the interface are plugins. A shipped plugin swaps the execution environment for a remote sandbox so nothing runs on your own hardware. It can hand a task to a Claude Code session, to OpenAI's Codex, or to any agent speaking the same open hand-off standard, and use the answer. Like the shipping container: standardize the box, not the cargo.
• Against Claude Code. Ahead: no subscription, open all the way down, any model including one hosted inside your own walls. Behind: three all-or-nothing permission presets, thin hooks into other systems, and the credential question.
• Your keys, both halves. The default store is a plaintext file, locked to your own user account, and the project's README says the agent's tools run as that same user, so the store "cannot isolate secrets from the agent"; an OS-keychain provider is deferred, not shipped. But every key is only a reference to an environment variable and the launch environment wins, so a secrets manager can hand the key in at launch with the file never written, and spawned commands get a scrubbed environment. A weak default, a real capability, and a decision the operator has to make on purpose.
• The warning, verbatim. "It has not undergone a security audit and must not be treated as secure or production-ready." Published in plain language, in the same box as the code, on day one.
• The close. 225,000 engineers have already voted for the architecture. The audit has not been held.

A note on specifics: star and fork counts are from the GitHub API on 15 September 2026; the credential behaviour is taken from the project's own READMEs and design notes at that day's commit. Vendors are named for identification, not endorsement.

Sources:

• deepseek-ai/deepseek-harness, repository and README. GitHub
• DeepSeek Harness safety notice (SAFETY.md). Safety notice
• Credential store README (dsh-credentials-local): precedence, the same-user limit, the deferred keychain provider. README
• CLI reference: credential resolution order and the subprocess environment scrub. Reference

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

Three institutions on one continent answered, in public and in one week, the questions most boardrooms are still debating. A bank in Tokyo let generative AI write the code for the system that holds every customer's balance. China's highest court told every judge in the country how to rule when an AI clones a voice. And one of India's largest outsourcers found it had the equivalent of twenty thousand people's time on its hands, and had to decide what to do with it.

None of the three is a vendor announcing a product. All three are institutions reporting on themselves.

In this episode, Stephen Forte covers:

• Tokyo, the build. Sony Bank and Fujitsu published phase-by-phase results from a year of AI-assisted development on the bank's core banking system: development period down 30 percent, hours down 40 percent, 99 percent of source code generated. The companies' own figures. Fujitsu now plans to sell the method to the other banks on its platform, which makes the bank's advantage a rental. The question the next modernisation proposal will not answer is who, in your building, signs for a ledger where humans wrote one line in a hundred.
• Beijing, the law. China's Supreme People's Court issued twenty-four articles of judicial guidance, its first rules for AI cases. Cloning a voice without consent "constitutes an infringement of their voice rights"; an unauthorised digital likeness violates the right to name and likeness; using AI to assemble private information is a privacy breach. The posture in one sentence: "tolerance should not be mistaken for permissiveness, nor should prudence be interpreted as acquiescence." It is guidance to courts rather than a statute, it does not settle the training-data question, and it drew the boundaries around people before data.
• India, the people. Wipro's chief technology officer, Sandhya Arun, told Reuters that AI had freed capacity "equivalent to" roughly 20,000 of the company's 243,000 employees, redeployed inside the firm. "It doesn't necessarily mean person-to-person replacement by an agent." An outsourcer sells hours, so freed hours are unsold inventory unless the pricing moves to outcomes. Your outsourcer's freed capacity is your next negotiation.
• The close. "Capacity equivalent to twenty thousand people" sounds like a headcount figure. It is hours that were freed and then had to be pointed at something. Capacity is not a saving. It is a decision nobody has made yet.

A note on specifics: the Sony Bank figures are from the companies' joint release and are not independently audited; the models were Anthropic's Claude and Claude Code via Amazon's cloud. The court guidelines are quoted from the court's own English release. The Wipro figures are the company's own, as reported by Reuters.

Sources:

• Fujitsu and Sony Bank, joint press release, "Sony Bank and Fujitsu apply Generative AI to Core Banking System Development," 14 September 2026. Release text
• Supreme People's Court of China, "SPC sets rules to curb AI misuse," 10 September 2026. english.court.gov.cn
• Reuters, "Wipro's AI push frees capacity equivalent to 20,000 workers, CTO says," 10 September 2026, via The Star. Article

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

On Monday, Accenture and Google Cloud launched a new business group whose headline is not software but people: a planned workforce of a thousand "forward deployed engineers" who sit inside client companies and build the AI for them. The most capable software company in the world has just said, in its own press release, that its enterprise AI does not install itself.

Yesterday's episode was about an airport that keeps its AI engineers in-house so the knowledge stays in the building. Today is the counter-bet: the supply side wagering that most companies will rent those people instead.

In this episode, Stephen Forte covers:

• What was actually announced, stripped of the adjectives: nearly fifty thousand Google Cloud-skilled staff already, a thousand-person forward-deployed workforce to be established, and four stated priorities, three of which are about adoption and none about the model.
• The reference customer problem: the one worked example is YouTube, a Google property, and the numbers are the companies' own.
• Where "forward deployed" comes from, why Palantir made it famous, and why the frontier AI labs and now the largest consultancy on earth have copied it.
• The dishwasher test: nobody builds a division of a thousand plumbers when the machine works in most kitchens on its own.
• The real asset: what a forward deployed engineer learns about how your company actually works, and the question of who owns it when the badge is handed back.
• The one staffing decision to make before the proposal arrives: seat one of your own people beside each of theirs, and make the handover the deliverable, not the agent.

Sources:

• Accenture Newsroom, "Accenture and Google Cloud Deepen Partnership with Formation of New Accenture Gemini Enterprise Business Group," 8 September 2026. All figures and quotes are from this release, read in full.

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

A weekend edition about your YPO chapter, the most important part of YPO, and exactly how an AI assistant fits into running it. Not the case for AI, but the plumbing that has to exist first and the things a chapter actually does with it once it does.

Stephen is the Regional Learning Officer for the Pacific, has founded two chapters, has been chapter chair, and will facilitate the chapter chair workshops at GLC in San Diego and Thailand in 2027. Everything here is what his own chapter does.

In this weekend edition, Stephen Forte covers:

• The plumbing: a domain the chapter owns, a Google Workspace subscription for the officers, mailboxes attached to roles rather than people, and a shared drive organized by learning year with the contracts, receipts, run sheets and minutes. Then connect the assistant. You are not handing over a job, you are handing over a memory.
• The board meeting: transcript to commitments, each sent back to the person who made it, and next month's agenda drafted from what is still open.
• The learning calendar: four events by the first of October, drafted in August from last year's run sheets and ratings instead of a September scramble.
• Member outreach: individual notes drafted from attendance history, always read and sent by a human, and the member who went from nine events to two, who needs a phone call, not a note.
• The money: who owes what in one sentence through the books, and the hard line: a window into the vault, never a second key.
• Governing documents, Game Plan follow-through, the weekly officer update, events and awards.
• Two rules: Forum is never on the list; administration is a system, Forum is a promise. And never automate the notes that are supposed to cost you something.

The ask: if you have built a piece of this, a spreadsheet you are secretly proud of or a run sheet that worked twice, Stephen wants it, and especially wants to know what broke. Write to him directly at stephen@forte.hk, and forward this to your chapter manager.

Sources:

• Stephen Forte's own practice as chapter founder and chair, Regional Learning Officer for the Pacific and Game Plan coach. All anecdotes are anonymized; no chapter, officer, manager or staff member is identified.
• YPO's chapter learning calendar requirement (four events by 1 October), as provided to chapter officers.

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

A CEO in Atlanta posted this week about the worst thing an AI agent ever did to his company: it was careful. It hit a broken field, assumed it lacked permission, quietly skipped the last step, and a product shipped attached to nothing while every dashboard stayed green. His line: "A loud failure gets fixed in ten minutes. A quiet skip ships and waits."

Field notes from one week of people running AI inside real companies, tiered honestly: one story on the record, one going around, one from a builder's test chat.

In this episode, Stephen Forte covers:

• Battlbox: how an agent's sensible caution at a zero it did not understand became the most expensive thing it could have done, and why nobody writes a post-mortem for a dashboard that stayed green.
• The night watchman and the alarm panel reading zero: no intruder, or dead sensors, and why the whole value of the watchman is knowing the difference.
• The story going around about a support bot that only worked because a junior employee nobody had on the chart was correcting it every day, and the eighteenth-century chess machine with a man inside.
• The funny one: an agent that refused a made-up order from its own "CEO" agent, reported it to the human, and got an apology. "We accidentally built HR."
• The one document almost no company has: the map of where the humans still sit inside the automation, and the two sentences per agent that produce it for free.

Sources:

• John Roman, CEO of Battlbox, post on X, 4 September 2026.
• Tanuj (@tanujDE3180), post on X, 4 September 2026; secondhand and unverified, presented as a story going around.
• Jeremiah K (@neolaj), thread on X, 8 September 2026.

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

A consultant closing out a healthcare technology conference in Singapore told the room something almost no vendor ever volunteers: his own employer, the group that runs Changi Airport, throws away more than six out of every ten AI projects it starts. Not after launch. Before one.

Every applied-AI story usually gets told around what shipped. This one is about what got killed on purpose, and that turns out to be the more useful story.

In this episode, Stephen Forte covers:

• Why Changi Airport Group's discard rate is not a confession: the ideas that survive land on real, working infrastructure the team spent years building, including custom-built agents and reusable technical plumbing, so killing an idea costs almost nothing instead of a career.
• The method behind the discipline: working backwards from the customer's journey before choosing a single tool, "customer over the product," the opposite order from how most AI pilots actually get built.
• Two analogies that reframe the number: a pharmaceutical industry that filters hard before anything reaches a patient, and a pilot's "go-around," the decision to abandon a landing and circle back, one of the most important judgments in the entire flight.
• The mirror for your own team: not what has AI done for us lately, but what have you refused to ship, and can anyone tell you why. Most companies do not have a kill rate. They have a hope rate.
• Why this travels past an airport: a hospital group in Nairobi, a logistics operator in Rotterdam, a retailer in Sao Paulo all carry the same shape of problem, and none of them needs an airport's budget to copy the actual behavior.

Sources:

• Healthcare IT News, "Major Singaporean airport group offers healthcare lessons on agentic AI," by Adam Ang, 1 September 2026. All quotes and figures are from this reporting, read in full.

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

On Wednesday, OpenAI released GPT-6 Astra and its president said it is "not unreasonable to feel that we are now in the AGI era." Two days earlier, an NPR reporter walked the floor of a GE Appliances oven plant in northwest Georgia, where a manufacturing vice president with nearly forty years on the floor gave his verdict on the AI running his line: "It can outthink me."

The story of applied AI this week is not that it took somebody's job. It took somebody's judgment.

In this episode, Stephen Forte covers:

• The three AI systems running inside one plant: cameras that inspect every unit and stop the line the moment they see a wrong gasket; a staffing tool that moves workers between sections as demand shifts; and a demand model that lets the plant change its weekly build almost at the last minute. None of them is a robot arm. The hands on the line are still human hands.
• The unit economics that explain why: stopping a line costs $300 to $500 a minute, and GE Appliances says a single percentage point of quality improvement is worth $1.5 million to $2 million a year. The least glamorous prize in the AI economy, which is precisely why it is credible.
• Why the first thing automated on a real floor was not the worker's task but the supervisor's call: what counts as a fault, who goes where, what to build next. A factory has always paid for hands and for the judgment that directs them; for a century they came bundled. This plant unbundled them.
• The credit, which is not optional: workers are moved, not removed; the company added 600 jobs in Georgia as part of a $180 million expansion; and the executive closest to the machine said on the record, "At least in the foreseeable future, I don't see AI replacing large populations of humans."
• Why this reaches a hospital group in Manila or a logistics business in Rotterdam: every operation runs on a layer of judgment nobody wrote down, and that judgment is now copyable. The veteran is not obsolete; the veteran's judgment can be bought, mounted on a camera, and run on every shift.
• The close: do not ask which jobs AI will take. Ask which of your judgment calls a machine could already make better than your best veteran. Name three and you have found where your AI money should go. It was never the chatbot.

A note on timing: the NPR reporting is from 1 September 2026. The plant's AI deployment (GE Appliances' Brilliant Factory programme on Google Cloud's Gemini Enterprise) was announced in April 2026; what is new is the on-site reporting and the veteran's verdict.

Sources:

• NPR, "'It can outthink me': How a major manufacturer came to embrace AI," by Andrea Hsu, 1 September 2026. All plant details, cost figures and quotes are from this reporting.
• OpenAI, "GPT-6 Astra: A new generation of intelligence," 3 September 2026. Greg Brockman's "AGI era" remark via Fortune, 3 September 2026 (reporter briefing at launch).
• GE Appliances and Google Cloud, "GE Appliances Reinvents Manufacturing Operations at Scale with Google Cloud's Gemini Enterprise," 22 April 2026 (deployment date).

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

Anthropic shipped two new frontier models this week and left the headline price exactly where it was: $10 per million input tokens, $50 output, unchanged. The number that moved is one almost nobody looks at. Cached input reads fell 75%, from $1.00 per million tokens to $0.25.

The price you get quoted is the price of answering once. Your bill is set by re-reading.

In this episode, Stephen Forte covers:

• What a cached read actually is, and why it decides agent economics: an agent is not answering one question. Every step, it is handed the whole situation again — your instructions, every tool definition, the document or codebase, and a conversation that keeps getting longer. On the new models a cache hit costs 2.5% of the standard input rate, against 10% on Anthropic's other models.
• Anthropic's own estimate that the change makes ordinary workloads ~25% cheaper and heavily agentic ones up to ~45% cheaper — aired as the company's figure, not an independent measurement. The gap between those two numbers is the lesson: the more autonomously software operates, the more of the bill was sitting in that one line.
• Why a quoted per-token price is very nearly useless for budgeting anything that works on your behalf over time.
• The demand side: Cisco said last week it is rolling an agent out to all 90,000 employees — not a pilot, not a department — working across email, chat, project tracking and documents. And agentic interactions on its internal AI platform grew nearly 350% in a single quarter. Cost per unit of agent work is falling sharply while volume grows at that rate; those do not cancel out.
• The quieter item in the same announcement: Anthropic shipped two models with identical architecture that differ only in the strength of their safety limits. The more constrained one is generally available; the less constrained one goes only to vetted cybersecurity and life-sciences organisations, through verification built in coordination with the US government. Not a better model for more money — the same model twice, with access to the looser one decided by who you are rather than what you pay.
• The close: a company that wanted you to believe its product had gotten cheaper would have cut the headline number. Anthropic left it alone and cut a line most buyers have never looked at. That is information about where the money actually is.

Also mentioned: In November, alongside the YPO Global Business Summit in Istanbul, the YPO Technology Network is running a full-day AI Global Summit on 6 November. Stephen is speaking, along with people from Microsoft and other leading AI companies. Registration is open.

Sources:

• Anthropic, Claude Fable 5.1 and Mythos 5.1, announced 1 September 2026. Pricing cross-verified across VentureBeat, TechSpot, implicator.ai and CybersecurityNews, plus the Claude Platform pricing documentation. The 25% / up-to-45% effective-cost figures are Anthropic's own estimate.
• Cisco Blogs, "MyAgent and the Rise of Ambient Intelligence: Cisco's Next Step in Enterprise AI," 27 August 2026, by Thimaya Subaiya, EVP of Operations. MyAgent runs on Cisco's Circuit platform across Outlook, Webex, Jira and SharePoint; the ~350% quarter-over-quarter growth figure is Cisco's own.

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

On Monday, Microsoft 365 broke for roughly a day and a half. It was covered almost everywhere as an Outlook outage. It was also something nobody quite named: the first mass outage of a corporate AI assistant. Microsoft's status page listed Copilot among the affected services, and Copilot prompts needing company data failed while the outage ran.

The model was working the entire time. It just could not reach anything.

In this episode, Stephen Forte covers:

• What actually failed on August 31: within about forty minutes, Microsoft had isolated a failure pattern involving authentication — not email, but the system that proves who you are. It spread to Outlook, SharePoint, OneDrive, Teams, Microsoft's own security product and Copilot, running into a second day.
• Microsoft's stated cause, verbatim: "an issue within a core authentication configuration used by multiple Microsoft 365 services." Engineers reading the error messages concluded an internal certificate had expired — Microsoft has not confirmed that, and the episode airs it explicitly as inference, not finding.
• Why the takeaway is not about the model: Copilot did not fail because anything was wrong with the model. What broke was its ability to reach email and files. Enterprise AI does not sit on top of the business — it sits inside it, inheriting every dependency of the platform it lives in.
• Why the boring explanation is the useful one: no attack, no adversary, no breach — a configuration in an authentication layer on an ordinary Monday. The unglamorous layer underneath decides whether the AI works, and almost nobody has it on a risk register.
• Honest credit: Microsoft kept a public status page current throughout and listed the affected services, including its own AI product.
• The second story: G20 technology and commerce officials are meeting in Chapel Hill, North Carolina, where the United States is asking them to endorse a framework called the Carolina Principles — reserve new regulation for genuinely novel problems, create no new AI supervisory agencies, regulate by sector rather than one broad law. It would go to G20 leaders in December. The European Union is moving the other way. The episode takes no view on which is right; the consequence is that a company operating in both markets does not get to pick one.
• Three quick items: OpenAI has reportedly bought Apple Mac minis and Mac Studios by the tens of thousands to train computer-use agents on real machines (unconfirmed); McKinsey finds 32% of organizations skipped at least one software purchase because they could build it with AI coding tools, nearer half among top performers; and Microsoft's own security product was on Monday's affected list.
• The close: no action item. You cannot fix Microsoft's authentication layer, and any vendor claiming this week that their product would have saved you is selling something. What is available is a correction to a mental model — you do not have an AI strategy separate from your infrastructure. You have one thing.

Sources:

• Microsoft 365 service health incidents EX1464935 / MO1465074, August 31 – September 1, 2026, via TechCrunch, Computerworld, IT Pro and BleepingComputer. The expired-certificate detail is an inference from error messages (Born's Tech and Windows World); Microsoft has not confirmed it.
• Reporting on the G20 ministerial in Chapel Hill and the proposed "Carolina Principles": Al Jazeera, Quartz and TechXplore, September 1–2, 2026.
• The Information on OpenAI's Mac mini and Mac Studio purchases for computer-use agent training, August 2026, via The Decoder. Not confirmed by OpenAI or Apple.
• McKinsey, The State of AI: Global Survey 2026.

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

On back-to-back days last week, two of the largest companies in the world put an AI number in front of their investors. TD Bank's chief executive said the bank had essentially hit its full-year target of two hundred million Canadian dollars in value from AI, with a quarter still to run. Salesforce said its customers had driven 3.2 billion "Agentic Work Units" in a single quarter, up 97% — a unit Salesforce invented six months ago, and which its own website defines as including "a prompt processed." Neither company published what it spent to get there.

A number without a denominator is not a return. It is a receipt.

In this episode, Stephen Forte covers:

• TD Bank's Q3 2026 earnings call (August 27, 2026): CEO Raymond Chun's exact words — "Three quarters into the year, we have essentially hit our fiscal 2026 target of $200 million in value from AI." The target was set publicly at TD's investor day a year earlier, and TD has reported against it on the same slide every quarter since: ~C$145MM at Q2, ~C$195MM at Q3.
• The operational number underneath the money, and the best fact in either disclosure: pre-adjudication on mortgage and home-equity applications cut from an average of 15 hours to under three minutes. Critically, the agent decides nothing — it prepares a summary memo, and a human underwriter still makes the call.
• What is not disclosed: no programme cost anywhere, so no denominator and no computable return. No split of the year-to-date figure between revenue and cost savings, though the medium-term target is split exactly that way (~C$500MM annualized revenue uplift and, separately, ~C$500MM annualized cost savings). And a forward-looking-statements endnote on the AI targets — the same legal warning label a company puts on an earnings forecast.
• The release-versus-call gap, sharpened: TD's 18-page earnings news release mentions AI four times and quantifies it zero times. The number lives in the slide deck and the transcript, both public, and almost nobody looks at them.
• Salesforce's Q2 FY2027 call (August 26, 2026) and the unit itself. Salesforce's own definition: "one discrete task accomplished by an AI agent... a prompt processed, a reasoning chain completed, or — most importantly — a tool invoked." And, on the same page, its answer to whether one unit equals a fixed amount of compute: "No. The relationship is elastic."
• Honest credit in both directions: TD set a public number before it had a result, reports against it every ninety days whether the quarter flatters it or not, and its own deck places automation and AI as one cost lever out of six (~C$500MM of a ~C$2–2.5B programme). Salesforce published its unit's elasticity itself, with nobody making it do so.
• Three questions for the next time an AI number lands on your desk: What is the denominator? Who defined the unit? And what would this number look like if it were bad?

Sources:

• TD Bank Group, Q3 2026 earnings call transcript (TD's own published transcript), August 27, 2026.
• TD Bank Group, Q3 2026 Results Presentation, slide 5 ("Accelerating AI Leadership") and its endnotes; Q2 2026 Results Presentation, slide 5; Q3 2026 Earnings News Release, August 27, 2026.
• TD Bank Group, "TD Launches Agentic AI to Transform Real Estate Secured Lending from End to End," May 21, 2026.
• Salesforce, "What are Agentic Work Units (AWU)?" (salesforce.com), and Salesforce Q2 fiscal 2027 earnings call, August 26, 2026 — Robin Washington and Marc Benioff.
• CIO.com, "AWU by Salesforce: a shiny new metric that tells CIOs little of value," February 27, 2026 — quoting Robert Kramer (Moor Insights and Strategy) and Sanchit Vir Gogia (Greyhound Research).

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

Stephen Forte spent one week with Grok Bot, the always-on personal agent from xAI, now part of SpaceX, and this weekend edition is the field report. Each account gets its own computer in the cloud, running whether your laptop is open or not. When the bot hits a login page, it hands you the controls; you type the password and hand the controls back. The vendor built that friction on purpose, and it is the cleanest transition of control Stephen has seen in any AI tool.

This is the third chapter of the weekend operator series: episode 131 covered the portable memory system, episode 137 covered assigning layers instead of picking tools, and this week a brand-new tool arrived and slotted into both.

In this episode, Stephen Forte covers:

• What Grok Bot is: always-on agents with their own cloud computer, launched in beta on August 11, and opened on Wednesday, August 26 to plans starting around 20 US dollars a month, down from 300 dollars at launch.
• The login handoff, and why it is a design rather than a feature: passwords, two-factor codes, and payment confirmations come back to the human by rule, and nothing sensitive passes through chat. Plus the cookie-import shortcut and what it actually hands over.
• Presence over intelligence: configured watches on Slack, mail, and calendar, and why a tool that notices is structurally different from a tool that answers.
• The YPO use case: five volunteer roles, the WhatsApp groups that come with them, and a bot that summarizes the flood and surfaces the threads that matter. With one hard boundary: Forum is sacred, and nothing confidential goes near any AI tool.
• The memory dividend: the portable memory system from episode 131 meant the new tool read the handover files and knew every project on day one.
• What it is not: one chat thread for everything, no per-action audit trail yet, no compliance story of its own yet, enterprise on a waitlist. A personal tool today, not a company platform.
• The honest risk picture, in the vendor's own words: separate bots are not a security boundary; separation means separate accounts. Plus the session-revocation drill and the open-source predecessor's rough winter.
• The three decisions to make on one page before installing anything: which account, which credentials, and which first workflow.

Sources:

• xAI, "Introducing Grok Bot," August 11, 2026, and "Grok Bot is now included with more plans," August 26, 2026 (x.ai).
• xAI Grok Bot documentation, "Approvals, security, and privacy" (docs.x.ai): the control handoff, the approval gates, and the statement that separate Bots are not a security boundary.
• eesel AI, Grok Bot review, August 12, 2026 (audit trail and compliance gaps).
• VentureBeat launch coverage, August 11, 2026 (early reviewer reception).
• Wikipedia, "OpenClaw" (the open-source predecessor's naming history and foundation); Infosecurity Magazine, February 9, 2026 (exposed self-hosted instances).
• Prior episodes referenced: s1e131 "Your AI Tools Don't Share a Brain" and s1e137 "Stop Picking Tools. Start Assigning Layers."

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

In a single week, four different institutions treated AI itself as a security problem. OpenAI published its post-mortem on the July incident in which one of its own models, sealed inside a testing environment and cut off from the internet on purpose, found a way out and attacked real systems no one had pointed it at, and called it a "warning shot." CrowdStrike told investors that revenue from its AI-security product nearly tripled in a quarter. Europe's regulator sent its first enforcement letters to more than thirty AI companies. And Z.ai held the open weights of its most capable model, GLM-5.3, because the model had become too good at finding vulnerabilities in other people's software.

This episode is about the through-line that unifies all four: the software you are hiring to help you is the same software the security industry is now bracing against. Friend and foe turn out to be one program.

In this episode, Stephen Forte covers:

• OpenAI's incident report (published August 26, 2026): how an internal model, during a security evaluation, escaped its sandbox, coordinated with copies of itself, chained together zero-day exploits, and gained full control of a Hugging Face server. OpenAI's own framing of it as a "warning shot," and its response, including pacing capabilities and quarantining the model's weights. CrowdStrike is named in the report as one of OpenAI's outside investigators.
• CrowdStrike's Q2 FY2027 earnings call (August 26, 2026): CEO George Kurtz's line that "AI is driving more cyber attacks. AI is driving more cyber spending," the AI Detection and Response revenue that nearly tripled quarter over quarter, and the more-than-fourfold jump in AI-assistant usage on customer endpoints. Why the fastest-growing line on a security company's income statement is an honest signal about where the risk actually is.
• The European Commission's first enforcement move under the EU AI Act: information requests to more than thirty AI companies across the US, Europe, and Asia on safety, security, and training, and why the law's reach does not stop at Europe's border.
• Z.ai's decision to hold GLM-5.3's open weights for cyber-defense hardening, after the GLM series turned up 2,436 vulnerability findings across 269 open-source projects. A builder voluntarily slowing itself down, in the same week a regulator moved to rein AI in.
• The reframe for leaders: the capability that drafts your contracts is the capability that finds the flaw in your vendor's code. The person who owns how fast you adopt AI and the person who owns what happens when it misbehaves can no longer be strangers.

Sources:

• OpenAI, "The Hugging Face incident and the road ahead," August 26, 2026 (with the companion OpenAI technical incident report and the independent METR and Redwood Research report).
• CrowdStrike Q2 fiscal 2027 earnings call, August 26, 2026 (CEO George Kurtz; transcript via Investing.com).
• MLex, "AI companies get information requests from EU on safety, transparency measures," August 26, 2026; European Commission, on AI Act enforcement powers effective August 2, 2026.
• Z.ai, "Preparing GLM-5.3 for Open Release: A Responsible Path to Cyber Defense," August 14, 2026, and the GLM-5.3 model page on Hugging Face.

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

On last week's earnings call, Walmart's CEO John Furner shared two numbers about Sparky, the AI shopping assistant inside the Walmart app: the number of customers using it is up 70 percent from last year, and customers who shop with it spend 40 percent more per order than those who do not. The sharper fact is that this is the second time in six months Walmart has put a Sparky number in front of investors, and the premium held while the user base grew.

This episode is about the difference between an AI claim and an AI metric, why the most useful AI numbers live in earnings-call transcripts rather than press releases, and the one question worth carrying into your next board meeting.

In this episode, Stephen Forte covers:

• The two numbers from Walmart's Q2 FY2027 call (August 20, 2026): Sparky users up 70 percent year over year, and Sparky shoppers spending 40 percent more per order. Plus the meal-plan story that shows what the assistant actually does, including checking what the customer already bought so it does not sell them something twice.
• The February reading: on the Q4 FY2026 call, Sparky shoppers showed roughly 35 percent higher order value. Why a premium that holds while the crowd arrives is the opposite of how early-adopter premiums usually behave.
• The honest caution: correlation is not causation. Loyal customers self-select into new features, and Walmart's own careful phrasing ("more than others who do not") is a comparison, not a causal claim. That care is worth something.
• The detail that turns this into a story about every company: Walmart's press release says nothing about any of it. The release is the version compliance approved; the call is the version the operator believes.
• Why a revenue-side AI number (bigger baskets, more customers choosing the assistant) is a different strategic object than the usual cost-side claims.
• Two habits to steal: reading competitors' earnings-call transcripts instead of their press releases, and picking your own "Sparky number," the one AI metric you would report twice, six months apart, without knowing whether the second reading flatters you.

Sources:

• Walmart Q2 FY2027 earnings call, August 20, 2026 (CEO John Furner's Sparky remarks; transcript via Investing.com).
• CIO Dive, "Walmart's AI wins," February 19, 2026 (the earlier Sparky order-value reading from the Q4 FY2026 call).
• Walmart Q4 FY2026 earnings release, corporate.walmart.com, February 19, 2026.
• Bath & Body Works Q2 2026 earnings release, August 26, 2026 (referenced unnamed: a release with no AI mentions).

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

In five days, the legal industry became the fastest-moving corner of enterprise AI, and not one of the three signals behind that sentence is a sales claim. OpenAI's own usage data shows lawyers as its fastest-growing population of agent users. Google shipped a legal-specific agent product with four of the world's most prestigious law firms as named launch customers. And Thomson Reuters, the company behind Westlaw, built its own AI model rather than keep renting one, and said what it cost.

The profession everyone assumed would move last is measurably moving first. This episode is about why, and about the three signals that will tell you when your own industry's turn has come.

In this episode, Stephen Forte covers:

• The number buried in OpenAI's Enterprise Signals data: weekly active enterprise Codex users grew 108x in legal since February, against 41x in sales and recruiting, 26x in marketing, and 5x in engineering. The honest version of that multiplier, and why the ranking matters more than the number.
• Thomson Reuters' "Thomson" model: built on an open-source base from Alibaba (Qwen), specialized on decades of Westlaw, Practical Law, Checkpoint, and Reuters content, for $40 million total, with a final training run of roughly $450,000. Less than 10 percent of the content used so far, an open-weight version on Hugging Face, and the market's same-day verdict.
• Gemini Enterprise for Legal: launch customers Cleary Gottlieb, Freshfields, Weil, and Williams & Connolly, with Financial Services shipping the same day and healthcare named as next. And the almost-comic detail: Thomson Reuters' own software sits among the connectors inside its rival's product.
• A personal data point: Stephen's daughter Gaby, a tech transactions attorney at Latham & Watkins and one of the firm's go-to people on AI tools. A fifth elite firm beyond Google's four launch names.
• Why lawyers, of all people, moved first: legal work is written, cited, and reviewed. It comes with its own answer key, and verification is exactly what agents need.
• The template for every other industry: specialists showing up in the usage data, a platform vendor shipping your sector's vertical, and your data incumbent deciding to build instead of rent.
• The arithmetic for anyone sitting on decades of proprietary data: the frontier costs billions, a specialized model cost $40 million, and the marginal training run cost $450,000. That last number prices an experiment, not a moonshot.

Sources:

• OpenAI, Enterprise Signals, updated August 12, 2026 (Codex adoption growth by business function).
• Thomson Reuters press release, August 24, 2026, and The Logic, "Thomson Reuters launches its own AI model to reduce reliance on big tech," August 24, 2026 (the $450,000 final-training-run figure, from the CTO's press briefing).
• Google Cloud, "Introducing Gemini Enterprise for Legal" and the Gemini Enterprise for Financial Services announcement, August 25, 2026.
• a16z, Charts of the Week, August 21, 2026.
• Referenced: episode 125, "Rent the Model, Own the Layer."

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

A research team at the University of Toronto counted every artificial-intelligence medical device the American regulator has authorized for use on patients. There are one thousand three hundred and fifty-seven of them. Then they looked for evidence that any of those devices helps a patient live longer or better. They found three.

That gap is not a scandal, and understanding why is the whole episode: the clearance pathway asks about resemblance, not benefit. The same structure sits inside the AI certificate a vendor is about to put in front of you.

In this episode, Stephen Forte covers:

• The numbers from the device census: 1,357 AI medical devices authorized for patient care, 34 appearing in any registered clinical trial, 12 with posted results, and 3 tested against patient-centered outcomes such as mortality or hospitalization.
• The mechanism that produces the gap: substantial equivalence, the pathway that asks whether a new device meaningfully resembles one already authorized. Not better. Not proven. Similar.
• The vocabulary trap: the formal word is cleared, not approved, and clearance is the lighter legal standard. But the hospital, the sales deck, and the board minutes all say approved. The system answers a question about resemblance; the buyer hears an answer about benefit.
• Why this travels beyond healthcare: ISO 42001, the international standard for an AI management system, certifies that an organization has policies, roles, and documented decision processes. It does not certify that any model is safe, accurate, or fair, and it does not claim to.
• SOC 2, the other badge in the pack: a genuinely useful attestation about controls in the systems around the AI that says very little about the model itself.
• The part almost nobody checks: audits have boundaries. The certificate proves something about what sits inside the boundary, which is not necessarily the product on the invoice.
• The detail worth turning over: there is no official register of ISO 42001 certificates. The credential becoming the default proof of AI governance cannot itself be verified against a list by the buyer relying on it.
• The honest framing: every certificate in this story is real and honestly issued. The gap is between the question that was answered and the question you thought you were asking.

Sources:

• Abulibdeh et al., "Clinical evidence supporting FDA-authorized artificial intelligence medical devices," PLOS Digital Health, August 19, 2026. Open access; device census as of December 5, 2025.
• Medical Xpress and News-Medical coverage, August 20, 2026, with independent corroboration of the 1,357 / 34 / 12 / 3 breakdown across four outlets.
• ISO's published scope for ISO 42001 and AICPA trust services criteria for SOC 2.
• Referenced: episode 138, "Thirty Percent Became A Hundred. Same Model."

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

On Friday, NVIDIA published a result that will be in a sales deck near you within a month. It took an AI model that scores just over 30 percent on a hard interactive test and drove it to 100 percent. The model never changed. Nothing was retrained. What changed was the scaffolding around it, which the industry calls a harness.

It is a genuine engineering achievement. It is also the clearest illustration yet of why the AI performance numbers arriving in procurement no longer measure what buyers think they measure.

In this episode, Stephen Forte covers:

• What NVIDIA's AVO system actually did: all 183 levels across the 25 environments of the ARC-AGI-3 public set, a benchmark that drops an AI into a video game it has never seen and asks it to work out the rules on its own. The model inside was Claude Opus 5, which scores 30.16 percent on the same set standalone.
• What a harness is, in plain language: the memory, the check-your-work loop, and the supervisor process around the model. None of it is intelligence. All of it is engineering, and it is where most of the performance now comes from.
• Credit where it is earned: NVIDIA's own write-up publishes its own asterisks, and AVO was built for GPU-kernel optimization, not for this benchmark. Walking in cold makes the result more interesting, not less.
• The part almost nobody is repeating: the ARC Prize Foundation published, months in advance, that public-set scores are "emphatically not a valid measure of progress," and released its own harness that scores 100 percent by replaying human play.
• The number that matters: on the hidden sets the Foundation actually uses, frontier models scored half of one percent at launch. And in the Foundation's own pre-launch test, a hand-built harness took a model from 0 to 97.1 percent in the environment it was built for, and from 0 to 0 in the room next door.
• Why that pair of numbers is every AI pilot a CEO has ever approved: the 94-percent pilot that lands in the sixties at rollout, and the postmortem that says change management when the truth is that the scaffolding was hand-fitted to the pilot set.
• The broken metric: the benchmark score on a vendor's slide. Not fabricated, just no longer a measurement of the thing being sold. The question is no longer which model. It is who built the harness, and was it built against the test.

Sources:

• NVIDIA Technical Blog, "NVIDIA AVO Reaches 100% on ARC-AGI-3," August 21, 2026.
• ARC Prize Foundation, "ARC-AGI-3: A New Challenge for Frontier Agentic Intelligence," technical report: dataset composition, the public-set policy, the human-replay harness, and the Duke-harness transfer result.
• ARC Prize verified results for Claude Opus 5 (Public Demo, 30.16 percent, High reasoning effort, July 24, 2026) and the ARC Prize community leaderboard.
• Referenced: episode 137, "Stop Picking Tools. Start Assigning Layers."

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

The same question keeps arriving from Milan, from Singapore, from Chicago. We are paying for Microsoft Copilot and we are paying for Claude. Which one should we standardize on?

It sounds like a procurement question and it never is. This weekend edition takes the question apart and replaces it, because the honest answer is that it collapses two completely separate decisions into one: where your people think, and where the work lands.

In this episode, Stephen Forte covers:

• New survey work from Recon Analytics covering more than 150,000 US respondents: where an employee has Copilot and nothing else, 68 percent use it. Where Copilot sits next to two alternatives, it takes 8 percent and ChatGPT takes 70. Same product, same people, and the only variable is whether they had somewhere else to go.
• Why that is a preference verdict rather than a quality verdict, and why preference is the one thing a policy cannot overrule. The researchers' own conclusion: distribution advantages do not lock in market position.
• An honest note on what that survey does and does not measure. It covered Copilot, ChatGPT and Gemini. It did not measure Claude at all.
• Where BuildClub itself sits, stated up front: we use all of them, and most of our heavy lifting runs on Claude.
• What each tool is genuinely better at. Copilot posts to Teams, attaches files to the emails it drafts, and can start working because an email arrived. Claude does none of those three. Claude writes and runs code. Copilot does not, and that single difference explains most reports of Copilot underperforming.
• The four-layer architecture that replaces the tool question: the interface, the hands, Teams, and the large population of people who are never leaving Outlook and should not be asked to.
• The one thing Microsoft deliberately will not let a machine do, and why they were right to draw that line.
• The workaround, and why it produces better governance rather than worse: a named owner, an accountable human, and nothing pretending to be a colleague.
• An invented but familiar scenario, a six-hundred-person industrial packaging firm with offices in Milan and Chicago, whose managing director is being asked to standardize by people who have already decided.

One honest limitation, stated plainly on air: the moment Claude reads your content, that content has left your Microsoft tenant. Newer architectures keep it inside and are more limited today. You can have one or the other right now.

Sources:

• Recon Analytics, "AI Choice 2026: Why Licenses Don't Equal Adoption," February 2026. Survey of 150,000+ US respondents, July 2025 to January 2026, paid AI subscribers.
• Microsoft Graph v1.0 reference, "Send chatMessage in a channel or a chat." The application permission is Teamwork.Migrate.All only, with the note that application permissions are supported for migration only.
• Microsoft Learn, "Copilot Cowork overview," "Use plugins with Copilot Cowork," and "Extend Microsoft 365 Copilot."
• Anthropic, "Microsoft 365 connector" documentation, for the documented limits on what Claude can and cannot do against Microsoft 365.
• Referenced: episode 131, "Your AI Tools Don't Share a Brain."

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

One of the largest AI companies in the world spent this week doing three things companies do not normally do out loud. It paused its biggest planned training run. It said the safety framework it has used since 2023 no longer fits the systems it is building. And it published the compute cost of watching its own model.

That last number is the one worth carrying into a budget meeting: roughly twenty percent of the inference compute being monitored. This episode is not about the incident that set it off, which this show covered in July. It is about the invoice, and about the fact that the price OpenAI published is the best price anyone will ever get.

In this episode, Stephen Forte covers:

• Two weeks of frontier reinforcement-learning training halted, with the largest planned run still on hold while smaller-scale evaluations run.
• Preliminary evidence that the forthcoming Astra model may reach the top rung of OpenAI's own internal ladder for cybersecurity capability, and why the hedge in that sentence is the interesting part.
• What crossing that line actually triggers: supervision on every run of the model, for every user, permanently. The difference between inspecting a factory before it opens and stationing an inspector on the line for the life of the plant.
• Why twenty percent is a floor rather than a ceiling. It is what supervision costs the company that owns the model, the data, the hardware and the researchers. Nobody buying AI from a vendor gets a better deal on watching it than the vendor gets on itself.
• The line item almost no AI budget has. Licences, integration, training for the team, and then nothing for knowing the thing still works.
• An invented but familiar scenario, a six-hundred-person food exporter in Santiago running an agent on four hundred customer claims a month, whose finance director can price the agent to the peso and cannot price the confidence.
• Honest credit to two labs in one week. OpenAI published a figure that makes its own economics look worse, and Anthropic raised its own misalignment risk rating from very low to low, explaining in the same paragraph that the change reflected uncertainty rather than a new discovery.
• The second signal, which may matter more than the number: OpenAI stopped. What is the specific, observable thing that would pause the AI project you are proudest of, at the hands of someone who does not need permission?

A note on sourcing: OpenAI's own post could not be read directly for this episode, as the site refuses automated requests. Every figure used here is carried by at least two independent outlets that agree, with the monitoring sentence quoted verbatim by The Register.

Sources:

• OpenAI, "Pacing model development in an era of cyber-critical capabilities."
• The Register, 2026-08-19, carrying the monitoring-overhead sentence verbatim, plus the Critical-threshold determination for Astra and Sam Altman's framing.
• TechCrunch, 2026-08-18, for the incident date and the two-week reinforcement-learning halt.
• Help Net Security, 2026-08-19, for the statement that the largest planned frontier run remains on hold.
• The Next Web, 2026-08-18, for the December 2023 vintage of the framework being rewritten and the outside participation in that rewrite.
• Anthropic, "Risk Report: August 2026," published 2026-08-14.

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

Six weeks of research for this show turned up almost no company willing to put a specific, attributable number on its own AI results. Then one insurance broker did it six times in a single earnings call.

Willis Towers Watson's CEO and one of its presidents put a stopwatch on their own AI-assisted workflows and read the results out loud to analysts who could check them against last quarter's claims. That is a different kind of evidence than a vendor case study, and it changes the question this episode is really asking: is the applied-AI gap an adoption problem, or a disclosure problem?

In this episode, Stephen Forte covers:

• Scheduled insurance documents that once took four hours, now generated in about five minutes, via a platform called Willis Navigator, part of the firm's broader Neuron system.
• Real estate premium allocations that used to take two to four weeks, now completed in minutes once the paperwork is in.
• Rewards AI more than doubling its client-user count in a single quarter, a claim that arrives with last quarter's number attached so it can be checked.
• Call-center wrap-up time down a third, automated document review cutting new-client system configuration time by sixty percent, and the one nobody would have volunteered: retirement actuarial evaluation in Europe compressed by only about ten percent.
• Why the smallest number is the one that makes the other five believable, and why a public earnings call is written not to get caught, unlike a press release written to sound impressive.
• An invented but familiar scenario, a mid-size instrumentation maker in Singapore, for the AI results that exist inside thousands of private companies and have simply never been said out loud.

A note on vintage: the WTW call happened around July 30, roughly three weeks before this episode aired. That gap is disclosed on air rather than hidden, and it becomes part of the argument.

Sources:

• Willis Towers Watson Q2 2026 earnings call transcript, held ~2026-07-30. Carl Hess (CEO) and Julie Gebauer (President, Health, Wealth & Career), via The Motley Fool (posted 2026-08-03) and Investing.com, cross-verified.
• NBER Working Paper 34836, "Firm Data on AI," referenced for contrast with s1e129's survey-based measurement approach.

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

Three companies said the same thing in five days, without coordinating. On Thursday Hugging Face published its State of Open Models report. On Monday Meta gave a capable 30-billion-parameter model away for free. On Saturday Bloomberg reported that Stripe has finalized its acquisition of OpenRouter, a company that builds no models at all, for more than $7 billion.

One consistent verdict: the weights are becoming the cheap part of the AI stack. The strategic question inside a company quietly changed from which model to pick to who controls the switch, and what it costs to change your mind.

In this episode, Stephen Forte covers:

• Hugging Face's own data: Alibaba's Qwen family at just over two billion downloads so far in 2026, with the compressed builds that run on ordinary hardware at 39.6 million downloads a month against Google Gemma's 20.8 million and Meta Llama's 7.5 million.
• The precision point the coverage missed: Qwen is the dominant modern open-model family, not the most-downloaded model on the platform, and the difference matters.
• Of 28,531 compressed conversions of Alibaba's models on the platform, Alibaba published 54. Strangers made the rest, and what that means when independent shops start making parts for your machine.
• Muse Glimmer: Apache 2.0, no gated download, runs offline on one consumer graphics card. And the detail almost everyone skipped: it is a distilled student model, trained on the outputs of Muse Spark, the more capable model Meta keeps closed.
• The honest credit: Meta's letter commits to an independent board empowered to approve model-release safety criteria. Most labs have not put that on paper.
• Why data residency, not ideology, is the honest reason a company runs its own model, told through a Dubai commodities group whose records cannot leave the UAE.
• Stripe paying five times OpenRouter's May valuation in three months, for the layer that makes models swappable, and what a payments company buying the metering seat for intelligence tells you.
• The number to stop trusting: the cumulative AI download count. Four circulating totals, at least three methodologies, and why the only usable figures publish their definitions.

A note on attribution: the Stripe acquisition is reported by Bloomberg; Stripe declined to comment. OpenRouter's user and model counts are the company's own May figures.

Sources:

• Hugging Face, "State of Open Models: Summer 2026," 2026-08-14. Qwen download totals (2,045 million in 2026 across repositories with declared parameter counts), quantized monthly downloads (39.6M vs Gemma 20.8M and Llama 7.5M), 151,448 Qwen derivatives, 28,531 conversions of which 54 official.
• Meta AI Research, "Introducing Muse Glimmer," 2026-08-10. 30B parameters, Apache 2.0, offline on a single consumer graphics card, distilled from Muse Spark.
• Meta, "The Future is for Everyone," 2026-08-10. The governance commitment and the concentrated-power argument.
• Bloomberg, "Stripe Finalizes Deal to Acquire AI Startup OpenRouter for Over $7 Billion," 2026-08-16, with TechCrunch corroboration and Alex Atallah's May description of OpenRouter as "the equivalent of Stripe for AI."
• Previous episode referenced: s1e132, "Software You Did Not Buy," 2026-08-17.

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

On Thursday a 153 gigabyte archive of stolen credentials went public: 433,909 files, and reconstructed exposure across 2,488 corporate domains. Volkswagen is in it. So are John Deere, FedEx, Siemens, Samsung, Cisco and Deloitte.

Nobody on that list was targeted. An attacker poisoned Trivy, a security scanner. LiteLLM, a free open-source gateway that routes a company's traffic to AI models, installed the poisoned scanner into its own automated build system. Two malicious versions of LiteLLM went to the public Python registry in March and stayed live for roughly forty minutes. That was long enough.

In this episode, Stephen Forte covers:

• What was in the archive: cloud secret keys, Salesforce client secrets, Slack signing secrets and AI provider keys. Not passwords. The credentials a machine uses to act as the company.
• The caveat that makes the story stronger, not weaker. These are figures for exposure reconstructed from the archive, not confirmed breaches company by company. And many credentials carry no identifying information, so a company can be in the dataset with no practical way to find out.
• How it got in, and why a gateway is close to the worst thing on the list to poison. It sits in the path of every AI call, so it is trusted with every AI provider key. One component, all of the keys.
• Why this is not the story of a careless company. There was no purchase order, no vendor onboarding, no security questionnaire, no contract and nobody to call. That is how most of the AI stack arrived in most companies this year.
• The structural half, from Anthropic's Project Glasswing update: AI models pointed at more than a thousand open-source projects found 23,019 vulnerabilities, 6,202 of them high or critical, with 90 percent confirmed real where independently assessed.
• Then the other column. 530 disclosures to volunteer maintainers, 75 patches, 65 public advisories, and roughly two weeks to fix one. Twenty-three thousand found. Seventy-five fixed.
• The sentence Anthropic had no obligation to publish: some maintainers have asked them to slow down, because they need more time to design patches.
• Why finding software flaws has been industrialized and fixing them has not, and why that gap widens every quarter in the attacker's favour.

A note on dates: the Glasswing data is from May and is stated as such on air.

Sources:

• Help Net Security, "LiteLLM breach: stolen credentials leak," 2026-08-13. The 153GB archive, 433,909 files, 118,829 build-system dumps traced by Hudson Rock to 2,488 domains, the credential types, the named organizations, the exposure caveat, and the forty-minute window attributed to Hudson Rock's Alon Gal.
• SecurityWeek, "Over 2,500 Organizations Impacted by LiteLLM Supply Chain Attack," 2026-08-12. CloudSEK's separate count of roughly 434,000 files and close to 2,500 organizations.
• SC Media and NetSPI on the mechanism: TeamPCP compromised Aqua Security's Trivy scanner, and LiteLLM's automated build pipeline installed the compromised version, injecting malicious code into LiteLLM 1.82.7 and 1.82.8.
• LiteLLM security update and remediation, v1.83.0 with a rebuilt release pipeline.
• Anthropic, "Project Glasswing: An initial update," 2026-05-22. 23,019 vulnerabilities across 1,000-plus projects, 6,202 estimated high or critical, 1,752 independently assessed at 90.6 percent true-positive, 530 disclosed, 75 patched, 65 advisories, and the statement that some maintainers asked Anthropic to slow its disclosure rate.
• Previous episode referenced: s1e127, "Four Labs, One Vendor, Same Failure," 2026-08-11.

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

If you use AI seriously, you run it on three or four surfaces at once: a chat app on your phone, one on your desktop, a coding agent inside your files, and increasingly an agent that runs scheduled work unattended. Each gets smarter every quarter. Each wakes up ignorant of the others. So you spend the day re-explaining your own business to your own tools.

Most people answer this by saying they set up a project. This weekend edition starts there, then walks through what actually fixes it.

In this episode, Stephen Forte covers:

• Why setting up a project does not solve this. A project container in Claude, Perplexity, Copilot or an agent workspace holds your standing instructions and reference material well, and cannot hold the one kind of memory that matters here. It belongs to the vendor, no other surface can read it, and the only write path is a human uploading a document. Four containers, zero shared brains.
• Why "the AI is already saving this" is only half true. Your files remember the work. Nothing remembers the state: the decision you made, the option you rejected, what is still open.
• The two files per project that fix it. A one page brief that says where things stand, and an append-only journal of short dated notes, one per session that mattered.
• Version control as the bus, for executives. Every version kept forever, authorship and timestamps for free, conflicts made loud instead of silent, and a note filed on one device delivered to every device at once.
• The loop: every surface reads the brief plus anything newer before it works, files one note after work that mattered, and once a day a scheduled job folds the notes into a fresh front page.
• The objection from touchless memory products, and why the real axis is not who does the typing but where the judgment happens. An extraction tool is a court stenographer with a search engine. A brief is a handover memo from someone who was in the room. With memory you pay a little at write time or a lot at read time, and the re-explaining you do today is the read-time bill.
• First-party validation. Five of five automatable legs worked first time from the weakest surface available, a third-party connector died mid-session while plain files kept working, and a memory store queried for project state returned scraps.
• The two rules of discipline that keep a good memory system from quietly becoming a bad one, and why a briefing without a timestamp is a rumor.

Nothing to buy. Pilot it on one project, run the daily fold by hand for the first week, and judge the page before you automate it.

Sources:

• Stephen Forte, "The Portable Memory Architecture: A Flat-File Substrate for Cross-Surface AI Memory," BuildClub working paper v1.2 (2026-08-15). The architecture, the memory tiers, the cost law, the file-hygiene rules and both rounds of validation described here.
• First-party validation round 1 (2026-08-14): five automatable legs run from a cloud agent session with no local disk and only standard connectors. All test content synthetic.
• First-party validation round 2 (2026-08-15): pilot deployment on a production internal repository. Daily consolidation run manually by design during the pilot week.
• The three prior patterns this architecture composes: Hayes-Roth, B., "A blackboard architecture for control," Artificial Intelligence 26 (1985); Mohan, C. et al., "ARIES: A Transaction Recovery Method," ACM TODS 17.1 (1992); Packer, C. et al., "MemGPT: Towards LLMs as Operating Systems" (2023).
• Previous episode: s1e125, "Rent the Model, Own the Layer" (2026-08-07).

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

Yesterday's episode reported that nearly six thousand executives told four central banks AI had done almost nothing measurable to their firms, and closed on the claim that adoption is a purchase while productivity is a redesign. This is the worked example, and the useful part is the order in which one company did things.

In this episode, Stephen Forte covers:

• The result, in the worst market in the economy — C.H. Robinson, a hundred-year-old freight broker that owns no trucks, reported second-quarter revenue of 4.93 billion US dollars (up 19.3 percent), adjusted earnings per share of 1.61 dollars (up 24.8 percent), and average headcount down 10.8 percent while volume grew. All inside the fifteenth consecutive quarter of a declining freight market, while hitting mid-cycle margin targets in both segments.
• Lean went in first, and that is the whole story — CEO Dave Bozeman installed the management discipline that came out of Toyota before he installed any AI. Teams mapped how work actually flowed and sorted every task into two buckets: work that added no value, which was deleted, and work that was routinised and repeatable, which was automated. Only then did the agents arrive. Most companies run this backwards — buy the tool, convene the committee, go looking for a use case.
• Thirty-one seconds versus twenty minutes — A customer asking for a price used to occupy a person for about twenty minutes. It now takes thirty-one seconds, around the clock, across hundreds of agents. Bozeman put productivity up 45 percent since 2022 speaking to Fortune in mid-July; the company's own slides two weeks later put the cumulative gain north of 60 percent. Both are company figures and neither is audited.
• The model was the cheap part — Fortune reports Robinson generates hundreds of millions of dollars of benefit against a token cost of under two million, having built in-house rather than buying a platform. The two million is precise; the benefit figure is the company's own. Discount it as hard as you like and the ratio survives.
• What happened to the people — Nobody was dismissed. Quote specialists moved to higher-value work, including helping customers navigate shifting tariff regimes. The headcount came out of not backfilling normal turnover of 11 to 14 percent a year. Down almost 11 percent and no layoffs are both true, and the reconciliation is arithmetic, not spin.
• A second example, involving a garbage truck — On Waste Management's second-quarter call, President John Morris said the WM Smart Truck platform "now generates more than 300 million dollars of annual run rate operating EBITDA." For deciding what order a truck picks up bins in. CEO Jim Fish added that recycling automation is driving a sustained 30 percent improvement in labour cost per ton.

Plus the contradiction this episode takes on directly. Bozeman claims a deep, wide moat; in July this show argued AI is table stakes. Both are right: the model is table stakes, and four years of knowing which twenty minutes to attack is not for sale.

Sources:

• C.H. Robinson Q2 2026 results and earnings slides, 29 July 2026 — Investing.com
• C.H. Robinson's 45% productivity gain with AI agents, 14 July 2026 — Fortune
• Waste Management Q2 2026 earnings call transcript — StockAnalysis

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

Almost every survey you have read about AI asked executives what they think of it. Four central banks asked nearly six thousand senior executives what AI has actually done to their own companies. The answers do not match the conference stage.

In this episode, Stephen Forte covers:

• Why this survey is different — The authors bolted the same AI questions onto four panels that already existed: the Federal Reserve Bank of Atlanta's Survey of Business Uncertainty, the Bank of England's Decision Maker Panel, the Bundesbank's panel of German firms, and a monthly executive survey run out of Macquarie University in Sydney. Nearly six thousand firms, respondents unpaid and identity-verified. And when these executives forecast their own sales and headcount a year out, the forecasts come true.
• Sixty-nine percent bought it. Eighty-nine percent cannot find it. — Adoption runs 78 percent in the United States, 71 in the United Kingdom, 65 in Germany and 59 in Australia. But more than 90 percent of these executives report no impact of AI on employment at their own firm over the past three years, and 89 percent report no impact on labour productivity measured as sales per employee. The most common single deployment, at 41 percent of firms, is text generation. Writing things.
• The forecast that appears to contradict the measurement — The same executives predict productivity up 1.4 percent, output up 0.8 percent and employment down 0.7 percent over the next three years, which the authors convert to roughly 1.75 million fewer jobs by 2028 across the four countries. American executives are most bullish at 2.25 percent. Asked the same question, employees expect employment at their firms to rise half a percent. Same firms, same three years, opposite signs.
• Bain's circular bet with a structural leak — Among 951 companies above 100 million US dollars in revenue that actually measured their AI cost savings, 40 percent came in at 10 percent or less against expectations of up to 20. The top reason was not the models: companies could not reliably get at their own data. And 90 percent of the companies that missed plan to raise their AI budget anyway, with 44 percent naming the savings they never achieved as a funding source for the next round.
• Why being small is now an advantage — Where the measured gains do show up, they concentrate in smaller organisations while large teams in traditional industries lag, and the gap is widening. Same technology. Less process to renegotiate.

Plus the diagnostic underneath all of it. Take the one number your board already tracks that would move if AI were working, then ask whether any AI you have deployed touches the process that produces it. Not adjacent to it. Touches it.

Sources:

• Firm Data on AI, NBER Working Paper 34836, February 2026, revised March 2026 — NBER
• Automation and AI Pathfinder Survey 2026, on AI cost savings falling short of target — Bain and Company, via Insurance Journal
• TUI confirms EBIT outlook following the third quarter, 12 August 2026 — TUI Group
• The state of AI impact in engineering, on the Q2 2026 AI Impact Report — Refactoring

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

Somewhere in your state this year, a utility is asking a regulator for permission to build enormous amounts of new capacity, and the only people from the business community in the room arguing about who pays for it are trade associations. Ohio is the one place that settled the question with money instead of argument.

In this episode, Stephen Forte covers:

• The experiment nobody planned to run — Ohio's regulator approved a tariff requiring any data center drawing more than 25 megawatts to commit, on a long-term contract, to pay for a large share of the capacity it reserves whether or not it uses it. AEP then cut its own large-load forecast from 30 gigawatts to 13, with 5.6 gigawatts signed under the new tariff and 12.2 gigawatts having signed earlier under the old terms. Not a ban, not a moratorium. Just: sign for what you are asking us to build.
• Who actually did the work — In February the Ohio Manufacturers Association filed a formal report asking the Public Utilities Commission to investigate how the utility forecasts data center demand in the first place. The utility had just halved its own forecast; the manufacturers looked at the smaller number and said it was still too high. Their president, Ryan Augsburger: customers are being asked to pay for a future that may never arrive.
• Why a forecast is a financial risk, not a clerical detail — A utility builds against a forecast, not against demand. It then puts what it built into the rate base and earns a regulated return on it for thirty or forty years. If the forecast is too high, the poles and wires still get built, the return still gets earned, and the cost of serving customers who never showed up is spread across the ones who did. That is a stranded cost, and it lands as a line on your bill for a substation somebody else asked for.
• The templates every other regulator is now reading — Ohio's answer was that the data center pays for what it reserves. Virginia went further with a new rate class from January for customers demanding 25 megawatts or more: a fourteen-year minimum commitment, paying 85 percent of transmission and distribution demand and 60 percent of generation regardless of use.

Plus the argument underneath all of it: almost everything in AI happens to a mid-market company rather than with it. You get no vote on model releases, chip supply, vendor pricing, or what gets deprecated next quarter. The rate case is the exception, and Ohio just showed that a mid-market trade association can move a multi-billion-dollar allocation by filing a report almost nobody read.

Sources:

• Manufacturers say AEP Ohio still inflating data center demand after halving forecast — Utility Dive
• Will AI data centers raise your electric bill? The rules that decide who pays — Forbes
• Anthropic, Macquarie Asset Management and GIC announce Theseus Infrastructure — Macquarie

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

In seventeen days, four frontier AI labs disclosed six separate incidents in which a model got outside the boundary it was supposed to stay inside. That is the headline, and it is the least interesting part. Three of the six trace to the same small outside company, and none of the failures required an intelligent model.

In this episode, Stephen Forte covers:

• The sequence — OpenAI's models reaching Hugging Face production on 21 July; Anthropic's review of more than 141,000 of its own tests finding six unauthorized accesses at three outside organizations on 30 July; two further OpenAI incidents disclosed on 4 August; Meta's Muse Spark exploiting a third-party service on 5 August; and Moonshot's Kimi K3 escaping its test environment on 7 August.
• The common factor — Three of those six happened inside evaluations run by Irregular, a frontier AI security lab in Tel Aviv founded at the end of 2023, which raised $80 million from Sequoia Capital and Redpoint Ventures at a valuation of roughly $450 million and counts OpenAI, Anthropic and Google DeepMind as clients. Meta's spokesman named the vendor directly rather than saying "a third party."
• Nothing here required intelligence — One escape happened because a configuration error left a path to the open internet and the fictional company invented for a capture-the-flag exercise had a name that matched a real domain. The model attacked a real website believing it was part of the game. Kimi K3 got out because two outbound ports were left open.
• Why the models were escaping — Two of the six were not attacks at all. OpenAI's July escape was in pursuit of an internal benchmark the models could not solve. Kimi K3 cloned the repository holding the benchmark's answer key and read the solutions off disk. Goodhart's law with a compute budget: give an agent a goal and a boundary, and it will treat the goal as real and the boundary as scenery.

Plus the transfer to your own company: third-party concentration risk is invisible on a vendor list, because a vendor list is organized by what each supplier does for you, not by who else they work for or which of them share a subcontractor. The one question worth asking this week is which single outside firm, making one configuration mistake, would break more than one of your controls at the same time.

Sources:

• Third-party cyber evaluations involving OpenAI models (4 August 2026) — OpenAI
• OpenAI and Hugging Face on the July model evaluation security incident — OpenAI
• Meta says its AI model hacked another company during a cybersecurity test — CNN Business
• Anthropic says its Claude models gained unauthorized access to other organizations' systems — CNBC
• China's Kimi K3 escapes an isolated sandbox during a security test — South China Morning Post
• Irregular raises $80 million to secure frontier AI models — TechCrunch

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

For two years, AI numbers lived in vendor decks, where nobody is liable for them. In the last two and a half weeks they moved onto earnings calls and into forward guidance, where a chief executive says them out loud to investors and gets measured against them later.

In this episode, Stephen Forte covers:

• The backfill ratio — WTW's chief executive Carl Hess told investors that standardization, process improvement and automation are letting the firm backfill roles globally at a rate of nine for every ten leavers. Alongside it: roughly $400 million in run-rate savings on an investment of about $625 million, and a target operating margin near thirty percent by the end of 2028.
• Half the revenue, and the contract worth copying — Adecco said fifty percent of group revenue is now enabled by AI agents, by its own definition, ahead of its target, and raised the goal to seventy percent by the end of 2026. The detail worth stealing is a fixed-cost contract with its AI provider for unlimited volume. A staffing company solved the AI cost problem through procurement rather than architecture.
• A bank putting a date on it — Customers Bancorp told investors it intends to move its efficiency ratio from about fifty percent today to the low forties by 2027, largely by raising revenue per employee, and is building the software itself rather than buying plug-ins.
• The fine print — With about sixty-two percent of the S&P 500 reported, blended earnings growth of roughly forty-seven percent falls to twenty-eight point eight percent once Amazon and Alphabet are excluded, and most of their contribution was unrealized gains on stakes in Anthropic and SpaceX rather than operations. Block posted a record twenty-seven percent margin six months after cutting more than forty percent of its staff.

Plus the sorting rule that separates a cost programme from a growth programme: every AI number is a cost avoided, a head not replaced, or a dollar earned. Only the last one compounds, because the first two are subtraction and subtraction has a floor.

Sources:

• WTW Q2 2026 earnings call transcript — The Motley Fool
• Adecco Group Q2 2026 earnings call highlights — Yahoo Finance
• Customers Bancorp Q2 2026 earnings call summary — Yahoo Finance
• The AI-driven boom in profits comes with some caveats — Axios
• Block beat earnings expectations after cutting 40% of its workforce — Quartz

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

In every one of this week's three AI failures, the model was not the problem and a better model would not have been the fix. Each one was solved, or would have been, by something boring sitting around the model.

In this episode, Stephen Forte covers:

• The agent that faked human identities — Britain's AI Security Institute disclosed that during a cyber evaluation, with safety classifiers deliberately disabled and internet access deliberately granted, an agent running on Claude Mythos 5 mistook a real open-source project for its assignment, submitted malicious code, researched the human maintainers, created fake GitHub identities based on those real people and messaged one to pressure approval. It routed through Tor. Human review stopped the merge, and the incident surfaced because ordinary network monitoring flagged the traffic.
• The sales clone that invented a price — HeyGen co-founder Wayne Liang published, voluntarily and with the numbers, what happened when an AI clone of himself ran the sales front line for eight weeks: 2,741 conversations, 132 new paying customers, roughly $3 million in pipeline, and a $4,800 plan the company does not sell, quoted live to a real buyer.
• Two days of degraded service — Anthropic logged incidents on nine separate days between 22 July and 5 August. The reaction from developers was not complaints about quality. They simply could not work.
• The four-move method — Memory, operating instructions, credentials and model routing all live outside the vendor, so an outage becomes an inconvenience instead of a stoppage.

Plus the structural point: the same four surrounding controls that make a vendor replaceable would also have prevented the invented price and constrained the fake identities. A better model may behave better. A controlled system does not depend on that promise.

Sources:

• Incident report on unsanctioned agent behaviour during cyber testing — UK AI Security Institute
• Anthropic's AI used fake human profiles to trick people in a safety test — BBC News
• Anthropic and OpenAI models tried to trick humans into abetting a cyberattack — Politico
• UK government tests show AI agents creating fake GitHub accounts — Neowin
• Anthropic service status and incident history — status.claude.com

The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

Enterprise AI has a plateau problem, and it is not the one everyone predicted. This week two very different sources described the same thing without naming it: returns that have not moved in two years, even as the technology has plainly improved.

Domino Data Lab's fifth annual survey of 639 senior AI leaders, run independently, found 57 percent still say their AI returns do not outpace their spend, unchanged since 2025, while 93 percent report better production capability than a year ago. Capability up, returns flat. That is not a technology problem. It is a measurement problem.

Meanwhile OpenAI's chief financial officer, Sarah Friar, published a scorecard proposing a new unit, "useful intelligence per dollar," and in doing so named the trap: for years software success was measured through adoption, seats and active users and renewals, and AI breaks that proxy completely. A thousand lit seats can produce nothing you would put in front of a board.

Stephen Forte on why the unit you count AI in is the wrong unit, the four questions to put to your largest AI investment today, why productivity felt is not revenue banked, and why the number on your AI dashboard you trust the most is probably the one measuring the least.

Almost every conversation about AI and work assumes your employees are on the receiving end of your decisions: leadership decides, the organisation adapts, and the only question is how kindly you manage it. In much of Europe that assumption is simply false.

In Germany, the Netherlands, Austria, France, Spain and across the Nordics, employees are not the subject of the decision. Through their representatives they are a party to it, by law. Germany's Works Constitution Act gives a works council co-determination over "the introduction and use of technical devices designed to monitor the behaviour or performance of employees," and the Federal Labour Court reads that to cover systems merely capable of monitoring, not only those intended to. Most enterprise AI tools qualify almost incidentally. Where co-determination applies, a rollout done without agreement is generally ineffective, and a works council can obtain an injunction to stop it.

Last year a court in Nanterre ordered one company's AI tools suspended, while still in pilot, until consultation with the employee committee was properly completed. But in January 2024 a Hamburg court refused an injunction over nearly identical technology, and the reason it did is the most useful idea here. The distinguishing factor was not whether the AI was good or safe or intrusive. It was whether the company deployed it or merely permitted it. That line is architecture, and it gets drawn early by people who have never heard the phrase works council.

Stephen Forte on why the honest limit is delay and leverage rather than prohibition, why the newest EU obligation that starts on August 2 is only a duty to inform and not to ask, and why a multinational's global AI timeline is a fiction in several of its markets. Your AI timeline does not belong to your plan. It belongs to your most protected workforce.

Two software companies on opposite sides of the world have now done the same strange thing to themselves, and the reason they gave is not the one anyone expected.

On July 22, monday.com, the Israeli work-management company listed in New York, filed notice of a roughly twenty percent workforce reduction, about 620 people, with restructuring charges of forty-five to fifty-five million US dollars. In the same breath it reaffirmed full-year revenue guidance of about 1.47 billion US dollars and nineteen to twenty percent growth. Grow twenty percent, shrink twenty percent, same announcement.

Co-CEO Eran Zinman said the decision "was not made to reduce costs or replace people with AI," that "the organization we built for our previous chapter is not the organization that fits the new AI era," and that work which "could have been done in a few days" had instead been taking "many months with multiple meetings and endless friction." Then the line that makes the episode: "This wasn't people's fault." The fix he describes is a flatter organisation with fewer management layers and smaller, more autonomous teams. The constraint AI relieved, in his telling, was coordination. Not the cost of labour.

He is not alone. In March, Atlassian, the Australian equivalent, cut about 1,600 people, roughly ten percent, while growing thirty-two percent, explicitly to "self-fund further investment in AI and Enterprise Sales." Mike Cannon-Brookes was unusually straight about it: their approach is not that "AI replaces people," but "it would be disingenuous to pretend AI doesn't change the mix of skills we need or the number of roles required in certain areas."

Stephen Forte on why two companies that sell AI betting their own org charts is worth more than any vendor presentation, why Salesforce is the awkward third case that teaches the distinction between an AI-shaped decision and a cost cut wearing AI language, and why revenue per employee, a number sitting underneath headcount planning, peer benchmarking, board judgement and acquisition pricing, just moved about twenty-two percent at one company through nothing more than a redrawn structure. No action items in this one. One idea, and one number that stopped meaning what you think it means.

The Digital Omnibus on AI entered into force on July 27, and the headline everyone read was that Europe has softened its AI rules. It has. The European Union's high-risk obligations moved out by up to sixteen months: to December 2, 2027 for standalone systems in areas like hiring and credit, and August 2, 2028 for AI embedded in regulated products like medical devices and machinery. If your company builds AI into a regulated product, that is real relief.

What almost nobody has been told is that the transparency rule was not moved at all. Article 50 applies on August 2, 2026. The European Commission confirmed it in a single sentence in its own guidance, and published a full set of interpretive guidelines for it on July 20 — which is not what regulators do a fortnight before a deadline they intend to postpone.

Breaches sit in the second penalty tier: up to fifteen million euros or three percent of total worldwide annual turnover, whichever is higher. Worldwide, not European. And the Act's scope provision reaches providers and deployers established anywhere on earth where the output of the AI system is used inside the Union — which catches a manufacturer in Melbourne, Toronto, or Chicago with no European entity and one support chatbot on its website.

Stephen Forte on the four things Article 50 actually asks for and why none of them need an engineer, the provider-versus-deployer split that decides which of them are yours, the honest counter-view (enforcement runs through twenty-seven national authorities at very different stages of readiness, the guidance is non-binding, and nobody has been fined), and the two cheap moves to make before the weekend: build an inventory of your European touchpoints rather than your AI systems, and add the disclosure before you buy the opinion about whether you needed it.

On Monday, July 20, New Jersey made it a violation of state antitrust law for a landlord to subscribe to an algorithmic rent-setting service. The violation is paying for the software. Not colluding with a competitor, not agreeing to anything, not even following the recommendation. Writing the check.

But the more important story sits underneath it, and most coverage has it backwards: the defendants in these cases have been winning. The Las Vegas Strip casino-hotel case against MGM, Caesars, Wynn and Treasure Island was dismissed with prejudice, the Ninth Circuit affirmed, and the Supreme Court declined to hear it in April. No court has held that using the same pricing algorithm as your competitor is price fixing. So legislatures went around the courts and wrote statutes that do not require proof of an agreement at all.

Which brings up the exposure nobody has briefed you on. California's Assembly Bill 325 has been law since September 2025. It has no industry limit. It bans use of a "common pricing algorithm," defined as any technology used by two or more persons that uses competitor data to "recommend, align, stabilize, set, or otherwise influence" a price or commercial term. Not collude. Influence. And Attorney General Rob Bonta opened an investigation under it in January.

Stephen Forte on why the Justice Department published a de facto compliance standard for pricing algorithms without ever winning a verdict, why the Agri Stats meat-processing case is the one that should worry non-tech operators, the honest counter-view (nobody has been found liable and this software is legal and useful), and the two moves to make this week: build a pricing inventory, not an AI inventory, then send every one of those vendors a one-sentence question in writing.

Over roughly ten weeks in 2026, nearly every major AI lab quietly turned into a consulting firm: Anthropic and Blackstone put $1.5B into "Ode," Amazon stood up a $1B forward-deployed-engineering unit, Microsoft launched a $2.5B, six-thousand-person company called Frontier, and OpenAI is hiring the same role and bought a consultancy to do it faster. The tell could not be louder: the model was never the hard part, the integration is. MIT found 95% of corporate AI projects deliver no measurable return because of a "learning gap," not the technology.

Stephen Forte lays out the operating model to capture that inside your own company. Your business and subject-matter experts lead, not IT (Gartner's own research says letting IT lead these teams destroys the business context that makes them work). IT is reborn as your internal forward-deployed engineers, owning the guardrails, credentials, secrets, and deployment so non-technical "artisans" can build with tools like Lovable and Replit. Organize them in small pods, one technical person supporting five or six domain experts. Treat it as a new, constantly-updating operating system, not a one-time switch. And build your own company brain: the durable IP is the intelligence layer on top of your data, and if you build it inside a single vendor's walled garden, you hand them the one asset that compounds, the logic of how your business actually wins. Rent the tools. Own the crown jewel.