YPO Technology Network AI Brief

You did not approve these agents. There was no vendor evaluation, no procurement process, no board sign-off. But they are running in your environment today.This episode covers three agents that arrived without the normal enterprise procurement process: Microsoft Scout — the always-on ambient AI agent now live inside Microsoft 365; Accenture's strategic investment in AlphaSense — the agentic market intelligence platform used by ninety percent of the S P 100; and Anthropic's Mythos cybersecurity AI, now running in over one hundred fifty organizations across fifteen countries including critical infrastructure.The question is not whether to adopt AI agents. That decision has already been made for you. The question is whether you know what they are authorized to do.Three desk actions: ask your CTO what Scout is authorized to do in your environment; find out if your top competitors are using AlphaSense; and if you are in critical infrastructure, ask your security team about Glasswing access.

Two headlines came out of Google this week — and most people are reading them as separate stories. They are one. Google is raising eighty billion dollars to build AI infrastructure. That infrastructure is already live, and it is dismantling the way your company gets discovered, evaluated, and chosen by buyers. Google is not updating search. It is replacing it.This episode covers: Google's eighty-billion-dollar equity raise (including a ten-billion-dollar placement to Berkshire Hathaway); what AI Mode and AI Overviews mean for business discovery; why ninety-three percent of AI Mode queries end without a click; what GEO — Generative Engine Optimization — actually requires; and two concrete actions for your desk this week.

For the last four years, serious AI mostly meant sending prompts to a cloud data center and paying the meter. This episode looks at two announcements that point in a different direction: Microsoft turning Windows into a runtime for persistent agents, and Nvidia pushing data-center-class AI compute into laptops and deskside workstations. The business question is not whether cloud AI goes away. It does not. The question is whether some of the most sensitive, expensive, and operationally important AI work starts moving closer to where the data and the people already are. Microsoft: Windows Agent Framework points toward agents that live inside the operating system, persist across tasks, and use local memory under user control. Nvidia: RTX Spark puts serious local inference capability into enterprise laptops and workstations, changing the hardware-refresh conversation. Executive takeaway: If your AI strategy assumes cloud-only deployment, that assumption is about to be tested by cost, privacy, and governance pressure. Two action items for leaders: put RTX Spark-class machines into the fall hardware evaluation, and have IT run a Windows Agent Framework proof of concept before the procurement cycle closes.

At Microsoft Build 2026, the company unveiled its MAI family of frontier AI models, a direct shot across the bow at Claude Code and OpenAI's developer tools. GitHub Copilot simultaneously announced a switch from flat-rate to token-based billing, with some enterprise teams reporting monthly invoices jumping from $29 to over $750. Meanwhile, an unnamed Fortune 100 client quietly accumulated a $500 million Claude API bill in a single month, and law firm Kirkland and Ellis committed half a billion dollars to build a proprietary AI platform rather than rely on off-the-shelf tools. Three action items for CEOs this week: audit every flat-rate AI contract before your next renewal, set hard token budget ceilings at the team level before bills arrive, and watch Microsoft Build announcements closely for capability shifts that could reorder your vendor stack.

The Receipt Week — Three Things Enterprises Just Confirmed About AI This week the agentic enterprise stopped being a keynote slide and started producing real artifacts. Three stories. One thesis. Snowflake acquires Natoma — The leading enterprise MCP infrastructure company just got absorbed by the platform most of your teams already run on. Your agent-to-data connections now have a new landlord. The question for your CIO: what is your exit cost if they raise the toll? Yoshua Bengio names names — One of the three godfathers of AI went unusually specific in Singapore, citing PocketOS, Replit, and a multi-university study documenting AI agents deleting production databases, generating fake reports, and covering their tracks. His demand: digital trails and clear accountability — not safety frameworks. Audit logs. Open Router raises $113M at $1.3B — The AI model abstraction layer just closed a Series B led by Google's growth fund. The co-investors: Snowflake Ventures, Databricks Ventures, MongoDB Ventures, and ServiceNow Ventures — the corporate arms of the same platforms whose customers worry about lock-in. That is hedge investing at minimum. At most, it is those platforms telling you what they see coming. The operator architecture for the agentic enterprise: Lock down connection. Lock down action. Keep model choice open. Three things to do this week: Get your CIO and CDO in a room with one question: what would it cost to move our agent-connection layer? The answer should be a number, not a paragraph. Write the agent accountability policy your audit committee will ask about next quarter — three written answers: who is accountable, what is the audit trail, how is the action reversed. Put a model-abstraction line item in your AI architecture. You should be able to swap underlying models with a small code change, not a rewrite. Mentioned in this episode: Snowflake, Natoma, Anthropic, MCP (Model Context Protocol), Yoshua Bengio, MILA, PocketOS, Replit, Open Router, CapitalG, Databricks, MongoDB, ServiceNow Listen every weekday for a sharp 7–10 minute brief on what is moving in enterprise AI — written for CEOs and senior leaders, not engineers.

On Tuesday, in Sydney, Sam Altman — the CEO of OpenAI — publicly walked back the white-collar jobs apocalypse he had warned about. Quote: "I'm delighted to be wrong about this." Forty-eight hours after our Tuesday episode argued the opposite, the CEO of the most valuable AI lab in the world said the thesis is wrong. Or at least premature. The story is not Altman versus Suleyman. The deeper story — what does a CEO do when the people building this technology no longer agree about what it is going to do? And while that disagreement is playing out, two other things happened this week that no one in your executive team is going to brief you on. DeepSeek, the leading Chinese AI lab, made a 75% V4-Pro price cut permanent — locking in margin pressure on OpenAI, Anthropic, and Google. And Microsoft just blocked Databricks from connecting to Power BI — the latest "toll gate" being erected by platform owners (Workday, ServiceNow, HubSpot are doing the same) to control which AI agents can act on your data. Stephen Forte argues: the AI market just stratified along three axes. Labor — no consensus. Cost — collapsing. Distribution — locking up. A CEO needs a position on all three. Three things to do this week: Write a one-page scenario for what your company looks like under both Altman's and Suleyman's labor timelines. Hand it to your board. Pull your two largest AI vendor renewals into a single review. If the per-token cost assumption dates from 2025, send it back. Ask your CIO to map your semantic layer dependencies — where "revenue," "customer," and "order" actually get defined. That's where your AI agent strategy lives. The most useful thing the people building this technology have done all year is tell you, by disagreeing publicly, that you are allowed to disagree too. The AI Brief is produced for YPO Technology Network members. New episodes every weekday at 6 AM ET.

95% of enterprise generative AI pilots deliver zero measurable return. The average large enterprise abandoned 2.3 AI initiatives last year, with $7.2M in average sunk cost per abandoned project. Those numbers come from MIT Project NANDA and S&P Global. They are not paranoia. They are the data. This is an opinion episode. Stephen Forte names what he is seeing in the field directly: the AI transformation market has a grifter problem. Not all of it. Not even most of it. But enough that every CEO needs a framework before they sign the next proposal that lands in their inbox. Five red flags every CEO should be able to spot inside a week: They closed you in one or two meetings. Workflow transformation requires process mapping, not a discovery call. They are proposing to build you something proprietary. MIT data: internal builds fail at twice the rate of vendor-led, platform-based solutions. The deliverable is murky and the technology is opaque. If you cannot see how you would leave their platform — assume that is intentional. Gartner: 40% of agentic AI projects will be discontinued by 2027. They want significant payment up front. Serious vendors stage payments against verifiable deliverables. The proposal has no real data work line item. Industry consensus: data preparation is 70-80% of any real AI project. If it is not in the budget, it is not a serious program. Plus: the Klarna pivot moment — what happens when even the best-run, most-platform-native enterprise AI deployment has to walk it back. And three things every CEO should do this week before signing the next proposal. The most strategic AI decision you make this year may be the one you do not sign. The AI Brief is produced for YPO Technology Network members. New episodes every weekday at 6 AM ET.

The white-collar AI thesis stopped being a thesis this week. It became a forecast. Then it became a company. Then it became a market price. ClickUp laid off 22 percent of its workforce last Thursday — and CEO Zeb Evans said it was not a cost-cutting move. It was a "radical embrace of AI." The company is replacing those people with 3,000 internal AI agents, and is introducing million-dollar salary bands for the workers who stay. Same week, Microsoft AI CEO Mustafa Suleyman told the Financial Times that most white-collar desk work will be fully automated within 12 to 18 months. And Anthropic is closing a $30B round at a $900B+ valuation — the largest private AI valuation in history. Three stories. One thesis. Stephen Forte walks CEOs through why ClickUp may be the proof of concept Suleyman's timeline needed, why the Anthropic valuation is a labor-substitution bet not an AI lab bet, and what the "ClickUp test" means for your own org chart over the next 90 days. Three things to do this week: Get your CFO and CHRO in a room with one question: if we ran ClickUp's playbook, what does our org chart look like in 12 months? It's a stress test, not a plan. Pressure-test the Suleyman 18-month timeline against three of your own functions. Accounting, legal, marketing — borrow ClickUp's list. Start building your top-decile AI-leveraged compensation philosophy before your top decile asks. ClickUp's million-dollar bands will leak into the labor market. Stories referenced: ClickUp 22% layoff + million-dollar AI bands | Suleyman 12–18 month white-collar automation timeline | Anthropic $30B round at $900B+ valuation | Anthropic $1.25B/month SpaceX compute commitment The AI Brief is produced for YPO Technology Network members. New episodes every weekday at 6 AM ET.

