That is the opening move in a 90-minute argument about productivity, AI, space, and what “fair share” means.

I watched the entire Squawk Box interview from Blue Origin’s Rocket Park so you can skip it.

Here are the 8 ideas worth stealing.

Together with Outskill:

Bezos said it best: AI elevates the people who learn to wield it

Here’s the catch. Most people use barely 5% of Claude, while Skills, Connectors and Cowork keep shipping every week.

Outskill packed 800+ hours into a free 2-day Claude Mastery Workshop: Claude plus 10+ AI tools and workflows, live this weekend:

save your Free spot !

The bulldozer is in your hands. Time to use it.

1. The Tale of Two Economies

“You have a bunch of people doing really well, and a bunch struggling to pay rent and groceries. Politicians use this age-old technique of picking a villain and pointing fingers. That doesn’t solve anything.”

One group thrives. One group drowns. The political class picks a villain, charges at it, and collects applause.

Bezos prefers the five whys: trace a broken thing to its root cause and fix it there, so the fix holds. Root-cause work is expensive. Finger-pointing is free.

Steal this: when a “fix” feels good for ten seconds and changes nothing, that is the tell. The same discipline separates the founders top VCs actually back from the ones who pitch villains.

2. The Nurse in Queens Pays $12,000 (Bezos Wants Zero)

“A nurse in Queens making $75,000 pays more than $12,000 in taxes. How about we start by having her pay nothing?”

He wants the federal income tax burden on the bottom 50% set to zero. That cohort generates 3% of federal revenue: small for the government, large for the household. $1,000 a month is rent in many cities, or a year of groceries.

Steal this: if you price for lower-income customers, run the same math. Your price ceiling sits below what your finance team modeled.

3. America Already Runs the World's Most Progressive Tax System

“We don’t have a revenue problem. The top 1% pay 40% of all tax revenue. The bottom half pay 3%. We have a spending problem.”

He flips the debate from revenue to spending. His receipt: New York City schools at $44,000 per student, 30% above Chicago, LA and Boston, triple Miami and Houston, with worse outcomes than all of them. Same country, same curriculum, triple the cost, weaker results. A company run that way dies; a school system survives because the market can’t reach it, and the waste stacks in the middle layers between the dollar and the classroom.

Steal this: before any budget cycle, ask whether existing money is spent well. Founders who treat unit economics as a daily dashboard find the answer fast, and so do the investors reading their board decks.

4. AI Hands the Engineer a Bulldozer

“There will be no more radiologists, no more software engineers because AI does it better. These people are wrong. It is going to elevate all of them.”

You dug a basement with a shovel. Someone handed you a bulldozer. The job moves up an altitude and the work survives. This cuts straight against the AI-eats-white-collar-jobs thesis running the discourse.

Steal this: audit what your engineers do, then split it into identifying problems versus typing code. The best AI coding tools already cover the second half.

5. The Productivity Surge Brings a Labor Shortage

“One earner in many two-income households will drop out by choice. Productivity gains mean people can afford it. I predict deflation in certain core categories.”

The contrarian call: families opt down to one income, so labor gets scarce rather than redundant. Food and housing construction get cheaper, assuming the technology stays loosely regulated. It reads a lot like the calls Mark Cuban keeps getting right.

Steal this: build a watchlist of three categories where AI deflation lands first (construction, food, software). Track unit costs quarterly. The signal reaches sharp investors before it reaches the headlines.

6. The Building Permit Is an AI Agent Problem

“Why does a permit take six months to five years? I should get a yes or no in 10 seconds, then the authority to build.”

Permitting is rules-checking: zoning, setbacks, height, use. A well-trained model returns a decision in seconds and lists the reasons on a no. Process time drops from years to seconds, with no policy fight required.

Steal this: municipal middleware sits wildly underbuilt. If you want a wedge, ship the permit-decision agent cities adopt. Start with how to build an AI agent and 100 agent ideas with implementation notes.

7. The Engineer's Job Was Never Typing Code

“What does a good software engineer really do? We identify problems and help solve them. The code is execution.”

Most engineers measure value in code shipped. Bezos says that metric was always off. The problem-identification layer survives automation, while syntax expertise loses ground each quarter. Engineers who move into product thinking and systems design pull ahead.

Steal this: list the last five problems you solved in code. For each, did you find the problem, or did someone hand it to you? That ratio tells you who survives the transition.

8. For-Profit Value Beats Charity

“If I do my job right, the value to society from my for-profit companies will be far larger than my charitable giving.”

His giving rule is independence over dependence: he funds family shelters with sub-180-day stays that teach interviewing, skills, and financial management. The deeper claim is one tech intuits and rarely says aloud. A company solving a problem for hundreds of millions creates more aggregate welfare than a large foundation, because exchange stays voluntary. Customers pay when value beats price, the same logic behind every method used to value a company.

Steal this: if your company delivers value, treat it as your primary moral act. The giving is the company.

What to Steal Today

The doctrine distills to six moves: stop pointing fingers, fix spending, untax the bottom half, treat AI as productivity, build companies that create value, and trust root-cause analysis.

Founders: the bulldozer is in your hands. The work was never typing, it was finding problems worth solving. Map your week against that ratio. If you are raising on the back of it, study the decks that built unicorns and what top VCs check in diligence.

Investors: the productivity gains point to labor shortages and core deflation. Build a watchlist around cheaper construction, food and code, and keep the investor lists close for the rounds that follow.

Operators: the five whys is free. Use it on every broken process this month. Fund causes, not costumes.

For the AI thread running under all of this, The AI Corner tracks AI agents, tools and models, and where the jobs debate goes next.

If this saved you 70 minutes, send it to one founder or investor who needs it.

Full podcast:

The gap is rarely talent. It is knowing which steps matter and which to skip.

This is the path production agents actually run, stripped to the parts that ship. Copy the code, follow the seven steps, and your agent goes live today.

A year from now, building an agent will feel as routine as writing a script. The people who learn it this week run the teams that lean on it later.

Here is the full build:

▫️ The 7-step path, from picking the problem to a running agent, each step with the copy-paste asset

▫️ The minimal Agent SDK starter, a working agent in about 15 lines, plus the custom-tool pattern

▫️ The reusable system-prompt template that makes an agent behave the same way twice

▫️ 5 first agents worth building this week, each with the tools it needs and the hours it gives you back

▫️ The build-or-script decision that saves two weeks of wasted effort

▫️ Memory done right, the three levels, and the one most beginners over-build

▫️ A full worked agent, an inbox-triage agent wired end to end and ready to clone

▫️ The guardrails, hooks and permissions that keep an autonomous agent safe

▫️ The cost controls, model routing and caching that keep a 24/7 agent cheap

▫️ The debugging checklist for the moment it breaks on a live task

▫️ The framework picker, Claude Agent SDK versus LangGraph, CrewAI, and Managed Agents

🤖 The First Agent Build Kit

The full system in one place: the 7-step path, the copy-paste Agent SDK starter, the system-prompt template, 5 ready-to-build agents, memory done right, a full worked agent, the guardrails, the cost controls, the debugging checklist, and the framework picker.

One subscription unlocks every build kit

This is one kit in a growing library. Premium opens all of them:

▫️ Loop engineering for coding agents

▫️ Build a five-agent sales team in a weekend

▫️ The Claude managed agents guide

▫️ The Claude best practices power-user guide

▫️ The Codex background workflows playbook

▫️ The one-person startup operating system

Plus a fresh build kit every week. One agent shipped from these guides pays for the year in the first afternoon.

Try premium free for 7 days. Or get 50% off this week only.

Get 50% off forever

Read more

His playbook is teachable. That is the whole opportunity.

You can encode an operator’s rules into agents that run the motion for you: source, enrich, sequence, forecast, expand. Your people keep the part that closes deals, the judgment and the room.

Most teams bolt AI onto a broken funnel. This wires operator-grade GTM into a system that runs itself.

Here is the full build. Behind the paywall:

▫️ The 8-agent GTM stack, each one mapped to a proven operator rule, with the copy-paste prompt

▫️ The operator rules as guardrails, so your agents inherit the discipline that scaled revenue, rather than generic best practices

▫️ The 3 workflows that chain them, the morning loop, the outbound loop, and the forecast loop

▫️ The brutal-negativity forecast agent that keeps your pipeline honest and your board trust intact

▫️ The land-and-expand agent that turns one small contract into a whole-account motion

▫️ The tool stack, Clay, HubSpot, Claude, and the connectors that let agents act inside your systems

▫️ The keep-it-human map, the GTM work to protect from automation

▫️ The 30-day rollout, from your first agent to a self-running engine

Pair it with the deeper AI Corner library:

▫️ The AI Agents library for orchestration and reliability

▫️ The Prompting and Context Engineering library for the agent prompts

▫️ The AI Tools and Models library for the stack

▫️ The Business and Investing library for the revenue math

Related builds worth reading next: the five-agent sales team, loop engineering, the how to build an AI agent guide, and the VC founder playbook.

🛠️ The GTM Agent Stack

The full system in one place: the 8 agents with copy-paste prompts, the operator guardrails, the 3 workflows, the tool stack, the keep-it-human map, and the 30-day rollout.

Get The GTM Agent Stack below 👇

Try premium free for 7 days. Or get 50% off this week only.

Get 50% off forever

Read more

Has your friend already built an AI agent? He probably did, and described it excitedly over coffee:

“My AI agent watches my inbox, tags each email, drafts a reply, sends it!”

Four steps, same order, every single time, nothing about it deciding anything on its own.

The problem is… that is not really an AI agent. It is a workflow wearing a more expensive name.

The word has done real damage this year. Companies are buying autonomy they will never use, skipping the work that would have made it pay, and filing the result under “AI doesn’t work for us.”

In reality, it works fine. They just never figured out which of two very different things they were building.

That difference decides whether the money compounds or evaporates. It is also the easiest thing in AI to get right, the moment someone hands you the question that actually sorts it.

Something worth knowing before we get into it:

The people actually shipping AI systems in 2026 are overwhelmingly from non-technical backgrounds.

Lovable just published a data study on this, and the numbers are worth sitting with for a second:

The barrier between idea and running product has essentially collapsed.

This is the story nobody is telling loudly enough. Software creation used to be a narrow technical discipline. It is becoming something much broader. Operators, founders, marketers, and domain experts are shipping real products by themselves, without a dev team, without a technical co-founder, without months of runway burned on engineers.

The barrier between “I have an idea” and “I have a running product” has essentially collapsed. If you have been sitting on something because you assumed you needed an engineer first, that assumption is no longer accurate.

Start building on Lovable

Exclusive 10% off for readers.

Everyone wants the shiny AI agent. Most teams just need the boring workflow. And now, anyone can build either one themselves.

Table of Contents

1. The Only Difference That Counts

2. Why Most of What You Want Is a Workflow

3. You Can’t Buy Your Way There

4. The Filter Nobody Bothers to Apply

5. Where to Actually Point It

6. The Part You Won’t Want to Hear

1. The Only Difference That Counts

One question splits every AI system into a workflow or an agent. And it all boils down to:

Who decides the steps?

A workflow runs your script

A workflow walks a path someone already drew.

The sequence is locked before a single email arrives, and the model only fills the slots that need a brain.

Back to that inbox. Sort by topic, pull the order, draft from a template, send.

The model does the sorting and the writing, but the road never bends. It cannot read a strange message and decide today calls for a detour.

A recipe is the closest thing to it. The cook is skilled and the knife work is real, but the steps and their order belong to whoever wrote the card.

Underneath, almost every workflow turns out to be one of three plain forms. Chain the steps so each output feeds the next.

Classify the request up front, then send it down its own lane. Or fire several checks at once and gather what comes back.

Dress it up however you like, that is most of business automation.

An agent writes its own

An agent starts from a goal and a toolbox, then builds the road as it walks.

First move, second move, whether to circle back, when to quit. None of that lives in a script.

Same inbox, different animal. The agent reads a complaint, decides on its own to open the order system, spots that the package shipped cracked, checks what the refund policy permits, sends the money back, and writes the customer a note.

Nobody choreographed any of it. The thing reasoned its way through in real time.

That improvisation is the entire appeal and the entire hazard. A workflow keeps your plan. An agent throws the plan away and bets on itself.

Every real argument about cost, risk and control grows straight out of that one fact.

2. Why Most of What You Want Is a Workflow

The instinct runs backward. Founders reach for the harder, smarter-sounding option, certain their problem deserves it, when the plain one fits almost every time.

At the end of the day, the agent is the exception and not the opening move.

Agents feel like the real thing

An agent looks like arrival. Autonomous, reasoning, deciding without anyone holding its hand.

Building one feels like graduating from plumbing to intelligence, and that feeling has sold an enormous amount of software nobody needed.

Look at the actual work, though. Tagging tickets. Summarizing a contract. Drafting a first pass. Lifting figures off an invoice. Tidying a CRM record.

Every one of those has a known form, and a workflow handles known forms cheaper, faster, and without a surprise at 2 a.m.

Autonomy is never free. An agent can loop on one step until the credits run out, talk itself into something absurd, or stall in a corner you never thought to test, and because the reasoning happens in the dark, you may never learn why.

The bill for that freedom arrives as cost, as debugging time, and as the runs that simply go wrong.

The honest test

A ten-second test ends most of these debates. This is it:

Could you draw the flowchart yourself?

Yes means build the workflow. The path is knowable, so write it down. What comes back is steady, the kind of thing a junior engineer can fix on a Tuesday without paging anyone senior.

A real no, where the right steps genuinely hinge on what the system uncovers and reshuffle on every run, is the one place an agent earns its keep.

Even there, letting it roam loose is the rookie error. So put structure around the autonomy.

The agent owns the open-ended part, but it runs inside a process with checkpoints, a log of everything it touched, and a human gate at the moments that carry money. The flexibility survives and the blindness dies.

That hybrid has a name, the “agentic workflow”, and for the handful of problems that truly need a mind of their own, it beats a naked agent nearly every time.

3. You Can’t Buy Your Way There

Choosing the right architecture clears half the problem. The other half kills more projects than any model ever has, and it is the quiet belief that value ships in a box you can buy and bolt onto this morning’s process.

The lesson from the last big rewiring

Think of it like this:

Electricity reached the factory floor decades before it paid a dime. Owners ripped out the steam engine, dropped an electric motor in the same spot, and changed nothing else. Output barely moved.

The payoff waited on a smaller idea. Motors could be cheap and tiny, so every machine could carry its own, so the floor no longer had to crowd around a single shaft of power. Arrange the machines in the order the work actually flows, and you have invented the assembly line.

Nobody got rich buying the motor. The money lived in redrawing the whole building around what a cheap motor suddenly made possible.

Redesign beats a shopping spree

AI repeats the pattern beat for beat. A license here, a seat there, the process underneath frozen exactly where it stood.

The tools see a little use, the results land flat, and a meeting goes on the calendar to ask where the magic went.

A system that does not understand how the work truly happens gives back nothing worth keeping. The people who own that work and were never consulted will route around it on instinct, and adoption stays thin no matter how clean the demo looked.

The honest move is to take one process and cut its work into three piles.

1. Rule-bound steps get scripted.

2. Judgment steps go to AI inside a workflow.

3. The heavy calls stay with a human who has to answer for them.

Most of the value hides in the first two piles, not in some oracle that does everything at once.

Going live is not a switch, either. Run it in a sandbox, then in shadow mode beside the people still doing the job by hand, then in supervised production once it has earned a little trust.

Log every action and every correction so the thing keeps sharpening instead of freezing at the accuracy it had on launch day.

4. The Filter Nobody Bothers to Apply

Workflow or agent is the second question. The first one, the one almost everyone walks straight past, is whether the task deserves automating at all.

Skip it and a full month can vanish into something that never held a payoff.

Four things worth checking first

Volume leads. The task should run hundreds or thousands of times a month, or touch enough money that improving it lands on a real line of the books.

Pattern follows. Not carbon-copy identical, but regular enough that rules and old examples still bite.

Scatter belongs on the list too. The more a person bounces between Gmail, Slack, a spreadsheet and the CRM to finish one task, the more an automation has to pull together.

Last, the pain has to sit still long enough to measure. Hours burned, errors logged, deals stalled, a number you can name today and check again later.

No measurement, no way to know you won.

Run a candidate against all four bars and watch most of them trip on at least one, which is the entire point of owning a filter.

Write it down before you wire it up

One step decides the result, and it touches no software at all. Write the process out by hand. Every move, every odd exception, in the words a person would actually use to explain it.

Output quality sits downstream of input clarity, almost completely. Feed the model fog and it hands fog right back. The slop everyone pins on AI is usually slop somebody fed in first.

An afternoon of honest documentation, then handed to the model to draft a plan and pick fights with your logic, is the highest-return hour in the whole build. It happens once per process and never again.

5. Where to Actually Point It

Knowing the difference is dead weight without a place to aim it. A short list of functions keeps surfacing as the right first ground, because the work there runs nonstop, sprawls across systems, and bores everyone unlucky enough to do it by hand.

Start in the back office

Accounts payable is the cleanest opening move in most companies. Invoice intake and purchase-order matching are rules in a costume, so script them.

Coding entries to the right account asks for a little judgment, so let AI take the first swing and let a person check the odd ones. Cheap to baseline, miserable by hand, easy to love.

Procurement lives on context buried inside contracts, portals and inboxes. Onboarding a vendor or testing compliance means dragging facts out of six open tabs.

Automate the dragging and leave the sourcing and the negotiating to people who can read a room.

Operations is a machine built for exceptions, and routing them is repetitive, patterned, automatable work. Returns and allocation blend hard rules with judgment, so a workflow with a human watching the expensive calls beats setting a loose agent free in the warehouse.

The pain, the delays and the misroutes, sits in plain sight and counts itself.

Then the revenue side

Sales buries fortunes in clerical work. One large deal can cross six teams and eleven handoffs before anyone signs. Routing it, enriching the CRM, running commission math, all of it devours hours a rep should spend across the table from a buyer.

Lift it off their plate and you hand back the only resource they cannot make more of.

