Block Fires Half Its People, Stock Jumps 24%

Welcome to the Architecture of Elimination

“Today we’re making one of the hardest decisions in the history of our company: we’re reducing our organization by nearly half.” — Jack Dorsey, CEO, Block Inc., February 26, 2026

On February 26, 2026, Jack Dorsey sent a message that will echo through every boardroom in the world. Block—the fintech company behind Square, Cash App, and Afterpay—cut its workforce from over 10,000 to just under 6,000. More than 4,000 people received departure notices in a single day. The company’s stock surged 24% in after-hours trading. Roughly $8 billion in market value appeared before Dorsey’s post on X finished making the rounds.

This isn’t a cost-cutting exercise from a struggling company. Block reported Q4 gross profit of $2.87 billion—up 24% year-over-year. Adjusted EPS came in at $0.65, beating analyst estimates. Full-year EPS guidance was raised to $3.66, well above the $3.22 Wall Street expected. The business is accelerating, not contracting.

Dorsey’s justification was blunt: “Intelligence tools have changed what it means to build and run a company.” He predicted that most companies will reach the same conclusion within a year.

As someone who spent a decade building high-performance payment applications and 14+ years as an enterprise architect, I’ve seen this pattern before. Not the technology—the governance vacuum around it. Block didn’t just fire 4,000 people. It wrote a template that every CEO in the world can now copy. And the architecture profession needs to respond—before it’s too late.

The Numbers That Rewrite Corporate Behavior

Let’s be precise about what happened. These aren’t projections or think-piece speculation. These are audited financial results paired with the largest AI-attributed workforce reduction in corporate history:

Metric	Value	Signal
Employees cut	4,000+ (nearly half)	Largest single AI-justified reduction ever
Stock reaction	+24% after-hours	Market reward: ~$8B in new market cap
Q4 Gross Profit	$2.87B (+24% YoY)	Cuts made during record performance
Full-year EPS guidance	$3.66 (vs $3.22 expected)	54% projected profit jump for 2026
Restructuring charges	$450–$500M	Severance, benefits, equity vesting
Engineering productivity gain	~40% more code per person	Via internal AI platform “Goose”

The 24% stock jump isn’t just a number. It’s a signal that rewrites corporate behavior. Every CEO in America watched a man fire nearly half his workforce, blame a technology with limited proven productivity gains at enterprise scale, and walk away with Block’s best single-day stock move in years. The market didn’t ask for evidence. It priced the narrative.

$8 Billion Approximate market value created the day 4,000 people lost their jobs

The Goose That Laid the Golden Excuse

Block’s internal AI platform, codenamed Goose, started roughly two years ago as a small engineering test tool. Built on Anthropic’s Claude via the Model Context Protocol (MCP), Goose has since expanded across nearly every department. Engineers reportedly ship ~40% more code per person than six months ago. Every remaining employee was already required to use AI tools daily before the announcement. AI fluency was embedded into performance reviews.

This is where the story gets interesting—and where enterprise architecture analysis becomes essential. Let me separate what’s real from what’s narrative:

What’s Architecturally Real

Block invested in a genuine internal AI platform. Goose is open-source, well-documented, and uses MCP to integrate with internal systems—from Databricks data pipelines to Square’s inventory management. Their principal ML engineer publicly stated that 90% of his code is now written by Goose. Non-engineering teams use it for compliance automation, data queries, and ticket resolution. This is a real architectural capability, not vaporware.

What’s Narrative Engineering

Block went from 5,477 employees to nearly 13,000 in three years—a classic COVID-era hiring binge. Critics on Wall Street were quick to note that Dorsey is unwinding less than half of that excess. One investor wrote: “This has much more to do with managerial incompetence than whether AI is going to take your job.”

Oxford Economics published research in January 2026 suggesting firms are “dressing up layoffs as a good news story” by attributing cuts to AI rather than admitting to past overhiring. Forrester predicts that 55% of employers who laid off workers for AI already regret it, and that half of AI-attributed layoffs will be quietly rehired—often offshore at lower salaries.

The truth? Probably both. Block has a real AI capability AND is correcting a hiring binge. The architecture exists. The 4,000-person attribution to AI alone does not survive serious scrutiny. But the market doesn’t care about nuance—it cares about the signal.

The Template Effect: Why Every CEO Is Now Watching

Block didn’t act in isolation. It crystallized a pattern that’s been building across the tech sector throughout 2025–2026:

Company	Action	AI Justification
Amazon	~30,000 corporate jobs cut	“Fewer layers” + AI as most transformative tech since internet
Salesforce	~5,000 roles eliminated	AI agents handle ~50% of customer interactions
Klarna	40% workforce reduction	AI chatbot does work of 700 agents
Shopify	Hiring freeze	“Prove AI can’t do it before hiring a human”
Accenture	~11,000 roles cut	“Those we cannot reskill will be exited”
Block	4,000+ cut (half the company)	“Intelligence tools changed what it means to run a company”