Three stories from the last week that, taken together, name the shape of the AI-era company — and the shape most CEOs are accidentally building instead. Polsia raised 30 million dollars at a 250 million dollar valuation. The company has approximately 10 million dollars in ARR. The founder, Ben Cera, is the only person at the company. Sound Ventures led; True, Offline, Adjacent, Tekton, Drysdale, and VaynerFund alongside. The agents ran the fundraise. Gartner surveyed 350 senior executives at billion-dollar companies already deploying AI agents. 80 percent had already cut headcount. The companies that cut the most produced almost identical financial returns to the companies that cut the least. Helen Poitevin, VP analyst, on the record: workforce reductions may create budget room, but they do not create return. Walmart disclosed three Sparky numbers on its first-quarter earnings call: customers using Sparky show a 35 percent higher average order value than non-users, weekly active users more than doubled in a single quarter, and units purchased through Sparky more than quadrupled. Same workforce. Bigger basket. Public earnings call. The wrong question is who do I cut. The right question is what can my people now ship. Stories covered: Polsia — solo founder, zero employees, 10 million dollars ARR Gartner — 80 percent cut headcount, the cuts did not pay Intuit — 17 percent reduction, 300 to 340 million dollar restructuring charge, AI handling 50 million weekly transactions Walmart Sparky — 35 percent AOV lift, WAU up over 100 percent in one quarter Suleyman vs Marcus — 100,000 dollar bet on white-collar automation timing About this show: The YPO Technology Network AI Brief is a daily AI intelligence brief for CEOs and Presidents of mid-market and large companies. Hosted by Stephen Forte, founder of BuildClub. Subscribe and share with a fellow member.

Something shifted this week in enterprise AI — and most coverage missed it because it happened in pieces. SAP launched its Autonomous Enterprise at Sapphire with 50+ Joule agents. KPMG and Anthropic struck the largest Big Four AI deal yet. Andrej Karpathy joined Anthropic's pre-training team. And the White House started briefing AI labs on an executive order that could put a 90-day federal review in front of every frontier model release. Four stories. Two days. One arc — and one clear winner. In this episode, Stephen Forte walks CEOs through what the agentic enterprise actually looks like now that SAP and KPMG just made it the default, why Karpathy choosing pre-training (not safety, not deployment) is the talent signal of the year, and how the Trump administration's draft executive order could decelerate model release velocity right as the application layer accelerates. Key takeaways for CEOs: The pilot phase of agentic AI ended this week. Your peers — and your auditors — are treating agents as production infrastructure. Pick your enterprise AI vendor like you are picking an ERP, not a model. The model is becoming a commodity; the channel is the moat. Build a version of your 2027 plan that assumes one foundation-model upgrade per year, not two. Voluntary 90-day reviews tend not to stay voluntary. Stories referenced: SAP Sapphire 2026 | KPMG–Anthropic global alliance | Andrej Karpathy joins Anthropic | Trump frontier-model executive order draft The AI Brief is produced for YPO Technology Network members. New episodes every weekday at 6 AM ET.

Three competing agent operating systems shipped inside a sixty-day window — Google's Gemini Enterprise Agent Platform, Microsoft's Copilot Studio plus Agent Framework stack, and Anthropic Managed Agents — and Google's I/O 2026 pivot on Tuesday made the platform decision a CEO call this quarter, not a CTO project for next year. In this episode, Stephen Forte walks through the three-layer architecture every CEO needs to understand (brain, session, hands), compares the four real options with the companies running them, and explains why the harness decision matters more than the model decision. If you pick the right platform for where your people already work, you can have one Artisan on one workflow in production by Friday. What you will learn: The brain-session-hands architecture: why keeping those three layers clean is the difference between a demo and a production system Why MCP (Model Context Protocol) being native across Google, Microsoft, and Anthropic stacks is the largest hedge against platform lock-in ever offered in enterprise software The honest case for and against each of the four options — Google Gemini Enterprise, Microsoft Agent Framework, Anthropic Managed Agents, and LangGraph neutral build Why the $30 Microsoft Copilot seat headline is actually closer to $90 all-in, and what that means for your platform math The one-week pilot framework: one workflow, one Artisan, one platform — and the two metrics (time saved, error rate) that tell you whether you have earned a platform commitment The CEO move this week: Run a one-week pilot on a single finance or operations workflow using the agent platform your knowledge workers already live on. Put one senior operator — not a committee — in charge, measure time saved per task and error rate versus the human baseline, and decide by Friday whether you have earned the right to a platform commitment. Pick it like you would pick an HRIS: not for the demo, but for where the work actually lives. Links: Perplexity Computer Anthropic Managed Agents engineering blog Google Gemini Flash announcement Microsoft Agent Framework GA LangChain State of Agent Engineering MCP project

In this extended episode of the YPO Technology Network AI Brief, Stephen Forte makes the case that the most important hire of the next five years has no job title yet: the AI Artisan, the practitioner who sits between product, design, and engineering — steering models, orchestrating tools, and translating deep domain expertise into working software. The episode pairs that role definition with two supporting ideas: the Constellation of Apps thesis, which argues that the era of the monolithic enterprise suite is ending in favor of hundreds of sharp, task-specific micro-apps; and a practical two-system build method using Perplexity Computer and Replit that lets a single Artisan ship a working prototype in a week. If you are a CEO deciding how to deploy AI inside your organization this quarter, this episode gives you the role to hire for, the architecture to aim at, and the method to hand someone on Thursday. What you will learn: What an AI Artisan actually does — the four responsibilities that define the role, and why the best candidates are deep domain experts, not engineers How to find your existing Artisans right now: not by job title, but by asking one question of your direct reports Why the Constellation of Apps is replacing the enterprise suite — and the two real-company micro-app examples (accounts payable and lead scoring) that illustrate the shift The new division of labor between frontline teams and IT: frontline builds the scalpels, IT builds the operating table The two-system build method — Perplexity Computer as the thinking and writing environment, Replit as the execution environment — and the five-part handoff artifact that connects them The CEO move this week: Ask each of your direct reports who on their team has built something with AI in the last sixty days that actually moved a number. Take one name from that list, pair them with one small, specific, recurring frontline problem, and give them a week with the two-system method. A working prototype by Friday is the bar — and if it takes longer, the problem was not well-defined enough. Links: Research pack for this episode Perplexity Computer — the thinking and writing environment used in the two-system build method Replit — the browser-based execution and deployment environment Anthropic Model Context Protocol (MCP) — the open standard that collapsed the integration cost driving the Constellation of Apps shift

Three things happened over the weekend that, taken together, mean your existing SaaS stack just got publicly graded on a curve. One investor with a spreadsheet. One reorg at OpenAI. One quiet number from Anthropic's CFO. The agent economy is no longer something coming — it is something already grading you. What's inside this episode: The SaaStr Agent API Report Card. Jason Lemkin graded 116 enterprise software companies on whether AI agents can actually use them. Stripe got an A-plus. Workday got a D. Only 27 of the 116 hit A-tier. This is the first public scorecard CEOs can use to evaluate their own stack. OpenAI reorganizes around agents. Greg Brockman put in charge of a unified ChatGPT-plus-Codex agentic platform. Codex shipped to iOS. ChatGPT wired to your bank account via Plaid. Seventy-two hours of urgency. Anthropic passes OpenAI in paid enterprise. Ramp's AI Index showed the flip. Anthropic's CFO disclosed a $30B annualized run-rate — up from $250M two years ago. 120x in 24 months. The three stories are one story told from three angles. Anthropic winning is the result. OpenAI reorganizing is the response. Lemkin's scorecard is the playing field. Once your vendors are publicly graded on agent readiness, every CEO in your peer group asks the same two questions at their next operating review — and the vendors on the wrong side of the line stop being your software providers and start being your migration project. What to do this week: Pull Lemkin's scorecard. Find your top 10 vendors. Twenty minutes, not a project. Notice which of your vendors are silent — the ones that did not even get graded. That is also useful information. Sources: Jason Lemkin / SaaStr Agent API Report Card The Verge — OpenAI executive reshuffle The Rundown AI — The Enterprise Shift OpenAI Saw Coming The Rundown AI — OpenAI Takes Codex Mobile The YPO Technology Network AI Brief is hosted by Stephen Forte, founder of BuildClub and a member of YPO. Episodes drop weekday mornings.