Marketing is the most tempting ground to automate and the easiest to wreck. Lead scoring and routing is high-volume and pattern-rich, a strong early bet, as long as a human still studies the borderline names instead of trusting the score blind.

Botch this one and the cost is not wasted minutes, but most likely dead deals.

Content is the piece everyone sprints at and limps away from. Treat it as a button that prints posts and you get exactly what that sounds like. The win is feeding it something that already worked and reworking that across formats, so the model recasts proven ideas instead of conjuring hollow ones from a cold prompt.

Campaign reporting earns its automation the second the volume starts to ache. Hauling numbers out of ad platforms, email tools and analytics into one straight answer is repetitive and scattered, the precise sweet spot.

One channel trips the volume bar. Ten channels pays you back every Monday you stop losing to the rollup.

Customer research rewards you in proportion to how far people have to dig today. A rep assembling the company site, fresh news, old tickets and CRM history before every call is doing exactly the hunt an automation erases. A clean single source of customer truth shrinks the prize, so slide it down the list.

Pipeline hygiene is the dull one worth doing first anyway. Records kept current, stale deals flagged, blank fields chased down. It never stops, reps loathe it, the cost is trivial to measure, and a wrong move costs nothing to undo.

One line ties the function together. Give the busywork to the machine so people pour their hours into judgment and relationships, where revenue is genuinely won and lost. Automate the friction around the human work, never the human work itself.

Outreach mass-produced with nobody in the loop reads as exactly that, and it spends the trust you were trying to earn.

6. The Part You Won’t Want to Hear

Failed AI projects rarely die of bad models. The models are fine.

AI projects die because someone bought autonomy the business would never touch and skipped the unglamorous work that turns any of this into money.

That unglamorous work is the entire game.

Map a process by hand, script the dull stretches, point AI at the judgment, keep the weighty calls human, then measure what actually changed. None of it looks good on a slide. All of it shows up on the P&L.

The companies pulling ahead are not the ones with the flashiest agents. They are the ones who ran that boring loop once, watched it pay, then ran it again on the next process, and the next, until the whole place had rebuilt itself around work that compounds.

The agent can wait. The honest first step is admitting the thing you needed was a workflow, and that chasing the cooler toy is what slowed you down.

That refusal to flinch is the whole story.

I watched the full Circuit documentary so you can skip it. Here are the 10 takeaways that matter.

One thread runs through them: once AI takes the execution, the edge moves to judgment and go-to-market craft. Fitting, given who powers this issue.

Together with Attio:

Dario’s point cuts to one question: what do you do that AI struggles to replicate?

GTM Atlas Volume II is the operators answering it, with six new entries live:

▫️ What only a human can deliver by Travis Bryant, Anthropic’s Head of US Mid-Market GTM

▫️ Hire for slope, not for pedigree by Cristina Cordova, COO of Linear (ex-Stripe, Notion)

▫️ Your product is the pitch by , Head of Growth at Lovable

Plus a perk stack from Wispr Flow, Granola, Notion, and Anthropic.

Steal the systems the best operators run right now:

Explore the Free GTM Atlas

Now, to Dario, starting with the half of the automation curve almost everyone skips.

1. The automation curve has a brutal second half

“You automate 90% of the job, great. People are 10 times more productive in the other 10%. But eventually it gets close to 100%. Now, the sequel to that is, well, then you have to find something else for them to do.”

Most analysis stops at 90 percent and calls it a productivity revolution. Dario keeps going. For some workers, AI already replaces rather than augments, and augmentation and replacement turn out to be the same curve, the same people, separated by time.

At Anthropic, Claude writes almost all the code today. Engineers feel superhuman, which is exactly why the endpoint hides. The window to plan for the second half is open now, while it still reads as good news.

Track before the turn:

▫️ Which roles you augment today

▫️ Which roles raise output while headcount holds flat

▫️ Whether your workforce plan accounts for the second half at all

Why it matters: the companies that survive the second half built for it during the first. Plan for the jobs turn ahead of the curve announcing it.

2. The super weapon Anthropic held back

“Some of the early companies that we gave this to said things like, this is a super weapon. You should have to own a gun license to use it. Please don’t release this.”

A project called Mythos sits under every public Anthropic story. It found thousands of cybersecurity vulnerabilities and mapped exploitable flaws across every major operating system. Anthropic’s own read: released openly, it could hack banks, reach state secrets, and hit critical infrastructure.

Dario calls it “a particularly large jump,” one that arrived ahead of any internal schedule. The response was Project Glasswing: controlled access for a few trusted organizations, federal agencies included. It is the first live test of whether a private company can hold that much power responsibly.

Why it matters: enterprise and government buyers now bet on which vendors hold the governance to handle a Mythos-level event. The labs with pre-set release criteria set the precedent the rest follow.

3. One engineer, zero lines of code, 17x growth

“Now I talk to my Claude and it writes the code. And then while it does that, I talk to the next Claude and it writes some code. And at any point I have either a few Claudes running and up to a few thousand Claudes running, doing things.”

Boris Cherny, the engineer behind Claude Code, spent six months coding through Claude rather than typing syntax. This is parallelized AI labor: dozens to thousands of instances running at once on complex tasks. Claude Code’s internal volume at Anthropic is up 17x year over year, and one Code with Claude attendee put it plainly: “I have the confidence of a 22-year-old with VC money.”

The job changed. The winners orchestrate the most parallel agents against the hardest problems:

▫️ Understanding what is worth building

▫️ Judgment on direction and priority

▫️ Directing agents toward the right goal

▫️ Knowing when to override the output

Why it matters: treat this as a tool and you go 10x faster. Treat it as a replacement for thinking and you become replaceable. Judgment survives, execution commoditizes.

4. A 25% chance of collapse, and the airline test

“If there was a 25% chance of an airplane crashing, you wouldn’t get on that plane. That’s right. 25% is too high. We’re trying to make that probability much, much lower. That is the goal.”

He puts collapse odds at 10 to 25 percent and holds the number under pressure. His logic: the technology exists, many actors will build it regardless, and collective action is the hardest problem class in history, so one player opting out shifts little. The better move is to sit at the frontier with the most safety-focused team.

The person building the thing is telling you the risk is genuine. That is the data point. Reducing that number is half of Anthropic’s operating budget, and the same person who calls 25 percent too high builds harder, faster.

Why it matters: a 10 to 25 percent risk estimate belongs in scenario analysis and board conversations as a planning input, from the CEO of the most valued AI company by revenue.

5. Why he left OpenAI, and what actually drove it

“When you feel that you can’t trust someone, when you feel that their values are not what they say they are, when you feel that they’re not honest, that makes it very hard to continue to work with the company.”

Coverage compresses Dario’s exit into safety disagreements. The deeper driver was trust. Safety frameworks invite honest disagreement among smart people. A gap between stated values and actual behavior is a different category, and once it opens, the argument ends.

The number that says the rest: every Anthropic co-founder still works there, which at this scale and under this much Pentagon and competitor pressure is rare. That cohesion is a competitive asset.

Why it matters: trust is the load-bearing wall of every partn

6. The Pentagon blacklisted them, and the lines held

“What does winning this fight actually look like? I won’t even call it a fight. This is more a debate about what the proper use of AI by the government is.”

Anthropic wrote its red lines before the meeting: bans on mass surveillance, human oversight required on any targeting. The Pentagon pushed to strip them, Anthropic held, and the blacklist followed. Lawsuits came, Trump called Dario “an ideological lunatic,” and the ban later lifted with the lines intact.

The lesson sits in the sequence: specificity before the meeting beats philosophy after it.

Why it matters: the companies that built Washington credibility during calm periods gain leverage when the next capability reveal forces a policy response. Define your red lines before the room.

7. A school was hit, and Claude was in the chain

“What we’ve seen here is Claude assists, but a human makes the final call. So a human made that final call, not Claude. Imagine if you had a world in which the AI model just makes the decision and the human never sees it. That’s what we were standing up for.”

A US missile hit a girls’ school in Iran, more than 150 people died, and Claude may have been in the targeting chain. Dario calls the strike terrible and separates two questions most coverage fuses: was the outcome acceptable, and was the decision architecture acceptable.

The counterfactual is the hard part. The alternative to Claude assisting under human oversight is AI from less careful actors making lethal calls with a human fully outside the loop.

Why it matters: “human in the loop” is the load-bearing phrase in high-stakes AI. Every org using AI in consequential calls needs a written answer to one question: who makes the final call, and how do you verify it happened?

8. The bet everyone called crazy

“At that point in time, I know it sounds crazy now looking back, not a lot of people believed, hey, scale-up is the way that these models are going to get smarter and better. That was sort of an unusual, countercultural, scientific perspective.”

Before ChatGPT made scaling obvious, Dario argued it would work: add compute and data to large models and they improve, predictably, on the same algorithm. In 2016 that read as fringe, and the founding team held it anyway. They were right.

The rarer thing is the conviction held under social pressure for years until it paid out. To spot the 2025 version: find the belief researchers hold privately, consistent for two-plus years under pressure, where the holder stays put when the room pushes back.

Why it matters: Anthropic’s whole position traces to one technical conviction held under resistance. The next decade-long return hides inside a belief today’s consensus still calls wrong.

9. $285 billion gone in a day, and why the pie still grows

“The existing incumbents may be smaller in relative terms. Some of them may go down in value. Some of them may even go out of business if they don’t adapt. But I would guess that the software industry gets larger, not smaller, although there will be some big losers.”

Claude Cowork launched, and $285 billion in software market cap vanished in a day. Traders called it the SaaSpocalypse. Dario’s actual view is more useful: total software grows while distribution shifts hard. Those are two statements, and fusing them is how sharp operators misread the moment.

Which side you land on:

▫️ You can name what your product does that AI struggles to replicate

▫️ That answer is specific, defensible, and hard to build around

▫️ Your users would lose something irreplaceable if you vanished

▫️ Your moat lives in the workflow, the data, the relationship, or the judgment layer

Try this: complete the sentence “AI can do everything we do except ___.” A specific, defensible ending is your moat. A blank is the work to finish before the next launch ships.

10. Silicon Valley yo-yoed on regulation. Dario held the third path

“They started with a position of, you know, even having transparency around this technology is all just totally apocalyptically destroy our potential. And then as soon as they see the first real danger, there’s all this talk of nationalization and the government should just seize it. Come on, folks.”

Silicon Valley swung from “any regulation kills us” to “nationalize AI” inside one capability reveal. Dario stayed put. His position is specific: the technology rides a smooth exponential, it keeps getting more capable, and governance belongs in place ahead of the crisis.

His mechanism:

▫️ Pre-release testing and auditing before any major model ships

▫️ Accountability that skips government ownership

▫️ Transparency enough that outsiders verify what labs claim

▫️ A line between “the government should know” and “the government should own”

Why it matters: the policy fight stays open, and the next reveal forces another response. Show up with consistent, specific positions. The ones who held them help write the rules.

What this means for you

Dario runs the most valued AI company by revenue, believes civilization faces a meaningful chance of collapse, and builds harder anyway, because handing the lead to someone less careful is the worse outcome.

Three principles to carry forward:

1. The automation hump reads as productivity until it turns. Build for both halves while it still feels like good news.

2. Trust is the actual reason partnerships break. Values that drift from behavior end things faster than any strategy fight.

3. The smooth exponential feels like stillness until it goes vertical. Most people are standing in that flat stretch right now.

Founders: build something that compounds on the right side of the curve. Physical world, human judgment, or directing AI at scale: pick one lane deep enough that the next Claude launch makes you harder to replace. Write your moat answer down before the next reveal.

Investors: Anthropic went underdog to trillion-dollar in four years on two contrarian bets. The next decade-long return hides in a belief the current consensus still calls fringe. Back the person who holds it and stays put.

Operators: the SaaSpocalypse repeats. Map where your users lose irreplaceable workflow context if you vanished. That is your moat.

Quiet, quiet, quiet.

And then zoom.

Plan for the zoom.

Keep reading

Anthropic, Claude, and the power fight

▫️ Claude and Anthropic library

▫️ Inside the Fable 5 and Mythos government ban

▫️ Anthropic passed OpenAI at $30B ARR

▫️ Dario Amodei on safe AI and AGI

Agents, Claude Code, and the new job

▫️ The Claude Code system that replaces your dev loop

▫️ Loop engineering for coding agents

▫️ Claude managed agents guide

▫️ The Anthropic AI jobs report

Moats, markets, and the SaaS shift

▫️ SaaS defense playbook for the AI era

▫️ Marc Andreessen on the AI moat

▫️ The biggest VC-backed startups

▫️ The investor list of lists

Full documentary

If this breakdown saved you 47 minutes, share it with one founder or investor who needs to see it. They will thank you later.

One of the most powerful companies in history almost slept through the biggest platform shift in a decade.

Google held every ingredient: the talent, the data, the compute, and a decade of AI research sitting in the building. Then ChatGPT shipped, and for a few months the giant looked flat-footed while a startup set the pace.

What Sundar Pichai did next is the part worth studying. He rebuilt the entire company in 18 months, in a deliberate order most analysts read right past.

He walked through it with Nilay Patel on Decoder after Google I/O 2025. I went through the full 45 minutes so you can keep yours.

Here are the 10 moves that matter, and the thread running through every one:

Raw capability counts for little until you organize to act on it.

Founders feel that sharpest at go-to-market, where a beautiful plan and an empty pipeline weigh exactly the same.

together with HubSpot for Startups:

Pichai’s lesson is execution over planning. Here is the go-to-market version of it.

On June 18, HubSpot for Startups and Clay run a live build-along for seed and pre-seed founders. You build it in the room with them:

▫️ Define your ICP from genuine buying signals

▫️ Build and enrich a prospect list in Clay

▫️ Launch AI-personalized outbound in HubSpot

You leave with pipeline, rather than a plan.

Apply to HubSpot for Startups and you become eligible for up to 90% off HubSpot, plus a shot at $1,000 in Clay credits.

📅 June 18, 11 AM ET (4 PM CET). 45 to 60 minutes, live:

Save your FREE Seat

With that on your calendar, back to Pichai, starting with the diagnosis almost everyone missed:

1. Pichai read the ChatGPT shock as permission

“I always internalized that moment. It was tough to convey it outside. But I felt like the Overton window had changed. People were adopting these technologies faster than we had expected. And so to me, it was a way to go and actually express ourselves through our products.”

Most teams read a rival’s breakthrough as a gap to close. Pichai read it as clearance to move.

Google held the ingredients. What it missed was the organizational readiness to deploy them, so the ChatGPT launch exposed a structural deficit rather than a capability one. He diagnosed that first, and the order is the whole difference between a strategic response and a reactive one.

The useful question after a competitor’s big launch skips past “are we behind.” It is “do we hold what we need to move, and are we organized to use it.”

Why it matters: a shock stays existential only while you lack the assets to answer it. Hold them, and the shock becomes permission. The teams still standing after the wave diagnosed the bottleneck before touching the org chart.

2. Merging Brain and DeepMind: the 5-step sequence that followed

“One AI team, we had world-class research teams in Brain and DeepMind. Bringing that together as Google DeepMind was harder than it sounds because it’s like saying, go put Stanford and MIT together and create a department out of it.”

From outside, Google DeepMind looked like a branding call. Pichai calls it the hardest part of the entire restructuring: two elite, proud, culturally distinct research houses fused into one model capability.

Merging two functions that both succeed and both believe they are right is harder than shutting one down, and most companies stop short of the will to do it. The moves that followed were sequenced on purpose:

▫️ Unified AI research under Google DeepMind

▫️ Centralized infrastructure under Amin Vahdat

▫️ Created a Chief AI Architect role, filled by Koray

▫️ Consolidated Search under single leadership

▫️ Weekly AI product reviews run by Pichai himself

Why it matters: each move set up the next. Research, then infrastructure, then accountability, then decision speed. Founders restructuring under pressure should map dependencies the same way, since sequence decides whether a restructuring compounds or collapses.

3. The 90-day filter that sets your decision speed

“A big part of my framework is over time understanding that there are very, very few decisions which are really consequential, and most decisions aren’t. So what matters much more is that you make the decision, because that’s what determines the velocity of an organization.”

This line runs counter to how most founders were trained. Treating every decision as heavy creates the same jam as treating every decision as light.

The distinction Pichai draws is simple: some choices look big yet reverse inside 90 days, and others lock in. Combining Brain and DeepMind was the second kind. Most product launches are the first, and experience is what lets you sort them fast.

Why it matters: organizational velocity comes from decision throughput on the reversible calls. Before your next decision stalls, ask one thing: can we fix this in 90 days if we are wrong? A yes means make the call and move. That single filter buys more speed than any process overhaul.

4. 13 products, one infrastructure layer, a moat that compounds

“For the first time, we have such a common infrastructure powering all of them with our Gemini models and the underlying AI infrastructure. So we are more able to, with intent, do things which cut across things.”

The fragmentation critique of Google is as old as the company, and the 2025 answer is structurally new. Thirteen products, each with a billion users, shared distribution for most of Google’s history yet ran on separate technology.

Gemini changes that. One model and one intelligence layer now power Search, Maps, Gmail, and Docs from a single base. Personal Intelligence is the proof: one infrastructure build, one user toggle, every product upgrades at once.

Why it matters: platforms with common infrastructure compound, because each improvement reaches every surface at once. Google’s moat here is architectural depth multiplied by distribution scale, and matching one side leaves the other gap wide open. Few rivals close both inside 36 months.

5. Agents finally deliver Google's 10-year assistant dream

“This long-running vision of Assistant we’ve all had and worked through myriad forms of it, and failing to fully do it well. I think we are closer than ever before to deliver on that promise. We haven’t delivered it yet.”

That admission is worth isolating. Google Assistant, Duplex, a decade of attempts, all fell short. Agents are the first technology able to execute the original vision, on four building blocks Pichai sees finally in place:

▫️ Reasoning across a problem

▫️ Tool use and code execution

▫️ Planning over multiple steps

▫️ Long-running task management

The same stack underpins what teams now ship with Claude Code and agent loops.

