Block's 40% AI Layoffs Just Broke Your Per-Seat Pricing

◆ DEEP DIVES

1. 01

   The Block Template: AI Layoffs Are Now a Growth Strategy — and Your Revenue Model Is in the Blast Radius

   <h3>What Happened</h3><p>On February 26, 2026, Jack Dorsey cut <strong>~4,000 employees</strong> — nearly 40% of Block's ~10,000-person workforce — and explicitly attributed it to AI making roles redundant. Block posted Q4 revenue of <strong>~$6.25B with gross profit up 24% YoY</strong>. The market's response: a <strong>24% stock surge</strong> in after-hours trading. Block's internal AI agent, <strong>Goose</strong>, delivers quantified gains: 8-10 hours saved per worker per week, 20-25% of manual work eliminated.</p><blockquote>Dorsey publicly warned: 'Within the next year, I believe the majority of companies will reach the same conclusion and make similar structural changes.'</blockquote><h3>Why This Is a Structural Shift, Not a One-Off</h3><p>This isn't a cost-cutting story dressed in AI language. It's the moment <strong>Wall Street explicitly rewarded AI-driven headcount reduction</strong> as a strategy. Every public company board saw that 24% number. Every CFO is now running the math. The $450M-$500M in restructuring charges Block is absorbing in Q1 tells you they view this as a one-time investment in a permanently leaner operating model.</p><p>The implications fork in two directions. <strong>For your own org:</strong> every role you request will be evaluated against 'could an AI agent handle 25% of this?' If you're not the one framing that analysis, someone less informed will do it for you. <strong>For your customers:</strong> if you charge per seat and your top accounts reduce headcount by 20-40%, your revenue model has a structural crack. Dorsey's prediction, whether hyperbole or not, sets the expectation.</p><h3>The Contradictory Signal</h3><p>Interestingly, Citadel Securities' data shows <strong>software engineering job postings are rebounding</strong> despite AI coding assistants — suggesting a Jevons paradox where more productive engineers create demand for <em>more</em> engineers. But non-technical roles appear to face a fundamentally different dynamic. The Citrini research report that briefly tanked Visa 4.5%, Mastercard ~6%, and DoorDash 7% before full recovery shows <strong>markets have zero consensus</strong> on AI's economic impact. Your product strategy needs to be robust across multiple scenarios.</p><h3>The Pricing Reckoning</h3><p>Seat-based SaaS pricing assumes a human logs in. When AI agents replace human operators, 'seats' become meaningless. You could see <strong>usage skyrocket while revenue flatlines</strong>. The companies that figure out agent-native pricing — per-API-call, per-outcome, per-workflow-completion — first will have a massive acquisition advantage. A 5% monthly churn rate compounds to <strong>46% annual customer loss</strong>, and agent-driven churn is <em>silent</em>: no angry email, just a flatlined usage graph.</p>

   Action items

   • Model what happens to your revenue if 20%, 40%, and 60% of product interactions shift from human seats to AI agents within 24 months. Present findings to leadership by end of Q1.
   • Build an 'AI headcount efficiency' analysis for your product org — map every workflow to AI automation potential and estimate team size at 70% current capacity. Complete before next planning cycle.
   • Reframe your AI feature positioning from 'productivity boost' to 'headcount efficiency' in your next PRD and sales enablement materials. Include specific FTE-reduction ROI calculations.
   • Pull your actual monthly churn rate, calculate the annual compound effect, and compare against the 5% monthly = 46% annual benchmark. If above 3% monthly, propose a retention-focused sprint.

   Sources:Jack Dorsey's Block Axes Staff · Anthropic CEO Says Company Won't Agree to Pentagon Demands · The Briefing: Ellisons' Hollywood Victory · 🎬 Netflix exits $83B Warner Bros. deal · Block layoffs 🚫, lying to the browser ⏰️, Nano Banana 2 🍌 · OpenAI Raises $110 Billion