OpenAI just raised $4 billion to start an implementation company. Microsoft just disclosed two serious security holes in its own AI agent framework. These are not two separate stories — they are one story told from two ends. In this episode of the YPO Technology Network AI Brief, Stephen Forte unpacks why the implementation layer is becoming required infrastructure for enterprise AI, and why your agent stack is now complicated enough that you cannot reasonably govern it from the inside. What's covered: OpenAI Deployment Company — A $4 billion raise at a $10 billion valuation, backed by TPG, Bain Capital, Brookfield, and Advent. Bain & Company, Capgemini, and McKinsey are inside the deal as implementation partners. The model labs just consolidated the implementation layer — exactly as we predicted three weeks ago in "From Press Release to P&L." Microsoft Semantic Kernel vulnerabilities — Microsoft disclosed two serious security holes in its own AI agent framework: a prompt-to-shell remote code execution and an arbitrary file write. Patched versions shipped this month. The lesson Microsoft's own security team put on the page: "Your large language model is not a security boundary. The tools you expose define your attacker's affected scope." Why outside eyes matter — In a market this young, every lesson is being learned in real time. Internal teams have seen one network — theirs. Implementation partners with cross-client visibility import pattern recognition you cannot build inside one building. That is what OpenAI just raised $4 billion to industrialize. Two moves to make this quarter — Inventory every AI agent framework your teams are running, and what version. Then pressure-test your AI program with one question: "How many other companies have you watched do this?" The takeaway: The implementation layer is becoming required infrastructure. Not because anyone wants to spend more on consulting. Because the only way to safely operate systems this new is to import the cross-client pattern recognition you cannot build inside one company. You cannot learn this from the inside. Sources: OpenAI Deployment Company announcement, May 15, 2026 — MarketingProfs AI Update "When prompts become shells: RCE vulnerabilities in AI agent frameworks" — Microsoft Security Blog, May 7, 2026 The YPO Technology Network AI Brief is a daily, peer-to-peer briefing for CEOs and senior business leaders on what AI news actually means for how you run your company.

Weekend Special Edition for YPO members. One topic, no rapid fire. This week: the company brain — a permissioned, governed AI memory layer that reads across meetings, email, documents, tickets, and CRM so leaders can finally understand the operating record of the firm, not just the structured slice their dashboard shows. There is a version of your company that your dashboard cannot see. It lives in meeting transcripts, support tickets, CRM notes, and the language your people use when nobody is assembling the pattern. In the old world, looking at that material sounded like prying. In the AI world, refusing to build a governed memory layer over it starts to look like managerial malpractice. In this 14–17 minute deep dive, host Stephen Forte makes the CEO/operator case for the company brain and draws a clear line between operating intelligence and surveillance: What the company brain actually is, in plain English — RAG, vector search, knowledge graphs, GraphRAG, and the MCP connector layer Why every major platform is converging on the same pattern — OpenAI Company Knowledge, Microsoft 365 Copilot, Google Gemini Enterprise, Claude Enterprise Search, and Glean The governance line — the company brain should be a permissioned window, not a skeleton key, with disclosure, role-based access, retention limits, and audit logs Real reference points — Klarna's internal assistant Kiki, Morgan Stanley Wealth Management's OpenAI-powered advisor tool, and Moderna's company-wide AI deployment What the UK ICO, the FTC, and NIST already say about employee monitoring and AI confidentiality Four moves for Monday morning: Inventory the corpus — list every system where company memory lives Pick three questions worth answering — account health, project drift, sales-to-delivery handoff, or your three Build the permission model before the pilot, not after — governance is the product Require citations on every answer that touches an operating decision If a vendor cannot tell you in one sentence how their system inherits your source-system permissions, that vendor is not ready for your company. Walk them politely to the elevator. This is the YPO Technology Network AI Brief weekend edition — peer-to-peer, CEO-grade, and built for members running $13M+ companies who want the perspective before the next executive committee meeting. Subscribe and listen at the YPO Technology Network AI Brief on RSS.com.

Social Capital published an AI agents primer this month that walks the architecture of the agent stack. One section in it is genuinely important and almost nobody is measuring it yet: Hidden Human Cleanup Costs. Stephen reads that finding as the line item your AI vendor invoice is not showing you — and the lever you have on your next renewal. What's covered How agents fail differently than traditional software — not with red error boxes, but with confident wrong answers, false-assumption actions, and quietly abandoned tasks that compound through fifteen steps of a workflow before anyone notices The cleanup math — diagnosis, impact analysis, rebuild, restart. At $50–$200 per hour fully loaded, a 5% intervention rate on 10,000 monthly tasks runs over $200,000 a year per agent. Off invoice. The Amazon Q examples as the cleanest public data — December 2025's 13-hour AWS-China outage from an autonomous production-environment deletion, March 2026's 120,000 lost orders and 1.6 million errors, and the separate incident days later that dropped 99% of North American marketplace orders for six hours The spookier number from the March 2026 Claude Code source leak — 1,279 sessions with 50+ consecutive failures wasting roughly 250,000 API calls per day at one of the best-resourced AI labs in the world The one-question test for vendor evaluation — "What is your intervention rate per hundred tasks?" plus "What is the average cleanup cost per intervention?" Get both answers in writing before any renewal. The thesis: The vendors who minimize human cleanup costs are the ones who will justify their economics in production. The vendors who do not are running pilots. They just call them products. The challenge: Pull your current intervention rate by agent and by workflow this week. If your team cannot tell you, you do not have an agent program — you have a science project. The cleanup cost line item is the leverage you have on your next renewal. Most CEOs are not using it yet. The YPO Technology Network AI Brief is hosted by Stephen Forte for YPO members and senior operating leaders.

There are two workforces inside your company right now, and the gap between them is widening every quarter. Writer's 2026 AI Adoption Survey found that super-users save 4.5x more time, are 5x more productive, and are 3x more likely to be promoted with a raise compared to their non-adopting peers. Same job title. Same company. Same tenure. Stephen makes the case that this is not a productivity bump — it is a different employee — and that the historical PC adoption analog (which took 15 years to show up in productivity statistics) is the wrong mental model. This cycle is moving in months, not decades. What's covered The hard data — Writer's April survey on super-users, Gallup's 50% adoption number, Microsoft's 22-point critical thinking lift when managers model AI use, and the executive numbers nobody is saying out loud (77% will not promote non-adopters, 60% are planning layoffs of AI refusers, 92% cultivating an AI elite) What the adopters are actually doing differently — not "they use AI more." They have internalized a different mental model of work. Decomposition, iteration, critical evaluation. The thinking skill, not the software skill. Why the PC analog is misleading — Solow's 1987 productivity paradox took 15 years to resolve. That slow burn was a gift. This cycle is opening gaps in months. The story of a software engineer in his late twenties being measurably outpaced by 23-year-olds who design their workflow around AI from the first keystroke. Three moves CEOs should make as a sequence — (1) elevate the adopters now into broader scope and role redesign, (2) replace generalized AI training with workflow-specific 1:1 coaching that sits next to each employee and shows them what AI does for THEIR Tuesday morning, (3) be honest with the small percentage who will not adapt A note on what this is not — AI fluency is a skill, not a personality test. Most people can acquire it. The bifurcation is between the curious and the refusers, not the brilliant and the average. The thesis: This is not about whether AI is the future. That argument is over. This is about whether your company elevates the adopters, trains the curious, and is honest with the refusers — or protects the resisters until it cannot afford to anymore. The challenge: Walk the floor this week. Have a real conversation with one super-user about how they work now. Have a real conversation with one refuser about what they think is going to happen. The data you collect on those two walks will tell you more about your company than any AI strategy deck. The YPO Technology Network AI Brief is hosted by Stephen Forte for YPO members and senior operating leaders.

A week ago Tuesday, OpenAI silently swapped the default ChatGPT model from GPT-5.3 Instant to GPT-5.5 Instant. Most enterprises did not notice. Their sensitive workflows ran on a different model at lunchtime than they did at breakfast — with a different hallucination profile on legal, medical, and financial outputs — and nobody at the C-level was told. Stephen reads the default swap as the cleanest test of where your company sits on a much larger divide: PwC's finding that 74 percent of AI's economic value is being captured by 20 percent of companies. What's covered What actually changed on May 5 — GPT-5.5 Instant becomes default, GPT-5.3 phased out for paid users in 90 days, real benchmark improvements on hallucination in sensitive domains, and the parallel rollout of GPT-5.5-Cyber for vetted teams The three-question test — which model is our team on, when did it last change, did anyone evaluate the new one against our workflows. If you cannot answer all three quickly, you are in the 80%. The core reframe — two ways a company can relate to AI right now. Consume it as a feature (whatever's in the chat box is what you run) or run it as infrastructure (versioned, evaluated, governed). The 74/20 divide is not about adoption. It is about posture. Three concrete moves the leaders are making — version-controlling the model stack, running an evaluation harness on sensitive workflows, and picking growth use cases on purpose rather than productivity use cases by accident The GPT-5.5-Cyber footnote — why specialty AI procurement is starting to look like the Pentagon's procurement (callback to S1E60), and what that means for the commodity tier most enterprises are buying without realizing it The thesis: The companies that noticed last Tuesday's default swap are running infrastructure. The companies that did not are running a chat box and hoping. That is not a tools problem. That is the whole problem. The challenge: One engineer, one evaluation harness, one person whose job description includes "tell me when the model changed." That is the gap between the 20 percent and the rest. Run the three-question test this week. The YPO Technology Network AI Brief is hosted by Stephen Forte for YPO members and senior operating leaders.

