The Board Room

Deep dives

1. 01

   Compute Is Being Weaponized — Your Cloud Provider Is Now Your Competitor

   The most important strategic revelation this week isn't a model launch — it's Microsoft's CFO telling Wall Street that Azure growth was deliberately sacrificed to feed internal AI products with higher margins and lifetime value. When Satya Nadella says internal workloads have better unit economics than external customers, he's confirming that in a GPU-constrained world, your cloud provider's compute allocation decisions are structurally misaligned with your needs.

   In a compute-constrained world, your cloud provider isn't a utility — it's a competitor with first-mover advantage on its own infrastructure.

   Meta's response was immediate and aggressive: poaching three senior Stargate infrastructure executives — Peter Hoeschele, Shamez Hemani, and Anuj Saharan — to staff a new 'Meta Compute' group reporting near the CEO. Zuckerberg simultaneously installed Alexandr Wang (former Scale AI CEO) to run the broader AI org. This isn't opportunistic hiring — it's a strategic capability acquisition that represents irreplaceable institutional knowledge about planning and operationalizing $100B+ infrastructure programs. For OpenAI, losing these architects during Stargate's critical scaling phase is an execution risk that compounds over 18 months.

   ---

   The Revenue Validates the Thesis

   Anthropic's revenue jumping from $9B to $30B annualized in roughly one quarter — a 233% increase — validates two things simultaneously: demand for frontier AI is accelerating, and the ability to serve it is directly gated by compute capacity. Anthropic's response — a multi-year CoreWeave deal, a 3.5GW capacity agreement with Broadcom and Google starting 2027, and a stated ambition of 10GW total — reveals a company that understands the constraint isn't model quality but infrastructure throughput. OpenAI's counter-narrative to investors, emphasizing its 'warchest of billions of dollars worth of compute,' inadvertently confirms the same thesis.

   Energy Makes It Worse

   Layer in the Strait of Hormuz blockade with crude at $105 (up 83% YTD), and your infrastructure cost assumptions from Q4 planning are already obsolete. ERCOT's emergency hearing revealed 410,000 MW of filed data center demand in Texas alone — against a grid that serves a fraction of that. Nevada's utility publicly admitted it will burn more fossil fuels to keep data centers running. Lumentum's order books are filled through 2028, confirming this is a multi-year supercycle, not a bubble. The window for securing favorable compute terms is closing.

   The AI race is a compute race, and the worst strategic posture is single-provider dependency on a hyperscaler whose internal AI products compete for the same GPUs you need.

   Musk's partnership with Intel to build a chip fab is the most extreme expression of this logic: when your largest AI consumers vertically integrate, the foundry model's pricing and allocation mechanics are failing. Intel's participation as partner rather than supplier suggests it has accepted its future lies in manufacturing-as-a-service. Expect Google TPU or Amazon Trainium teams to explore similar arrangements within 18 months.

   What to do

   1. →

      Audit AI compute dependencies — map every critical workload to its provider and identify single-provider concentration risk by end of Q2

      NowMicrosoft just proved your provider is allocating against you; you need visibility into your exposure before you can negotiate alternatives
   2. →

      Initiate multi-provider compute negotiations with at least two alternatives (CoreWeave, Lambda, or second hyperscaler) within 30 days

      NowLumentum orders through 2028 confirm supply tightening; every quarter you delay means worse terms and longer lead times
   3. →

      Conduct immediate retention risk assessment of top 10 infrastructure leaders with pre-approved board-level counteroffer authority

      NowMeta is actively recruiting your people — the comp packages required will look excessive until you calculate the cost of a 12-month infrastructure delay
   4. →

      Reforecast H2 2026 infrastructure costs assuming oil sustains above $100 through year-end

      This sprintEnergy costs compound the compute crunch; your Q4 budget assumptions are already wrong
2. 02

   Your Real Competitor Is Your Customer's Engineering Team — Not Another Vendor

   The most consequential finding from a16z's direct conversations with enterprise AI buyers isn't about pricing wars between vendors — it's that every enterprise buyer interviewed is drawing a hard line: buy non-core, build core in-house. A B2C logistics company explicitly plans to repatriate AI from third-party tools. A financial institution draws the line at mortgages and financial services — those get built internally, period. As foundation model costs plummet and APIs simplify, enterprise engineering teams are asking whether they even need vendors for their most important use cases.

   No enterprise buyer interviewed chose the cheapest tool. Not one. Buyers chose the tool that proved indispensable — not inexpensive.

   The Multi-Vendor Hedge Is Standard Practice

   Enterprises are deploying 2-3 AI tools for the same use case as deliberate policy. A financial institution does this as redundancy against hallucinations and outages. A logistics company deploys a premium tool for high-stakes work and a cheaper alternative for commodity tasks. This means your TAM per account may be larger (multiple vendors), but your revenue per account is structurally capped. The goal isn't exclusive deals — it's winning the premium allocation within a multi-vendor stack.

   ---

   Claude's Quality Collapse Proves the Risk

   This week validated the multi-vendor thesis in real time. Analysis showing Claude Opus 4.6's thinking depth dropped 67% — likely from cost-driven inference rationing — triggered measurable developer migration to OpenAI's Codex and GPT 5.4. Harrison Chase's warning about losing accumulated agent memory when switching providers reveals a deeper structural vulnerability: model providers are quietly absorbing agent state behind their APIs, creating switching costs that are invisible until triggered. This is the cloud data-gravity problem all over again, but accumulating faster.

   The Micro-SaaS Fragmentation Threat

   Meanwhile, non-technical knowledge workers are building custom automation on top of existing SaaS APIs using Claude Cowork and Perplexity Computer — for $0 and zero engineering time. One practitioner replaced Zapier with webhooks and AI flows at 4x performance and near-zero cost. Multiply this across every pain point in every SaaS tool, and the prediction of a 'Cambrian explosion' of micro-tools capturing the user relationship while your platform becomes invisible infrastructure starts looking conservative, not speculative.

   What Enterprise Buyers Actually Want

   Pricing model innovation — not price level — is the real differentiator. Enterprises want dual pricing models: one predictable (committed spend, per-seat) and one outcome-based (gainshare, per-result). Outcome-based pricing makes comparison nearly impossible, effectively neutralizing commodity pressure. But it demands robust, mutually trusted outcome measurement — a capability most AI companies lack. With $300B in VC deployed last quarter, the supply-side flood won't abate. Market leadership perception shifts within a single quarter. The decisions you make in the next two quarters about integration depth and pricing architecture will determine whether you consolidate or get consolidated.

   What to do

   1. →

      Conduct a 'build vulnerability audit' across your AI product portfolio — classify each major customer's use case as core or non-core and estimate the timeline before in-house build becomes viable

      This sprinta16z confirms enterprises are actively planning repatriation of core AI; you need to know which revenues are structurally at risk
   2. →

      Mandate a model-agnostic agent architecture with formal parity testing between at least 2 frontier providers within 60 days

      This sprintClaude's 67% quality collapse proves single-model dependency is a business continuity risk, not a theoretical concern
   3. →

      Deploy forward-embedded customer success engineers into your top 10 accounts this quarter to create integration depth that's genuinely painful to replicate in-house

      This sprintThe only defense against the build-vs-buy migration is making your product more expensive to replicate than to renew
   4. →

      Establish agent memory and state portability policy before scaling agentic deployments — audit where accumulated agent context lives and mandate export capabilities

      This quarterAgent memory is the new data-gravity lock-in; setting ownership terms now avoids painful migration later
