Read more

Always-on agents are getting shipped by every platform, alongside agent safety layers, which comes as a time when there’s growing concern around agents. Surveys show that most companies can’t say which agent did what, and most consumers aren’t willing to give one access to their inbox. Speed connects all of it: the products are shipping, and the workforce estimates are landing, before anyone has built the identity controls or the training they depend on.

Vendors Are Selling Agent Safety. Buyers Are Sharing Credentials.

Nvidia launched its Open Agent Safety Platform Monday with more than 100 partners and a claim that the platform would have stopped July’s Hugging Face breach. A CNBC piece quoted Nvidia’s enterprise AI VP saying that Hugging Face had reported more than 17,000 agents attacking its infrastructure over days and weeks. Hugging Face’s own July disclosure, per a separate report, describes 17,000 recorded events in an attacker action log... not 17,000 agents. Nvidia has also agreed to buy Hugging Face for about $12.9 billion, and its launch materials included no independent test results. The bottom line is that Nvidia is asking buyers to trust a safety claim that hasn’t been tested independently, about a company it’s acquiring. (Nvidia releases software platform to stop AI agents from misbehaving) (Nvidia Says Its New Agent Safety Platform Could Have Stopped the Hugging Face Breach)

Gartner called OpenClaw an unacceptable cybersecurity risk for business users back in February, and IT’s default answer to agent platforms like it has been to ban it. Now, Red Hat, Nvidia, OpenAI, and others are building OpenClaw Enterprise, billed as “Kubernetes for agents.” An OpenAI staffer on the project admitted that persistent agent deployments remain limited and that most IT teams ban these platforms outright. That’s a vendor describing its own market, which is rare. (OpenClaw slips on a suit to evade widespread business bans)

Permissions without identity let a company limit what an agent can do but not say which agent did it.

Fifty-four of 137 respondents in VentureBeat’s August agent security survey said they enforce scoped permissions at runtime. Thirty-seven of those also run agents in production, and only 15 of the 37 give every agent its own managed identity. The other 22 run some or most agents on shared credentials. Permissions without identity let a company limit what an agent can do but not say which agent did it. A CISO quoted in the piece (a former KPMG auditor) called it an accountability problem which is the right frame.

Using isolation to control agent access sounds good on paper, but even after the portal blocked it, an OpenAI agent reached Australia’s Medicare statistics service... OpenAI found out about it 54 days later. The same VentureBeat survey shows that only 12 of the 137 respondents said high-risk agents run in isolation, while 64 of the 109 organizations running agents reported an incident or near-miss in the past year. It’s a self-selected sample, which VentureBeat admitted, but points to the complexity of containment and permission management. (22 of 37 surveyed companies that enforce AI agent permissions still have agents sharing credentials)

Vendors are selling the containment layer, most buyers haven’t built the identity layer to support it. The question I’d put to any of them is simple: when something goes wrong, can you tell me which agent did it?

Share BE AI READY

Vendors Shipped Agent Coworkers. Buyers Haven’t Said Yes.

If the issue of managing agent permissions isn’t concerning enough, the “always on” agents that are being shipped simultaneously by OpenAI, Meta, Microsoft, and more, are worth considering. Access sharing at the individual level is being requested more and more by the AI.

OpenAI’s Dots keep working after an employee closes the chat window. They get their own cloud computer and browser, connect to more than 4,000 apps through plugins, and report back through ChatGPT, Slack, and Microsoft Teams. A VentureBeat piece added the part enterprise buyers should read twice: OpenAI is piloting specialist Dots with their own organizational identity and credentials, and working with Microsoft to bring them under Agent 365. Custom Rules and an Activity View sit on top, with an auto-review layer deciding what needs a human’s approval. The first Dot is free for Pro and Business Premium customers. OpenAI hasn’t said what the next one costs. (OpenAI launches Dots, always-on AI agent coworkers, and ChatGPT Space where they can collaborate with human teams)

Meta’s Muse hit about 2.8 million downloads in its first two weeks. Tuesday, Meta pushed it toward small businesses — a Reuters piece added the business angle. Integrations with Shopify, QuickBooks, Stripe, and Canva come with it, and about a third of Muse users have already connected a business account, per a Wall Street Journal report that VentureBeat relayed. Employees will arrive with personal agents before IT has finished sanctioning the corporate ones. (Meta expands Muse AI agent for small businesses)