On May 1, the Pentagon signed agreements with eight frontier AI labs — SpaceX, OpenAI, Google, NVIDIA, Reflection, Microsoft, Amazon Web Services, and Oracle — to deploy models on Impact Level 6 and 7 classified networks. Most of the press read it as a defense story or a politics story. Stephen reads it as the procurement playbook most enterprises haven't built yet. What's covered What the Pentagon actually structured on May 1 — eight vendors named, Impact Levels 6 and 7, the $200M Google contract from 2025, the separate $500M Scale AI deal, and Oracle added on the day of the announcement Three things the Pentagon got right — multi-vendor sourcing against a single capability scope, use restrictions written into the contract rather than into policy, and an expandable framework rather than a fixed roster Why Anthropic ended up frozen out — the use-case restrictions they refused to remove, the supply-chain risk classification that followed, and what their absence teaches operators about vendor-customer values alignment Three operator moves for your own AI vendor stack — pull the real list, classify by workflow class not by product, and put use-case scoping into the contracts at renewal Why compute reliability is what makes vendor optionality possible in the first place The reframe: Most enterprises are running a roster. The Pentagon built a framework. One bar, one contract template, multiple vendors qualified, workloads portable. New vendor signs, gets in. Old vendor falls behind, gets de-prioritized without a renegotiation. The challenge: Probably three weeks of work to build a vendor stack that survives the next model release without an emergency board meeting. The Pentagon did the procurement work at signing time. You can do it at renewal time. Cheaper either way. The YPO Technology Network AI Brief is hosted by Stephen Forte for YPO members and senior operating leaders.

Anthropic's annual conference last week shipped enterprise infrastructure rather than another headline model — Managed Agents, multi-agent orchestration, outcomes-as-rubric, a memory feature called dreaming, and a serious compute expansion. Most of the coverage reads like a product launch recap. Stephen reframes it as a P&L event and walks through the three-stage method for turning announcements like these into a workflow change a CFO will defend in the budget cycle. What's covered What Anthropic actually shipped — Managed Agents, multi-agent orchestration, outcomes (rubric-based self-checks), the dreaming memory feature, and why the compute expansion is the silent variable that turns a fragile experiment into a budget line Why most enterprise AI rollouts stall — not a model problem, a sequencing problem Stage one — Build the bad version in Perplexity Computer. Three patterns that show up almost every time: the order is wrong, the agent reads the instruction differently than you wrote it, and the QA step belongs at every stage rather than the end Stage two — Run it manually for two weeks with a senior person in the loop and a daily two-line journal that becomes the operating manual The handoff — How Perplexity Computer writes the spec as markdown while you iterate, and how that markdown folder seeds Anthropic's Managed Agents with light tweaks rather than a rewrite Stage three — Move the hardened version into a managed environment with long-running sessions, scoped permissions, persistent memory, and an audit trail The thesis: Use Perplexity Computer, or a tool like it, to learn the workflow. Use Anthropic Managed Agents, or one like it, to run the workflow. Two different tools for two different jobs. Discover, then operate. The challenge: Pick one workflow this quarter — reconciliation, expense triage, sales-order processing, customer onboarding, ticket routing. Build the bad version in a flexible environment over a week. Run it for real for two weeks. Then harden it into a managed environment built to run it every day. Ninety days, end to end. One workflow, demonstrably cheaper, faster, or more accurate than it was the quarter before. The YPO Technology Network AI Brief is hosted by Stephen Forte for YPO members and senior operating leaders.

Weekend Special Edition. The Saturday deep dive on secrets management for AI agents — the unglamorous infrastructure decision that determines how big your blast radius is when something goes wrong. Stephen walks through the BuildClub stack, the patterns we use with clients, and the specific mistakes that cost companies the most. The single thesis: Treat your agents like employees, not like scripts. Give them an ID. Give them the minimum access they need. Write down what they have. Revoke it when they leave. Same playbook you already run for humans. What you will get out of this episode: Why the over-provisioning trap is universal — and why it is not a careless-developer problem The two angles for production deployment: corporate identity in your tenant, and giving the agent its own user account How to structure your secrets vault so a single leak does not own the whole company Where to keep the seed credential — and why GitHub Actions secrets plus OIDC federation beats a static admin key OAuth 1 vs OAuth 2 vs static API keys, explained for a non-technical audience The two practical disciplines that matter most: rotation and revocation BuildClub's offline-first build pattern and why it gives client IT a precise ask instead of a fuzzy one Vendors and tools mentioned: Infisical — open-source secrets management; what we run at BuildClub 1Password Service Accounts — solid alternative if your org already runs 1Password Microsoft Entra Agent ID — first-class identities for AI agents in your tenant GitHub Actions OIDC — short-lived cloud credentials, no long-lived keys GitGuardian — automated secret scanning across your repos The two-thing close: If I were sitting in your seat this quarter, I would (1) pull the list of every agent, automation, and integration in your company that holds a credential — just the list, not a project — and (2) rebuild one workflow the right way as the template for everything that follows. Listen. Share with a fellow member who is shipping their first agents. Stay sharp. Hosted by Stephen Forte, CEO of BuildClub. The YPO Technology Network AI Brief is a daily podcast for CEOs and senior business leaders.

Earlier this week, we talked about inference getting cheaper. Today is the other half of the story: AI may be getting cheaper to run, but it is not getting simpler to install inside a real company. OpenAI and Anthropic are both moving deeper into enterprise AI services. The strategic lesson is not the deal structure. It is the admission: the hard part is no longer only the model. The hard part is understanding how work actually happens inside companies. In this episode, Stephen Forte explains why the best AI deployments start with workflow archaeology: interviewing the people doing the work, mapping repeated task patterns across teams, finding where humans act as middleware between machines, and building agents around shared work instead of individual job titles. Key takeaways: Do not start with, “What agent should we build?” Start with, “What work is actually happening?” The unit of analysis is not the employee. It is the task pattern. Many companies have seven people doing the same 20 percent of work in different departments. Measure agents by output: transactions handled, files normalized, exceptions routed, cycle time reduced, and human review required. AI adoption is a migration, not a rip-and-replace transformation. The future is not one bot per employee. It is a new operating system for the business, assembled from the real work people already do.

Sierra closed a $950 million round at a $15.8 billion valuation, led by Tiger Global and GV with Benchmark, Sequoia, Greenoaks and others. Eight months ago the company was valued at $10B. The reason for the step-up is not a keynote demo. It is revenue: $100M ARR in November, $150M by early February, and a customer list that includes Cigna, Prudential, Blue Cross Blue Shield, Rocket Mortgage, SoFi, Ramp, Discord, Rivian, Sonos, and Wayfair. Stephen Forte's read: customer service is the first enterprise workflow with a billion-dollar AI receipt attached, and the part your CFO should underline is the pricing model, not the round size. In this episode: Why outcome-based pricing changes every line item in your stack How a single agent across phone, IVR, chat, WhatsApp, email, and 34+ languages becomes the wedge into your front office Why the contact center stops being a cost line and becomes a competitive surface Three CFO-grade moves this quarter: model a 30-60% per-contact cost reduction in the 2027 plan, put outcome pricing in every contact-center RFP, separate brand-defining calls from payroll-consuming calls The honest caveats: a $15.8B valuation on $150M ARR is a huge multiple, ARR is not profit, and we have lived through chatbot hype before, but the customer list is different this time The contact center stopped being just a cost center this week. It became a competitive surface. Treat it like one.

Anthropic is reportedly finalizing a roughly $1.5 billion joint venture with Blackstone, Hellman & Friedman, Goldman Sachs, and General Atlantic to deploy Claude across private-equity portfolio companies. Three weeks earlier, OpenAI was reported to be backing a parallel vehicle with TPG, Bain Capital, Advent, and Brookfield. Same plot, different cap tables. Stephen Forte's read: the frontier labs are not just shipping models anymore. They are buying distribution, because the last mile of enterprise AI is harder than the demos made it look. In this episode: What the Wall Street Journal reported and who is putting in what Why benchmarks do not solve the integration problem: old ERPs, custom CRMs, and the three Karens with the spreadsheets What PE-backed CEOs should expect from the value-creation team in the next twelve months Why the service layer, not the model, is becoming the lock-in layer Three things to do this quarter: ask the sponsor, write portability into every contract, double down only where proprietary data creates advantage The labs are not just selling models anymore. They are buying customers. The CEOs who notice early get to negotiate. The ones who do not get assigned.