2. 02

   Your Next Power User Isn't Human: Agent-First Architecture Is Now a Platform Requirement

   <h3>The Convergence</h3><p>Multiple independent signals this week confirm that <strong>AI agents are becoming the primary consumers of software</strong>, and the infrastructure to support them just crossed from experimental to production-grade:</p><ul><li><strong>Stripe's annual letter</strong> defines 5 levels of agentic commerce — from agents filling out checkout forms (Level 1) to agents that anticipate needs and buy autonomously (Level 5). Stripe says we're between Levels 1 and 2 now, processing <strong>$1.9T in 2025</strong> (1.6% of global GDP).</li><li><strong>Google's FunctionGemma</strong> achieves on-device function calling at just 270M parameters, while Perplexity is embedding AI APIs directly into Android OEM handsets.</li><li><strong>OpenAI's Realtime API</strong> went GA with improved tool use, instruction following, and lower latency — voice-first agentic interfaces are now shippable.</li><li><strong>Agent frameworks are proliferating</strong>: helm (TypeScript), Algolia Agent Studio (RAG + MCP), Cognizant neuro-san (enterprise multi-agent) all launched in the same cycle.</li></ul><blockquote>When the company that sees more commerce data than almost anyone on Earth tells you agent-mediated purchasing is the next paradigm, you build for it.</blockquote><h3>The API Agent-Readiness Audit</h3><p>The 'Every SaaS is now an API' thesis has specific, auditable requirements. Your product needs to pass three tests for agent consumption: <strong>(1) Speed</strong> — fast enough for multi-step workflows where agents chain 5-10 API calls. <strong>(2) Data model cleanliness</strong> — structured enough for LLM reasoning without human interpretation. <strong>(3) Error message clarity</strong> — descriptive enough for agent self-correction without human intervention.</p><p>There's a critical distribution angle here too. Claude Code — one of the leading AI coding agents — <strong>defaults to building custom implementations from scratch</strong> rather than recommending existing tools. If your product isn't in AI training data and recommendation sets, you're losing market share you can't even measure. This is the new SEO: optimize for AI agent recommendations or become invisible.</p><h3>The Leveraged vs. Function Agent Fork</h3><p>Two distinct agent paradigms are emerging that demand different product architectures. <strong>Leveraged agents</strong> make users more productive (can ship at 80% accuracy if UX makes correction easy). <strong>Function agents</strong> do the job entirely (need 99%+ reliability before shipping). Mixing these up — shipping a Function agent with Leveraged-agent error rates — is one of the most costly mistakes in AI product development right now. Classify every AI feature explicitly.</p><h3>The Cost Reality</h3><p>Don't assume AI compute costs are about to plummet. <strong>Hyperscaler capex is projected at $770B in 2026</strong> (up from ~$500B in 2025). CoreWeave hit $1.6B in Q4 revenue but still lost $452M. GPU rental prices for H100 and A100 are <em>increasing</em>, not decreasing. The Jevons paradox is confirmed: token prices fell ~44% since January 2026 while consumption nearly doubled. Your total AI spend will likely <strong>increase</strong> even as unit costs fall.</p>

   Action items

   • Run an API agent-readiness audit against the three criteria (speed, data model cleanliness, error clarity) by end of March. Score each endpoint and create a remediation backlog.
   • Audit your checkout/payment/transaction flows for agent-readiness: can an AI agent programmatically discover, evaluate, and complete a transaction without a human? Document gaps by end of Q1.
   • Test what happens when developers ask Claude Code, Cursor, and Copilot to solve problems your product addresses. If they build from scratch instead of recommending you, create an AI agent distribution strategy this quarter.
   • Rebuild your AI feature cost model to account for Jevons paradox — model costs as (declining unit price) × (2-4x usage growth) rather than assuming linear cost reduction.

   Sources:Building for agents 🚀, engineering taste 🎯, vibe PMing😎 · SWLW #692: End of Productivity Theater · Weekly Dose of Optimism #182 · Google Nano Banana 2 🍌, xAI cofounder departs 👋, Anthropic vs DoW ⚖️ · Nano Banana 2 🍌, Netflix loses WB bid 🎬, Block's AI layoff 💼 · Charts of the Week: DExit . . . real or feigned?

