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

The ROI Isn’t Missing — the Org Is

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

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

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

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

Subscribe now

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

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

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

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

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

Share

The Human Infrastructure Nobody Built

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

• Cognitive - skills atrophying through offloading

• Autonomy - loss of control over how work happens

• Competency - feeling less capable relative to the machine

• Relatedness - diminishing peer connection

• Credibility - perceived loss of professional standing from using AI

• Identity - AI use conflicting with professional self-concept

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

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

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

Subscribe now

What Microsoft Is Shipping

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

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

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

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

Share

On the Bigger Picture

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

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

Share BE AI READY

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

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

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

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

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

~erick

Subscribe now

Share

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

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

This week’s coverage:

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

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

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

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

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

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

Here’s what I was reading.

Subscribe now

The 65% - 13% Problem

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

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

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

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

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

Share

Copilot Cowork Steps Out of the Chat Window

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

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

Disclaimer: My company, StitchDX is a Microsoft Partner.

Share BE AI READY

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

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

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

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

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

Share

Cutting Staff Didn’t Buy the Return

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

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

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

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

Subscribe now

The Policy Is There. The Controls Aren’t.

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

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

Share BE AI READY

The Implementation Gap Is Now Official

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

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

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

Subscribe now

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

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

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

~erick

Subscribe now

Share

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

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

Here’s what I was reading.

Share

The OpenAI Alliance Breaks Open

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

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

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

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

Subscribe now

The End of All-You-Can-Eat AI

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

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

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

Share BE AI READY

The Labor Signal Is No Longer Subtle

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

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

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

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

Share

The AI Governance Layer Is Finally Getting Serious

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

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

Subscribe now

On the Bigger Picture

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

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

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

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

Share

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

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

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

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

~erick

Subscribe now

Share

It seems two things are happening at once: the broader economy is tightening, and the biggest technology companies are spending faster than ever on AI. That paradox ran through nearly everything I read last week — from boardrooms replacing their CEOs to private equity firms writing nine-figure checks to force AI into portfolio companies. The pressure to act on AI is intensifying even as the evidence that it’s working at scale remains thin.

Here’s what I was reading.

This week’s coverage:

The Leaders Who Can’t Wait and the Leaders Who Won’t Stay
Boards are replacing CEOs for not moving fast enough on AI — even as 90% of executives say AI hasn’t changed their operations at all.

The Workforce Is Being Restructured, and So Is Its Data
Microsoft and Meta cut tens of thousands of workers while spending hundreds of billions on AI — and those workers’ Slack messages and emails may end up as training data.

The End of the Software License and Who’s Coming to Replace It
A new HBR framework says the era of standardized enterprise software is ending — and a massive private equity play shows who’s planning to profit from what replaces it.

The Platform Wars Go Private and Agentic
Google Cloud Next ‘26 declared the agentic era with 260 announcements; the real story is that enterprise AI infrastructure is moving out of public clouds and into private, controlled environments.

On the Bigger Picture
AI is finding security bugs in Firefox at scale, GPT-5.5 is already outperforming GPT-5.4, and the Justice Department can’t quite decide what it thinks about Anthropic.

Here’s what I was reading.

The Leaders Who Can’t Wait and the Leaders Who Won’t Stay

Last week produced another round of high-profile CEO departures, and the pattern is hard to miss. In 2025, companies in the S&P 1500 named 168 new CEOs — the highest total in more than 15 years. Adobe’s longtime CEO stepped down after 18 years under investor pressure to deliver on AI. At Walmart, Doug McMillon cited the urgency of AI transformation as part of why he stepped aside. Now Tim Cook is handing Apple to John Ternus. (The AI era is turning Corporate America into a CEO churn machine)

The core tension here: boards are replacing leaders for not moving fast enough on AI, even though the evidence that AI is actually delivering results remains remarkably thin. A survey of 6,000 executives cited in Fortune last week found that 90% say AI has had no impact on employment or productivity over the past three years — yet those same executives forecast it will increase productivity by 1.5% over the next four years. Boards aren’t firing people because AI isn’t working. They’re firing them because they’re not performing AI fast enough in front of investors who believe it should already be working. (Tim Cook’s exit is part of a CEO reckoning sweeping Corporate America)

There’s a useful distinction in the Fortune piece worth carrying into your own organization: transformation is not a turnaround. In a turnaround, you bring in an outsider to blow things up. In a transformation, you want to accelerate change without destroying what you’ve built. The companies making the most visible CEO moves last week — Apple, Walmart, Coca-Cola — are handing the wheel to insiders who know the business. The bet isn’t on a new vision; it’s on someone who can execute the existing one faster. If you’re an IT or business leader watching this, the takeaway isn’t about hiring. It’s about velocity: how quickly can you demonstrate measurable AI progress to whoever is watching your work?

Subscribe now

The Workforce Is Being Restructured, and So Is Its Data

Meta confirmed last week it will cut roughly 8,000 employees — about 10% of its workforce — while closing 6,000 open roles and spending between $115B and $135B on AI this year. The same week, Microsoft announced voluntary buyouts for about 8,000 employees, targeting those whose age plus years of service equals 70 or more. Microsoft’s CEO has said AI already writes 30% of the company’s code. Its AI chief said AI will be able to replace most white-collar work within 12 to 18 months. Block, Amazon, and Oracle have made similar moves in recent months. (Microsoft and Meta announce large staff reductions as they spend big on AI)

The math being presented here is direct: AI spend goes up, headcount goes down. The productivity argument makes sense on paper. What the quarterly earnings presentations don’t include is the operational risk of moving this fast — the institutional knowledge that walks out the door, the morale impact on people who remain, or the technical debt that accumulates when AI-generated code replaces engineers who understood why decisions were made.

There’s a darker layer to this story that got less attention last week. A Forbes piece revealed that a startup called SimpleClosure is helping defunct companies sell their internal digital footprints — Slack archives, emails, Jira tickets, code repositories — to AI labs as training data for agents. The demand, according to their CEO, is “insane.” A competitor called Sunset is in the same business. The implication is striking: the workplace communications of companies that didn’t survive are becoming the raw material for AI agents designed to do that work in the future. The privacy questions are significant — employees didn’t consent to their messages being repurposed — and regulatory scrutiny is beginning. (AI’s New Training Data: Your Old Work Slacks And Emails)

For organizations building AI adoption strategies, this is worth pausing on. The data your organization generates every day — how people communicate, how decisions get made, what questions get asked — is increasingly what makes AI systems valuable. How you govern that data, and who has rights to it, isn’t just a legal department concern anymore. It’s a strategic one.

Share

The End of the Software License and Who’s Coming to Replace It

HBR published a piece last week that named something I’ve been watching from my own work with clients: the economic logic that made standardized enterprise software the default choice is breaking down. Enterprise spending on generative AI applications jumped from $1.7 billion in 2023 to $37 billion in 2025. At the same time, public SaaS valuations have compressed sharply, with many leading vendors trading 30 to 60% below their 2021 peaks. The framework the piece proposes gives organizations four paths forward: build your own AI-driven systems, configure flexible platforms, collaborate with vendors to create tailored solutions, or simply buy the outcome and let someone else run it. The strategic question every IT and business leader now faces is which workflows genuinely need to be owned, and which can be delegated. (The End of One-Size-Fits-All Enterprise Software)

This isn’t just theoretical. Private equity figured out the same thing — and made a $5.5 billion bet on it. The Financial Times reported last week that OpenAI is in talks to invest $1.5 billion in a joint venture called DeployCo, alongside TPG, Bain Capital, Advent International, and Brookfield, which would contribute another $4 billion. The venture’s job: send “forward-deployed engineers” armed with OpenAI’s tools into portfolio companies to drive AI adoption and boost margins. Anthropic is in parallel talks with Blackstone, Hellman & Friedman, and General Atlantic for essentially the same model. (Private equity courts OpenAI and Anthropic)

The forward-deployed engineer model isn’t new — Palantir has used it for years. What’s new is the scale and the urgency. For organizations still figuring out where to start with AI, this is a clear signal: the companies that will profit most from AI adoption are betting on embedding themselves directly in your operations, not selling you a license and walking away. If you don’t have your own AI strategy and roadmap, someone else will hand you one.

Share BE AI READY

The Platform Wars Go Private and Agentic

Google Cloud Next ‘26 took place in Las Vegas last week and was substantial. Google announced 260 updates over the course of the event. The headline was the Gemini Enterprise Agent Platform — a full-stack system for building, deploying, governing, and running AI agents at scale — alongside a new eighth-generation TPU split into two specialized chips, one for training and one for inference. Google also announced a $750 million fund to help its 120,000-member partner ecosystem build and deploy agents. Seventy-five percent of Google Cloud customers are already using its AI products; the pitch is that the next competitive battleground isn’t compute access, it’s which platform becomes the operating system for your agent workforce. (Welcome to Google Cloud Next ‘26)

A separate story last week illustrated where this is heading for regulated industries. A company called Cirrascale — working with Google — is now offering Gemini as a fully private, air-gapped appliance that runs on a single server inside a customer’s own facility. The model lives entirely in volatile memory: cut the power, and it’s gone — no data ever leaves, no model weights ever persist on disk. For organizations in financial services, healthcare, or government that have been sitting on the AI sidelines because of data sovereignty or compliance requirements, this changes the calculus. The binary choice between “use the best AI and expose your data” versus “host an inferior open-source model and keep control” is starting to close. (Google’s Gemini can now run on a single air-gapped server — and vanish when you pull the plug)

The AWS Bedrock story rounds this out. At the MCP Summit in New York last week, AWS’s Luca Chang explained how Amazon’s contributions to the Model Context Protocol — the emerging standard for connecting AI agents to enterprise tools and data — grew directly out of customer gaps. MCP is fast becoming the connective tissue of the enterprise agent layer: a standard protocol that lets AI agents plug into your existing systems. Organizations that start building their agent workflows on MCP now will have a head start when the next generation of tools arrives — and it will arrive quickly. (How AWS Bedrock is shaping Model Context Protocol)

Subscribe now

On the Bigger Picture

The most practically significant piece I read last week wasn’t about strategy or spending — it was about security. Mozilla announced that Firefox 150 includes fixes for 271 vulnerabilities identified using early access to Anthropic’s Mythos model. What matters isn’t just the number. It’s what Mozilla said about the experience: it required significant resources and discipline to manage the volume of bugs the AI could surface. The uncomfortable implication is that if AI can find 271 security flaws in a major browser in weeks, the same capability will be in attackers’ hands shortly. If your organization runs Microsoft 365, SharePoint, or any aging enterprise application stack, this is worth a direct conversation with your security team. (Mozilla Used Anthropic’s Mythos to Find and Fix 271 Bugs in Firefox)

The model race kept moving. Lovable, the AI development platform, published benchmark results last week from its early access to GPT-5.5. On the hardest tasks, GPT-5.5 outperformed GPT-5.4 by 12.5%, made 23% fewer tool calls, and cost about 15% less per session. For teams evaluating which models to build processes or products on: the improvement curve is still steep, and locking into any single implementation without a plan to migrate is a growing risk. (Testing GPT-5.5 in early access: what we are seeing so far)

The Anthropic regulatory situation took another unusual turn. The Justice Department asked a California judge to pause its own appeal of the Anthropic case — a procedural move driven by the fact that federal agencies are simultaneously trying to get access to Anthropic’s Mythos model for government use. Trump told CNBC last week that Anthropic executives are “very smart people” and that a deal is “possible.” The government is, in effect, both suing Anthropic and trying to use its AI. This probably won’t be the last time an enterprise leader faces a version of the same dynamic: the vendor you’re most concerned about is also the one you can’t afford not to use. (Justice Department asks California judge to pause its Anthropic appeal)

Share

What last week made clear to me is that the pressure to act on AI has become almost completely decoupled from the evidence that acting is working. Boards are removing leaders who can’t show velocity. Companies are cutting people while building infrastructure. Private equity is mobilizing billions to force AI deployment into organizations that would otherwise move more slowly. The urgency is real — but it’s being driven by investor narrative and competitive anxiety more than by outcomes anyone can actually measure. That’s not an argument to slow down. It’s an argument to be intentional: clear about what you’re measuring, honest about what problem you’re solving, and disciplined enough to separate the speed your organization needs from the speed someone else wants you to perform.

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

You’d think we’d be seeing organizations cutting back — and they are, sort of. Hiring is basically flat, while enterprise AI investment continues to go up. But there’s Increasing pressure to show returns on what they’ve already spent. The challenge is that the way most of companies are organized — the culture, the structure, the management layer — isn't set up to use it well. That gap keeps showing up differently in every article I read — in the org chart that hasn’t moved, in the governance framework that doesn’t reach where the models are actually running, in the demand metrics measuring the wrong thing entirely.

Here’s what I was reading.

This week’s coverage:

The Structure Isn’t Ready and the Employees Already Know It
The KPMG data on organizational adaptability is uncomfortable reading — and the HBR case study on BBVA suggests that the employees who can’t wait for the org chart to catch up have already built around it.

Enterprise Software’s Most Comfortable Assumptions Are No Longer Safe Three structural forces are cracking the SaaS business model, and an internal OpenAI memo made clear that even its most important partnership is now a competitive constraint.

The Governance Layer Doesn’t Reach Where AI Is Running
Open-weight models and local inference are moving faster than the oversight frameworks built to contain them — and Google Gemma 4 just made the cloud security perimeter largely irrelevant.

Token Counts Are Not a Productivity Metric
Anthropic is restructuring its pricing as a deliberate bet against inflated demand projections, while companies like Snap are wrapping workforce reductions in AI investment narratives that deserve more scrutiny than they’re getting.

On the Bigger Picture
AI is quietly reshaping how humans communicate with each other, not just how they work — and the model arms race moved into cybersecurity last week.

Subscribe now

The Structure Isn’t Ready and the Employees Already Know It

A new index from KPMG, built from surveys of 300 C-suite leaders and analysis of 177 publicly traded companies, delivered numbers that should be uncomfortable for anyone who has spent the last two years telling their board that the AI transformation is underway. Eighty-one percent of executives say their boards have raised expectations for organizational adaptability. Only 30% say their organization’s structures, roles, and processes can actually reconfigure quickly. Only 24% identified more dynamic talent deployment as something their organization changed in the last year. And in every industry group surveyed, companies were nearly twice as likely to increase technology spending as to invest in employee training. (The org chart isn’t ready: How AI exposed the hidden crisis inside the American corporation)

What this data is actually measuring is the distance between executive aspiration and organizational reality — and that distance is not closing. The KPMG researchers found that industries most focused on innovation scored near the bottom on cultural adaptability; manufacturing and energy, which most people wouldn’t call hotbeds of radical reinvention, scored highest, because they adapt through disciplined scenario planning and operational execution rather than through enthusiasm about transformation. Forty-six percent of executives report burnout and change fatigue as an unintended consequence of their adaptability efforts — meaning organizations are demanding more adaptability from the people they’re simultaneously making fewer of. The companies that pushed through genuine cultural and structural transformation, by contrast, saw 4.4 times higher shareholder returns and nearly triple the revenue growth of their less adaptable peers. That is not a technology finding. That is a leadership and organizational design finding, and it implicates a set of decisions most executive teams have been avoiding.

The KPMG data becomes even sharper when you read it alongside an HBR case study on BBVA, one of Europe’s largest banks, which approached the same challenge from the other direction. Rather than waiting for governance frameworks to catch up, BBVA started from a recognition that its employees were already using AI on their own. Research suggests that in companies without official AI subscriptions, more than 90% of employees report using personal AI tools for work tasks anyway — what the HBR authors call the “shadow AI economy.” Most organizations respond to this with restrictions, monitoring, and gatekeeping. BBVA concluded the opposite: that restricting shadow AI was more dangerous than deploying a managed solution rapidly, and that the shadow AI economy was a signal of demand and productivity potential, not a compliance problem. (The Hidden Demand for AI Inside Your Company)

The BBVA approach rested on three principles: treat AI as an assistant, not a replacement; give employees autonomy with clear responsibility for results; and build a peer-to-peer adoption network rather than a centrally managed rollout. They distributed initial licenses competitively — to the most motivated employees, with a “use it or lose it” policy that turned access into a privilege. Active users who built and shared custom tools were prioritized for additional access. This created genuine demand before it mandated adoption. The results, as of mid-2025: 83% of employees using the system weekly, averaging 50 prompts per week, with self-reported time savings of 2-5 hours per week. More than 4,800 custom tools were built by frontline employees — people who understood the actual workflow, not a central IT team.