In 2025 alone, companies directly attributed 55,000 job cuts to AI—more than 12x the number just two years earlier. U.S. companies announced 108,435 layoffs in January 2026 alone, up 118% year-over-year. Employee concerns about AI-driven job loss have skyrocketed from 28% in 2024 to 40% in 2026.

Dorsey’s prediction is clear: “I think most companies are late. Within the next year, most will make similar structural changes.” Whether he’s right about AI or not, the market has already validated the template: cut hard, cite AI, collect the stock premium.

55,000+ Jobs directly attributed to AI in 2025 alone—a 12x increase from 2023

The Payments Architecture Angle: Why This Matters More Than You Think

I need to put on my payments architect hat here, because this story has a dimension most commentators are missing. Block isn’t just any tech company—it’s a payments infrastructure company. Square processes billions in gross payment volume. Cash App has 59 million monthly active users. Afterpay handles buy-now-pay-later transactions across multiple markets.

When you cut half the workforce from a payments company operating at this scale, you’re making a massive bet on architectural resilience. Here’s what’s at stake:

Transaction Integrity at Scale

Payment systems demand zero-tolerance for errors. Every transaction involves money movement, regulatory compliance, fraud detection, and settlement. Cutting 4,000 people means 4,000 fewer humans available for incident response, compliance monitoring, and system maintenance. If Goose can genuinely handle the operational load, this is an architectural revolution. If it can’t, the first major outage will be devastating.

Regulatory Exposure

Block operates across 14+ markets. Each jurisdiction has its own financial regulations, anti-money-laundering requirements, and consumer protection laws. The EU’s DORA regulation (Digital Operational Resilience Act) specifically requires financial entities to maintain adequate human oversight of critical ICT systems. Cutting half your workforce while citing AI automation may directly conflict with regulatory expectations in European markets.

The Fraud Detection Paradox

Block’s payment systems rely on sophisticated fraud detection models. AI is excellent at pattern recognition—but adversarial actors also use AI. When you reduce the human layer that interprets edge cases, investigates unusual patterns, and exercises judgment in ambiguous situations, you create exactly the kind of governance gap that sophisticated fraud exploits.

Vendor Concentration Risk

Goose runs on Anthropic’s Claude. Block’s entire productivity thesis—the one that justified eliminating 4,000 jobs—depends on a single AI vendor. As I wrote in Edition #41 about the $31 Billion Blog Post, the partner-as-competitor paradox is real. What happens if Anthropic changes pricing, capabilities, or terms? What happens if Claude experiences a major outage during a peak transaction period? Block has built its future on a vendor dependency that would make any enterprise architect uncomfortable.

AI Washing or Genuine Architectural Shift? The EA Diagnostic

For Enterprise Architects advising leadership on how to respond to the Block precedent, here’s a diagnostic framework to separate genuine AI-driven transformation from what Deutsche Bank analysts are calling “AI redundancy washing”:

Diagnostic Question	Genuine Transformation	AI Washing
Is there a measurable AI platform?	Internal AI tool with documented productivity metrics, adoption data, and integration architecture	Vague references to “AI tools” without specifics on what platform, how it’s measured, or how it integrates
Are cuts aligned with capability, not just headcount?	Specific roles identified as automatable with evidence of AI replacement capability	Broad percentage cuts across the board regardless of function or AI applicability
Is there a governance framework?	AI governance board, risk assessment, vendor due diligence, regulatory alignment	No governance structure; AI decisions made by CEO proclamation or investor narrative
What’s the vendor risk posture?	Multi-vendor strategy, fallback plans, model portability, contractual protections	Single-vendor dependency with no exit strategy or resilience planning
Does the timing match overhiring correction?	Workforce grew organically; cuts clearly tied to new AI capabilities	Massive pandemic-era hiring binge followed by cuts “because AI”

Block scores mixed on this diagnostic. It has a genuine AI platform (Goose) with documented adoption. But it also has a textbook COVID hiring correction, single-vendor AI dependency (Anthropic), and a CEO who personally watched Elon Musk run the same playbook at Twitter three years ago—from the investor table. The honest answer is that Block’s reality sits somewhere between architectural innovation and narrative arbitrage.

What Enterprise Architects Must Do Now

Whether Block’s move is genuine or theatrical doesn’t change one critical fact: your CEO has seen the 24% stock jump. The conversation is coming to your organization. Here’s how Enterprise Architects must prepare:

1. Build the AI Capability Map Before the CEO Asks

Don’t wait to be asked “what can we automate?” Map every business capability against AI maturity: which processes have AI tools deployed, which are in pilot, which are candidates, and which require human judgment by design. When the conversation happens—and it will—you need to be the one with the data, not the one scrambling.

