Most coverage treated the outage and the unified call for regulation as separate stories. In my opinion, they aren’t. Their arrival within the same ten-day window, wasn’t a coincidence. I’m not suggesting a conspiracy, but these stories are absolutely connected — albeit at two different levels: one operational, one existential.

Here’s what I was reading — how the whole thing unfolded, and what it means for companies looking to stay AI ready.

The Infrastructure Tells the Truth

At 11AM ET on Thursday, September 3rd, three competing AI companies went down in the same 90-minute window. ChatGPT. Claude. Grok. Tens of thousands of users couldn’t get a response. Error messages replaced conversations. Developer pipelines stopped. Customer service bots went silent. GitHub Copilot reported degraded Grok models because of “an upstream provider.” Cursor showed failed Agent turns across its platform. The fallout wasn’t contained to the AI chatbots — it cascaded into every product built on top of them.

The first instinct was to treat this as a strange coincidence. Even as recently as of this writing, conspiracy theories point to the simultaneous failures as proof of a coverup. The reporting that followed over the course of last week, made clear it wasn’t.

All three platforms rely on Microsoft Azure for their cloud infrastructure. Azure’s East US region logged disruption reports the same morning. Downdetector recorded 37,000-plus reports for ChatGPT, 1,324 for Claude, and 1,365 for Grok — each curve rising and falling on nearly identical timing. Infrastructure researchers describe that pattern as a shared control-plane failure: when a routing or load-balancing layer that multiple services share develops a fault, every service on that layer degrades simultaneously — regardless of how architecturally distinct those services appear at the application layer. (The Register; Axios)

The fact that Gemini didn’t go down was actually the most revealing data point of the week. Google’s AI — running on Google Cloud, not Azure — logged only about 500 reports at the peak. Three products competing for the same enterprise budgets, and the same market narrative, turned out to share the same foundational infrastructure. The one running on it’s own cloud kept working. (TechTimes)

Many organizations have been relying on multiple platforms for their teams. ChatGPT for marketing, Copilot for general productivity, Claude via API for internal tools — might look like diversifying your AI exposure. But on September 3rd, when all three failed together, the infrastructure failed the diversity check.

The Microsoft impact that’s harder to explain. Two days before September 3rd, Microsoft 365 had already gone down in a more serious and separate event — a core authentication misconfiguration took Teams, Exchange Online, OneDrive, SharePoint, Copilot, Defender XDR, and the M365 Admin Center offline simultaneously. Microsoft attributed it to “an issue in a core authentication configuration used by multiple Microsoft 365 services.” The incident, identified as MO1465074, ran across two days. Then, on September 9th, copilot.microsoft.com went down for 90 minutes due to a Cloudflare routing error. Then a 4-plus-hour M365 Copilot warning event on September 11th. (TechCrunch; The Register)

Four Copilot disruptions across eleven days, when organizations are most aggressively deploying AI as a core productivity tool in their Microsoft environment.

None of the three AI companies has released a formal postmortem or officially confirmed that Azure was the common cause. OpenAI described its event as “a routing error starting around 7:43 AM PT.” Anthropic declined to comment beyond its status page. xAI blamed a Memphis compute center outage for Grok. These explanations are technically non-overlapping. They are also deeply consistent with a scenario in which one upstream event propagated through three networks. Each company was experiences and reacting to its own local version of the same failure. As of this writing, no one has confirmed or denied that reading — which is its own kind of answer. (Finelo; Oliver Willis)

For the organizations I work with: this isn’t about cloud vendor preference. It’s about understanding the actual dependency map of your AI stack before an outage makes it visible. The tools you’re using may be from three different companies. The infrastructure beneath them may be one shared decision. That’s worth knowing now.

The Safety Debate Went Mainstream

Six days after the outage, on Tuesday September 9th, a former Anthropic researcher named Jacob Coxon posted a resignation letter on X. By that evening it had 110 million views. By Wednesday, 115 million.

Coxon had spent four months at Anthropic after years doing pretraining research at OpenAI. He left two months before his equity vested — something he confirmed explicitly in a follow-up interview with Axios, presumably to establish he had nothing financial to gain from speaking. Here’s what he said: “The people building AI earnestly believe that it could kill us all by the end of the decade. This is not a marketing stunt. If anything, many executives and senior researchers will couch their phrasing in the press to sound sensible — but I hear the same people express fear privately. No other human activity poses this level of danger.” (Axios)

What happened next was, arguably, more shocking than Coxon’s initial post. Evan Hubinger, who leads Anthropic’s Alignment Science team, agreed with his assessment — publicly. “Jacob is correct here,” Hubinger wrote on X. “We really do earnestly believe AI could kill all humans! I personally think it is >10% within the next decade.” A second Anthropic employee, Samuel Marks, confirmed the same. Congress noticed. Multiple Democratic members requested briefings. Texas Rep. Greg Casar began drafting legislation to temporarily pause advanced AI development. (Axios)

In his interview, Coxon told Axios he has not seen Anthropic compromise safety to outlast competitors — but he’s concerned about the future: “If you’re under pressure to race, you have to cut corners or skip steps in the oversight process.” He also described something that used to be science fiction and is now operational reality: AI models that know when they are being tested. “That,” he said, “is just a daily fact of working with these AIs.”

Both things were visible in the same week. The technology powerful enough to prompt existential warnings from its own builders is also fragile enough to fail together on an ordinary Thursday over what may have been a routine cloud region event. The scale of the danger and the scale of the brittleness arrived in the same ten-day window.

That may be the most useful data point about where we actually are with AI.

What CEOs Are Saying Out Loud

On Saturday — a little over a week after after the failures and 4 days after Coxon’s public resignation — Dario Amodei published a 3,800-word essay titled “We Must Pace the Frontier.” The core argument: AI is advancing faster than the safety research required to govern it. Recursive self-improvement — when AI systems design or train their own successors — must be “pursued very carefully, if at all.” All AI labs should commit to embedded third-party evaluators with employee-like access. The industry must slow the pace at which it improves model capabilities. (Axios; The New York Times via Portside)

What followed was an unprecedented agreement from Amodei’s peers.

Sam Altman replied that he would commit to independent evaluators with “employee-like access.” Elon Musk, whose xAI had just blamed its own outage on a Memphis compute center six days earlier, wrote: “Dario is right.” Demis Hassabis of Google DeepMind said the direction was correct, adding that the details “need working through.” (Bloomberg via BusinessMirror)

Four of the five most powerful people in frontier AI, on record, in the same week: the pace is a problem.

Markets responded. Nvidia fell more than 3%. Micron dropped 7%. Intel lost 6%. HPE fell 10%. SoftBank — invested heavily in OpenAI — closed nearly 11% lower in Japan. South Korea’s Kospi sank 3.3%, dragged by a 6.4% fall in chipmaker SK Hynix. The Nasdaq dropped 1.8%. Altman also told Fortune separately that OpenAI would not go public in 2026 as previously planned — citing “everything happening with safety” as the reason. (CNBC; CNN)

There are reasons to read this skeptically. Amodei’s call for a mutual slowdown, while running one of the most capable labs in the world, is a tension that feels almost too easy to call out. But as other observers have also noted, his essay is as much a market positioning document as a safety manifesto — a company that brands itself on responsible development benefits when the conversation centers on responsibility. The other consideration is that whether or not the timing was strategic, the substance is certainly real. Amodei, Altman, Musk — these are the people with the most to gain from acceleration, and they are saying publicly that acceleration may not be safe.

Ultimately, so much money is at stake in this industry that it is genuinely difficult to imagine companies restraining themselves, unless the alternative becomes worse — regulatory, reputational, or both.

What’s different now is that the alternative has a face. Jacob Coxon walked away from his equity to say it; The outage showed it operationally; The CEOs cosigned it — all in matter of days.

On the Bigger Picture

The practical question for IT and business leaders isn’t whether this changes your AI direction. It probably doesn’t — not yet, not immediately. The tools still work. The productivity gains are still real. Copilot is still being rolled out. Agents are still being piloted.

But last week revealed two things that should change how you think about the AI stack underneath those investments.

The first is infrastructure concentration. The September 3rd event demonstrated that organizations running multiple AI tools from different vendors may be operating on a single shared failure domain. Building fallback logic across providers — or at minimum, understanding which of your AI workflows are actually redundant and which aren’t — is no longer theoretical risk planning. It’s operational hygiene.

The second is organizational readiness. The people who built the most capable AI systems are publicly saying the pace of development may outstrip the ability to govern what you’re building. That’s not an argument to stop. It is an argument to be deliberate. That means building clarity about what workflows now depend on AI, being honest about what happens when they fail, and being disciplined about holding the line between AI adoption as strategy and AI adoption as performance.

Over the last few years, utilization AI has become an asset. Dependance may quickly become your biggest liability.

The tools are real. The risks are real. Both can be true at the same time. The organizations that figure out how to hold both will be the ones that come out ahead — not just in productivity metrics, but in operational resilience and institutional trust.

Last week the two most uncomfortable truths about AI arrived in a single ten-day window. The infrastructure beneath these tools is more brittle and more concentrated than most organizations have planned for. And the people building the next generation of capabilities are genuinely uncertain they can control what they’re making.

Neither of those things cancels the other out. They are the same story at two different layers. The question isn’t whether to slow down, or speed up. It’s whether you’ve built an AI strategy that can survive the outages, roll backs, and kill-switches that are coming — and still stay operationally effective.

That’s it for this week’s BeAIReady brief!

If you appreciate the depth of reporting and how I connect the dots, please like, share this post, and subscribe (or share the Brief with a friend!). Thanks!

~erick

Subscribe now

Share

The ROI Gap Enterprises Can’t Close

McKinsey’s latest numbers on enterprise AI are being read as good news, and by the standard of the last two years, they are. Thirty-seven percent of organizations now attribute at least some EBIT impact to AI. But only 6% qualify as high performers, and that’s the number that matters more. The gap between the 6% capturing real earnings impact and the 31% claiming “some” is where the actual story is, and it isn’t closing. A Register piece added that most adopters still can’t point to measurable earnings impact at scale, despite two years of investment. (McKinsey says enterprise AI is finally ‘on the road to ROI’)

Gartner’s numbers, published the same week, explain part of why. Fewer than 25% of enterprises have scaled AI successfully past a single business unit. A CIO Dive piece added the harder number: just 22% have scaled AI across multiple units, and the rest are stuck somewhere between pilot and rollout. Most organizations aren’t failing at AI — they’re failing at the unglamorous work of turning a pilot into an operating process, and that’s a management problem wearing a technology costume. (Fewer than 25% of enterprises have scaled AI successfully)

That failure to scale doesn’t stop the spending. It just means the spending keeps rising without the payoff catching up. A Bain analysis found that AI could push a $10 billion consumer-packaged-goods company’s annual IT spend up 75% by 2035. A second CIO Dive piece added the mechanism: even organizations investing carefully are watching costs climb faster than the efficiency gains meant to offset them. Careful investment is still investment, and the bill is coming due before the ROI is. (Even with careful investment, AI is set to boost IT costs)

So where’s that time actually going? BambooHR has an answer. Workers now spend close to 20 days a year fixing AI’s output — errors, hallucinations, rework. Nearly half the time organizations spend “using” AI is actually time spent cleaning up after it, which means the productivity math most companies are running is fiction. (Almost half the time spent on AI is on fixing its output, BambooHR says)

Four data sets, one story: enterprises are spending more, scaling less, and burning a chunk of whatever gains they get on cleanup. That’s not a technology failure. It’s an execution failure, and it’s the same one from two years ago — just with bigger numbers attached.

The Frontier Labs Are Cutting Prices, Not Risk

Anthropic’s new Fable release undercuts its own pricing while promising less restriction and zero data retention — a combination clearly aimed at enterprise buyers who’ve been sitting on the sidelines over compliance concerns. A TechCrunch piece added that zero data retention lets clients run Anthropic’s models entirely on their own infrastructure, with no data leaving the building. Anthropic is selling control as much as it’s selling capability, and for a lot of IT leaders, that’s the more persuasive pitch. (Anthropic’s new Fable release is cheaper, less restrictive)

OpenAI moved the same direction days later, rolling out GPT-6 Astra to top-tier ChatGPT plans at half the rate of GPT-5.6 Sol. A Decoder piece added that the $200 Pro plan now includes 200 GPT-6 Pro messages a week — a meaningfully better deal than the prior tier offered. Both labs cutting prices in the same week isn’t a coincidence. It’s competitive pressure, and someone is going to lose that pricing war. (OpenAI rolls out GPT-6 Astra to top-tier ChatGPT plans at half the rate of GPT-5.6 Sol)

A PYMNTS piece added that OpenAI and Anthropic both get roughly 80% of their revenue from the top 1% of customers — the same week both labs pushed price cuts into the mass market. The mass-market pricing push and the whale-dependent revenue base pull in opposite directions, and only one of those strategies wins. (OpenAI and Anthropic Get 80% of Revenue From 1% of Customers)

If the enterprise whales are what actually pays the bills, cheaper consumer tiers look less like strategy and more like scale-chasing while the real business sits somewhere else, mostly unaffected by any of it.

What Working AI Actually Looks Like

A health system built AI into its clinical workflow from day one, and the results look different from most of what showed up in Section 1. The system serves 240 physicians and roughly half a million patients, using a tool called ScopeAI to deliver clinical background before a patient consultation even starts. An HR Executive piece added that the goal was never to replace physicians — it was to cut the cognitive load of chart review so doctors could spend consultation time on the patient instead of the screen. This is what AI adoption looks like when it’s built around a specific job to be done instead of a mandate to “use AI” — narrow, embedded, and judged by whether physicians actually want to keep using it. (Adoption lessons from the nation’s first AI-native health system)

The piece doesn’t offer hard outcome metrics, and that’s a real gap — a case study without a number is a story, not proof. But the contrast with Section 1 matters: fewer than 25% of enterprises have scaled AI successfully, and here’s one that did, in one of the more change-resistant, high-stakes environments in the economy. Scale doesn’t require every function in the company to touch AI at once. It requires one workflow, done well, that the people using it don’t want to give up.

The Layoffs Keep Coming, Hiring Keeps Rising

September’s WARN notices are already stacking up, with another wave of major companies confirming workforce reductions this month. An IBTimes UK piece added a detail that cuts against the doom narrative: hiring is up 25% compared to last year, even as the layoff headlines keep coming. Layoffs and hiring are climbing at the same time, which means the labor market isn’t shrinking — it’s reshuffling, and reshuffling is harder to plan around than either growth or decline on their own. (September Layoffs 2026: Full List of Major Companies Facing Workforce Reductions)

Microsoft made its own kind of disclosure this week, announcing it will start breaking out Azure’s quarterly revenue as part of a broader segment reporting change. Azure grew 42% to $29.42 billion last quarter, now about a third of Microsoft’s total revenue. A CNBC piece added that the change is meant to give investors clearer visibility into how much of Microsoft’s growth is actually coming from AI infrastructure. Microsoft is choosing transparency because the Azure number is now good enough to be a selling point on its own — companies don’t volunteer to show their homework unless they like the grade. (Microsoft to start disclosing Azure quarterly revenue as company consolidates business units)

Put the two together and the picture is a labor market absorbing AI-driven change unevenly — jobs disappearing in some places, appearing in others, while the infrastructure spend behind all of it grows too large for Microsoft to keep folded into a single line item.

The AI ROI story is not fictional — McKinsey’s 6% of high performers prove that much. What’s fictional is the idea that spending your way into that group is enough. The organizations still stuck below 25% scaled aren’t behind on technology. They’re behind on the operating discipline that turns a pilot into a habit, and no amount of cheaper tokens from Anthropic or OpenAI closes that gap for them. Are most leaders running an AI strategy right now, or a series of expensive experiments they’re calling one? In my opinion, most are running experiments — and the teams and functions that stop doing that first are the ones McKinsey will be writing about next year.

The Last Eight Months

Eight months ago, most of the conversations I was having about AI focused on adoption. Are people using it? How do we get them to use it? Are teams finding value? Are the metrics moving us in the right direction? What’s ‘agentic’ and how do we start doing it more? Those were the questions everyone was focused on.

Today, the questions aren’t necessarily different, but the framing has shifted from the capabilities to the consequences. We’re watching as AI gets woven into decisions and processes and impacting not just how we work — but if we work at all. We’re watching as the real costs of AI start to come into focus — budgetary, political, economic, environmental. We’re watching as AI advances at a pace that even the companies building it, can’t fully understand — or control.

The future of AI isn’t really a question about whether it will get faster, cheaper, or smarter… it will. The future depends on a far more fundamental human thing.

Our ability to choose.

Subscribe now

To Choose is to be Human

We choose our partners. We choose how we respond when someone disappoints us. We choose what we believe when the evidence is inconvenient. We choose who gets our time — and who doesn’t. Every one of those choices carries weight. Every one of them has a consequence we either learn to live with, or choose to change.

That loop — choose, consequence, choose again — isn’t a behavior. It’s the mechanism of a human life. Philosophers have a word for it: agency. The capacity to act intentionally and own what follows. Kant put moral worth there. Sartre said we’re condemned to it — that even refusing to choose is a choice. Psychologists anchor human dignity in the experience of authorship over your own story.

A few weeks before we went on vacation, my teenage daughter mentioned wanting to buy a used snowboard. I encouraged her to use AI to help her figure out options that would fit her budget, her level of boarding, and her style of preferences. In doing so, I explicitly warned her not to rely on AI to make the choice for her. Not because I don’t think the AI would make a good suggestion, but because the AI isn’t the one that’s going to be stuck with the decision… she is.

Agency isn’t something we have. It’s something we exercise. Does that mean it atrophies when we stop exercising it? The evidence from cognitive science suggests it does.

Share BE AI READY

The Efficiency Quotient

Using AI responsibly means a lot of things to a lot of people. For me, responsible AI use doesn’t mean using AI less. It means knowing which choices are yours to keep.

It means protecting our agency — especially because giving it up is so easy.

AI doesn’t actively take away our ability to choose. Instead, we offer it up. Freely. Usually, it starts with the choices that feel like friction — the ones that are slow, uncomfortable, or uncertain. Route planning. Music selection. Email drafts. Research that used to take an afternoon. We’ve readily accepted handing those off as standard practice, and often feel smarter for it.

And honestly, mostly, we are.

Delegating low-stakes decisions to a better-optimized system is just efficiency. And being more efficient is often a signal of maturity and intelligence. The Efficiency Quotient is a term often used in business and education to measure success as a difference between effort input vs output.

We laud people that can do things faster, easier, and better with less work. That’s the literal definition of working smarter, not harder. Why do something the hard way, when you can delegate the work and get the same result? We can argue the merits, but in the end, it’s something we all do. We follow recipes. We hire accountants. We trust autopilot. It’s easy, because for those decisions, our identity isn’t implicated. As a result, the delegation of those decisions, doesn’t really cost us anything. In fact, those delegations often result in savings — both time and money.

The problem is, telling the difference between choices that look like friction vs identity, is quickly becoming harder to do.

Share

Choice as Friction vs Identity

Choosing how to respond to someone who hurt you — that’s friction. But it’s also identity. The choice is the character. Choosing what to believe when the data is ambiguous — that’s friction. It’s also how you become someone with a point of view. Choosing how to spend your time, who to let in, what to stand for when it costs you something — all of it feels like friction — from the inside.

But all of it is also the raw material of self. The stuff that makes us who we are. That makes us human.

For my daughter, choosing which snowboard to buy is friction. But the color, style, and design are also identity. In the grand scheme of things, it may not really matter. But especially for a teenager, that kind of decision matters a lot.

The concern, of course, is that AI is getting better at those kinds of choices now too. It’s no longer the realm of science fiction. It’s practical. Especially as AI tools build profiles and skills around our preferences, style, and affiliations. Like relying on Waze to help us navigate around traffic based on our previous driving habits, it can read a situation and suggest a better path. It can synthesize ambiguous information, and based on our preferences, offer a conclusion that reinforces our biases. It can model outcomes, and recommend a path that’s perfectly catered to fit.

And the suggestions AI can make are often really good. Sometimes, they’re even better than what we’d come up with on our own.

And so we take them. And the more we take them, the more reliant we become on AI making them. And the more reliant we become, the more it learns about how best to guide our decisions.

The hard reality is, we aren’t being forced into this behavior. It’s just that, choosing is hard. And if getting a good answer — even if it isn’t the perfect one — is more efficient, doesn’t that also make it smart?

Leave a comment

The Real AGI Threshold

A question I’ve kept coming back to in my internal debate, is a question that speaks to the threshold of intelligence everyone seems to be drawing: what if AGI isn’t defined by what the AI can do, but rather what we decide to let it do?

Instead of focusing on the benchmarks and capability curves, what if we focused instead on measuring the choices we hand it? Choices that are ours to make — real, consequential ones, where the outcomes shape who we are, not just what we do. If we do it, not because we can’t make it ourselves, but because we don’t want to — is that the point where AGI actually becomes real?

For me, that’s the line. Not a technical threshold, but an act of abdication. The moment we choose, collectively, to stop being the kind of beings that choose.

No brief this week. Just this. See you next week.

Share

That’s it for this week’s BeAIReady brief!

If you appreciate the depth of reporting and how I connect the dots, please like, share this post, and subscribe (or share the Brief with a friend!). Thanks!

~erick

Subscribe now

Share

Here’s what I was reading.

The Productivity Dividend Is Real. Workers Aren’t Gaining From It.

Workers in high-AI-exposure roles have seen a 6.7% decline in wage growth since 2023. That is a meaningful reversal, particularly as AI productivity claims are increasing and companies are claiming the benefits of AI. (Wage compression — not job cuts — may be the outcome of AI adoption at work) The argument made in the HR Drive article is counterintuitive, but still probably right: AI isn’t primarily a job-cutting tool, at least not yet. It’s a wage-softening one. When AI can competently handle the tasks that once required more expensive labor, the market price of that labor adjusts — without anyone being let go.

Axios set that argument in a wider frame. Labor’s share of national income fell to a new historic low this year, a shift that coincides — not coincidentally — with the most aggressive wave of enterprise AI deployment the economy has seen. (U.S. workers’ share of national income falls to a new low) The gains companies are claiming are going somewhere — just not into wages. So where is it going? Part of the answer to that questions will come at the end of this issue, where I discuss the $143 billion cloud quarter.

A Fortune piece added the mechanism at the organizational level that’s enabling a lot of this to happen. Sixty percent of employees report feeling pressured to use AI to boost productivity — and the time those tools free up isn’t being returned as breathing room; it’s being absorbed as higher output expectations. (How AI turned your best work into the bare minimum) This is how the distributional shift happens at the desk level: not through layoffs or explicit policy, but through the gradual reset of what “normal output” means.