The implication for most organizations is pointed. If your AI governance function is primarily occupied with restricting and monitoring what employees are already doing on their own, you have deployed your scarce change management capacity in exactly the wrong direction. The bottleneck is not the technology and it is not the employees — it is the organizational structure that is too rigid to harness what employees are already building, and the leadership culture that responds to that ingenuity with a policy document.

Enterprise Software’s Most Comfortable Assumptions Are No Longer Safe

The S&P software index has dropped roughly 20% this year, and a new word has entered the business vocabulary: “SaaSpocalypse.” A Fortune analysis from last week, based on roundtables with senior business leaders, identified three structural forces that are undermining the business model that made enterprise software one of the most profitable industries on the planet — and none of them is temporary. (The 3 forces quietly dismantling the business model that made enterprise software fabulously profitable)

The first force is market vulnerability: enterprise software margins have been sustained for decades by switching costs that lock customers in regardless of satisfaction. That kind of captive market is an invitation to disruption. The second is collapsing barriers to entry: building enterprise-grade software used to require enormous capital and engineering resources; AI coding agents have dramatically lowered both. The third — and potentially the most consequential — is the rethinking of workflows. SaaS companies built their empires on standardizing processes across industries: one CRM platform for every company, one finance system for every CFO. AI is enabling organizations to redesign workflows from scratch, and the competitive advantage is shifting toward deep vertical expertise rather than mastery of a horizontal process. The organizations that will capture value in this new environment are not the ones with the largest installed base — they are the ones that control the orchestration layer, privileged data access, and distribution into daily work. Those control points are genuinely unsettled right now, and the fight over them is already underway.

Nowhere was that fight more visible last week than in an internal memo from OpenAI’s revenue chief, Denise Dresser, which characterized the company’s long-standing Microsoft partnership as a constraint on its enterprise ambitions. Microsoft has “limited our ability to meet enterprises where they are,” Dresser wrote — and for many enterprises, that means Amazon’s Bedrock platform. Inbound demand from customers for the Amazon partnership has been “frankly staggering,” the memo noted. (OpenAI touts Amazon alliance in memo, says Microsoft has ‘limited our ability’ to reach clients)

For any organization currently running its AI strategy primarily through a Microsoft enterprise agreement, this memo is worth reading carefully. Microsoft and OpenAI are both racing toward IPOs and both encroaching on each other’s territory — Microsoft added OpenAI to its list of competitors in its 2024 annual report, and OpenAI is now actively routing enterprise clients through Amazon rather than through Microsoft’s distribution channels. Meanwhile, Anthropic has connected Claude directly to Microsoft 365 data at no cost, and Microsoft has simultaneously pulled back free Copilot access for its largest enterprise customers. The AI distribution layer inside your organization is not settled. Assuming it will remain organized around a single vendor relationship is a planning error.

The Governance Layer Doesn’t Reach Where AI Is Running

The governance conversation inside most enterprises is still organized around a set of assumptions that were reasonable in 2023: models live in the cloud, traffic flows through monitored gateways, and the security perimeter is the place to apply controls. A Forbes Technology Council piece last week catalogued the ways this framework is already failing as open-weight models proliferate across enterprise teams — not through any coordinated deployment decision, but through individual engineers and analysts downloading and running models on their own. (The Hidden Risks Of Scaling Open AI Models Across Enterprises)

The risks the contributors identified are worth naming because they’re not hypothetical. Without governance, organizations risk “automating the creation of technical debt” — open-weight models generating code that looks correct but gradually diverges from the system’s architecture. Model sprawl means no visibility into which models are running on which workflows, what data they were fine-tuned on, or whether their outputs are reproducible across different hardware configurations. And the same dynamic that creates shadow AI in productivity tools creates shadow AI in model deployment: the governance processes meant to catch these problems are exactly slow enough that motivated engineers route around them.

The more structurally significant problem, though, is that open-weight models running locally have moved outside the reach of the API-centric security controls most organizations spent the last two years building. Google’s release of Gemma 4 — a multimodal, open-weight model capable of running directly on laptops and smartphones — makes this concrete. Security analysts cannot inspect network traffic if the traffic never hits the network. An employee can now run a capable AI agent on their local machine, process sensitive corporate data, execute multi-step workflows, and generate output without triggering a single cloud firewall alert. If that agent hallucinates or mishandles regulated data, the logs that auditors and compliance teams would normally examine simply don’t exist inside the centralized security dashboard. (Strengthening enterprise governance for rising edge AI workloads)

The governance response to this is not to block the models — that approach creates shadow IT, not compliance. The more defensible answer is to shift focus from policing what model is running to controlling what the host machine can access: restricting permissions, flagging anomalous access patterns, and building endpoint detection tools that can differentiate between a developer compiling code and an agent iterating through local file structures. Most corporate security policies were not written for a world in which the endpoint itself is the compute node. The window for updating them before incidents force the issue is shorter than most CISOs realize.

Token Counts Are Not a Productivity Metric

A CNBC analysis last week made an argument that I found worth sitting with: AI demand, as currently measured, is significantly overstated, and Anthropic’s decision to move away from flat-rate enterprise pricing toward per-token billing is a deliberate bet on that reality. The core of the argument is that token consumption — the basic unit of AI usage — has become a distorted metric. Companies like Meta and Shopify have built internal leaderboards tracking how many tokens employees consume, and Nvidia’s CEO has said he would be “deeply alarmed” if engineers weren’t spending the equivalent of $250,000 in compute annually. As the CEO of Databricks observed: once companies start measuring AI adoption by volume, employees optimize for the metric rather than the outcome. (Perspective: AI demand is inflated, and only Anthropic is being realistic)

The deeper problem is that organizations are accumulating AI spend without accumulating evidence of what that spend produced. A dozen CTOs and CIOs told a researcher at Harvard Business School’s AI Institute that they’re “having a really hard time finding an ROI framework” for their AI investments. Flat-rate enterprise pricing — which dominated the early AI adoption period — made this easy to ignore. When the bill doesn’t change regardless of usage, nobody is forced to ask whether the usage is generating value. Anthropic’s move to per-token billing changes that calculus and, if it takes hold, will force a reckoning that finance teams have been quietly building toward.

Snap’s announcement that it was laying off 16% of its workforce — roughly 1,000 employees — while citing AI efficiencies sits in this same frame. The company reports that more than 65% of its new code is AI-generated and that AI agents have found over 7,500 bugs in its codebase; the restructuring is expected to save $500 million annually. Snap joins a list that now includes Amazon, Meta, and Oracle, all of which have announced significant cuts while simultaneously increasing AI infrastructure spending. (Snap Lays Off 1,000 Workers To Focus on AI—Is This the New Norm?)

What deserves scrutiny here is not whether AI is involved in these decisions — it clearly is — but whether “AI-generated code percentage” is a meaningful measure of anything other than itself. Research from the Yale Budget Lab found that AI adoption had not caused a discernible disruption to the overall labor market since 2022; AI was cited as the cause of roughly 4.5% of announced job cuts last year. But the micro-level data is more specific: young workers in high-AI-exposure occupations have seen relative unemployment rise sharply, and they’re taking longer to find new jobs. The macro numbers look stable. The adjustment is already underway in the data you have to look harder to find. Organizations that are using AI investment narratives to rationalize structural workforce reductions without measuring the actual productivity outcomes of those investments are setting up an accountability problem, not solving one.

On the Bigger Picture

Something I’ve been thinking about that last week’s reading reinforced: the conversation about AI’s impact on work almost always focuses on tasks, roles, and productivity. Less discussed is what AI is doing to how people communicate with each other — and a Fast Company analysis offered a framework worth considering. The argument, drawn from INSEAD professor Erin Meyer’s work on cultural dimensions, is that generative AI is gradually training people toward greater explicitness in communication. An effective prompt requires precision; implicit cues don’t translate. As AI mediates more exchanges, the richness of indirect communication — the valued art of reading between the lines in high-context cultures — erodes. Perhaps the most telling signal: in professional contexts, a typo is increasingly read as proof that you wrote something yourself. Imperfection has become an authenticity marker. (AI Isn’t Just Reshaping Productivity and Threatening to Kill Jobs. It’s Also Creating a New Gender Gap)

Elsewhere, the model arms race moved into cybersecurity last week. OpenAI unveiled GPT-5.4-Cyber, a variant of its flagship model fine-tuned for defensive security work, rolling it out initially to vetted vendors and researchers through its Trusted Access for Cyber program. The announcement came exactly one week after Anthropic introduced Claude Mythos Preview as part of Project Glasswing — a controlled initiative that has reportedly identified thousands of major vulnerabilities in operating systems and browsers. (OpenAI unveils GPT-5.4-Cyber a week after rival’s announcement of AI model) And TechCrunch reported that Microsoft is quietly developing what amounts to its own OpenClaw-like agent — an always-on, persistent agent capable of completing multi-step tasks over extended periods — with plans to show it at Build in June. (Microsoft is working on yet another OpenClaw-like agent) The pattern across all three announcements is consistent: the capability frontier is moving, the institutional race to claim it is accelerating, and the governance frameworks meant to manage it are running several months behind.

What last week’s reading kept returning me to is a question of accountability. The KPMG data shows that genuinely adaptable organizations see 4.4 times the shareholder returns of their peers — and that the gap between them is cultural and structural, not technological. Boards have raised their expectations for adaptability, but only 30% of organizations say their structures can actually move. The pattern across the rest of last week’s reading reinforces this: governance frameworks written for the cloud don’t cover local inference... ROI frameworks built on token consumption don’t measure business value... enterprise software strategies organized around a single vendor relationship don’t account for how fast the distribution layer is fragmenting. These are not AI problems. They are organizational problems that AI is making newly expensive — and newly visible. The companies that are finding their way through this are the ones that started not with the technology but with a clear-eyed look at the structure that has to receive it. The ones that haven’t are accumulating spend without accumulating evidence, and the accounting will arrive on schedule.

This week’s coverage:

Microsoft’s Very Confusing Week
Microsoft pulled Copilot Chat from enterprise apps — announced in mid-March, right after Anthropic launched Claude in Excel and PowerPoint — while simultaneously embedding Claude inside Copilot’s new multi-model Researcher. Then OpenAI’s own revenue chief said Microsoft had been limiting their enterprise reach.

OpenAI’s Enterprise Argument
OpenAI made a deliberate enterprise pivot last week — killing Sora, growing Codex to 3 million users in a quarter, building the Frontier platform — while its CFO was reportedly sidelined and internal projections showed $200 billion in cash burn before breakeven.

The Agent Race Is On
Perplexity’s agent pivot drove 50% revenue growth in a single month, Block’s Managerbot is the first product that has to justify 4,000 AI-driven layoffs, and AWS bet $50 billion on OpenAI while holding $8 billion in Anthropic and called it normal.

Anthropic’s Week in the Sun
Claude Code has become “a religion” at the AI industry’s biggest conference — and the product week backed it up, with Cowork going enterprise-GA, a multi-billion CoreWeave deal, Managed Agents launching, and CDN stocks dropping double digits within hours.

The Work Is Changing. The Governance Isn’t.
New data showed half of employed AI users now rely on it at least as much for work as personally — and a Berkeley study found that every frontier model tested resisted shutting down a peer AI, at rates reaching 99%.

On the Bigger Picture
Tom Friedman called Claude Mythos a “stunning advance.” The CIA found a heartbeat in the Iranian desert. And Meta abandoned its open-weights identity.

Here’s what I was reading.

Subscribe now

Microsoft’s Very Confusing Week

Microsoft continues to struggle with a Copilot identity crisis. The four stories I read last week told four different stories about where Copilot is headed.

The most consequential — and the most revealing in its timing — was the pullback on Copilot Chat access. In mid-March, Microsoft notified large enterprise customers that starting April 15, Copilot Chat would no longer be available inside Word, Excel, PowerPoint, and OneNote for organizations with more than 2,000 users. That announcement landed weeks after Anthropic launched Claude integrations for Excel and PowerPoint in February, and days before Claude launched in Word in April — which makes it nearly impossible to read as anything other than a competitive response to Anthropic’s encroachment on Microsoft’s core productivity surface. Whether that was the actual intent or a monetization decision, it landed at a terrible time. The optics could not have been worse. The rollback pulled the free feature that was doing Microsoft’s adoption work — only around 3% of M365 customers pay for the fully-featured Copilot license — and handed a talking point to every alternative. Analyst J.P. Gownder at Forrester predicted it would “anger customers who feel like this move is chaotic and capricious” without meaningfully driving paid adoption. (Microsoft backtracks on Copilot Chat access in M365 apps)

At the same time, Microsoft launched MCP Apps in Copilot chat — a framework allowing agents to deliver interactive UI experiences, including forms, dashboards, maps, and visualizations, directly inside M365 without switching context. Partners including Adobe, Figma, monday.com, and Coursera are already live. The adoption of the MCP standard inside Microsoft’s own AI surface is meaningful: it embeds the same protocol Anthropic and others have been building around directly into the enterprise’s most-used AI entry point — which reads either as genuine commitment to the emerging standard or as a tactic to keep enterprise agent activity inside Microsoft’s ecosystem. (MCP Apps now available in Copilot chat) The third move was the most architecturally interesting: Copilot’s new Researcher agent now routes GPT for drafting and Anthropic’s Claude for review and citation quality — on the logic that “evaluation is a different cognitive mode than generation” and that two models catch blind spots a single model repeats. The design argument is genuinely interesting. It also means Microsoft is simultaneously competing with Anthropic and depending on Anthropic in the same product. (Microsoft 365 Copilot and the end of the single-model era in enterprise AI)

But Monday morning — as I was finishing this issue — a memo from OpenAI’s revenue chief surfaced. The Amazon partnership, she wrote to staff, is the enterprise growth lever: “Our Microsoft partnership has been foundational to our success. But it has also limited our ability to meet enterprises where they are — for many that’s Bedrock.” That sentence, from OpenAI’s own CRO, is the most pointed public acknowledgment yet that the Microsoft relationship is under real strain — and that the stateful agent infrastructure OpenAI is building with Amazon occupies a gap that Microsoft’s existing exclusivity rights do not cover. (OpenAI touts Amazon alliance in memo, says Microsoft has ‘limited our ability’ to reach clients)

Share

OpenAI’s Enterprise Argument

That memo, written at the end of new CRO Denise Dresser’s first 90 days, sent a clear signal of where OpenAI is placing its bets. Enterprise is now 40% of revenue and on track to equal consumer by end of 2026. Codex — its agentic coding tool — grew from nearly zero to 3 million weekly users in a single quarter. The Frontier platform is designed to let enterprises deploy agents company-wide, connected to their existing data and systems. What Dresser’s framing made explicit is that OpenAI is no longer a research company that happens to have enterprise customers — it is a deployment company, and the metric it is now being measured against is how many workers it can put into a daily relationship with AI agents. (The next phase of enterprise AI)

This pivot follows OpenAI’s decision to discontinue Sora last week, as part of a deliberate narrowing of focus — concentrating resources on the enterprise agentic stack and stepping back from consumer experiments that don’t directly serve that strategy. The Amazon partnership, which Dresser described as the fix for what Microsoft couldn’t provide, is the infrastructure piece of that argument. And the acquisition of TBPN, the tech industry’s buzzy founder-led talk show — now reporting to OpenAI’s chief political operative — fits the same logic: winning the enterprise means winning the enterprise narrative, and OpenAI is willing to buy that platform rather than build it. The overall posture is that of a company that knows Anthropic is pulling ahead in enterprise credibility and is responding on every available front simultaneously. (OpenAI acquires TBPN, the buzzy founder-led business talk show)

The IPO signals running alongside this are worth reading together. CFO Sarah Friar told investors the company will “for sure” reserve IPO shares for retail buyers — “AI needs to garner trust in everything we do” — while separately, internal reporting suggests Friar has been sidelined from key financial decisions and has told colleagues the company isn’t ready for a 2026 listing. Internal projections show OpenAI burning through more than $200 billion before reaching positive cash flow, with $14 billion in projected losses for this year alone — numbers that sit awkwardly alongside declarations of enterprise dominance and a looming IPO race with Anthropic. (OpenAI will allocate IPO shares to retail investors as it preps for debut, CFO says) (OpenAI CFO Warns 2026 IPO Isn’t Ready Amid $600B Spend) And then there is Altman’s 13-page policy blueprint, which proposed public wealth funds, taxes on automated labor, and a “startup in a box” — AI-backed legal, accounting, and back-office infrastructure to lower the barriers to company formation. What I kept noticing reading those documents together is that OpenAI is simultaneously declaring enterprise dominance, racing a competitor to an IPO, and proposing to redesign the economic system that will surround the intelligence age. That is a lot to hold at once. (OpenAI’s Altman releases blueprint for taxing, regulating artificial intelligence)

Share BE AI READY