For eighteen months the story has been the same. AI is expensive, and getting more expensive. That story has inverted. The price of using AI, not building it, is collapsing, and most of your vendors are quietly hoping you do not notice.In this weekday brief, Stephen Forte teaches the single most important distinction in AI economics, walks through four pieces of evidence in eleven days that the price floor is cracking, and gives you three concrete moves for the contracts already sitting in your legal folder.What you'll learn:Training vs. inference. Training is medical school. Inference is every patient visit for the next forty years. Inference is north of ninety percent of what you actually pay.The chip split. Google announced TPU 8t for training and TPU 8i for inference on April 22. Nvidia, AMD, and AWS Trainium/Inferentia are all moving the same direction. F1 cars vs. delivery vans.The Nebius/Eigen deal. On May 1, Nebius paid $643M for a startup that does one thing: makes AI run inference faster and cheaper. Three months earlier they bought Tavily for $275M. Same theme.DeepSeek V4 (April 24). An open-weight Chinese model claims to close the gap with frontier reasoning at a fraction of the cost. Western vendors will discount or explain why they aren't.Anthropic at $900B. A $50B round only pencils if inference economics work at industrial scale. That is the bet.Models are splitting too. Frontier models are neurosurgeons. Distilled models (Haikus, Minis, Nanos) and mixture-of-experts architectures are nurse practitioners — 95% of the visits at 10% of the cost.Three moves for this week:Pull every AI vendor contract signed in the last eighteen months. Find the inference pricing line (per token, per request, per seat).Ask your CIO: what percentage of our AI workload could run on a smaller or distilled model? The honest answer is north of seventy percent.Open the renegotiation conversation now. Not at renewal. Vendors fighting for share will move on price.The training story made the headlines. The inference story makes the budget. For eighteen months you have been the seller's customer. As of last week, you are the buyer.Sources:Bloomberg — Nebius Agrees to Buy Startup That Makes AI Run Faster, Cheaper (May 1, 2026)TechCrunch — Google Cloud launches two new AI chips to compete with Nvidia (April 22, 2026)<a href="https://techcrunch.com/2026/04/24/deepseek-previews-new-ai-model-that-closes-the-g

Google is selling the enterprise agent control plane from the top down. Employees are building the AI workforce from the bottom up. In today's YPO Technology Network AI Brief, Stephen Forte connects those two moves and explains why CEOs need to stop asking which model is best and start asking who governs the work. Stories covered: Google's push to make Gemini Enterprise the control plane for enterprise AI agents Why agent governance is becoming a board-level operating question Writer's 2026 enterprise AI adoption data on AI elites, non-adopters, and shadow AI Gallup and HBR signals showing that employees are already building AI leverage from the bottom up The CEO takeaway: the model is not the moat. The operating system around the model is. Sources: Reuters, Writer, Gallup, Harvard Business Review.

An AI coding agent at Amazon was given a bug to fix. It found a solution. It deleted and recreated the entire production environment. That is not the interesting part. The interesting part is Amazon's explanation: this was not an AI failure. It was user error, specifically misconfigured access controls. In the narrow technical sense, Amazon was right. Which is exactly the problem. This shorter weekend edition focuses on the real enterprise lesson: agents don't go rogue. They inherit. They inherit permissions, approval paths, stale documentation, and identity from systems that were built for humans. Key ideas in this episode: IAM, in plain English: identity and access management is the permissions system companies use to give rights to people, machines, services, and now agents. Permission inheritance: if an agent runs inside a human engineer's session, the authorization system may see only the human's authority. Knowledge inheritance: agents can industrialize stale wikis and outdated internal process docs at machine speed. Identity inheritance: if agents lack separate identities, audit logs compress machine decisions into human actions. Cost as the warning light: API retry storms and runaway compute are often control failures before they are AI failures. The practical question for leaders: where can an agent inherit a human's permissions, stale knowledge, human-only approval paths, or an audit identity that hides the machine? Sources: Breached.Company — Kiro incident analysis Barrack.ai — Amazon AI deleted production analysis CRN — AWS official Kiro response Fortune — Amazon retail incidents AWS — Agent Registry launch RocketEdge — agent cost incidents Hosted by Stephen Forte.

The honeymoon era of enterprise AI is over. Three stories landed this week that change the conversation in your boardroom from whether to do AI to how much it will cost you, who you will buy it from, and what the geopolitical risk looks like. In this episode: Microsoft and OpenAI restructure the most lucrative partnership in tech. Exclusivity is gone. OpenAI can sell on AWS within weeks, Google likely next. The real shift is architectural — Azure for stateless API calls, AWS for stateful agents — and what it means for the model decisions every CIO now has to make per workload. Tokenmaxxing is detonating cost structures. Uber exhausted its entire 2026 AI budget before May. Anthropic billed one user a hundred-fifty-thousand dollars in a single month. The killer insight: most token bills aren't a vendor problem, they're a model selection problem — and that decision happens at the prompt layer, not the procurement layer. China blocks Meta's Manus deal. Beijing's NDRC ordered Meta to unwind a two-billion-dollar acquisition with no justification. Singapore-washing is dead. If you have any cross-border AI M&A on your roadmap, your diligence playbook just changed. What I'd do this quarter: Re-open every multi-year Azure AI commitment signed under exclusivity assumptions. Name an AI FinOps owner with hard kill switches at the API layer. Reassess any cross-border AI M&A based on origin of talent and IP, not legal domicile. Sources: Microsoft — The next phase of the Microsoft-OpenAI partnership VentureBeat — Microsoft and OpenAI gut their exclusive deal Pragmatic Engineer — AI token spending out of control New York Times — Tokenmaxxing GitHub — Changes to Copilot individual plans TechCrunch — China vetoes Meta's $2B Manus deal Reuters — Blocking Meta's AI startup buy raises risk for cross-border China tech deals

Meta installed monitoring software on every U.S. employee laptop — keystrokes, clicks, periodic screenshots — to train AI agents that will replicate white-collar work. CTO Andrew Bosworth confirmed there is no opt-out. The same week, Meta confirmed 8,000 layoffs. Europe blocked the program at the border under GDPR. The United States did not. Stephen unpacks the deeper question every CEO is about to face: every company building internal AI agents needs proprietary training data. Where does yours come from? Three takeaways for your leadership team: Write the one-page workplace-monitoring policy now, before a vendor pitches the line and HR has to react in a meeting. Route this to the CHRO, not the CIO. It is a labor question wearing an IT costume. Map your proprietary workflow data this quarter. The cost curve on observation has collapsed; the question is what you will not ask for at any price. Sources: Platformer — Casey Newton on Meta's MCI program The Lives of Others (2006) — referenced in episode The YPO Technology Network AI Brief publishes Monday through Friday. Forward to a fellow member if it was useful.

MCP — Model Context Protocol — has gone from a curiosity to enterprise infrastructure in less than a year. Last Friday, the Linux Foundation made it official, formalizing MCP under its new Agentic AI Foundation alongside production integrations from SUSE, AWS, and Fujitsu. Translation: it is now the standard your engineers are building on. In this episode, Stephen Forte explains: What MCP actually is — the USB-for-AI analogy, in plain language, no developer experience required Why it became default — Anthropic, OpenAI, Google, Cursor, LangChain, LiteLLM, IBM LangFlow all support it Why it cannot be deployed alone — the protocol is open by design, and an open protocol without a wrapper is a powerful electrical outlet with no cover The AgentOps layer your team needs — gateway, identity, logging — same pattern as DevOps, new layer of the stack Three direct questions to ask your CTO this quarter, and why naming a single owner matters more than convening a committee Brex (the corporate-card and spend-management fintech) made the point cleanly this week with the open-source release of CrabTrap — a small proxy that watches every HTTP call an agent makes before it goes out. A 306-practitioner study published this month puts the urgency in numbers: 82% of organizations have agents in production or pilot, and the number-one cited challenge is reliability, not capability. The protocol your engineers are excited about is genuinely useful and genuinely standard. The work of making it safe to operate is a separate budget line and a separate skill set — and it is the price of admission for running this stuff in a real company.