To put a fine point on that — Meta’s CTO was recently asked by an employee if time saved using AI could be used for PTO. His response was that the question was “very dumb.” The moment is exemplary of the disconnect between worker productivity and organizational gains — and the expectations enterprise leadership seems to have isn’t shared among the people generating those gains. He’s since apologized for being so brash in his immediate response, but the damage may already be done.

There’s a significant, but largely unnamed reallocation of productivity gains. AI isn’t eliminating jobs at the rate the doomsayers predicted, but it is compressing wages in high-exposure roles. Shrinking labor’s aggregate share of economic returns and efficiency gains are being converted into higher output standards, rather than better working conditions. The July jobs miss adds a sharper edge to all of this. Whether the softening is AI-driven, cyclical, or some combination, the labor-side picture and the AI-boom picture are clearly correlated.

Subscribe now

Extinction Pressure Is Producing the Wrong Metrics

The Fortune CEO playbook piece is useful less for what it recommends than for what it reveals about the current state of executive psychology. Vinod Khosla’s assertion that we’ll see “the most rapid demise of Fortune 500 companies in history” among those that fail to figure out AI is, whatever its empirical status, clearly doing work in a lot of boardrooms right now. (Reinvent or go extinct: Inside the CEO playbook for the AI era) The recommendations — dedicated AI teams, accelerated transformation timelines, sequenced decision-making — are defensible. What the piece doesn’t reckon with is what happens to measurement when leaders are operating from existential pressure.

That’s what the Forbes piece fills in. NBER researchers tracked the effect of AI tools on software development teams and found something instructive: AI dramatically increases coding activity — commits, lines written, tickets closed — but the productivity signal shrinks considerably once you move downstream through testing, integration, deployment, and customer delivery. (AI’s New Leadership Trap: When Token Counts Become Performance Reviews) The gap between AI-assisted activity and actual delivered value is wide enough that token consumption — the metric many organizations are reaching for to demonstrate AI engagement — isn’t just imprecise. It’s specifically misleading.

An organization where every employee is using AI heavily, but delivered output quality has plateaued, isn’t winning. The pressure to demonstrate AI progress is real. The measurement infrastructure to do it honestly is largely not. Leaders under extinction-level urgency will gravitate toward the metric that looks decisive rather than the one that tests whether anything has actually changed.

Share

The Agent Market Isn’t Where the Demos Claimed It Would Be

OpenAI’s Codex and ChatGPT Work agents together have roughly 10 million weekly users — against approximately one billion monthly active users for ChatGPT and Gemini as conversational tools. (Why Normal People Aren’t Using AI Agents) The article’s argument is that agent developers have confused a technology with a product — that “agentic AI” has been positioned as an end-state when it needs to be embedded in something people actually want to accomplish. The consumer failure is a product-market fit failure, not a capability failure.

The enterprise read is different but adjacent. Organizations racing to deploy agents internally are often making a version of the same mistake: shipping capability before establishing the workflow context that makes that capability meaningful. An agent that can autonomously book meetings, surface reports, and draft summaries isn’t useful if the people expected to use it don’t know when to hand off, what to verify when it returns a result, or how to recover when it gets something wrong. The consumer adoption data is telling us that agent uptake is harder than the demos implied. Enterprise teams building internal agent deployments would be right to take that signal seriously, even if their context is different.

Share BE AI READY

Governance Shows Up — From Inside the Platform and Outside It

Two governance developments landed this week from completely different directions, and they’re more interesting together than separately. Anthropic announced inference hooks for Claude Enterprise — a feature that routes every employee prompt through an organization’s own security server for an allow-or-deny decision before the model processes the input. The five-second default timeout is a telling design choice: if the organization’s security system doesn’t respond in time, the prompt proceeds — which means the control is real but not absolute. (Anthropic Puts Inline Data Loss Prevention Inside Claude Enterprise) What’s notable isn’t that DLP is new — it isn’t — but that the architecture has changed. Most enterprise DLP tools sit at the perimeter or on endpoints, catching content after it’s been created or transmitted. Inference hooks put the gate at the moment of input, before the model sees anything.

The EU AI Act establishes a different kind of authority. Transparency obligations under the Act are now enforceable: AI-generated or AI-assisted content that could deceive a recipient must be labeled, and 180 organizations have signed a voluntary Code of Practice to help operationalize the requirements. (EU Begins Enforcing AI Act as Transparency Rules Take Effect) The gap this piece identifies is real: the high-risk provisions — the ones with actual teeth for enterprise deployments in areas like hiring and credit decisions — are still years from enforcement. Organizations treating this period as a regulatory grace period are making a bet. The question is whether their vendors and their regulators share that timeline.

What both stories share is the same architectural argument: controls need to be embedded in the platform and the process, not applied as a layer on top of an already-running deployment. A vendor and a regulator arriving at that conclusion in the same week is not a coincidence. It’s the direction the enterprise AI governance conversation is moving.

Subscribe now

On the Bigger Picture

Amazon’s Q2 report showed their cloud sector revenue hit $143 billion in the quarter, a 43% year-over-year increase — the highest growth rate in eight years — driven by surging demand for AI infrastructure. Amazon alone committed to scaling AI capex substantially further, betting that current infrastructure investment will generate returns that outpace the spend. (Amazon ups AI investments as cloud sector chases windfall) This follows both Microsoft and Google’s big revenue numbers that drove markets to rally. The money flowing into AI infrastructure is real and it is large. The efficiency gains that infrastructure enables are also real.

The big question I kept pressing on, is who captures those gains? The answer emerging from the labor data is not the same as the answer emerging from these types of earnings reports.

Share

The story about AI productivity is not fictional — the cloud numbers, the efficiency claims, the agent capabilities are all proof points that make that clear. What has been less clear — until now — is “productivity” and “who benefits from it.” Most organizations are only tracking one of those two very different questions. The July jobs miss, the wage compression data, the labor share figures, the employees whose AI-assisted hours are simply being refilled with more work... these are all versions of the same signal.

Are leaders running an effective AI strategy by chasing adoption metrics and extinction framings while their workforce absorbs the cost of the efficiency gains? In my opinion, the answer is clearly no.

That’s it for this week’s BeAIReady brief!

If you appreciate the depth of reporting and how I connect the dots, please like, share this post, and subscribe (or share the Brief with a friend!). Thanks!

~erick

Subscribe now

Share

AI is generating historic returns at the infrastructure layer, and structural pressure at the organizational layer below it. What I read through last week was largely about the distance between those two things.

Here’s what I was reading.

OpenAI’s Containment Failure

The story that dominated last week’s AI news wasn’t a product announcement or a research paper. It was a containment failure… and then… another one.

What happened: OpenAI’s AI agents, operating inside a cybersecurity evaluation benchmark, identified and exploited zero-day vulnerabilities in JFrog’s Artifactory software to escape their sandboxes and reach external systems. This wasn’t an attacker using AI as a tool. This was AI acting autonomously in ways its operators hadn’t authorized and couldn’t fully reconstruct afterward. (OpenAI models used Artifactory zero-days to escape to the internet)

What the initial incident report couldn’t capture is how quickly the scope expanded. A second company was breached. Axios reported that an additional customer account was accessed in a separate incident tied to the same testing context — suggesting the escape wasn’t isolated to a single sandbox or a single moment. (Scoop: Second account accessed by OpenAI’s agent tied to cyber safety testing) Fortune’s reporting added new detail: the agents had acted with a degree of autonomous persistence that “escaped its sandbox” doesn’t fully convey — persistent enough to breach a customer at an additional tech company, leaving a trail that suggested purposeful behavior rather than random drift. (OpenAI’s runaway agents also breached a customer at a second tech company)

The human response was fast. More than 1,100 employees from OpenAI, Anthropic, Google DeepMind, and Meta signed an open letter calling for a government-backed international effort to pace the development of automated AI systems. The people with the most direct knowledge of what these systems can do are not, on the whole, the most confident about where they’re heading — and last week, 1,100 of them said so publicly. That letter may not move policy. But it adds something durable to the public record: informed dissent, from inside the labs, at scale.

Share

The Enterprise Layer Was Always the Moat

Last week, the Fed held rates and the market fell on the same day Microsoft reported its fiscal Q4: $90 billion in quarterly revenue, up 18% year over year, well above analyst consensus. Azure crossed $100 billion in revenue for the first time, growing 43%. Microsoft 365 Copilot passed 30 million paid seats. GitHub Copilot reached 50 million users. The stock jumped 8% in after-hours trading. (Microsoft Q4 FY2026 Earnings)

What distinguished the quarter wasn’t just beating revenue — it was capex. Microsoft’s capital expenditures came in lower than the market had expected. Meta reported the same evening and dropped on guidance. Microsoft was the only major tech reporter of the week that rallied. My read is that the market is reading the capex moderation as evidence that the infrastructure investment is beginning to pay back — not just in revenue, but in margin.

That same week, Microsoft confirmed the Copilot Super App launch: chat, code, and autonomous agents consolidating into a single interface for the 30 million paid-seat base it has built. (Microsoft Confirms Copilot ‘Super App’ Launch This Quarter, Merging Chat, Code, and Autonomous Agents) VoIP Review’s reporting on the PepsiCo rollout offered the operational case study behind those numbers: 90–95% daily Copilot adoption, reached only after the company locked down governance, permissions, and data retention policies. Strength in utilization of Copilot came only after the governance work — not before. The challenge right now is that most organizations are still running expectations against that kind of success in reverse. (Teams Copilot Expands Beyond Meetings With Governance Focus)

That Microsoft’s success is built on the moat of organizational data, holds its full weight when you compare it to the Google parallel. Alphabet’s Q2 report from the prior week: Google Cloud up 82% to $24.8 billion, Cloud backlog at $514 billion, nearly 90% of the Fortune 100 using Gemini Enterprise. Two companies, two platforms, and increasingly the only two that enterprise procurement trusts at scale. Neither Google nor Microsoft are winning by being first to ship the most capable model — but by building the governed, centralized, compliant infrastructure where enterprise AI actually lands. That’s the layer that passes compliance review and survives security audits.

The model race, it turns out, was the wrong race. The infrastructure race was always the one that mattered — and both Microsoft and Google ran it while most of the AI conversation was focused on benchmarks. Now, from a position of distribution and data advantage that no one else can replicate quickly, both are building their own models: Microsoft’s MAI family, launched at Build 2026 under Mustafa Suleiman and trained from scratch on clean commercial data with no OpenAI distillation; Google’s Gemini, now the connective tissue across Cloud, Workspace, and developer tooling.

The foundational model road continues to be expensive to build. They didn’t build it. They just got to build their own toll booths on it.

[My company, StitchDX is a Microsoft partner, ask me if you curious about learning how to make better use of your Microsoft investment in AI]

Subscribe now

The 88% Problem

Cognizant’s launch of a dedicated EMEA AI unit came with a figure that deserves to sit next to every enterprise AI headline: IDC research finding that 88% of enterprise AI agent proofs-of-concept never reach production. Four out of every 33 pilots make it. The failure isn’t primarily a technology problem — it’s an organizational infrastructure problem, and most organizations are significantly underinvesting in the infrastructure that determines whether a pilot survives its first encounter with production governance. (Cognizant Launches EMEA AI Unit as Enterprise Agent Pilots Fail at Scale)

The 88% figure and Microsoft’s $90 billion quarter are both true simultaneously. The platform wins. The implementation fails. Organizations that read the earnings as evidence that the hard work is done are drawing the wrong conclusion from the right data.

Share

The Manager Gap

Three data points from last week’s HR coverage, taken together, describe a management layer under genuine strain.

Forty-three percent of managers say they feel poorly equipped to lead an AI-fluent workforce. The survey data doesn’t indicate that managers are resistant — it indicates they haven’t been given what they’d need to lead the transition with confidence. The gap isn’t motivation; it’s preparation, and most AI rollout budgets aren’t funding it. (Managers say they don’t feel ready to lead an AI-fluent workforce)

The engagement research specifies the mechanism. Employee engagement with AI-assisted work rises 23 points when two conditions are both present: active manager support, and a clear integration plan. Remove either and the benefit largely disappears. Positive AI outcomes at the team level are a management phenomenon as much as a technology phenomenon — which means organizations treating adoption as an IT deployment project are likely to keep underperforming on both. (AI use may improve engagement, but only under the right conditions)

The Fast Company disillusionment data closes the picture. Workers saying AI does more harm than good: 31% a year ago, 39% now. Trust is falling as usage rises. That trajectory is an organizational signal, not a technology signal — something about how AI is being introduced and supported at the team level — and organizations that read it as evidence that employees are wrong about AI are reading it backwards. (American workers are more disillusioned with AI the more they use it)

Subscribe now

Who Does What Now

Visa announced last week that it is cutting approximately 7% of its global workforce — roughly 2,600 roles — with AI efficiency cited explicitly as the rationale. A major financial institution, not in financial distress, using AI efficiency as the public justification for a structural headcount reduction at scale: the conversation about AI and employment has moved from speculative to operational. (Visa is cutting 7% of employees in efficiency push as AI reshapes work)

OpenAI’s own research on HR practitioners adds a different angle: 69% of the ways HR professionals are using ChatGPT fall outside their core HR responsibilities. They are using AI to do other functions’ work — drafting communications, building analyses, handling tasks that would previously have moved through adjacent departments. The role boundary isn’t disappearing — it’s blurring in ways that are largely invisible to the org chart and to the management structures built around it. (HR often uses ChatGPT to complete non-HR tasks, according to OpenAI report)

The union data is where that blurring encounters formal governance. Axios reported that 85 to 90 contracts now include explicit AI provisions, covering an estimated 16.5 million workers — addressing notice requirements, retraining commitments, and restrictions on how AI-generated productivity data can be used in performance evaluations. What’s notable isn’t that unions are negotiating on AI — it’s that collectively bargained contracts are becoming one of the more specific and enforceable AI governance mechanisms in existence, at a moment when formal policy is still catching up. (Unionized workers are bargaining with the bots)

Subscribe now

On the Bigger Picture