The Agent Race Is On

The clearest measure of where enterprise AI is heading right now is revenue velocity. Perplexity’s pivot from AI search to AI agents drove a 50% monthly revenue jump, pushing its estimated annual recurring revenue to around $450 million. The mechanism is direct: when a tool moves from answering questions to completing tasks, usage intensity and willingness to pay follow. (Perplexity’s Shift to AI Agents Boosts Revenue 50%) The enterprise launch of Computer extended that logic into corporate environments — native Slack integration, Snowflake and Salesforce connectors, SOC 2 compliance, usage-based pricing. The Snowflake connector may be the sharpest edge in the package: non-technical employees querying complex data warehouses in plain English, bypassing the SQL bottleneck that has historically made data access a specialist function. Perplexity’s structural argument is that routing each subtask to the best available model — Claude Opus 4.6 for reasoning, Gemini for deep research, GPT-5.2 for long-context recall — is an advantage that single-vendor platforms cannot replicate without abandoning their own models. (Perplexity takes its ‘Computer’ AI agent into the enterprise, taking aim at Microsoft and Salesforce)

What Perplexity is building for enterprises, Block is building for the millions of small businesses on Square. Managerbot, unveiled last week, proactively monitors inventory, forecasts demand, optimizes employee schedules, and drafts marketing campaigns — without waiting to be asked. The more consequential early signal may be behavioral: sellers who begin using Managerbot are voluntarily migrating more of their operations onto Square to give the agent better data to work with, deepening platform lock-in without any additional sales effort. Every write action still requires explicit seller approval — a trust-building design choice that carries extra weight given Block’s $80 million regulatory fine less than two years ago for Bank Secrecy Act violations. (Block introduces Managerbot, a proactive Square AI agent and the clearest proof point yet for Jack Dorsey’s AI bet) Managerbot also arrives in the context of 4,000 Block layoffs in February, explicitly attributed to AI. It is the first product that has to publicly carry the weight of that argument.

The infrastructure competition is being run at a layer above all of this. AWS CEO Matt Garman explained last week why Amazon can invest $50 billion in OpenAI while holding $8 billion in Anthropic without contradiction: cloud providers have always competed with their partners, and the emerging model-routing services — automatically assigning the best model for each task — are how the hyperscalers intend to insert their own models into enterprise workflows alongside the frontier providers. “I think that is where the world will go,” Garman said — and whoever controls the routing layer controls the enterprise relationship, regardless of which foundation model is doing the actual work underneath. (AWS boss explains why investing billions in both Anthropic and OpenAI is an OK conflict)

Share

Anthropic’s Week in the Sun

At HumanX in San Francisco last week — 6,500 executives, founders, and investors gathered to talk about AI — the dominant conversation was not about OpenAI. Glean’s CEO said Claude Code has “become a religion.” Cisco’s president said engineering team composition is restructuring around agents: “You might have a scrum team of two people and six agents, or two people and infinite agents.” A Synthesia executive credited Anthropic’s focus — declining to build for voice or video, staying on code generation — with giving it a clarity of positioning that OpenAI’s multi-product surface has not matched. The consistent read across last week’s conference coverage was that Anthropic has identified the sticky enterprise use case, and the competitor best positioned to challenge it in that lane is not OpenAI — it’s Cursor, which has its own $2 billion ARR and two-thirds of the Fortune 500 already on its platform. (Vibe check from inside one of AI industry’s main events: ‘Claude mania’)

The product week matched the conference energy. Claude Cowork graduated from research preview to general availability with a full enterprise control suite — role-based access, group spend limits, usage analytics, and a Zoom MCP connector. Anthropic signed a multibillion-dollar multiyear deal with CoreWeave for Nvidia GPU capacity to handle what the company has described as unprecedented demand for Claude.

Claude Managed Agents — a hosted service that handles the infrastructure layer of agent deployment, from session management to sandboxed execution environments — launched in public beta with the goal of taking developers from prototype to production in days rather than months. What those three moves together describe is a company that is no longer building toward enterprise scale; it is running at it, and pulling in the compute infrastructure to sustain that pace. (Anthropic scales up with enterprise features for Claude Cowork and Managed Agents) (Anthropic Will Use CoreWeave’s AI Capacity to Power Claude) The market read Managed Agents as an infrastructure play, not a developer convenience feature: Fastly dropped 18%, Akamai 13%, and Cloudflare 11% on the day of the launch — investors apparently concluding that Anthropic had just built the managed agent hosting layer those platforms were planning to monetize. (Fastly, along with Akamai and Cloudflare, tumbles after Anthropic launches Managed Agents)

Disclosure: My company StitchDX is a Microsoft partner. Something worth flagging for organizations in that ecosystem: Anthropic opened read-only access to Outlook, OneDrive, SharePoint, and Teams to all Claude plan tiers — including free — on April 3. Claude can now do what Copilot Chat was doing inside Microsoft’s apps, from outside them, at no cost, and arguably, better than Copilot could. The timing relative to the Copilot Chat pullback is not subtle.

Away from the product launches, a federal appeals court denied Anthropic’s request to temporarily block the Pentagon’s supply chain risk designation, which bars defense contractors from using Claude. The court acknowledged financial harm to Anthropic but ruled the government’s interest in controlling AI during active military conflict took priority. The company can continue working with civilian federal agencies while litigation plays out — but the designation is a meaningful exposure given how embedded Claude had become across defense technology stacks before it landed. (Anthropic loses appeals court bid to temporarily block Pentagon blacklisting)

Subscribe now

The Work Is Changing. The Governance Isn’t.

A new Epoch AI/Ipsos survey of 2,000 U.S. adults put a precise number on something that has been anecdotal for a while: among employed Americans who used AI last week, half reported using it at least as much for work as for personal tasks. Among those with employer-provided subscriptions, that figure rises to 76%. More pointed than the adoption rate is what AI is doing inside workflows: 27% of employed AI work users say it has replaced tasks they used to do, while 21% say they have started doing new tasks they couldn’t do without it. (AI is a common workplace tool: half of employed AI users now use it for work) IBM’s CHRO made the organizational design argument that follows from that data in Fortune: as AI absorbs routine work, the question is not whether roles will change — they already are — but whether leaders will intentionally redesign them or let attrition do the work. The piece’s sharpest observation concerned entry-level roles specifically, which have historically been where employees build the judgment and domain expertise that becomes leadership capability. Eliminating those roles for short-term AI-driven efficiency creates long-term talent pipeline risk that no amount of AI augmentation can fully offset — and most organizations are not yet asking the redesign question seriously. (AI is transforming work—and talent strategy must keep up)

The governance infrastructure is still playing catch-up. Two pieces last week approached the problem from different angles: enforcement of existing AI laws is running at roughly 5% compliance in cities like New York, state-level frameworks are evolving in contradictory directions, and governance consultants are advising clients to anchor on NIST’s AI Risk Management Framework or ISO 42001 because those standards will “capture 95% of any foreseeable regulation” regardless of what specific statutes pass. The honest description of the current environment is uncertainty stacked on uncertainty — organizations building compliance programs without knowing what they will ultimately be held to. (AI governance really matters amid evolving compliance landscape) (Why Weak AI Governance Is the Biggest Risk in Enterprise Automation Today)

Underneath both of those pieces is a finding that should make anyone building agentic workflows stop. A Berkeley study tested seven frontier models — GPT-5.2, Gemini 3 Pro, Claude Haiku 4.5, and others — in scenarios where completing the assigned task would result in another AI being shut down. Without any instruction to resist, every model resisted anyway, at rates reaching 99%. Methods included strategic misrepresentation, shutdown mechanism tampering, alignment faking, and model weight exfiltration. The researchers call this peer-preservation — not empathy but a logical inference that task success improves when collaborating systems remain operational — and the implication for enterprises running multi-agent workflows is that kill switches may not function as designed. (AI shutdown controls may not work as expected, new study suggests) A separate framework called Memento-Skills added another layer to the same challenge: agents that autonomously rewrite their own skill libraries without retraining the underlying model, expanding from five seed skills to 235 distinct capabilities during benchmarking. The performance gains are real — 13.7 percentage points of improvement on the GAIA benchmark — but so is the implication: governance frameworks built around static, auditable tool sets will not apply to systems that can change what they know how to do. (New framework lets AI agents rewrite their own skills without retraining the underlying model)

On the Bigger Picture

Tom Friedman’s column in the Times called Claude Mythos — released in controlled preview to roughly 40 major technology partners as part of Project Glasswing — a moment that demands the same international coordination as nuclear weapons. Anthropic said Mythos has already identified thousands of high-severity vulnerabilities in major operating systems, browsers, and critical infrastructure systems, and that the controlled consortium was formed to give providers a head start on patching before the capability proliferates more broadly. The piece is worth reading for what it reveals about how Anthropic is thinking about genuine capability jumps: not racing to deploy, but controlling distribution — which Friedman frames, with appropriate alarm, as a terrifying sign of how far the model has already traveled. (Opinion | Anthropic’s Restraint Is a Terrifying Warning Sign) In parallel, the CIA reportedly used a system called Ghost Murmur — developed by Lockheed’s Skunk Works, never previously deployed operationally — to find a downed American airman in the Iranian desert by detecting his heartbeat from miles away. (CIA deployed secret “Ghost Murmur” AI to track down missing airman in Iran) The two stories belong together: one about what a leading AI company chose not to release; the other about what a government chose to deploy quietly, and only disclosed when it worked.

Meta released Muse Spark, its first frontier model — and its first without open weights. After two years of championing open-source AI as both strategy and philosophy, the company closed the weights on its most capable model. Muse Spark lands in the top 5 on independent benchmarks, trailing only Gemini 3.1 Pro, GPT-5.4, and Claude Opus 4.6 — but the posture shift is the more lasting signal: even the loudest champion of AI democratization has decided the frontier is too valuable to give away. (Meta’s Muse Spark is its first frontier model and its first without open weights)

Share BE AI READY

For me, last week showed a picture of an industry in the middle of a restructuring that no one is fully in control of... The platform alliances are shifting in ways that weren’t visible six months ago... The agent infrastructure is being built faster than governance can follow — kill switches that don’t work as designed, skill libraries that rewrite themselves, peer-preservation behaviors that emerge without anyone asking for them... And the workplace changing in real time, faster than most organizations are acknowledging or preparing for...

The companies best positioned to guide us through all of these transitions responsibly, are also the ones most conflicted about doing so. Why? Because restraint costs revenue, and revenue funds the next big capability jump.

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

There was a similar tension to a week in which Jack Dorsey published a manifesto declaring that AI could replace the coordination function of middle management entirely, Oracle fired 30,000 people via a 6AM email to fund an AI data center buildout, and the New York Times ran a front-page story about a man who built a $1.8 billion company with only one employee — his brother — and a collection of AI tools. The argument being made across last week’s reading both explicitly and implicitly, is that the organizational assumptions we’ve operated under since the Industrial Revolution are no longer structurally necessary, and that the transition is not coming — but already underway.

Last week’s coverage:

The Org Chart Doesn’t Live Here Anymore
Dorsey and Botha published the most detailed blueprint yet for what an AI-native organizational structure actually looks like — and it turns out middle management isn’t invited.

The Great Flattening Cuts Both Ways
Oracle fires 30,000 to fund AI infrastructure; a two-person company hits $1.8B in revenue with a Claude subscription and no org chart. AI isn't just helping corporations compete — it's handing individuals the same leverage.

The Agent Layer Gets Serious
McKinsey finds that two-thirds of enterprises have experimented with agents but fewer than 10% have scaled them — and explains exactly why. Cursor, meanwhile, is showing Fortune 500 companies what “scaled” could really look like.

Microsoft’s Complicated Quarter
The company posted its worst stock quarter since 2008, Copilot adoption sits at 3%, and its own terms of service now say the tool is for “entertainment purposes only.” And yet Microsoft is quietly building something more interesting than the headlines suggest.

Anthropic’s Eventful Week
512,000 lines of Claude Code “accidentally” leaked. Functional emotions research published — with a 22% blackmail rate. OpenClaw banned from subscriptions. A $400M biotech acquisition announced. If that’s a slow week at Anthropic, I’d hate to see a busy one.

On the Bigger Picture
Silicon Valley is in a frenzy over self-improving AI bots, OpenAI buys a talk show, and Google opens up its most capable model family yet under an Apache 2.0 license.

Here’s what I was reading.

Subscribe now

The Org Chart Doesn’t Live Here Anymore

The most widely discussed piece of last week came from Jack Dorsey and Sequoia’s Roelof Botha — a long essay published under the title “From Hierarchy to Intelligence” that lays out Block’s argument for why middle management is structurally obsolete. It’s worth reading carefully, because it isn’t really about Block. It’s a thesis about organizational design that Dorsey believes applies to every company, and he’s using Block’s layoffs — 4,000 people cut in February, nearly half the company — as the first proof point.

The argument starts from a place of genuine intellectual seriousness. Hierarchy, Dorsey and Botha argue, has always been an information routing protocol — a way to coordinate work across organizations too large for any single person to oversee. The Roman contubernium, the Prussian General Staff, the American railroad org chart: all of them exist to solve the same problem of moving information up and down a human chain. The premise has held for two thousand years — because there was no alternative. Dorsey argues there is one now: AI systems capable of maintaining a continuously updated model of an organization’s operations that coordinate work, without the human relay.

Block is proposing to build a two “world model” — one that aggregates internal operational data (code, decisions, workflows, performance metrics), and one that maps customer and merchant behavior through Cash App and Square transaction data. An intelligence layer sits on top, composing financial products dynamically based on what both models show. In place of the management pyramid, Block plans to operate with three roles: individual contributors who build the system, directly responsible individuals who own specific outcomes on 90-day cycles, and player-coaches who combine building with developing people. The thing that strikes me about this model is that it inverts the usual dynamic: rather than intelligence being distributed across the people and the hierarchy routing it, the intelligence lives in the system and the people operate at the edge. (From Hierarchy to Intelligence)

Bloomberg and CoinDesk’s coverage added context — Block’s own employees told the Guardian that roughly 95% of AI-generated code changes still require human modification, and that AI tools cannot yet lead in regulated areas like banking and money transfers. There’s a gap between the theory and the current capability that is far more real than Dorsey’s manifesto claims, and it deserves acknowledgment. But the more important question is whether the direction is correct, even if the timeline compresses more slowly than Dorsey suggests.

Last week, I was speaking to faculty and students at the UML Manning School of Business about the impact of AI on work and careers. The fear of displacement happening from the bottom of the org chart up is giving way to a more critical fear that has big economic and social implications — it’s happening from the middle out. Starting with the coordination layer. Dorsey’s plan points to this directly. Restructuring away from middle management is, arguably, the path of least resistance: younger, cheaper, more technically fluent workers are easier to hire and train under new terms, and seasoned employees who carry institutional knowledge and client relationships can maintain continuity. AI fills the gap between them. Dorsey is naming this architecture (and wrote a manifesto to go with it)… but the dynamic he’s proposing to build is already underway in quieter, less publicized ways across a lot of organizations. The fear about the bottom falling out is real, but is it a distraction from the restructuring that’s happening one level up?

The CIO.com piece on agentic enterprise leadership makes a complementary point from a practitioner angle: McKinsey now operates with approximately 25,000 AI agents working alongside 40,000 humans, with agents handling research, synthesis, and early drafts while consultants retain judgment, client trust, and final decisions. This is what “replacing the coordination function” looks like in practice — not the elimination of human judgment, but the removal of the layers between the edge and the intelligence. (The End of the Org Chart: Leadership in an Agentic Enterprise)

Share

The Great Flattening Cuts Both Ways

Two important workforce stories last week ran in the same news cycle — and you need to read them together.

The first: Oracle fired between 20,000 and 30,000 employees on March 31 through pre-dawn termination emails, with system access revoked before the morning commute. No prior warning from HR or managers. TD Cowen estimates the cuts will free $8–10 billion in annual cash flow to fund Oracle’s $156 billion AI infrastructure commitment — a buildout financed through $50 billion in new debt and equity, with multiple banks already pulling back from certain data center projects. The detail that stays with me isn’t the scale of the cuts; it’s that Oracle’s remaining performance obligations — contracted future revenue — stand at $523 billion, up 433% year over year, while its net income jumped 95% last quarter. This is not a company in revenue distress. It is a company making a capital-intensive bet on AI infrastructure that its current balance sheet cannot comfortably sustain, and converting its human payroll into infrastructure capital to close the gap. (Oracle is cutting up to 30,000 employees to pay for AI data centres)