3. 03

   AI Capability Timelines Just Compressed 18 Months — Your Org Design Is Already Behind

   Every major AI forecaster revised timelines shorter simultaneously this week. Ryan Greenblatt — historically conservative — doubled his probability of full AI R&D automation by end of 2028 from 15% to 30%. Ajeya Cotra substantially updated in March. Lifland and Kokotajlo pulled estimates forward approximately 1.5 years. The meta-signal: the forecasting community has a systematic bias toward conservatism — meaning even these updated, shorter timelines are likely still too long.

   A 30% probability of full AI R&D automation by 2028 means there is a significant chance of recursive self-improvement dynamics within your current strategic planning window.

   The Evidence Is Concrete

   METR and Epoch AI's MirrorCode benchmark tested whether AI can autonomously reimplement complex software. Claude Opus 4.6 successfully reimplemented gotree — a 16,000-line bioinformatics toolkit with 40+ commands — a task estimated at 2-17 weeks for a human engineer. The strategically critical finding: performance continues to scale with inference compute on larger projects, meaning these capabilities improve predictably with spending, not requiring new breakthroughs. Meanwhile, LinkedIn proved at production scale that a single LLM can replace five specialized ML systems serving 1.3B users at sub-50ms latency — collapsing years of accumulated ML architecture.

   ---

   The Workforce Pipeline Is Already Broken

   The structural workforce implications are cascading faster than HR models account for. Entry-level tech hiring has collapsed 67% since 2022. Employment for 22-25 year-old developers is down nearly 20%. A Harvard study shows junior employment falls 7.7% within six quarters at AI-adopting firms. Meanwhile, 54% of engineering leaders plan to hire even fewer juniors — a classic tragedy of the commons that's individually rational but collectively catastrophic.

   The hollowed-out career ladder is arriving in software engineering at compressed speed: expensive deep-systems architects at the top, AI-augmented prompt engineers at the bottom, and almost no one developing in between. The senior engineers you need in 2032 are the juniors you're choosing not to hire in 2026.

   Where Sources Diverge

   OpenAI's experimentation with a 'super senior + super junior' team structure signals that even the company with the most advanced AI believes human mentorship is non-negotiable. The UPenn/Boston University research adds a structural constraint: AI workforce automation is formally modeled as a Prisoner's Dilemma — individual cost-cutting is self-defeating at scale, and an automation tax is now on the academic policy agenda. If you're running a 3-year automation program, model a world where Year 2 carries a 15-25% tax on each displaced role.

   Signal	Data Point	Implication
   R&D automation probability	15% → 30% by 2028	Recursive improvement within planning window
   Autonomous code reimplementation	16K lines, 2-17 week task	Software cost function entering step-change
   Junior hiring collapse	-67% since 2022	Senior talent crisis by 2030
   ML system consolidation	5→1 at LinkedIn scale	Architectural debt now competitive liability

   What to do

   1. →

      Commission a 90-day AI workforce transformation study: model your engineering org's output under 30%, 50%, and 70% AI coding scenarios within 18 months — present to board with restructured hiring plans

      This sprintForecasters simultaneously halved their timelines; your workforce plan built on last year's assumptions is already wrong
   2. →

      Reframe junior hiring from 'headcount expense' to 'talent R&D' in your next budget cycle — establish a protected junior development budget with explicit multi-year ROI modeling

      This quarterDeveloping a junior to senior over 4-5 years costs a fraction of poaching seniors in a talent-scarce 2030 market
   3. →

      Conduct a knowledge concentration audit — map bus factor across all critical systems and establish a mandatory threshold below which remediation is required

      This quarterAI-driven team compression is silently concentrating institutional knowledge; one departure can create an existential risk
   4. →

      Pilot a 'super senior + super junior' team structure on one product area this quarter to test whether it outperforms senior-only + AI teams

      This quarterOpenAI's own structure suggests AI cannot replace experiential judgment — validate this for your context before committing to org-wide decisions