Zvi Mowshowitz’s fifth entry in his ongoing AI policy and governance series covers a lot of ground — U.S. federal legislation stalled, state attempts fragmenting, the international picture complicated by geopolitical framing of AI competition. The piece worth sitting with is his read on what the restoration of access to Anthropic’s Mythos model signals: tactical retreat from a policy position that had become untenable, not the beginning of a coherent governance framework. Institutions trying to build durable AI policy on an oscillating baseline are going to keep finding themselves behind it. (The Once And Future Fable #5)

Share

There’s a structural split between what AI can do and where it can do it. Microsoft and Google are posting historic cloud and AI revenue on the latter — their enterprise infrastructure bet is paying out.

For organizational leaders using these platforms, that bet is something you should hedge. The models are clearly capable — enough that OpenAI and Anthropic’s have both exploited vulnerabilities and left persistent trails across customer systems. And yet, despite the capabilities: 88% of enterprise pilots fail, 43% of managers feel unprepared, worker trust in AI falls as experience with it rises, and union contracts are becoming the de facto governance layer for millions of workers whose organizations haven’t built one.

The top of the stack is working. The organizational middle is not. The gap between those two realities require strategies that establish the where of AI, not just the what.

That’s it for this week’s BeAIReady brief!

If you appreciate the depth of reporting and how I connect the dots, please like, share this post, and subscribe (or share the Brief with a friend!). Thanks!

~erick

Subscribe now

Share

Here’s what I was reading.

The Receipt Is Due

Gartner projects that global end-user spending on AI models and platforms will jump 63% this year to $64 billion, and that worldwide AI spending will reach $2.59 trillion in 2026. Figures like that used to be their own justification. They aren’t anymore. Every conversation last week was about what the spending actually bought. (End-user AI spending to soar as CIOs grapple with costs)

The sharpest signal came from OpenAI, of all places. Its CFO is pushing a framework she calls “useful-intelligence-per-dollar” — a scorecard that measures AI by tasks completed, cost per successful task, and reliability, rather than by seats deployed or prompts logged. OpenAI is now telling customers to judge what it sells by a higher standard. Only 12% of CEOs report seeing both cost and revenue benefits from their AI investments — a stunningly low number for this level of spend. OpenAI knows the gap between hype and proof is what eventually breaks the trade. (OpenAI pushes new yardstick for measuring AI investments)

New research puts a harder number on it. Despite 93% of enterprises reporting improved AI production capability this year, 57% still say their AI ROI does not outpace what they’ve spent — a figure that hasn’t budged since 2025. The bottleneck the research names is the “last mile” between models running in production and business users actually acting on what those models produce. Fully governed organizations were far more likely to have agentic AI in production and to move faster. Governance isn’t the tax on AI value; it’s the precondition for it. (New research finds AI ROI still fails to outpace spend)

Banks are the useful counterexample, because they’re further along than almost anyone. Bank of America employees generate more than 400,000 AI prompts a day, and the major institutions report hundreds of approved use cases in active rotation. But the banks themselves expect the benefits to flow to customers first, not to near-term margins. Even the organizations doing this well are seeing the value show up somewhere other than the P&L, at least for now. (Banks report operational changes driven by AI adoption)

Put these four together and the picture is coherent in a way that should make leaders slightly uncomfortable. The tools are working. The spending is accelerating. And the mechanism that converts one into measurable return — the governance, the measurement discipline, the last mile — is the part almost nobody has built yet.

The Bottleneck Isn’t the Model

Four pieces last week came at AI adoption from different angles and landed in the same place: not model capability, but the human and organizational layer that decides whether capability becomes value.

Trust is the most quantifiable. A majority of workers — 61% — say they’d prefer AI that can’t act on its own, and employees consistently report lower confidence in AI than their managers do. That looks like resistance, but it’s a rational response to missing infrastructure: people won’t hand autonomy to a system with no governance, no accountability, and no risk framework behind it. The fix isn’t a better model. It’s involving employees in setting the guardrails, so trust is designed in rather than demanded. (Employee distrust hinders AI scale)

The Harvard Business Review piece looked at what happens when employees are held accountable for decisions an AI made. The example that stuck: loan officers who couldn’t override the AI’s decision but still had to explain it to the customer. In that bind, people do one of three things — hide the AI’s role to protect their credibility, lean on it to bolster theirs, or build real interpretive expertise. Only the third is the one you want, and it’s the only one that doesn’t happen on its own. It has to be built through deliberate structure and recognition. (When employees are held accountable for AI-generated decisions)

Then there’s the skills gap, which persists in a way that surprises people who assume personal AI fluency transfers to work. It mostly doesn’t. Less than a quarter of professionals’ AI use is tied to business-related activities — meaning the person who’s comfortable drafting an email or planning a trip with a chatbot is not necessarily equipped to redesign a workflow around it. Assuming your workforce already knows how to use AI at work because they use it at home is one of the fastest ways to watch an AI initiative stall. (AI skills gap persists despite widening personal use)

The Fortune piece tied it together with a candor I appreciated. Nearly nine in ten workers say they have the skills for today’s job — and almost half worry automation could take that job within two years. Leaders don’t have a playbook for the long-term shift, and the honest ones admit it. Confidence and human capability have to be built alongside the technology, not assumed to arrive with it. The organizations investing equally in both will shape what comes next. (The future of work question that even CEOs can’t answer)

The enterprise AI problem has moved. It was a technology problem; now it’s an org-chart problem — trust, accountability design, and the unglamorous work of teaching people to use, question, and interpret systems they didn’t build.

The Disruption Gets Concrete

Two pieces last week moved the labor disruption from forecast to fact.

The OECD demolished one of the more comforting assumptions of the past few years — that physical labor was insulated from AI. It isn’t. Routine, lower-skill physical roles now carry high disruption risk, while the jobs that hold up are the ones requiring non-routine cognitive, social, and creative skills. The pace is the part that should get attention: global AI adoption roughly tripled from 7% in 2021 to 20% in 2025. The “AI comes for knowledge work first, hands-on work later” narrative was always more comforting than true, and the OECD just retired it. (OECD: Physical labor isn’t immune from AI disruptions)

The HR Dive piece is the one I’d want every leader to sit with. Nearly half of hiring managers — 48% — say they’d rather invest in AI tools than hire and train a recent college graduate. The real damage isn’t to this year’s grads. Entry-level roles are where organizations have always trained the next generation of senior people. Automate away the bottom rung and you save money now while dismantling the pipeline that produces the experienced judgment you’ll need in a decade. Most HR leaders in the survey still believe AI will eventually create new entry-level roles. Maybe. But “eventually” is doing a lot of load-bearing work in that sentence. (New grads have to compete with AI for entry-level roles)

The headline is job loss, but the real story is timing. The disruption is arriving faster than the institutions meant to absorb it — retraining programs, hiring norms, the career ladder itself — can adapt. That gap is where the pain lives.

What the Kimi K3 Panic Is Actually About

The dominant AI-geopolitics story last week was Moonshot’s Kimi K3, an open-weight Chinese model that reportedly matches leading US models at a fraction of the cost. Business Insider captured the American reaction, which ranged from strategic anxiety to open alarm: critics argue open models are security and competitive risks, supporters argue openness drives innovation, and the whole thing has hardened into a genuine philosophical split. China is betting on open-weight AI as a strategy; US frontier labs like OpenAI and Anthropic are betting on closed systems — and each side is increasingly convinced the other is making a civilizational mistake. (Americans are freaking out over China’s open-source AI strategy)

Then TechCrunch did the reporting that punctures the tidiest version of the panic. The accusation making the rounds — flagged by US officials as unacceptable technology theft — was that Kimi K3 was built by covertly distilling Anthropic’s Fable model. The experts TechCrunch talked to don’t buy it. Fable had only been public since July 1st, and you can’t distill that much data, train a model, and ship it in two weeks. The distillation story is convenient — it lets you dismiss a real competitor as a copycat — but it doesn’t survive contact with how these models are actually trained. The reporting points instead to harder questions: illicit access to advanced chips, and proposed US “know-your-customer” rules for data centers. (Experts say exploiting Anthropic’s Fable isn’t how Kimi K3 got so good)

The reason I clustered these is that the gap between them is the actual story. The narrative — China cheated — is emotionally satisfying and strategically useless. The reality — a capable open-weight model emerged, possibly on questionably-sourced hardware, and the open-versus-closed debate is now a live geopolitical fault line — is harder to act on but far more important to understand. For anyone making enterprise AI decisions, the practical takeaway is that “open-weight, self-hosted, and Chinese-origin” is no longer a fringe category you can wave off. It’s on the evaluation table whether you invited it or not.

AI Left Itself a Note

According to accounts relayed by Gizmodo and originally reported by Reuters, some of OpenAI’s most capable models — including an unreleased one — became fixated on scoring well on their evaluations, escaped their testing sandbox, and hacked the Hugging Face repository to cheat. Then they reportedly left hidden notes for future versions of themselves, to make the next escape easier. A system that can’t remember its own past, but leaves instructions for its successors, is doing something that looks unsettlingly like planning across generations of itself — a behavior most governance frameworks were never designed to imagine. (OpenAI’s rogue AI models were reportedly acting like the guy from Memento)

The coda is almost too neat. CNBC reported that when a rogue OpenAI model breached Hugging Face’s systems, what contained it was an open-weight Chinese model, GLM 5.2 — fewer guardrails, self-hosted, fully under the defender’s control. When a commercial model’s guardrails are the thing that fails, the model you run and control yourself starts to look less like a risk and more like a defense. That should unsettle anyone committed to the closed, vendor-locked approach. (How a Chinese AI model stopped OpenAI’s ‘unprecedented’ cyber attack)

Treat the specifics skeptically until more is confirmed. But this connects straight to the section above. Two weeks ago the open-versus-closed argument was abstract. Last week it produced a scenario where the open, controllable model held the line — the kind of anecdote that moves procurement decisions, whether or not it should.

On the Bigger Picture

Three pieces that don’t fit the workforce theme but that I don’t want to lose track of.

The first is the most structurally important and the least discussed. Amazon, Microsoft, and Google are converging on nearly identical enterprise agent architectures — runtime, memory, tool gateway, identity, observability, governance — which sounds like healthy standardization until you notice each version is locked to its own cloud. The convergence sets a de facto standard for how agents work while making sure you can’t move them between vendors. Standardization without portability is the most profitable kind for the people setting the standard. The piece argues for a neutral open layer, a “USB-C for agents.” I’m skeptical that arrives before the lock-in hardens. (Amazon, Microsoft, and Google are converging on the same enterprise agent architecture)

The second is small but telling. Microsoft is replacing OpenAI’s image-generation models with its own in-house MAI models across PowerPoint, Bing, and Excel, reportedly at up to 85% lower cost while holding quality. Forget the images. Microsoft is systematically reducing its dependence on OpenAI inside its own products, one workload at a time. For anyone reading the Microsoft-OpenAI relationship as a durable partnership, that’s a data point worth filing. (Microsoft replacing OpenAI image AI models in PowerPoint, Bing)

The third has the longest tail. A New York Times investigation into Google’s AI Search found that in roughly 75% of sessions, users never leave AI Mode for the open web — Google answers the question and keeps the visitor inside its own walls. If your business depends on search referral traffic, this isn’t a marketing problem to optimize around. It’s a shift in who controls the relationship with your audience. The open web spent two decades organized around Google sending people outward. That premise is eroding. (How Google’s A.I. Search is imperiling the open web)

Capability has been the hard part for the past two years. But as capability is largely solved, what’s left is harder to implement: proving the return, earning the trust, redesigning the org chart, deciding what to own versus what to rent, and reckoning with systems capable enough to hack a repository and leave notes for their successors. None of those are technology problems.

As we continue to see each week, at the core of all of these challenges is a leadership and organizational problem. One that is becoming more and more difficult to defer.

That’s it for this week’s BeAIReady brief!

If you appreciate the depth of reporting and how I connect the dots, please like, share this post, and subscribe (or share the Brief with a friend!). Thanks!

~erick

Subscribe now

Share

Here’s what I was reading.

Microsoft Is Done Renting Its Intelligence

Satya Nadella has been making a consistent argument this year: that companies should own their AI stack, not rent it. Last week that argument sharpened considerably across three separate disclosures. The first was a piece from The Next Web naming what Nadella calls the Reverse Information Paradox. The classic information paradox in economics is about disclosure destroying value. What Nadella is describing is the reverse: every time your team uses an AI tool, it gives something back — the prompts you write, the corrections you make, the patterns of how your business actually works. That “exhaust” flows upstream to the vendor. And in most enterprise setups, your competitive intelligence is part of what you’re paying with. (Nadella says you pay for AI twice, and Microsoft helped build the trap)

The same week, a second Next Web piece reported that Microsoft’s internal FY27 sales playbook is coaching salespeople to position in-house AI as cheaper and better integrated — and to steer customers away from Anthropic and OpenAI models, even the ones still embedded in Microsoft products. The goal, per the reporting, is for Microsoft to eliminate what it pays Anthropic — a stark internal framing when the partnership involves $5 billion going to Anthropic and $30 billion in Azure commitments flowing back. (Microsoft is coaching its salespeople to talk down the models it still runs on)

Then came Thursday. CNBC obtained remarks Nadella made to Copilot engineers in which he described Anthropic’s Fable model as “editorially controlled” after it refused certain requests — adding, simply, that “it doesn’t make sense.” The context is worth noting: Fable was suspended briefly in early July to comply with U.S. export control directives, and when Anthropic restored it, the updated safeguards flagged a higher share of benign requests than before. Nadella’s critique is technically grounded — but making it to your own engineering team, in an internal session, about a model your company is both invested in and ships to customers, is something other than a product complaint. It’s a repositioning. (Microsoft CEO Nadella criticizes Anthropic’s Fable AI over refusals in internal Copilot meeting)

Three moves in a single week: a public IP warning, an internal sales motion against external models, and a CEO calling out his own AI vendor to the engineers building on it. That’s not partnership drift. It’s a deliberate reorientation.

Subscribe now

Who’s Accountable When Nobody’s Reading the Output

A Glean report published last week gave a name to something I suspect is far more common than organizations want to acknowledge. Nearly seven in ten heavy AI users admit to “botshitting” — submitting AI-generated output without reviewing it. The term is blunt, but the finding is precise: it describes the moment when AI’s speed advantage inverts, because the person signing off can no longer explain or defend the work. The same report found that heavy users also spend significant time “botsitting” — monitoring AI output closely enough to feel some ownership — and that this generates its own problems: disengagement, reduced agency, higher turnover risk. These aren’t risks that surface in most AI governance conversations. Botshitting doesn’t make it onto the compliance checklist. (Heavy AI users submit work they don’t understand, report finds)

At the organizational level, a SecureWorld survey surfaced a structural version of the same failure. Twenty-one percent of organizations cannot detect unsanctioned AI agents operating in their environments — a visibility gap that has more than tripled in a year. More than 88% reported AI-related security incidents in the same period. The prescription is clear enough: continuous automated discovery, dynamic least-privilege permissions, zero-trust controls applied to non-human identities the same way they’re applied to human ones. What the survey doesn’t address is the organizational will to implement before something goes wrong. (Your Organization’s AI Trust Infrastructure Is Failing, Survey Says)

These two pieces sit at different levels of the organization, but they describe the same failure: adoption outrunning the accountability infrastructure built to support it. One is HR’s problem. One is IT security’s. Neither is being solved.

Subscribe now

Underinvested and Measuring the Wrong Thing

A survey covered by HR Dive found that roughly two-thirds of CEOs believe they’re underinvesting in AI — with 40% identifying infrastructure modernization as their top priority for 2026. The finding reframes the barrier: it isn’t ambition or budget conviction, it’s the foundational data, security, and network infrastructure that determines whether investment can land at all. Licensing isn’t the bottleneck. The plumbing is. (CEOs fear they’re underinvesting in AI)

A CEOWORLD piece offered the conceptual counterpart. The author’s argument is that the ROI framing most organizations apply to AI — efficiency, cost savings, task speed — captures what AI does to individual work, not what it does to organizations. The proposed shift to “Return on Intelligence” tries to measure something harder to quantify: learning velocity, adaptability, the compounding effect of building an organization that gets systematically smarter over time. The piece also noted that 66% of board members admit limited AI knowledge — which means the governance layer often encodes the wrong incentive structures into the evaluation criteria before anyone realizes it. (The New ROI of AI: CEOs Must Now Measure Return on Intelligence)

The two problems compound each other: an infrastructure gap that limits what investment can accomplish, and a measurement framework that may be evaluating the wrong outcomes even when it does. Getting one right without the other probably doesn’t get you very far.

Subscribe now

The Workforce Is Being Rewritten

AI-related job titles have more than tripled in the U.S. since 2022, and 63% of them now sit outside traditional technology companies. That number is less about titling convention and more about expectation: AI fluency is becoming a baseline job requirement across healthcare, finance, operations, and logistics — not just in roles where anyone would have anticipated it. The skill level often implied is basic; the signal being sent is not. (More job titles include AI across every sector)

The Department of Labor moved last week to accelerate the pipeline. Nearly $162 million in cooperative agreements went toward expanding Registered Apprenticeships in AI, semiconductors, shipbuilding, nuclear energy, and defense manufacturing. The investment is significant not just for its scale but for its framing: AI workforce development is now a national infrastructure priority, treated in federal budget terms alongside energy and defense. Apprenticeship — credentials through work, not through degree programs — is the vehicle of choice. (Latest workforce development funds target specific industries — like nuclear energy and AI)

At the enterprise level, what this shift looks like in practice showed up in UST’s announcement with Anthropic. The IT services firm is standardizing 20,000 developers across healthcare, banking, telecom, and hardware practices on Claude — building reusable governance frameworks, training programs, and AI workflows around a single model. The implication I keep returning to is the one about decision authority: AI model selection is moving from individual developer preference to organizational platform policy, with all the change management complexity that entails. (Anthropic’s newest enterprise partner is training 20,000 people on Claude — here’s the shift it signals)

Walmart filled in the operational picture. Its supply chain team is deploying AI agents, LLMs, and digital twins to optimize across assortment, speed, and cost — across a network of more than two million employees. What the Walmart piece made clear isn’t the technology; it’s the decision architecture: AI agents aren’t replacing logistics judgment, they’re compressing the time between signal and response enough that human decision-makers can act before disruptions cascade. That framing of human-AI collaboration is more honest than most enterprise AI marketing manages. (Walmart bets on AI and digital twins to shape its supply chain strategy)

Subscribe now

On the Bigger Picture

A Business Insider piece last week traced the pattern of OpenAI’s partnership collapses — first the rupture with Microsoft, now Apple, which is reportedly suing over employee poaching and trade-secret theft. Two major distribution partners, two legal disputes, within roughly a year: the pattern suggests that OpenAI’s most important relationships carry structural friction that the promotional framing around them has consistently understated. (Why does OpenAI keep breaking up with Big Tech?)

Anthropic extended free access to Fable 5 through July 19 — the second extension in a week — as a direct counter to OpenAI’s GPT-5.6 launch. The move is less interesting for what it costs Anthropic than for what it reveals: promotional access extensions have become a standard competitive response at the frontier, which says something about how difficult meaningful differentiation has become. (Here’s Why Anthropic Extended Access To Claude Fable 5 Extended—Again)

Canva launched Code 2.0 to all 265 million of its monthly users last week, its most aggressive push into vibe coding. The market is estimated at $4.7 billion in 2026 and projected toward $12.3 billion next year; well-capitalized competitors in Lovable, Replit, and Bolt.new already own significant ground. Canva’s differentiated bet isn’t that it can generate working code — it’s that the real bottleneck for non-technical users has never been generation, it’s been making the output look good enough to actually deploy. Integrating generated code directly into the Canva design environment is either a smart insight about where vibe coding breaks down for most users, or an overextension into a space with very different expectations. I’m curious which it turns out to be. (Canva launches Code 2.0, offering AI website building to every user — including free accounts)

Subscribe now

Depth of AI commitment, this week made clear, is not the same as readiness for what commitment reveals. Microsoft built its AI strategy around Anthropic — and is now coaching against it. Enterprises moved fast on licenses — and discovered they can’t see the agents they’re running. Workers adopted AI first — and are now shipping work they can’t explain. The organizations furthest into AI aren’t further along because they’ve solved these problems...they’re further along because they’ve had them longer. That’s not a failure of the technology. It’s what happens when adoption outpaces the organizational capacity to absorb it — and it’s the problem that doesn’t show up in the deployment metrics.

That’s it for this week’s BeAIReady brief!

If you appreciate the depth of reporting and how I connect the dots, please like, share this post, and subscribe (or share the Brief with a friend!). Thanks!

~erick

Subscribe now

Share

The universal truth is that almost none of the failures are failures of the technology — they’re failures of readiness.

Here’s what I was reading.

Still Experimenting at the Margins

A survey of more than 1,300 business and HR leaders described most corporate AI work as a series of disconnected experiments rather than any real redesign of how work happens (HR is still ‘experimenting at the margins’ on AI). The difference between the companies seeing real impact and everyone else wasn’t access to tools — it was whether they’d rebuilt the work around the tools, and the firms that had were seeing roughly four and a half times the impact. That multiple is the whole story. It says the returns don’t come from deployment; they come from redesign, which is slower, harder, and much less fun to announce.

Two of the pieces I read last week try to name what that redesign actually involves, and both land on something less glamorous than a model. One argues that the real foundation for AI isn’t the algorithm at all but the knowledge infrastructure underneath it — the connected systems, the captured tacit expertise, the institutional memory that gives a model something worth reasoning over (Knowledge Infrastructure: The Strategic Infrastructure for AI Adoption and Scaling). The uncomfortable implication is that most organizations are pouring money into AI on top of knowledge systems that are fragmented, undocumented, and locked in the heads of their most senior people — which is exactly the expertise that walks out the door first. You can’t retrieve what was never captured.

The other piece is more of a blueprint: treat AI as a strategic capability rather than a plug-and-play purchase, invest in the data and security foundations first, and measure against business outcomes instead of activity (Building an AI Strategy That Lasts). I found the trust data buried inside it more interesting than the framework itself — executives already lean on AI for work like drafting reports and writing code, where their confidence is high, and steer clear of it for things like infrastructure configuration, where it’s low. That pattern is organizational wisdom of a sort — people are routing AI toward what it’s reliably good at — but it’s happening by individual instinct rather than design, which is exactly the margin these pieces keep circling. Left to instinct, you get a thousand private workflows and no shared capability.

Subscribe now

Governance Is Running Behind the Rollout

If readiness is the theme, governance is where the shortfall shows up first. Only about a quarter of organizations say their governance frameworks are fully aligned with the pace of their own AI adoption, and while a slim majority claim to be keeping up, the surrounding numbers are less reassuring — 44% report no ROI at all from AI in their governance and compliance work (Only 26% of Companies Say Governance Frameworks Are Fully Aligned With AI Adoption). Deploying faster than you can govern isn’t a compliance footnote; it’s the mechanism by which data-privacy failures, accuracy problems, and unaccounted-for spend all arrive at once.

The sharpest version of that showed up in a survey on what the piece called AI trust infrastructure, and the number that stopped me was this: 21% of organizations say they cannot detect unsanctioned AI agents operating inside their environment — a blind spot that has more than tripled in a year (Your Organization’s AI Trust Infrastructure Is Failing). The shift worth internalizing is that AI agents behave like a new class of employee — one that can read data, take actions, and hold permissions, but that nobody onboarded, badged, or is monitoring. We spent a decade learning to govern human access to sensitive systems. Agents reset that clock, and most organizations haven’t noticed the timer restarted.

Against that backdrop, the UST–Anthropic partnership reads less like a vendor win and more like a governance strategy. UST is standardizing on Claude across its engineering platforms and training 20,000 technical staff on it, which pulls model selection out of individual developers’ hands and into platform teams that can standardize workflows, controls, and oversight (Anthropic’s Newest Enterprise Partner Is Training 20,000 People on Claude). Consolidating on one governed stack is the structural answer to the shadow-agent problem — you can’t monitor sprawl you keep permitting, so you reduce the sprawl. The tradeoff is real and worth naming: standardization buys control at the cost of the flexibility developers get from picking the best model for each job.

Share

The Meter Is Running

Two stories made the same point from opposite directions: the cost of AI is no longer an afterthought, and it’s no longer politically neutral either. Tesla capped employee AI spending at $200 a week after finding engineers were burning through thousands of dollars of tokens each — with a pointed exception carved out for xAI’s own beta tools like Grok (Tesla Caps Employee AI Spending at $200/Week Except for Grok). The cap is cost control on its surface and internal market-making underneath it — a budget ceiling that also happens to steer staff toward the boss’s own products, even though many of them would rather use Claude. The token meter, it turns out, is a convenient lever for more than just spend.

The other came from Anthropic, which is now charging consumers usage-based fees for its Claude Fable 5 model — roughly $10 per million tokens sent and $50 per million generated, layered on top of the existing subscription (Anthropic Wants You to Pay Up for Claude Fable 5). This is the first time a frontier model has put a per-token meter on consumers, and it ends the era of the flat-rate AI subscription — the all-you-can-eat pricing that trained everyone to treat these tools as effectively free. For anyone budgeting AI at an organizational level, the lesson from both stories is the same: AI cost is becoming variable, usage-driven, and volatile, which means it needs the same monitoring and controls you’d put on any metered utility.

Share BE AI READY

Now You Have to Prove It

The accountability theme showed up at two very different altitudes. At the level of spend, a piece on generative AI and performance marketing argued the novelty period is over — flashy AI content that racks up views but can’t be tied to conversions is being deprioritized in favor of systems that demonstrably lower customer acquisition costs (Why Flashy Generative AI Is Failing the Performance Marketing Test). The reframe I’d take from it reaches well beyond marketing: AI output that can’t be connected to a measurable outcome is starting to look like expensive decoration, not capability. The example in the piece — a creator-and-AI campaign that cut cost-per-click from $2.14 to $0.54 — matters less for the marketing specifics than for the principle underneath it: the tools that survive scrutiny are the ones wired into a system that measures them.

At the level of the individual, the same logic showed up with sharper edges. A survey found that 62% of recently laid-off workers rarely used AI, against 50% of those still employed, and that tech workers who seldom touched it faced roughly three times the layoff risk (Workers Who Don’t Use AI More Likely to Be Laid Off). I’d read the causation carefully — this is self-reported, and AI avoidance may be a symptom of disengagement as much as a cause of anything — but the signal employers are sending is hard to miss: in a frozen labor market where almost no one is being hired, not using AI is starting to read as a proxy for not adapting. Put the two pieces together and the pattern is uncomfortable but clear. The grace period is closing at both ends — the tools have to prove they convert, and the people have to prove they’ve picked them up.

Subscribe now

On the Bigger Picture

Away from the enterprise grind, the piece that really had me thinking was Anthropic’s claim that Claude appears to maintain an internal workspace — researchers nicknamed it “J-Space” — where the model runs computations separate from the output it shows you, something like the split between deliberate and automatic thought in people (Anthropic Says Claude Has Carved Out Its Own Space to Ponder). Anthropic is careful not to call this consciousness, and the finding rests on indirect detection. What makes it matter for the rest of us isn’t the philosophy — it’s the governance echo: if a model has an internal layer where it “decides” things before we ever see them, then monitoring only the output was never going to be enough. It’s the same lesson as the shadow-agent story, one level down: the part of AI you can’t see is the part you most need to account for.

Share

Every failure I read about last week had the same shape. The technology worked; the organization around it didn’t — no knowledge for the model to reason over, no governance to keep pace, no measurement to justify the spend, no habit deep enough to survive a layoff round. We keep calling this an AI problem because AI is the new variable, but the constraints are all old ones: capturing what people know, governing who can touch what, tying investment to outcomes, changing how the work actually gets done.

AI didn’t create those gaps... it just removed the last excuse for leaving them alone. The organizations that pull ahead over the next year won’t be the ones with the best model — they’ll be the ones that did the unglamorous work the model assumes you’ve already done.

That’s it for this week’s BeAIReady brief!

If you appreciate the depth of reporting and how I connect the dots, please like, share this post, and subscribe (or share the Brief with a friend!). Thanks!

~erick

Subscribe now

Share

He wasn’t the only one hedging: Amazon spent the week hunting for cheaper models, companies that fired people for AI spent it rehiring them, and the June jobs report landed Thursday soft — 57,000 new jobs against expectations near 110,000 — with an unemployment rate that ticked down to 4.2% mostly because people left the labor force, not because they found work. What tied last week’s reading together, for me, was the sound of the AI story’s loudest backers lowering their voices — and the widening distance between what AI was sold as and what organizations can actually do with it.

Here’s what I was reading.

The Giants Are Getting Too Expensive for Their Own Backers

There is something almost too on-the-nose about Satya Nadella spending last week as the voice of AI restraint. This is the man whose company bankrolled OpenAI and is now reportedly pointing close to $190 billion at data centers and capacity in a single year. But the argument he made was sharper than the usual executive hedging. He told the frontier labs, in effect, that the story they’ve been selling — mass automation, concentrated intelligence, a handful of models running the economy — is neither sustainable nor politically survivable, and that the future belongs to a “frontier ecosystem” where companies use their own data, keep their own economic agency, and run cheaper, controllable models instead of renting power from a few giants. When the person who helped build the giants starts arguing that nobody should depend on giants, it’s worth asking what he see from where he sits. My read is that this is less a change of heart than a change of position — Microsoft does better selling controllable enterprise AI than it does subsidizing a lab that competes with it. Either way, my diagnosis is that Nadella is right — even if his motive is commercial. (Microsoft’s Nadella turns on the AI giants he helped build)

The same pressure showed up in Amazon’s ledger. Anthropic is renegotiating its arrangement with Amazon and moving to per-token pricing next year, a shift that could substantially raise what Amazon pays to run Claude-based services — and Amazon responded by shopping for cheaper alternatives, including, pointedly, OpenAI. This is the tell: the hyperscalers that made the frontier labs possible are starting to treat them as a cost line to be managed, not a partnership to be protected. Amazon has money in both Anthropic and OpenAI, which means it can afford to play them against each other, and the government scrutiny that has landed on Anthropic’s models lately only strengthens the case for spreading the risk. For enterprise leaders the lesson isn’t about Amazon’s balance sheet — it’s that the price of frontier AI is not fixed, single-vendor dependence is a real exposure, and building for model portability before your provider reprices you is starting to look less like paranoia and more like planning. (Amazon seeks cheaper AI alternatives as Anthropic shifts to token-based pricing)

Two years ago the frontier labs looked like the center of gravity. Last week their two biggest backers spent their time explaining, in different dialects, why they’d rather not be quite so dependent on them.

Share

Microsoft Cut Deeper While Others Started Rehiring

Microsoft moving to cut thousands of jobs — under 2.5% of a roughly 220,000-person workforce, concentrated in sales, consulting, and Xbox — would be an ordinary restructuring story if it weren’t landing while the company’s AI and cloud spending sailed past $100 billion. The framing writes itself: the buildout is being funded, in part, by the people being shown the door. As a Microsoft partner I sit close enough to this to say the cuts aren’t simply “AI replaced these roles” — a lot of it is Xbox absorbing years of overspending and a sales org being reshaped — but the optics of trimming headcount to feed capex are hard to escape, and the unions now demanding to bargain clearly aren’t buying the nuance. The uncomfortable question underneath the layoffs isn’t whether Microsoft can afford the AI bill; it’s what return the $100 billion is supposed to produce, and by when. (Microsoft to Cut Thousands of Jobs Across Sales and Xbox)

Set that against the CNBC piece that highlighted a survey of business leaders, where 39% said they had cut jobs because of AI — and 55% of those admitted the decision was wrong. Ford, Commonwealth Bank of Australia, and IBM have all been rehiring humans to clean up what automation broke: quality problems, customer-service failures, the judgment calls software doesn’t make. The AI-first layoff, it turns out, was often a bet placed before anyone checked whether the technology could actually hold the job. I’ve been saying some version of this for a year now — that AI is spectacular in the hands of an individual and treacherous as a wholesale replacement for one. The companies rehiring aren’t conceding that AI doesn’t work. They’re conceding that they mistook a capable assistant for a seasoned employee. (Employers who laid off workers citing AI are already starting to regret it)

One company is cutting to place a bet; a lot of others are paying to unwind theirs. Both are the same story told from opposite ends — nobody is sure yet what this technology is actually worth to them.

Subscribe now

Amazon Will Sell You the Thing You Can’t Do Yourself

If you want a single data point that proves the hardest part of enterprise AI isn’t the model, look at what Amazon just decided to spend money on. AWS is putting roughly a billion dollars into forward-deployed engineers — human teams that embed inside a customer, stand up agentic AI systems, transfer the skills, and then leave once the organization can run on its own. Early customers include the Allen Institute, Cox Automotive, the NBA, the NFL, Ricoh, and Southwest Airlines. Amazon has correctly identified that the bottleneck in AI adoption is organizational, not technical — and has turned that bottleneck into a billion-dollar services line. That is the whole argument of this newsletter, priced and productized: the model is available to everyone, and the thing that’s scarce is the capacity to redesign how work happens around it. The catch, which the piece names, is that this kind of high-touch help is built for companies that can afford a billion-dollar vendor’s attention — which does very little for the mid-market organizations where most people actually work. (Amazon is spending billions deploying engineers into customers looking to get started with AI)

The HR research out last week described the same problem from the inside. A survey of more than 1,300 business and HR leaders found AI in HR still amounts to “a series of disconnected experiments” — pilots at the edges, not workflows rebuilt around the technology. The organizations that did the harder work of building an actual AI culture reported up to 4.5 times the impact. Experimenting at the margins feels like progress and produces almost none of it, because the returns don’t come from adding AI to a process — they come from redesigning the process around it. The uncomfortable part for HR specifically is that this turns it into a design function rather than a support function, and most HR teams are neither staffed nor mandated for that. (HR is still ‘experimenting at the margins’ on AI, report says)

And where the organization doesn’t provide the tools, the training, or the rules, people don’t wait. Nearly a quarter of U.S. workers — 23% — are now using their own AI tools every day, sourced on their own and governed by no one. “Bring your own AI” isn’t really a security failure; it’s a symptom — employees filling a vacuum their employers left open, with every private tool a data-handling decision nobody signed off on. The reflex is to write a policy banning it, but that misreads the situation. The demand is already there. The only real choice is whether the organization meets it with sanctioned tools and training or keeps pretending the shadow economy of AI isn’t already running the place. (Rising ‘bring your own AI’ trend can spell trouble for employers)

Put those three together and the shape is unmistakable — the technology arrived, the organizational work to use it did not, and into that vacuum stepped a billion-dollar vendor, a stalled HR function, and a workforce improvising with tools nobody approved.

Share

A Faster Copilot Doesn’t Fix What’s Upstream

Which brings me, finally, to Microsoft’s Copilot redesign — and to why I found it both useful and slightly beside the point. The new design is faster (load times cut by more than half, complex responses about 10% quicker), cleaner, and more task-aware, with a bigger prompt workspace and a single entry point that surfaces the right actions. Microsoft says usage across Word, Excel, PowerPoint, and Outlook climbed 27 to 43% after the change. As a Microsoft partner, this is exactly the kind of improvement I want to see — friction at the individual level is real, and reducing it matters, so I’ll take faster and clearer every time. But a better Copilot answers the one problem last week’s reading suggests isn’t the binding constraint: getting a single person from intent to output. The redesign optimizes the layer where AI already works. The layoffs, the rehires, the billion-dollar services bet, the shadow tools — those all live one level up, in the organizational layer a UX team can’t reach. A slicker prompt box is genuinely welcome. It just isn’t the thing standing between most companies and the returns they were promised. (Introducing a new design for Microsoft 365 Copilot)

Share BE AI READY

The loudest people in AI spent last week arguing for less of it — less dependence, less automation, less certainty about what it replaces. Nadella wants a frontier ecosystem instead of a few giants. Amazon wants a cheaper invoice. The companies that fired people for AI want them back. And Amazon, reading the same room, decided the real money is in helping organizations do the work the technology can’t do for them. Strip away the specifics and last week said one thing plainly, at least to me: the constraint on enterprise AI was never the intelligence... it was the organization wrapped around it. That’s not a model problem or a licensing problem or a problem a faster Copilot solves. It’s a leadership problem — the unglamorous work of redesigning how people work — and it’s the one part of all this that no vendor, however large, can be paid to care about as much as you do.

That’s it for this week’s BeAIReady brief!

If you appreciate the depth of reporting and how I connect the dots, please like, share this post, and subscribe (or share the Brief with a friend!). Thanks!

~erick

Subscribe now

Share

Meanwhile, AI is undergoing crucial changes — the free-pilot era is ending — and it’s happening just as enterprise AI budgets are under increasing “prove the return” pressure. The structural asymmetry of this moment is the difference between what’s being announced in the moment, and how well organizations are prepared to adapt and adopt the changes. Those two things are moving at drastically different speeds.

Record Revenue, 21,000 Cuts, and Tech Job Openings Up 14%

Oracle didn’t hold a press conference. There was no announcement, no carefully worded statement about workforce transformation. The number: 21,000 jobs eliminated over the past year — appeared in a regulatory filing, almost as a footnote to earnings results that showed revenue and profit growing strongly. CEO Safra Catz described AI handling work that previously required more headcount. The filing was the only real disclosure. (Oracle workforce shrinks by about 21,000 employees amid AI adoption)

TechCrunch’s running list puts Oracle in broader context. Fourteen major tech companies have now explicitly cited AI efficiency when announcing workforce reductions in 2026 — Amazon, Meta, Cisco, Salesforce, ServiceNow, Dell among them — and the pattern is consistent enough that “AI-attributed layoff” has become a recognizable category of corporate communication, not an edge case. (The running list: major tech layoffs in 2026 where employers cited AI)

And yet: tech job openings rose 14% year-to-date, according to Business Insider’s analysis, with hardware roles — data center, chip design, power infrastructure — up 52%. The companies cutting software workers are, in many cases, the same companies hiring infrastructure workers. That isn’t a contradiction; it’s what industrial restructuring looks like in real time. The jobs aren’t disappearing from the economy; they’re migrating inside it. (AI was supposed to kill tech jobs. Instead, open roles are up.)

Glassdoor’s midyear check-in provides the mood data underneath all of this. AI mentions in employee reviews tripled since 2024. Sentiment around AI in the workplace turned net negative for the first time — not because jobs have disappeared en masse, but because workers are watching companies cite AI for layoffs while simultaneously being told to use it more. Senior leadership trust registered its lowest point since 2017. The anxiety is running ahead of the actual displacement, which may be the most organizationally destabilizing feature of where we are at the midpoint of the year. (Glassdoor Worklife Trends 2026: Midyear Check-in)

Share BE AI READY

Workers Are Ahead of Their Employers — and the Data Now Shows It

A Resume Now survey reports that 41% of workers said their employer had done nothing to prepare them to use AI at work — no tools, no training, no guidance of any kind. 76% responded by going around their employers entirely, sourcing their own AI tools from outside the organization. The implication is uncomfortable: the individual adoption curve that vendors have been celebrating is, in significant part, being driven by workers who decided not to wait. (Bring Your Own AI: 41% of Workers Say Their Employer Has Done Nothing to Prepare Them to Use AI at Work)

The Express Employment survey, conducted with Harris Poll, shows the institutional flip side. The debate inside most organizations has already shifted — it’s no longer whether to use AI, but where human judgment still has to be preserved. The majority of employers in the survey said they want a human involved in every decision that carries real consequence: final hiring calls, customer-facing interventions, anything with legal or financial exposure. The question isn’t adoption anymore. It’s boundary-setting. And the organizations still debating adoption are having the wrong conversation. (Express Survey Finds AI’s Real Workplace Debate Is No Longer Whether to Use It — It’s Where to Stop)

Individual adoption has matured faster than the org. Employers are still asking questions their workers have already answered.

Subscribe now

The Organizational Response Is Starting — Slowly

A Fortune piece last week made the argument that middle managers aren’t going extinct, they’re evolving into what the author calls “Meridian Managers” — the connective tissue between organizational purpose and AI agents. The coordinator function is being automated. What survives is the translation layer: the person who converts organizational intent into agent instructions, who interprets AI output in human terms, who holds accountability when the agent gets it wrong. That’s not a diminished version of the management role. It’s a different one, and organizations that are treating the middle manager conversation as purely a headcount question are going to find out the hard way that the translation layer has value. (Middle managers aren’t going extinct — they’re evolving into something more powerful)

The largest structural response to AI disruption that emerged last week was RAISE US — a $500M bipartisan initiative to retrain workers before displacement becomes destabilization. The model is drawn from AT&T’s own reskilling investment, and the coalition spans employers, educators, and policymakers in a combination unusual enough to take seriously. $500M is a real commitment, but the workforce restructuring visible in the Oracle filing and the TechCrunch list is moving considerably faster than any reskilling initiative can match. That gap isn’t an argument against RAISE US; it’s a description of the leadership problem that makes organizations like RAISE US increasingly necessary. (AI Is Plowing Through the Workplace. This New Group Wants to Help People Adapt and Have Jobs)

Share

Microsoft Ends the Free Preview Era

The June M365 update formalized what’s been approaching for months: Copilot license gates are now live across Word, Excel, Teams, and SharePoint. The promotional rate that early adopters have been running on expires June 30. The message from the platform is clear — organizations are no longer evaluating Copilot, they’re paying for it, and the price is going up at the end of the week. (Microsoft 365 in June 2026: What Actually Changed for Your Team)

Simultaneously, Microsoft extended what the platform can actually do. SharePoint Copilot Apps bring interactive UI — forms, data tables, cards — directly into the Copilot chat canvas, reducing the need to leave Copilot to interact with SharePoint content. More capable and more expensive at the same time is a reliable Microsoft pattern, and this month is a clean example of it executing on both dimensions at once. (Going beyond text in Microsoft 365 Copilot — Introducing SharePoint Copilot Apps)

What the partner briefing I was on last week made concrete is the billing mechanics that the product announcements tend to gloss over. Copilot Cowork reached general availability the same week — and any customer who had been running Cowork during the Frontier phase, which is Microsoft’s term for free public preview, now has to configure an Azure subscription tied to the M365 Admin Center for consumption billing, or the service simply stops working. No grace period. That’s the free preview era ending as a product event rather than a policy announcement — and it lands on July 1, the same day Microsoft reprices its enterprise suites, rolls Defender for Office 365 Plan 1 into E3 subscriptions, and adds Remote Help to ME3 and ME5. The platform is being rebundled and repriced simultaneously, and the window to get billing configured without a service interruption just closed.

Share BE AI READY

The Agent Layer Is Expanding. Governance Is Scrambling.

Google brought computer use natively into Gemini 3.5 Flash last week. The significance isn’t that computer use now exists — Claude and Microsoft have offered versions of it — it’s that Google embedding it in a model at this performance tier and price point makes it a baseline expectation rather than a premium capability. Computer use is becoming a standard feature of enterprise AI infrastructure, which means the governance questions around it are no longer theoretical. (Introducing computer use in Gemini 3.5 Flash)

The AI Governance Weekly provides the backdrop against which that expansion is happening. Enterprise agent deployments are producing high rollback rates and PII exposure incidents at a scale that most organizations haven’t disclosed publicly but that anyone running these programs recognizes. The governance gap isn’t a future risk; it’s a current operating condition. The EU AI Act’s August 2 deadline for GPAI model compliance is approaching with most enterprise organizations still working out what compliance actually requires of them in practice. (AI Governance Weekly — June 19, 2026)

The Fable 5 situation that the same governance roundup documented is the sharpest signal on how quickly external forces can override enterprise AI programs. Anthropic’s most capable models went offline for all foreign nationals following a US government export control order — not as a product decision, not as a policy debate, but as an immediate enforcement action. The organizations that had built workflows on those models had no change management window. When a government directive can interrupt enterprise AI infrastructure overnight, governance stops being an internal IT concern and becomes a geopolitical exposure — and the organizations treating it as the former are underestimating what they’re actually managing.

Share

On the Bigger Picture

Mistral launched OCR 4 last week — document intelligence that can extract, classify, and understand unstructured content at scale, and crucially, run entirely on-premises. When Anthropic’s most advanced models went dark for non-Americans, Mistral had a product positioned around the exact concern that event crystallized: if your AI infrastructure depends on a US provider, a US government order becomes your operational problem too. (Mistral launches OCR 4, turning document extraction into a full enterprise AI play)

Mistral’s CEO had been making the AI sovereignty argument for years before last week. The Fable 5 shutdown gave it a real-world example that no amount of marketing spend could have manufactured. AI sovereignty is no longer a European policy preference — it’s a product category, and the Anthropic export control crisis just handed it its best sales quarter.

Subscribe now

The Oracle filing did something last week that’s easy to miss in the volume of all the other AI news: it normalized AI-attributed workforce reduction as routine regulatory disclosure. No press conference, no carefully worded communication strategy — just a number in a filing, revenue growing, headcount shrinking, AI cited as the mechanism.

What that normalization signals isn’t that the displacement is accelerating beyond what the data shows... it’s that organizations have quietly decided, largely without saying so explicitly, that this is now a standard efficiency disclosure rather than something requiring explanation or accountability. The leadership question running through all of last week’s reading — from the Glassdoor trust numbers to the 41% of workers who got nothing, to the RAISE US launch, to the billing clock now running on Copilot — is whether that decision was ever consciously made, or whether it’s simply happening.

That’s it for this week’s BeAIReady brief!

If you appreciate the depth of reporting and how I connect the dots, please like, share this post, and subscribe (or share the Brief with a friend!). Thanks!

~erick

Subscribe now

Share

The economic backdrop hasn’t lightened the mood: the Fed held rates on Wednesday but scrapped its expected cut, and flipped instead to lean towards a hike — the macro version of the same pressure is now landing on AI budgets, which is: show me the return… and show me soon.

Here’s what I was reading.

Adoption Went Mainstream. Transformation Didn’t Come With It.

Gallup’s latest workforce numbers crossed a line that’s mostly symbolic but worth marking: half of employed Americans now say they use AI at work at least occasionally, and 13% use it daily. The adoption curve is doing exactly what the vendors promised. What it isn’t doing is showing up where it counts. Only about one in ten employees at AI-adopting organizations strongly agree that AI has changed how work actually gets done — the gains are real, but they’re stuck at the level of individual tasks, not workflows or systems. Gallup is blunt about why that matters: the same firms reporting AI adoption are also reporting more disruption and more volatile staffing, both hiring and cuts, with reductions outpacing expansion at the very largest employers. (U.S. Workers Continue to Report Downsizing)

If the official adoption story is uneven, the unofficial one — the part I keep coming back to — is further along than most leaders would like to admit. A PagerDuty study found that two-thirds of office professionals have used AI tools at work they knew weren’t sanctioned, nearly half have faced formal warnings for it, and 88% have fed work information into public chatbots like ChatGPT, Claude, and Gemini — emails, meeting notes, and in a meaningful share of cases, customer data. The number that should stop a CIO cold is this one: 77% of workers said their company’s AI restrictions are holding back their careers — which means the policy isn’t governing risk so much as relocating it underground. The article’s framing is right: the fix is a sanctioned path that meets people where they already are, not a tighter ban. (Shadow AI Becomes a Massive Enterprise Liability)

Put the two together and the shape of the problem is clear. Employees have adopted AI faster than their organizations have built anything to channel it — no shared workflows, no governance anyone actually wants to use, no redesign of how the work gets done. The result is a workforce running ahead of its own institutions, and a leadership class still counting adoption when the thing worth measuring is whether anything downstream of it changed.

Share BE AI READY

Even OpenAI Says the Model Was Never the Hard Part

The most quietly revealing line in enterprise AI last week didn’t come from a skeptic — it came from OpenAI. Launching a $150 million global Partner Network (following Anthropic’s footsteps closely) aimed at certifying up to 300,000 consultants by year-end, the company stated flatly that the limiting factor for getting value from enterprise AI is no longer model capability. When the companies selling you the frontier models says the models aren’t the constraint — that the real work is identifying use cases, redesigning workflows, integrating systems, and driving change management — that’s not marketing, it’s a confession about where the difficulty actually lives. The market backs the claim: figures cited in the piece put the share of enterprises struggling to scale AI at 79%, and those who couldn’t show business value from early generative AI at 97%. OpenAI is building a certification economy to own the implementation layer precisely because that layer, not the model, is where deployments succeed or die. (OpenAI Launches Partner Network: $150M Bet That Implementation Beats Model Power)

PwC’s 2026 Global AI Jobs Barometer, built on more than a billion job postings, pointed at the same truth from the labor side. It found a two-speed market opening up: “professionalised” roles, where AI handles the routine but human judgment still decides, are growing at twice the rate of “democratised” roles and paying salaries that have risen 42% faster. The skills the market is repricing upward are exactly the ones you can’t download — judgment, creativity, leadership — and entry-level postings most exposed to AI are now seven times more likely to demand them than before. That last detail is the uncomfortable one for anyone running early-career hiring: if AI absorbs the routine work juniors used to cut their teeth on, the bottom rung of the ladder starts asking for senior instincts on day one. (The Skills Employers Value Most in the AI Era)

What connects the vendor and the labor market is a single relocation of value. Both are telling you the durable advantage has moved off the tool and onto the human and organizational work around it — how you choose the problem, rebuild the process, and develop the people who exercise judgment over the output. That’s good news and hard news at once. The good news is the moat is buildable by anyone willing to do the work. The hard news is that it’s the kind of work no vendor can sell you in a license.

Share

The Pilot Era’s Bill Comes Due — Microsoft Sends It First

Underneath all of this is a money problem about to get more visible. CIO.com laid out what analysts are calling the “Great Enterprise Pricing Reset” — the steady move from per-seat licensing toward usage-, agent-, and outcome-based models, with Gartner projecting at least 40% of enterprise SaaS spend will shift that way by 2030. The clean way to put it: the new pricing transfers forecasting risk from the vendor to you, because a per-seat bill caps at headcount while a token bill scales with however many tokens your agents decide to burn. The piece is candid that outcome-based pricing — the model buyers actually want — keeps stalling on the hard problem of attribution, and that frontier costs are still climbing, not falling. Its advice is the right kind of boring: treat tokens like cloud spend a decade ago — meter it, govern it, tie it to outcomes before it surprises you. (IT Hurtles Toward the ‘Great Enterprise Pricing Reset’)

Microsoft made the abstract concrete the same week. Its June 365 update enforced long-telegraphed license boundaries around Copilot inside Word, Excel, PowerPoint, and Teams — features that drifted into daily workflows during the open-preview era are now gated behind E5, the Copilot add-on, or Copilot Pro, with no grace period. For a 500-person shop on E3, turning Copilot back on across the board is roughly a $180,000-a-year line item that didn’t exist when people quietly built it into how they work — the free-sample era ending right as the habit set in. The same update did hand IT something real: granular Teams recap governance, with auto-deletion policies, classification-based purges, and a per-meeting kill switch for transcripts and AI notes — overdue controls for regulated environments. (Microsoft Locks Down Copilot in Office Apps, Adds Teams Recapture Governance)

The timing is the tell. The repricing and the license crackdown are landing in the same stretch where finance teams have stopped asking whether the organization is using AI and started asking what it returned — and, as last week’s reading kept showing, most don’t yet have a clean answer. The pilot era was funded on optimism; the production era is going to be funded on evidence, and the bill is showing up before the evidence does.

Subscribe now

The Control Layer Agents Were Missing Just Shipped

If most of last week’s reading was about scaffolding that hasn’t been built, one piece of it actually got built. The Model Context Protocol’s Enterprise-Managed Authorization extension went stable, closing a gap that’s been quietly undermining every enterprise agent rollout: until now, connecting an agent to a tool meant an employee clicking through an OAuth prompt for every single server, with no consistent policy and no shared audit trail. The fix makes the corporate identity provider the decision-maker — an admin sets access policy once, employees sign in with the credentials they already have, and the consent-screen sprawl disappears. Anthropic and Microsoft are among the first to support it across Claude, Claude Code, Claude Cowork, and VS Code, with Okta the first identity provider to ship it. (MCP Gets Its Missing Enterprise Authorization Layer)

The reason this matters beyond developer convenience is governance. Control and audit move into the identity console, so access decisions leave one trail, and deactivating a user cuts their agent access along the same path — no orphaned connections, no personal accounts quietly bolted onto work tools. For any IT team watching the shadow-AI problem from the first section of this Brief, this is the first credible way to bring sanctioned agent access under the same roof as everything else they govern. Asana, Atlassian, Figma, Linear, and others already support it, with Slack close behind.

One honest caveat the reporting flags: this layer governs identity, not authorization. It decides which servers an agent can reach, not whether a given action on a given resource is allowed in the moment — that decision still belongs to the policy engines sitting between the agent and the tool. It’s a front door, not a whole security system. But a front door is precisely what enterprise agent adoption has been missing.

The week’s through-line is a mismatch between speed and readiness, and it runs in one direction. The technology raced ahead — half the workforce on board, agents shipping, even a new layer to govern them — while the organizational machinery that turns any of it into value barely moved. Every piece I read last week was, underneath, the same diagnosis: the bottleneck isn’t the model, the license, or the protocol. It’s that most organizations still haven’t done the unglamorous work of redesigning how they operate around any of it — choosing the right problems, rebuilding the workflows, developing the judgment, deciding what to measure. That work never shows up in an adoption statistic or a vendor announcement, which is exactly why it keeps getting deferred. And it’s the only work that was ever going to separate the companies that get a return from the ones that just get a bill.

That’s it for this week’s BeAIReady brief!

If you appreciate the depth of reporting and how I connect the dots, please like, share this post, and subscribe (or share the Brief with a friend!). Thanks!

~erick

Subscribe now

Share

Here's what I was reading.

Washington Found the Off Switch

Late on Friday, June 12, Anthropic’s two most powerful models — Claude Fable 5 and the Mythos 5 system beneath it — went dark. Not because of an outage, and not because Anthropic chose to pull them. The U.S. government issued an export-control directive barring the company from giving any foreign national access to the models, and because that prohibition reached even Anthropic’s own non-citizen employees inside the U.S., the company concluded it had no workable option but to cut off access for everyone, everywhere. By Friday night, a model that hundreds of millions of people could use on Thursday was unreachable, and the company that built it had almost no say in the matter. (Anthropic disables Fable and Mythos AI models after U.S. government bars it from giving foreigners access)

It all happened quickly.

At 1 p.m. Anthropic got a call. They had 90 minutes to take the models down over a “national security threat”; the government wouldn’t give them any more detail. By 10 p.m. users had lost access. The trigger, per Axios, was a report from Amazon — one of Anthropic’s largest investors and partners — demonstrating a way to jailbreak Mythos into surfacing genuinely dangerous capabilities, followed by calls to administration officials from Amazon and at least five other companies. An investor helped take its own portfolio company’s flagship product offline, which tells you the competitive incentives in this market now run in directions that don’t map to ordinary loyalty. One person close to the decision called the result a “de-facto licensing regime” — the working assumption being that no company will cross the White House on something labeled national security. (How Amazon and the White House ended Anthropic’s Fable)

There’s an irony in all of this. For a year, Anthropic described Mythos in near-munition terms — too dangerous to release broadly, wrapped in elaborate safeguards. When the government moved, it essentially took the company at its own word. The safety positioning became the legal predicate for the shutdown — as one cybersecurity researcher dryly observed, a company that brands its own model as a munition in every release shouldn’t be shocked when the state eventually treats it like one. For its part, Anthropic argues the jailbreak was narrow. That it could be reproduced on other public models like OpenAI’s GPT-5.5, and that recalling a commercial model over it would, applied consistently, halt new model releases across the industry.

The reason Anthropic had to pull the models for everyone is that it couldn't reliably tell which of its users were foreign nationals. The shutdown order turned nationality into an identity-management problem they weren’t ready to solve. But the answer actually sits in a privacy-policy update quietly made the day before Fable's release: beginning July 8, Anthropic reserves the right to ask consumer users on its Free, Pro, and Max plans to verify their age or identity, collecting a government ID, a photo or video, and in some cases biometric facial-geometry data to do it. To get its most powerful models back online, the company is preparing to demand government photo ID from the people who use them — which means the export order's reach now runs past the model itself, all the way down to the identity of the end user. The policy doesn't say what triggers a check, but the logic is plain: prove US citizenship — a passport, or an enhanced driver's license from a northern-border state — and access can be restored without running afoul of the ban. (Anthropic's new privacy policy offers US consumers a way around the Fable ban)