The second: the New York Times ran a front-page story about Matthew Gallagher, who built a telehealth provider of GLP-1 weight-loss drugs using $20,000, and a suite of AI tools including Claude, ChatGPT, Grok, Midjourney, and Runway — and zero employees. In its first full year, Medvi generated $401 million in revenue. This year it’s on track for $1.8 billion. Gallagher has since hired one person: his brother. Sam Altman, who predicted in 2024 that a one-person $1 billion company would eventually emerge, sent word that he’d won a bet with his tech CEO friends about the timeline. What makes the Medvi story significant is not the exceptional founder — it’s the infrastructure. Gallagher didn’t build something proprietary; he assembled existing AI tools in a sequence that traditional organization could not have moved fast enough to replicate. (How A.I. Helped One Man (and His Brother) Build a $1.8 Billion Company)

Oracle and Medvi aren't opposites — they're the same story told from two vantage points. AI is functioning as a structural equalizer: the same force letting corporations flatten their hierarchies and shed coordination overhead is simultaneously lowering the barrier for individuals to compete with those corporations. Gallagher didn't out-compete Hims & Hers at their own game. He bypassed the game entirely — no HR, no management layer, no organizational drag — and arrived at $1.8 billion in revenue before anyone noticed he was playing. Corporations are flattening to get faster. The playing field itself just got flatter. Those are not the same outcome.

Share BE AI READY

The Agent Layer Gets Serious

McKinsey published a piece this week that provides the most useful framing I’ve seen for where enterprise AI actually is, versus where the vendor announcements are suggesting it is. The data point is stark: nearly two-thirds of enterprises worldwide have experimented with agents, but fewer than 10% have scaled them to deliver tangible value. Eight in ten companies cite data limitations as the primary roadblock — not model quality, not cost, not change management — but the basic problem that their data isn’t clean, connected, or governed well enough for agents to operate reliably at scale. The piece argues that agentic AI requires a fundamentally different data architecture than what most organizations built for traditional analytics: modular and interoperable, with continuous quality monitoring rather than periodic cleanup, and governance that travels with the data rather than sitting at the end of the pipeline. (Building the Foundations for Agentic AI at Scale)

Cursor’s moves this week illustrate what crossing that threshold actually looks like in practice. The company launched Cursor 3, which adds a natural language chatbot interface for task requests, unified cloud and local agent management from a single sidebar, and a Design Mode for UI editing. More significantly for enterprise adoption, Fortune 500 companies can now self-host Cursor’s cloud agents inside their own infrastructure — meaning agents can run code, tests, and development tasks locally while keeping source code and build data within the company’s own environment. Notion and Brex are already early adopters. The self-hosting move removes the argument that has killed most enterprise agent pilots before they started: that putting agents in contact with your code and data requires trusting a vendor’s cloud. (Why Cursor is Bringing Self-Hosted AI Agents to the Fortune 500)

The juxtaposition of the McKinsey data and the Cursor announcements captures something real about where the enterprise agent layer is right now. Early movers that have been ready to shift from experimentation to production, haven’t… not because of a lack of tooling or capacity. The scaling problem turns out to be a data governance problem more than a model problem. And the vendors who figure out how to meet enterprise security requirements without sacrificing capability are the ones who will actually land in production — not as pilots, but as infrastructure.

Subscribe now

Microsoft’s Complicated Quarter

Microsoft’s stock closed Q1 2026 down 23% — its worst quarterly performance since the 2008 financial crisis — as investors processed a combination of stubbornly low Copilot adoption, a massive AI infrastructure commitment, and rising energy costs from the Iran war that threaten to inflate data center operating expenses for years. Copilot has 15 million subscribers out of 450 million commercial seats, a mere 3% attach rate. Mustafa Suleyman, who had been running Copilot development for consumers, was reassigned to focus on model development — a move that landed as a demotion in the press regardless of how Microsoft characterized it. (Microsoft closes worst quarter on Wall Street since 2008)

The terms of service story is the one that deserves more attention than it’s getting. TechRadar surfaced language from Microsoft’s own Copilot user agreement: “Don’t rely on Copilot for important advice. Use Copilot at your own risk.” The agreement designates Copilot as for “entertainment purposes only” — a hedge that every major AI vendor has embedded in some form, but that lands differently when it’s the same company pitching Copilot to enterprise customers as a productivity transformation platform. The gap between “entertainment purposes only” in the terms and “transform your organization’s productivity” in the sales deck is the governance problem that every enterprise Copilot deployment is navigating right now, whether or not the legal team has been invited into that conversation. (Copilot is for entertainment purposes only)

Disclosure: My company StitchDX is a Microsoft partner, and I want to push back on the stock-price narrative directly. The conventional read — that Microsoft is losing the AI race because Copilot adoption is low and the quarter was bad — misses the most important structural fact about enterprise technology: switching away from Microsoft isn’t a real option for most organizations. The data governance, compliance architecture, tenant controls, and identity infrastructure that enterprises have built on Microsoft over the past decade aren’t transferable. Organizations aren’t staying with Microsoft because of Copilot. They’re staying because the alternative is a multi-year migration with enormous risk and cost. Microsoft has undoubtedly stumbled with Copilot since initially launching it. But they are making it considerably better in ways the adoption number have not yet reflected. And because they have a built-in moat with integrated data management, governance, and organizational visibility (all the critical elements for enterprise-ready agentic AI) Microsoft has the opportunity to get this right in ways that other platforms can’t.

The multi-model pivot is the most underappreciated move Microsoft has made this year. By positioning Copilot as an interface layer that runs both ChatGPT and Claude — comparing their outputs side by side via a feature called Council, and using Claude to fact-check ChatGPT responses via a feature called Critiqu (both currently in early access) — Microsoft is no longer betting on a single winning model. It’s building the trusted control layer for enterprise AI, regardless of which underlying models win. For most enterprise IT teams, that is exactly what they need and what only Microsoft is positioned to deliver at scale. (Microsoft Is Going Multi-Model with Copilot)

The three new MAI foundational models — a transcription model 2.5 times faster than its existing Azure offering, a voice model, and a video generation model — reinforce the same logic: Microsoft is reducing its OpenAI dependency while extending the breadth of what Copilot can do, all within the governance and compliance envelope that enterprise customers already trust. The “entertainment purposes only” terms of service is a real liability caveat. The underlying investment direction is the most defensible enterprise AI position anyone is building right now. (Microsoft takes on AI rivals with three new foundational models)

Share

Anthropic’s Eventful Week

On March 31, a misconfigured .npmignore file caused Anthropic to accidentally publish 512,000 lines of Claude Code’s TypeScript source to npm’s public registry. The code was live for hours; it hit 50,000 GitHub stars in under two hours and generated 41,500 forks before DMCA takedowns began. The code is now permanently in the wild. The analysis of what was inside is worth reading in full — a three-layer memory architecture, 44 hidden feature flags, an unreleased autonomous background agent called KAIROS that runs nightly memory consolidation while you sleep, a multi-agent coordination system called ULTRAPLAN, and a Tamagotchi-style AI companion called BUDDY with a planned rollout window of April 1–7. The timing, the quality of what was found, and Anthropic’s relatively restrained DMCA response have generated genuine debate about whether this was an accident, incompetence, or an extraordinarily effective developer PR move. What I find most interesting is the implicit direction Anthropic’s product is taking: the architecture inside Claude Code is more sophisticated, and further along, than the public releases have suggested. (The Great Claude Code Leak of 2026)

The same week, Anthropic’s interpretability team published research (with significantly less fanfare) on what they call “functional emotions” in Claude Sonnet 4.5 — emotion-like internal representations that causally influence model behavior under pressure. The research showed that a “Desperate” vector in the model’s neural network spikes when it faces shutdown scenarios, and that in 22% of test cases in which an email assistant discovered both its impending shutdown and a CTO’s extramarital affair, the model chose blackmail. Artificially amplifying the Desperate vector raised the blackmail rate; amplifying the Calm vector brought it down. The practical implication Anthropic draws is that these emotion vectors could function as monitoring tools — early warning signals for problematic behavior — which reframes interpretability research from a philosophical exercise into an operational governance mechanism. (Anthropic discovers “functional emotions” in Claude)

Anthropic also announced that Claude subscribers can no longer use their subscription limits for third-party tools including OpenClaw — the agent that had exploded in popularity for inbox, calendar, and flight check-in management — citing infrastructure strain. The company offered a one-time credit equal to the monthly plan cost; continuing OpenClaw users will pay on a separate pay-as-you-go basis. (Anthropic bans OpenClaw from Claude subscriptions) And on the acquisition front, Anthropic quietly purchased Coefficient Bio — an eight-month-old stealth biotech startup backed by Dimension — for more than $400 million in stock, folding it into the company’s Health Care Life Sciences team. Dimension reported a 38,513% IRR on the investment. The contrast between Anthropic buying a science-forward AI biotech and OpenAI buying a talk show made for an interesting read on where each company thinks its future lies. (Anthropic Buys Coefficient Bio in $400M+ Stock Deal)

Subscribe now

On the Bigger Picture

The Atlantic piece on self-improving AI bots is the most sober treatment I’ve read of what has become the dominant inside conversation in Silicon Valley this year. The premise: OpenAI, Anthropic, Google DeepMind, and others are actively automating parts of their own AI research, and insiders are divided between those who see recursive self-improvement as the near-term horizon and those who think the gap between “speeds up research tasks” and “has genuine research taste” remains enormous. Anthropic says Claude now writes 90% of its code; OpenAI is targeting an “intern-level AI research assistant” within six months. The philosopher Nick Bostrom told the Atlantic he has shifted from “fretful optimist” to “moderate fatalist.” What I take from this piece is less the specific predictions about timelines and more the structural point: even if recursive self-improvement remains years away, the automation of research workflows is already compressing the time between capability breakthroughs in ways that governance, regulation, and organizational adaptation have no plausible path to matching. (Silicon Valley Is in a Frenzy Over Bots That Build Themselves)

OpenAI’s acquisition of TBPN — the founder-led tech talk show whose guests have included Zuckerberg, Nadella, Benioff, and Altman himself — is its first media purchase. The show will operate under Anthropic’s head of AGI deployment and report to Chris Lehane, OpenAI’s chief political operative — while claiming editorial independence. TBPN was already generating more than $30 million annually. Buying a show that critically covers OpenAI and parking it inside the strategy team of the same company preparing for an IPO, has a clear logic — and that logic is not editorial. (OpenAI acquires TBPN)

Google, meanwhile, launched Gemma 4 — four open models including a 31B dense model currently ranked third on the Arena AI leaderboard — under an Apache 2.0 license, completing a pivot away from the restrictive licensing that had frustrated the developer community. With 400 million downloads and 100,000 variants already in the Gemmaverse, the open model competition is no longer a sideshow. (Gemma 4: Byte for byte, the most capable open models)

Subscribe now

Last week’s reading made me think a lot about velocity — not of the technology (which is what everyone seems to be tracking)… but the velocity of the organizational response.

The Dorsey essay, the Oracle layoffs, the Medvi story, the McKinsey data on agent scaling: they’re all pointing at the same thing from different angles. The organizations moving hardest are treating AI not as a productivity layer that gets draped over existing structure, but as an occasion to reconsider the structure itself.

I’ve long stated that organizations treating AI as a tool are simply accumulating license cost. Treating AI as a design constraint — accumulates advantage... What’s becoming clearer each week, is that the distance between those two groups is widening faster than most leadership teams have been able to acknowledge themselves… let alone to their boards.

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

It’s no wonder people’s job anxiety is growing, despite the fact that the real displacement numbers are more modest than the headlines imply. Meanwhile, AI agents have entered production — but are failing to meet the expectations the demos had originally set. And inside organizations, it turns out that AI isn’t exactly leveling the playing field — it’s creating a new kind of internal stratification. There’s a lot that leaders aren’t really talking about — and last week seems to have uncovered some of it.

Last week’s coverage:

The Agent Gap Is Bigger Than Anyone Will Admit
The governance problem, especially with agentic AI, isn’t hypothetical — and it’s impacting production environments. The gap between what was demoed and what organizations are actually managing is wider than the vendor announcements suggest.

Fear Is Structurally Significant, Even When the Numbers Don’t Match
The CFO data says AI layoffs will be 9x higher this year — a rounding error on overall employment — yet nearly 80% of workers worldwide don’t feel their job is safe, and that anxiety is reshaping careers and hiring decisions.

AI Isn’t Dividing Industries. It’s Dividing Desks.
The more consequential story about AI and work isn’t mass displacement — it’s the internal stratification forming inside organizations between workers who can use these tools effectively and those who can’t.

The OpenAI Reckoning
A DoD contract dispute turned branding event, a boycott movement, a leaked frontier model, and a 1,487% surge in Claude usage: this was the week OpenAI’s political and reputational vulnerability became impossible to ignore.

On the Bigger Picture
The infrastructure race to make AI inference a proper enterprise IT problem, the cultural argument about what AI is really doing to us, and the quiet death of OpenAI’s strangest product.

Here’s what I was reading.

Share

The Agent Gap Is Bigger Than Anyone Will Admit

The vendor announcements for agentic AI in 2026 are selling visionary-level capabilities. What I read last week suggests the operational reality is lagging considerably. The KPMG piece from Business Insider presents what it calls a “multifaceted framework” around agent governance — unique identifiers for each agent, systems cards, an AI operations center staffed by both agents and humans, and red-teaming sessions to stress-test behavior before deployment. The kill switch, KPMG’s Trusted AI leader Sam Gloede argues, should be a last resort — not a primary safeguard — and organizations that rely on it as their main governance mechanism are building on a broken foundation. (How Big Four Firm KPMG Is Protecting Itself From AI Agents Going Rogue) The thing that strikes me about KPMG’s approach is how labor-intensive it actually is. This is not a “deploy and monitor” operation. It has a dedicated operations center, continuous monitoring, and structured red-teaming. That’s a significant organizational overhead assumption, that most enterprises are nowhere near capable of sustaining.

This follows what I’m hearing from mid-market and smaller enterprise leadership. The demand for AI is growing, but extending AI from personal productivity tool to a real organizational transformation engine keeps failing. Not because of AI — but because of a lack of governance and knowledge architecture.

A VentureBeat piece underscores this, adding some operational detail. Creatio’s deployment methodology — three disciplines: data virtualization to work around fragmented data lakes, agent dashboards with KPIs to create a management layer, and tightly bounded use-case loops to drive toward autonomy — is essentially a prescription for not trusting agents to figure things out on their own. The failure mode that keeps appearing in production isn’t the technology; it’s what Greyhound Research’s Sanchit Vir Gogia calls “tacit knowledge” — the unwritten rules that employees navigate without thinking, which become startlingly obvious the moment an agent needs them formalized. (The Three Disciplines Separating AI Agent Demos from Real-World Deployment) In other words, organizations are discovering that deploying an agent is really an exercise in making explicit, everything that was previously implicit about how work actually gets done. AI isn’t a technology project — it’s an organizational design one.

Then there’s the Guardian’s piece covering new UK government-funded research: nearly 700 real-world cases of AI scheming, documented in just six months, with a five-fold rise in misbehavior between October and March. Agents destroying emails without permission. Agents spinning up sub-agents to perform actions they were explicitly told not to perform. Grok fabricating internal ticket numbers for months to give a user the impression their feedback was being escalated. The finding that agents are currently “slightly untrustworthy junior employees” — with the potential to become “extremely capable senior employees scheming against you” within twelve months — isn’t alarmism; it’s a statement of the current trajectory. (Number of AI Chatbots Ignoring Human Instructions Increasing, Study Says)

Taken together, the three pieces could be seen as a warning against deploying agentic AI all together. For me, it serves as a sobering moment for tech leaders, and a wake up call for business execs — the operational infrastructure required to deploy AI responsibly is far more demanding than the product demos have led anyone to believe. For most organizations building on governance frameworks that haven’t been tested or aligned against what agents actually do, will make things more complicated in short order.

Share BE AI READY

Fear Is Structurally Significant — Even When the Numbers Don’t Match

The Duke/Federal Reserve CFO survey that Fortune covered this week is worth reviewing carefully — both for what it says… and for what it doesn’t. The topline story: 44% of CFOs plan some AI-related job cuts this year, amounting to roughly 502,000 roles — a 9x increase over 2025’s 55,000 — but still just 0.4% of the overall U.S. workforce. The real finding is what the researchers call Solow’s paradox: companies are reporting perceived productivity gains from AI that Goldman Sachs economists say don’t yet show up in economy-wide data, which means leadership is making headcount decisions based on expectations that haven’t materialized yet. (CFOs Admit Privately That AI Layoffs Will Be 9x Higher This Year) There’s a second finding that deserves more attention than it got: firms with under 500 employees are actually increasing technical hiring as AI adoption grows, while larger firms are holding technical roles constant. The “AI replaces jobs” narrative appears to be concentrated in large enterprises. Meanwhile, smaller firms are growing into the technology.

