The Board Room

Deep dives

1. 01

   AI Finds Your Vulnerabilities Before You Do — And Your AI Tools Are Creating New Ones

   The Offense-Defense Equation Just Broke

   When Wiz CTO Ami Luttwak — now operating under Google's umbrella — says the new AI models are 'essentially the best cybersecurity researchers in the world, and that's a problem,' he's describing a threshold that ten independent sources this cycle confirm has been crossed. Anthropic's upcoming model found 500+ high-severity vulnerabilities in mature open-source software including Ghost CMS, the Linux kernel, Vim, and Emacs — using prompts as simple as 'find a vulnerability.' One critical Ghost vulnerability had been missed by 13 years of human security research.

   The cost of vulnerability discovery just collapsed to near-zero. Your patch velocity, risk scoring, and security SLAs were all calibrated for a world where finding zero-days was expensive and slow. That world ended this week.

   Your AI Tools Are Creating the Targets

   Here's the compounding problem most organizations haven't connected: while AI makes it trivial to find vulnerabilities, your engineering teams' AI coding tools are simultaneously creating them at scale. A study of 117,000+ dependency changes found that AI coding agents select known-vulnerable package versions 50% more often than human developers. Nearly 20% of AI-recommended packages are pure hallucinations — and because 43% of those hallucinated names are consistent across queries, attackers can predictably register them with malicious payloads. This 'slopsquatting' vector is the first attack class native to the AI agent era. Georgia Tech has already traced 74 CVEs directly to AI-generated code, with over half rated Critical or High severity.

   The Proof Points Are Already Operational

   Amazon's CISO CJ Moses disclosed that AI tools are reducing pentesting costs by over 40% — not through headcount reduction, but through capability expansion, with AI handling continuous vulnerability testing and highlighting exploit chains for human review. Synthesia's AI-driven vulnerability management architecture reduced manual security review to just 11% of findings. Meanwhile, on the attacker side, Akira ransomware has compressed its kill chain to under 4 hours from initial access to full encryption, and DeepMind's research demonstrated 86% prompt injection success rates in HTML/CSS and 80%+ memory poisoning at less than 0.1% contamination.

   ---

   Where Sources Diverge — and the Gap That Matters

   There's a revealing tension in how different sources frame the AI security response. Amazon advocates for a human-in-the-loop model — Moses compares AI decision-making to 'that of a 7-year-old' and requires human approval for any exploit action. RSA 2026 ground truth confirms 98% of offensive security remains human-in-the-loop. But the attack side faces no such constraint. Frontier model providers are also expanding cybersecurity refusals — creating what one source calls 'a slow-moving supply chain crisis' for any security vendor built on a single model API. The same providers whose models find vulnerabilities are restricting their use for defense. This asymmetry is structural and widening.

   GitHub's 2026 Actions roadmap — workflow-level dependency locking, scoped secrets, Layer 7 egress firewalls, real-time telemetry — represents the most comprehensive platform response, with a 3-6 month delivery timeline. The 322 cybersecurity startups across 18 categories at RSAC 2026 signal peak fragmentation before inevitable consolidation, with Agent Security/Non-Human Identity and AI SOC emerging as the categories where M&A will concentrate.

   What to do

   1. →

      Commission an AI-augmented audit of your open-source dependency stack within 30 days, prioritizing components stable (unaudited) for 2+ years

      Now500+ vulns found in 'stable' OSS means your unaudited dependencies are your largest unhedged risk — adversaries with API access are scanning them now
   2. →

      Establish mandatory security review gates for all AI-generated code contributions by end of quarter

      This sprintAI agents select vulnerable deps 50% more often than humans; without gates, your productivity gains are creating proportional security debt
   3. →

      Deploy multi-model AI security tooling — do not single-source to one provider, given expanding cybersecurity refusal policies

      This quarterNon-deterministic refusals mean the same defensive query can fail in one session and succeed in the next; multi-model architecture is a survival requirement
   4. →

      Target <15% manual security review rate using Synthesia's layered-automation architecture as reference model

      This quarterAmazon's 40% cost reduction at maintained headcount proves the model works; the freed capacity should expand coverage, not reduce team size
   5. →

      Add AI cybersecurity risk as standing board agenda item with quarterly threat landscape updates

      This sprintAI-powered vulnerability discovery at zero marginal cost is a material risk disclosure consideration — boards operating on pre-AI threat models are making decisions on stale assumptions