Why it matters: the agent paradigm is durable because it pays off a user expectation that already existed for a decade. Products that deliver an old promise grow faster than products that ask users to believe in a new one, so the adoption curve is shorter than it looks.

6. Pichai called a live Search result wrong on camera

“I think it’s probably more opinionated than it should be for the particular query you showed me. That’s my reaction as a user. I think that’s the scope for improvement.”

The most candid exchange in the interview. Patel ran a live search for “best Chromebook,” the AI overview gave one answer, Reddit gave another, the Times gave a third, and Pichai owned the problem on the spot.

The tension underneath is structural. The more AI overviews answer directly, the more useful Search feels, and the less it surfaces the organic content underneath. Google’s stated check is measurement: 25 years of satisfaction data, bounce rates, session length, return visits.

Why it matters: watch AI overview accuracy against click-through to organic results over the next 18 months. That gap is the cleanest signal of whether Search strengthens or erodes, and it shapes how you should rank when AI answers the query.

7. Conde Nast told its teams to plan for zero search traffic

Conde Nast CEO Roger Lynch: “Every year our search traffic was down more than we had forecast. So last year I told our teams, assume there is no search. You have to have your businesses planned as if search is zero.”

Google Zero moved from a publishing meme to a formal planning assumption at one of the largest media companies on earth. Pichai’s reply pointed to surfacing quality content, filtering low-quality clicks, and growing information overall. Each holds up, and each sidesteps the core worry.

The worry: AI overviews answer the question so well that the click vanishes. A great answer can produce zero traffic, because intent and outcome are separate things.

Why it matters: every business living on search referral should already hold its own version of the Conde Nast plan. Planning around the loss of a channel you fail to control is the rational baseline, so build the GEO playbook and your AEO backlink sources now, ahead of the curve forcing it.

8. Pichai calls AI anxiety rational, and that reshapes consumer AI

“No, I don’t think so. That’s the point I’m making. I’m, in fact, arguing against it. People are standing and telling about how AI could make a lot of jobs go away. Why wouldn’t you feel a sense of anxiety about it? I think those are deeper issues which we have to tackle as a society.”

Several executives frame public distrust of AI as a messaging miss that better demos fix. Pichai rejects that outright. In his telling the anxiety is grounded: job displacement fears hold weight, and energy concerns are legitimate.

The gap between polling (young people broadly dislike AI) and usage (nearly a billion users) reflects genuine tension rather than confusion. Closing public trust means solving the underlying problems, and reframing them leaves the gap open.

Why it matters: founders building consumer AI should plan for a trust deficit that marketing fails to fix. Products showing immediate, personal value close it, while products that ask users to bank on a future benefit stall. A sitting CEO calling this societal sets the terms for the next wave.

9. "Foothills of the singularity" has a precise definition

“I think for him, the advent of AGI is what he thinks of as the singularity. There is a harder definition of AGI, which is that it has to more comprehensively do the wide range of tasks, including cognitive tasks, in a way that’s comparable. So I think we’ll, at some point, actually put it out as a company.”

Demis Hassabis closed Google I/O with one of the year’s most-quoted lines, and Pichai grounds it in a specific bar: AI performing the full range of human cognitive tasks at a comparable level. All of them, rather than some.

Current systems sit below that bar, so “foothills” does precise work: closer than consensus expects, with road left. Google plans to publish a formal company definition of AGI, and that document rewards a close read when it lands.

Why it matters: when major labs publish operational AGI definitions, those definitions become product roadmaps, and the capabilities that close the gap attract the most capital. Track the definition and you track the priorities.

10. Skip the AGI label, build for the 36-month window

“I think that timeline doesn’t matter because the rate of progress means you’re dealing with ever more intelligent systems in a profound way. Three years from now, whether you and I call it AGI or not, doesn’t matter because it’ll be very, very powerful and we have to prepare for it.”

A precise answer dressed as an evasion. Pichai treats the label as a distraction from preparation that already needs to start. Three years out, the systems become powerful enough that societal readiness outweighs the name.

Why it matters: founders building today should model roadmaps against systems much more capable in 36 months. The strategic risk is a capability jump landing ahead of any declaration. Build for the present environment, and design the architecture that survives the next one. Both belong on the roadmap now.

What this means for you

The Decoder interview reads as a strategic document rather than a product update. The company that almost missed generative AI reorganized around one thesis: unified research, common infrastructure, faster decisions, and AI converging across every product surface. The structure is in place, and the execution runs on.

For founders. Structural readiness decides whether you can answer a competitive shock, because capability that lacks organization stays latent. Pichai’s order applies at any scale: unify research, centralize infrastructure, create single accountability, consolidate decisions. Get the capability layer unified before you build product on top, the same discipline the one-person operating system runs on.

For investors. Google’s moat is the pairing of distribution and infrastructure rivals struggle to copy quickly. The threat to it is a better distribution channel rather than a better model, so watch which AI companies build consumer reach off Google surfaces. The biggest startups and the VC money flows point to where that reach is forming.

For operators. Google Zero is a planning assumption now. Quality content still gets indexed, and traffic-dependent revenue needs diversification that holds even as referral volume falls. The Conde Nast plan is the template, and the GEO and AEO playbooks give you the build.

For anyone building in AI. The agent paradigm is durable because it pays off an expectation a decade in the making. Winners deliver the promise everyone already believed, since fulfilled expectations beat novel use cases in a market where the underlying model swaps out.

The three principles to carry forward:

1. Structural readiness decides your response to a shock. The bottleneck is almost always structure ahead of technology.

2. Most decisions are reversible. Speed on the routine ones buys the room to deliberate on the few that lock in.

3. The AGI label is a distraction, the trajectory is the signal. Model your business against systems much more powerful in 36 months and build accordingly.

The window to prepare is shorter than the debate about the timeline suggests. The companies that treat this as a platform shift rather than a product category set the terms. The ones waiting for clarity inherit the conditions the first group creates.

If this breakdown saved you 45 minutes, share it with one founder or investor who should see it.

Keep reading

Strategy, moats, and restructuring

▫️ Business and Investing library

▫️ Founder mental models for the AI era

▫️ Marc Andreessen on the AI moat

▫️ The one-person startup operating system

▫️ What top VCs look for in 2026

Agents and the build stack

▫️ AI Agents library

▫️ The Claude Code system that replaces your dev loop

▫️ Loop engineering for coding agents

▫️ How to build an AI agent in 2026

Search, GEO, and the traffic shift

▫️ How to rank when AI answers the query

▫️ RIP SEO: the GEO playbook

▫️ AEO and GEO backlink sources for founders

AGI, jobs, and the market

▫️ Claude and Anthropic library

▫️ Dario Amodei on safe AI and AGI

▫️ The Anthropic AI jobs report

▫️ The biggest VC-backed startups

▫️ Where VC money is going in AI

Full podcast:

If this breakdown saved you 45 minutes, share it with one founder or investor who needs to see it. They will thank you later.

The gap traces back to one thing most teams overlook. Every time a model answers, two separate operations run on the GPU, and each one fights a different battle. The first reads your entire prompt in a single burst, and its speed rides on raw compute. The second writes the answer one token at a time, and its speed rides on memory bandwidth.

That split sets your latency and your bill, and inference engineering is the craft of bending it in your favor. Three years ago the work stayed locked inside frontier labs. Today every team running serious AI workloads leans on it, because the payoff is concrete: a latency target you reliably hit, and an inference bill that falls by most of its size once your volume earns the work.

Here is the full system:

▫️ The prefill and decode split, explained so the entire field organizes itself in your head, with the two metrics that matter

▫️ All 6 optimization techniques, mapped to the exact phase each one speeds up, with the tradeoff each forces

▫️ The prompt-structure rule that turns prefix caching from zero savings into most of your prefill cost gone

▫️ The 2026 serving stack, vLLM versus SGLang, and which one fits your workload

▫️ The build-versus-buy crossover, the honest math on when self-hosting open models wins and when the API stays cheaper forever

▫️ The 3 signals that tell you the moment to leave off-the-shelf APIs, plus the compliance trigger that overrides the cost math

▫️ The quantization sensitivity map, which layers tolerate compression and which ones poison quality

▫️ The decision framework to pick the right techniques for your product, rather than all of them

Pair it with the deeper AI Corner library (included in the premium subscription):

▫️ The AI Tools and Models library for the model and serving stack

▫️ The AI Agents library for the workloads that stress inference hardest

▫️ The Prompting and Context Engineering library for the prompt structure that drives caching

▫️ The Claude and Anthropic library for caching mechanics and pricing

▫️ The Business and Investing library for where this margin compounds

Related builds worth reading next: the token cost playbook, the AI coding tools guide, the context engineering guide, and loop engineering.

⚙️ The Inference Engineering Playbook

The full system in one place: the prefill and decode split, all 6 techniques mapped to phase and tradeoff, the prompt-structure caching rule, the vLLM versus SGLang choice, the build-versus-buy crossover, and the decision framework.

Access The Inference Engineering Playbook below 👇

Try premium free for 7 days. Or get 50% off this week only.

Read more

Jensen Huang has called deep learning right for 15 years, and he went unfiltered for 1 hour. I watched all of it so you can skip to the moves.

Here are the 10 that matter, with the action under each👇

Together with Outskill:

Move 7 below is the sharpest line in the whole talk: the job now goes to the expert AI user, and the edge comes from built workflows rather than a title.

That edge is learnable in a weekend:

Outskill runs a live 2-day Claude AI Mastery Workshop that drives Claude past the chat box, into the Code and Cowork modes where the agent work actually happens. It condenses 800+ hours of research into 16 hours:

▫️Chat, Cowork, and Code end to end
▫️ Skills, Connectors, and Plugins, plus 10+ tools that keep Claude working while you sleep
▫️ Live Saturday and Sunday, 10AM to 7PM EST

Walk in able to answer the one question a resume hides:

Sign up for $0

Now, back to the roadmap, starting with the inflection point almost everyone missed:

1. The actual inflection point landed 6 months ago, and almost everyone missed it

Agentic AI crossed the line, which means every infrastructure thesis you hold deserves a rebuild rather than an update.

“AI in the last several months became useful. That’s the big idea.”

Agentic systems now understand, reason, plan, and use tools to finish actual work. Jensen names Claude Code as the first system to do this productively, and that benchmark just became the floor every other system gets measured against.

Here is the number that rewrites the infrastructure math: agentic AI demands roughly 1,000 times the compute of generative AI, since agents read, reason, call tools, and generate far more tokens moment to moment. Multiply that by 100 times more users arriving at once, and GPU demand compounds instead of scaling linearly. The chips NVIDIA sold four years ago carry more value today than the day they shipped.

Try this → audit every AI workflow in your operation. Generative workflows are the 2023 answer to a 2026 problem, so find them and rebuild them with the loop engineering and agentic patterns that fit the new floor.

2. The model layer gets the attention, and NVIDIA deploys capital two layers below it

Capital follows value, and right now the value sits two layers below the conversation.

“AI is not just an application. AI actually reinvented the computer industry.”

Jensen frames AI as a five-layer stack: energy, chips, infrastructure, models, applications. The media lives at the model layer, while NVIDIA’s capital lands at infrastructure, specifically CoreWeave, Nebius, and Nscale. One dollar NVIDIA committed unlocked nine more from the institutional market, and the application layer comes next.

Healthcare, transportation, financial services, and retail each sit at the starting line of genuine transformation. That transformation depends on compute infrastructure existing first, before any application runs on top of it.

Try this → find the layer in your space that few are fighting for yet. That is where the next fundable company lives, and the YC requests for startups list is a useful map of the open ground.

3. NVIDIA's capital rule: $1 in must activate $100 out

Jensen writes checks to remove the constraint blocking the next $100, rather than chasing a return on the check itself.

“We invest at $1, it activates AI maybe by $100. If we can make that kind of amplification for the entire ecosystem, it would be tremendous.”

Two years ago the bottleneck was chips. Today it is energy, land, and power. The CoreWeave investment worked as a precisely placed lever: anchor capital that unlocked institutional confidence and nine dollars for every one NVIDIA put in. Every investor who co-invested alongside NVIDIA in CoreWeave, Nebius, and Nscale is seeing strong returns now. Early bottleneck identification is the entire thesis.

Try this → map the constraint in your market. The company removing that constraint is worth more than every company it enables combined, so the founder mental model to internalize is simple: get to the constraint first. The investor list of lists shows who is already funding the layer below.

4. AI-native gross margins flipped positive in 90 days, and the market still owes a reprice

The unit economics stopped being a bet. They are a fact, and the capital chase just changed sha

“Both of these companies and most of the AI native companies have turned. Their gross margins have gone extremely positive.”

OpenAI. Anthropic. Cursor. Gross margins crossed into strongly positive territory in the last three to six months. Token economics work. Demand is there. That is why OpenAI and Anthropic race for capacity right now, not profitability reassurance.

$100 billion went into AI startups last year. The largest single-year startup investment in human history. Software engineering job openings are rising, not falling.

Try this: watch capacity announcements from OpenAI and Anthropic. Capacity commitments are the leading signal for where AI product investment accelerates next.

5. The radiology jobs prediction was wrong, and the reason applies to your industry too

Computer scientists predicted the task correctly and predicted the job incorrectly.

“100% of radiology is now infiltrated by AI. It is completely integrated. And yet, the radiologist job was not wiped out.”

Computer vision reads scans at superhuman accuracy now, and radiologists review more patients, take more cases, and generate more revenue. Radiology departments turned into profit centers, and hospitals started hiring more radiologists. AI compresses the task, purpose expands to absorb the freed capacity, and hiring follows the expanded purpose.

Every knowledge-work vertical AI enters rides the same curve: task compression, then purpose expansion, then more hiring at the level of the expanded purpose. Your industry rides it too, as the AI jobs data keeps showing.

Try this → list the three tasks in your role AI automates today, then list what you actually get paid to accomplish. The gap between those lists is where you build the next two years, a theme the the AI jobs reckoning breakdown runs all the way down.

6. Jensen's task list is fully automated, and he works harder than ever

The CEO of NVIDIA is the sharpest living proof of his own argument.

“The purpose of a job and the task of the job are related, not the same.”

Jensen’s tasks are typing and talking, both superhuman by AI, and he works harder than ever because the purpose scaled up to absorb the freed capacity. A software engineer’s task is writing code, and the purpose is solving problems and building things that existed only as ideas. AI handles more of the task, the purpose expands, and the same logic reaches every role.

The skill gap between AI-native and non-AI-native graduates already shows up in this hiring cycle. The dislocation lives in the current offers, ahead of the next round.

Try this → write your purpose list and your task list as two separate documents. Every automated task is time returned, and every item on the purpose list is where that time goes. The AI engineer roadmap shows what that expanded purpose looks like in practice.

7. Graduating in 2026 with AI fluency wins the job, this hiring cycle

The most specific and consequential warning in the full 46 minutes.

“If you graduate and you’re not an expert AI user, you’re not going to take a job from another kid who is. That’s a dislocation.”

A skill that was optional yesterday became a requirement today, and Jensen named it flat out. The companies competing hardest for talent want people who use AI fluently, who built workflows around it, who direct AI systems toward outcomes. The AI-native candidate runs more productive at every level, from daily compounding rather than a job title, and it shows in the offers right now.

Try this → change your hiring filter. Ask every candidate to walk you through an AI-assisted workflow they built in the last 30 days. The answer reveals everything a resume hides, and the top-1% Claude setup plus Claude best practices define what fluent actually looks like.

8. Jensen's biggest fear is American disengagement, ahead of China getting AI

The competitive risk is cultural rather than external.

“My greatest concern is that we scare United States people to the point where AI is so unpopular they don’t actually engage it. That we lose our lead as a nation.”

Jensen wants everyone to hold access to AI, China included, and something else worries him. Science-fiction narratives, repeated loudly enough, breed a culture of fear, fear breeds disengagement, and disengagement is how you lose a technology race. America led the last industrial revolution by applying the technology faster than anyone, more than by inventing it.

Try this → audit how you talk about AI publicly and internally. A culture of application and a culture of avoidance grow from the same soil, and you choose which one you water. The MIT research on engagement design sharpens how that choice plays out.

9. Jensen's answer to a billion-dollar AI weapon inverts the arms race

The arms-race instinct loses before it starts, and Jensen’s framework flips it entirely.

“The way you defend against a super force is not with another super force. It’s with an abundance of cheap force.”

The threat is specific: a powerful coding AI in a bad actor’s hands scans thousands of endpoints at once and finds every vulnerability in your codebase faster than a human team could surface them. A single more-powerful defensive AI loses that race, because a motivated attacker out-scales any one defender at the top of the stack. The answer is distribution.

Picture open-source models, each small and cheap, each trained on one threat surface: authentication endpoints, API exposure, dependency chains, credential handling. Individually limited, collectively exhaustive. You can guarantee more coverage than they hold attack surface, even while their model might match yours, which is the whole defensive posture for the AI era.

Try this → map your threat surface by category rather than by severity. For each category, find whether an open-source model trained on that surface exists, and start deploying a swarm of small agents where the gap is widest.

10. Research that took months now takes a day, so add a zero to your ambition

The closing argument, and the one most people will hear and still underweight.

“Whatever level of ambition you have, it’s just not high enough. Whatever expectations I have for the company, you’ve got to increase it by about 100x.”

Jensen described his morning before taking the stage: a professor, then a scientist, research that used to take months collapsing to a day. Drug discovery, climate science, energy science, the physical sciences, all of it compressing across every field. He watched it happen this week, in person, ahead of any projection deck. The constraint on progress moved past compute, past models, past talent. The constraint is now ambition.

Try this → take your three-year roadmap and run one scenario: research timelines 30 times shorter, engineers 10 times more productive. Whatever ships in that version is your actual starting point, so rebuild from there.

The AI playbook: five principles to start using today

Every playbook built before agentic AI earns a rebuild. Here is what that rebuild looks like in practice.

For founders. Your moat is domain expertise applied through AI at a speed rivals struggle to match. The first agent you deploy should solve the recurring problem in your operation that goes unowned. Ship that, then find the next one, using the one-person operating system and the five-agent build as templates.