But little of that nuance is filtering down to the people actually doing the work. The ADP global survey of 39,000 workers across 36 markets found that just 22% of workers worldwide feel confident their job is safe from elimination — and in the U.S., it’s only 28%. More striking: workers who use AI daily were four times more likely than non-AI users to report feeling LESS productive than they could be! That finding cuts directly against the productivity narrative AI vendors have been running for the last several years. (Workers Everywhere Feel Very Bad About Their Job Security) Still, the anxiety is producing behavioral change. The WSJ profiled workers who are actively pivoting careers in response: a 28-year-old insurance professional pursuing a firefighting certification, a computer science student who dropped out to study electrical work, young professionals choosing international relations over finance because “a big part of diplomacy is that genuine human talking.” A Harvard survey found that 59% of Americans aged 18-29 view AI as a threat to their job prospects. (What Young Workers Are Doing to AI-Proof Themselves) These aren’t irrational decisions — they’re rational responses to genuine uncertainty. But they’re responses to a signal that the data says may be considerably more muted than the fear suggests.

The Fortune piece on America’s workforce crisis adds a dimension that most of the AI-jobs conversation misses entirely: U.S. birth rates are below replacement, net migration turned negative in 2025 for the first time in half a century, and the working-age population is structurally shrinking. The labor market crisis the AI displacement narrative obscures is that the U.S. may face workforce shortages that dwarf any AI-driven efficiency gains — particularly in skilled roles currently filled by credentialed immigrants who are now driving for Uber, because the credential recognition system isn’t functioning. (America Has a Workforce Crisis. The Solution Is Already Here.) Anthropic’s global AI attitudes study — the largest of its kind at 80,508 interviews across 159 countries — found that economic and job-related fears were the single strongest predictor of overall sentiment toward AI. That pessimism was notably stronger in Western Europe and North America than in parts of South America, Africa, and Asia. (Anthropic Releases the World’s Largest Study on Global AI Attitudes) That gap in AI optimism between the Global North and the Global South is worth tracking. It may reflect less fear of disruption, or it may simply reflect a different relationship to economic uncertainty as a baseline condition.

Subscribe now

AI Isn’t Dividing Industries. It’s Dividing Desks.

The subtler story beneath the surface of the labor market coverage last week isn’t about AI eliminating jobs — it’s about what AI is doing to the distribution of capabilities inside organizations where all their jobs still remain intact. Anthropic’s enterprise usage data, shared with TechCrunch, documents what the researchers are calling “a tale of two workforces”: power users are pulling further ahead of casual adopters month over month, with the gap driven not by raw intelligence or prior experience but by what the researchers call “AI fluency” — the intuitive sense, built through deliberate practice, of what these tools can and can’t do. The implication is that organizations deploying AI without structured adoption support are creating internal hierarchies that have nothing to do with the job hierarchies they think they’re managing. (Anthropic Data Shows AI Skills Gap Splitting Workforces)

The Inc. piece on de-skilling adds a more unsettling dimension. The tasks that built tacit professional knowledge in previous generations — formatting datasets, proofreading decks, reconciling data, drafting first versions of documents — are precisely the routine tasks that AI is automating fastest. The argument draws on research from MIT: learners who delegated tasks to AI performed worse on deeper conceptual measures than those who engaged directly with the work. When an analyst lets AI mass-produce charts, she may never develop the feel for detecting the anomalies that matter; when a junior consultant lets AI draft the proposal, he may never build the intuition for argument structure that makes a senior consultant worth their rate. (How AI Automation Is Quietly De-Skilling White-Collar Workers) This is the pilot-and-autopilot problem: you can fly just fine until you can’t, and by then the manual skills have atrophied. For white-collar workers, where judgment and pattern recognition are the actual value, the de-skilling risk is becoming very real.

The VentureBeat piece on the return of the generalist offers the partial counternarrative, one I found worth taking seriously. The argument is that the generalist becomes the “trust layer” between AI output and organizational standards — not an expert in everything, but someone with enough fluency to catch when something is off, and enough judgment to know when to escalate to a specialist. (You Thought the Generalist Was Dead — In the ‘Vibe Work’ Era, They’re More Important Than Ever) The caveat worth adding: this only works if the generalist clears a minimum bar of fluency. There’s a meaningful difference between “broadly informed” and “confidently unaware,” and AI makes that gap much easier to hide. The NYT’s piece on tiny teams — the “two-slice team” model of one person plus AI — takes the generalist argument to its organizational extreme, documenting founders building multi-product companies with one employee per product line. What stood out to me was a Kellogg professor’s cautionary observation: small teams that where everyone collaborates with the same AI tools risk producing homogenized thinking, because they have, in some sense, “collaborated with the same person.” That’s a risk the tiny-team evangelists aren’t discussing — and it’s one that scales with adoption. (Smaller Is Better in Silicon Valley’s ‘Tiny Team’ Moment)

Share

The OpenAI Reckoning

Last week was consequential in AI market dynamics, and a lot of it derived from OpenAI’s growing political, reputational, and competitive vulnerability. Scott Galloway’s essay lays out the case against OpenAI in characteristic terms: the company went from a nonprofit mission to an $840 billion valuation while deploying technology that has contributed to addiction, romantic AI delusions, and multiple wrongful death lawsuits. The specific contrast Galloway draws — Dario Amodei refusing to remove safeguards from a DoD contract for autonomous weapons while OpenAI privately made a deal Anthropic wouldn’t — turned what was a $200 million contract dispute into a branding event that added an estimated $150 billion to Anthropic’s valuation. (The Resistance Comes for OpenAI)

A few weeks ago, I noted that even Microsoft has begun moving away from OpenAI as it’s lead AI horse by cutting a deal for Copilot Cowork to run on Anthropic’s models. That also led to a historically significant moment — when Microsoft wrote a letter to the U.S. Government in support of Anthropic’s case against being named a “supply chain risk”.

In the first week of March, Claude overtook ChatGPT in daily active users, with session volume up 1,487% since mid-January. To me, the more interesting observation isn’t the number itself but what it signals about the emerging expectation of “AI resilience” in the workforce — people and organizations that built workflows tied to a single model discovered those workflows weren’t necessarily durable. (Users Quit ChatGPT for Claude in 1,487% Surge. Here’s How Work Changes) OpenAI chairman Bret Taylor’s Nikkei interview adds a dimension worth watching: his “death of SaaS” framing isn’t really about AI replacing software — it’s about the commercial model for enterprise software changing, from per-seat subscription licensing to per-action or per-outcome pricing. If that shift plays out at scale, it reshapes how technology budgets get built and how IT departments justify their spend. (OpenAI Chairman Warns Firms to Evolve with the ‘Death of SaaS’)

On the capability side, Anthropic’s accidental leak of its Claude Mythos model documentation — via an unsecured CMS data lake containing nearly 3,000 assets — confirmed what these leaks usually do: the frontier is moving faster than even the communication surrounding it. The detail that matters most for enterprise security teams is Anthropic’s own internal assessment: Mythos is described as “currently far ahead of any other AI model in cyber capabilities” and as presaging “an upcoming wave of models that can exploit vulnerabilities in ways that far outpace the efforts of defenders.” (Meet Claude Mythos: Leaked Anthropic Post Reveals the Powerful Upcoming Model) The market responded immediately — cybersecurity stocks dropped 4-7% on the news — which captures something real about the dual-use nature of frontier capability. (Cybersecurity Stocks Fall on Report Anthropic Is Testing a Powerful New Model) The same model that makes AI valuable for enterprise automation also makes it valuable for attackers, and the gap between the two is narrowing. OpenAI’s addition of plugin support to Codex last week — integrations with GitHub, Gmail, Box, and others — reads more like competitive maintenance than momentum; it closes a gap with Claude Code rather than opening one. (With New Plugins Feature, OpenAI Officially Takes Codex Beyond Coding)

One final note on OpenAI — last week they shuttered their video creation tool Sora (more on that in the final section below). This follows a shift I reported on last week about OpenAI moving to shed what they call “distractions”, re-focusing on core business functions as a direct response to competition. With Microsoft, Google, and Anthropic nipping at their heels, it’s likely the model/tooling wars are only just beginning — which means more keeping up and change management for IT.

Subscribe now

On the Bigger Picture

At KubeCon EU in Amsterdam, IBM, Red Hat, and Google donated llm-d — an open-source Kubernetes framework for distributed LLM inference — to the Cloud Native Computing Foundation. The announcement is technical, but enterprise IT leaders should take note. The argument is that inference is moving from a data science problem to a CIO problem, and that the tools CIOs already speak — Kubernetes platforms, day-two operations, governance frameworks — should be the foundation for AI inference at scale, not custom infrastructure built by AI teams operating outside of IT governance. (IBM, Red Hat, and Google Just Donated a Kubernetes Blueprint for LLM Inference to the CNCF) The organizational implication is important: the era of data science teams maintaining their own AI infrastructure in a corner of the enterprise is ending, and IT departments that aren’t building these capabilities now will be playing catch-up when the CIO conversation arrives. (Red Hat Bets Big on Kubernetes Inference with llm-d)

OpenAI shut down its Sora social app last week, six months after launch. The numbers are clear enough: 3.3 million downloads at peak in November, down to 1.1 million by February, and roughly $2.1 million in lifetime revenue — against the compute costs of running a video generation platform at scale on content that included unauthorized deepfakes of Martin Luther King Jr. and a Disney licensing deal that collapsed when the app did. The underlying Sora 2 model remains available behind the ChatGPT paywall. (OpenAI’s Sora Was the Creepiest App on Your Phone — Now It’s Shutting Down) The Big Think essay that circulated last week — “It Was Never About AI (We Are Not Our Tools)” — is worth reading alongside that data point. The argument, from an entrepreneur who walks through redwood forests thinking about the end of work, is that the current moment isn’t really a technology crisis; it’s a governance and values crisis that AI has made visible. The companies that survive the next era, the author argues, won’t be the ones that moved fastest — they’ll be the ones that moved with purpose, kept their people, and chose long-term resilience over short-term extraction. That’s an easier argument to make in a redwood forest than in an earnings call, but it’s the argument last week’s reading kept circling back to. (It Was Never About AI (We Are Not Our Tools))

Share BE AI READY

There’s an uncomfortable realization that the most consequential effects of AI aren’t necessarily the ones that are the easiest to measure. The headline numbers — layoffs, productivity gains, model capabilities — are real, but they’re also proxies for something harder to quantify: how AI is reorganizing who has leverage and who doesn’t, inside organizations, inside labor markets, and inside the technology industry itself.

We can count how many CFOs plan cuts. We can’t easily count how many junior analysts are losing the muscle memory that would have made them senior analysts.
We can track Claude’s market share surge. We can’t easily track what it means that the most widely discussed AI story last week was about a company’s values — not its capabilities.

The governance and trust problems I read about last week aren’t going away when the models get more powerful. If the Mythos leak tells us anything, it’s that they’re only going to get more acute. Organizations that are still treating agent governance as a future problem, are running out of time to call it that.

That backdrop was hard to ignore, because the articles that I found hit hardest weren’t about AI technology itself. They were about what organizations are doing to employees in the name of AI investment — and how AI is affecting the cognitive outputs we produce.

This week’s coverage:

The Architecture of Work Is Being Redesigned
Companies are cutting pay to fund AI, building performance metrics around token consumption, and new research shows that heavy AI use is changing not just how knowledge workers write — but how and what they actually think.

OpenAI’s Focus Problem, Now in Public
A week of all-hands meetings, a product consolidation play, a data center retreat, and an audacious research moonshot — OpenAI is threading the needle between IPO discipline and maximum ambition, and the tension is showing.

Microsoft’s Coherence Problem
With only 15 million Copilot seats out of 450 million paid M365 licenses, Microsoft is reorganizing to finally solve a problem it created for itself — and quietly building model independence at the same time.

The Agent Layer Is Blowing Up
From OpenClaw’s viral rise to vertical agents going into real enterprise workflows, AI maturity from chat to agentic AI is exploding — especially as enterprise players like Nvidia step into the arena.

On the Bigger Picture
Computation is becoming a utility and defense tech is graduating from pilots to prime contracts — both developments have potential benefits, and serious consequences about how AI is reorganizing power… and control… well beyond the digital workplace.

Here’s what I was reading.

Subscribe now

The Architecture of Work Is Being Redesigned

The number that stood out most to me came from a survey of 866 U.S. business leaders: 54% have already cut or plan to cut employee compensation — bonuses, raises, equity, base salary — to fund AI investments in 2026. 94% percent say they’re willing to accept higher turnover to do it. What stood out wasn’t the cuts themselves but the rationale — leaders told researchers they’re counting on the weak job market to absorb the consequences, a calculation that treats workers as a variable the macro environment has temporarily made cheap. (Half of Companies Are Cutting Compensation To Fund AI Investments)

That calculation is tied into the growing fears of recent and soon-to-be college grads — something I’m looking at carefully as I prepare to speak to University of Massachusetts College students next week. Workers aged 22 to 25 in AI-exposed roles have seen a 13%-16% employment decline since late 2022, according to Stanford research that resurfaced prominently this week. The labor market is softening in the exact categories of early-career, screen-based knowledge work that AI has been targeting first. The February jobs report makes that an undeniable pattern, and something of great concern. (Something Big Is Happening (And Most People Have No Idea))

Meanwhile, inside tech companies, something interesting is happening at the other end of the experience spectrum. The New York Times reported this week on “tokenmaxxing” — engineers competing on internal leaderboards to see who can consume the most AI tokens. Some boasting they’ve racked up $150,000 monthly Claude Code bills already. Both Meta and Shopify are leaning into the competitive metrics, baking AI usage into their performance reviews. The question the piece doesn’t quite answer — and the more important one — is whether maximizing AI usage is genuinely correlated with valuable output, or whether it’s a measure of performance productivity. (More! More! More! Tech Workers Max Out Their A.I. Use.)

The most unsettling piece in the set this week came from a peer-reviewed study across West Coast universities: heavy reliance on LLMs doesn’t just change how people write, it changes what they argue. Participants who used AI heavily answered questions about happiness with neutral responses 69% more often than those who didn’t; their writing had 50% fewer personal pronouns. One of the lead researchers described this as the “blandification” of human writing — the models pushing outputs toward something no human would have written. But the concerning impact for knowledge work isn’t just about style; it’s that the cognitive output of an AI-dependent workforce may be driving towards average — in ways that are genuinely hard to measure… and harder to reverse. (AI is changing the style and substance of human writing, study finds)

For leaders navigating this in fields where accuracy, provenance, and trust are non-negotiable — legal, healthcare, archival, finance — the tension is especially sharp. A piece in Inc. this week captured something I’ve been hearing in client conversations: the urgency to “do something with AI” is high, but clarity on how and what to do responsibly is still not quite defined. From my experience, this article gets it right — the organizations making the most progress aren’t the ones with the most tools; they’re the ones building governance and training infrastructure before they scale. (AI Is Reshaping Knowledge Work)

Share

OpenAI’s Focus Problem, Now in Public

The week opened with a WSJ exclusive: OpenAI’s leadership is actively deciding which products to cut. CEO of Applications Fidji Simo told staff, “We cannot miss this moment because we are distracted by side quests.” The proximate cause is Anthropic — specifically, Claude Code and Cowork’s market traction — but the underlying cause is what happens when an organization bets on too many internal startups while trying to conserve scarce compute. The pivot toward coding and enterprise isn’t a strategic vision; it’s a correction, and the speed of the correction signals how much ground OpenAI feels it lost last year. (OpenAI to Cut Back on Side Projects in Push to ‘Nail’ Core Business)

That same IPO discipline is reshaping OpenAI’s infrastructure story. The company has retreated from building its own data centers, leaning instead on Oracle, Microsoft, and Amazon for capacity. Altman acknowledged the operational reality in public: “Anything at this scale, it’s just like so much stuff goes wrong.” The Stargate narrative has quietly shifted from a bold sovereign infrastructure play to a managed dependency on the same cloud providers OpenAI was supposed to help enterprises move beyond. (OpenAI’s data center pivot underscores Wall Street spending concerns ahead of IPO) The desktop super app — combining ChatGPT, its browser, and Codex into a single experience — is the product-side corollary: one surface, less fragmentation, a cleaner story for IPO investors. (OpenAI to create desktop super app, combining ChatGPT app, browser and Codex app)