3. 03

   Anthropic's Pentagon Standoff Redraws the AI Vendor Risk Map

   <h3>The Situation</h3><p>Defense Secretary Pete Hegseth gave Anthropic CEO Dario Amodei an ultimatum: agree to <strong>'all lawful use' of Claude by 5:01 PM Friday, February 27</strong>, or face potential invocation of the <strong>Defense Production Act</strong> — a Korean War-era law designed to compel factories to produce munitions. The Pentagon also threatened to designate Anthropic a <strong>'supply chain risk,'</strong> the classification reserved for entities like Huawei. Anthropic's two red lines: no fully autonomous weapons, no mass domestic surveillance.</p><blockquote>Amodei offered to help transition the Pentagon to another provider — the first time a frontier AI company has publicly chosen principles over a $200M contract.</blockquote><h3>The Competitive Landscape Split</h3><p>Google, OpenAI, and xAI have all capitulated to the 'all lawful use' standard. Anthropic stands alone. But here's the contradiction that matters: <strong>on the same day</strong> as the Pentagon ultimatum, Anthropic quietly dropped its core Responsible Scaling Policy pledge — the hard commitment not to train more capable models without proven safety measures. CSO Jared Kaplan told Time it felt like 'unilateral disarmament.' This means Anthropic's safety positioning is simultaneously its strongest brand asset and its most unstable commitment.</p><p>Meanwhile, Anthropic's <strong>consumer growth is explosive</strong>: daily signups tripled since November, driven by Claude Code and Claude Cowork. Paid subscribers more than doubled since October. But <strong>86% of $4.5B revenue comes from API sales</strong> — making enterprise customer confidence existential.</p><h3>What This Means for Your Stack</h3><p>If the Pentagon designates Anthropic a supply chain risk, the downstream effects cascade: enterprise customers in defense-adjacent industries re-evaluate Claude dependency, procurement teams in regulated sectors flag Anthropic as a risk factor, and Anthropic's financial stability comes under pressure. Conversely, Anthropic's safety stance is a <strong>genuine trust premium</strong> for privacy-conscious enterprise buyers. The AI vendor market is bifurcating into defense-aligned (Palantir, Anduril, potentially Microsoft/Google) and ethics-aligned (Anthropic) camps. Your choice of AI vendor is increasingly a positioning statement.</p><p>Separately, three Chinese labs are running <strong>industrial-scale distillation campaigns</strong> against Claude with millions of requests and tens of thousands of fraudulent accounts — meaning Claude's capabilities are being extracted regardless of what the Pentagon does.</p>

   Action items

   • Conduct a vendor concentration risk assessment for AI model dependencies by end of March. Document fallback paths if Anthropic faces supply chain risk designation.
   • Build your own trust and safety layer on top of your LLM vendor rather than relying on their guardrails. Scope this as a Q2 initiative.
   • Evaluate multi-model orchestration (à la Perplexity's 19-model approach) as an architectural pattern for your next AI feature.
   • Add a 'government/regulatory risk' column to your AI vendor evaluation framework and update it quarterly.

   Sources:The authoritarian AI crisis has arrived · Anthropic CEO Says Company Won't Agree to Pentagon Demands · Jack Dorsey's Block Axes Staff · 🎓️ Vulnerable U | #157 · Weekly Top Picks #115 · Google Nano Banana 2 🍌, xAI cofounder departs 👋, Anthropic vs DoW ⚖️

4. 04

   Your Moat Is Thinner Than You Think — And the Clock Is Ticking

   <h3>The Evidence Is Converging</h3><p>Multiple independent signals this week point to the same conclusion: <strong>code-based competitive advantages are evaporating faster than most PMs realize.</strong></p><ul><li><strong>Agent-scraping</strong> is approaching the ability to clone production applications automatically, destroying development speed as a startup advantage.</li><li><strong>Cloudflare claims to have rebuilt Next.js's API surface with AI in a week</strong> — and Vercel's CEO personally responded with security vulnerability disclosures, confirming the threat level.</li><li><strong>OpenAI is raising $100B at a $730B+ valuation</strong>, making any AI startup valued under $10B an impulse buy. Even a $30B acquisition (Cursor) is only ~4% of OpenAI's value.</li><li><strong>GitHub pushes surged 41%</strong> between Q3 2024 and Q3 2025; iOS app releases jumped 60% YoY — AI coding tools are compressing time-to-market for everyone.</li></ul><blockquote>If an AI-powered startup cloned your core features in 3 months, what would you still have that they don't? If the answer is thin, your roadmap needs restructuring.</blockquote><h3>The Four Durable Moats</h3><p>The non-code moats framework identifies what actually survives: <strong>(1) Proprietary data</strong> that improves with usage and can't be replicated. <strong>(2) Network effects</strong> where each new user/agent makes the product more valuable. <strong>(3) Deep workflow integration</strong> that creates massive switching costs. <strong>(4) Trust and brand</strong> in regulated or high-stakes domains. Notice what's <em>not</em> on this list: UX polish, feature breadth, technical architecture. Those are all replicable.</p><p>The <strong>84% stat</strong> from this week reframes the timing: 84% of people have not yet used AI products. The market is far earlier than the hype suggests. You have more runway than you think to build durable moats — but the companies that move now to establish category-defining AI experiences will be very hard to displace once that 84% starts converting.</p><h3>OpenAI's Acquisition Map Is Your Threat Model</h3><p>OpenAI's M&A pattern reveals their five capability gaps: <strong>distribution, proprietary data, hardware, vertical AI apps, and infrastructure.</strong> The Io Products deal ($6.5B, Jony Ive hardware), Torch acquisition ($100M, healthcare), OpenClaw acqui-hire (personal agents), and failed Windsurf deal ($3B, coding tools) draw a clear map. If your product's value proposition appears on that list, you need to be either too big to buy cheaply or too embedded to replace. Amazon's proposed $50B OpenAI investment signals the AI platform layer is consolidating around 2-3 hyperscaler-backed providers — expect OpenAI API costs on AWS to become aggressively competitive, potentially below cost.</p><h4>The Vertical AI Opportunity</h4><p>All three major labs are 'on the prowl for specialized data to train their AI models.' If you've built proprietary data flywheels from user interactions, you have something OpenAI can't easily replicate — and you might be an attractive acquisition target at premium multiples. Oura's launch of a proprietary AI model for women's health, trained on <strong>clinician-vetted data</strong>, is a clean example: proprietary data moat → domain-specific model → premium personalized feature.</p>

   Action items

   • Write a one-page competitive moat memo answering 'If an AI-powered startup cloned our core features in 3 months, what would we still have?' Present to leadership this quarter.
   • Audit your product roadmap for features that overlap with OpenAI's five acquisition buckets (distribution, data, hardware, vertical apps, infrastructure). Stress-test differentiation for each.
   • Tag every major feature by moat type: code/speed, proprietary data, network effects, community/trust, or familiarity. Any feature whose only moat is 'we built it first' needs a defensibility upgrade plan.
   • Evaluate whether your product's user-generated content is indexable and contributing to organic growth. ChatGPT generates 76.5M monthly organic visits via shared conversations — a 15,200% SEO ROI.

   Sources:Narratives beat numbers 📣, non-code moats 🧱, VC liquidity shifts 🔄 · Building for agents 🚀, engineering taste 🎯, vibe PMing😎 · Dealmaker: OpenAI Builds an M&A War Chest · Cloudflare makes its own Vite-powered Next.js · Weekly Dose of Optimism #182 · Greenscreens vs. talking-heads 🟩, great productivity panic 🫨, ChatGPT's SEO audit 🔧