The Board Room

Deep dives

1. 01

   The Pricing Power Paradox: Your API Bill Is Funding a Monopoly That Open-Source Is Already Dissolving

   The Contradiction in One Frame

   Anthropic's valuation has crossed $1-1.2 trillion on 10x annual revenue growth. In the same news cycle, Fleet swapped Anthropic's Sonnet 4.6 for Kimi K2.6 with zero quality degradation at one-fifth the cost. Capital markets are pricing monopoly rents while the underlying technology commoditizes; both are true today, and only one survives the decade.

   The capital markets are paying for the layer they believe compounds. The open-source community is proving that layer is reproducible at 5x lower cost. Both bets are currently correct. The question is which one a three-year vendor commitment is exposed to when they diverge.

   The Evidence Is No Longer Anecdotal

   Several convergent signals say open-source has crossed a threshold that matters for procurement decisions this quarter:

   • Kimi K2.6: Opus-level quality at 20% of API cost, production-validated
   • Aurora and ZAYA1: Frontier parity achieved with 100x fewer training tokens
   • vLLM: 72% throughput improvement on H20 hardware
   • SGLang: Processing 57 billion tokens daily at scale
   • Zyphra: Training competitive models on AMD, breaking the NVIDIA dependency

   If inference costs fall 5-10x over the next twelve months, which this evidence trajectory supports, any business whose margin depends on API markup is building on sand. Firms whose value sits in orchestration, domain knowledge, or workflow get the opposite outcome: their cost per task falls with each model release without a single renegotiation.

   The Funding Paradox Makes This Urgent

   The infrastructure financing the frontier labs requires those labs to hold pricing power. Big Tech's collective free cash flow has collapsed 91% — from $45 billion to $4 billion per quarter — under AI capex weight. SoftBank just cut its OpenAI-backed loan from $10B to $6B, the first serious note of capital impatience. If returns arrive 2-3 quarters late, the correction lands on cloud pricing, API costs, and startup funding at the same time.

   The scenario most enterprises have not modeled: a 20-40% cloud price increase by Q1 2027 as hyperscalers attempt to recover margins. Any strategy predicated on flat or declining compute costs deserves a stress test against that scenario now, rather than when the price increase arrives.

   The Decision This Forces

   Buying locks in a cost basis set by a vendor whose pricing power is under active assault from free alternatives at one-fifth the cost. Building on open weights accepts a modest engineering tax in exchange for owning the curve. Neither choice is obviously correct this quarter. One of them will look obviously correct in eight quarters.

   ---

   The honest framing for any enterprise with more than 60% of AI spend concentrated in a single frontier provider is this: a contingency plan has to cover a 30% price increase when that provider moves to satisfy its investors, and it has to cover the open-source alternative a competitor adopted six months ago reaching the same quality at zero marginal cost.

   What to do

   1. →

      Qualify Kimi K2.6 and two additional open-source alternatives for non-critical production workloads by end of Q3

      This sprintFleet validated zero quality loss at 1/5 cost — your team can validate the same within 30 days and begin shifting non-critical traffic immediately
   2. →

      Model 20-40% cloud/API price increase scenario against current AI budget and present to CFO before next board meeting

      This sprint91% FCF compression at hyperscalers is unsustainable — pricing correction is a when not if, and the stress test takes 2 weeks to build
   3. →

      Cap single-vendor AI API concentration at 60% of total AI compute spend by Q1 2027

      This quarterThe Kimi K2.6 data proves multi-provider is viable without quality sacrifice — the only cost is the engineering tax of maintaining two integrations
   4. →

      Invest in building proprietary orchestration layer that abstracts model provider choice from application logic

      This quarterOrchestration, not model access, is where value accrues when the model layer commoditizes — Zenith winning 5/8 tasks at 43% cost proves this thesis