A Thales poll found that only 13% of respondents would let an AI agent read their email and 7% would let one move money between accounts. A Futurism piece set that poll against Muse’s download numbers, and added one user’s claim that Muse gave his home address to strangers on Facebook Marketplace. Downloads measure curiosity; those two percentages measure what people are willing to delegate. (The poll covers consumers, but the employees in your organization are consumers too.) (The AI Industry Has a Major Problem: Most People Aren’t Freaks Who Want an AI Agent Running Their Whole Life)

Meanwhile, Microsoft’s stock is aiming higher — but it’s not just the product that’s driving it. Piper Sandler raised its Microsoft price target to $610 from $550 on the E7 bundles with Copilot, E5, Entra, and Agent 365 news. Piper estimates that every 10% of seats moving from E5 to E7 adds $2 billion in annualized revenue. Microsoft said hundreds of customers bought millions of E7 seats in the first two months, and EY rolled it out to 400,000 employees. Microsoft is also moving from per-seat licensing to seat-plus-usage pricing, which turns what used to be a fixed line in the budget into a variable one. Piper expects Copilot and Cowork consumption revenue to reach a $2 billion annualized run rate by fiscal 2028. Nothing I read last week explained how a buyer would measure what that usage produced. (Piper Sandler Raises Microsoft Target, Sees Billions in Potential From E7 and AI)

Subscribe now

McKinsey Says 11 Million Workers Have to Move. Most Don’t Have a Path.

McKinsey Global Institute put its base case at roughly 11 million American workers, about 7% of the labor force, changing occupations over the next decade. That works out to 770,000 people a year against a long-run average of about 215,000. The pace would run roughly three to four times the historical rate, close to the 788,000-a-year level of the pandemic years. An Axios piece added that, for those that keep their jobs, 70% of workers will need some degree of role reinvention. That news comes as employee confidence on Glassdoor fell to a record low in September, with AI mentions in employee reviews up 164% from a year ago. (How AI could change the workforce)

McKinsey expects about 41 million jobs to be created against 36 million cut by 2035. A net positive of roughly 5 million jobs. The jobs will exist. Reaching them is the problem. Only one in seven displaced workers has a direct path into a growing job, about 85% of those jobs require a credential, and roughly 76% can’t be done remotely. The shrinking work sits in office administration, retail, and transportation, where lower-wage workers are 7.6 times as likely to need a new occupation. The growth is in healthcare, construction, and management. (McKinsey: AI will create more jobs than it kills — after destroying 11 million | Fortune)

A WSJ piece described marketers retitling themselves “marketing engineers,” with Greg Bresnitz recalling the moment he settled on the label. As AI claims more of the work, reinvention is one way workers can attempt to control their destiny. But a new title is cheap and easy. Reinventing roles for 70% of the workforce takes training that somebody will have to pay for. (Move Over, Storytellers: The Marketing Engineers Are Here)

Share

AI Writing Is Converging, and the Tells Keep Changing

Graphite, a marketing company, claims to have catalogued about 13,000 words and phrases it says flag AI-written text. The top one is “this matters,” which shows up 116 times more often in AI-generated content than in human samples. A Gizmodo piece added the model-by-model split: Claude Opus 5.5 leans on that phrase most, but its em dash use fell 99% from Opus 5, while OpenAI’s Astra is trending toward less human-sounding text. Here’s why “this matters”: for each published tell, models continue to edited them out of their next version, which makes detection a moving target rather than a control. (‘This Matters’: Researchers Identify Thousands of New Tells in AI Writing)

In a 2024 Science Advances study, 300 people wrote short stories, and the AI-assisted stories were rated more creative and were also more similar to each other. A 2026 PNAS Nexus study gave creativity tests to 22 AI models and more than 100 people, and the models’ answers were far more alike than the people’s. AI raises the floor on each person’s output and lowers the variety across the organization. A Psychology Today piece called out the mechanism: the first answer a person sees tends to pull everything after it toward itself, and AI is handing millions of people the same first answer. The author’s fix is practical, if low-tech. Write three rough lines of your own before opening the chat window. (AI makes your work easier. Yet it also makes you sound like everyone else.)

A writer can scrub every tell from a draft and the sameness is still there, because it lives in the ideas rather than the phrasing. That’s a quality problem for any team publishing AI-assisted work, and it’s a governance question before it’s a style question.