2. Establish AI Governance Before the Cuts Start

If workforce reduction is the decision, the architecture must ensure that operational resilience isn’t sacrificed for Wall Street optics. This means: AI risk assessment frameworks, vendor diversification requirements, human-in-the-loop mandates for critical processes, and regulatory compliance mapping against EU AI Act, DORA, and local labor regulations.

3. Challenge the “Single Vendor” Thesis

Block’s entire productivity argument rests on Goose/Anthropic. If your organization is building its AI workforce strategy around a single platform, you have a single point of failure masquerading as innovation. Architect for model portability. Design for vendor exit. Build graceful degradation into every AI-dependent workflow.

4. Protect the Knowledge Architecture

When you fire 4,000 people in a single day, you lose institutional knowledge that no AI model has been trained on: tribal knowledge about edge cases, historical context for architectural decisions, relationship capital with regulators and partners. Enterprise Architects must ensure knowledge management systems capture this before the exits happen—not after.

5. Reframe the EA Value Proposition

In a world where CEOs are incentivized to cut headcount and cite AI, the Enterprise Architect becomes the last line of defense for architectural sanity. Your value isn’t in saying “yes” to every AI initiative or “no” to every reduction. It’s in ensuring that whatever changes are made, the enterprise can still operate, comply, recover, and grow.

The European Dimension: Why Block’s Playbook Won’t Work Here

For European organizations watching Block with envy, a reality check is in order:

Factor	US Reality (Block)	European Reality
Labor law	At-will employment; 20 weeks severance offered voluntarily	Consultation requirements, works councils, notice periods of 3–6+ months
AI regulation	No federal AI regulation	EU AI Act enforcement deadline: August 2026
Data sovereignty	Flexible cross-border data flows	GDPR, data residency requirements, Schrems II implications
Financial regulation	State-level, relatively flexible	DORA mandates operational resilience + human oversight of critical ICT
Worker protections	Minimal federal requirements	European Works Council Directive, Transfer of Undertakings protections

The EU AI Act coming into full enforcement in August 2026 specifically classifies AI systems used in employment decisions as high-risk. Organizations using AI to determine workforce reductions will face transparency requirements, human oversight mandates, and potential penalties up to €35 million or 7% of global turnover. European CEOs who try to copy Block’s playbook without architectural governance will find themselves in regulatory crosshairs.

This is precisely where Fractional Enterprise Architects become indispensable. European organizations need the architectural expertise to navigate AI transformation within regulatory boundaries—without the overhead of full-time EA teams that may themselves be targets of the next “efficiency review.”

The Uncomfortable Truth for Enterprise Architects

I’ll say what few in our profession are willing to say: Enterprise Architects are not immune to this wave. If AI can help CEOs justify eliminating 4,000 jobs at a payments company, it can certainly be used to question the value of architecture functions.

The profession’s survival depends on demonstrating value that AI cannot replicate:

AI Can Do	Enterprise Architects Must Do
Generate architecture diagrams	Make judgment calls about trade-offs between competing business priorities
Analyze technical debt metrics	Navigate organizational politics to get remediation funded
Draft compliance documentation	Interpret regulatory intent and design governance frameworks that balance innovation with risk
Recommend technology patterns	Build trust with executives and translate technical reality into business language
Process vendor evaluations	Exercise ethical judgment about vendor dependencies and workforce implications

The architects who survive the Architecture of Elimination will be those who position themselves as strategic advisors on AI transformation—not just technical practitioners who can be replaced by the tools they govern.

Key Takeaways

1. Block wrote the template. The 24% stock jump is now a case study every CEO and board member has seen. Expect “intelligence tools” and “smaller, flatter teams” to appear in earnings calls across the S&P 500 by summer.

2. The truth is mixed. Block has a real AI platform (Goose) AND a COVID hiring correction. The honest architectural assessment is that both are true—and the market doesn’t care about the distinction.

3. Payments infrastructure demands governance. Cutting half the workforce from a company processing billions in transactions creates operational, regulatory, and fraud risks that no AI model has been proven to mitigate at scale.

4. European organizations cannot copy this playbook. EU AI Act, DORA, GDPR, and labor protections create a fundamentally different landscape. Architectural governance is not optional—it’s legally required.

5. Enterprise Architects must lead, not follow. Build the AI capability map. Establish governance. Challenge single-vendor dependencies. Protect institutional knowledge. Reframe your value as strategic, not technical.

When the market rewards elimination, architecture becomes the only thing standing between efficiency and catastrophe.

The Architecture of Elimination is here. The question isn’t whether your organization will face this conversation—it’s whether you’ll be the one leading it, or the one being eliminated by it.

Will you architect the transformation—or be transformed by it?