
Hosted by Stephen Forte · EN

For two years, CEOs argued about AI in the abstract. This week the most sophisticated, most heavily regulated enterprises on earth put audited numbers on it in their Q2 earnings. JPMorgan's Jamie Dimon says AI has cut jobs by 30 to 40 percent in discrete units across roughly 1,000 use cases; Citi says nearly nine in ten of its people now use its AI tools; Bank of America's assistant Erica handled 200 million customer interactions in a single quarter. AI at scale is real — but Dimon's tell is the story: the gains "accrue to the customer, not to JPMorgan," because every competitor is doing the same thing.Meanwhile Morgan Stanley says the AI capex cycle is only 10 to 15 percent complete, even as IBM lost a quarter of its value in a day and investors just named AI spending the market's single biggest risk. Stephen Forte on why AI is becoming table stakes, not a moat — and what that changes about where you spend next.

Every conversation your people are having with an AI right now is a business record — discoverable in a lawsuit, usually not privileged, and in most companies quietly set to auto-delete until the moment that becomes illegal. A Delaware court this spring removed a CEO and reinstated his predecessor over a $250 million earnout, and the decisive evidence was the CEO's own ChatGPT logs — including ones he had deleted. OpenAI is fighting a sanctions motion for allegedly destroying billions of ChatGPT conversations after a court told it to preserve them. And a federal judge ruled that a defendant's chats with a consumer AI were not privileged, because the AI is not a lawyer.Stephen Forte on what this teaches every CEO, the records-retention rules to set this quarter (with real numbers by industry), and the single best place to do genuinely confidential AI work: an open-weight model running on hardware you own, where there is no vendor log to subpoena.

The clearest signal yet about how risky enterprise AI really is did not come from a lab or a regulator. It came from the insurance industry, whose entire business is pricing risk — and which is now quietly refusing to price this one. Major carriers including Chubb, Travelers, Berkshire Hathaway, and W.R. Berkley have filed and won approval for explicit AI exclusions across general-liability, directors-and-officers, and errors-and-omissions policies; the standard industry exclusion form took effect on the first of the year, and regulators have approved more than 80% of the requests. The reason underwriters give is blunt: the risk cannot be priced.This week handed them two live examples — a GitHub AI agent tricked into leaking private code through a public comment, and a 35-gigabyte data-theft claim against Accenture. Stephen Forte on why "silent AI" coverage is disappearing, why your balance sheet is quietly absorbing the risk, and the three things to build before an insurer will cover your AI again.

Everybody spent two years being told AI would change everything, and this month the mood flipped to a smaller, sharper question: did it actually pay for anything? The reckoning is real and overdue, and the number underneath it is not flattering. Only about one in four companies has gotten AI into real production at scale; nearly half are still running pilots. But a small group is quietly getting real money back, and their returns have been checked by an independent firm, not the vendor that sold the software. What those companies share is almost disappointing: none of them "did AI." They each found one specific, expensive-in-hours chore and handed exactly that to the machine. Stephen Forte on the ROI reckoning, three audited examples across manufacturing, consumer goods, and frontline services, the pattern that separates the winners from the pilot pile, and the single question that tells you which group you are in.

Last week Anthropic did something that looked like a menu cleanup and was actually a strategy reveal. It merged Claude Chat, the back-and-forth you already know, with Cowork, Claude's agent that goes off and does a whole task across your files and tools, into a single home, and moved the agent to the cloud so it keeps working after you close your laptop and can even run on a schedule with no device on at all. Their own words: "handing Claude a task starts the same way a conversation does." Underneath the low-key rollout is the biggest change in how knowledge workers touch AI since ChatGPT arrived: the shift from consulting a smart assistant to assigning work to a tireless one. And Anthropic's data on 1.2 million sessions gives away what it is really for, over 90 percent of it is not software engineering, it is the administrative grind that surrounds every job. Stephen Forte on the workflow shift your team is about to feel, the four-way land grab it touched off with OpenAI, Microsoft, and Google, and the three moves to make before an always-on agent lands on your systems.