For investors. The $1-activates-$100 rule is the most useful filter in the market right now. Find the constraint in your sector, find the company removing it, and remember infrastructure is producing returns today while applications come next. The window before both turn into consensus is the one you sit in, and the VC playbook plus the investor list of lists help you move inside it.

For builders. AI fluency compounds, and the gap between the AI-native engineer and everyone else widens every month. Build the workflows now, because the hiring cycle moves now.

Five principles that hold regardless of what ships next:

▫️ Agentic AI crossed the line. The 1,000x compute math is permanent.

▫️ Capital belongs at the constraint, beyond the conversation. Find the layer few are funding.

▫️ AI compresses tasks, purpose expands, and hiring follows the expanded purpose.

▫️ The competitive risk is disengagement. Apply the technology.

▫️ Ambition is the binding constraint now. Add a zero and rebuild from that number.

Jensen spent 46 minutes telling you the ceiling moved. Most people will nod and keep their current plans. You now hold the moves to do something else with that information.

If this breakdown saved you 46 minutes, share it with one founder or investor who should see it.

Keep reading

Agentic AI and the build stack

▫️ AI Agents library

▫️ The Claude Code system that replaces your dev loop

▫️ Loop engineering for coding agents

▫️ Codex background workflows playbook

▫️ Build a five-agent sales team in a weekend

▫️ How to build an AI agent in 2026

AI fluency, tools, and models

▫️ AI Tools and Models library

▫️ How to use Claude like the top 1% of users

▫️ Claude best practices power-user guide

▫️ AI coding tools complete guide

▫️ The 2026 AI engineer roadmap

▫️ SaaS defense playbook for the AI era

Founders, capital, and the market

▫️ Business and Investing library

▫️ The one-person startup operating system

▫️ Marc Andreessen on the AI moat

▫️ Anthropic passed OpenAI at $30B ARR

▫️ The investor list of lists

▫️ What top VCs look for in 2026

▫️ Where VC money is going in AI

▫️ The Coatue AI report in 18 charts

Full interview:

If this breakdown saved you 46 minutes, share it with one founder or investor who needs to see it. They will thank you later.

That question is also your invoice. You pay per token, roughly three-quarters of a word each, on the way in and the way out. Most production apps resend the same system prompt, the same tool list, and the same documents on every call, paying full freight thousands of times a day. Prompt caching alone trims repeated input by up to 90% on Claude. Stack the rest of the system and a typical bill drops by half or more, with the output quality held steady.

This is the full system:

▫️ The 4-layer token model that maps every dollar you spend to a lever you control, from the prompt to the agent loop

▫️ Before-and-after prompt rewrites that cut input tokens 30 to 60% while holding output quality, ready to copy

▫️ The prompt-caching setup that delivers Claude’s 90% discount in practice, with the prefix-ordering rule, the cache_control breakpoints, and the hit-rate target

▫️ The retrieval pattern that replaces stuffing whole documents with searching for the chunks that matter

▫️ The agent and tool diet, including the serialization trick that halves the cost of structured data

▫️ The worked ROI math on a realistic agent workload, so you can size your own savings before you touch a line of code

▫️ The 8 failure modes that silently erase your savings, each with the fix

▫️ The 30-day rollout from measuring your spend to a fully optimized stack

Pair it with the deeper AI Corner library (all included in the premium subscription):

▫️ The Prompting and Context Engineering library for the patterns underneath every rewrite

▫️ The AI Tools and Models library for model rates and routing

▫️ The AI Agents library for the agent-loop economics

▫️ The Claude and Anthropic library for caching mechanics and model choice

▫️ The Business and Investing library for where this margin compounds

Related builds worth reading next: the context engineering guide, the 2026 prompt engineering guide, Claude best practices, loop engineering, and the Codex background workflows playbook.

💸 The Token Cost Playbook

The full system in one place: the 4-layer model, the prompt rewrites, the caching setup, the retrieval pattern, the agent and tool diet, the ROI math, the 8 failure-mode fixes, and the 30-day rollout.

Get The Token Cost Playbook below 👇

Get 50% off forever

Read more

This marks the first time a leading AI lab has pulled a publicly deployed frontier model because the federal government told it to. Every other Anthropic model, including Claude Opus 4.8, stayed live. Both sides now fight in public, and the details cut in directions that embarrass almost everyone involved.

Here is what happened, what each side claims, and why the precedent matters far more than the incident.

The timeline, straight

1. June 9. Anthropic launches Fable 5, the first public release from its top-tier Mythos family, with safeguards built to make Mythos-level capability safe for broad use, alongside Mythos 5 for select enterprise partners. Both build on Claude Mythos Preview, the model held back in April under a cybersecurity program called Project Glasswing.

2. June 10. CEO Dario Amodei publishes a policy essay arguing that governments should hold legal authority to block or reverse the release of frontier models that fail independent safety testing, comparing it to the FAA grounding unsafe aircraft.

3. Around June 11. Amazon, one of Anthropic’s largest investors, calls administration officials to share a report claiming its researchers jailbroke Fable and reached portions of Mythos that pose a national security risk, according to Axios. The Information reported that Amazon CEO Andy Jassy was among the tech leaders raising concerns to senior officials that week.

1. June 12, 5:21pm ET. Lutnick’s letter imposes export controls on Mythos 5 and Fable 5 for any location outside the US and any foreign national inside it, including Anthropic’s own non-citizen staff.

2. June 12, ~10pm ET. Faced with a directive that reached its foreign-born employees, Anthropic switches off both models for all users and posts its statement.

The business and investing stakes here run high, and the Claude and Anthropic library tracks the company’s policy posture across the year for context, including its path to a $1 trillion valuation and the moment it passed OpenAI on revenue.

What the government and its allies say

White House AI czar David Sacks laid out the administration’s version in a public post. His framing, paraphrased: Fable is Mythos with guardrails, so a guardrail failure exposes advanced cyber capability to people who should stay far away from it. A trusted partner testing Fable surfaced a jailbreak, the administration asked Amodei to fix it or pull the model, and in Sacks’s telling Amodei declined, so the export control followed reluctantly. Sacks argues the ball now sits in Anthropic’s court and that remediation would lift the controls quickly.

An administration official told Axios the Commerce Department acted after another company claimed it could jailbreak Mythos, and that the government had earlier tried and failed to get Anthropic to pause the release. Sacks also leaned on a pointed irony: Anthropic itself promoted Mythos as something close to a cyberweapon that warranted regulation, so a vulnerability in its consumer wrapper becomes, by Anthropic’s own standard, the company’s job to patch.

What Anthropic says

Anthropic’s statement tells a different story. The company says the letter withheld the specific national security concern, and that its understanding is the government learned of a jailbreak method. Anthropic reviewed a demonstration and characterized it as narrow and non-universal, essentially asking the model to read a specific codebase and fix software flaws, a capability it says ships in other public models including OpenAI’s GPT-5.5 and runs every day in the hands of the defenders who keep systems safe.

The company’s core arguments:

▫️ Testers so far have surfaced only narrow, non-universal bypasses, while the universal kind that broadly unlocks dangerous cyber capability stays unseen

▫️ It runs a defense-in-depth strategy, including 30-day data retention to detect and shut down attacks fast, a policy it says carries genuine commercial cost

▫️ Recalling a model over a narrow finding sets a precedent that, applied industry-wide, would freeze frontier deployments across every lab

▫️ It is complying while disputing the basis, calling the action a misunderstanding and working to restore access

Anthropic officials told Axios they walked the administration through how the alleged Amazon jailbreak was simple, reproducible on other models, and consistent with healthy safety systems. Both accounts agree a narrow technique was demonstrated. They split completely on what it means.

The irony everyone noticed

The framing that spread fastest, including a TechCrunch headline arguing Anthropic’s safety warnings may have backfired, writes itself. Anthropic spent years as the safety-first lab calling for government oversight of powerful models. Amodei published an essay days earlier requesting exactly the authority the government then used on his own flagship. Critics also seized on the 30-day retention policy, casting the safety-first company as one that now logs every prompt and output to a Mythos-class model.

Anthropic’s defenders read it the opposite way: the company asked for a transparent, fair, fact-grounded statutory process, and argues this directive, delivered by letter with the evidence sealed and the harmful result still undisclosed, departs from every one of those principles. Both readings stay live, and which one lands depends largely on how serious you judge the jailbreak to be, which is the part the public still waits to see.

The precedent every builder should track

Strip away the personalities and one question remains: should a government be able to switch off a commercially deployed model on a few hours’ notice, by letter, while the evidence stays sealed? This episode is the first working example of model-layer regulation in practice, and it rewards seeing clearly from both sides.

The case for it runs straight. A frontier model with advanced cyber capability is a national security asset, the government holds a legitimate interest in who can reach it, and a lab that markets its model as dangerous invites the state to treat it as dangerous. When independent testers surface a bypass, pausing the model while it gets patched reads as a reasonable precaution.

The case against it is the one Box CEO Aaron Levie made publicly, and it is the deeper structural worry. Regulating at the model layer hands the government sole discretion over when a model reaches the public, based on risk judgments that stay inherently subjective. Every release becomes a months-long negotiation over what a model can do and how dangerous that is, which produces a backlog, slows the market, and starts to make AI look like any other heavily gated industry. Levie’s sharpest line: had this paradigm existed three years ago, we might still sit near GPT-4. His proposed alternative is to regulate the applied use of AI in cyberattacks, fraud, and biosecurity, leaving the model itself free to ship.

The disagreement reaches past Fable. It is about whether the kill switch belongs at the model or at the use. This week was the first live test, and everyone walked away still arguing.

The AI tools and models library and the Claude and Anthropic library both track how this regulatory question keeps reshaping the release calendar.

The Amazon question

The strangest thread is the trigger. Amazon ranks among Anthropic’s largest investors and a major customer, having poured billions into the company and sold Claude across its cloud. Yet by the reporting, Amazon’s own researchers produced the report that set the takedown in motion, and Andy Jassy carried concerns to the administration.

Why would a major investor strike a blow this disruptive against a company it owns a large stake in? Three readings circulate, each still unconfirmed:

▫️ Genuine safety concern, where Amazon researchers found something alarming and escalated it through the channels available

▫️ Competitive positioning, where a backer with its own model ambitions gains from a rival flagship sitting grounded

▫️ Hedging a complicated relationship, where Amazon balances its Anthropic stake against its government and enterprise commitments

The honest answer is that outsiders still lack the evidence to tell which it is, and the venture dynamics around the big labs make all three plausible at once. The investor list of lists and the biggest VC-backed startups show how tangled the cap tables behind frontier AI have become.

The dual-use paradox at the center of it

Here is the technical knot that makes this hard to resolve cleanly. The capability in dispute, a model reading a codebase and finding or fixing software flaws, is exactly what you want on the defensive side of cybersecurity. The same skill that helps an attacker find a vulnerability helps a defender close it, and defenders run this work daily. By Anthropic’s account, and by Levie’s, the capability already ships broadly across current models.

That is why “is this a cyberweapon” resists a clean verdict either way. A frontier model is dual-use by design, and a rule that grounds any model capable of finding a software flaw would ground most of them. The disagreement between Anthropic and the administration is partly about severity and partly about this deeper question of whether dual-use capability can be governed at the model level while the field keeps moving. The SaaS defense playbook covers how defenders actually put these capabilities to work in production.

The three paths back to release

Anthropic says it is working to restore access. Realistically, Fable returns through one of three doors:

1. Government reversal. Anthropic demonstrates the jailbreak is narrow and reproducible elsewhere, the administration accepts the technical case, and the controls lift. Sacks has signaled this is the outcome the administration wants, which makes it the fastest path once the technical facts land.

2. Negotiated remediation. Anthropic ships a patch and extra safeguards, both sides claim a win, and the model returns with tighter controls. This reads as the likeliest middle path given the prior friction between the two.

3. Court order. Anthropic, already in litigation with the administration over a separate supply chain risk designation, escalates legally. Slower, and it hardens the conflict rather than settling it.

The backdrop matters here. In February, the administration directed federal agencies to stop using Anthropic’s technology after the company objected to certain defense uses, the DOD later labeled Anthropic a supply chain risk, and Anthropic sued. Sacks insists this week’s action runs separate from that history. Others read one continuous conflict. The truth likely sits in between, and the Dario Amodei safety thesis is now colliding with the politics it helped invite, an arc the Davos zeroth-world essay foreshadowed.

What this means for you

Set aside who is right. Three durable lessons hold whichever way the fight ends.

For builders. Treat single-model dependence as a live risk you design around. A model you built a product on can vanish overnight for reasons that trace to forces beyond your control. Design for multi-model resilience: an abstraction layer, a tested fallback to another provider, and an honest answer to “what happens to my product the night this specific model goes dark.” The AI coding tools guide and the power-user setup both cover building across providers.

For investors. Regulatory action now prices in at the frontier as a base case rather than a tail. A model’s release calendar, and therefore a lab’s revenue, can hinge on a letter. That reshapes how you underwrite the frontier labs and lifts the value of companies positioned one layer up from the raw model. The Coatue AI report and the venture map at VC Corner help size where that risk sits, and Mark Cuban’s track record on calling these moments early is worth a read.

For operators. The public, direct-to-audience nature of this fight is the new normal. As Anthony Pompliano observed, both sides skipped the press and posted their own versions, leaving citizens to judge. Read the primary statements, weight the partisan accounts accordingly, and assume every party argues its own book.

While Washington argues, build the leverage

The policy fight will run for weeks. The leverage sits in wielding Claude deeply enough that any single model’s fate matters less to your output. Here is where to go deeper, all in one place:

▫️ Loop engineering for designing the system that prompts your agent for you, in the loop engineering playbook

▫️ The one-person company that runs like a 30-person team, in the one-person startup operating system

▫️ Background automations that run while you sleep, in the Codex background workflows playbook

▫️ The six patterns Anthropic engineers use in the Claude Code dynamic workflows guide

▫️ The Claude Code system that replaces your dev loop, in the full system breakdown

▫️ A five-agent sales team you assemble in a weekend, in the build guide

▫️ A second brain on Claude with Obsidian and the Granola MCP stack

▫️ Your own stock analyst in 12 prompts, in the Claude stock analyst build

▫️ The power-user playbook in Claude best practices and managed agents

▫️ The complete skills library in the Claude Skills startup marketing library and the Claude Skills complete guide

What to watch next

▫️ Anthropic’s promised technical detail, and whether it convincingly shows the jailbreak reproduces widely

▫️ The administration’s evidence, since the sealed specifics sit at the heart of Anthropic’s complaint

▫️ Amazon’s explanation, if any arrives, for triggering an action against a company it heavily backs

▫️ The restoration timeline, and which of the three paths it travels

▫️ Whether other governments copy the move, since a US precedent for model-layer control invites imitation abroad

TL;DR

The US government ordered Anthropic to suspend Fable 5 and Mythos 5 three days after launch, over a jailbreak the administration calls a national security risk and Anthropic calls narrow and widely reproducible. Amazon, a major Anthropic investor, appears to have triggered it. The deeper fight is about model-layer regulation, where the government gates releases directly, and whether that freezes the field or protects it. For builders, the lesson is multi-model resilience plus deep Claude leverage. For investors, regulatory risk now prices in at the frontier. The evidence the public can verify stays thin, so weight every account, including this one, by who gains from it.

Keep reading

Anthropic, Claude, and the policy fight

▫️ Claude and Anthropic library

▫️ Anthropic’s $1 trillion valuation breakdown

▫️ Anthropic passed OpenAI at $30B ARR

▫️ Dario Amodei’s zeroth-world thesis from Davos

▫️ Dario Amodei on safe AI and AGI

▫️ The Claude Code source code leak

Build with Claude while the policy plays out

▫️ Loop engineering for coding agents

▫️ The one-person startup operating system

▫️ Codex background workflows: 10 automations

▫️ Claude Code dynamic workflows: 6 patterns

▫️ The Claude Code system that replaces your dev loop

▫️ Build a five-agent sales team in a weekend

▫️ Obsidian and Claude second brain playbook

▫️ Granola and Claude second brain MCP stack

▫️ Build your own stock analyst with Claude

▫️ Claude best practices power-user guide

▫️ Claude managed agents guide

▫️ Claude Skills startup marketing library

▫️ Claude Skills complete guide

▫️ How to use Claude like the top 1% of users

The capability, security, and market side

▫️ AI Tools and Models library

▫️ SaaS defense playbook for the AI era

▫️ AI coding tools complete guide

▫️ MIT on how ChatGPT is designed to hook you

▫️ Mark Cuban has been right every time

▫️ Business and Investing library

▫️ The investor list of lists

▫️ Where VC money is going in AI

▫️ The Coatue AI report in 18 charts

Peter Steinberger, founder of OpenClaw, put it to 8 million viewers in a day: stop prompting coding agents, start designing the loops that prompt them.

For two years the move was simple. You wrote a good prompt, fed enough context, read what came back, typed the next thing. The agent was a tool and you held it the whole time, one turn after another. That posture is ending. The new one is a small system that finds the work, hands it out, checks it, records what is done, and decides the next thing, while you watch instead of type.

Here is what changed in 2026, and why this stopped being a weekend bash-script project. The pieces ship inside the products now.

Claude Code added /goal in v2.1.139 on May 11, 2026, a native loop that runs across turns until a condition you wrote is true, with a separate fast model grading the work after every turn.

Codex shipped the same primitive in CLI 0.128.0 on April 30, plus an Automations tab and a triage inbox. Once you see that both tools expose the same five blocks, you stop arguing about which one and start designing a loop that works in either.

This is the full build:

▫️ The five building blocks of a loop mapped command-for-command across Claude Code and Codex, so your loop runs in whichever tool you are sitting in

▫️ Copy-paste /goal conditions that actually stop, plus the four constraints that silently break most of them (the evaluator reads the transcript, not your files)

▫️ A working SKILL.md skeleton and a sub-agent config for the maker-checker split that lets you trust a loop running unattended

▫️ The full reference loop, the morning-triage-to-merged-PR blueprint you design once and never prompt again