2. 02

   Microsoft Goes Solo as Smart Money Flees OpenAI — Your Vendor Leverage Is at a Cyclical Peak

   The Divorce Is Official

   Microsoft's Mustafa Suleyman didn't hedge: he explicitly declared Microsoft's intent to build a frontier large language model and become 'completely independent' from OpenAI. Combined with a renegotiated contract that permits Microsoft to pursue superintelligence on its own, this isn't a hedging strategy — it's a breakup announcement. Microsoft shipped competitive speech-to-text, voice generation, and image models built by teams of fewer than 10 engineers, with MAI-Transcribe-1 running on half the GPUs of competitors while outperforming Whisper across all 25 benchmarked languages.

   If your AI stack has meaningful OpenAI concentration, the next 90 days are your window to diversify from a position of strength rather than reacting to a crisis.

   The Secondary Market Data Is Devastating

   Caplight's data reveals the market's private verdict on OpenAI: through Q1 2026, institutional investors put $1 billion in OpenAI shares up for sale against only $200 million in buy orders — a 5:1 ratio. $600 million in shares found zero buyers. Typical sellers are looking to offload $50M+ blocks of preferred stock — these are institutional investors seeking the exit, not employees cashing out. This selling pressure 'far exceeded' that of Anthropic and SpaceX, making it a company-specific signal.

   The composition of who is buying tells you everything: Amazon and Nvidia wrote the biggest checks as strategic investors, but their motivation is 'supporting OpenAI as a customer' — relationship capital, not conviction capital. Meanwhile, $2B+ in capital is actively queued to deploy into Anthropic at a $380B valuation. SoftBank — now with roughly 25% of total asset value in OpenAI — has seen its stock decline 17% YTD.

   The Commoditization Case Strengthens

   Multiple sources converge on a thesis that should reshape your procurement strategy. Arcee AI's Trinity Large Thinking matches Anthropic's Opus 4.6 on agent benchmarks at 1/20th the cost. A large-scale study across 25,000 tasks found open models reaching 95% of closed-model quality. Alibaba's Qwen3.6-Plus scored 78.8 on SWE-bench, trailing only Anthropic's flagship. H Company's Holo3 hit 78.85% on OSWorld — outperforming both GPT-5.4 and Opus 4.6 — at one-tenth the inference cost, with an open-source variant under Apache 2.0.

   ---

   The Contrarian Case and What It Misses

   Not Boring's rigorous analysis argues the dominant 'OpenAI is like Amazon' narrative is structurally broken. Amazon's growth generated cash through negative working capital; every AI query burns compute. Anthropic's own Opus workloads drop to 35-50% gross margins versus 50-65% for Sonnet. Heavy Pro/Max users are net negative. With Google, Meta, DeepSeek, and each other all executing the same scaling-law strategy, this is a commoditization setup, not a winner-take-all market.

   For your vendor negotiations, the implication is clear: OpenAI needs your enterprise revenue for its IPO narrative more than you need OpenAI. Your leverage to negotiate favorable terms, pricing caps, and contractual protections is at a cyclical high. Architect for multi-vendor portability and negotiate aggressively now, while labs are burning cash to acquire enterprise accounts.

   What to do

   1. →

      Initiate AI API contract renegotiations within 60 days, leveraging open-weight convergence data and OpenAI's weakened secondary market position

      This sprintYour leverage is at a cyclical high — OpenAI needs enterprise revenue for IPO narrative; open-weight alternatives at 95% quality give you credible alternatives at the table
   2. →

      Build or accelerate a multi-model abstraction layer that enables provider switching without application-level changes by Q3

      This quarterMicrosoft's independence + model commoditization means the vendor landscape will look materially different in 12 months; switching costs are your primary risk
   3. →

      Evaluate Anthropic as co-primary AI partner and initiate enterprise commercial discussions if not already underway

      This quarter$2B+ in institutional demand at $380B valuation reflects market conviction that Anthropic is the preferred enterprise partner — negotiate while they're still hungry for logos
   4. →

      Stress-test AI strategy against 80% model pricing compression in 18 months — shift competitive moat assumptions to proprietary data and application layer

      This quarterWhen sub-10-person teams ship frontier-competitive models, model access ceases to be a scarce resource — your moat must live in your data and workflows