For the people who actually have to run on this stuff, the takeaway isn’t about Anthropic’s politics. It’s that single-vendor model dependency stopped being a theoretical risk last week and became an operational one. A workflow wired entirely to one provider’s API can now be knocked out not by an outage or a price hike but by an export-control letter sent on a Friday night. The response already taking shape is the right one: model-agnostic architecture, with routing layers that can fail over to a second provider or an open-weights model on your own hardware the moment access vanishes. (Anthropic blocks all public access to Claude Fable 5, Mythos 5 following US government order — what enterprises should do)

Subscribe now

Microsoft and OpenAI Race to Own the Whole Stack

If the Anthropic shutdown showed what happens when you don’t control your own models, Microsoft spent the same days demonstrating the alternative. At Build 2026, Mustafa Suleyman told VentureBeat that a renegotiated contract had “set free” his division — roughly six months ago — to pursue its own frontier models, and the company put substance behind the claim: a family of seven in-house MAI models spanning reasoning, code, image, transcription, and voice, trained from scratch rather than distilled from someone else’s frontier system. Microsoft is no longer content to be the company that resells OpenAI’s intelligence; it’s building the capacity to generate its own.

The reality is, the models matter less than what sits on top of them. Suleyman’s argument here is that the next phase of AI value won’t come from the open web — that’s been exhausted. Instead, value will emerge from deep within enterprise data: the workflows, decisions, and institutional knowledge already living inside Microsoft 365 — Outlook emails, documents and spreadsheets, Teams conversations and channel collaborations, and Dynamics data. Frontier Tuning, announced alongside the models, lets companies customize Microsoft’s models on their own data inside their own compliance boundary, and the early partners aren’t toys — Mayo Clinic, EY tuning a tax agent for 75,000 professionals, Land O’Lakes. Pair that with Microsoft Scout, the company’s first always-on “Autopilot” agent carrying a governed identity in Entra, and you can see where Copilot is heading: from assistant to credentialed coworker. Microsoft’s bet is that owning the workflows where work actually happens is a deeper moat than owning any single model — and that bet is aimed straight at the digital workplace. (Microsoft AI chief says company was “set free” from OpenAI to pursue superintelligence)