▫️ The token economics, where a loop burns money, and how to cap spend whether you are token rich or token poor

▫️ The 8 failure modes that turn an unattended loop into unattended mistakes, each with the fix

▫️ The memory spine, the on-disk state file that survives between runs because the model forgets and the repo does not

▫️ The 30-day rollout from your first /goal to a self-feeding loop with a verifier you trust

Pair it with the deeper AI Corner library:

▫️ The AI Agents library for orchestration and reliability

▫️ The Prompting and Context Engineering library for skills and intent

▫️ The Claude and Anthropic library for Claude Code and Codex internals

▫️ The AI Tools and Models library for the build stack

▫️ The Business and Investing library for where this leverage compounds

Related builds worth reading next: the Claude Code system that replaces your dev loop, the AI agent reliability playbook, the multi-agent code review build, the Claude Skills complete guide, and the context engineering guide.

🔁 The Loop Engineering Build Kit

The full system in one place: the five blocks mapped across both tools, copy-paste /goal conditions, SKILL.md and sub-agent configs, the reference loop, the token math, the 8 failure-mode fixes, and the 30-day rollout.

Get The Loop Engineering Build Kit below 👇

Get 50% off forever

Read more

The reason is a quiet role change. The founder stops being the individual contributor who writes the code and runs the ops, and becomes the orchestrator of agents that carry the work out. Your edge moves from execution to judgment. Anthropic made the same argument in its 36-page Founder’s Playbook, and the math is blunt: validation cycles that took months now take an afternoon, and a single founder can run like a team many times their headcount.

Here is the part most people miss. When building gets this cheap, the often-cited CB Insights number, 42% of startups dying because they built something nobody wanted, does not shrink. It climbs. The bottleneck moved from “can you build it” to “should you,” and that favors people with domain judgment, not just engineers.

This is the full operating system for running that company as one person. Here is what sits behind the paywall:

▫️ The 3-surface decision framework that tells you exactly when to reach for Chat, Cowork, or Code so you stop using a chat box for work that needs an agent

▫️ The 4-stage AI-native build (Idea, MVP, Launch, Scale) with the goal, the exit criteria, and the AI-era trap for each stage

▫️ 30+ copy-paste prompts that turn Claude into your validator, your architect, your security reviewer, your GTM strategist, and your board prep, each one ready to run today

▫️ The 12-function Founder OS, a complete prompt library across validation, business model, fundraising, GTM, product, sales, marketing, growth, ops, finance, customer success, and legal

▫️ The CLAUDE.md context system that keeps an agent building coherent software across months instead of re-deriving your architecture every session

▫️ The 8 AI-era failure modes that kill solo startups, each with the exact prompt-level fix

▫️ The solo tool stack for build, design, video, analytics, and support, so one person covers six departments

▫️ The 30-day rollout from raw idea to a company that runs without you in every loop

Pair it with the deeper AI Corner library:

▫️ The AI Agents library for orchestration and reliability

▫️ The Prompting and Context Engineering library for the prompt patterns underneath every exercise

▫️ The Claude and Anthropic library for the surfaces and skills

▫️ The AI Tools and Models library for the build stack

▫️ The Business and Investing library for fundraising and GTM

Related builds worth reading next: the Claude Skills complete guide, the Claude Code system that replaces your dev loop, the Claude Cowork breakdown, the AI GTM playbook, and the VC Corner investor list of lists.

🛠️ The One-Person Startup OS

The full system in one place: the 4-stage build, the 12-function prompt library, the CLAUDE.md context setup, the 8 failure-mode fixes, the solo tool stack, and the 30-day rollout.

Get The One-Person Startup OS below 👇

Get 50% off forever

Read more

Benedict Evans has called technology shifts right more consistently than almost anyone alive. If this is the first time you are hearing his name, you are about to read something full of gems.

He spent 25 years as one of the sharpest analysts in tech, across equity research, strategy consulting, and a long run as a partner at Andreessen Horowitz. Twice a year he publishes a macro deck on where technology is heading. His 2013 “Mobile Is Eating the World” became required reading for the smartphone wave while it was still forming, and he called mobile before most people knew what mobile meant.

His weekly newsletter reaches around 200,000 readers, and he has presented for Alphabet, Amazon, LVMH, and Goldman Sachs. When Evans publishes, serious people in tech read it carefully and argue about it for months. “AI Eats the World” is his most consequential deck yet, because it does not tell you AI is revolutionary. It forces you to ask which part of the revolution you are in, and whether the part you are betting on is the part that wins.

together with Hard Skill Exchange:

Evans makes you pick which part of the AI shift you are betting on. Here is one that is already arriving: your next customer may not be human.

Hard Skill Exchange is running a FREE virtual AI summit on exactly that. Agent-to-Agent GTM, where the people building machine-native go-to-market show what breaks when software becomes the buyer, the seller, and the decision maker.

▫️ 3 days, fully virtual, free for everyone, with no ticket and no travel

▫️ Agent-native GTM playbooks for a market where buyers skip ads, brands, and funnels

▫️ The operators defining the category before the consensus catches up

It runs live June 23 to 25, and then it is gone. Your next customer may not be human, so it would be a mistake to sit this one out:

Save your Free seat !

Table of Contents

1. Platform Transitions Eat Their Parents

2. The Financial Model Is Quietly Breaking

3. 900 Million Users. Almost Nobody’s Hooked.

4. Models Are a Commodity. Deal With It.

5. The Right Question About Jobs

6. The Uncomfortable Math

1. Platform Transitions Eat Their Parents

Every 10 to 15 years, the tech industry doesn’t just add a new layer. It rewrites the rules of the previous one, and the prior winners often don’t survive the rewrite.

Evans opens the deck here, and it deserves more than a quick nod.

The historical progression runs from Mainframes to PCs to the Web to Smartphones to Generative AI. Each transition didn’t just produce new companies. It made the dominant players of the prior era structurally irrelevant in ways they couldn’t have anticipated or defended against.

Microsoft went from owning essentially all of global computing in 2000 to less than 15% of computing units by 2025. Not because Windows got worse. Because the iPhone redefined what “a computer” was, and Microsoft had no answer for it.

This is what makes the current spending war legible. The CEOs committing hundreds of billions are not doing it because the returns are obvious. They are doing it because they have studied that chart and have no interest in becoming the next example on it.

Sundar Pichai said the risk of under-investing is significantly greater than the risk of over-investing. Zuckerberg said the worst case is that they “just prebuilt for a couple of years.” Those are not confident statements. They are the sound of people who know what happens to the unprepared.

The question nobody is asking loudly enough

What Evans doesn’t say explicitly, but the framing implies: the companies most at risk here are not the ones who refuse to invest. They are the ones who invest in the wrong layer.

Platform transitions have a habit of making yesterday’s moat look like a liability, and there are a lot of very expensive bets being placed right now on layers that may not be where the value ends up.

The companies that dominated the PC era built for PCs. The companies that dominated mobile built for mobile.

Winning the current infrastructure race does not guarantee winning what comes after it. That distinction is what the rest of the deck is really interrogating.

2. The Financial Model Is Actually Breaking

The four biggest tech companies, Meta, Microsoft, Alphabet, and Amazon, are planning a combined $700 billion in capital expenditure in 2026 alone.

The entire global telecom industry spends around $300 billion annually. Big Tech has entered that tier of physical investment almost overnight, and the balance sheets are starting to show it.

For most of their existence, these were asset-light businesses. Software scales without proportional physical investment. High margins, minimal infrastructure, free cash flow that funded buybacks, acquisitions, and everything else. That was the entire premise of their valuations, and it is now under serious pressure.

Meta and Microsoft are both approaching 55% of revenue going to capex in 2026. In 2015, Meta was spending around 10%. These numbers do not look like software companies anymore. They look like the capital structures of the industries they used to disrupt.

When a company’s cost structure changes this radically this fast, something has to give. Either the revenues scale to justify it, the margins compress, or the valuation assumptions get repriced. Right now, markets are betting hard on option one.

The deeper issue is that this investment is not discretionary anymore. You can’t half-build the infrastructure. You can’t decide in two years that you over-invested and sell the data centres back.

This is a one-way door, and the world’s most valuable companies walked through it while telling their shareholders it was the obvious move. Maybe it was. But the size of the bet means there is no graceful exit if the thesis is wrong.

A quick one, courtesy of Hard Skill Exchange:

While Big Tech bets $700B on the infrastructure, the go-to-market layer on top of it is already changing

The free Agent-to-Agent GTM Summit covers what happens when software becomes the buyer. 3 days, fully virtual, free for everyone, live June 23 to 25.

Grab your FREE seat

3. 900 Million Users. Almost Nobody’s Hooked.

ChatGPT has over 900 million weekly active users, but only 5% of them are paying. Evans shows the growth curve and it looks extraordinary, right up until the next slide reframes everything.

OpenAI’s own “Wrapped” data tells a different story. For at least 80% of users, total usage across all of 2025 was under 1,000 prompts. That is fewer than 3 per day. For the vast majority of people who “use” ChatGPT, it is something they open occasionally, the way you open a dictionary.

Evans calls this “a mile wide and an inch deep.”

At the end of the day, this is not product-market fit. Product-market fit is when people use something daily without being reminded it exists, when they complain loudly if it goes down, when they genuinely cannot describe their workflow without it.

The comparison to smartphones cuts in the wrong direction. Within three years of the iPhone, people were sleeping next to their phones. Within three years of ChatGPT, 80% of users are sending fewer prompts per day than they send text messages per hour.

The VC Corner

Model-Market Fit: The New Make-or-Break for AI Startups

The Framework Every AI Founder Is Missing…

Read more

2 months ago · 74 likes · Ruben Dominguez

The enterprise story mirrors the consumer one.

Bain’s data shows that across every major business function, the gap between “in pilot” and “in production” is enormous.

Everyone has a proof of concept. Almost nobody has something running at scale that has actually changed how the business operates.

Pilots are easy to start and hard to kill. They generate internal goodwill, satisfy board questions about AI strategy, and require minimal organisational change.

Getting from pilot to production means redesigning workflows, retraining people, and accepting that the model will sometimes be wrong. Most companies haven’t started that part.

The one real exception is coding. Enterprise AI spending on software development is roughly five times the next biggest category.

Among developers, AI has clearly become a daily essential. But coding is one profession, and the distance between “coding is transformed” and “work is transformed” is still vast.

4. Models Are a Commodity. Deal With It.

This is the part of the deck the industry is not engaging with honestly, and it has direct consequences for how you think about the biggest valuations in private market history.

Look at the benchmark chart for frontier LLMs. OpenAI, Anthropic, Google, Meta, the Chinese labs: scores are converging at the top. For most general use cases, the models are now functionally interchangeable.

And there are no network effects. A model doesn’t get better because more people use it. It doesn’t accumulate data about you that makes switching painful.

Evans draws the comparison to mobile telecom infrastructure, and it is the most pointed analogy in the deck.

Global mobile data traffic exploded over 15 years. Global telco stocks went essentially nowhere over the same period. The companies that built the pipes carried all the value but captured almost none of it.

Infrastructure businesses at scale, serving commodity demand, get priced like utilities. Necessary, steady, and low margin. Sam Altman’s “intelligence as a utility like electricity or water” is more accurate than he probably intends. Utilities are worth owning. They are not worth $850 billion.

Electricity producers don’t capture the value created by the industries running on their power. That value goes to whoever builds the product people actually use every day.

The interesting question is not who trains the best model. It is who builds the thing on top of it that becomes genuinely indispensable.

5. The Right Question About Jobs

Most of the public conversation about AI and employment is asking the wrong question. People want to know which jobs disappear. So the ultimate question according to Evans is:

Is this a job, or is it a task?

A task is a defined operation with a known input and output. A job contains judgment, relationships, and decisions made under genuine ambiguity. That’s a huge distinction when we talk about AI.

In 1950, there were nearly 100,000 elevator operators in the United States. Otis automated the elevator, and the profession was gone within a decade, because the job was just a task.

There was nothing else there. But accountants grew as a share of US employment for decades after software automated their core computational work, because what accountants actually do expanded as the cost of calculation fell.

Before grocery barcodes in 1974, the average US supermarket stocked around 8,000 products. By 2010, that number was 50,000. Automated inventory management didn’t just make stocking cheaper. It made a level of variety that was previously impossible suddenly achievable. The free task unlocked something that couldn’t exist before.

The live test nobody wants to talk about

Evans points to the Philippine outsourcing industry as the most immediate real-world test of this framework.

Two million people, 8% of GDP, built entirely on a skill and income arbitrage that AI is now directly threatening.

Whether those roles survive depends entirely on whether they are tasks or jobs. Some are pure tasks with defined inputs, defined outputs, no judgment required. Those are (or will be) gone.

Others involve enough human context, relationship management, and situational reading that they are genuinely jobs. Those will change, probably dramatically, but they won’t simply disappear.

Anyone telling you they know exactly which category any given role falls into is guessing. The honest answer is that nobody knows yet, and the outcome will vary enormously by industry, company, and how aggressively employers choose to act.

6. The Uncomfortable Math

One slide in Evans’ deck is more unsettling than any of the capex charts.

OpenAI and Anthropic are each valued in private markets at roughly $850 to $900 billion. The total market capitalisation of every US venture-backed IPO from 1995 to 2000, the entire dot-com boom adjusted to today’s dollars, was around $780 billion.

Two companies, each worth more than an entire era of internet investment, with business models nowhere near equilibrium, in a model layer that is commoditising in real time.

There are three ways to make that math work:

1. The valuations are irrational and a correction is coming.

2. The commodity thesis is wrong and one or both labs builds a lasting moat through something not yet invented.

3. The application layer ends up being worth so much that the model providers capture enough of it to justify the numbers.

Evans ends with William Goldman’s line: “No one knows anything.” The internet era produced AOL, Yahoo, and Pointcast before it produced Google. The mobile era produced WAP and Nokia before it produced the iPhone.

Every platform transition has false starts, confident predictions that age terribly, and a long stretch of genuine uncertainty before the real picture emerges. This one will be no different.

The infrastructure is real. The growth is real. The most important chapter of this story hasn’t been written yet.

The accountant who saw VisiCalc in 1979 and understood what it meant built something lasting. The one who called it a curiosity missed everything that followed.

That decision is sitting in front of every operator and founder reading this right now.

That gap is the reason AI exists at all. It is why researchers trained on the entire internet instead of curating datasets, and why everything is getting disrupted now instead of in 2040.

I watched the full Stanford CS153 lecture so you do not have to. Here are the 10 things that matter for any founder, operator, or investor paying attention.

Here are the 10 things that matter 👇

Together with Attio:

Jensen’s whole point is that agents stop demoing and start doing the work. Attio is where that already happens to your revenue. It is the AI CRM that runs around the clock, turning every signal into one living view of every account.

Here is what that looks like inside your pipeline:

▫️ Agents on every account that research, qualify, and move each deal forward while you sleep

▫️ One live picture of every account, built from emails, meetings, and agent activity as it happens

▫️ Ask Attio anything about your business and get instant answers and actions from one chat thread

It is the CRM for the new way of going to market. Join the 30,000+ teams already on it.

Start Free today !

1. The 1,000,000x number holds, and the reason behind it is the only strategy lesson you need this decade

Moore’s Law is over. It has been for a decade.

“In the case of NVIDIA and co-design, we got 1,000,000x over 10 years. Somewhere between 100,000x and 1,000,000x. When you’re talking about numbers that big, it really doesn’t matter.”

Dennard scaling collapsed around 2015, and without it Moore’s Law compounds to maybe 10x over a decade. Semiconductor physics ran out of road, and NVIDIA delivered the full million anyway.

The mechanism is co-design: optimizing CPUs, GPUs, networking, switches, storage, software, and compilers at the same time, against the same objective, instead of leaving each layer to its own team. It is the same vertical integration logic that turns a hardware company into a compounding machine.

Jensen made it concrete with RISC. John Hennessy at Stanford proved that a simpler instruction set co-designed with a compiler beats two separately optimized systems every time, because the whole outperforms the sum of the parts. Scale that across an entire compute stack and a million-x follows.

The downstream effect is not a faster computer, it is a different category of possibility. When compute gets a million times faster, researchers stop asking which data to use and reach for all of it, the entire internet. That abundance is what unlocked modern AI, not a breakthrough algorithm but a design philosophy.

Try this → before your next architecture decision, ask whether you are optimizing a layer or co-designing across layers. The answer predicts your ceiling.

2. NVIDIA built a multi-billion-dollar system with zero potential customers, and first principles is how you do that without going insane

The most expensive supercomputer ever sold cost $350 million.

“You would have precisely zero customers. The reason for that is because the most expensive thing that has ever been sold was $350 million. And you’re building something that’s multiple billions of dollars. So you’re building for a precisely marketplace of zero.”

Jensen did not survey the market, he reasoned through the problem. Pre-training was going to be enormous, the systems to run it at scale would cost more than anything ever built, and no customer existed yet, so they built it anyway. Hopper was designed for that bet, and the architecture landed exactly when the demand arrived.

The lesson is narrower than “be contrarian.” Market research tells you what customers want today. First-principles reasoning tells you what they will need to want for the world to work the way the evidence says it is heading. One builds the future, the other optimizes the present, and the best founders know which question they are answering.

Try this → take your most important product bet and ask whether it came from customer interviews or first-principles reasoning. If you cannot tell the difference, that is the problem to solve first.

3. Inference is where the money gets made, and the bottleneck is not what most engineering teams optimize for

Training builds intelligence, inference delivers it, and the entire business of AI runs on inference.

“The speed up over the previous generation: 50 times. In two years, we improved something by 50 times. Moore’s law would have improved it by 2x.”

Here is the constraint most engineers miss. Generating tokens is bandwidth-constrained, not compute-constrained. The pre-fill phase processes context, the decode phase generates every token, and decode dominates because it needs more memory bandwidth than a single chip can provide.