3. 03

   Block Eliminates 40% of Staff for AI-First Org — The Experiment Every Board Is Watching

   Dorsey's Thesis: Managers Are Information Routers. AI Routes Better.

   Jack Dorsey didn't just announce layoffs — he published an intellectual framework arguing that managers are fundamentally information routers, that AI can now build a live 'world model' of a business to perform this function, and that Block's 4,000-person cut (40%+ of staff) is the logical consequence. The resulting three-role structure — builders, problem-owners, player-coaches — is the most radical organizational redesign attempted by a public technology company in the AI era.

   This isn't a case study yet; it's a live experiment. Your board is watching. The question they'll ask next quarter: 'What percentage of our middle management's work is information routing versus judgment?'

   The Precondition Most Companies Can't Meet

   The critical nuance: Block is remote-first, meaning 'every decision, design, and plan already exists as a digital record.' This is the data substrate that makes AI management theoretically possible. Companies with significant in-person or hybrid operations face a structural gap — their institutional knowledge lives in hallways and unrecorded conversations. This creates a meaningful bifurcation: remote-first companies can move to AI-augmented management faster, while traditional-culture companies face a multi-year data infrastructure project before the same transformation is even feasible.

   Converging Signals: Who's Most Exposed

   Simon Willison — co-creator of Django, who writes production code daily with AI agents — identifies mid-career engineers as the most exposed cohort, not juniors. The logic is counterintuitive but sound: mid-career engineers' core value is reliably shipping well-known patterns at production quality with moderate supervision. That is precisely what agentic coding tools now do. Junior engineers are cheap and adaptable; senior engineers bring irreplaceable architectural judgment. The middle tier — your most expensive, most established cohort — is caught in a capabilities squeeze.

   OpenAI's Project Stagecraft compounds this pressure: 4,000 freelancers across commercial aviation, pharmacy, plant science, and HR are creating personas and simulating workflows that train models to replicate their expertise. One contractor's quote captures the dynamic: 'We all were aware that we were basically training AI to replace us.' Amex disclosed a 30%+ coding time reduction across 11,000 engineers. Zapier is measuring AI fluency across every hire in every department.

   ---

   The Organizational Frontier

   Moonshot AI's model — flat hierarchy, no KPIs, small autonomous teams of generalist talent, tight feedback loops — is producing results that compete with organizations ten times their size. Karpathy's 600-line autoresearch framework let Shopify's CEO (not an ML engineer) produce a model half the size that outperformed the original by 19% overnight. The bottleneck in AI has moved from 'who has the best ML team' to 'who can define the right optimization target and run the most experiments.'

   For your organization, Block's experiment creates both a template and a forcing function. The companies that figure out AI-native org design will achieve structural advantages in speed, cost, and decision quality that no amount of AI tool deployment within traditional structures can match. But the execution risk is real — Dorsey's thesis has never been tested at public-company scale, and the 3-week timeline from announcement to execution leaves little room for organizational learning.

   What to do

   1. →

      Commission an internal 'management task audit' within 60 days — map what percentage of middle management work is information routing vs. judgment, decision-making, and talent development

      This sprintThis is the analysis your board will ask for within two quarters; having data before they ask gives you the initiative
   2. →

      Audit your digital decision trail — determine whether your org's decisions, plans, and context exist in structured digital formats AI could consume

      This quarterBlock's precondition is digital-native operations; without this data substrate, AI-augmented management is architecturally impossible regardless of tool quality
   3. →

      Map your engineering workforce by tier against AI-automatable task profiles, specifically quantifying exposure in the mid-career band

      This quarterWillison's thesis that mid-career engineers are most exposed — not juniors — inverts most companies' workforce planning assumptions; validate or disprove for your org
   4. →

      Launch a pilot team (single pod) operating with AI-guided decision layers and flattened hierarchy; track velocity, quality, and retention vs. control group

      This quarterBlock's 4,000-person experiment is too large to replicate safely; a controlled pilot gives you data without existential risk
   5. →

      Track Block's operational metrics quarterly — product velocity, attrition rates, customer satisfaction — as the industry's leading indicator for AI-first org design

      WatchThis is a live experiment with $40B+ in market cap at stake; the results will shape every board's workforce planning for the next 3 years