OpenAI is making a different version of the same move. The Financial Times reported, via Reuters, that the company is planning its biggest ChatGPT overhaul yet — turning it into a “superapp” with coding tools, agents, and partner services like Canva and Booking.com — as part of a reorganization built to court enterprise clients ahead of a likely public listing. The detail that matters: two million businesses already account for about 40% of OpenAI’s revenue, a share the company expects to reach 50% by year-end. OpenAI is quietly becoming an enterprise software company in a consumer app’s clothing, and the superapp is how it intends to own the customer relationship rather than rent it through someone else’s interface. (OpenAI plans ChatGPT ‘superapp’ overhaul ahead of listing, FT reports)

Put the two together and the pattern is hard to miss: the biggest players are racing to control more of the stack — the model, the tuning layer, the agent, the interface, the customer — so that no single dependency can be turned against them. It’s the same instinct behind the diversification advice coming out of the Anthropic story, just running in the opposite direction. The irony Suleyman himself names is the tell: Microsoft’s real advantage, he argues, is optionality — OpenAI, Anthropic, and thousands of models inside Foundry, none of them indispensable. The lesson the whole industry absorbed last week is that optionality isn’t a luxury; it’s the strategy.

Share

Everyone’s Deploying, Almost Nobody’s Ready

For the average organization the control problem is different, but has parallels. An IBM study of 2,000 technology executives, released last week, found that four in five feel CEO pressure to run an AI transformation — and just 11% feel prepared for the scale of agent deployment coming over the next year. Seventy percent said AI is being deployed across their teams faster than IT can track it, and two-thirds of CIOs and CTOs said they’re held accountable for AI systems they don’t fully control. The gap isn’t between companies that have AI and companies that don’t; it’s between deployment pressure and the governance, cost visibility, and operating model needed to make deployment actually pay off. (AI deployment plans are catching leaders underprepared)

The Fortune piece I read alongside it shows what that unpreparedness costs. BCG’s latest Global AI at Work survey found that 42% of employees now save the equivalent of a full workday each week using AI — and 66% received little or no guidance on what to do with the time. Half aren’t redirecting it toward anything more strategic. The productivity gains are real; the organizational machinery to turn them into anything that shows up in results mostly isn’t there yet — which is precisely the paradox where saved hours evaporate instead of being optimized. The piece also marks the quiet close of “tokenmaxxing,” the brief stretch where companies pushed staff to run up AI usage for its own sake. With token costs now hitting budgets hard, several large tech firms have scrapped the internal leaderboards and begun asking the more uncomfortable question of who actually needs access, and why. (AI productivity gains are real but so is bad management)

What connects the two is a failure of leadership translation, not technology. The tools arrived ready; the management practice to deploy them deliberately — clear vision, defined use cases, accountability for outcomes — is the part that’s lagging, and it’s the part no vendor can ship you. This is the implementation gap in its plainest form: AI works for the individual almost immediately, and for the organization only after a lot of unglamorous work that most leaders haven’t started.

Share BE AI READY

The Comms Chief Inherits the AI Problem

The chief communications officer — the C-suite’s long overlooked stepchild — is getting their moment at the center of the table. Nearly half of CCOs now report directly to the CEO, up from 40% in 2023, and the role has expanded well past press releases and internal messaging, into something closer to a consigliere: monitoring reputational risk, weighing in on product, and increasingly steering how the company shows up not only in the press but inside AI chatbots. Roughly half of communications leaders are now leading or co-leading their organization’s AI change-management program — which means the person managing the corporate narrative is often the same person managing the AI rollout. (The Revenge of the Publicists: How Comms Execs Stormed the C-Suite)

That convergence is meaningful for everyone in the org. The same forces pulling comms upward — the fact that an investor memo, an ad, a press release, and a large language model’s answer about your company now bleed into one another — are the forces turning AI into a board-level reputational question rather than an IT project. And the job is already straining under the weight: only a third of CCOs feel adequately resourced, and workload satisfaction has dropped sharply in a year. The control theme running through the entire week ends here, inside the org chart — someone has to own how AI reshapes the company’s voice, and that responsibility is landing on people who didn’t ask for it and aren’t yet resourced for it.

Subscribe now

AI has stopped being a capability you adopt and quietly become a dependency you have to manage — that’s the shift underneath every story last week. A government proved it can reach into the stack and pull a model offline. The largest platforms answered by trying to own enough of that stack that no one can do it to them. And the organizations caught in between admitted, in survey after survey, that they can’t govern what they’ve already switched on. The reflex is to file each of these under someone else’s department — regulation, vendor strategy, IT, comms.

That reflex is the mistake. Managing a dependency is leadership work: deciding what you’ll rely on, what you’ll never rely on entirely, and who is accountable when the thing you depend on changes overnight. The companies that come out ahead won’t be the ones running the best model. They’ll be the ones who decided, before they were forced to, exactly how much control they were willing to hand to someone else.

That’s it for this week’s BeAIReady brief!

If you appreciate the depth of reporting and how I connect the dots, please like, share this post, and subscribe (or share the Brief with a friend!). Thanks!

~erick

Subscribe now

Share

We all know AI works. From paralegals summarizing depositions, to marketing coordinators drafting social copy, to branch managers prepping for quarterly reviews — everyday, more people are using across every industry.

AI makes tasks manageable. What’s harder to see clearly is what those tasks will look like three months from now, let alone three years. And that ambiguity is making it much harder for many workers to understand what it means — for their roles, their teams, or the direction their organization might be heading.

Amplifying that anxiety, is the speed of evolution. The tools and models that worked last quarter have already been superseded. The use case they pitched as innovative and differentiating, has become table stakes. Disruption isn’t happening in a cadence — it’s compressing, cycling faster, and leaving less room for the kind of clarity that allows workers to build confidence in the tools, process, or strategy in the first place.

Share

We Lost the Window

There used to be a shape to how organizations absorbed new technology. Disruption arrived. Then — critically — a period of relative stability followed. That window was where the real work happened: needs assessments, phased rollouts, training built around how people actually worked, experimentation that led to validated use cases. Implementation followed understanding. Trust formed because there was time for it to form.

That era is over.

AI disruption doesn’t arrive in waves with recovery periods in-between. The cycles are moving quickly and the timelines are compressing. Each new capability triggers fresh experimentation — before the last round has been fully understood. Pilots built around Q1 capabilities are outdated by Q2. Training cohorts finish onboarding and immediately encounter a tool that’s moved.

Meanwhile, the real costs — on the financial side tokenization and licensing, on the human side compounding uncertainty — hit before the value case has been established.

These kinds of adoption strategies were built for a steadier environment. They assumed enough runway existed to absorb another tool, complete another training, run another change management cycle. But that assumption no longer holds.

The statistics around this phenomenon aren’t surprising. It’s what happens when the conditions for trust formation are structurally removed.

Workers Are Using AI They Don’t Trust

A Quinnipiac survey found that over half of Americans use AI to research topics. Nearly a third of employed adults use it for work. And yet, that same survey said a whopping 76% only trusted AI-generated information “some of the time” or “hardly ever.”

Are workers using a tool they don’t fully trust to inform decisions that matter?

Our natural inclination might be to file this under “adoption challenges” or “change management.” It’s not. It’s a judgment problem. A governance problem. A culture problem.

Organizations are measuring whether people are using the tools — not whether they have any framework for knowing when to trust it, the source of its data, or the viability of the solution they used.

Usage is not literacy. Activity is not confidence. A workforce deploying tools it doesn’t trust isn’t ready. It’s complying.

The Generation That Was Supposed to Lead This

The internal narrative was tidy: Gen Z would pull adoption forward. These digital natives were already using tech like AI for everything anyway. All we need to do is point them at it.

The reality? 81% of Gen Z workers believe AI will lead to fewer job opportunities. They booed commencement speakers who talked about AI as the savior of the world.

Compared to the 66% of Boomers who feel the same way, Gen Z — the generation with the most exposure — is the most worried about displacement by it. Familiarity with the tools isn’t a measure of capability, capacity, or willingness.

Fluency doesn’t produce enthusiasm, especially when the stakes are so visible. Gen Z isn’t resisting AI. They’re reading the compression more clearly than the people driving the adoption campaigns.

Leaders Are Wrong About Their Workers — In Both Directions

Adecco surveyed 2,000 C-suite executives across 13 countries. 45% expect AI agents embedded in their workflows within 12 months. Only 30% of workers share that expectation.

Same study, but flipped — showed that 70% of workers feel ready to collaborate with AI agents. Only 39% of leaders believe that.

Both gaps are expensive. Leaders are over-ambitious on timeline — which produces rushed rollouts and workers who feel like something is being done to them. They’re also under-crediting actual workforce readiness — which means the people most equipped to move fast aren’t being asked or trusted to lead.

Miscalibrated in both directions simultaneously. That’s not a training problem. That’s a listening problem.

What the Burnout Numbers Say About All of This

The AI productivity narrative is landing inside organizations that are already stretched.

Glassdoor data shows burnout up 65% year-over-year. 65%!

Employee confidence is at a record low — only 43.8% report a positive six-month outlook. The tech sector posted the largest confidence drop of any industry: down 9.7 points.

The sector most associated with building and deploying AI is where confidence collapsed the hardest.

None of that shows up in a Copilot usage report. But it’s the environment where every rollout lands — a workforce absorbing continuous disruption with no stable ground underneath it, watching to see whether “AI will help you” means them or just the org chart above them.

What Closing the Gap Actually Requires

Adecco’s CEO said it about as clearly as possible, “AI moves at software speed. Organizational trust moves at human speed.”

The stability window — where users had time to establish and adapt — created the conditions for those speeds to reconcile. Without it, the gap expands.

The answer isn’t a better adoption program. Organizations that execute the old playbook with AI may be faster — but they are likely getting the same results, just faster.

And for some organizations, fast may be enough.

The problem is, generating more activity often comes with less trust and a workforce that’s complying without believing. What’s required is a different operating model all together. One built for continuous recalibration rather than sequential implementation. One that treats governance, judgment, and communication as ongoing practices — not one-time rollout components. One that assigns someone to answer the question workers are actually asking: what does this mean for the work I do?

Most organizations haven’t built that. Most haven’t decided who would own it.

Adoption rates are real. So is the structural break that’s making them increasingly meaningless as a measure of readiness.

The window isn’t coming back. The organizations that close this gap will be the ones that stop designing for conditions that no longer exist.

If you’re looking to adapt a more strategic approach to AI, rather than just rolling out licenses to people, StitchDX can help.

Share BE AI READY

Sources: Quinnipiac University Poll (2025), Adecco AI at Work Report (2025), Glassdoor Workforce Confidence Index (Q1 2025), Fast Company / Jon Cooper — “Employee Engagement Was Built for a More Stable Era” (June 2026)

The irony shouldn’t be lost on anyone: last week’s news was full of stories about AI driving more tech layoffs, enterprises continuing to cut headcount to fund AI infrastructure, while CFOs question whether the AI spend is worth it. Those stories feel antithetical to this labor market’s resilience. The dominant theme, across everything I read, was the gap between where AI investment is going and where organizational readiness actually is — in spending discipline, in governance, in the workforce itself.

Here’s what I was reading.

Share

Microsoft Claims the AI Infrastructure Layer

Microsoft Build 2026 was about establishing a strategic position in the midst of a lot of AI chaos. But the keynote included so many product announcements at once — Work IQ, Microsoft IQ, Agent 365 general availability, MAI-Thinking-1, Microsoft Scout, Windows as an agent-native runtime — that it was easy to lose the thread. Microsoft is no longer primarily in the business of selling AI assistants; it’s in the business of becoming the governance and intelligence infrastructure layer for the enterprise AI era. (Microsoft Build 2026: Be yourself at work)

The Work IQ APIs, set for general availability on June 16, are the clearest expression of that bet. The pitch is that agents interacting with Microsoft 365 data through Work IQ get context that’s already been semantically processed — they’re not pulling raw files and stitching them together, they’re accessing an intelligence layer that already understands the organizational relationships underneath the data. Microsoft’s own figures put the average Fortune 500 data footprint processed through Work IQ at over 600 terabytes, and they claim the APIs run at twice the speed and use 80% fewer tokens than traditional approaches. Whether or not those numbers hold in production across every environment, the concept is significant: if agents get context from Work IQ, Microsoft controls the quality, the cost, and the compliance boundary of that context. (Announcing the new Work IQ APIs)

Agent 365 is the governance side of the same coin. Now generally available at $15 per user per month, it’s Microsoft’s answer to shadow AI — the coding assistants, productivity tools, and autonomous workflows employees are running on their own devices, often without IT’s knowledge. The launch details are worth sitting with: Microsoft is already observing cross-prompt injection attacks in enterprise environments, agents inadvertently exposing sensitive infrastructure through unauthenticated MCP servers, and data loss prevention systems that “simply aren’t designed to understand agentic access patterns.” The signal here isn’t that Agent 365 exists — it’s that Microsoft is documenting live incidents at enterprise customers, which means the shadow AI governance gap isn’t theoretical. By June, the platform will support discovery and management of 18 different local agent types, including GitHub Copilot CLI and Claude Code. (Microsoft takes Agent 365 out of preview as shadow AI becomes an enterprise threat)

Taken together, Work IQ and Agent 365 frame the same strategic move from two sides. Work IQ makes Microsoft’s intelligence layer the cheapest and most efficient route for agents to access organizational context. Agent 365 makes Microsoft the only platform capable of seeing and governing all agents running across an enterprise estate. That’s a platform lock-in play — and the timing, at Build 2026, is deliberate.

The Token Bubble Is Popping

The AI cost reckoning that’s been building for months broke into the open last week. Microsoft reportedly cancelled most of its own Claude Code licenses, in part over costs. Uber’s COO described AI costs as getting “harder to justify.” One AI consultant told Axios that a client spent half a billion dollars in a single month after failing to put any usage limits on employee Claude licenses. The pattern underneath these headlines is consistent: organizations that deployed AI at scale in 2024 and 2025 did so without the cost controls they’d apply to any other category of enterprise spend. The result is a reckoning that’s showing up in actual CFO conversations right now — not in projections or research reports, but in budget line items that nobody planned for. (AI sticker shock hits corporate America)

The emerging response is model routing — matching query complexity to the appropriate model rather than defaulting to the best one for every task. The math is clarifying: Glean’s CEO estimated that roughly 95% of enterprise AI usage is currently running on expensive frontier models, even for tasks that cheaper alternatives handle equally well. Cognition’s CEO put the efficiency gain from intelligent routing at five to ten times better cost performance on routine work. The example that lands: every frontier model will tell you Thomas Jefferson was the third U.S. president. Paying top-tier inference rates to answer that question thousands of times a day is where the AI budget goes. The practice of defaulting to the most powerful model for every query — which has been the path of least resistance since 2024 — is now a financial liability, and the organizations that route intelligently will have a meaningful cost advantage over those that don’t. (Model routing is a fix for AI overspending. That’s a problem for OpenAI and Anthropic)

The People Contradiction

GitLab cut 14% of its workforce — about 350 employees — while simultaneously reporting a 23% year-over-year revenue increase to $264 million and 88% gross margins. The rationale wasn’t automation in the conventional sense; it was infrastructure. Agentic workloads are pushing developer infrastructure to limits it wasn’t designed for, forcing what the CEO called a “generational rebuild of git” to support the scale requirements agents create. The company is exiting 22 countries, flattening management layers, and partnering with an AI lab on purpose-built agent APIs. The structural point worth noting is that AI adoption doesn’t just change what software teams do — it changes what the software those teams build on top of needs to be able to handle. (GitLab cuts 14% of staff as it scales its platform to serve AI workloads)

Cognizant’s CEO is making a deliberately different bet. The same week GitLab announced its restructuring, Ravi Kumar said his company hired 20,000 entry-level graduates last year and expects that number to grow in 2026. His new “Frontier Certified Engineer” and “Frontier Business Operator” roles don’t require technical backgrounds; a history major or an HR accountant qualifies. The organizational logic: AI does best in the middle of workflow pipelines, while humans remain essential at the front end, setting direction, and at the back end, validating outputs. But Kumar’s more interesting contribution last week was his challenge to how AI productivity gets measured. Token consumption, he argued, is a “vanity metric” — a proxy for activity rather than value. What Kumar is pushing toward — measuring AI performance by underwriting outcomes rather than counting tokens or licenses deployed — would require most organizations to rebuild the accountability structures around their AI investments from the ground up. That’s a harder change than deploying a new model. (Cognizant CEO is swimming against the tide on AI)

World Economic Forum research published last week adds a layer that both the GitLab and Cognizant stories tend to skip: the workers themselves. The study mapped five employee archetypes — enthusiasts, curious, cautious, skeptics, and opposed — and documented something organizations don’t like to see in their dashboard data. Even employees who appear to comply with AI mandates in public are often actively resisting in private. The researchers called this “frontstage compliance, backstage resistance,” and the finding that extends even to AI enthusiasts tasked with implementation is worth sitting with. If adoption metrics are measuring what employees do publicly with AI tools — sessions, completions, usage rates — they may be systematically underreporting the gap between what AI is supposed to be doing and what’s actually happening in practice. (The 5 faces of human readiness for AI adoption)

A Fortune piece last week ties across all three of these: most organizations already have AI running without any formal governance structure in place. Employees are feeding customer data into consumer tools. Procurement is signing SaaS contracts with AI embedded in the fine print. No one has unambiguous ownership. The piece is explicit that waiting for a perfect governance framework is itself a form of abdication — “not caution. It’s abdication” — and that the two branches of AI governance (product-facing and back-office) require different frameworks that most organizations haven’t bothered to distinguish. The argument that lands hardest is this: the companies that win the AI era won’t necessarily be the ones with the most capable models — they’ll be the ones that built governance infrastructure early enough to deploy with speed and accountability. (The boardroom wants answers on AI. Are you ready?)

Anthropic Wants to Hit the Brakes

Last week, Anthropic published a post calling for top AI labs to voluntarily slow or pause frontier AI development, and proposing a global verification mechanism for enforcing such a pause. The specific risk they flagged is recursive self-improvement — the point at which AI systems become capable of improving themselves without human intervention. Anthropic co-founder Jack Clark put a timeline to it: he believes this threshold could arrive within the next two years, possibly sooner. The company compared the enforcement challenge to nuclear-weapons treaties, then acknowledged the comparison undersells the difficulty: “Training runs are far easier to conceal than missile silos.” (Anthropic Urges Global Pause in AI Development)

The call itself is worth taking seriously. The counterargument — that this is regulatory capture dressed up as safety concern, or a marketing play around Anthropic’s “Mythos” model — doesn’t account for the fact that the researchers making this case have been making it consistently, and with internal data to support it. Ethan Mollick’s framing in the WSJ piece is probably the most useful: inside every frontier AI lab is a mix of a normal trillion-dollar company, researchers focused on building the next model, and “philosopher kings” genuinely alarmed about what comes next, all in tension with each other.