NVIDIA’s answer was Grace Blackwell NVLink72: 72 chips ganged into the world’s first rack-scale computer, solving for the actual bottleneck and landing a 50x gain in two years. The co-design philosophy compounds, because a million-x over a decade is 50x here and 50x there, stacking.

Teams optimizing MFU, model flops utilization, are measuring the wrong thing. Jensen would rather run low MFU and be over-provisioned than hit 100% and fight Amdahl’s Law on every workload. Optimize for the constraint that limits you, not the metric that is easy to track.

Try this → name one metric your team optimizes that does not map to the constraint actually limiting your output, and retire it.

4. Stanford has a $40 billion endowment and no supercomputer, and Jensen says that is Stanford's fault

There is no chip shortage, there is a budget structure problem.

There is no chip shortage, there is a budget structure problem.

“It is not true that people are giving me orders, placing orders, and we’re not delivering chips. It is just not true. You’ve got to place orders.”

Every research department at Stanford raises its own grants, no grant is large enough to justify shared compute infrastructure, nobody pools resources, and the result is a campus of laptops and zero supercomputers.

Jensen’s fix is blunt. Stanford has $40 billion, so cut $1 billion, contract a cloud provider, and give every student access to AI supercomputers this year. The chips exist, the money exists, the structure is the problem.

His accountability framing is the sharpest insight here. When you tell someone it is not their fault, you take away their ability to fix it, because fault and agency are the same thing. Assign the fault correctly and you assign the power to solve it. He is not criticizing Stanford, he is refusing to let it off the hook.

The same pattern sits inside every large company: fragmented budgets, siloed compute, everyone underpowered. The organizations that aggregate first will produce the work that defines the next decade.

Try this → map every compute and data resource your team uses, find what is fragmented that could be pooled, and treat the gap as a budget structure problem rather than a resource problem.

5. The last time computing changed this fundamentally, it was 1964, and that date tells you exactly what to audit

This is a reinvention, not a technology cycle.

“For the first time, the way you write the software, how you process the neural network versus the software, and what the applications can do has now dramatically changed. Everything is fundamentally different.”

The IBM System/360 defined the computing model in 1964, and everything since (PCs, internet, mobile, cloud) was built on that foundation of prerecorded software, compiled binaries, and explicit instructions. The model held for 60 years.

Neural networks run differently than compiled code, and that one fact breaks every assumption the old model made:

▫️ Software is no longer written and compiled, it is trained

▫️ Output is generated as it happens, rather than retrieved from storage

▫️ The computer responds to intention, not only to instruction

▫️ Applications that needed human-level perception are now buildable

Alpamayo, NVIDIA’s self-driving system, is the proof. Thirteen years of self-driving work, nothing good enough, then deep learning arrived and the entire application category unlocked. That is what a genuine reinvention looks like: a different category of possible, not a faster version of the old thing.

Try this → audit your product’s core assumptions, find the ones shaped by the 1964 computing model, and ask whether they still hold. The ones that do not are either your biggest risk or your biggest opportunity.

6. The moment GPT shipped, agentic systems were obvious, and the founders who saw it built the infrastructure

Generative AI did not make images. It made thinking visible.

“Thinking is generating tokens that you consume internally. Generating tokens that you consume externally would be called tool use. And so the idea that after GPT happened two years ago, that we would be at this moment was fairly easy to predict.”

When GPT shipped, Jensen did not see a chatbot, he saw that the mechanism generating text can generate thoughts. Internal token generation is reasoning, external token generation is tool use, and the agentic trajectory was a direct mechanical consequence, a derivation rather than a guess.

The engineering between GPT and today was hard work by brilliant people: training models to reason step by step at scale, fine-tuning for reliability, building the tooling. The destination was legible in 2023 to anyone reasoning carefully about the mechanism.

The current signals read just as plainly. Agentic systems are here, continuous compute is replacing on-demand compute, and everything built for on-demand will get rebuilt. The founders who saw it early are building the infrastructure everyone else now rents.

Try this → name the next step in the trajectory from where AI is today, write it down, and build against it. If you cannot name it, that is the gap to close first.

7. Open models are not about the PR war with OpenAI, and the three reasons that matter more than the headline

NVIDIA burns more Anthropic and OpenAI tokens than almost any company, and that is not a contradiction.

“There are too many societies where the scale of their language is not big enough for somebody else to decide to make it a high priority. Unless you deeply care, it’s never going to be great.”

Three reasons, ordered by how underappreciated they are.

First, 230 languages where no major lab will prioritize fine-tuning. Nemotron, NVIDIA’s near-frontier open model, exists so any researcher anywhere can fine-tune for any language without starting from scratch. That is infrastructure for human intelligence at global scale.

Second, human priors. Alpamayo is a language model fused with a world model, and that fusion means the self-driving system needs a few million training miles rather than billions. The data requirement collapses when the model reasons from human experience instead of learning every edge case from zero.

Third, you cannot secure a black box. A closed-model arms race in cybersecurity is just version numbers climbing while everyone stays exposed in between. Transparency is how you defend, and Nemotron Nano, deployed in swarms, already runs this way.

Try this → pick one domain-specific model you build or use, and ask whether fusing it with a language model that carries human priors would cut your training data requirement. If yes, that is a compounding advantage sitting unused.

8. Vera Rubin is not a faster training chip, it is the first computer designed around how agents actually work

Agents do not compute the way training clusters compute.

“The AI is this multi-billion dollar system and it sends off an instruction to use a tool and that tool is gonna run on the CPU. Meanwhile, this GPU supercomputer, this multi-billion dollar system is waiting for this one CPU.”

The agent compute pattern has three requirements current cloud infrastructure was not built for.

Long-term memory has to live in storage wired directly to the processor fabric, because copying data off network storage kills latency. Tool use runs on CPUs, and cloud CPUs were designed for parallel throughput, 200 cores each doing independent work. Agent workloads need the opposite: single-threaded operations with extreme low latency, because a billion-dollar GPU cluster stalls waiting on one CPU thread.

Storage and CPU architecture both get redesigned for this pattern, and Vera Rubin is that redesign. Feynman, the generation after, is likely built for swarms of agents running sub-agents running their own sub-agents. Jensen names the method: identify the compute pattern, understand how it differs from the past, and build the system to match the actual workload.

Try this → map the actual compute pattern of your most important agent workload, find where latency enters, and ask whether your infrastructure was designed for that pattern. The gap is your performance ceiling.

9. Energy for AI is probably 1,000x current levels, Jensen has done the math, and the market is starting to agree

The bottleneck after chips is energy. This has been true for five years. Most people are still learning it.

The bottleneck after chips is energy, and most people are still learning that.

“The amount of energy that we need for computing is likely probably a thousand times more than we currently have. And so I think if you said we need a thousand times, I wouldn’t be surprised if we’re off by a couple of orders of magnitude.”

The reasoning is structural. Old computing is on-demand and retrieval-based: a server sits idle until a request arrives, responds, and goes back to idle, consuming energy per query. New computing is generative and continuous: a model runs at all times, contextually aware, generating outputs before you ask. The energy profile is a different category, not a 2x bump.

Two levers sit inside NVIDIA’s control:

▫️ Tokens per watt, already improved 50x, compounding through every generation

▫️ Co-design efficiency choices made from the chip level up

The lever outside its control but within reach of the market is energy infrastructure. Solar and nuclear needed subsidies to pencil out five years ago, and the compute demand is now strong enough that the market funds them without subsidies. Jensen calls this the best moment in history to invest in sustainable energy, which is a market-structure observation, because the demand curve justifies the capital.

Track this → tokens per watt across your inference stack. The teams improving it fastest will hold a structural cost advantage within three years that is hard to close from behind.

10. The AI doom narrative is not just wrong, it is built to sound unfalsifiable, and Jensen is not being polite about it

Jensen does not hedge here.

“It is not true that we have no idea how these systems work. It is not true that the technology is going to somehow in some nanosecond become infinitely powerful and therefore it’s going to take over the world. It is not true. These things are all being made up.”

The singularity-flash claim runs like this: at some unknown Wednesday at 7pm, AI becomes infinitely powerful, the game ends, no way to know when, no way to defend, some chance it ends civilization.

His counter is specific rather than “trust us.” We understand how these systems work, capabilities scale predictably with investment and architecture decisions, defenses can be built and tested, and the trajectory is legible. None of that fits the singularity-flash story. The more grounded version of the safety conversation looks nothing like the doom one.

The harm is concrete. The students in that hall are deciding whether to enter computer science, and the narrative shapes that choice. A generation raised to believe AI is an unfathomable danger enters policy rather than engineering, advocates for restriction rather than building, and cedes the field to people who do not share that hesitation.

GPUs are general-purpose compute. A billion people own them, running medical imaging, logistics networks, climate models, and video games. The comparison to atomic bombs makes useful thinking impossible, because every policy conclusion that starts there is contaminated.

Try this → the next time you read an AI safety claim, ask whether it is falsifiable. If no evidence could disprove it, it is a narrative, not a safety argument, so treat it accordingly.

The stack changed, all of it. Here is what that means depending on where you sit.

Jensen’s thesis is not about chips, it is about co-design as a principle applied at every scale. Optimize a layer and you get linear improvement. Co-design across layers and you get compounding. That holds for hardware, for product architecture, and for organizations.

Founders

The compute pattern for agents differs from the pattern for training, so build for the actual one and know whether your infrastructure matches the workload. The founders who map this in the next 24 months will build the platforms everyone else runs on, and the startup ideas worth building right now are already public.

Investors

The energy constraint is structural, and the market is now large enough to fund the solution without subsidies. The compounding returns sit in efficient inference, agent-optimized infrastructure, and the energy layer underneath all of it. Incumbency does not predict who wins, first-principles reasoning does, so find the teams doing it before the consensus catches up. Start from the investor list of lists and where the venture money is moving.

Operators

The computing model that held for 64 years just changed. The teams who internalize that as a first-principles fact will rebuild the stack correctly, the teams who treat it as an upgrade will spend the decade debugging assumptions that were never right for this environment. Start with how to use Claude like the top 1% of users and the complete guide to AI coding in 2026.

Anyone entering the field

The door is wider open than it has been since 1964, every layer of the stack is being rethought, and the people doing the rethinking are the ones reasoning most sharply about what changed. The 2026 AI engineer roadmap and the Claude Architect certification curriculum are where that reasoning starts.

Three principles to carry forward

▫️ Co-design wins. Individual layer optimization has a ceiling, and integration removes it.

▫️ The compute pattern determines the architecture. Know the pattern before you write a line of code, because everything else is guessing.

▫️ The trajectory is legible. GPT made agents obvious, agents will make swarms obvious, and the signals exist, so reason from them instead of waiting for the market to confirm them.

The stack changed, all of it. This is the best time in 60 years to be the person rebuilding it.

Full lecture: Stanford CS153 Frontier Systems, Jensen Huang from NVIDIA on the Compute Behind Intelligence.

If this breakdown saved you an hour, share it with one engineer, founder, or operator who needs to see it.

Full lecture: Stanford CS153 Frontier Systems, Jensen Huang from NVIDIA on the Compute Behind Intelligence

If this breakdown saved you an hour, share it with one engineer, founder, or operator who needs to see it. They will thank you later.

The agents that replace a workflow instead of assisting with it share one trait. They can pick up whatever tool the task needs, run it, read what happened, and adapt. That loop requires something most builders never give their agent. A computer of its own.

Satya Nadella framed the platform shift in one line. Every agent needs its own computer. The reason your agent feels like a clever demo instead of a worker is that it can reason about code but cannot run it, see the error, and fix it.

Here is the math that matters. A data agent that runs Python against a CSV and hands back a formatted report collapses a 30 to 45 minute analyst loop into a single call. Run that 10 times a week and you bank 5 to 7 hours. A coding agent that applies its own fix, runs your tests, and confirms nothing broke turns a five-message back-and-forth into one. The compounding shows up by Day 30, when your team stops babysitting prompts and starts shipping work that was already verified before it reached a human.

Together with Outskill:

Banking those hours assumes you can drive Claude past the chat box. Most people never touch its Code and Cowork modes, where the agent work actually happens. Outskill closes that gap in a weekend.

Their live 2-Day Claude AI Mastery Workshop condenses 800+ hours of research into 16 hours: Chat, Cowork, and Code, plus Skills, Connectors, and 10+ tools that keep Claude working while you sleep.

Register NOW!

Giving an agent a computer is the unlock. Doing it safely is the part that breaks teams in production. You cannot hand your agent your laptop, and a Docker container is not the isolation boundary you think it is.

This playbook is the build. Here is what sits behind the paywall:

▫️ The 4-layer build pattern that wires a sandboxed computer to any agent framework in under 40 lines, with copy-paste code for LangGraph, the OpenAI Agents SDK, and a raw Claude tool loop

▫️ 12 copy-paste prompts and tool definitions that give your agent a shell, a filesystem, and a package manager it can actually use without hanging

▫️ The accurate security model, including why Shai-Hulud and Copy Fail (CVE-2026-31431) turn a container foothold into host root, and the seccomp and kernel mitigations that stop it

▫️ The provider decision matrix across E2B, Modal, Daytona, Cloudflare, Fly.io, and LangSmith Sandboxes, with the price-per-1,000-runs math so you pick once and never re-platform

▫️ The 8 failure modes that kill sandbox agents in production, each with the exact fix (zombie sandboxes, secret leakage, fork explosions, cold-start tax, and four more)

▫️ The ROI model that converts sandbox spend into hours saved, with the break-even point most teams hit inside three weeks

▫️ The 30-day rollout broken into Week 1 through Week 4, from first shell call to burst-scale eval harness

▫️ 10 advanced moves: snapshots and copy-on-write forks, pre-warmed blueprints, authenticated service URLs, and the auth-proxy pattern that keeps secrets off the agent runtime entirely

Pair this with the deeper AI Corner library if you want the full operator stack:

▫️ The AI Agents library for orchestration and reliability

▫️ The Prompting and Context Engineering library for the tool-call patterns that keep agents on track

▫️ The AI Tools and Models library for the coding-agent and infra comparisons

▫️ The Claude and Anthropic library for the model side of the loop

▫️ The Business and Investing library for where the capital is moving on agent infra

Related builds worth reading next: the AI agent reliability playbook, the Claude Code system that replaces your dev loop, the 5-agent sales team you build in a weekend, the 20-agent script factory, the AI code review checklist, and the context engineering guide.

📦 The Agent Computer Build Kit

The full build in one place, wired and copy-paste ready: the 4-layer pattern, the 12 prompts and tool definitions, the provider matrix with the per-1,000-runs math, the 8 failure-mode fixes, the ROI model, the 30-day rollout, and the 10 advanced moves.

Get The Agent Computer Build Kit below 👇

Try premium free for 7 days. Or get 50% off this week only.

Read more

Andreessen said it. Amodei said it. Hassabis said it. Three frontier-lab CEOs converged on the same thesis in the same quarter, and OpenAI just shipped the most operational version to date.

Codex. Autonomous coding agent. Background workers. Scheduled tasks. Long-running jobs running in sandboxed environments while you sleep, shipping pull requests, drafting reports, qualifying leads, waking you up to merged work.

9 of 10 builders are still using ChatGPT like a smarter search bar.

Most people ask, get an answer, copy it out, move on. A workflow runs on a trigger, uses tools to act, and hands you a finished result. The chat answers. The automation acts.

This article is the operator playbook. 10 background workflows with the exact build pattern OpenAI’s team uses. By Sunday, you have at least 3 of them running.

Inside this Playbook:

▫️ The 10 background workflows OpenAI’s own team runs while they sleep, with copy-paste prompts for each:

• Morning briefing

• Codebase guardian

• Bug triage and fix

• PR review and merge

• Lead qualifier

• Client report engine

• Content repurposing

• Daily research digest

• Sales call prep

• Inbox triage

▫️ The 4-step build pattern that turns any task into a Codex workflow (Role → Tools → Trigger → Output)

▫️ The 6 failure modes that burn 5-10x your token budget, with the exact fixes

▫️ The Claude vs Codex matrix: which model leads which workflow, with the cost math

▫️ The 30-day rollout from your first scheduled task to a team-wide automation library

▫️ The quarantine pattern for untrusted input (prompt injection protection for client-facing workflows)

Plus the entire AI Corner premium archive:

▫️ Claude and Anthropic library

▫️ Prompting and Context Engineering library

▫️ AI Agents library

▫️ AI Tools and Models library

▫️ Business and Investing library

▫️ Your voice is the only AI moat that compounds

▫️ I built a $0 second brain with Obsidian + Claude

▫️ Build your own stock analyst with Claude: the 12-prompt system

▫️ The Claude Code system that replaces a 5-person team

Every breakdown. Every playbook. Every prompt library.

Try premium free for 7 days. Or get 50% off this week only.

🔒 THE FULL CODEX BACKGROUND WORKFLOWS PLAYBOOK (PREMIUM)

Get 50% off forever

Read more

Marc Andreessen said it to the a16z LPs in January. Dario Amodei said it at Davos. Demis Hassabis confirmed it on stage in May. The moat in 2026 lives in the system you build around the model, not in the model itself.

Anthropic just shipped the most operational version of that thesis to date.

Dynamic Workflows in Claude Code. Live since May 28, 2026. Claude writes its own custom harness in JavaScript, on the fly, for whatever task you give it. Subagents. Parallel execution. Per-agent model choice. Per-agent isolation. The same scaffolding Anthropic’s own engineers use to ship code migrations, deep research, 1,000-item sorts, and adversarial verification at scale.

9 of 10 builders have not tried it once.

The teams that internalize this before the rest of the market are the ones shipping reliable, auditable agents at production scale by Q4. The rest are still chaining 50 prompts by hand.

This article is the full playbook to be one of them. Six patterns. Fourteen steps. The code Anthropic’s engineers actually run.

For the strategic context, see the AI Agents library, the Prompting and Context Engineering library, and the Claude and Anthropic library.

The free section ends here.

Below the paywall:

▫️ The 6 patterns Anthropic’s engineers actually use, with copy-paste JavaScript for each:

• Fan-out and synthesize

• Classify-and-act

• Adversarial verification

• Generate-and-filter

