Skip to main content
a16z Podcast

What Happens When a Public Company Goes All In on AI

27 min episode · 2 min read
·
Owen Jennings

Episode

27 min

Read time

2 min

Topics

Productivity, Design & UX, Artificial Intelligence

AI-Generated Summary

Key Takeaways

  • Workforce restructuring trigger: A binary capability shift in late November–December 2025, when models like Opus 4 and Codex 5.3 became proficient with existing complex codebases—not just greenfield projects—made one or two AI-enabled engineers 10x to 100x more productive, directly causing Block's 40%-plus reduction in force concentrated on the development side.
  • Squad model replacement: Block replaced classic feature teams of roughly 14 engineers with squads of one to six people working alongside AI agents. Designers and PMs now ship pull requests directly. Internal tool BuilderBot autonomously merges PRs and completes features to 85–100%, with humans handling only the final 10–15% requiring deep contextual judgment.
  • Parallel agent workflow: Individual contributors now run 8–14 simultaneous agent instances rather than working linearly through a single pull request. The workflow shifts from sequential task completion to context-switching across multiple agents building in parallel, then reviewing, nudging, and committing outputs—a fundamental change applicable to engineers, PMs, and growth marketers alike.
  • Compliance and regulatory carve-outs: Block deliberately left its compliance team and compliance technology team nearly untouched during the restructuring. When operating in complex regulatory environments, companies should treat compliance headcount as a non-negotiable floor regardless of AI capability, maintaining human oversight to avoid regulatory and reputational risk during the transition period.
  • Defensibility through proprietary signal: Long-term competitive moats will belong to companies that deeply understand something structurally hard for others to replicate—proprietary data and domain insight—then run a continuous feedback loop using that signal plus agentic build tools like BuilderBot. Companies unable to articulate their unique signal risk being displaced entirely by AI-enabled competitors.

What It Covers

Block (parent of Square, Cash App, Afterpay) executed a 40%-plus workforce reduction in early 2026, restructuring around AI agents and squads of one to six people. Owen Jennings details how late-2025 model improvements broke the decades-old headcount-equals-output equation and what operating inside that transformation looks like.

Key Questions Answered

  • Workforce restructuring trigger: A binary capability shift in late November–December 2025, when models like Opus 4 and Codex 5.3 became proficient with existing complex codebases—not just greenfield projects—made one or two AI-enabled engineers 10x to 100x more productive, directly causing Block's 40%-plus reduction in force concentrated on the development side.
  • Squad model replacement: Block replaced classic feature teams of roughly 14 engineers with squads of one to six people working alongside AI agents. Designers and PMs now ship pull requests directly. Internal tool BuilderBot autonomously merges PRs and completes features to 85–100%, with humans handling only the final 10–15% requiring deep contextual judgment.
  • Parallel agent workflow: Individual contributors now run 8–14 simultaneous agent instances rather than working linearly through a single pull request. The workflow shifts from sequential task completion to context-switching across multiple agents building in parallel, then reviewing, nudging, and committing outputs—a fundamental change applicable to engineers, PMs, and growth marketers alike.
  • Compliance and regulatory carve-outs: Block deliberately left its compliance team and compliance technology team nearly untouched during the restructuring. When operating in complex regulatory environments, companies should treat compliance headcount as a non-negotiable floor regardless of AI capability, maintaining human oversight to avoid regulatory and reputational risk during the transition period.
  • Defensibility through proprietary signal: Long-term competitive moats will belong to companies that deeply understand something structurally hard for others to replicate—proprietary data and domain insight—then run a continuous feedback loop using that signal plus agentic build tools like BuilderBot. Companies unable to articulate their unique signal risk being displaced entirely by AI-enabled competitors.

Notable Moment

Jennings pushed back on the narrative that Block's layoffs were pandemic-era overhiring cleanup. He pointed out that the cuts fell disproportionately on engineering—not operations—arguing that no company slashes its development organization that deeply unless a technology has fundamentally changed how software gets built.

Know someone who'd find this useful?

Episode Transcript

The biggest moat is gonna be which companies understand something that's super hard for other people to understand and if your answer to that is I don't know then you maybe could get vibe coded away. Block was one of the first to make a pretty drastic decision in cutting 40% of the workforce. What led up to that decision? There's been this correlation between the number of folks at a company and the output from the company for decades and decades. I think that basically broke and what we were seeing is that one or two engineers who was on the tools is able to be ten, twenty, a 100 x more productive. Over time, it's like pretty obvious that these systems are just gonna be so much better than like having a thousand humans who are doing that work. I do believe that fundamentally for a given product or for a given roadmap, you're gonna need fewer engineers, fewer designers, fewer PMs. I think that's, like, very, very clear. So you show up on Monday, 40% of the company's gone. What's the most meaningful difference in how you're operating? I think the biggest thing is For most of the history of software, building faster meant hiring more people. The relationship was so consistent, it became a law of the industry. Headcount equals output. Block, the parent company of Square, Cash App, and Afterpay, decided to test what happens when that equation breaks. In early twenty twenty six, they restructured more than 40% of the company and rebuilt around small squads of one to six people working alongside AI agents. Teams that once had 14 engineers now run with three. Their internal tool, BuilderBot, autonomously ships features to production. Designers and PMs write code. And the company is building products like MoneyBot and ManagerBot that generate custom interfaces on the fly for tens of millions of users. This is what reorganizing a public company around AI actually looks like from the inside. A sixteen z general partner David Haber speaks with Owen Jennings, executive officer and business lead at Block. What did it actually look like for a large public company to restructure itself around AI? Owen Jennings is the business lead at Block where he oversees product, operations, and customer support across Square, Cash App, and Afterpay. Before this role, he was the CEO of Cash App during its critical scaling period. And recently, Block executed a roughly 40% reduction in force. And they've been pretty candid about AI being a critical component of that decision. Owen has gone through the AI transformation at scale across product lines and business units. And so we're gonna dig into that decision around the riff, how Block has adapted the current and future state of the business. So thank you so much, Owen. Welcome to the stage. Thanks, Taf. So Jonathan, I think, did an amazing job kinda setting the stage, you know, for this conversation, talking about how important it …

Get the full transcript (5,408 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all a16z Podcast transcripts →

You just read a 3-minute summary of a 24-minute episode.

Get a16z Podcast summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

Books, tools, and gear mentioned in this episode

SignalCast may earn commission on purchases via these links.

Tools

  • Internal tool BuilderBot autonomously merges PRs and completes features to 85–100%, with humans handling only the final 10–15% requiring deep contextual judgment.

More from a16z Podcast

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best Business Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's AI & Machine Learning Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into a16z Podcast.

Every Monday, we deliver AI summaries of the latest episodes from a16z Podcast and 192+ other podcasts. Free for one show.

Start My Monday Digest

No credit card · Unsubscribe anytime