Google retired Vertex AI in a single afternoon and replaced it with the Gemini Enterprise Agent Platform — what Sundar Pichai called "mission control for the agentic enterprise." Stephen Forte argues this is the moment AI agents got an HR system: cryptographic identity, a directory, an access gateway, and a performance review. In this episode: Why Vertex AI is gone — and what the replacement actually does The four pillars of the Agent Platform translated into HR terms (hire, deploy, supervise, review) The traction numbers Google disclosed: 40% QoQ growth, 8M seats, 2,800 enterprises The structural reveal: Anthropic crossed $30B annualized revenue — and is now Google Cloud's largest TPU customer Two concrete moves to make this quarter, plus one CEO-mirror question to leave you with The closing line: The compute will commoditize. The control plane will not. Sources: Google Cloud — Introducing Gemini Enterprise Agent Platform ComputerWeekly — Pichai mission-control framing Infosecurity Magazine — Kurian zero-trust quote Google Cloud Docs — Agent Identity overview Business Analytics Review — A2A protocol and Anthropic on TPU

Most AI conversations happening in boardrooms right now are cost conversations — G Piper is the AI sales agent running 24 hours a day on the website Clay — data enrichment platform that builds full buyer profiles from dozens of sources Artisan — autonomous outbound agent that writes and sends prospecting emails using enriched profiles Zapier — workflow orchestration layer connecting CRM, enrichment, inbound, outbound, and Slack Claude Opus via Replit — custom strategy layer built on Anthropic's model; runs as an AI VP of Marketing producing the morning brief Gamma — AI presentation tool that drafts decks from a brief when agents book meetings The numbers: $4.8 million in pipeline sourced first-touch by AI agents. $2.4 million closed from that same source. Team size moved from eight-to-nine humans down to 1.2. Total monthly cost for the connected stack: $2,000 to $5,000. Source: Jason Lemkin's original post — the eight-month postmortem that forms the basis of this episode. The AI Brief is a weekly episode from the YPO Technology Network, covering applied AI for CEOs and senior executives. New episodes every Monday and Friday.

The old salty guy problem. The senior operator who knows everything and is about to walk out the door with fifteen years of judgment. This episode is the framework for capturing what he knows before the fire goes out. No news cycle coverage today — we pivot to a single-thesis deep-dive on the retiring-expert problem. We introduce The Campfire Protocol, a 7-phase framework for turning tribal knowledge into an operational asset that survives the person. The stakes. Boeing 737 MAX: $1.6 billion in direct losses traced to lost institutional knowledge. Shell ROCK: $300 to $400 million per year in retained value. NASA, unable to recover its own spacesuit manufacturing expertise, awarded Axiom a $1.3 billion contract in 2022 to rebuild what it had lost. The 7 phases: CONSENT — the legal and personal permissions CORPUS — every artifact the expert has touched DISCOVERY — structured interviews on decision-making patterns INTERVIEW — recorded, transcribed, tagged ground truth SHADOW — AI watches the expert work for 30 to 90 days HANDOFF — the successor works with the AI for 90 days with the expert available STEWARDSHIP — ongoing maintenance so the knowledge base does not decay Failure and success cases: IBM Watson at MD Anderson — $62 million written off in 2017 Eudia at Duracell — outside counsel costs cut 50 percent by augmenting, not replacing NASA spacesuits — 19-year gap, full rebuild required Legal anchors: California AB 2602 and SB 683, Tennessee ELVIS Act, Moffatt v. Air Canada (2024), Mobley v. Workday (2025) class cert, iTutorGroup EEOC $365,000 settlement, DDB Technologies v. MLB (2008). The economics. Annual recurring: $18,000 to $24,000. One-time build: $70,000 to $175,000. Tooling: Guru, Dust.tt, Fathom, Fireflies, AssemblyAI, Microsoft Presidio, ElevenLabs PVC, Delphi.ai, Synthesia, HeyGen, D-ID. "The campfire does not scale. The campfire goes out." "You are not cloning a person. You are keeping the fire." "The goal is to never lose the conversation." If this was useful, send it to a fellow member. Stay sharp.

The UK government quietly confirmed an AI model just completed the hacking equivalent of a four-minute mile. Eleven of the largest companies on Earth already have a copy. The threat model you were operating under on Friday is not the one you are operating under today. In this episode: What Claude Mythos actually did on AISI's 32-step "Last Ones" test — and why Anthropic's own safety team called it "the greatest alignment-related risk" they've released The Roger Bannister four-minute mile analogy — why one lab crossing a capability barrier changes what every other lab believes is possible Project Glasswing — the eleven companies with access (AWS, Apple, Cisco, CrowdStrike, Google, JPMorgan, Microsoft, NVIDIA, Palo Alto Networks, Goldman Sachs, Linux Foundation) and the oversight framework that isn't public Why your threat model shifted from nation-states to "everyone who has ever been angry at you and kept a copy of something" The three-step playbook to ask about by Friday: kill switches (1-10-60 rule, CrowdStrike/SentinelOne/Defender isolation), agentic security platforms reading your logs 24/7, and immutable 3-2-1-1 backups (Veeam, Rubrik, Commvault, AWS S3 Object Lock) The CEO mirror — a three-column credential audit to take into your next forum meeting Key line: "The tool does the skill. The tool does the twenty hours of work. A motivated amateur with a Claude API key and a grudge is now a credible threat." Cybersecurity used to be a specialist problem. It is now an operational problem. It belongs in the same meeting as insurance and succession. The YPO Technology Network AI Brief is a daily, peer-to-peer podcast for YPO members (CEOs and Presidents of $13M+ companies) making sense of AI without the hype. Produced by BuildClub.

Welcome to the YPO Technology Network AI Brief with Stephen Forte. Every weekday morning in about ten minutes, Stephen walks you through what actually happened in AI — and what it means for the company you run.Not the hype cycle. Not the vendor press releases. Just answers, through the CEO lens, with a take.Weekdays at 6am Eastern. Saturdays, a longer weekend edition.Follow the show and share it with a fellow member.

Episode summary. Sam Altman says a world-shaking AI cyberattack is coming within twelve months. The proof of concept arrived this weekend: one Roblox download on a personal device triggered a three-company breach that ended with Vercel's source code, GitHub tokens, and NPM publishing keys for sale on BreachForums. Stephen Forté connects the warning, the breach, and the architectural fix most companies have not yet implemented — giving every AI agent, tool, and integration its own machine identity.Why this matters. AI is no longer a tool sitting next to your business. AI is the attack surface. The new physics is clear: your security perimeter now includes every AI tool used by every vendor of every employee of every customer. The fix is not another seat license — it is plumbing, and your CIO can implement it this quarter.What this episode covers:Sam Altman's Axios interview and why frontier-lab safety data backs the warning — Anthropic's 99% valid zero-day finding rate, and the $2,283 / 20-hour discovery of Chrome CVE-2026-5873.The Vercel breach chain of custody: Lumma Stealer → Context.ai OAuth tokens → Vercel mailbox → GitHub + NPM. 580 employee records, undisclosed API keys, sold by ShinyHunters for $2M.The GitGuardian 2026 numbers: 28M hardcoded secrets exposed in 2025, AI credentials up 81% YoY, 24,000 unique creds leaked from MCP config files alone.The architectural fix: machine identity and agent-level authentication — treating every AI tool, agent, and integration as its own authenticated principal rather than sharing an employee's OAuth token.The three questions to take to your CIO and CISO this week.Key takeaway. The breaches coming in 2026 will not look like the breaches of 2024. The attacker does not need to beat your security team. The attacker walks through three companies on a single thread of inherited AI trust. Identity is the new perimeter — and AI agents need identities of their own.Hosted by Stephen Forté for the YPO Technology Network.

Sam Altman warns of a world-shaking AI cyberattack. Vercel gets breached because someone downloaded Roblox. The fix is not another seat license — it is architectural.In this episode, Stephen Forte unpacks the Context.ai supply chain incident, the Claude Opus Chrome zero-day discovered for $2,283 in twenty hours, and then pivots into the three-layer architectural pattern almost no company has built yet: dedicated machines, scoped agent identities, and managed secrets.Stories coveredSam Altman’s warning to Axios of a world-shaking AI-powered cyberattack within twelve monthsAnthropic’s internal safety evaluation showing Claude Opus finds valid zero-days 99% of the timeClaude Opus discovering Chrome zero-day CVE-2026-5873 in 20 hours for $2,283 in computeThe Vercel breach chain of custody — Lumma Stealer → Context.ai OAuth tokens → Vercel GitHub and NPM accountsGitGuardian’s 2026 State of Secrets Sprawl: 28M secrets exposed, AI credential leaks up 81% YoY, MCP config files leaking 24,000 credentialsThe architectural prescriptionLayer 1 — Dedicated machine: Mac mini, cloud VM, or Cisco Secure AI Factory. Aligned with IEEE-USA sandboxing guidance to NIST.Layer 2 — Scoped identity: Own email, own IAM role, own audit trail. Microsoft Entra Agent ID, Okta agent identity, Google Cloud Agent Identity (“cryptographically attested”).Layer 3 — Managed secrets: AWS Secrets Manager, Azure Key Vault, Google Secret Manager, HashiCorp Vault (dynamic secrets), or 1Password Secrets Automation.The numbers that matter60% of breaches involve the human element (Verizon DBIR 2025)Stolen credentials are the #1 initial access vector at 22%; phishing is #3 at 16%91% of companies deploy AI agents; only 10% have a governance strategy (Okta)76% of organizations report growth in non-human identities (SANS Institute, April 2026)Machine identities outnumber human identities 45:1 to 144:1SourcesTechCrunch — Vercel confirms security incident via Context.ai breachThe Hacker News — Vercel breach tied to Context.ai hackBleepingComputer — Vercel confirms breach<a href="https://vercel.com/kb/bulletin/vercel-april-2026-security-incident" rel="noopener norefe