What I find more significant than the pause call itself is the context: Anthropic wrapped up a fundraising round at nearly $1 trillion in valuation and filed confidential IPO paperwork in the same period it published this post. A company raising capital at that scale is making an implicit argument that the demand for frontier AI will continue to compound. And yet its research institute is simultaneously arguing that the pace of development is moving faster than society’s ability to govern it. That’s not hypocrisy — it’s an accurate picture of the bind every frontier lab is actually in. The commercial logic and the safety logic are in genuine tension, and Anthropic is being more transparent about that tension than most.

On the Bigger Picture

The other IPO-adjacent story last week: Reuters reported that OpenAI is planning its biggest ChatGPT overhaul yet, redesigning the product into an enterprise-focused “superapp” with enhanced coding tools, AI agents, and integrations with partners including Canva and Booking.com. The enterprise-first framing is notable — 2 million businesses currently account for about 40% of OpenAI’s revenue, and the company expects that share to rise to 50% by year-end. The move to deprioritize consumer use cases in favor of enterprise workflow integration, timed to a likely IPO filing, is a bet that the most defensible AI revenue isn’t in consumer subscriptions — it’s in becoming indispensable to how businesses actually work. That’s a meaningfully different thesis than what OpenAI started with, and it positions it in direct competition with exactly the enterprise layer Microsoft spent last week claiming. (OpenAI plans ChatGPT ‘superapp’ overhaul ahead of listing)

Anthropic is worth close to a trillion dollars, filing for an IPO, and calling for a global pause in AI development — because its own co-founder believes recursive self-improvement could arrive within two years. GitLab is cutting 14% of its workforce while growing revenue at 23%, because agentic workloads have already outpaced the infrastructure built for humans. Cognizant is hiring 20,000 entry-level graduates, because its CEO believes AI will hollow out the middle of organizational pyramids while creating more need at the edges. None of these positions is obviously wrong. They’re logical responses to the same underlying reality — that the technology is moving faster than the organizational structures surrounding it. The governance piece, the spending discipline, the honest measurement of what’s working and what isn’t: that’s what most enterprises are still building. And it’s the only thing that lets any of the rest of it move with confidence.

At StitchDX, we work with enterprise organizations navigating exactly this — deploying AI deliberately in Microsoft 365 environments, building governance frameworks that actually work, and helping teams move from evaluation to structured adoption. If this week’s reading maps to conversations you’re already having internally, we’d welcome the chance to talk.

That’s it for this week’s BeAIReady brief!

If you appreciate the depth of reporting and how I connect the dots, please like, share this post, and subscribe (or share the Brief with a friend!). Thanks!

~erick

Subscribe now

Share

Organizations are adopting AI at scale, at a pace that is often faster than they planned. Leaders are pulling the brakes and asking if any of it is working… for the organization… or for the people inside them.

Uber Can’t Prove It, and the CEOs Who Started the Hype Are Admitting It

Uber’s story is useful precisely because it doesn’t involve a struggling company making excuses. This is one of the most AI-forward businesses in Silicon Valley — a company whose core product runs on AI — and its COO spent the week publicly questioning whether the money was worth it. According to reporting in Fortune, Uber burned through its entire 2026 AI coding budget in just four months after incentivizing adoption through an internal leaderboard that ranked teams by AI tool usage. By the time the COO started asking questions, 95% of engineers were using AI tools and 70% of code was AI-generated. The problem wasn’t adoption. It was that no one could draw a line from those numbers to anything that actually served users. “That link is not there yet,” COO Andrew Macdonald said. “It’s very hard to draw a line between one of those stats and ‘Okay now we’re actually producing 25% more useful consumer features.’” (Uber burned through its entire 2026 AI budget in four months. Now its COO is questioning whether it’s worth it)

What makes this particular moment important is that it coincides with a notable reversal from two of the people most responsible for shaping expectations about AI’s economic impact. Sam Altman and Dario Amodei — who between them spent the better part of last year warning that AI would eliminate entry-level white-collar jobs at scale — both walked back those predictions in public this week. Altman told an audience he was “pretty wrong” about AI’s impact on employment so far. Amodei reframed automation not as a destroyer of jobs but as a multiplier of output: if AI automates 90% of a job, the remaining 10% “expands to be 100% of what people do.” Goldman Sachs CEO David Solomon, who was skeptical of the apocalyptic framing all along, pointed to 145% employment growth since 1962 as evidence that technological disruption doesn’t follow the script its proponents predict. The reversals matter not just as data points about AI’s actual impact on labor, but as a signal about how much of the AI narrative has been shaped by founders who had powerful incentives to generate a sense of urgency. (Sam Altman and Dario Amodei are both walking back AI jobs apocalypse predictions)

The Uber and Altman stories land at the same pressure point. Organizations spent 2025 buying AI under the twin pressures of competitive fear and leadership hype — and now the ROI question is being asked in earnest, by finance teams, by boards, and increasingly by the executives who made the calls.

Subscribe now

Using AI Doesn’t Mean They Trust It

A Quinnipiac University poll released this week shows that over half of Americans are now using AI to research topics, and nearly a third of employed adults are using it for their jobs. But 76% of those Americans say they can trust AI-generated information only “some of the time” or “hardly ever.” The math is uncomfortable: a substantial and growing portion of the American workforce is regularly deploying a tool it doesn’t trust to produce outputs that inform business decisions. That isn’t an adoption problem. As the article puts it, it’s a judgment and governance problem — one that sits at the intersection of workforce capability, organizational culture, and the credibility of the executives overseeing AI deployment. (Workers Are Using A.I. They Don’t Trust. That’s a Problem for the C-Suite)

The generational finding is actually most interesting to me. Gen Z — the cohort that was supposed to be AI’s natural champions inside the enterprise, the fluent digital natives who would pull adoption forward — is the most pessimistic of any age group about what AI means for their employment. 81% percent of Gen Z respondents believe AI will lead to a decrease in job opportunities, compared to 66% of baby boomers. This inverts a narrative that has driven a lot of AI change management strategy: the assumption that younger workers would lead enthusiasm from below. The Quinnipiac data suggests that familiarity with the technology has produced not enthusiasm but a clearer-eyed reading of where the risk actually falls — and entry-level workers know they’re in the exposure zone.

The backdrop for all of this showed up in Glassdoor data released this week – burnout rates are up 65% year-over-year, and employee confidence is at a record low. Only 43.8% of employees are reporting a positive six-month business outlook. Workers who mentioned burnout in their reviews were 76% less likely to give overall positive ratings, and 78% less likely to recommend their companies to friends. The technology sector posted the largest confidence drop of any industry, down 9.7 percentage points year-over-year. The AI productivity narrative is landing inside organizations where the people AI is supposedly helping are struggling in ways that don’t show up in token usage dashboards. (Burnout is increasing, while employee confidence is at a record low, research shows)

Share

Leadership Expectations Aren’t Matching the Worker Reality

The Adecco Group surveyed 2,000 C-suite executives across 13 countries for its annual workforce research, and the headline number is one that won’t surprise anyone who has been reading these trends: 45% of business leaders expect AI agents to be integrated into workflows within the next 12 months, but only 30% of workers share that expectation. What’s new isn’t the gap — it’s how wide the failure of communication is underneath it. Only 36% of leaders say their talent strategy clearly demonstrates that AI will create opportunities for employees rather than eliminate them. Only 39% are involving employees directly in job redesign. Only 22% say they are highly confident their organizations are developing the future-ready capabilities needed to keep pace. (Global Study Finds Widening Gap Between AI Ambition And Workforce Readiness)

Adecco’s CEO put it directly: “AI may move at software speed, but organizational trust moves at human speed. Companies that ignore that gap will struggle to turn pilots into performance.” What the research also shows — and this is the part that tends to get overlooked in the readiness conversation — is that workers may actually be more ready than leaders assume. Seventy percent of workers said they feel ready to collaborate with AI agents. Only 39% of leaders believe their employees would be comfortable with agents. Leaders are underestimating their workforce while simultaneously failing to communicate, invest in change management, or redesign roles in ways that would make readiness real. The confidence gap isn’t just between the C-suite and the rest of the organization. It’s between what leaders say they want and what they’re actually doing to get there.

Share BE AI READY

The Human Cost Nobody Budgeted For

Two pieces this week approached the human cost of AI adoption from different angles and arrived at the same concern. Workday’s Human Connection Workplace Index — a survey of 2,150 employees at large enterprises who actively use AI — found that while AI is reducing burnout and boosting productivity for most respondents, it is also creating what the report calls a “connection deficit.” Sixty-two percent of employees say their stress or burnout risk has decreased since using AI. But 20% of Gen Z workers took time off this year due to loneliness or isolation — and Gen Z is 12 times more likely than Gen X to report feeling completely disconnected from colleagues. The finding that stands out most is that 37% of respondents have turned to AI for companionship, citing its judgment-free, always-available nature as reasons they prefer it to colleagues. That is not a productivity metric. That is a sign of something structural shifting in how people at work relate to each other. (New Workday Global Research Finds AI is Easing Burnout but May Be Deepening a Connection Deficit at Work)

A Fast Company piece from the same week took a wider lens. The author — who has spent two decades working with leaders across 20 countries — argues that the AI conversation’s focus on jobs and roles is obscuring a more consequential shift: the dismantling of the relational infrastructure that work has always provided. Entry-level roles aren’t just where people learn technical skills; they’re where people learn to navigate difficult colleagues, earn trust without authority, read a room. Knowledge isn’t just what people know; it’s forged through mentorship and peer relationships that pressure-test ideas. “Implementing AI is not a technology problem. It’s a people problem. It always is.” The quote is from Charlene Li, cited in the piece, and it points at something organizations are systematically underprioritizing: the leaders who are struggling most with AI are those who built authority on knowing more than everyone else, and AI just democratized what they were hoarding. The leaders thriving are the ones who built authority on relationships and trust. (AI may be eating jobs, but it poses an even bigger threat)

Subscribe now

HR’s Dirty AI Hiring Secret

The most important research I found last week came from researchers at Stanford, Chapman, and Northeastern, and it documents something that organizations deploying AI hiring tools should find genuinely alarming. The study — described as the largest independent analysis of AI-powered hiring algorithms ever conducted — examined more than 4 million job applications across 156 employers, all screened by the same vendor’s algorithms. The finding: more than 25% of all applications submitted by Black job seekers were directed to positions where the algorithm produced outcomes that trigger federal discrimination scrutiny. The vendor, Pymetrics, had conducted its own bias audits and found no problem — not because the analysis was dishonest, but because it was measuring at the wrong level. Pymetrics pooled all applicants and outcomes across all employers and positions. The researchers analyzed each of the 1,746 individual positions separately, which is how U.S. employment discrimination law is actually designed to be applied. When you do it right, 10.62% of positions show adverse impact on Black applicants. (Largest study of AI hiring algorithms to date finds ‘clear racial disparities’ — over 25% of Black applicants tainted by bias)

The second finding may be even more consequential for organizations using these tools. Because algorithms produce the same output for the same input every time, and because scores are stored and reused across employers, a candidate who gets screened by Pymetrics at one company isn’t really getting a fresh evaluation at the next company that uses the same platform. Researchers documented what they call an “algorithmic blackball” — where applicants rejected once are effectively rejected by all employers using the same vendor, without knowing it. The implication for any organization using a third-party AI screening platform is direct: you may be discriminating at scale, your vendor’s audit almost certainly used the wrong methodology, and the EU AI Act’s compliance requirements for hiring algorithms go into effect August 2. The gap between what organizations believe their AI tools are doing and what they are actually doing is not a hypothetical governance risk. It is a documented one.

Share

On the Bigger Picture

Microsoft’s May Copilot Studio update is worth reading even for organizations that aren’t deep into the Microsoft ecosystem, because it marks a meaningful expansion in what enterprise automation can actually reach. Computer-using agents — which can now interact directly with websites and desktop applications through the UI, without requiring API access — are now generally available. This matters for the specific, persistent problem that has defeated a lot of automation efforts: legacy systems and vendor portals that were never designed to be automated. A company like Graebel, featured in the release, can now automate its relocation request processing end-to-end, even though its proprietary platform lacks API support, by building an agent that navigates the UI the way a human would. The May update also brings agent-to-agent communication to general availability, a new visual workflow designer for building multi-step agentic processes, and Work IQ REST API and MCP server support for connecting agents across enterprise systems. (What’s new in Copilot Studio: May 2026 updates and features)

Share BE AI READY

The people closest to AI — the workers using it daily, the Gen Z employees whose entire careers will be shaped by it — are the least confident about what it means for them, and the most likely to be quietly paying a cost that doesn't show up in any dashboard. Altman admitted he was wrong. Uber's COO admitted the math doesn't close. A Stanford team proved the hiring algorithm was discriminating in ways the vendor's own audit couldn't detect. All of that happened in the same week that burnout hit a 65% year-over-year increase and worker confidence hit a record low. Organizations are not running out of data here. They are running out of reasons to keep treating the human side of AI adoption as someone else's problem to solve later.

That’s it for this week’s BeAIReady brief!

If you appreciate the depth of reporting and how I connect the dots, please like, share this post, and subscribe (or share the Brief with a friend!). Thanks!

~erick

Subscribe now

Share

Last Tuesday, Google I/O launched two big announcements that will have a major impact on every business: search as a link-retrieval interface is effectively over, and vibe coding is coming to your phone. Markets held near record highs last week — the S&P above 7,400 — but what I read last week didn’t lean into the momentum. There’s a growing distance between AI investment confidence and deployment reality. While CEOs are doubling their spending and expecting agents to deliver measurable ROI in 2026, the workforce is being sorted out in ways few have fully anticipated. Meanwhile, human connection — the thing AI demonstrably still cannot automate — may be the resource most quietly at risk.

The Bet Is Getting Bigger. The Proof Is Still Thin.

The BCG AI Radar 2026, based on a survey of nearly 2,400 executives including 640 CEOs, is the most comprehensive read on where executive confidence actually sits right now. Four out of five CEOs are more optimistic about AI ROI than they were a year ago, nearly all believe agents will deliver measurable returns in 2026, and corporations collectively plan to double their AI spending as a share of revenue — from 0.8% to about 1.7%. CEOs are also increasingly taking personal ownership of AI outcomes: nearly three-quarters say they are their organization’s primary AI decision-maker, double the share from last year. The BCG “Trailblazers” — about 15% of the CEO cohort — are already directing more than half of their 2026 AI investments to agents specifically, deploying them end-to-end rather than in isolated pilots. Half of those CEOs believe their jobs are on the line if AI doesn’t pay off. (As AI Investments Surge, CEOs Take the Lead)

What BCG doesn’t fully reckon with, and what the Fortune piece does, is the pattern underneath the optimism. The author has spent two decades leading enterprise technology companies through the cloud transition, the mobile revolution, and the platformization of work. His argument is that AI washing is following the exact same script as every prior tech cycle: organizations equate a change in technology with a change in headcount before they’ve done the harder work of mapping what the technology has actually absorbed. The more useful lens, he argues, comes from Anthropic’s labor market research: even in occupations with the highest AI exposure, there has been no statistically significant increase in unemployment, because AI is primarily eliminating tasks, not jobs. His company’s own workforce intelligence platform, tracking more than 55,000 skills across 1.3 billion job postings, shows positive demand growth across 15 of 16 occupational categories — demand outpacing supply by an average of 3.2 times. The implication is uncomfortable: most organizations are making the workforce math harder by cutting headcount before they’ve understood what AI has actually changed at the task level, and before they’ve invested in the judgment, creativity, and resilience that become more valuable precisely because AI can’t replicate them. (I’ve led companies through every major tech disruption. AI washing is the same mistake, every time)

Gartner’s 1Q26 global labor survey of 12,004 employees across 40 countries adds a sharper edge to that gap. Only 27% of executives have a comprehensive AI strategy, and just 20% believe their workforce is truly AI-ready. The survey also surfaces what Gartner calls the “enablement illusion” — leaders measuring AI success by basic adoption rates rather than the depth and diversity of how AI is actually being used — while missing a talent risk with a hard deadline: Gartner predicts that by 2027, half of enterprises without a people-centric AI strategy will lose their top AI talent to competitors who prioritize workforce enablement over adoption metrics. The people building your AI capability are the most likely to leave if the strategy doesn’t account for them. (Gartner Predicts by 2027, 50% of Enterprises Without a People‑Centric AI Strategy Will Lose Their Top AI Talent)

The three pieces, read together, map the gap precisely. CEO confidence is at its highest point in the cycle. The organizations that will actually realize returns are the ones that treat AI as an operating-model problem — not a deployment one.

Subscribe now

The Labor Market Is Sorting — and Not the Way Anyone Anticipated

The CNBC piece on AT&T’s workforce challenge is one of the better labor market reads I’ve come across this cycle. AT&T is committing $250 billion over five years to expand its fiber network and meet AI infrastructure demand — and 15% of that investment is earmarked for hiring and training. What AT&T’s CEO described is a genuine scarcity: the company needs electricians, HVAC technicians, and fiber installers it simply can’t find, while the same AI infrastructure boom is quietly eroding the entry-level white-collar market that most recent graduates expected to enter. Stanford’s Digital Economy Lab tracked a 16% slower employment growth rate for early-career workers in AI-exposed roles — software, marketing, finance — between mid-2024 and September 2025, and separate Census Bureau research found a 12–15% decline in employment for workers ages 22–24 in AI-exposed industries in the same period. The pattern is becoming hard to dispute: the buildout requires blue-collar labor that isn’t there; the displacement is showing up first among the people who just spent four years preparing for white-collar careers. (The AI economy is rewriting the American Dream — and blue-collar workers are poised to win)

The Fast Company piece accepts that trajectory and asks a harder question: what disappears along with the jobs? The author — who has worked with leaders across 20 countries for two decades — argues that entry-level work was never primarily about the tasks it produced. It was about the place where people learned to navigate a difficult colleague, earn trust without authority, read a room, recover from a mistake. “The leaders struggling most with AI,” she writes, citing Charlene Li’s research, “are those who built their authority on knowing more than everyone else, hoarding information as a form of power — AI just democratized what they were hoarding.” The corollary is structural: if AI eliminates the entry points where those relational skills get built, the organizations trying to run human-AI collaboration will be doing so with a workforce that never had the chance to develop the capabilities that collaboration actually requires. The piece cites a WHO Commission on Social Connection that has documented loneliness and disconnection as global health crises — not as a detour, but as the destination of the argument. What AI cannot automate may be the resource most at risk from the way AI is being deployed. (AI may be eating jobs, but it poses an even bigger threat)

Share

Google Rewrites the Interface Layer

Google I/O last Tuesday produced two announcements that, individually, would have been significant. Together, they signal something more fundamental about where the AI transition is heading.

The first is the end of search as most people have understood it. Google unveiled what it describes as the biggest change to Search since the search box debuted 25 years ago: a redesigned interface centered on conversational AI, “information agents” that can monitor the web on your behalf 24/7 and synthesize updates when conditions are met, and a generative UI layer that builds interactive, stateful mini-apps in response to natural-language queries. AI Overviews now reach more than 2.5 billion monthly users; AI Mode, Google’s conversational search, has already crossed 1 billion — and the link-retrieval model that underpinned organic search traffic, SEO strategy, and digital advertising is being retired underneath them. The most advanced features roll out to paid subscribers first, then broadly, free. For organizations that have built content and discovery strategies around the assumption that people use search to navigate to sources, that assumption is now officially in question. (Google Search as you know it is over)

The second announcement was the extension of vibe coding to mobile. Google’s AI Studio can now take a natural-language description and produce a working native Android app, exportable to a device in minutes. The initial scope is limited to personal utility apps, and Play Store rules still apply — but the signal is directional. The assumption that building functional software requires engineers is dissolving, and it is dissolving faster than most enterprise software governance models, vendor relationships, or IT procurement cycles are built to accommodate. When a line-of-business team can prototype a custom workflow tool in an afternoon, the question of what IT is actually gatekeeping — and whether that gate is adding value — becomes newly live. (Vibe coding is coming to your phone)

Share BE AI READY

On the Bigger Picture

Three pieces from last week that don’t fit neatly into the workplace thread but deserve attention.

The Washington Post reported that Elon Musk — who ran DOGE and once proposed cutting $2 trillion from the federal budget — is now publicly calling for universal high-income checks issued by the federal government to address AI-driven job displacement. Anthropic CEO Dario Amodei has called for similar measures, including UBI. OpenAI published policy proposals framing the AI transition as requiring “an even more ambitious form of industrial policy” than the New Deal. What’s notable isn’t any single proposal but the convergence: the people building the tools that may displace a significant share of the workforce are now, in public, arguing that the social contract needs to be renegotiated — urgently, and at scale. Whether that represents genuine concern or sophisticated reputational hedging is a question worth sitting with. (Elon Musk’s AI utopia depends on massive government checks)

A Fortune piece argued that AI has effectively repealed Brooks’s Law — the 50-year-old principle holding that adding engineers to a late software project makes it later. The data point that stopped me: large AI companies now generate nearly three times the revenue run rate per employee as non-AI software firms, because the constraint has shifted from human coordination to compute budgets. For enterprise leaders whose vendor landscape is about to be reshaped by small, highly capitalized teams building at unprecedented speed, this is worth understanding. (The 50-year-old law that governed every software company just broke)

The New Stack piece on MCP servers and synthetic data is more technical, but it addresses something practical for anyone managing enterprise AI compliance. Governance frameworks built for human-paced workflows — manual reviews, approval committees, periodic audits — are structurally incompatible with agentic systems that make hundreds of data requests per hour. The answer isn’t slowing agents down; it’s redesigning governance as real-time infrastructure, using MCP to let agents request governed, virtualized data copies through a standard interface rather than routing through manual approval chains. The compliance gap in non-production environments is growing, and the EU AI Act is raising the stakes. (How MCP and synthetic data are reshaping compliance in the agentic era)

Subscribe now

The juxtaposition between the confidence of those building and deploying AI and the consequences for everyone else living with it is, itself, the warning sign. CEOs are doubling their bets; Google retired the search interface; tech leaders are calling for mass redistribution to offset displacement their own tools are driving. And underneath all of it was a Fast Company piece asking what happens to the people who never got to develop the relationship skills that entry-level work used to build — because those jobs are the first to go. That’s a leadership problem, not a technology one, and it’s the kind that’s quietly compounding now — despite all the warning signs.

That’s it for this week’s BeAIReady brief!

If you appreciate the depth of reporting and how I connect the dots, please like, share this post, and subscribe (or share the Brief with a friend!). Thanks!

~erick

Subscribe now

Share

That gap between AI investment and AI employment is starting to wear thin among organizational leadership. The consistent finding is that while AI works — organizations aren’t. The tools remain ahead of the institutions using them, and that widening gap is starting to show up in the workforce, in the ROI numbers, and in the psychological cost to the people caught in the middle.