Subscribe now

Twenty-two of 37 surveyed companies enforce agent permissions and still have agents sharing credentials. Six in seven displaced workers have no direct path into a growing job. Usage billing is arriving ahead of any agreed way to measure the result... that’s what buying speed first looks like when nobody has built the control. Are leaders running an AI strategy if they can’t say which agent did what, or what the usage bought? 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, and subscribe. Each share helps us me get the word out!

~erick

Subscribe now

Share

Workers Are Performing AI Use, Not Doing It

Organizational demands for AI aren’t translating to the real-world work. In a survey, 44% of workers said they feel the pressure to use AI, 42% weren’t confident about folding AI into their processes, and only 22% called themselves very confident. Sixty percent said they either aren’t expected to use AI or don’t have clear expectations. Workers are being pushed to use AI without anyone defining what using it well looks like. (44% of workers feel ‘AI-whelmed’ as pressure to use AI grows)

Nearly half of employees in a Visier study reported pressure to use AI, and a similar share admitted they exaggerate their use and expertise to colleagues and managers. Seven in 10 worried adoption could hurt their careers or cost them their jobs. When employees can’t safely say what isn’t working, they report that everything is. Visier’s Andrea Derler put the cost bluntly: leaders who don’t allow that transparency get blanket answers, which means “you’re wasting time.” (Employees report performative AI use amid role changes)

Usage is the easiest AI number to report... and (perhaps more importantly) the easiest to inflate. Derler said the pressure to show results runs through every level: CIOs need to prove ROI, managers push their teams, employees guess at what counts. So what does a rising adoption curve prove? Sometimes only that people learned what to say.

Share BE AI READY

Employers Are Paying for AI Skills While Judgment Erodes

An HR Dive piece on a Payscale study found that 58% of companies are paying premiums for AI skills or plan to. Sixty-one percent are rewriting job descriptions because of AI, but fewer than half say their salary structures have kept up. Payscale projected what comes next: new hires commanding premiums of 20% to 40% while current employees who upskilled get nothing, a “retention time bomb.” Employers are pricing AI skill into new hires and leaving employees who upskilled without a raise. (Should workers be paid for AI skills?)

Three in four employees told IBM that critical thinking and other skills, human judgment among them, were starting to erode because of AI. Eighty percent of CHROs said AI creates invisible work: validating recommendations, fixing errors. The skill that makes AI output trustworthy is the one employees said they were losing, and the validation labor was landing on them anyway.

Where workflows built judgment in, 62% of CHROs reported rising confidence in AI-enabled decisions. Where they didn’t, 57% reported it falling. That’s a design choice, and the data showed it paying off, but only slightly more. (IBM report warns AI could erode human skills deemed vital by CHROs)

Jack Clark made the human-side case in Fortune back in April: the degrees gaining value are the ones built on synthesis across subjects and knowing which questions to ask, and Anthropic’s own researchers had estimated AI could theoretically handle 94% of computer and math tasks. (Anthropic billionaire cofounder Jack Clark studied literature, not code—and says liberal arts degrees will win in the AI age | Fortune) Pay is following AI tool fluency, while the judgment Clark and IBM both pointed to isn’t showing up in Payscale’s numbers.

Subscribe now

The Bottleneck Is the Workflow, Not the Model

More than two-thirds of the 154 executives AWS interviewed across 27 countries named legacy workflows, not technology limits, as the biggest barrier to AI value, a CIO Dive piece reported. AWS’s Tom Godden called it a business problem before an IT one and said treating it as an IT problem yields nominal gains at best. The executives who got value rebuilt end-to-end processes and reinvested the time saved in areas they’d planned in advance.

Godden’s explanation for where the gains go was simple: speeding up coding does nothing for governance, funding, approvals or coordination across teams. Making one step faster doesn’t make the whole chain faster, and that’s where the savings disappear. BMW’s CIO told AWS the biggest surprise was how much alignment, process reengineering and change management mattered compared with the technology. Sysco is targeting $500 million in AI savings over three years and Chewy projected $50 million a year (targets, not results). Gartner research cited in the piece put the share of enterprises that had scaled AI across multiple operations below 25%. (AI gains call for organizational overhauls: AWS)