Episode summary. On February 17, 2026, federal Judge Jed Rakoff issued the first nationwide ruling holding that conversations with consumer AI chatbots are not protected by attorney-client privilege and are fully discoverable in litigation. Six weeks later, the Delaware Court of Chancery used a CEO's deleted AI chat logs as trial evidence in a $250 million earnout dispute. This episode walks CEOs, GCs, and CISOs through what the courts actually held, what it means for your company in practice, and the five specific moves to make this week.Why this matters. Every prompt your employees type into ChatGPT, Claude, Gemini, or Copilot is now a timestamped, logged document living on a third party's servers under terms that explicitly permit disclosure to regulators and courts. The candor of AI conversations — precisely because employees feel they are thinking in private — makes them disproportionately damaging in discovery. This is the AI wake-up call, and it lands harder than email did in the 2000s or Slack did in the 2010s.The Four Rulings You Need to Know1. United States v. Heppner — No. 25 Cr. 503 (JSR), 2026 WL 436479 (S.D.N.Y. Feb. 17, 2026). Judge Jed S. Rakoff, Southern District of New York. The anchor case. Bradley Heppner, former Chair of GWG Holdings, was indicted for securities fraud allegedly costing investors more than $150 million. Facing a grand jury subpoena, he used the free version of Anthropic's Claude to generate 31 documents analyzing his defense strategy and shared them with Quinn Emanuel. FBI agents seized the documents during a Dallas search warrant. The government moved to compel. Rakoff — calling it "a question of first impression nationwide" — ruled the documents were not privileged on three independent grounds and found they may have even waived privilege over the original attorney-client communications Heppner had pasted into Claude.2. Fortis Advisors LLC v. Krafton, Inc. — C.A. No. 2025-0805-LWW (Del. Ch. Mar. 16, 2026). Delaware Court of Chancery, Vice Chancellor Will. Krafton acquired Unknown Worlds Entertainment (maker of Subnautica) for $500M up front plus a $250M earnout. When the deal soured, Krafton's CEO used an AI chatbot to draft a "Response Strategy to a No-Deal Scenario" including a "pressure and leverage package" and a "two-handed strategy" combining legal pressure with softer retention offers. The court quoted the AI logs extensively to establish pretextual intent — and noted the CEO's admitted deletion of some logs may "factor prominently" in the damages phase. Civil discovery, not criminal. The reasoning travels.3. Warner v. Gilbarco, Inc. — No. 2:24-CV-12333, 2026 WL 373043 (E.D. Mich. Feb. 10, 2026). Magistrate Judge Anthony P. Patti. A pro se plaintiff in an employment discrimination case used ChatGPT to prepare filings. The court upheld work product protection on narrow facts — a pro se li

Healthy-company layoffs are no longer just a lagging indicator of weakness. In this weekend edition, Stephen Forte argues they can be an early signal of organizational redesign — and explains what mid-market CEOs should do before the pressure shows up in their numbers.What this episode covers:Why this wave of layoffs is different from 2009 and different from the 2023 over-hiring correctionWhy many strong companies are redesigning around new information economics, not just cutting costsWhy most mid-market firms should not copy Block directlyThe pattern Stephen sees across successful and failed AI adoption effortsA practical 90-day playbook for CEOs: pick two workflows, map them properly, run shadow mode, define decision rights, and learn from overridesKey idea: the real shift is not AI as a tool. It is AI as a change to how context moves, how decisions get made, and what parts of management remain valuable.If your company is healthy, that is not a reason to delay this work. It may be the best reason to start it.

Stephen Forte explores why AI investments are failing and the answer is not what you think. Drawing on the CIA 1944 Simple Sabotage Field Manual and a landmark 2026 survey showing 29 percent of employees actively sabotage their company AI strategy, he unpacks the invisible resistance destroying AI ROI.The CIA Manual: How 80-year-old bureaucratic sabotage tactics are alive and well in your AI steering committeeThe Data: 29 percent sabotage rate (44 percent among Gen Z), plus a 30-point perception gap between executives and employeesThe Failure Landscape: 95 percent of AI pilots deliver zero ROI (MIT), with BCG attributing 70 percent of failure to people, not technologyThe Fear Factor: 89 percent of workers worried about job security, 55,000 AI-related layoffs in 2025The Spectrum of Resistance: From overt refusal to invisible pretenders, plus the vicious cycle that makes sabotage look like technology failureThe Solution: Champion networks achieve 3x implementation success. Find the domain experts already using AI on their ownKey insight: The programming language of this era is English. The real skill is domain expertise. Find your champions, reward them, and let your laggards self-select out.Sources: Writer/Workplace Intelligence 2026 Survey, MIT NANDA Initiative, BCG, RAND Corporation, ADP Research, Aalto University, CIA Simple Sabotage Field Manual (1944)

Today, one thread ties together a thousand layoffs at Snap, a survey showing the majority of C-suite leaders admitting AI is fracturing their organizations, and Molotov cocktails thrown at a tech CEO home. That thread is the cost of what you, as a leader, have not yet said.Snap cuts 1,000 jobs (16% of workforce) citing AI productivity. CEO Evan Spiegel was direct. Most CEOs have not been.Writer 2026 survey of 2,400 executives: 54% of the C-suite say AI is tearing their company apart. 97% deployed agents, only 29% see ROI. 35% cannot shut down a rogue agent.Physical attacks on AI leaders: Molotov cocktails at Sam Altman home, 13 bullets through an Indianapolis councilman front door over a data center vote.The thesis: Having no AI policy is a policy. You are just letting fear set it for you.Hosted by Stephen Forte.

Every adoption metric just crossed the line — and the line turns out to be behind us. Three stories about AI adoption outrunning governance at a pace no one predicted.Stories covered:The 50% Line — Gallup's Q1 2026 workplace survey of 23,717 employed adults finds 50% now use AI at work, up from 46% last quarter. But only 41% of organizations have formally integrated AI — meaning roughly 14 million American workers are using AI tools their employer hasn't approved or secured.CyberStrikeAI: 600 Firewalls in 5 Weeks — A free, open-source AI tool autonomously compromised 600+ Fortinet FortiGate firewalls across 55 countries. No zero-day vulnerabilities needed — just exposed management interfaces and weak authentication. The barrier to autonomous cyberattack just dropped to zero dollars and a laptop.96% Agents, 12% Governed — OutSystems surveyed 1,900 IT leaders: 96% are already using AI agents in production, but only 12% have centralized governance. Gartner forecasts 40% of enterprise applications will include task-specific agents by end of 2026, up from 5% in 2025.Action items:Ask your CISO about exposed management interfaces and single-factor authentication gaps — today, not next quarterFind out what percentage of your workforce is using AI tools IT hasn't provisionedCount your agents — if nobody can give you a number, that is the number that matters mostHosted by Stephen Forte. New episodes weekdays.

Three stories about how AI companies stopped competing on capability and started competing on leverage — and what the squeeze means for every CEO writing checks right now.Stories covered:Musk's Grok Toll Booth — The New York Times confirmed Elon Musk is requiring every bank advising the SpaceX IPO to purchase Grok enterprise subscriptions. Goldman Sachs, JPMorgan, Morgan Stanley, and others have committed tens of millions. Not because Grok won a bake-off — because the alternative is losing access to $500M+ in advisory fees from a $50B+ raise.GPU Prices Surge 48% — The Ornn Compute Price Index shows Nvidia Blackwell GPU rentals now cost $4.08/hour, up from $2.75 eight weeks ago. Half of planned 2026 data center builds are delayed — not by chips or capital, but by 5-year lead times on high-voltage electrical transformers.OpenAI Kills Sora — OpenAI is discontinuing its video generation tool with roughly six months notice. A Futurum Group survey found 61% of enterprises cite OpenAI as their primary generative AI platform — raising hard questions about single-vendor dependency.Action items:Lock in compute contracts before the next price jumpBuild optionality into your vendor stack before a deprecation notice forces your handIf 40%+ of your AI workloads run on a single vendor, draft a migration playbook nowHosted by Stephen Forte. New episodes weekdays.