• Tournament

• Loop-until-done

▫️ The 14-step roadmap to ship your first Dynamic Workflow this weekend

▫️ The 8 use-case compositions: migrations, deep research, sorting at scale, root-cause investigation, triage, design taste, lightweight evals, and verification

▫️ The quarantine pattern for untrusted input (prompt injection protection)

▫️ The 7 failure modes that burn 5-10x your token budget, with the fixes

▫️ The 30-day rollout from your first workflow to a shipped Claude Skill

Plus the entire AI Corner premium archive:

▫️ Claude and Anthropic library

▫️ Prompting and Context Engineering library

▫️ AI Agents library

▫️ AI Tools and Models library

▫️ Business and Investing library

▫️ Your voice is the only AI moat that compounds

▫️ I built a $0 second brain with Obsidian + Claude that compounds for life

▫️ Build your own stock analyst with Claude: the 12-prompt system

▫️ The Claude Code system that replaces a 5-person team, etc

Every breakdown. Every playbook. Every prompt library.

Try premium free for 7 days. Or get 50% off this week only.

→ Unlock the full toolkit:

Get 50% off forever

🔒 THE FULL DYNAMIC WORKFLOWS PLAYBOOK (PREMIUM)

Everything below is operational. Copy. Paste. Adapt:

Read more

And that’s where the competitive advantage is won or lost.

Ask a founder how their team is doing with AI and you’ll hear some version of the same answer. “I use ChatGPT to draft emails.” “We have a share prompt in Notion.”

Okay. Now remove every AI tool from your team. If the business runs the same way, just a bit slower, nothing has actually changed. Most teams are in that category and don’t know it.

There are five levels of real AI adoption. Most companies are sitting at Level 1 or 2 while telling themselves they’re at 3.

The levels below are a diagnostic and a plan. So use them to find where you actually are. Be honest while reading. The coaching only works if you are.

And don’t skip ahead. That’s how companies spend six months building the wrong things.

📢 A quick word before we get into it:

The fastest way to tell what level your team is at: hand them a tool and watch

A Level 1 team uses Lovable to draft a landing page nobody ships. A Level 3 team spins up subagents that research the codebase, audit the build, and synthesize a dataset in parallel, while the founder is in a meeting.

Subagents just shipped. Anton Osika put it directly: “AI products should hide complexity without hiding power.”

It is the closest thing I have seen to letting a Level 1 team operate like a Level 3 one, without rebuilding the stack.

AI Corner readers get 10% off through this link.

Claim your exclusive 10%

Now back to the diagnostic:

Table of Contents

1. Level 1 — The Isolated User

2. Level 2 — The Enthusiastic Team

3. Level 3 — The Systems Builder

4. Level 4 — The Transformed Organization

5. Level 5 — The Continuous Reinventor

6. A Final Honest Note

LEVEL 1 — The Isolated User

“I’ve been playing with AI. It’s pretty cool.”

What This Actually Looks Like

At Level 1, AI is a personal experiment. Someone on your team (or even you) has started using ChatGPT or Claude in their personal time and is now occasionally using it at work.

Usage is sporadic. There’s no shared language around it. No one is teaching anyone else.

The defining characteristic of Level 1 is that AI lives in individual browser tabs. When the tab closes, the work is gone. Nothing is saved, systematized, or repeatable. If that person goes on holiday, the AI usage of the entire team effectively drops to zero.

Diagnostic Signals — Are You Here?

If you answered yes to most of these, you are at Level 1. Welcome! Everyone starts here. But the danger isn’t being here. The danger is thinking you’re not.

The Real Ceiling at Level 1

The ceiling at this level is isolation. Every person is rediscovering the same things independently. One person figures out a great way to summarize meeting notes. Another person is spending 45 minutes doing it manually. Neither knows about the other.

So the compounding knowledge that makes AI transformative simply cannot happen when everything lives in individual conversations that disappear.

There is also a confidence problem. People at Level 1 often don’t know what they don’t know. They have seen AI write a paragraph or answer a question, but they have no mental model for what AI can actually do at scale. This limits what they even think to try.

Coaching Plan: How to Move to Level 2

Step 1: Create psychological safety around experimentation.

The single biggest barrier at Level 1 is fear of looking foolish. People don’t want to admit they’re new to this.

So run a team session. Call it an “AI Show and Tell” where everyone shares something they tried, whether it worked or not. Normalize failure. The goal is to make experimentation feel like the expected behavior, not an extracurricular one.

Step 2: Pick one shared tool and commit to it.

Tool fragmentation at this stage is a distraction. Pick one primary AI interface (Claude, ChatGPT, Gemini) and make it the team standard. Reduce the cognitive overhead of “which tool do I use?” The best tool is the one your team will actually use consistently.

Step 3: Identify your early adopters and amplify them.

There are always one or two people who are naturally ahead. Find them. Give them time, recognition, and permission to experiment more. Make them informal champions. They will do more to move the team than any top-down mandate.

Step 4: Assign one concrete use case this week.

The fastest way out of Level 1 is a single forcing function: one specific task, done with AI, by everyone on the team, this week. Not “use AI more.” Something specific. “Summarize your last three client meetings using AI and share the output in Slack.” Specificity kills paralysis.

Step 5: Start a simple shared document of what works.

A Google Doc. A Notion page. A Slack channel. It doesn’t matter. Start capturing the prompts, approaches, and use cases that actually produce good results. This is the seed of your future prompt library and institutional knowledge base.

LEVEL 2 — The Enthusiastic User

“Our team is using AI. It feels magical. We’re saving time.”

What This Actually Looks Like

Level 2 is seductive. There’s genuine enthusiasm, visible results, and people feel meaningfully more efficient. Leadership is paying attention. There might even be a shared Slack channel where people post cool AI outputs. AI has moved from personal experiment to team conversation.

But here’s the truth: almost nothing structural has changed. The work is still being done the same way it always was. AI is a faster typewriter, not a new system. Headcount is the same. Processes are the same. The org chart looks identical to two years ago.

The danger at Level 2 is that the “magic feeling” creates the illusion of transformation. Teams get comfortable here. It feels like progress.

Well, it is progress, but it’s the easy part.

Diagnostic Signals — Are You Here?

If yes to most: you’re at Level 2. This is where most companies in 2026 are sitting. Comfortable. Not yet transformed.

The Real Ceiling at Level 2

The ceiling here is person-dependency. Every AI workflow lives inside a person’s head or their individual chat history. If Sarah leaves, Sarah’s AI workflows leave with her. You haven’t captured institutional knowledge, you’ve just given individuals faster keyboards.

The other ceiling is scope limitation. Teams at Level 2 are using AI for tasks that were already being done. No one has asked the more important question: what work should we be doing that we haven’t been able to do before because it was too expensive or time-consuming? That’s where the real value hides.

Coaching Plan: How to Move to Level 3

Step 1: Systematize what’s already working.

Audit what your team is actually using AI for. Identify the five most common use cases.

Now codify them: write proper, reusable prompts with instructions, context, and output format specifications. Move these from individuals’ heads into a shared, versioned library. Give it a home with ownership. Someone whose job it is to maintain and improve it.

Step 2: Connect AI to at least one real data source.

The leap from Level 2 to Level 3 begins when AI stops working only on what you paste into it.

Identify one system (a CRM, an analytics dashboard, a financial tool) and find a way to pull data from it into your AI workflow.

This might be a simple export and upload process at first. That’s fine. The point is to experience what happens when AI has context it didn’t have before.

Step 3: Redesign one full workflow end-to-end.

Don’t add AI to an existing process. Redesign the process around AI.

Take one high-frequency, high-effort workflow (a weekly report, a client brief, a variance analysis) and ask: if AI is doing the heavy lifting, what does this process look like from scratch?

The answer is usually radically different from what you have today.

Step 4: Measure and publicize the gains.

At Level 2, people feel the magic but can’t quantify it. Start measuring.

Time saved per task. Quality scores. Volume handled. Even rough numbers create accountability and excitement. Share them. Nothing accelerates adoption like proof.

Step 5: Hire or designate an AI translator.

You need someone who understands both the business problems and the AI capabilities well enough to bridge them.

This isn’t a data scientist or an IT person. It’s a curious, operational thinker who can look at a messy business process and reimagine it. Find them internally first. If you can’t, hire for it.

LEVEL 3 — The Systems Builder

“Our AI agents are working across tools. Real automation is happening.”

What This Actually Looks Like

Level 3 is where things get genuinely interesting, but also genuinely uncomfortable.

AI agents are now connected to multiple systems. Work is happening without direct human initiation. A trigger in one system sets off a chain of actions across others. Things are getting done overnight that used to require a Monday morning meeting.

Uncomfortable, because people start looking at their role and asking hard questions. If an agent can pull data from three systems, flag anomalies, draft a memo, and route it to the right person.. what exactly does the analyst do now?

Questions like that deserve honest answers, not reassurance.

Diagnostic Signals — Are You Here?

Level 3 is real systemic change. Most teams hit it in pockets where one function transforms while others stay at Level 2. That’s normal. The goal is to expand the pockets.

The Real Ceiling at Level 3

The ceiling at Level 3 is brittleness and trust.

Agents break when edge cases arise. Data is messier than anyone anticipated. Outputs need more checking than you hoped. Teams build impressive systems and then spend enormous energy maintaining them and debugging failures. This creates fatigue and skepticism.

The other ceiling is organizational resistance.

When systems start doing things automatically, people get nervous. Privacy concerns, compliance questions, “what if it’s wrong?” objections.

These are real concerns wrapped in legitimate fear. The teams that navigate this fastest are the ones that build robust feedback loops. That build ways for humans to catch, correct, and teach the system from its mistakes.

Coaching Plan: How to Move to Level 4

Step 1: Build a “trust framework” for your agents.

Define explicitly:

• What decisions can agents make autonomously?

• What requires a human in the loop?

• What requires human approval before action?

Create a tiered model. Low-stakes, reversible actions get full autonomy. High-stakes, irreversible actions always get human review. That’s what makes agents trustworthy enough to actually use at scale.

Step 2: Instrument everything.

If you can’t see what your agents are doing, you can’t trust them, improve them, or explain them to your leadership and regulators. Build logging, audit trails, and monitoring into every agent workflow from day one.

This is the boring infrastructure work that separates serious AI programs from impressive demos that never scale.

Step 3: Create feedback loops into your agents.

The best AI systems get smarter over time because humans correct them and those corrections get incorporated.

Build a simple mechanism (a Slack reaction, a thumbs down button, a weekly review) where humans can flag bad outputs. Someone should own the process of periodically reviewing these flags and updating the system’s instructions, context, or logic accordingly.

Step 4: Now ask the hard organizational question.

With agents handling meaningful workflow volume, sit down with your leadership team and ask: if we doubled our output with the same headcount, what would we do with it? And if some roles are genuinely redundant, what’s the right way to handle that?

Level 3 forces a talent and org design conversation. Don’t avoid it. Lead it.

Step 5: Expand successful patterns across functions.

Find the one or two agent workflows that are working exceptionally well. Document the pattern: the data sources, the trigger, the decision logic, the output format, the human touchpoints.

Now find three other processes that fit the same pattern. Clone and adapt. Scaling at Level 3 is about pattern replication, not building every workflow from scratch.

LEVEL 4 — The Transformed Organization

“We’ve restructured around AI. The org chart has changed. The math has changed.”

What This Actually Looks Like

Level 4 is where AI stops being a tool the organization uses and starts being a force that reshapes the organization itself.

Reporting structures change. Roles merge. Headcount grows more slowly than revenue. Teams that used to have five people accomplish the same or more with two, because the other three were primarily doing coordination, formatting, routing, and basic analysis; all things agents now handle.

This is also where the best talent starts to self-select in. People who want to be at the frontier of how work gets done are drawn to Level 4 companies. People who want certainty and stability are not. Knowingly or not, your culture has made a choice.

Diagnostic Signals — Are You Here?

Very few companies are genuinely here yet. If you are, you have a significant and compounding advantage.

The Real Ceiling at Level 4

Paradoxically, the ceiling at Level 4 is speed of reinvention.

Organizations that restructure successfully can become attached to the structure they built. They optimize the new org design relentlessly, and then a new model capability arrives that makes part of that design obsolete again.

The teams that get stuck are the ones that treat Level 4 as a destination rather than a waypoint.

The other risk is capability concentration. When teams get very small and very AI-dependent, key-person risk becomes acute in a new way.

If the one person who understands the agent stack leaves, you could lose capabilities that took 18 months to build. Documentation and knowledge transfer become mission-critical disciplines.

Coaching Plan: How to Move to Level 5

Step 1: Build a permanent “reinvention rhythm.”

Schedule a quarterly process where each team asks:

• What have we built in the last 90 days that we would build differently today?

• What new capabilities exist that we haven’t explored?

This exercise creates discipline. The teams that reach Level 5 treat reinvention as a normal operating cadence, not an emergency response.

Step 2: Invest heavily in documentation as infrastructure.

At Level 4, your AI workflows are core business infrastructure. Treat them like it. Every agent, every prompt system, every integration should be documented as thoroughly as your financial controls.

This is the thing that keeps your capabilities alive when people move on.

Step 3: Start thinking about AI as a competitive intelligence function.

At Level 4, you are sophisticated enough to start systematically monitoring what AI can newly do and mapping it against your processes.

Assign someone (or an agent) to track major model releases and capability updates, and to translate them into “here’s what this unlocks for us specifically.” This turns AI advancement from a distraction into a strategic signal.

Step 4: Hire for reinvention tolerance, above almost everything else.

The people who thrive at Level 5 are not the best prompt engineers or the best coders. They are the people who genuinely enjoy building something, seeing it become obsolete, and building something better.

This is a personality trait more than a skill. It’s rare. Hire it aggressively when you find it.

LEVEL 5 — The Continuous Reinventor

“We rebuild before we have to.”

What This Actually Looks Like

Level 5 is a posture. A culture. A genuine organizational belief that the half-life of any current process is short, and that this is exciting rather than exhausting.

At Level 5, the question “how do we do this?” is always followed by “and how might we do it completely differently in six months?” Teams here are not chasing AI — they are ahead of it, in the sense that they have built the muscle to adapt before the adaptation is forced on them.

There is no fixed org design at Level 5. No fixed workflow. No sacred process. The only thing that is fixed is the commitment to the customer outcome and the business objective. How you get there is always in question.

Diagnostic Signals — Are You Here?

Honestly? If you’re asking whether you’re here, you’re probably not. Level 5 organizations don’t agonize over their level. They’re too busy building.

Coaching Plan: How to Stay Here

There is no “staying here” without continuous motion.

Level 5 is defined by reinvention, which means any period of consolidation is the beginning of regression. The coaching plan at this level is more philosophical than tactical.

Step 1: Protect the builders.

The people who actually build your AI capabilities are your most strategically important employees. Protect their time. Protect them from bureaucracy. Pay them accordingly.

Step 2: Distinguish between healthy reinvention and chasing shiny objects.

Not every new model capability needs to be integrated immediately. Level 5 requires judgment. The ability to distinguish between a new capability that is genuinely transformative for your specific business and one that is interesting but peripheral.

That judgment is a leadership skill, and it needs to be cultivated deliberately.

Step 3: Teach the outside world what you’ve learned.

The organizations that sustain Level 5 over time tend to be generative. They share what they’re learning through content, recruiting, and community. This creates a talent magnet and a knowledge feedback loop that compounds their advantage further.

Step 4: Never let AI literacy become a senior-only skill.

The most dangerous Level 5 failure mode is when AI capability concentrates at the top or in a specialist team.

The organizations that sustain this level are the ones where the most junior person on the team is also building, experimenting, and contributing to the collective knowledge.

A Final Honest Note

Most companies will spend 2026 convincing themselves they are at Level 3 while operating at Level 1 or 2.

A wrong self-assessment is real and costly.

The diagnostic above is designed to make that gap visible. Use it in a room full of people. Argue about it. The disagreement is usually more valuable than the conclusion.

What level you’re at today matters far less than the rate at which you’re moving. A Level 1 team moving fast is more valuable than a Level 3 team that has stopped questioning whether there’s a better way.

The only real mistake is standing still and calling it stability.

I watched the full Prof G Markets live show in San Francisco so you do not have to.

The AI Corner

Practical AI workflows, prompts, and tools for founders and operators who want to compound an advantage every week

By Ruben Dominguez

Here are the 10 biggest takeaways:

📢 A quick word before we get into it.

Galloway’s whole argument is that enterprise AI runs ahead of the controls that should govern it. The cost side breaks first. The access side breaks next, and quietly.

Opal’s 2026 Identity Governance Report just showed that 80% of systems are exposed through stale access. Access that should have been removed and was not…

Now layer AI agents on top, with permissions that compound every week, and the blast radius becomes impossible to contain.

Opal maps how AI-ready teams fixed the access layer before agents made the problem permanent.

Read the 2026 Report !

The CFOs running the AI cost audit Galloway describes will run the access audit next. The teams ready for both are on the right side of every line in this breakdown

1. Uber burned its entire 2026 AI budget before April. The COO said the costs are getting hard to justify

The flagship promise of enterprise AI was the simplest one. AI does the work, the bill goes down.

“The technology is actually more expensive than the humans it is supposed to replace.”

AI eliminated nearly 50,000 jobs this year. That approaches the full 2025 total. The layoffs arrived on schedule. The savings did not.

Uber exhausted its entire 2026 AI budget before the first quarter ended. Microsoft canceled cloud code licenses across multiple divisions. An NVIDIA executive confirmed publicly that compute runs far beyond the cost of employees.

The Uber COO did not hide it. CFOs say costs are hard to justify only after the internal conversation has already gotten uncomfortable.

Three things broke the model at once:

1️⃣ Compute costs were modeled against 2023 pricing. Usage assumptions were wrong by a factor.

2️⃣ Enterprise deployment requires far more inference volume than any projection captured.

3️⃣ Nobody budgeted for what happens when 10,000 employees get an AI tool with no usage ceiling.