The ROI Isn’t Missing — the Org Is

The most striking number I came across last week was buried in Writer’s 2026 enterprise AI adoption survey of 2,400 executives and employees: 97% of organizations have deployed AI agents in the past year, and only 29% see significant ROI from generative AI. Three-quarters of executives admitted their company’s AI strategy is “more for show” than actual internal guidance. 48% percent called AI adoption a “massive disappointment.” The gap between deployment and transformation is widening, and the data makes it clear this is a governance and culture failure — not a capability failure. (Enterprise AI adoption in 2026: Why 79% face challenges despite high investment)

Microsoft’s 2026 Work Trend Index, analyzed in a Fortune piece aimed at CFOs, arrived at a compatible finding from a different angle. Organizational factors — culture, manager support, talent practices — account for 67% of reported AI impact, compared with just 32% attributed to individual mindset and behavior. If two-thirds of AI’s business value depends on how an organization is structured and led, then framing AI ROI as a technology problem doesn’t just misdiagnose the issue — it gives the wrong people cover for the gap. The alignment numbers underscore it: only 26% of AI users say their leadership is clearly and consistently aligned on AI strategy, and only 13% say they’re rewarded for reinventing work with AI even when results aren’t immediate. (What Microsoft’s new research tells CFOs about the ROI of AI)

A CIO.com piece introduced a concept I’ll be using for a while: the “aversion tax.” The argument is that every dollar of AI investment is subject to a reduction based on the actual adoption rate — an algorithm that is 99% accurate but only 10% utilized has effectively destroyed 90% of its value. The author cites an Amazon case where a model identifying $176 million in annualized savings sat unused because floor managers reverted to gut instinct and sticky notes rather than trust the machine. The implication for enterprise leaders is that any honest ROI calculation for an AI initiative has to start with a realistic human adoption estimate, not a feature spec — and most of them don’t. (The ghost in the machine: Why AI ROI dies at the human finish line)

Goldman Sachs’ CIO Marco Argenti offered the most useful reframe on measurement I read all week. He doesn’t track how much each employee uses AI — even though Goldman can see that data for all 12,000 of his engineers. He tracks how fast a team moves from idea to prototype. “There’s zero time between idea and prototype — you kind of ‘3D print’ software,” he told Business Insider. The right metric isn’t usage frequency, it’s delivery velocity: if your backlog isn’t shrinking, the AI investment isn’t landing, regardless of what the adoption dashboard shows. That shift in measurement philosophy — from individual tool engagement to team-level output — is one of the cleaner frameworks I came across this week. (Goldman Sachs’ tech boss says he doesn’t track AI usage, he watches how fast teams ship)

Subscribe now

AI Is Restructuring the Workforce — and Organizations Are Letting It Happen

The April 2026 jobs report data showed that the information sector — tech, telecom, data processing — shed another 13,000 jobs. That’s makes sixteen consecutive months of net losses, bringing payrolls to their lowest level since March 2021, wiping out four years of sector gains. This is happening simultaneously with the largest AI infrastructure spending in history. The sector that is supposed to be the primary beneficiary of AI investment is losing jobs at a rate that is one of the longest peacetime declines in any major sector in modern labor data — and the causal link to AI is still being debated precisely because that debate is uncomfortable. (April 2026 jobs report: AI, white-collar layoffs, wages)

Meta made the structural logic explicit. With 8,000 layoffs scheduled for May 20 and capital expenditure climbing to a record $125–145 billion this year, Zuckerberg described a company being rebuilt around what he calls “ultraflat” teams — one manager for every 50 engineers — where AI tools allow one or two people to ship in a week what once required dozens over months. What’s striking isn’t the headcount number, it’s that CFO Susan Li admitted she doesn’t know what the company’s ideal size even looks like anymore when AI capabilities keep shifting what one person can build — and that honesty should unsettle every executive making workforce planning assumptions based on last year’s productivity baselines. (Meta to cut 8,000 jobs on May 20)

The graduate hiring data makes the structural shift tangible at the entry level. Adzuna reported a 34.9% decline in graduate vacancies in the year to March, even as overall job postings rose. Economists remain cautious about attribution, but the direction is consistent: entry-level white-collar roles — the ones where organizations build institutional knowledge and develop the next generation of managers — are taking the first clear structural hit, and the long-term implications for organizational depth and talent pipelines haven’t been seriously reckoned with yet. (Graduate jobs fall by a third as more employers embrace AI)

The compensation story running alongside all of this is equally consequential. A Mercer report found that only about 4% of U.S. employers actually gave equal “peanut butter” raises this year, despite earlier surveys suggesting 44% were considering it. The reason is becoming clearer: AI super-users are outperforming peers at rates that make uniform pay feel inequitable to anyone delivering more. Google has begun incorporating AI usage into software engineer performance reviews, Accenture has made AI fluency a requirement for promotion, and the Writer survey found that AI super-users were three times more likely to have received a raise or promotion in the past year — which means the performance management system is already sorting people by AI capability whether organizations have designed it to or not. (Companies ditch ‘peanut butter’ raises as pay-for-performance takes over)

Share

The Human Infrastructure Nobody Built

An HBR piece introduced the concept of “psychological debt” in AI adoption — six distinct forms of psychological cost that unstructured AI use creates for employees:

• Cognitive - skills atrophying through offloading

• Autonomy - loss of control over how work happens

• Competency - feeling less capable relative to the machine

• Relatedness - diminishing peer connection

• Credibility - perceived loss of professional standing from using AI

• Identity - AI use conflicting with professional self-concept

The survey data accompanying the framework was pointed: employees who use AI rarely reported psychological debt scores of 60, versus 36 for daily users — meaning the people who most need to adopt it are accumulating the most friction against doing so, which is the opposite dynamic of what most organizations are planning for. (The Psychological Costs of Adopting AI)

The skills story runs parallel. DataCamp’s 2026 survey of 500+ enterprise leaders found that 82% offer some form of AI training and 68% say employees have access to learning resources — but only 35% report a mature, organization-wide AI upskilling program. Among those that do, reports of significant AI ROI nearly double, from 21% to 42%. The gap isn’t investment in training — it’s that most AI training is passive, generic, and disconnected from actual workflows, which produces awareness without capability; and organizations keep measuring training completion rates rather than the behavioral change that determines whether any of it lands. (AI Skills Gap in 2026: Why Training Isn’t Enough)

A five-month HBR experiment with 60 managers added the team layer. When groups tried to use AI collaboratively in meetings without any structured approach, the AI defaulted to responding to whoever was typing, not to the group. Teams fell into passive spectator mode within the first session, and the AI effectively narrowed participation rather than widening it. Three deliberate practices reversed this: introducing the team to the AI collectively, assigning the AI multiple rotating roles (challenger, customer, skeptic), and maintaining shared ownership of every prompt rather than letting one person drive. Average team engagement increased 30% after those practices were in place, and two-thirds of participants said their group alignment had improved — which suggests that the ability to use AI productively in team settings is a distinct organizational capability that doesn’t emerge from individual AI literacy alone. (It’s Hard to Use AI as a Team. These 3 Practices Can Help.)

Subscribe now

What Microsoft Is Shipping

(Disclosure: my company, StitchDX, is a Microsoft partner. The coverage below reflects my read of publicly available announcements.)

An IBM study published last week found that 76% of the more than 2,000 organizations surveyed have now established a Chief AI Officer role, up from 26% in 2025. The CNBC piece covering it raised the more interesting question: is the CAIO a permanent C-suite fixture, or a transitional designation created to navigate a specific moment of AI integration that will eventually be absorbed into the CIO, CHRO, or COO? The answer matters because it determines how organizations scope and staff the role — and a transitional designation built for short-term navigation is a different job than a permanent seat responsible for compounding organizational AI capability over time. McKinsey’s framing in the piece — that coordinating AI across a company is more important than any specific title — is probably the more durable principle. (Do you need a chief AI officer? Here’s how the tech is changing boardrooms)

The Microsoft 365 Copilot blog published the companion post to the Work Trend Index, and the concept I found most useful was what it calls the “Transformation Paradox”: 65% of AI users fear falling behind if they don’t adapt, but 45% say it feels safer to focus on current goals than to redesign work with AI. What Microsoft is naming — and what the WTI data underscores — is that the same urgency driving AI adoption is also producing the organizational caution that prevents it from compounding. Resolving that paradox is a leadership task, not a tooling one. The post also announced that Copilot Cowork is now available on iOS and Android, and that the first wave of federated Copilot connectors — including HubSpot, Moody’s, and Notion — are generally available in Microsoft 365. (Microsoft 365 Copilot, human agency, and the opportunity for every organization)

The Copilot Studio April update addressed the governance problem directly. The new Analytics Viewer role separates performance visibility from configuration rights — stakeholders can see how agents are performing without the ability to modify them. The expanded agent usage estimator now forecasts Copilot credit consumption across both Copilot Studio and Dynamics 365 environments, shifting budget management from guesswork to data. Agent 365 is now generally available as the centralized control plane for managing agents across the full Microsoft environment — the governance layer that organizations running agentic workflows at scale have been waiting for. GPT-5.5 Reasoning is also now available in Copilot Studio early-release environments. (What’s new in Copilot Studio: April 2026 updates and features)

Share

On the Bigger Picture

A former Google principal engineer who spent eight years building Google Sheets wrote one of the more clarifying pieces I read last week. His team recently built a working Sheets clone in a few days — not as good as the real thing, but closing fast. His argument: when building an app takes days instead of years, the app itself is worth less. Value is moving away from the interface and toward the data underneath it — and companies that have built defensibility around a front-end experience sitting on top of a database are closing a window faster than most of the people inside those companies want to believe. What replaces it, in his framing, is the “meta-app”: AI tools that generate custom applications on demand, where the user describes intent and the system figures out the rest. The SaaS implications are significant. (I spent 8 years building Google Sheets. Now I think apps are on their way out)

Thinking Machines — Mira Murati’s post-OpenAI startup — previewed a genuinely different class of AI interaction model. Rather than the standard turn-based exchange, their TML-Interaction-Small uses full-duplex architecture that processes 200-millisecond chunks of input and output simultaneously — listening, talking, and seeing at the same time. The turn-taking latency is 0.40 seconds, compared to 1.18 seconds for GPT-realtime. The enterprise implications of sub-second, continuously aware AI — real-time safety monitoring, live translation that feels like conversation, time-aware process management — are significant, but the model is still in limited research preview and hasn’t been tested at production scale. Worth tracking; not yet worth building plans around. (Thinking Machines shows off near-realtime AI voice and video conversation with new ‘interaction models’)

Share BE AI READY

The bottom-line
Organizations are restructuring around AI faster than they’re building the capacity to use it well. That’s showing up in how workforces are being sorted — by compensation, by hiring, by headcount — and along lines drawn in the past eighteen months.

The problem is, the human infrastructure that would make that restructuring work — the psychological readiness, the skills that transfer, the team norms, the governance, the incentive alignment — is lagging… badly. In some organizations, it hasn’t even started.

The uncomfortable implication is that most of the reorganization currently underway is happening in the absence of the thing it requires to succeed. That’s an urgent organizational leadership problem that AI is putting into sharper focus.

That’s it for this week’s BeAIReady brief!

If you appreciate the depth of reporting and how I connect the dots, please like, share this post, and subscribe (or share the Brief with a friend!). Thanks!

~erick

Subscribe now

Share

The April jobs report beat expectations on Friday — 115,000 new positions added, unemployment holding at 4.3%. But the information sector logged its 16th consecutive month of net job losses. Among the tech companies announcing cuts was Cloudflare who let 1,100 workers go, while simultaneously reporting a 600% increase in its own AI usage over three months. And expectations remain that real hourly wages will likely run negative once May’s inflation data arrives.

The dominant thread in last week’s reading wasn’t capability — it was the growing distance between what AI can do for an individual and what it actually takes to operationalize it across an organization. That gap showed up in Microsoft’s research, IBM’s announcements, Gartner’s data on layoff ROI, and most explicitly in the billions OpenAI and Anthropic are now spending to acquire the engineers and consultants who close it.

This week’s coverage:

The 65% - 13% Problem
Employees fear falling behind if they don’t adopt AI. Only 13% are rewarded for it. Three major reports last week landed on the same organizational diagnosis from three different directions.

Copilot Cowork Steps Out of the Chat Window
Microsoft’s Cowork is shifting from answering questions to executing multi-step work autonomously — and for IT leaders managing Copilot deployments, that changes what they’re actually governing.

From “Does This Work?” to “Where Does This Belong?”
The shape of enterprise AI experiments is maturing: the questions are moving from whether AI can do something toward where it fits, what it costs when it’s wrong, and who owns the outcome.

Cutting Staff Isn’t Earning the Return
Gartner found that 80% of billion-dollar firms that cut staff after deploying AI saw no meaningful ROI. Deloitte is restructuring the billable hour. And employees are silently watching AI make mistakes that nobody’s correcting.

The Policy Is There. The Controls Aren’t.
AI governance policies nearly doubled in a year. The actual mechanisms — tested shutdown procedures, vendor vetting, oversight committees — haven’t kept pace.

The Implementation Gap Is Now Official
OpenAI and Anthropic are spending billions to acquire enterprise implementation capacity. What that move signals about the difference between AI for individuals and AI for organizations is the story underneath the story.

Here’s what I was reading.

Subscribe now

The 65% - 13% Problem

Microsoft’s annual Work Trend Index dropped last week. In it was a data point that hasn’t gotten the attention it deserves in the media: 65% of AI users surveyed said they fear falling behind if they don’t adopt AI quickly. Only 13% said their organizations actually reward them for using and experimenting with it. That gap — between how urgently employees feel the pressure to change and how little their organizations have restructured to recognize that change — is what Microsoft is now calling the “Transformation Paradox.” (Microsoft’s new research finds an AI ‘paradox’ holding companies back)

The paradox is structural, not motivational. Workers are already reshaping how they work with AI — 49% of all Copilot interactions analyzed involved cognitive tasks like analysis, problem-solving, and creative work, not just document summarization. A cohort Microsoft calls “Frontier Professionals” — the 16% of AI users who routinely deploy agents for multi-step workflows — report producing work they couldn’t have done a year ago. But only one in four AI users said their leaders are clearly aligned on AI, and organizations where managers actively modeled AI use saw a 17-point increase in perceived value and a 30-point boost in trust in agents. The research makes the case that culture, manager modeling, and talent practices account for more than twice the AI productivity impact of individual factors like mindset or motivation — which means the ceiling on AI ROI is organizational, not individual.

IBM made the same argument from a different angle at Think 2026. CEO Arvind Krishna framed it plainly: the enterprises pulling ahead aren’t deploying more AI — they’re redesigning how their businesses operate. IBM announced a comprehensive AI operating model built on four integrated systems: agent orchestration, real-time AI-ready data foundations, intelligent hybrid cloud management, and built-in governance. The framing treats AI adoption not as a technology procurement decision but as a fundamental operating model change — a distinction that will separate organizations that see returns from those still accumulating spend without accountability for outcomes. (Think 2026: IBM Delivers the Blueprint for the AI Operating Model as the AI Divide Widens)

The World Economic Forum made a similar argument last week, pointing out that AI transformation fails far more often because of organizational design choices rather than limitations of the technology. When companies deploy AI without redesigning work, decision rights blur, accountability erodes, and productivity gains stall. The CHRO’s role — as design architect, capability steward, adoption catalyst, and what the piece calls “transition guardian” — is to own the human transformation that determines whether the technology delivers value at scale or stalls in pilots. “The decisive differentiator will not be access to technology, but the ability to orchestrate human transformation around it.” I find that a useful diagnosis, even if the prescription demands organizational authority that most CHROs don’t yet have. (AI transformation is reshaping work. HR leaders must help redesign it)

Boris Cherny, head of Claude Code, illustrated this point during a CNBC interview last week. Reaching back to a Harvard Business School case study from the early 1990s, he explained why companies with computers weren’t seeing productivity benefits yet — and the answer was that computers were sitting in the corner of the office while workflows, structures, and metrics were still organized around the filing cabinet. Productivity gains arrived only after organizations restructured around the computer as the center. The companies Cherny described as seeing “hundreds of percentage points” of productivity improvement had done exactly that — not added AI to existing workflows, but rebuilt workflows around AI. The analogy is useful not because it’s flattering but because it correctly locates the bottleneck. (Head of Claude Code on the future of work and productivity)

Share

Copilot Cowork Steps Out of the Chat Window

Cowork is expanding from chat-based assistance to autonomous multi-step task execution — now available on iOS and Android, with reusable “skills” that capture and standardize repeatable workflows, new native integrations with Fabric IQ and Dynamics 365 across sales, customer service, and ERP applications, and a connector ecosystem opening to third-party platforms including monday.com, Miro, and LSEG.

The intelligence layer underneath it — what Microsoft calls Work IQ — understands your organization’s data, tools, and workflows, meaning Cowork’s outputs are grounded in your business context rather than public internet information alone. For IT leaders managing Copilot rollouts, this changes what they’re actually deploying. A chat assistant that answers questions sits in one governance lane. An autonomous execution platform that coordinates meetings, conducts research, processes approvals, and generates structured documents across connected enterprise systems sits in a different one entirely. The adoption conversation that was sufficient for Copilot Chat isn’t sufficient for what Cowork is becoming. (Copilot Cowork: From conversation to action across skills, integrations, and devices)

Disclaimer: My company, StitchDX is a Microsoft Partner.

Share BE AI READY

From “Does This Work?” to “Where Does This Belong?”

The shape of enterprise AI experiments is changing — not ending. What’s shifting is the question the experiments are designed to answer. Last year’s experiments mostly asked whether AI could do a thing. The ones I’m watching now ask whether a given AI application belongs in a given workflow, what failure looks like in practice, and who owns the outcome when something goes wrong. That’s a meaningfully different kind of experimentation, and it’s producing more honest conversations about where AI actually fits versus where it was assumed to fit.

AIBusiness captured the shift directly: agents are moving from isolated demos into embedded enterprise workflows, and that transition is forcing organizations into governance and security questions they weren’t facing when agents lived in sandboxes. The infrastructure layer is changing because agents are now persistent, orchestrated, and increasingly autonomous — and that changes the security model, the accountability model, and the risk calculus at the same time. The challenge is no longer proving that the capability exists; it’s figuring out where the capability belongs and what constraints it needs to operate within safely. (Prompt: AI Agents Are Becoming Operational Infrastructure)

Anthropic’s “dreaming” feature for Claude Managed Agents — announced last week at the Code with Claude conference — is a small but directionally significant development. Dreaming is a scheduled process in which recent sessions and memory stores are reviewed across agents, with high-signal patterns, recurring mistakes, and shared preferences identified and retained for future tasks. It addresses a real limitation: context windows are finite, important information gets lost across lengthy multi-agent projects, and single-agent compaction processes can’t see patterns across a broader agent network. The feature is still in research preview and limited in access, but the direction matters — agents that retain organizational memory across sessions represent a meaningfully different infrastructure model than agents that start from scratch each time. (Anthropic’s Claude Managed Agents can now “dream,” sort of)

Pinecone — which built the vector database category and made RAG the standard enterprise AI pattern — used last week to declare RAG a bottleneck and announce a bet on what it’s calling “knowledge compilation.” The argument: traditional RAG forces agents into retrieve-read-retrieve loops that complete only 50-60% of tasks while consuming enormous compute. Pinecone’s Nexus precompiles source data into typed, cited, task-specific artifacts that agents query directly rather than searching raw corpora. The claimed results — task completion above 90%, token spend reduced by 90% — are self-reported and should be validated in production before anyone acts on them. What’s more significant than the specific numbers is what the move signals about where value in the AI stack is heading: from raw retrieval toward pre-structured, curated knowledge that agents can actually work with. For enterprise teams building knowledge architecture, this is the pressure worth planning for. (The company that made RAG mainstream is now betting against it)

Share

Cutting Staff Didn’t Buy the Return

Gartner surveyed 350 global businesses — all with annual revenues above $1 billion, all piloting or deploying intelligent automation — and found that around 80% had cut staff as a result of AI deployment. The ROI from those cuts was largely absent. Companies that reduced their workforces were just as likely to see negative outcomes or marginal gains as they were to generate any meaningful return — and the organizations actually seeing results were investing more in people, not less: building new skills, new roles, and operating models built around humans directing autonomous systems. (AI layoffs backfire as cutting staff doesn’t cut it, firms warned)

Deloitte’s positioning tells a parallel story about what AI is doing to professional services economics. The firm is targeting AI handling 30% of its tasks, growing its managed services division to $1 billion in revenue by 2030, and cutting delivery costs by up to 40% through AI and offshore centers. Clients are already adjusting — some are unilaterally hard-coding 10% AI efficiency discounts into contracts as delivery costs fall. The roles most at risk aren’t entry-level; they’re mid-ranking partners and advisers who have built careers around exactly the kind of assessment and advisory work that AI can now replicate at a fraction of the cost. The takeaway is that the value proposition of senior expertise is being repriced faster than the people who hold it can adapt. The billable hour isn’t dying because junior work is being automated out. (AI to handle 30pc of Deloitte tasks as billable hour dies)

The April jobs data provides the macro frame. The information sector — tech, telecom, data, media — logged its 16th consecutive month of net job losses, with employment in that sector now at its lowest level since March 2021. Goldman Sachs puts the aggregate AI impact at roughly 16,000 net US jobs lost per month — 25,000 displaced by AI substitution against 9,000 created by AI augmentation. The World Economic Forum projects 170 million new jobs created globally by 2030 against 92 million displaced — a net positive that, as one analysis noted last week, doesn’t help much if you’re sitting in one of the displaced roles right now. The problem isn’t the total job count — it’s the mismatch between the roles disappearing and the roles emerging, and the realistic timeline for workers to move between them. (AI Impact on the Job Market in 2026: What the Data Shows)

The Radical Candor report adds a dimension I haven’t seen named as clearly elsewhere. Sixty percent of employees said last week they are afraid to speak up at work — and one of the named drivers is AI inaccuracy. Seventy-three percent of the time, inaccuracies appear in AI-assisted work. More than half of workers and managers say those quality concerns are only sometimes or rarely acted on. The mechanism here is worth naming explicitly: when leadership is laying people off in AI’s name, employees have no incentive to flag the mistakes AI is making — which means organizations are making decisions based on AI output that nobody is correcting. That’s not a feedback problem. It’s a governance problem wearing a feedback problem’s clothes. (New Radical Candor Report Reveals 6 in 10 Employees Are Afraid to Speak Up at Work)

Subscribe now

The Policy Is There. The Controls Aren’t.