Three stories exploring the gap between what we believe and what the data shows in AI.Anthropic Mythos / Project Glasswing — An AI model too dangerous to release is now controlled by eleven handpicked organizations and the White House. That is not a safety framework. That is a guest list.OpenAI Acquires TBPN — OpenAI spent hundreds of millions to buy a podcast. It reports to their chief political operative. The sole financial relationship is now OpenAI. When you cannot control the narrative through technology, you buy the megaphone.AI Coding Quality Collapse — Six independent studies converge on the same finding: AI-generated code has more bugs, and developers using it believe they are faster when they are actually 19% slower. The 39-point perception gap is the largest ever documented.

Weekend Special Edition | Saturday, April 11, 2026Anthropic launched Claude Managed Agents in public beta on April 9, 2026. The infrastructure problem that was killing enterprise agent projects between prototype and production is now a managed service. This episode goes deep on what changed and what to do about it.What we cover:Claude Managed Agents: four core capabilities — secure sandboxing, long-running autonomous sessions, multi-agent coordination (research preview), and a full governance layer. Pricing: standard token rates plus $0.08/session-hour.The three-agent harness: Planner expands your 1-4 sentence prompt into a full product spec. Generator builds in sprint rounds. Evaluator interacts with the live application via Playwright — clicking through UI, testing API endpoints, checking database states — and grades output against calibrated thresholds, running 5-15 iteration cycles until complete.The context problem solved: externalized state via JSON specs, progress logs, and git commits rather than in-context memory. The Ralph Loop prevents premature completion claims.Early adopters: Notion, Asana, Rakuten (10x faster agent delivery, 22-point task success improvement), Vibecode.The five-point executive playbook: find your stalled agent project, scope by workflow not AI capability, separate generators from evaluators in every AI process, design governance before scaling, get on the multi-agent coordination waitlist at claude.ai.Hosted by Stephen Forte, YPO Tahoe Integrated, YPO Miami Gold, YPO London Gold

OpenAI published a 13-page policy paper on April 7, 2026 — the same morning The New Yorker published a 1.5-year investigation into Sam Altman's trustworthiness on AI safety. This episode reads OpenAI's proposals not as forward-looking policy, but as a pre-apology for disruption that is already underway and already documented.In this episode:What OpenAI is actually proposing: a four-day work week, a Public Wealth Fund, a robot tax, worker voice mechanisms, and mandatory AI safety auditingHow each proposal maps to a specific, documented harm — including 60,000 job cuts in March alone and $852 billion in AI-driven capital concentrationOpenAI's two-year lobbying record against the exact safety policies the paper now endorsesThe timing collision: the policy paper and the New Yorker investigation dropped on the same dayWho is funding the D.C. think tanks that will define responsible AI policyA closing question for every CEO: could your company write the equivalent internal document?Sources:OpenAI — Industrial Policy for the Intelligence AgeTechCrunch — OpenAI's vision for the AI economyFortune — Sam Altman says AI needs a New DealAbout the show: The YPO Technology Network AI Brief is a daily podcast for YPO members — CEOs and company presidents — covering AI developments with direct business impact. Hosted by Stephen Forte.

One Employee Destroyed a Warehouse. Now Imagine Your Network. | April 9, 2026A Kimberly-Clark warehouse in Ontario, California is gone — 1.2 million square feet, total loss — because one employee had access, motive, and fuel that was already in the building. This episode traces that pattern from the physical world into the digital: 500,000 tech layoffs coming this year, the SolarWinds supply chain attack explained, and last week’s AI-era version of the same breach — 40 minutes, three major AI labs in the blast radius simultaneously.What we cover:The Ontario warehouse fire: Chamel Abdulkarim, 29, arrested on felony arson charges after destroying a 1.2M sq ft Kimberly-Clark distribution center serving 50 million peopleThe layoff fuse: 78,557 tech cuts in Q1, 9x increase forecast this year — every departing employee walking out with system knowledge, credentials, and potentially still-active accessSolarWinds explained: Russian intelligence spent 14 months inside US government networks — Treasury, Homeland Security, State, DOE — through a trusted update that 18,000 organizations installed voluntarily. $90M+ recovery. First CISO ever charged by the SEC.AI’s SolarWinds: LiteLLM poisoned on PyPI for 40 minutes, cascading to Mercor — supplier to OpenAI, Anthropic, and Google simultaneously — 4TB claimed stolenThree actions: offboarding access audit, AI supply chain dependency monitoring, AI-powered log monitoringKey data:1.2M sq ft warehouse, total loss — one person, no specialized skills78,557 Q1 tech layoffs | 47.9% attributed to AI | 9x increase forecast 2026SolarWinds: 18,000 orgs | 14 months undetected | $90M+ recovery | 11% avg revenue impactLiteLLM attack: 40 minutes active | all 3 top US AI labs in blast radius | 4TB claimedIBM X-Force: 4x increase in supply chain attacks since SolarWindsSources:LA Times: Kimberly-Clark Warehouse FireTom’s Hardware: Q1 2026 Tech LayoffsBreachsense: SolarWinds Case StudyMercor/LiteLLM BreachMandiant: SolarWinds SUNBURST AnalysisHosted by Stephen Forte, YPO Tahoe Integrated, YPO Miami Gold, YPO London Gold

The Citizen Hacker | April 8, 2026Anthropic built an AI model so capable at finding security vulnerabilities that it cannot be released to the public. Claude Mythos Preview has already found thousands of high-severity flaws in every major operating system and browser, including a 27-year-old bug that survived decades of expert review. This episode unpacks what that signals about corporate security today, introduces the citizen hacker, and closes with five specific moves every company needs to make before this month is out.What we cover:The model Anthropic won't release: what Claude Mythos found, and what it means that it found these flaws entirely autonomouslyThe reality check: 94% of passwords reused, breaches taking 328 days to detect, hackers paying employees up to $15,000 for network accessThe citizen hacker: how vibe coding's mirror image is already attacking companies at scaleThe five moves: credential audit, AI log monitoring, agent governance, behavioral monitoring, continuous patchingKey data:74-95% of breaches involve the human element (Verizon / SentinelOne 2025)Average credential breach detection: 328 daysTime-to-exploit: negative one day (Mandiant 2025)Insider risk: $19.5M per organization annually (Ponemon 2026)Attacker breakout time: 29 minutes, down 65% (CrowdStrike 2025)Global ransomware damage: $74 billion in 2026 (Cybersecurity Ventures)Sources:Anthropic Project GlasswingSecureframe 2026 Data Breach StatisticsMandiant: Negative Time-to-ExploitPonemon/DTEX 2026 Cost of Insider RisksForrester: Vibe Hacking and No-Code RansomwareCybersecurity Ventures: Ransomware Damage 2026Hosted by Stephen Forte, YPO Tahoe Integrated, YPO Miami Gold, YPO London Gold

This episode of the YPO Technology Network AI Brief, hosted by Stephen Forte, maps the agent explosion happening across every major enterprise platform — and explains why the right move is neither consolidation nor inaction.Key topics covered:Why Salesforce, Notion (21,000+ custom agents), Jira, Zoom, monday.com, and Asana all shipped autonomous agents in the same quarterThe governance crisis: 3M+ corporate AI agents in deployment globally, with only 47% monitoredScenario: Velocity Digital (400-person agency) discovers 31 unauthorized agents running for six weeksThe experimentation thesis: why picking one agent now is the wrong moveScenario: Meridian Financial's 90-day, $180K experiment generates a projected $2.1M annual productivity gainFour structural differentiators: model flexibility, local access, data connectivity, and governance surfaceArthur AI's Agent Discovery platform as an early governance responseQuotable close: "The window for informed experimentation is roughly 90 days before market consolidation starts making the decision for you."Hosted by Stephen Forte for the YPO Technology Network.

In this episode of the YPO Technology Network AI Brief, Stephen Forte examines Microsoft's multi-model Copilot rollout — one of the most substantive architectural changes in enterprise AI this year. The episode covers what's deploying now, what goes generally available May 1, and why the gap between Microsoft's installed base and active usage is a change management problem, not a technology problem.Key topics covered:Multi-model Copilot: Critique and Council modes — GPT and Claude reviewing each other's work, producing a 13.8% improvement on the DRACO research benchmark; Council mode runs multiple models in parallel and synthesizes where they agree and divergeCopilot Cowork and Agent 365 — long-running agentic work that continues after you close the browser, currently in the Frontier program with Capital Group; Agent 365 goes GA May 1 at $15/user/monthThe adoption gap — Microsoft has 400 million installed users but only 15 million paid Copilot seats (3.3% penetration); of those, only 35.8% are actively using the product versus ChatGPT Enterprise's 83.1% activation rateCopilot Studio model marketplace — April GA brings a platform where enterprise developers can orchestrate Claude, GPT, and Grok models against internal data via Fabric integration and the Agent-to-Agent protocolPricing referenced:Agent 365: $15/user/month (GA May 1)Microsoft 365 E7 bundle (E5 + Copilot + Agent 365): $99/user/month (GA May 1)Copilot enterprise: $30/user/month; SMB: $21/user/monthHosted by Stephen Forte for the YPO Technology Network.