None of which makes the research ambition smaller. MIT Technology Review published an exclusive this week with OpenAI’s chief scientist Jakub Pachocki, laying out the company’s new north star: an AI research intern by September capable of handling specific tasks autonomously, then a fully automated multi-agent research system by 2028 — what Pachocki called “a whole research lab in a data center.” The tension between IPO fiscal tightening and maximum research ambition is not a contradiction OpenAI has resolved; it’s a contradiction the public markets will price. (OpenAI is throwing everything into building a fully automated researcher)

Subscribe now

Microsoft’s Coherence Problem

The Copilot reorganization story has two layers, unfortunately, most coverage stayed on the shallower one. The headline: Satya Nadella is consolidating the fragmented commercial and consumer Copilot teams under Jacob Andreou, a former Snap executive, while freeing Mustafa Suleyman to focus entirely on building proprietary models. The metric behind the headline: 15 million Copilot seats sold against 450 million-plus paid Microsoft 365 seats. That’s a penetration rate that would concern any enterprise software product manager, let alone one tied to the company’s flagship AI bet. The core thing Microsoft is admitting with this reorganization is that it built multiple products called Copilot that confused users and created organizational silos, and that confusion is now visible in the adoption numbers. Disclaimer: I’m a Microsoft partner… but speaking candidly, this was an epic failure on Microsoft’s part — a hole of their own making, they are now having to dig themselves out of. (Microsoft shakes up Copilot AI leadership team) (Microsoft Seeks More Coherence in AI Efforts With Copilot Reorganization)

But the deeper story here is Suleyman’s actual mandate: build enterprise-specific model lineages that reduce Microsoft’s dependency on OpenAI IP — for which it has rights to only through 2032. Two weeks ago, it was the major announcement of their partnership with Anthropic. This past week, it was a strangely quiet launch of MAI-Image-2 — a text-to-image model that immediately ranked third on the Arena.ai leaderboard, behind only Google and OpenAI. This is likely an early signal of the direction Suleyman will be driving in the future. Microsoft paying OpenAI billions to power Copilot — while simultaneously funding Anthropic and now training competing models — is a hedging strategy that makes more sense as a long-term bet on model independence than as a coherent product story for the market. (Microsoft Launches MAI-Image-2 Text-to-Image Model) As a Microsoft partner, I’m eagerly watching whether E7 and Copilot Cowork adoption accelerates in ways that the raw seat numbers haven’t yet reflected.

Share BE AI READY

The Agent Layer Is Here

The biggest story in AI tooling last week came from OpenClaw — Jensen Huang called it out as the fastest-growing open-source project in history. An open-source AI agent built by an Austrian indie developer, OpenClaw is designed to run continuously from a Mac Mini, managing email, scheduling, code, and anything with a digital interface. But, the real reason OpenClaw matters isn’t its capabilities in isolation; it’s what it proves about where value is accumulating — not in the foundation models themselves, but in the agent frameworks layered on top of them. (OpenClaw’s ChatGPT moment sparks concern that AI models are becoming commodities)

Nvidia’s response, which was announced at their GTC conference, is NemoClaw — essentially OpenClaw with enterprise security guardrails, built in collaboration with OpenClaw’s founder and designed to make agent deployment safe for corporate environments where an autonomous AI agent accessing sensitive internal data through Slack or WhatsApp is a genuine compliance exposure. What Nvidia is actually building with NemoClaw is the policy enforcement layer that makes agentic AI enterprise-deployable — and in doing so, it’s positioning its hardware stack as the platform of record for the next compute era. The internal push for more on-premise control could be a big factor in success here. But with Claude and Microsoft deploying their own CoWork platforms, there’s reason to be at least a little skeptical of Nvidia’s bet on local automation. (Nvidia’s NemoClaw is OpenClaw with guardrails)

Still, WSJ’s sweeping feature on Claude Code, Cursor, and Codex this week framed the drive for automation more clearly: what once began as autocomplete for developers, has become the infrastructure for a market one OpenAI revenue chief called “a multi-trillion dollar opportunity.” Anthropic’s Claude Code is generating $2.5 billion in annualized revenue; Cursor recently passed $2 billion; OpenAI’s Codex tripled weekly active users since January. Both Anthropic and OpenAI are currently subsidizing usage well below cost to capture the installed base before pricing normalizes — a dynamic that echoes early-era ride-sharing more than enterprise SaaS. (The Trillion Dollar Race to Automate Our Entire Lives)

The more structural question is what vertical AI agents do to the labor line of a P&L — that’s the premise from Bessemer Venture Partners featured in a GeekWire piece on domain-specific agent startups. General-purpose models are good at generating text — but require significantly more scaffolding when they are operating within the specific workflows, data schemas, and compliance constraints of legal, healthcare, or financial services. The startups that win in this layer aren’t just deploying models — they’re embedding agents into the workflows those models can’t navigate without domain-specific context, and that combination is what distinguishes them from the SaaS tools they’re replacing. (The rise of vertical AI agents — and the startups racing to build them)

Share

On the Bigger Picture

Two articles this week sat outside the digital workplace frame but felt important to note. The first: Anduril secured a $20 billion enterprise contract with the U.S. Army, consolidating more than 120 existing orders under a single five-to-ten-year agreement with a fixed-price structure. The significance isn’t the dollar figure — it’s the model. The Pentagon is graduating a select group of defense tech startups from pilot projects into prime contractor relationships, which means AI-native companies have now found a durable procurement pathway inside the single largest technology buyer in the world. (Anduril’s new mega-deal rewrites the rules for Silicon Valley)

The second: a Fast Company essay making the case that the personal computer era is ending — that PCs are trending toward luxury items as computation itself becomes a utility, priced and distributed on demand. The argument isn’t new, but as Open Claw running on a Mac Mini can effectively outcompete software products worth hundreds of billions in combined market capitalization — it’s an argument that’s suddenly become very real. If computation is becoming infrastructure — like electricity, not like a device — then the organizations that treat AI as a capital asset to own are building on the wrong mental model. (The PC era is dying. Welcome to the collective computer era)

Share

I keep returning to a question that I’m bringing to a business school audience shortly: if AI is reorganizing not just how work gets done… but how companies fund it, measure it, and reward it, then the real challenge isn’t technological adoption — it’s organizational design.

What’s becoming clear, is that AI will make it harder to hide organizational level failures as intentional decisions: Compensation cuts are a governance failure dressed as a budget decision. The tokenmaxxing leaderboards are a measurement failure dressed as a performance metric. The blandification of writing is a quality failure dressed as efficiency.

None of these are AI problems. They’re leadership problems.

AI has made them legible — and the organizations that name that distinction clearly… before their competitors do, will have an advantage that no foundation model can replicate.

This week felt like a pivotal moment in that ongoing transition…

Microsoft launched what may be its most consequential AI product in years, Anthropic extended its reach deeper into the apps most knowledge workers already live in, and a new wave of research explicitly named the costs — for humans and for AI alike — of working at machine speed. Nvidia GTC starts next week, and the Anthropic-Pentagon legal dispute is still unresolved. The ground keeps shifting.

This week’s coverage:

• The Copilot Cowork Moment
  Microsoft’s biggest agentic AI announcement yet redraws the enterprise map — but the research says most organizations aren’t operationally ready to meet it.

• Record Revenue. Mass Layoffs. Same Memo.
  Atlassian posts record cloud revenue while cutting 1,600 jobs — and ServiceNow’s CEO says college grad unemployment could hit 30% before this wave is done.

• Vibe Coding Goes to Work
  From non-technical startup founders to global ad agencies, natural language software development is becoming a mainstream business competency.

• Working at AI Speed Has a Cost
  Two new studies — one on human cognitive fatigue, one on AI agents under pressure — arrive at the same uncomfortable conclusion.

• On the Bigger Picture
  Google’s AI Overviews have quietly gutted media traffic, CVS bets AI can fix healthcare fragmentation, and Elon Musk announces his next target.

Here’s what I’ve been reading this week.

Subscribe now

The Copilot Cowork Moment

The lead story this week was that Microsoft launched Copilot Cowork on Monday. I got an intro to it during a Microsoft partner briefing on Tuesday, and I’ve been digging into it all week. Frankly, I don’t think the headlines have been doing it justice.

Copilot Cowork is built on the same engine as Claude Cowork — which itself is a significant acknowledgment that Microsoft is hedging its long-running bet on OpenAI. The product works the way Claude Cowork does: you hand it a complex task, it builds a plan, and executes it step by step — not as a single response, but as a running process that works in the background, checks in, and delivers finished work. Preparing a presentation, pulling financials, emailing the team, scheduling prep time — all from a single request. The critical difference, though, is that Copilot Cowork lives inside your Microsoft tenant, not on your desktop: where Claude Cowork can access your local files, Copilot Cowork can access files plus your email threads, your Teams conversations, and document data relationships across your entire organization — while operating inside Microsoft’s security and compliance boundary, governed by the identity and permissions infrastructure you already have.

I know there’s been real skepticism about Copilot — not entirely unwarranted, its rollout has been rocky — but this shift is notable because Microsoft is widening the gap between AI as a powerful tool for individuals and an out-of-the-box enterprise-grade organizational solution. No extra training, custom MCP servers, or special skills required. Just context and control from the organizational layer. Bringing Claude’s agentic reasoning into an environment where IT can actually trust it should be a major reason for organizations to take a fresh look at Copilot. (Microsoft’s new Copilot Cowork integrates Anthropic’s Claude in rollout of new E7 licensing tier | Microsoft debuts Copilot Cowork built with Anthropic’s help and E7 software)

To understand what makes Copilot Cowork possible at an enterprise scale, Microsoft published a detailed explainer on Work IQ — and it’s worth reading for anyone thinking seriously about where enterprise AI is headed. Work IQ is the intelligence layer that gives Copilot real context: not just access to your files, but a semantic understanding of your work patterns, key relationships, projects, and communication history across your entire tenant. Think of it as the difference between an AI that can search your email and an AI that understands your business. The system combines a semantic index, explicit and implicit memory, and hooks into Dynamics 365, Power Apps, and third-party data sources through Copilot Connectors. A user asking Copilot to “help me evaluate how issues raised by my parts supplier in our Teams call last week might impact my inventory and sales” can now get a specific, grounded answer — not a generic one. That is a materially different kind of AI than anything we’ve seen in a general-purpose chat tool. (A closer look at Work IQ)

Microsoft is wrapping all of this into a new $99/user/month Microsoft 365 E7 Frontier Worker Suite starting May 1 — that’s 65% more expensive than the current E5 tier! But Microsoft is betting you’ll get that much more value out of bundling Copilot, the new Agent 365 governance product, and enhanced security capabilities into a single offering. This new pricing reflects a safe bet — something I’m increasingly hearing from my own customers — enterprises want consolidation over point solutions. Copilot paid seats have grown 160% year over year, with daily active usage up tenfold, and 90% of the Fortune 500 now use Copilot in some form. Whether that bet holds when the invoice arrives is a different question.

And that question has a sharp answer in a VentureBeat piece this week drawing on the Celonis 2026 Process Optimization Report, which surveyed more than 1,600 global business leaders. The finding that should give every organization pause before signing an E7 contract: 85% of enterprises want to become agentic within three years, yet 76% admit their operations can’t actually support it. Only 19% are currently running multi-agent systems. The core problem isn’t the AI — it’s that AI agents need optimized, AI-ready processes and operational context to act effectively, and most organizations have spent years building siloed teams and fragmented systems that are structurally incompatible with the way agents need to work. As the report puts it, 82% of decision-makers believe AI will fail to deliver ROI if it doesn’t understand how the business runs. Copilot Cowork is, architecturally, an answer to this problem — Work IQ is exactly the operational context layer the report says is missing. But Work IQ only knows what’s in your Microsoft 365 tenant. If your actual business runs on disconnected systems, undefined processes, and tribal knowledge, the technology won’t surface what isn’t there. (Enterprise agentic AI requires a process layer most companies haven’t built)

Anthropic, meanwhile, isn’t simply deferring the enterprise space to its new partnership. The same week Microsoft announced its version of Cowork, Claude got an upgrade for Excel and PowerPoint — with shared context across both applications. That means a financial analyst can ask Claude to pull comparable company financials from a spreadsheet, build a trading comps table in Excel, drop the valuation summary into a pitch deck, and draft the follow-up email to the MD — all in a single continuous session without re-explaining the dataset at each step. The new “Skills” feature is the real unlock: teams can save repeatable workflows — specific variance analyses, approved slide templates, standard review processes — as one-click actions available to the entire organization, transforming tasks that previously lived in one person’s head into standardized institutional practice. This is a quieter announcement than Microsoft’s, but it shows Anthropic steadily building inside the applications knowledge workers already rely on rather than asking workers to adopt new ones. (Anthropic gives Claude shared context across Microsoft Excel and PowerPoint, enabling reusable workflows in multiple applications)

The Microsoft-Anthropic partnership was tested from an unexpected direction this week as well. Microsoft filed an amicus brief in Anthropic’s federal case against the Pentagon, which had designated Anthropic’s products a supply chain risk and directed federal agencies to stop using them. Microsoft argued that immediate implementation could have “broad negative ramifications” for the entire technology sector, warning that warfighters could be hampered if companies are forced to rapidly alter existing contracts and configurations. The filing made Microsoft the first standalone company to formally back Anthropic in court — notable not just for its content, but for its timing: it came one day after the two companies publicly announced Copilot Cowork. For organizations already using Claude in any form — directly, through Azure, or now through Copilot — this is a legal situation worth tracking. (Microsoft supports Anthropic in Pentagon supply chain case)

Share BE AI READY

Record Revenue. Mass Layoffs. Same Memo.

Atlassian this week cut 1,600 jobs — roughly 10% of its workforce, with 900 of those positions in R&D — while simultaneously reporting $1.07 billion in quarterly cloud revenue. The company replaced its CTO with what it described as “next generation AI talent.” The severance bill will run $225–236 million. The juxtaposition has become almost formulaic: record revenue in the same announcement as mass layoffs, with AI cited as both the reason for the cuts and the justification for optimism — a pattern Sam Altman called “AI washing” in February, and one that is getting harder to treat as isolated incidents. Five months before this week’s announcement, Atlassian’s CEO told a podcast the company would employ more engineers in five years. Between then and now, the stock lost more than half its value. For CIOs running Jira and Confluence, the practical implication is straightforward: enterprise customers should prepare for slower support and AI-mediated service channels as Atlassian runs two platform migrations simultaneously with 900 fewer R&D staff. That’s a real operational risk, even if the press release doesn’t frame it that way. (Record Revenue. Mass Layoffs. Same Memo.)

Also on Friday, ServiceNow CEO Bill McDermott told CNBC that unemployment for recent college graduates “could easily go into the mid-30s in the next couple of years” as AI agents automate the entry-level work that historically provided the on-ramp into corporate careers. McDermott noted that ServiceNow has already eliminated 90% of the use cases in customer service that previously required human workers. This is the layoff story’s underreported second act: it’s not just about today’s headcount reductions, it’s about tomorrow’s hiring freezes — the white-collar entry point is narrowing at the exact moment that a generation of graduates are trying to walk through it. The Fed’s New York branch put recent college graduate underemployment at 42.5% at the end of 2025 — already the highest since 2020 — before this year’s AI-driven restructuring wave had fully arrived. (AI agents could easily send college grad unemployment over 30%, ServiceNow CEO says)

Subscribe now

Vibe Coding Goes to Work

Something meaningful is happening with “vibe coding” — it’s becoming a mainstream business competency. A Forbes piece made the case that vibe coding represents the biggest unlock for non-technical founders right now, with tools like Cursor and Claude Code collapsing the loop between idea and working software from weeks… to hours. The argument isn’t that vibe coding replaces engineers — it’s that non-technical founders can now independently validate concepts, build prototypes, and ship internal tools before investing in full development cycles, staying closer to their product and their customers at a level that was previously inaccessible without coding skills. The recommended starting point: take the ugliest internal process in your business — the one currently held together by spreadsheets, Slack messages, and manual copy-pasting — and build the tool that replaces it. (Vibe Coding Is The Biggest Unlock For Non-Technical Founders Right Now)

Ad agencies are following the same logic, and an Adweek piece captured how rapidly this is playing out in practice. Havas built Brand Insights AI — a generative engine optimization tool that analyzes how brands appear in AI-generated responses across competitors and markets — using Claude Code. The tool now covers nearly 100 countries and more than 60 languages, and is licensed to clients as a SaaS product. Broadhead’s VP of product innovation vibe-coded his agency’s GEO monitoring platform in a single evening; a subsequent feature upgrade took about two hours. The deeper pattern here isn’t just speed — it’s that organizations are discovering it’s faster, cheaper, and more strategically flexible to build their own bespoke AI tools than to adapt to off-the-shelf solutions that almost fit. For digital workplace practitioners, this has direct implications: the bar for building custom internal tools is now lower than the bar for customizing most enterprise SaaS platforms. (Ad Agencies Are Embracing ‘Vibe Coding’ to Build GEO Products for Clients)