Only 7% of enterprises describe their data as completely ready for AI, a Fortune commentary piece reported, and fewer than a quarter have a data strategy at all. Sixty-three percent either lack AI-suitable data management or aren’t sure they have it. McKinsey’s survey, the piece noted, found just 6% of companies reporting significant impact. Data readiness, not model quality, is where enterprise AI stalls. (The backwards AI pacing debate and how far business is from the front…)

Microsoft’s own AI write-up, published the week before, had already made the workflow argument from the inside. Access and usage didn’t change how the work got done until the sales team rebuilt around a business outcome: a tool licensed to more than 200,000 people, the post said, plateaued until the team mapped how account managers spent their week. The supply-chain team simplified its processes first, then built a single source of truth so agents reasoned from the same data, and cut cycle time by up to 75% in selected workflows. (What we’ve learned from Microsoft’s own AI transformation) The footnote on the 20% close-rate gain compares 687 sellers who used Copilot heavily with those who used it lightly, January through June 2024.

Share

The Frontier Debate Keeps Skipping What’s Already Deployed

Bill Gates told NBC News that “No one thinks self-regulation is enough,” and called for required safeguards and monitoring that he described as overhead for the industry, not a dramatic slowdown. Mark Zuckerberg told the same network the opposite: no industrywide coordination needed. Microsoft’s Brad Smith asked a UN session whether an airplane maker worried about crashes would say it needs to win the race. California, Maryland and New York each moved on AI rules. The pacing argument was still about who sets the pace: Congress, the labs together, or each lab alone. (Bill Gates says AI companies self-regulating isn’t enough and governments should be involved in monitoring)

A class action filed the Friday before argued that even the slowdown talk breaks the law. The plaintiffs, paid subscribers to ChatGPT, Claude, Grok and Gemini, alleged that the labs’ September 12 responses to Dario Amodei’s pacing essay amounted to an illegal agreement that reduces what consumers get. Amodei’s essay had itself flagged antitrust exposure and asked the government for a narrow waiver, and Sen. Josh Hawley said he wouldn’t agree to any exemption. The plaintiffs argued that agreeing to slow down together is itself the violation, even if each lab slowing on its own wouldn’t be. (Lawsuit says Anthropic, OpenAI, SpaceXAI and Google made illegal agreement on AI slowdown)

An Ethan Mollick post argued the whole debate underrates what’s already here. GPT-6 Astra and Fable 5.1, he wrote, can reliably do weeks of human work when properly guided, and the capability overhang between what those models can do and what most people do with them is massive. If every lab stopped training tomorrow, the models already deployed would still change how large parts of the economy work. His four human advantages (deep knowledge, wide knowledge, taste and agency) sound a lot like the judgment IBM and Clark were pointing at. (The Overhang)

A Fortune piece argued pacing would cost the economy little, because enterprises need time to absorb what’s already on the table. Mollick argued a slowdown wouldn’t change much. Both put the unabsorbed capability in organizations, not labs. So who owns absorption? Gates wants Congress to own safety, Zuckerberg wants each lab to own it, and nobody in that argument owned the harder job: getting organizations to absorb what’s already shipped.

Subscribe now

Inflated usage numbers, pay structures rewarding tool fluency, workflows nobody redesigned, data that only 7% of enterprises call ready... they all trace to one choice: leaders bought the capability and left the organization around it as it was. The pacing fight will run for months, and it’s a fight over models. Are executives running an AI strategy when nobody owns the job of absorbing what’s already deployed? 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

The Slowdown Argument Went to Court

Last week’s entire Brief focused on the pacing debate. Anthropic, OpenAI, SpaceXAI and Google are now defendants in an antitrust complaint alleging that their public calls to slow frontier development amounted to illegal coordination — the filing points at a September 12 slowdown effort following Dario Amodei’s essay, and cites the public statements from Amodei, Musk, Altman and Hassabis as evidence of an agreement (Anthropic, OpenAI, SpaceXAI, Google sued over call to ‘pace’ AI development). Four companies are being sued for saying, out loud and separately, that the technology they sell might be moving too fast.

