YPO Technology Network AI Brief

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. Hosted by Stephen Forte.

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)TechCrunch — DeepSeek previews new AI model that closes the gap with frontier models (April 24, 2026)Bloomberg — Anthropic Weighs Funding Offers at Over $900 Billion Valuation (April 29, 2026)

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.