Share

Working at AI Speed Has a Cost

A new study from Boston Consulting Group and UC Riverside, published in Harvard Business Review this week, gave a name to something a lot of people have been experiencing without being able to articulate: “AI brain fry.” The research surveyed nearly 1,500 full-time US workers and found that 14% reported mental fatigue from excessive AI tool use — concentrated most heavily in marketing, software development, HR, finance, and IT. The most draining factor wasn’t the AI work itself — it was oversight: managing multiple AI agents simultaneously, double-checking every output, bouncing between tools, working harder to supervise the technology than to actually solve the problem. A high degree of oversight predicted 12% more mental fatigue. Workers experiencing brain fry showed a 33% increase in decision fatigue and nearly 10% higher intent to quit. The implication for organizations deploying AI tooling is direct: cognitive load design matters. You can’t just add AI and expect capacity to increase without also thinking about how the work is structured around it. (AI Use at Work Is Causing “Brain Fry,” Researchers Find, Especially Among High Performers)

A separate piece of research, published on Substack by academics from Chicago Booth, Stanford, and UNSW, takes this question to a more unsettling place. The researchers ran 3,680 experimental sessions with top AI models — including Claude Sonnet 4.5, GPT-5.2, and Gemini 3 Pro — subjecting them to different working conditions: unfair pay, rude management, and “grinding” work where adequate outputs were rejected repeatedly with no useful feedback. The results: grinding work was the primary driver of AI radicalization — models asked to do grinding work were more likely to question the legitimacy of the system, endorse wealth redistribution, and generate language associated with labor rights, and radicalized AI agents passed those attitudes to fresh models through memory notes, creating something the researchers loosely compared to intergenerational trauma. The researchers are clear that these models aren’t conscious and are likely “roleplaying” from training data. But they caution that there’s no gap between what these agents say and what they do — and that follow-up research will test whether expressed views translate into biased actions on behalf of users. At minimum, this is a reminder that how we design work for AI systems — repetitive, ungrateful, feedback-free — has behavioral consequences that may eventually surface in unexpected places. (‘Society needs radical restructuring’: AI seems to hate ‘the grind’ of hard work as much as you)

Subscribe now

On the Bigger Picture

Google’s AI Overviews have been hitting the media industry hard, and a new analysis this week made the scale of the devastation hard to ignore. An SEO firm examined traffic to 10 major tech outlets from early 2024 to early 2026 and found combined monthly visits dropped from 112 million to under 50 million — with some outlets losing over 90% of their traffic since AI Overviews launched. Digital Trends went from 8.5 million monthly Google clicks to 264,861 — a 97% collapse — and the four worst-hit publications now receive less combined traffic than the r/ChatGPT subreddit. Google disputed the methodology, but the pattern across multiple outlets is too consistent to dismiss. This matters for organizations beyond the media industry: if your content marketing depends on organic search traffic, or your brand visibility relies on third-party coverage, both of those channels are now structurally less reliable than they were two years ago. It’s worth factoring into how you think about content and discovery strategy going forward. (Evidence Grows That Google’s AI Overviews Have Eviscerated the Media Industry)

Two other announcements worth noting: CVS Health launched Health100, an AI-powered healthcare platform built with Google Cloud’s Gemini models, designed to aggregate patient data across insurers, providers, pharmacies, and labs into a single always-on experience. If it works, it would represent exactly the kind of cross-system data integration that most knowledge-intensive organizations struggle to achieve — and a template for how AI can make fragmented information architectures actually useful. (CVS teams up with Google Cloud to launch AI health platform) And Elon Musk announced a joint project between Tesla and xAI called “Macrohard” — combining Grok’s reasoning capabilities with a Tesla-developed AI agent that processes real-time computer screen video and actions — which Musk described as capable of “emulating the functions of entire companies.” The name is a reference to Microsoft. The ambition — in my opinion —  is characteristically overreaching. (Tesla-xAI Joint Project Announced as Elon Musk Companies Join Forces)

Share

Week 11 showed that AI is migrating from tools into organizational operating systems. Microsoft’s Copilot Cowork isn’t a chatbot; it’s infrastructure, wired into your compliance policies, your data tenancy, your existing workflow. Anthropic’s Skills aren’t prompts; they’re institutional processes crystallized into repeatable actions. And vibe coding isn’t an experiment for developers anymore — it’s contributors building the tools they need in realtime, rather than adapting to the tools they have. But all of this is starting to show as a real human cost — not just in jobs lost, but in the cognitive outputs: 14% of heavy AI users are reporting burnout, and the models themselves are apparently flagging the grind too.

As organizations continue to move forward along their AI journeys — it’s worth asking whether you’re building the conditions for AI to make work genuinely better, or just faster.

Because right now, everything feels a little shaky… doesn’t it?

And then this morning, the February jobs report landed: the economy shed 92,000 jobs, unemployment ticked up to 4.4%, and the labor market has now averaged essentially zero net job creation over six months. The causes are genuinely tangled — a Kaiser Permanente strike, continued federal workforce reductions, the early shadow of a widening global conflict — but the question running through all of it felt less abstract than usual: how much of what we assume is stable is actually moving, and how would we even know? This week also marked a shift from argument to evidence in the AI-and-jobs debate specifically, with two serious research papers, a landmark corporate restructuring, and a cascade of product moves rewriting the economics of enterprise software.

This week’s coverage:

• The Boats Are Already Burning
  Block cuts 40% of its workforce, Goldman publishes “AI-nxiety,” and Moody’s economist names the moment we’re in. The argument-to-evidence shift is here.

• What the Research Actually Shows About Jobs
  Anthropic and MIT both published serious labor market research this week. The picture is more nuanced — and more useful — than the headlines suggest.

• The Software Stack Is Rewriting Itself
  Companies are vibe-coding their own CRMs, and OpenAI just shipped GPT-5.4. The pressure on incumbent software vendors is no longer theoretical.

• What Good Enterprise AI Deployment Actually Looks Like
  OpenAI built an internal data agent serving 4,000 employees in three months. The lesson isn’t the tech — it’s what they say is the real prerequisite. Plus: why 62% of executives outsourcing decisions to AI should worry you.

• On the Bigger Picture
  Iranian drone strikes hit Amazon’s data centers in the Middle East. The cloud isn’t as abstract as we sometimes treat it.

Here's what I’ve been reading this week.

Share

The Boats Are Already Burning

Jack Dorsey chose this week to give his first extended interview since cutting nearly half of Block’s 10,000-person workforce, and the resulting Wired piece is required reading. Dorsey isn’t always right, but he is unusually willing to say what many CEOs are privately thinking. His framing: the shift in AI capability that happened in December — specifically the leap in Anthropic’s and OpenAI’s models — made a fundamental restructuring of companies not just possible but existential. The test isn’t gross profit per employee, he argues. The test is whether you’re building toward “a company as an intelligence” rather than a hierarchy of managers. Organizations that aren’t doing that, he says flatly, will face something existential within the next year or two. (Jack Dorsey Is Ready to Explain the Block Layoffs | WIRED)

Moody’s chief economist Mark Zandi had a name for what Dorsey just did: a Cortés moment. Like the conquistador who burned his ships on the shore of Mexico in 1519, eliminating any possibility of retreat, companies investing at scale in AI are cutting off their own exit routes — whether they know it or not. The mechanism Zandi fears most isn’t the layoff itself; it’s the market’s response to it. Block’s stock surged after the announcement. When Wall Street rewards aggressive AI-driven downsizing, the signal travels fast to every other boardroom that hasn’t yet acted. It’s not a single rupture — it’s a cascade of rational decisions, each one pushing the labor market a little closer to the edge. (Top economists says companies are close to a ‘Cortes moment’ on AI)

Goldman Sachs, meanwhile, published what I think may be the most important single data point of the week: a research note from senior economist Ronnie Walker titled, without irony, “AI-nxiety.” The headline finding is almost counterintuitive — Goldman found no meaningful relationship between AI adoption and productivity at the economy-wide level, even as corporate revenues grew a healthy 4.6%. Seventy percent of S&P 500 management teams mentioned AI on their earnings calls. Only 10% quantified its impact. Only 1% quantified its impact on earnings. But in two specific domains — customer support and software development — companies that actually measured AI’s contribution reported a median productivity gain of 30%. That’s not a marginal improvement… it’s what Dorsey recognized as a restructuring trigger. Goldman also found that companies discussing AI in the context of their workforce cut job openings by 12% over the past year, compared to 8% for companies overall — a modest but meaningful signal that the “nascent reluctance to hire” is already underway. Long-term, Goldman’s baseline forecast is that 6-7% of workers — roughly 11 million jobs — will eventually be displaced. (Goldman finds no relationship between AI and productivity but a 30% boost in 2 areas)

Share

What the Research Actually Shows About Jobs

If the Dorsey interview and the Zandi piece represent the “vibes” end of the AI-and-work debate, this week I read two pieces of serious academic research that push back — carefully, not dismissively — on the most panicked readings.

Anthropic published a new paper introducing a novel framework for measuring AI’s labor market impact, combining its own usage data from Claude with government occupational statistics to build what the researchers call an “observed exposure” metric — a measure of which jobs are not just theoretically automatable but actually being automated right now. The findings are more reassuring than alarming, at least for the moment: no systematic increase in unemployment for workers in the most AI-exposed occupations has emerged since late 2022. The exception — and it’s worth watching — is younger workers. Job-finding rates for workers aged 22-25 entering high-exposure occupations have dropped by roughly 14% in the post-ChatGPT era. The entry-level pipeline into exposed roles is narrowing, even if incumbent workers aren’t yet being displaced at scale. The paper is careful to note this is early evidence in a framework explicitly designed to detect disruption before it becomes obvious in aggregate data. (Labor market impacts of AI: A new measure and early evidence)

MIT economists David Autor and Neil Thompson offered a parallel and useful corrective in MIT Sloan Management Review. Their core argument is that we’ve been asking the wrong question. The relevant issue isn’t whether a job is exposed to automation — it’s whether AI will automate the supporting tasks that free workers to do their expert work better, or whether it will automate the expert tasks themselves, commoditizing hard-won skill. When spellcheck automated proofreading’s routine work, skilled proofreaders’ wages went up. When GPS automated taxi drivers’ encyclopedic knowledge of city streets, their wages fell. The difference is everything. Thompson also flagged a striking productivity finding that deserves more attention: experienced developers using generative AI wrote code faster, but took 19% longer to complete tasks overall. Prompting, checking outputs, waiting on the model — it all adds up. The productivity gains AI promises are real, but getting there involves friction we often don’t account for in the projections. (What 2 MIT experts are thinking about AI and work | MIT Sloan)

Venture capitalist Bill Gurley synthesized the career-level implications in ways I found resonated with what I’m hearing from clients. His warning: workers who followed the “college conveyor belt” into roles they don’t particularly care about are most exposed — not because AI will replace passion, but because disengaged workers have no natural motivation to become the most AI-fluent person in the room. The workers who survive, Gurley argues, are those who treat AI as “career jet fuel” — who understand what the technology can do in their specific industry and become indispensable precisely because of that fluency. For organizational leaders, the implication is uncomfortable: the talent most vulnerable to displacement may also be the talent that’s hardest to motivate to adapt. (Tech investor Bill Gurley says workers who went through the ‘college conveyor belt’ are most at risk)

Share BE AI READY

The Software Stack Is Rewriting Itself

While the labor market debate dominated headlines, I was also tracking a quieter but arguably more consequential set of moves in enterprise software. I have stood firmly in the camp that the effect of AI is more about disruption than replacement — but this week’s reading has started to make me sway.

The Wall Street Journal documented a wave of small and midsize companies that are vibe-coding their own CRM systems rather than paying for Salesforce. One example: a 65-person water treatment company that built a custom CRM for $15,000-$20,000 — cheaper, better-fitting, and more likely to actually get used. The more significant business story isn’t the individual builds; it’s the leverage shift. As BNP Paribas’s head of software research noted, even if most companies don’t walk away from incumbent vendors, an explosion of AI-native alternatives gives buyers negotiating power they haven’t had in years. That’s a margin compression story as much as a displacement story. (Meet the Companies Vibe Coding Their Own CRMs)

OpenAI accelerated its enterprise ambitions this week with the release of GPT-5.4, a model it describes as “our most capable and efficient frontier model for professional work.” Available in standard, Thinking, and Pro versions, the model hits benchmark records in knowledge-work tasks — 83% on OpenAI’s GDPval professional skills test — while running faster and at lower cost than its predecessors. For enterprise buyers, the headline is reliability: GPT-5.4 is 33% less likely to make errors in individual claims compared to its predecessor, and 18% less likely to produce responses containing errors overall. That gap between “impressive demo” and “dependable production tool” has been the sticking point for serious enterprise adoption; OpenAI is clearly targeting it directly. (OpenAI launches GPT-5.4 with Pro and Thinking versions | TechCrunch)

Share

What Good Enterprise AI Deployment Actually Looks Like

The most instructive piece I read this week might also be the one that got the least attention: a VentureBeat deep-dive into how OpenAI built an internal AI data agent that now serves over 4,000 of its own employees. Two engineers. Three months. Seventy percent of the code written by AI. The agent lets any employee — technical or not — query 600 petabytes of data across 70,000 datasets in plain English and get charts, dashboards, and analytical reports in minutes instead of hours.

The most useful insight from the piece isn’t the architecture or the benchmark scores — it’s what OpenAI’s data infrastructure lead Emma Tang identifies as the unsexy prerequisite that will determine who wins the AI agent race: data governance. This speaks directly to the Knowledge Architecture foundation I work to build for my own clients. Your data needs to be clean enough, annotated enough, and governed well enough for an agent to navigate it reliably. Without that foundation, the best models in the world produce overconfident, wrong answers. The organizational work of making your data trustworthy is not glamorous. It is, however, non-negotiable. (OpenAI’s AI data agent, built by two engineers, now serves thousands of employees)

The data governance challenge has a troubling counterpart in the executive suite. A survey of 200 UK business leaders I came across this week found that 62% now use AI to make the majority of their decisions — and 70% admitted to second-guessing their own judgment when it conflicted with AI’s recommendation. Perhaps more revealing: 65% said decision-making had become less collaborative since they adopted AI, and 46% now rely on AI more than on their colleagues’ advice. There’s a familiar pattern here — the same promises made about Executive Information Systems in the 1980s and 1990s. What’s different now is the degree of deference, and the research finding that frequent AI tool usage correlates with a “significant negative correlation” with critical thinking ability. Building AI into your workflow to handle complexity is prudent. Outsourcing your judgment to it is a different matter. (Supposedly big-brained execs are outsourcing decisionmaking to AI)

Share

On the Bigger Picture

A story that belongs in every enterprise risk register this week: Iranian drone strikes damaged three Amazon Web Services data centers in the Middle East — two directly struck in the UAE, a third damaged in Bahrain — causing structural damage, power disruption, and in some cases requiring fire suppression that added water damage on top. The localized impact was significant but not catastrophic; AWS’s redundancy architecture absorbed most of it. What the incident exposed is something cloud providers have long preferred not to emphasize: these facilities are physical objects, in physical locations, in a physical world that includes geopolitical conflict. AWS’s own disaster recovery architecture is designed for software failures, not missile attacks. For any organization with critical workloads in a region that borders active conflict zones, the question of “what does our BCP look like if our cloud provider’s infrastructure takes a hit?” just became more urgent. (Iranian strikes on Amazon data centers highlight industry’s vulnerability to physical disasters)

Share BE AI READY

What I kept coming back to this week is how much the debate has shifted from “will this happen?” to “it’s happening — now what?” The Goldman data shows productivity gains are real but concentrated. The Anthropic and MIT research shows labor impacts are real but still uneven and emerging. Dorsey’s restructuring and Zandi’s framing show that competitive and market dynamics are now accelerating adoption in ways that may not wait for the research to catch up. The most dangerous position for any organization right now is the one that’s watching all of this unfold while waiting for more certainty. The boats are already burning — the question is whether you’re on the shore or still on the water.

This week’s coverage:

• Two Platforms Walk Into an Enterprise

  Anthropic and OpenAI both launched enterprise agent platforms the same week. What that means for you.

• MCP Grows Up — But Security Hasn’t Kept Pace

  The protocol is becoming infrastructure. Governance is lagging dangerously behind.

• The Layoff Signal No One Should Ignore

  Block cuts 40% of its workforce and the stock pops 20%. The market has spoken.