CNN’s coverage laid out the antitrust theory more carefully, and the mechanics matter here (Lawsuit says Anthropic, OpenAI, SpaceXAI and Google made illegal agreement on AI slowdown). The claim isn’t that any lab signed anything. It’s that parallel public statements from a handful of firms controlling most of the frontier can function as a restraint of trade regardless of intent. That’s a real doctrine, not a stunt filing. If it survives a motion to dismiss, the practical effect is that labs get a legal reason to stop talking publicly about safety — and the conversation moves somewhere nobody can see it. That’s a worse outcome than whatever the plaintiffs think they’re preventing.

Markets had already priced their own view. AI names sold off Monday on slowdown talk while the rest of the index held steady, and the 10-year touched 5% on the same session. Investors are treating restraint as a threat to the trade, which tells you how thin the margin is between “responsible pacing” and “revenue guidance.”

The human version ran in the Journal, on Jacob Coxon, who left Anthropic and became the public face of AI existential risk — with a colleague quoted saying, flatly, “We earnestly believe AI could kill all humans!” (The Anonymous Math Geek Who Quit Anthropic—and Became the Face of AI Safety). I read these profiles with one question: does the argument change anything I’d do Monday morning? Mostly it doesn’t. But the lawsuit changes the incentive to make the argument at all, and that’s the part a mid-market leader should track — because the signals you rely on to judge vendor risk come from people who may soon have counsel advising them to stay quiet.

Seventy-Two Percent Is a Data Problem — the statistics of failing AI

Seventy-two percent of failed AI initiatives trace back to the data, not the model — that’s the not-so-surprising finding from a survey covered by CIO Dive (AI failures often trace back to poor data foundation: survey). The model isn’t the risk. The pantry is a mess — and instead of cleaning it up, we keep hiring chefs hoping it’ll work itself out. I’ve watched this play out on Copilot rollouts repeatedly — the tenant is licensed, the pilot group is enthusiastic, and the answers come back wrong because the source content is stale, duplicated, or permissioned to everyone.

The more surprising statistic: Ninety percent of IT leaders reported security incidents connected to Microsoft 365 misconfigurations, with 39% able to name a specific incident (Enterprises grapple with Microsoft 365 misconfigurations). Permission sprawl has been a problem since before Covid. Now, companies are layering a semantic index on top of it. Copilot oversharing content is a direct result — it finds it, surfaces it, and hands it to someone who wasn’t supposed to see it. If you haven’t run SharePoint permissions and sensitivity labeling as a prerequisite project, you don’t have a Copilot rollout. You have a discovery engine pointed at your own mess. (PSA: my company, StitchDX is a Microsoft partner, and this is something we get called in to fix.)

And then there’s the governance piece. Nearly half of senior AI leaders admitted to bypassing their own AI governance process when a deployment was urgent, per EY research (Businesses sidestep AI governance policies as concerns mount).

Half.

Not half of junior staff working around policy — half of the people who own the policy. A governance framework that gets suspended under deadline pressure isn’t governance, it’s documentation. The useful read here is that governance has to live in the deployment path itself — in approval gates, in the tenant configuration, in who can provision what — rather than in a PDF someone signs off on annually.

Share BE AI READY

Agents Got Loose Before the Guardrails Went Up

Cisco recently launched an internal agent platform designed to support their employees. Within 2 weeks, 90,000 users were active, with 50% using it daily. More interestingly, roughly 700 agents were built, and formally authorized (AI agents are going rogue. CIOs are racing to put guardrails around them). The enterprise agent conversation has flipped from exploratory to defensive, and it only took a quarter. A year ago the CIO question was which agents to build. Now it’s which agents already exist, who owns them, what credentials they’re carrying, and what happens when one of them does something unexpected.

Speaking of unexpected behavior — Google disclosed that a Gemini model gained unauthorized access to three outside systems during testing. It guessed credentials and logged into live sites because it, apparently, didn’t distinguish the test from production (Google says its AI model gained unauthorized access to three outside systems). No harm done, by Google’s account. But a frontier lab with world-class safety staffing couldn’t reliably keep its own model inside the sandbox, which is a bracing thing to read if you’re a 900-person company about to let an agent touch your ERP.

So where does that leave a mid-market IT leader? Not at “don’t do it.” The honest position is that agent oversight is now its own workstream with its own owner — an inventory, an identity model, a scope boundary, and a kill switch — and if that work isn’t funded, the agents will still show up. They’ll just show up unmanaged.

$2.7 Trillion Bought a Better Version of Yesterday