2. 02

   AI Liability Is Becoming Uninsurable — Your Deployment Ceiling Now Has an Underwriter

   The Coverage Gap Nobody Is Pricing

   Berkshire Hathaway and Chubb are removing AI-related damages from standard commercial policies, and they have received 80% regulatory approval to do so. The total specialty AI insurance market today is $40 million, smaller than a single Series B round. Projections put it at $5B by 2032, which is another way of saying adequate coverage at reasonable prices will not exist for several years.

   Companies are deploying AI aggressively while their insurance quietly exits coverage of the thing being deployed. The first major uncovered AI loss is still hypothetical. Every one of them is, right up until it isn't.

   Why This Matters This Quarter, Not Next Year

   The incentive structure is economically irrational and organizationally predictable. The team deploying AI reports to the CTO. The team managing insurance reports to the CFO. In most organizations, these two decisions are made by different people who do not coordinate. Deployment accelerates. Coverage narrows. The gap widens quarterly.

   The window matters because bespoke AI liability coverage is still being written at reasonable rates today, on the strength of a minimal loss history. That window closes the moment a headline-making uncovered incident forces repricing across the specialty market. The Mythos result of 423 Firefox vulnerabilities in a single month shows the attack surface. The Canvas breach affecting 275M people during finals week shows the exposure. Combine the two with a coverage exclusion and the balance-sheet risk is material.

   Insurance Posture as Deployment Ceiling

   A reasonable skeptic would call this a risk-management question for the general counsel and move on. The skeptic is half right. It is also a deployment-ceiling question. An AI application that creates $50M in value but carries $200M in uninsured liability is not a net positive. It is a contingent liability that belongs in the 10-K. Firms that lock in coverage now get a roadmap set by their engineers. Firms that wait get a roadmap set by their underwriter.

   The PE Angle Amplifies This

   TPG, Blackstone, and Brookfield committed $10B alongside OpenAI, and private equity firms are now mandating AI adoption across portfolio companies. The liability profile splits along an awkward seam: the operating partner at the fund writes the deployment mandate, the portfolio company's balance sheet absorbs the uninsured exposure. That mismatch produces the first litigation cycle, and it arrives before the insurance market scales to meet it.

   What to do

   1. →

      Commission a cross-functional audit of AI deployment against current liability coverage within 60 days — map every production AI system to its applicable insurance policy

      NowStandard exclusions are already in effect at 80% regulatory approval — you may already be operating with material uninsured exposure and not know it
   2. →

      Engage specialty AI insurance broker to secure bespoke coverage while loss history is clean and pricing is reasonable

      This sprintThe $40M specialty market means there are only a handful of underwriters writing this coverage — early movers get better terms before the first major loss event reprices the market
   3. →

      Create a governance link between AI deployment approvals and insurance/risk management sign-off

      This quarterThe deployment team and insurance team making decisions independently is the organizational failure mode this exposure exploits
   4. →

      Raise AI liability coverage at the next board meeting as a specific agenda item with CFO and General Counsel co-presenting

      NowBoard-level visibility is the forcing function — most boards do not know their standard policies now exclude AI damages
3. 03

   The One-Week Product: When Your Moat Is Reproducible by a Newsletter Publisher with a Coding Agent

   The Existence Proof That Moved

   A non-programmer — a newsletter publisher — built a feature-complete email client in seven days that replaced a $30/month Superhuman subscription. Split inboxes, command palettes, undo-send, email rendering, unsubscribe flows. Every feature that took Superhuman's engineering team months is now a one-week project for someone who cannot write code. This is not a prototype. It is a working production inbox.

   When implementation cost approaches zero, the entire surface of competitive advantage moves to problem selection and structural positioning. The winning organizations will be the ones that can answer, in one sentence, why their product cannot be rebuilt in a week by a motivated user with a $100/month coding agent subscription.

   The Pattern Is Now Weekly, Not Quarterly

   Three data points make this structural rather than anecdotal:

   1. Airbnb: 60% of new code is AI-written — a company operating at this ratio has a fundamentally different cost curve than a competitor at 10%
   2. Stripe's projects.dev: Combines Vercel + Stripe + Supabase into single-click deployment, collapsing days of setup into minutes
   3. Factory: Positioning as a "coding harness for non-coders" — the institutional version of the one-week build

   The uncomfortable companion number: current LLMs corrupt 25% of document content in long editing workflows. Both things are true. The firms that chase the 60% without building verification scaffolding will pay for it in production incidents.

   Which Moats Survive and Which Don't

   Moat Type	Survives?	Example
   Nice UX over commodity workflow	No	Email clients, note-taking apps, project management
   Multi-tenant network effects	Yes	Slack's value is the network, not the UI
   Proprietary data	Yes	Bloomberg Terminal's value is the feed, not the interface
   Regulatory surface area	Yes	Banking software's value is the audit trail
   Distribution + enterprise contracts	Yes (for now)	Fortune 500 procurement cycles protect incumbents 4-6 quarters

   The Agent-Native Architecture Shift

   The builder deliberately added hidden selectors and debug endpoints to make his app operable by AI agents. This is the mobile-responsive moment for the agent era. Applications that expose agent-friendly interfaces become composable in automated workflows. Applications that do not become dead ends. Mandating agent-operability in product architecture today is a decision that looks cosmetic for two quarters and structural for the next ten.

   What to do

   1. →

      Audit every product in your portfolio against the 'one-week rebuild' test — identify which features exist as workflow automation vs. genuine proprietary value

      This sprintThe market has not yet repriced SaaS renewals against this reality — you have 2-4 quarters before retention cohorts reflect it
   2. →

      Mandate agent-operability (hidden selectors, API endpoints, state exposure) as a design requirement for all new product surfaces starting next sprint

      This sprintThis is the mobile-responsive moment — first-mover advantage accrues to products that become composable in AI-agent workflows
   3. →

      Set internal AI code-generation adoption target benchmarked at 40% of new code by Q1 2027, with verification scaffolding to mitigate the 25% corruption rate

      This quarterAirbnb at 60% is the benchmark — your engineering teams are either approaching that or falling behind competitors who are
   4. →

      Evaluate any portfolio companies or product lines competing primarily on 'better UX for commodity workflows' for strategic pivot or divestiture timeline

      This quarterThe floor has dropped permanently on this category — distribution moat buys 4-6 quarters at most before renewal pressure arrives