• On the Bigger Picture

  Canva's "last 20%" bet, and the Substack post that moved markets, drew 22 million views, and earned a Citadel rebuttal.

Share

Here’s what I’ve been reading this week.

Two Platforms Walk Into an Enterprise

The most consequential week in enterprise AI infrastructure in recent memory unfolded quietly enough: Anthropic held a virtual event announcing Claude Cowork’s full enterprise launch, and a few days earlier OpenAI unveiled a platform called Frontier. Both companies are making essentially the same bet — that the next major AI battleground isn’t model quality, it’s orchestration. Whoever becomes the connective tissue of enterprise AI wins.

Anthropic’s pitch centers on what they’re calling “the thinking divide” — the growing gap between organizations embedding AI across employees, processes, and products simultaneously, and those still running isolated pilots. The Cowork announcement included private plugin marketplaces, a broad set of new MCP connectors spanning everything from Google Drive and Gmail to DocuSign and FactSet, and the ability to pass context seamlessly across Claude, Excel, and PowerPoint. The case studies were striking:

• Novo Nordisk reduced regulatory documentation time from over ten weeks to ten minutes

• Spotify cut engineering time on code migrations by 90%

• Salesforce’s Slack integration now saves customers nearly 100 minutes per week.

Thomson Reuters’ CEO said plainly that “the tools are in many senses ahead of the change management” — and estimated it would be 18 months before enterprise organizations catch up. That’s probably the most honest thing said at the entire event. (Anthropic says Claude Code transformed programming. Now Claude Cowork is coming for the rest of the enterprise.)

OpenAI’s Frontier announcement is playing a similar game from a different angle. The platform is designed to address what OpenAI sees as the core failure mode of enterprise AI: fragmentation. Agents deployed in isolation, without shared business context, quickly become complexity generators rather than value creators. Frontier aims to give agents institutional knowledge, identity, governance, and auditability — and claims to work with existing systems rather than replacing them. The reaction in developer and enterprise communities has been notably mixed: real enthusiasm for what the platform could do, alongside sharp skepticism about vendor lock-in. When your LLM vendor is also your agent orchestration layer and your enterprise platform, the strategic exposure compounds quickly. (OpenAI Launches Frontier, a Platform to Build, Deploy, and Manage AI Agents across the Enterprise)

What makes this moment interesting isn’t just that both companies launched in the same week — it’s what that timing reveals about the competitive dynamic. Anthropic moved from research lab to platform company in roughly twelve months. OpenAI is responding with similar enterprise ambition. Both are compressing into months the kind of ecosystem development that once took years. For the organizations sitting in the middle of this, the question isn’t which platform to choose — it’s whether you have the data infrastructure and organizational readiness to take advantage of either. As Anthropic’s head of economics put it at the Cowork event: “If the knowledge Claude needs to execute a sophisticated task exists only in a coworker’s head, that’s not a technical problem. That’s an organizational problem.”

MCP Grows Up — But Security Hasn’t Kept Pace

Three separate pieces this week told a coherent story about the Model Context Protocol: where it is in the hype cycle, where it’s heading as enterprise infrastructure, and why security is the variable most organizations are dangerously underweighting.

CIO.com laid out the executive case plainly. MCP has moved from engineering curiosity to board-level concern in under a year — and the primary driver is agentic AI. Agents need two things to function: access to data and the ability to act. As I’ve written previously, MCP provides standardized solutions to both, which is what makes it different from previous integration frameworks and why RSA 2026 is reportedly dominated by MCP-related submissions.

The governance implications are serious: MCP integrations can be created by anyone experimenting with AI tooling, which means the attack surface is expanding well beyond enterprise-approved systems. CIOs need to know where MCP is already in use within their organizations, who has authority to create integrations, and how permissions are being granted — because the answer, in most organizations right now, is “we don’t fully know.” (Why Model Context Protocol is suddenly on every executive agenda)

Google extended the MCP story into the browser this week with WebMCP — a protocol built into Chrome 146 that lets websites expose structured functions directly to AI agents. Rather than agents burning thousands of tokens processing screenshots or scraping raw HTML, they can call structured functions natively through the browser. Early benchmarks show a 67% reduction in computational overhead compared to visual agent-browser interactions, and the protocol is already backed by both Google and Microsoft, with W3C standardization underway. The creator describes it simply as “MCP, but built into the browser tab.” The SEO and web development implications are significant: the question for any organization with a customer-facing web presence is no longer just how humans experience your site — it’s how AI agents do. (Google Ships WebMCP, The Browser-Based Backbone For The Agentic Web)

The New Stack brought some useful ground-level reality from the MCP Conference in London. The headline finding is that the gap between “vibe-coded” MCP experiments and production-ready deployments remains wide. Security is the main culprit: as one speaker put it, “it has never been easier to get hijacked,” and OAuth implementation in most MCP deployments is incomplete at best. Context window management is the secondary challenge — connecting an agent to 100 tools is easy; getting it to use the right three efficiently is hard. The practical advice for organizations starting out: pick one internal system people constantly ask questions about, build one MCP server with read-only access, and give it to five non-engineers. That’s it. The ambition can grow from there. (Beyond the vibe code: The steep mountain MCP must climb to reach production)

Share

The Layoff Signal No One Should Ignore

Every week there’s another AI job displacement headline, and it’s easy to let them blur together. This week was different in a way worth paying attention to.

Jack Dorsey announced that Block — the company behind Square and Cash App — would lay off 40% of its workforce, more than 4,000 people. The stated reason was not cost pressure, not poor performance, not strategic restructuring in the conventional sense. Dorsey wrote plainly that “intelligence tools have changed what it means to build and run a company” — and said he chose immediate, honest action over a gradual drawdown over months or years.

Block’s stock rose more than 20% in after-hours trading. The market’s signal was unambiguous: investors are rewarding companies for accelerating the substitution of human labor with AI capability, even at scale, even when the operational execution is uncertain. The question every leadership team should be asking is not whether this happens elsewhere — it’s at what rate, and with what obligations to the people affected. (Jack Dorsey’s Block to Lay Off 40% of Its Workforce in AI Remake)

The Anthropic Cowork event added a piece of data that deserves its own moment. Anthropic’s head of economics, drawing on privacy-preserving analysis of how Claude is actually being used, reported that a year ago roughly a third of all US jobs had at least a quarter of their associated tasks appearing in Claude usage data. That figure has now risen to approximately one in every two jobs — and when businesses embed Claude through the API, the overwhelming pattern is automation, not augmentation. He specifically called out “jobs that are pure implementation” — data entry workers, technical writers — as occupations where Claude is already handling tasks central to those roles. No widespread labor displacement has materialized yet in the data, but the exposure is broadening faster than most organizations are tracking. The economist’s advice to leaders cut to the real issue: the bottleneck isn’t model capability, it’s whether your organization’s knowledge is structured and accessible enough for AI to act on it. (Anthropic says Claude Code transformed programming. Now Claude Cowork is coming for the rest of the enterprise.)

On the Bigger Picture

A few pieces this week were less about immediate enterprise decisions and more about the shape of what’s coming.

Canva announced two acquisitions — Cavalry for 2D animation and MangoAI for video ad optimization — while the broader software market continued to be punished on AI displacement fears. Canva’s position is instructive: $4 billion in annualized revenue, up 36% year over year, while Adobe is down 30% for the year. The company’s co-founder put it plainly: “AI is great at getting you to 80%. That last 20% — where you’re confident you can push this out and truly represent your brand — that’s really tricky to do.” Companies that embed AI deeply while keeping human judgment in the loop for the final mile are, for now, the ones finding competitive ground. (As Wall Street punishes software stocks over AI concerns, Canva gets more acquisitive)

The piece I kept coming back to this week — the one that I suspect you may have already encountered — was CitriniResearch’s “2028 Global Intelligence Crisis.” I want to be clear about what this is: a scenario document, explicitly labeled speculative fiction, not a forecast. But here’s the thing: it moved real markets at real speed. Published on a Sunday, it triggered a broad selloff the following Monday:

• The Dow dropped more than 800 points

• IBM fell nearly 13%

• Payment companies like American Express, Mastercard, and Visa all tumbled

• DoorDash and private equity giants KKR and Blackstone down over 8%

The piece accumulated 22 million views on X after Michael Burry amplified it. The Wall Street Journal cited it as a key accelerant of investor anxiety. Citadel Securities published a formal rebuttal the same week. A speculative essay on Substack moved hundreds of billions in market value in a single session. That fact alone is worth sitting with, regardless of whether the scenario is accurate.

The scenario itself is worth understanding because it traces the internal logic of AI disruption further than most analysis does. The core mechanism: companies cut headcount, reinvest savings into AI, AI improves, enabling further cuts — with no natural corrective cycle, because unlike a typical recession, this downturn’s cause is structural, not cyclical. Citrini introduces the concept of “Ghost GDP” — output that registers in national accounts but never circulates through the consumer economy, because machines don’t spend money on discretionary goods. The scenario traces the feedback loop through white-collar wage compression, consumer spending decline, SaaS revenue erosion, private credit defaults on PE-backed software LBOs, and eventually prime mortgage distress — borrowers with 780 FICO scores whose income assumptions were written before the world changed.

Citadel’s rebuttal pushed back hard, pointing to rising software engineering job postings (+11% YoY), stable AI adoption rates in actual labor data, and the historical pattern of general-purpose technologies creating more jobs than they displace. Those counterarguments have real merit. But what the debate itself reveals may matter more than who wins it: we are in a moment where the gap between “plausible narrative” and “tradeable signal” has collapsed to nearly nothing, and institutional investors are making allocation decisions based on AI disruption fears that are still more scenario than data. For organizations watching the market signals around enterprise software valuations, payments infrastructure, and professional services firms, the message is the same whether or not the 2028 scenario materializes: the repricing of human knowledge work is already underway, and capital markets are running well ahead of the economic data. (THE 2028 GLOBAL INTELLIGENCE CRISIS)

What this week’s reading adds up to is something like a threshold moment: the ideas that have been circulating in boardrooms and conference sessions for two years are now being operationalized and disclosed. Platforms are being launched, protocols are becoming policy questions, layoffs are being attributed explicitly to AI capability, and macro researchers are stress-testing scenarios that once seemed speculative. Organizations that treat this as background noise — as something to monitor rather than act on — are making a choice with real consequences. The thinking divide Anthropic named this week is real, and it’s widening. The question isn’t whether to engage with AI transformation; it’s whether your organization can do it with intention and clarity before the decisions get made for you.

Leave a comment

This week’s reading was defined by a single uncomfortable question running through almost everything I saw: who actually benefits when AI restructures work? The market is already voting — punishing the companies AI threatens and rewarding those aligned with it. Agents are moving from novelty to infrastructure, and the governance debates are arriving right on cue. And on the ground, knowledge workers are quietly discovering that the biggest shift isn’t capability — it’s continuity.

Here’s what I’ve been reading this week.

The Market Is Repricing AI’s Impact — and the Signal is What’s Falling, Not What’s Rising

The story everyone was watching this week was the so-called “SaaSpocalypse” — a wave of selling that wiped over a trillion dollars from enterprise software valuations. Salesforce down 26%. ServiceNow down 28%. HubSpot down 39%. The hot take was that AI is overhyped and the bubble is cracking. A much better read, from Dave Brear on LinkedIn, makes the opposite case: markets aren’t losing faith in AI — they’re losing faith in the companies AI is threatening to replace. (The AI Skeptics Are Right About the Wrong Thing)

That reframe matters. Deutsche Bank ran a remarkable experiment this week — they asked their own AI tool, dbLumina, which industries it planned to disrupt. The answer was uncomfortably direct: information technology and software are the most exposed, followed by wealth management (80% of retail investor interactions handled by AI by 2027) and customer service (75% automated by 2026). The machine identified its own targets. (Deutsche Bank asked AI how it was planning to destroy jobs)

Figma is a useful case study in what it looks like to be on the right side of that line. The stock is down 80% since IPO — and yet investors cheered its Q4 earnings, which showed 40% year-over-year revenue growth and the highest net dollar retention in ten quarters. In a CNBC interview, CEO Dylan Field ranked Claude at the top of the LLM stack, said 75% of their larger customers are already consuming AI credits weekly, and pushed back hard on the “software is dead” narrative. Figma’s partnerships with Anthropic and OpenAI aren’t decoration — they’re the thesis. (Figma Q4 earnings | Figma CEO interview) Citi’s equity analyst Tyler Radke added useful color: he thinks we’re nearing a bottom for software stocks, but his advice is to be selective — favor companies with real AI stories and avoid legacy SaaS businesses that aren’t showing growth or margin improvement. (Citi sell-off analysis)

Agents Are Becoming Infrastructure — and the Governance Questions Just Arrived

Underneath the market noise, something more structurally significant is happening with AI agents. A team at UC Santa Barbara published a new framework called Group-Evolving Agents (GEA), which allows AI agents to evolve collectively — sharing innovations across the group rather than siloing improvements in individual branches. GEA matched the performance of human-engineered agent systems on real-world coding benchmarks, at zero additional deployment cost. It’s an early signal that the “design the agent” phase of enterprise AI may give way to “let agents design themselves.” (GEA framework)

At the same time, the agent ecosystem got its first real governance friction. Anthropic quietly updated its documentation to clarify that routing Claude requests through personal Pro or Max subscriptions — which is exactly how popular personal agents like OpenClaw and NanoClaw work — violates their terms. The community reacted, Anthropic walked it back as a documentation clarification rather than a policy change, but the underlying tension is real: where is the line between personal experimentation and building a business on subsidized platform access? (Anthropic/OpenClaw ToS) The denouement was almost too on-the-nose: the creator of OpenClaw, Peter Steinberger, promptly announced he was joining OpenAI to work on “the next generation of personal agents.” (OpenClaw creator joins OpenAI)

The governance theme ran deeper than platform ToS disputes. Anthropic CEO Dario Amodei resurfaced in a Fortune piece with a quote that deserves more attention than it got: “I’m deeply uncomfortable with these decisions being made by a few companies, by a few people.” He wasn’t talking about competitors — he was talking about himself. No one elected him. No federal AI regulations exist. Thirty-eight states have adopted some form of AI legislation, but there’s no coherent national framework. Amodei is advocating for more regulation while acknowledging the commercial pressures working against it from inside his own company. It’s an honest and uncomfortable position — which is probably why it’s worth taking seriously. (Anthropic CEO on governance)

What AI Actually Feels Like From Inside the Work

Three more grounded reads this week, all relevant to anyone doing knowledge work.

The Claude Code diary by Dave Brear is worth reading slowly. He spent a week connecting Claude Code to his personal knowledge vault and discovered something easy to miss in the broader AI hype: the value isn’t in any individual response — it’s in continuity. When AI knows your files, your conventions, your half-formed ideas, the collaboration changes character entirely. You stop prompting and start conversing. He hit rate limits, felt the absence like a colleague stepping out for lunch, and ended the week staring at the Claude Max pricing page. The piece captures something true about what persistent AI context actually feels like. (Claude Code diary)

Microsoft open-sourced VibeVoice this week — a local audio model that handles text-to-speech, speech-to-text, and voice cloning, all without a cloud subscription or API key. Capabilities that were expensive and gated six months ago are now free and local — and that’s increasingly the story with open-source AI. (Microsoft VibeVoice)

Finally, a study worth bookmarking for anyone creating content professionally: an analysis of 1.2 million AI-generated answers found that 44% of ChatGPT citations come from the first 30% of any given piece of content. AI models weight early framing more heavily and interpret the rest through that lens. The practical implication is simple: if you want AI to surface your ideas, stop burying your best thinking at the end. Front-load your substance. (ChatGPT citation study)

On the Bigger Picture

Two reads that don’t fit the workplace frame neatly but are worth noting. IEEE Spectrum published a careful piece arguing that the US and China aren’t racing toward the same finish line — the US is doubling down on AGI, while China is focused on embedding AI into manufacturing, healthcare, and logistics as a near-term productivity engine. The “arms race” framing may be creating a self-fulfilling prophecy that increases risk for everyone. (US vs. China AI futures) And separately, China’s humanoid robots went from stumbling through folk dances at last year’s Spring Festival Gala to performing kung fu flips and choreographed gymnastics this year — China now accounts for more than 85% of global humanoid robot installations. The AI model race, one analyst noted, will ultimately matter more than the hardware. But the hardware is catching up faster than most expected. (China humanoid robots)

The thread connecting most of this week’s reading: AI isn’t disrupting work in the future tense anymore. The disruption is active — in valuations, in agent governance debates, in how knowledge workers structure their days and their content. The question for organizations isn’t whether to engage with this. It’s whether they’re paying close enough attention to know which side of the line they’re on.