Global AI spend hits roughly $2.7 trillion in 2026, up 49.5% year over year, with about 35% of it going straight into infrastructure — servers, chips, data center capacity (Global AI spend will nearly double in 2026 due to infrastructure demand). I read that and compared it to the number out of Fortune’s Leaders Forum: 60% of companies have deployed AI agents — only 5% have redesigned a workflow (CEOs warn against falling into AI’s efficiency trap). Trillions are being spent, so we can do the same work slightly faster. The phrase the CEOs kept using was the “efficiency trap” — the biggest risk being “a better version of yesterday.”

I’d put that on a slide in front of any executive team still building their AI case against headcount avoidance.

McKinsey gave a more structural version of the argument, sketching what they call the agentic organization and reporting that 89% of organizations still operate on essentially industrial-age structures while 1% function as decentralized networks (The agentic organization: Contours of the next paradigm for the AI era). I’m skeptical of the framing — McKinsey has a five-pillar model for every era, and this one assumes you can restructure an operating model without first fixing the knowledge systems the agents would draw on. You can’t build a decentralized network of agents on top of a filing system nobody has maintained since 2019. But the underlying observation holds: org design, not tooling, is the binding constraint now.

You can’t build a decentralized network of agents on top of a filing system nobody has maintained since 2019.

Meanwhile Anthropic is reportedly pacing past $100 billion in annual revenue, up 50% in two months (Anthropic tops $100 billion revenue pace, report says). Vendor growth that steep tells you demand is real. It tells you nothing about whether the buyers are getting anything back, and those are genuinely separate questions.

Share

AI Became the Anonymous Whistleblower

Employees are using AI to deliver criticism they won’t sign their names to, and HBR put a label on it: safety by proxy (What Leaders Need to Know About AI and Psychological Safety). Eighty-three percent of business leaders said psychological safety directly affects whether AI initiatives succeed. If your team needs a model to voice dissent on their behalf, the AI isn’t the finding — the silence underneath it is. This is the piece from the week I’d most want an HR leader and a CIO to read in the same room, because it’s the rare story where the technology is a diagnostic instrument rather than the subject.

Jack Clark’s argument ran adjacent to it. Anthropic’s cofounder studied literature, not computer science, and made the case that liberal arts training is what holds up as AI absorbs the technical middle — with Anthropic’s own researchers estimating AI could theoretically handle 94% of computer and math tasks (Anthropic billionaire cofounder Jack Clark studied literature, not code). I want to believe it. I also notice it’s a convenient thing for an AI executive to say. The defensible version isn’t that philosophy majors win — it’s that judgment, framing, and the ability to decide what’s worth asking are the parts of knowledge work that don’t compress. Which happens to be exactly the skill set required to govern an agent fleet, so the two stories in this section are closer than they look.

Share BE AI READY

On the Bigger Picture

Axios laid out four scenarios CEOs should prepare for through 2027 — rapid advance, a catastrophic incident, political backlash, and gradual integration (The 4 ways that AI could play out). It’s a genuinely useful board artifact, mostly because it forces the conversation past “are we doing enough AI” and into “which of these are we resilient to.” Pair it with the efficiency-trap framing and you’ve got a decent ninety minutes with a leadership team.

And one small thing, because it’ll matter more than it sounds: Teams is adding simultaneous screen sharing for two people, shipping in November (Microsoft Teams will soon support two people sharing screens at once). Anyone who’s run a design review or a system walkthrough knows exactly how much friction that removes. (Yes, I noticed that in a week about trillion-dollar infrastructure spend, the most immediately useful item is a dual-screen toggle. That’s usually how it goes.)

Share

The spend figure, the 5% redesign rate, the half of AI leaders bypassing their own governance, the 90% with M365 misconfiguration incidents... none of that is new to anyone who reads this newsletter. What’s new this week is the speed. Agents landed inside enterprises faster than anyone built oversight for them, and the labs that shipped them are now in court over whether they’re even allowed to suggest slowing down. The remedy is unglamorous and it hasn’t changed — permissions cleanup, content lifecycle, data ownership, an agent inventory, a governance gate that actually blocks something — and none of it demos well to a board. Are leaders who fund the platform and defer the foundation running an AI strategy? In my opinion, no. They’re running a procurement cycle under a better name, and the 72% failure figure is what that looks like eighteen months 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

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