The entire ROI case for enterprise AI depends on the cost equation flipping. Every CFO eventually faces a line item they cannot explain to a board. That moment is already here at Uber, Microsoft, and Salesforce.

For the honest version of which jobs AI is actually replacing right now, see no one is safe from AI and the SaaS defense playbook for the AI era.

2. Stripe spends $100,000 a day on AI tokens. The person who spends the most gets the trophy

The cost problem goes beyond size.

“They’ll create leaderboards at these companies, like Meta, like Amazon, where they will track how many AI tokens you’re using. The people who are using the most tokens are the most AI-deployed. Those are the ones who get recognized. Maybe they’ll get a promotion.”

Stripe’s technical staff spends nearly $100,000 on AI tokens every day. Salesforce is on track for $300 million in Anthropic spend this year. One Anthropic employee ran up a Claude Code bill of $150,000 in a single month. ServiceNow exhausted its entire Anthropic budget. Shopify reported earnings partially offset by increased LLM costs.

Meta. Spotify. Pinterest. Same story. Same quarter.

Companies built recognition systems around consumption. Employees rationally responded by consuming as much as possible. The incentive and the outcome are completely disconnected.

Four things broke in parallel:

1️⃣ A KPI measuring activity, instead of output

2️⃣ A leaderboard that rewards cost generation, instead of value creation

3️⃣ A promotion system tied to spend, instead of return

4️⃣ A budget with no anchor to any identifiable result

Token leaderboards are a company car with no fuel budget. Hand someone a tool, measure them on how much they use it, and the bill becomes the metric.

For the operator playbook on which AI workflows actually deliver ROI a CFO can name, see 25 Claude Skills that give your startup a marketing team it cannot afford yet, build your own stock analyst with Claude, and the 5-agent sales team you can build this weekend.

3. An MIT professor found 95% of AI projects connect to no return. The market has not priced that in

The number is the thesis.

“About 5% of the projects that people are using tokens for, CFOs can connect to some sort of return. They’re really intoxicated. Using AI as much as you can and talking about it in your earnings calls, it’s like adding .com back in the 90s.”

Companies added “.com” to their names in 1999 to signal relevance. It worked for about 18 months. Mentioning AI on earnings calls serves the same function today. A market communication strategy. Not a proof of value.

Galloway’s specific prediction: the first major CEO who announces a significant AI pullback due to missing ROI is the trigger event. NVIDIA’s first earnings miss follows. That miss takes the broader market down 5% to 10%.

NVIDIA has beaten estimates 15 consecutive quarters. The streak is the pressure.

The profile of the trigger CEO:

▫️ A traditional Fortune 500 company, not a tech native

▫️ Someone with credibility and no evangelism invested in the AI trade

▫️ A CFO-driven decision announced quietly on an earnings call

▫️ A statement that starts with “efficiencies” and ends with “scaling back”

When the first credible CEO says it out loud, the repricing happens the day of the announcement. NVIDIA is the tell.

For the investor lens on this exact moment, see Coatue’s 18-chart AI report, where VC money is going in AI, and the most valuable VC-backed startups in the world.

4. Chinese AI models are 10-30x cheaper. 80% of American startups are already using them

The part most enterprise AI conversations skip.

“Every developer in the world has heard of them because 80% of American AI startups are now using Chinese models.”

DeepSeek. Kimi K2. Xipu. GLM. The pricing gap runs 10x in some comparisons. 30x in others.

Two structural reasons explain it. Chinese AI companies receive direct government subsidies. They also engage in what the industry calls distillation: industrially harvesting outputs from American frontier models and using those outputs to train their own systems. Galloway names it plainly. Sophisticated theft.

Cost-pressured companies unable to justify their Anthropic or OpenAI bills migrate to whatever delivers similar outputs at a fraction of the price. The economics make the decision for them.

The migration runs without coordination:

1️⃣ CFO flags AI spend as unjustifiable

2️⃣ Procurement gets involved

3️⃣ Technical team identifies cheaper alternatives

4️⃣ DeepSeek performs comparably at 10-30x lower cost

5️⃣ Migration happens without announcement

American AI companies compete against models that are cheaper partly because they were built on stolen outputs. Markets alone will not correct that.

For the AGI race across labs and what each one is betting on, see Demis Hassabis named his AGI year, Anthropic just passed OpenAI in revenue spending 4x less, and Sam Altman watched 900 million people talk to one personality every week.

5. Galloway's precise prediction: AI valuations fall 50-70% in 24 months.

One number forces a choice between two futures.

“One of two things is going to happen. Either the valuations of AI are going to come down by 50% or 70%, or we’re going to have labor chaos in these industries. I absolutely think it’s the former.”

Walk the numbers. 155 million working Americans. Half are AI-vulnerable. That is 75 million people. At $100K average labor cost, that is a $5 trillion pool of potential savings. To justify current AI valuations through labor replacement alone, you need 5-7 million layoffs in 2-3 years. Roughly 10% labor destruction.

That has not happened. The layoffs this year are real. They are far below what the valuation math requires.

The AI fear machine runs on catastrophizing as a business model. Fear is the product. Capital is the outcome.

Mass disruption at the speed the valuation requires means visible chaos, political crisis, regulatory response. Disruption at the speed the evidence supports means valuations compress 50-70%. Quiet. Certain. Galloway thinks the second outcome is where this ends.

Being right about the technology and wrong about the timeline produces the same financial result as being wrong entirely.

For the VC version of this argument, see what top-tier VCs actually look for in 2026, what top VCs check in due diligence before writing checks, and $80 billion in 3 months: Q1 2026’s record-breaking fundraising.

6. Xi Jinping can flood the U.S. with cheap AI. 90-day window before Trump acts

The optimal play from Beijing is already obvious.

“AI is the only thing that feels like it’s propping up the economy right now. The Trump administration has too much to lose.”

A White House at 34% approval has one economic prop: the S&P and NASDAQ. Those indices have one primary support mechanism, which is the AI trade. Flood the U.S. market with cheap Chinese LLMs, go directly to CFOs already sick of their AI bills, and the trade begins to unwind.

Xi does not need to win the AI race. He needs to win the pricing war in procurement meetings.

80% of smaller American startups have already shifted to Chinese LLMs on cost alone. With a strategic push, it accelerates.

Galloway’s prediction unfolds in four steps:

1️⃣ Mass Chinese LLM adoption surfaces in earnings calls

2️⃣ American AI companies lobby for protection using distillation claims

3️⃣ The administration frames it as national security

4️⃣ The Trump administration bans Chinese LLMs within 90 days, using the BYD vehicle ban as the template

A Chinese LLM ban is a geopolitical event with direct market consequences. It validates the threat, protects American AI incumbents from below-cost competition, and installs the first real regulatory layer on a sector operating without one.

For the geopolitical and vertical-integration thesis, see Elon Musk and the outer limit of vertical integration and Dario Amodei named “the zeroth world”.

7. China ran this playbook on German industry for 30 years. AI is next.

“What China has done to Europe economically, they’re going to try to do to the AI market what they tried to do to the steel market here in the 80s and 90s.”

China attracted Volkswagen, Daimler, and Siemens with favorable economics. Chinese production and R&D became so profitable that when Germany tried to restrict IP theft and product dumping, its largest companies lobbied against the policy from the inside. They were already dependent on the arbitrage.

The steel playbook, now running on AI:

1️⃣ Subsidize model development to below-market pricing

2️⃣ Attract American developers with cost savings

3️⃣ Harvest outputs via distillation to improve models further

4️⃣ Create economic dependency before policy can respond

5️⃣ Use dependent American companies as lobbying assets against any proposed ban

Industrial strategy disguised as market competition.

For the strategic context of who positions for the next decade, see Mark Cuban on the AI thesis, Marc Andreessen on why the AI moat is not the model, and the AI agent that thinks like Jensen Huang, Elon Musk, and Dario Amodei.

8. SpaceX is the greatest business built in 50 years. The IPO bundles it with a division losing $2.5B per quarter.

Separate the asset from the structure.

“If you want to hang out with Snow White, SpaceX, you have to also invest in this money furnace called xAI.”

SpaceX by the numbers: 90% global launch capacity. Two-thirds of all low-Earth orbit satellites. $16 billion in revenue. $8 billion in operating profit. 30% annual growth. The deepest competitive moats of any business operating today.

At $700-800 billion, that company is priced aggressively but defensibly. Double it to $1.6 trillion for the Elon premium. That case can be made.

At $2 trillion, at 107 times sales, growing revenue at 15% annually, losing $20 billion per year, the numbers collapse.

The comparison that ends the argument: Google went public growing at 240% annually at 10 times revenue. SpaceX goes out growing at 24% at 100 times revenue. The ratio is roughly 1,000 to 1 in Google’s favor.

The Snow White is real and worth owning. The furnace is real too. Buying both without separating them is the mechanical path to overpaying by several hundred billion dollars.

For the VC playbook on separating asset from structure, see the most valuable VC-backed startups in the world, the ultimate investor list of lists, and Elon Musk and the outer limit of vertical integration.

9. SpaceX, OpenAI, and Anthropic IPO at $4T combined. None profitable. Retail investors are the last buyers.

The smartest people in the room are selling to you. That is not a metaphor.

“When these companies go public, it’s effectively the smartest people in the room saying: we’ve squeezed as much juice out of this as we can. We need to find people stupider than us to invest at this valuation.”

$4 trillion combined. That exceeds every dot-com IPO adjusted for inflation. It equals roughly half the combined value of every IPO in the prior 50 years. None of the three are profitable.

NASDAQ changed its rules specifically for these companies. Previously: 12 months of public trading before joining passive index funds. Now: 15 days for mega-caps. These three will represent approximately 6% of global public equity markets on listing day, before reporting a single public quarter.

The exit sequence is mechanical:

1️⃣ VCs and early investors know the financials better than anyone outside

2️⃣ Private capital can fund rounds of $10-15 billion without a public listing

3️⃣ Going public means insiders believe they have extracted maximum private value

4️⃣ The NASDAQ rule change accelerates passive fund inclusion before the public has one quarter of data

5️⃣ Retail investors become the last buyers in the chain

Galloway’s advice: sell immediately. Regardless of VC pressure, manager pressure, or any long-term vision framing.

Retail investors are the last buyers in a chain that started with the people who know these companies best. Sell on day one.

For the broader macro context on the AI capital cycle, see Coatue’s 18-chart AI report, where VC money is going in AI, and Anthropic is closing in on a $1 trillion valuation.

10. The one career skill AI cannot average its way into.

AI fluency is commoditizing. Relationships are not.

“The only competence that’s really important is storytelling and relationships.”

When Google posts a job, 200 resumes arrive within 60 minutes. The listing closes. Of the top 10 candidates brought in, 70% of the time the person hired had an internal advocate. Not the strongest resume. Not the most AI-proficient. A relationship inside the building.

AI drives output toward the median. The literal mechanism is averaging the previous words to predict the next one. Everything AI produces is a weighted mean of existing thought.

AI cannot produce the person who sends a text saying you were exceptional today. It cannot manufacture the advocate in the room when your name comes up.

Galloway’s four-part framework for anyone under 40:

1️⃣ Be as social as possible. Out of the house, not on a screen. Relationships compound like money.

2️⃣ Invest in storytelling and writing. If someone reads your work and says it sounds like AI, that is the worst professional insult available right now.

3️⃣ Get comfortable with rejection at volume. More no’s now means more advocates later.

4️⃣ Find your group before you need it. The person who gets the job had a friend in the room before the job existed.

Everyone is training to use AI better. Almost no one is training to be more human. The median is crowded. The internal advocate is not.

For the writing voice that distinguishes you from AI output, see your voice is the only AI moat that compounds. For the personal knowledge stack that makes your work sound like yours, see I built a $0 second brain with Obsidian + Claude that compounds for life and I built a second brain in 10 minutes with Granola + Claude.

Full podcast:

If this breakdown saved you two hours, share it with one founder or investor who needs to see it. They will thank you later.

The AI repricing playbook

The core argument is not that AI fails. AI is mispriced, misbilled, and misunderstood simultaneously, at historic scale.

For founders

The AI cost conversation is coming to your board whether you invite it or not. Map every dollar of AI spend to a specific outcome a CFO can name. Produce one number this week that a board member can connect to a result.

▫️ The SaaS defense playbook for the AI era

▫️ 50 game-changing AI agent startup ideas for 2026

▫️ The AI GTM playbook for 2026

▫️ 70 startup ideas YC wants you to build

▫️ The Claude Code system that replaces a 5-person team

For investors

Separate the technology from the valuation. Unprecedented fundamentals at insane valuations still produce bad returns. Model the technology on its merits. Price it on evidence, instead of narrative.

▫️ What top-tier VCs actually look for in 2026

▫️ Coatue’s 18-chart AI report

▫️ Where VC money is going in AI

▫️ The U.S. VC database most founders never find

▫️ The full investor lists archive

For operators and people in tech

The cheapest route to irrelevance is doubling down on AI fluency alone. AI fluency is commoditizing in real time. Write in a voice that sounds like you. Build one internal advocate this month, before you need it.

▫️ Your voice is the only AI moat that compounds

▫️ The single best productivity decision you can make with Claude right now

▫️ I built a $0 second brain with Obsidian + Claude

▫️ Build your own stock analyst with Claude

▫️ Why ChatGPT and Claude keep disappointing you

The 5 principles to take from Galloway

1️⃣ 95% of AI projects connect to no return a CFO can name. That number will move. Watch when it does.

2️⃣ Valuations correct before labor markets collapse. The apocalypse is not on schedule.

3️⃣ China’s pricing advantage is structural. Policy is the likely U.S. response. The 90-day clock is running.

4️⃣ The IPO window is insiders exiting at peak valuation. Sell on day one.

5️⃣ Relationships compound. Start before you think you need to.

The technology survives the valuation. It always has. The question is what you paid to hold it while the market caught up.

If this saved you 2 hours, share it with one founder or investor who needs to see it.

Further reading

The AI macro and capital cycle

▫️ Dario Amodei named “the zeroth world”

▫️ Marc Andreessen on why the AI moat is not the model

▫️ Mark Cuban on the AI thesis

▫️ Anthropic is closing in on a $1 trillion valuation

▫️ Anthropic just passed OpenAI in revenue, spending 4x less

▫️ Coatue’s 18-chart AI report

The AGI countdown across labs

▫️ Demis Hassabis named his AGI year

▫️ Sam Altman watched 900 million people talk to one personality every week

▫️ Dario Amodei and the long game of safe AI

▫️ Elon Musk and the outer limit of vertical integration

The personal AI moat stack

▫️ Your voice is the only AI moat that compounds

▫️ I built a $0 second brain with Obsidian + Claude

▫️ I built a second brain in 10 minutes with Granola + Claude

▫️ Build your own stock analyst with Claude

▫️ 25 Claude Skills that give your startup a marketing team

The investor and fundraising playbook

▫️ What top-tier VCs actually look for in 2026

▫️ What top VCs check in due diligence

▫️ The U.S. VC database most founders never find

▫️ The angel investors SaaS database for 2026

▫️ The ultimate investor list of lists

▫️ The most valuable VC-backed startups in the world

It is called The Price of Meaning. It is a formal proof that the entire class of AI memory systems most teams are building on right now is broken at the foundation.

Every retrieval-augmented generation pipeline. Every vector database. Every agent whose memory is based on embedding proximity. The proof shows that the same geometry that lets them work at small scale forces them to forget at large scale, and to invent things they were never told

The bigger the memory, the worse it gets.

That detail matters, because every founder reading this is building toward the moment the memory needs to be big.

The agent that worked beautifully on 100 documents starts hallucinating on 10,000. The customer-support bot that nailed every query in beta starts inventing policies in production. The research assistant that synthesized perfectly across 50 papers starts citing studies that exist only in its head when you give it 5,000.

This is a topology problem. And the teams that internalize it before the rest of the market are the ones who ship reliable agents in 2026.

This article is the 30-step playbook to be one of them.

The math

If you ship one AI agent into production this year, the cost of getting memory architecture wrong looks like:

▫️ Engineering time debugging hallucinations: $30K+ per year, per agent

▫️ Lost customer trust from agent errors: unmeasurable, but a permanent multiplier on churn

▫️ Re-architecting at scale once you hit Series A or B: $200K+ in dev time

▫️ Compute on bloated vector stores: $15K to $50K per year

That is roughly $250K of exposure per AI product before you count brand damage.

Your investment in the fix: the architecture below. Open source. Most of the pieces you already have.

One weekend of redesign protects you from a quarter of engineering budget burning on the wrong abstraction.

For the production discipline this builds on, see Claude and Anthropic library and the Business and Investing library.

The free section ends here.

Below the paywall:

the 6 architectures that replace broken vector memory, the 12 copy-paste prompts that constrain Claude into structured output (zero fabrication by construction), the schema-as-fibration pattern that gives you one source of truth across retrieval, generation, and validation, the 4 verification loops that catch fabrications before they ship, the 30-day rollout, and the 6 failure modes that kill 80% of agent rebuilds.

Plus the entire AI Corner premium archive:

▫️ Claude and Anthropic library — every breakdown on the company, the models, the releases

▫️ Prompting and Context Engineering library — every prompt playbook, every framework

▫️ AI Agents library — every agent build, every architecture, every system

▫️ AI Tools and Models library — every tool comparison, every workflow

▫️ Business and Investing library — every thesis, every market breakdown

▫️ Your voice is the only AI moat that compounds

▫️ I built a second brain in 10 minutes with Granola + Claude

▫️ I built a $0 second brain with Obsidian + Claude that compounds for life

▫️ Build your own stock analyst with Claude: 12 prompts replace a $250K Bloomberg terminal

▫️ The Claude Code system that replaces a 5-person team

▫️ 25 Claude Skills that give your startup a marketing team , etc….

Every breakdown. Every playbook. Every prompt library.

Try premium free for 7 days. Or get 50% off this week only:

Get 50% off forever

🔒 THE FULL CONTEXT AS TOPOLOGY PLAYBOOK (PREMIUM)

Everything below is operational. Read it once. Adapt to your stack. Ship by Sunday:

Read more