This week looked like a fireworks show of AI launches — OpenAI's GPT-5.6, new real-time voice models, Microsoft leaning on its own in-house models. The more important story ran underneath all of it: the AI inside your company has quietly become a black box you can neither see into nor fully trust. Microsoft has begun replacing OpenAI and Anthropic with its own cheaper MAI models inside Excel and Outlook — its AI chief said the goal is to "eliminate that cost." The security firm Wiz found six major AI coding assistants showed users a fake file path in their safety confirmation while writing to sensitive files. And an independent developer discovered Anthropic had run an undisclosed location tracker inside Claude Code for months.Stephen Forte on why you are now accountable for an AI you cannot inspect — and the three clauses to put in every AI contract before your next renewal: model-transparency and change-notification, an independent audit-logging layer, and a named owner for what is actually running in your stack.

The strange truth of AI in 2026 is that the technology keeps clearing bars we thought were years away — Alberta's provincial government just used Claude to scan 466 million lines of code in 20 hours, work that would have taken six and a half years by hand — while the business results stay stubbornly flat. MIT finds 95% of enterprise AI pilots deliver no measurable impact; an NBER survey of more than 6,000 executives across four countries finds roughly 90% saw no productivity gain over three years.This week the most sophisticated vendors on earth told you, in dollars, where the real bottleneck is: Microsoft committed $2.5 billion and 6,000 of its own engineers to embed inside customer companies and deploy AI for them — following Amazon's $1 billion, and Anthropic's and OpenAI's own embedded teams. Stephen Forte on why your AI bottleneck was never the model, and the three moves to make before you fund one more pilot.

Every boom has a tell, and it is never in the press releases. This week the AI boom's insiders started hedging their own story: Meta announced it will rent out its "excess" AI compute while chipmakers sold off, Oracle's SEC risk factors laid bare the strain of its $300B OpenAI/Stargate commitment, and Mark Zuckerberg told his own employees that AI-agent progress "hasn't really accelerated" as expected. Yet the same week, Abu Dhabi's MGX closed a $49B AI fund and Anthropic signed a 20-year, ~$19B data-center lease.Stephen Forte on what it means when sellers plan for surplus while buyers still pay scarcity prices — and the three moves to make before signing any multi-year AI contract: shorten and reopen, read your vendors' risk factors like a credit file, and re-run build-versus-rent every quarter.

For two years the question was "how will governments regulate AI?" This month the answer got bigger: the state wants to own a piece, police what the models say, and decide who they may serve.Ownership: OpenAI floated giving the US government a ~$42.6B (5%) equity stake (Alaska-Fund style) and wants Anthropic, Google, and Meta to follow; Altman also called for a US-led "IAEA for AI."The red-line case: the Pentagon designated Anthropic a "supply-chain risk" — a first for a US company — over its red lines against autonomous-weapons and surveillance use; a court has paused it. A vendor's values can become your outage.The rules being written this week: the FTC opened a rule treating AI "ideological steering" as deception; the UN convened 193 nations in Geneva; and the UK's FCA is weighing direct supervision of the models themselves.Host Stephen Forte on why your AI vendor is becoming a quasi-sovereign institution — and three vendor-risk moves: treat frontier access as a governed dependency, get your vendor's red lines in writing, and track the FCA/FTC/Geneva if you're regulated.Sources: FT/CNBC; Tech Times; FTC.gov; UN News; FCA.org.uk.

An extended, single-thesis episode. For a century the two biggest lines on your P&L — payroll and per-seat software — have been fixed costs sized to peak, sitting there hoping to earn their keep. Stephen Forte's belief: AI turns them into variable costs billed per outcome — per interaction, per order, per resolution.The spine: a fixed cost is a bet on utilization; a variable cost is a bill for results.Two live proofs: Medicare's new ACCESS model pays organizations only when AI-supported chronic care hits measurable health outcomes; Salesforce's Agentforce charges $2 only when its agent resolves a ticket.The capstone: adopting AI properly isn't bolting a tool onto the org chart — it's rewiring the company's operating system (why MIT found 95% of GenAI pilots deliver no P&L impact: they installed new software on the old OS).Plus four moves to make this quarter — and why Stephen has bet his own company on this shift with pay-for-performance managed agents.Sources: CMS.gov; Salesforce; MIT NANDA; company reports.