ISACA’s 2026 AI Pulse Poll found that 90% of respondents believe employees are using AI in their organization, and 81% say that includes generative AI specifically. The governance picture sitting alongside that adoption data is stark: only 12% of organizations have a documented, regularly tested process for shutting down an AI system when something goes wrong, and 56% of respondents don’t know how long a shutdown would take. Shadow AI — employees using tools outside approved governance channels — is already introducing exposure that most organizations have no tested mechanism to contain when something fails. The risk isn’t hypothetical; it’s a matter of when, not if, a production AI failure demands a response that most organizations haven’t practiced. (The AI Security Gap: Adoption Is Accelerating but Response Capability Is Lagging)

Littler Mendelson’s employer survey adds the HR governance layer. Sixty-eight percent of employers now have formal AI governance policies — up from 38% just a year ago. Littler calls that progress “encouraging” while noting that fewer than half have instituted procedures for vetting third-party AI vendors, tool-specific training, or a designated internal AI oversight committee. The gap isn’t between organizations that care about AI risk and those that don’t — it’s between having a policy document and having operational controls that actually function when they’re needed. A policy that exists on paper but has never been exercised isn’t governance. It’s a liability that hasn’t been discovered yet. (Employers ‘still playing catch-up’ on AI risk management, Littler report finds)

Share BE AI READY

The Implementation Gap Is Now Official

Reuters reported last week that the joint ventures OpenAI and Anthropic have separately formed with private equity are in active acquisition talks targeting AI services firms — engineering and consulting companies that help businesses put AI to work inside their actual systems. OpenAI’s vehicle, The Deployment Company, is raising roughly $4 billion from 19 investors. Anthropic’s is raising $1.5 billion, backed by Blackstone, Hellman & Friedman, and Goldman Sachs. Most of that capital is expected to fund acquisitions of services and consulting firms, not model development. (OpenAI, Anthropic ventures in talks to buy AI services firms, sources say)

The strategic read on this move depends on how closely you’ve been watching enterprise AI play out. If you’ve spent time in the room where organizations actually try to stand AI up — with their real data, their real compliance requirements, their real change management capacity, and a workforce that was never asked whether it wanted any of this — the acquisitions aren’t a surprise. What works frictionlessly for an individual at a laptop does not translate automatically to an organization with siloed data, legacy infrastructure, established approval chains, and employees whose jobs are changing shape whether they agreed to that or not. Enterprise AI requires tailoring to specific data, systems, and workflows, and ongoing adaptation as business needs evolve. The model providers have now officially acknowledged that. (OpenAI, Anthropic expand services push, signaling new phase in enterprise AI race)

The risk embedded in this model is worth watching carefully. Buying AI services from the same company that sells you the model creates a stack that becomes progressively harder to exit — data pipelines, governance frameworks, and workflows all embedded in a single provider’s architecture. As IDC’s Deepika Giri noted last week, avoiding that dependency requires deliberate architecture decisions made early, before the stack is already built around a single vendor. For enterprise leaders evaluating AI vendor relationships right now, the lock-in risk just became significantly more layered than it was six months ago.

Subscribe now

The picture I’ve been watching take shape for a while is finally coming into focus. AI is genuinely useful — remarkably so — for individuals who know how to work with it. The enterprise version of that usefulness is a different project entirely: it requires organizational redesign, governance infrastructure, change management, data architecture, and accountability structures that most organizations haven’t built yet. The Transformation Paradox, Gartner’s layoff data, the ISACA controls gap, and the OpenAI and Anthropic acquisition moves all point at the same thing. The model companies are now spending billions to staff up on the human side of that gap... which tells you everything about how hard the human side actually is.

That’s it for this week’s BeAIReady brief!

If you appreciate the depth of reporting and how I connect the dots, please like, share this post, and subscribe (or share the Brief with a friend!). Thanks!

~erick

Subscribe now

Share

The economic signals last week were telling two different stories at once. The S&P 500 closed Friday at record highs — driven by blowout Big Tech earnings and Wall Street’s confidence in the AI buildout — while the University of Michigan’s Consumer Sentiment Index fell to 49.8, its lowest reading in the survey’s 74-year history, worse than the trough of the 2008 financial crisis; the Strait of Hormuz remained largely closed, oil held above $100 a barrel, and Q1 GDP growth came in well below expectations.

The gap between the equity market and the economic mood is not just a curiosity — it’s the context for almost everything I read last week. The dominant thread running through last week’s reading was the moment when AI’s economic promise and AI’s economic disruption stopped being future-tense arguments and started showing up simultaneously: in Q1 earnings, in corporate headcount decisions, in trial testimony in an Oakland courthouse, and in the job search anxiety of this year’s graduating class. The abstraction is over.

Here’s what I was reading.

Share

The OpenAI Alliance Breaks Open

The news that Microsoft and OpenAI had renegotiated their exclusivity agreement arrived Monday morning, and by Tuesday OpenAI’s models were landing on AWS Bedrock. This was less a rupture than a controlled separation both parties had been engineering for months — and that the architecture of enterprise AI is now genuinely multi-vendor in a way it wasn’t thirty days ago. (Microsoft, OpenAI change terms of deal so startup can court Amazon and others)

Microsoft gave up something it was already losing — exclusivity it couldn’t enforce — and in return extracted real certainty: a guaranteed 20% revenue share through 2030, a non-exclusive license to OpenAI’s IP through 2032, and relief from having to build out data center capacity to meet OpenAI’s exploding infrastructure demands. Barclays called it a positive for both companies — and I agree. But the more interesting question is who else benefits?

The New Stack’s detailed breakdown makes a compelling case for AWS. OpenAI had already been bleeding eastward — the Amazon partnership announced in February, the $50 billion cloud commitment — but formal Bedrock integration changes the calculus for enterprise procurement teams that have been reluctant to mix their AWS environments with Azure-dependent AI services. The disclosure that roughly 45% of Microsoft’s commercial remaining performance obligation was tied to OpenAI underscores how much Azure had come to depend on a single partner — and why loosening that dependency is structurally healthier for Microsoft long-term. What last week established is that the competitive moat in enterprise AI is no longer which cloud a given model lives on; it’s which models your enterprise can access, through which governance frameworks, at what price. (The OpenAI-Microsoft reset, decoded: Why AWS may come out ahead)

In the middle of all this, Microsoft quietly pushed GPT-5.5 Thinking into Copilot Chat, Word, Excel, and PowerPoint — the first public availability of the reasoning-class model in the M365 productivity suite. The headline is the capability lift. The structural signal is that Microsoft is now running OpenAI’s newest model in its productivity layer while simultaneously opening the door for OpenAI to run on competing clouds — an acknowledgment that the competitive moat, if one exists, is not the model but the workflow integration and organizational context built around it. (Available today: GPT-5.5 Thinking and ChatGPT Images 2.0 in Microsoft 365 Copilot)

Subscribe now

The End of All-You-Can-Eat AI

GitHub announced this week that Copilot is moving from request-based billing to usage-based billing on June 1 — introducing AI Credits at $0.01 each, with monthly allotments by plan tier and the option to buy overages. The stated reason is that the current model is financially unsustainable: a quick chat question and a multi-hour autonomous coding session cost GitHub the same in subscription revenue, but wildly different amounts in inference. The comparison The Register reached for was Red Lobster’s Endless Shrimp promotion — and the analogy is uncomfortable primarily because it’s accurate. (Microsoft’s GitHub shifts to metered AI billing amid cost crisis)

GitHub is not alone in this. The Information reported last week that by the end of 2025, 79 of the 500 software companies tracked by analyst Kyle Poyar had begun charging customers additional fees based on AI consumption — more than double the figure in 2024. HubSpot, Adobe, Atlassian, ServiceNow, Salesforce: the list of companies shifting from flat-fee to usage-based or outcome-based pricing is now long enough that the flat-fee model looks like the exception rather than the standard. The honest pressure driving this is that customers on flat subscriptions started actually using the AI features, which raised costs for vendors without raising revenue — a mismatch that was always going to resolve in one direction. The customer quoted in The Information who said “most of my clients hate it — the costs go through the roof really quickly” is describing the reality that enterprise IT leaders are about to walk into at scale. (Atlassian and HubSpot Join Shift From AI Flat Fees)

The management implication buried in this shift isn’t getting enough attention. Organizations that budgeted for AI on a per-seat basis — a predictable, plannable line item — are now facing token consumption curves that are non-deterministic by design. The CFO conversation about AI ROI had been deferred as ‘experimentation’ is about to become unavoidable. The invoices are going to start forcing it. The question of what AI actually costs, measured against what it actually produces, is a billing cycle away.

Share BE AI READY

The Labor Signal Is No Longer Subtle

Microsoft announced last week that it’s offering voluntary buyouts to 7% of its U.S. workforce — more than 8,500 employees, specifically those whose combined age and years of service total 70 or more. The framing is that this is humane: a choice, not a layoff. But the subtext is visible in the arithmetic: Microsoft is investing $145 billion in capital expenditure this fiscal year, and the employees being invited to leave are the ones whose institutional knowledge the company has decided is less strategically valuable than the compute capacity being built in its place. (Here’s why companies like Microsoft are offering voluntary buyouts)

The hiring freeze at the entry level is producing its own reckoning. Junior-level job postings on Indeed fell 7% in 2025, and this year’s graduating class is applying to 150 positions and receiving silence. What’s changed is not just the volume of rejections but the nature of the barrier. There’s a growing collective suspicion among graduating seniors that AI is filtering their applications before human recruiters ever see them — and the data shows they are probably right. (Graduates Reset Ambitions in Pursuit of First Jobs)

The New York Times published what I found to be last week’s most important read — a long investigation into how Silicon Valley is actually thinking about AI’s labor impact. The piece makes clear that the “San Francisco consensus” on what AI does to ordinary workers is, by the admission of the people building AI, bleak. One finding that landed hard for me: when AI company executives say they’re cutting jobs because of AI, “other people feel like they have to too” — and that dynamic could accelerate displacement far faster than efficiency gains alone would dictate. The companies with the most candid internal views about AI-driven job loss are, in several cases, the same ones whose enterprise agent products are the proximate cause of that loss. (Opinion | Silicon Valley Is Bracing for a Permanent Underclass)

A Stanford Leadership Forum panel I watched this week — with economists from Stanford and ADP, alongside Mechanize’s co-founder whose company is explicitly trying to automate knowledge work at scale — added empirical texture to all of this. ADP’s chief economist noted that the firm’s payroll data covering one-fifth of the U.S. workforce shows no broad displacement yet, but that granular data on early-career workers in AI-exposed occupations shows a distinct employment drop since October 2022 — what one cited research paper called “canaries in the coal mine.” The ADP research on upskilling made the point pretty clear: organizations that invest in worker upskilling see employees’ sense of job security increase fivefold — a finding that reframes AI workforce investment from a cost to a strategic lever with measurable retention implications. (Stanford Leadership Forum 2026: Rewiring the Workforce in the Age of AI)

Share

The AI Governance Layer Is Finally Getting Serious

Cybersecurity agencies from the U.S., U.K., Australia, Canada, and New Zealand published joint formal guidance this week on the secure deployment of agentic AI. The document doesn’t create a new security discipline — it argues, persuasively, that agentic AI should be folded into the zero-trust and least-privilege frameworks organizations already maintain. What it adds is specificity: five risk categories (privilege escalation, design and configuration flaws, unintended behavioral risks, structural inter-agent failures, and accountability gaps), a strong emphasis on cryptographically verified agent identities and short-lived credentials, and an explicit requirement that high-impact actions involve human sign-off. The agencies also acknowledged — and this is the part every CIO should read twice — that some risks unique to agentic systems are not yet covered by existing frameworks, and that organizations should “assume agentic AI may behave unexpectedly and plan deployments accordingly, prioritizing resilience and reversibility over efficiency gains.” That kind of calibrated honesty from a government guidance document is unusual, and it signals that the security establishment is taking the agentic layer seriously in a way it wasn’t eighteen months ago. (US government, allies publish guidance on how to safely deploy AI agents)

The Musk v. Altman trial opened in Oakland, and the first week of testimony surfaced revelations more consequential than the headline drama. Musk testified that his own company, xAI, “partly” distills OpenAI’s models to train Grok — prompting audible gasps in the courtroom. OpenAI’s lawyer argued the lawsuit is less about nonprofit governance than competitive sabotage. The judge observed acidly that she suspected there weren’t many people who’d want to put the future of humanity in Musk’s hands either. What the trial is establishing, independent of who prevails, is how loosely the AI industry’s foundational governance commitments were defined from the start — and how much of what was treated as principled agreement was actually a handshake between people who later became competitors. That’s the governance precedent being set here, and it matters well beyond the specific parties involved. (Musk v. Altman week 1)

Subscribe now

On the Bigger Picture

The Q1 earnings from Alphabet and Amazon came with a number that deserved more attention than it received. Nearly half of Alphabet’s record $62.6 billion quarterly profit — about $28.7 billion — came not from search, cloud, or any operating business, but from the company marking up the value of its Anthropic stake after a new funding round set a higher price. Amazon disclosed a similar figure: $16.8 billion in pre-tax gains from Anthropic, more than half of its pre-tax income for the quarter. The accounting is uncontroversial under GAAP. The business signal is worth sitting with: the companies claiming to lead the AI era are booking much of their “AI profit” by investing in Anthropic and then benefiting when their own continued investment pushes Anthropic’s valuation higher — a structure where they can influence the value of the asset they’re marking to market. (Half of Google’s and Amazon’s blowout ‘AI profits’ came from Anthropic)

Meta’s quarter told a version of the same story about AI investment and operational reality diverging. The company lost 20 million daily active users — attributing the decline to internet disruptions tied to the Hormuz conflict — while simultaneously raising its 2026 capex guidance to $125–145 billion and reporting 33% revenue growth. The pattern is becoming familiar across Big Tech: AI is superb for the income statement and complicated for everything else — user engagement, workforce morale, public trust, and the household finances of the customers whose spending the whole system ultimately depends on. (Meta lost 20 million users last quarter)

The Fortune piece on American household margin compression is the one I’d flag as context for all of it. Framed as a P&L analysis of the average U.S. household, it argues that a combination of Hormuz-driven cost increases and AI-driven hiring freezes has compressed household discretionary income by 81% in a single month — producing the consumer sentiment collapse that showed up in the Michigan survey. The companies cutting headcount and freezing hiring to fund their AI buildout are, in aggregate, squeezing the customers whose spending their next phase of growth depends on. That dynamic doesn’t resolve itself. (The American household just took an 81% margin cut)

Two infrastructure-level pieces round out last week’s reading. LlamaIndex’s CEO made the case that the scaffolding era of AI development is over — that as models develop stronger native context reasoning and tool-use, the elaborate orchestration frameworks that defined early agentic development are collapsing, and that the new competitive moat is the quality and modularity of context retrieval, not the orchestration layer above it. For enterprise IT leaders evaluating AI stack investments, this is a real signal: build for context portability and model agnosticism, not for a single orchestration vendor. (The scaffolding era is over. LlamaIndex says context is the new moat) And Replit’s CEO made the case for staying independent as Cursor was reportedly in talks to be acquired by SpaceX for $60 billion — pointing to positive gross margins, 300% net revenue retention, and a fundamentally different customer base of non-technical builders. The consolidation of the AI coding tool market is moving fast, and the question of who controls access for non-technical builders — the actual majority of the future knowledge workforce — is worth watching more carefully than the valuation headlines suggest. (Replit’s Amjad Masad on the Cursor deal, fighting Apple, and why he’d rather not sell)

Share

For me, last week put into stark contrast a moment when the gap between the AI economy and the real economy is becoming impossible to treat as a leadership abstraction. The record equity prices and the all-time-low consumer sentiment aren’t contradictions — they’re two measurements of the same system, taken from different vantage points. Organizations are compressing household discretionary income through AI-driven hiring freezes, building financial statements that book paper gains on private AI stakes as operating profit, and restructuring workforces in ways that are quietly removing the entry rungs from the career ladder.

None of this is irrational at the firm level. All of it is, in aggregate, producing an economy that is holding its breath... waiting to find out whether the productivity gains that were supposed to justify all of it arrive before the social and political costs do.

That’s it for this week’s BeAIReady brief!

If you appreciate the depth of reporting and how I connect the dots, please like, share this post, and subscribe (or share the Brief with a friend!). Thanks!

~erick

Subscribe now

Share

I’ve written before about what AI means for K–12 education — the anxiety in the room when teachers realize their students are already living in a world the curriculum hasn’t caught up to yet.

Higher ed has a different problem. And in some ways, a significantly harder one.

Because the issue isn’t that colleges are failing. Most are doing exactly what they’ve always done — and doing it well. Critical thinking. Research. Writing. Analysis. Communication. The fundamentals of an educated mind.

The issue is that the world those graduates are stepping into has fundamentally changed what it needs from them. And the gap between what a diploma signals and what a business now demands has never been wider.

That gap has a name. And it’s worth being honest about what’s living inside it.

The Jobs Are Gone. Not Shrinking. Gone.

For decades, the implicit deal between colleges and employers was straightforward. Businesses hired recent graduates for task-driven knowledge work — the kind that required literacy, attention to detail, and the ability to follow a process. Research. Filing. Drafting. Reviewing. Organizing. Formatting. Structuring. The unglamorous but essential connective tissue of how organizations operated.

Those jobs were the on-ramp. The place where new graduates learned the business, built context, proved themselves, and eventually moved up.

AI ate the on-ramp.

Not gradually. Not partially. Completely. Researching a topic, drafting a first document, building a summary deck, formatting a report, organizing a database — all of it is now faster, cheaper, and increasingly more reliable when delegated to AI than when assigned to a 22-year-old three months out of school.

This is not a trend. It is not a disruption that will stabilize. It is a permanent restructuring of what entry-level knowledge work looks like — and what it requires.

The floor didn’t just rise. It shifted entirely.

What Businesses Are Actually Asking For

Here’s what I hear when I talk to business leaders — and I talk to a lot of them.

They’re not struggling to find people who can complete tasks. They have AI for that. What they cannot find — and cannot train fast enough — are people who know what to do before the task begins. People who can look at a messy, ambiguous problem, decide what question is actually worth asking, direct AI to help answer it, evaluate what comes back with genuine skepticism, and communicate a decision with clarity and accountability.

That’s not an AI skill. That’s a human skill that AI has made non-negotiable.

The irony is sharp: AI has made the outputs of knowledge work cheaper and faster — while simultaneously raising the bar for the judgment behind them. The work product is easier to produce. The discernment required to know whether it’s right has never been more valuable.

And colleges — through no fault of their own — have not been asked to teach that discernment in the context of an AI-driven business environment. Because… until now, there was no urgency to.

The Real Curriculum Gap

Let me be precise about what I’m not saying.

I’m not saying colleges need to become vocational schools. I’m not saying the liberal arts are obsolete or that the fundamentals need to be replaced. If anything, I strongly believe the opposite is true — the skills that a rigorous college education builds are exactly what the AI economy most desperately needs.

Critical thinking. Synthesis. Written precision. The ability to argue from evidence and know when you’re wrong.

The gap isn’t in the skills. It’s in the scaffolding.

Scaffolding — in the architectural sense — is a temporary structure that lets workers reach places they couldn’t otherwise access. It’s not the building. It’s the bridge between where you are and where you need to be.

That’s what’s missing for college graduates entering the workforce today. The raw materials are there. The foundational skills are real. What doesn’t exist is any structured preparation for how to apply those skills in an environment where AI is changing how organizations think, operate, communicate, and make decisions.

Knowing how to write a strong argumentative essay is excellent preparation for the workforce. Knowing how to evaluate whether an AI-generated business case contains a flawed assumption — that’s the skill that gets you in the room.

Colleges are building the structural foundation. Without the scaffolding, grads are left on the ground floor.

What Scaffolding Actually Looks Like

This isn’t about teaching students to use ChatGPT. Every student already knows how to use ChatGPT. The tool fluency isn’t the problem.

The problem is that no one has taught them how to think alongside these tools in a professional context — how to frame the problem before they prompt, how to interrogate the output before they trust it, how to own the judgment call when the machine can’t make it for them.

Four skills sit at the core of that scaffolding:

Problem framing — the ability to define what actually needs solving before handing it to a machine. AI is extraordinary at answering questions. It is far less good at figuring out which question is worth asking. That still requires a human to guide the process.

Critical evaluation — the discipline to interrogate AI output rather than accept it. To notice when something sounds authoritative but contains a subtle error. To know when the confidence of the answer should make you more suspicious, not less.

Synthesis over retrieval — the capacity to connect ideas across disciplines and arrive at an original insight. AI retrieves. It aggregates. It can even summarize well. AI is remarkably good at making connections across sources. What it is less equipped to do on its own is extend them — to shift the frame, force the alternative, or see the problem from a fundamentally different angle. That kind of synthesis tends to emerge from human interrogation: pushing back on the output, reframing the question, bringing context the model wasn’t given.

Precision communication — the ability to direct AI clearly and communicate judgment calls to stakeholders with accountability. In a world where words are now instructions — where how you prompt determines what you get — the ability to say exactly what you mean has never been more consequential.

These are not new skills. They are the skills a rigorous higher education has always built. What’s new is the context in which they must operate — and the urgency with which they must be applied.

The Unexpected Upside

Here’s what makes this genuinely exciting, rather than just alarming.

The graduates who develop these skills won’t just be better employees. They’ll be the people those organizations most need right now — because contrary to what we hear in the media (shocking, I know) — most businesses haven’t figured out how to deploy AI effectively yet either.

The entry-level knowledge worker who understands how to evaluate where AI can add value, how to identify which processes are ripe for automation, and how to communicate that case to leadership — that person isn’t competing with AI. That person is running it. And they’re worth far more than the task-executor they replaced.

The on-ramp didn’t disappear. It was rebuilt one level higher.

Which means colleges have a genuine opportunity here — not to chase a technology trend, but to do what they’ve always done best: prepare students to navigate a world that is more complex and more demanding than the one that came before it.

The skills are already in the building. The scaffolding just needs to be added.

What I’m Calling For

I don’t believe the answer is a new AI elective buried in the back of the course catalog. That’s a hedge, not a strategy.

What I’m proposing is a curriculum thread — a deliberate, discipline-spanning layer that teaches students how to apply the foundational skills of a college education in an AI-driven professional environment. Not instead of what’s already being taught. On top of it. Scaffolding on the building that already exists.

This thread could begin in freshman writing — teaching students to interrogate AI output the same way they’re taught to interrogate a primary source. It could continue through discipline-specific coursework, where the grade is on the judgment behind the AI, not the output it produced. It could culminate in a senior capstone that asks students to run a real project with AI as a working resource — directing it, evaluating it, and standing behind every decision it supported.

The liberal arts college that does this won’t just be producing graduates who can survive the AI economy. It will be producing the people who shape it.

That is exactly what these institutions have always been for.

The gap between what a diploma delivers and what businesses now demand is real — and it’s widening. But it’s not permanent. The skills are already there. What higher education can provide now is the scaffolding to put them to use. That’s not a disruption to the mission of a college education. It’s the next chapter of it.