PJFP.com

Pursuit of Joy, Fulfillment, and Purpose

Tag: vertical integration

  • The AI Industrial Revolution: Naval, Guillermo Rauch, Blake Scholl, and Max Hodak on Software Factories, Vibe Coding Hardware, AI Regulation, Healthcare Economics, and What Humans Can Uniquely Do

    This is the full episode of Naval Ravikant’s conversation with three frontier founders: Guillermo Rauch of Vercel, Blake Scholl of Boom Supersonic, and Max Hodak of Science. The premise is that all three are building their own factories rather than assembling off-the-shelf parts, so the interesting question is not what they are building but what they are learning about how to build in the age of AI. Over roughly an hour the discussion moves from software factories and the thousand-x engineer into hardware, regulation, healthcare economics, autonomous companies, and a long closing argument about what humans can still uniquely do. Watch the full conversation on the Naval Podcast YouTube channel. We previously published two segments of this same discussion: part one, Waste Tokens to Save Time, on software factories and whether pure software is dead, and part two, Vibe Coding Hardware, on jet engines, vertical integration, and China’s open-source bet. This post covers the entire episode end to end.

    TLDW

    Four builders argue that AI has turned the engineer’s job from shipping output into building the factory that produces output, which is why token leaderboards are the new vanity metric and why you should waste tokens to save time. Guillermo Rauch frames the thousand-x engineer and the building-block economy, and asks whether pure software is dead now that models speak English. Blake Scholl shows how Boom turned hardware engineering into software, letting two engineers design an entire jet engine and collapsing months of regulatory compliance documentation into minutes. Max Hodak makes the case for extreme vertical integration, a captive MEMS foundry, and a sober counter to Silicon Valley deregulation triumphalism: the bottleneck is the voters and the regulator’s asymmetric incentives, not just bad rules. The group works through healthcare as a fixed-bucket non-market, China’s cost-reduction strategy and its approved implantable brain interface, autonomous software that runs site reliability and security research with thousands of concurrent agents, a company-wide hackathon where the receptionist shipped a real automation, and a long debate on creativity, out-of-distribution surprise, intent, attribution, and the definition of art. The throughline: humans become verifiers, value moves to creativity, taste, and agency, and the single best move is to get extremely good with the tools, because it is people with AI versus people without AI.

    Thoughts

    The strongest idea in the episode is the quiet redefinition of what an engineer is for. Rauch’s point is that you no longer judge a person by how well they ship a single output. You judge them by whether they can build the factory that produces outputs B through Z. That reframe instantly explains why token leaderboards are nonsense. Counting tokens consumed is the same category error as counting lines of code written, a measure of motion mistaken for a measure of progress. Naval’s “waste tokens, save time” is the correct response: tokens are cheaper than people, so optimize for your own wall-clock time and the final output, and throw three models at the same problem if that gets you unstuck faster. The uncomfortable corollary, which the group says out loud, is that leverage in idea domains was never linear. The hundred-x and thousand-x engineer is not a new phenomenon. AI just made it impossible to keep pretending otherwise.

    The second thread that ties the whole hour together is verification. Everyone converges on the same future: humans stop producing the work directly and move up the stack to signing off on it. Rauch is precise about what that means. Saying “I understand this pull request” no longer requires reading every line. It requires being able to say you wrote the test harness, the proofs, the type checkers, and the simulations that let you stand behind it in production. That is a profound shift, because it accepts that the code may be spaghetti you do not fully understand while insisting that the evaluator around it is trustworthy. Blake extends the same logic to regulation, and this is the most underrated argument in the episode. If you treat a 200-page lightning-strike compliance document as a test suite and a regulation as an exit criterion for an agent loop, then a body of rules you once resented becomes a guard rail that lets you move faster, not slower. The cost of change collapses, change aversion drops, and you can finally afford to iterate on physical things.

    Max Hodak is the adult in the room on regulation, and the episode is better for it. The Silicon Valley consensus is that regulation is simply friction to be deleted, and there is plenty of dysfunction to point at: the NRC permitting essentially zero nuclear plants for decades, the FDA’s asymmetric incentives where approving a bad drug ends a career but blocking a good one costs nothing visible. But Hodak keeps pulling the conversation back to the harder truth. This is where the voters are. If you removed the current regulatory package, something very similar would get voted right back in, because the asymmetry reflects how the public actually weighs a visible death against an invisible delay. Real reform is not “deregulate,” it is narrow and surgical: prohibit the FDA from drawing adverse inferences across different users of a compound, build innovation zones where people consent to different rules, or copy Europe’s notified-body model so review capacity can actually scale. That is a far more serious position than the usual abundance-or-bust framing.

    The healthcare segment is the part of this conversation you will not find in the two clips, and it is the most heterodox. Hodak’s diagnosis is that healthcare is a fixed bucket of money that grows with tax receipts, not a technological growth industry where falling prices expand the market the way phones and laptops did. Because there is no real private market, you get a small communist society running inside a larger capitalist one, with the waiting lines and frozen product quality that implies. His prescription is not single payer and not insurance reform. It is to drive the cost of bringing devices and drugs to market so low that a patient can buy a restored sense or an extra decade of life on a credit card, the way they finance a car, and his warning is that China’s lower approval costs and its already-approved implantable brain interface put it on track to do exactly that. Whether or not you buy the twenty-percent-of-income deductible he floats, the framing that a private market is the missing feedback loop is the kind of argument that gets too little airtime.

    The closing debate on creativity is where the four of them disagree most productively, and they are careful enough to notice that their conclusions follow from their definitions. Hodak defines art as meaningful out-of-distribution behavior, which lets a military maneuver or a math proof count, and leads him to think a sufficiently capable model gets there too. Naval defines art as conveying an emotion with intent, which makes attribution load-bearing: the same photo down to the last pixel means more when a human took it, and a startup doing hardware attestation of human authorship suddenly has a real market. The shared observation that should worry every builder is that AI output collapses to a distribution mean. Every Claude-built website ends up the same serif font, the same brown and cream, the same monospace spacing, recognizable as slop precisely because it is in-distribution. The optimistic read, and the one Naval lands the episode on, is that this leaves an enormous and durable lane for humans who can step outside the system, and that the practical move for everyone is simply to become excellent with the tools, because the real divide is people with AI versus people without.

    Key Takeaways

    • The job of an engineer has shifted from shipping a single output to building the factory that produces multiplicative outputs, so people are now judged on the leverage they create rather than the work they personally do.
    • There were always 10x engineers, and in idea, intellectual, and digital domains the real spread is 100x or 1000x. AI leverage just made that gap impossible to deny.
    • Token leaderboards and token consumption are the new lines-of-code: a measure of activity that does not map to value. Measure your own time and the final output instead.
    • Waste tokens to save time. Models are still far cheaper than a human, so throwing Codex, Claude, and Gemini at the same problem repeatedly is rational even when it looks wasteful.
    • Low-quality first-pass code is fine because you can spend more tokens later to harden it for production. The constraint is verifiable domains, not code quality.
    • A model is roughly as good as you are in a domain. The quality of your prompting and reprompting strongly determines the output, though this dependence should fade as models improve.
    • Models graduated from junior to principal engineers: they now return with multiple routes and tradeoffs rather than running away with the first idea, even if their time and cost estimates are often wrong.
    • A junior gets knowledge they could never have produced alone, but an experienced architect still extracts far more juice. Taste and judgment, like picking Postgres versus ClickHouse, remain the human’s edge.
    • Pure software’s moat is in question now that models speak fuzzy, sloppy English. For hardware founders this is a boon, since good software finally becomes cheap to produce.
    • The building-block economy, from Mitchell Hashimoto, argues agents need powerful reusable infrastructure rather than reinventing queues and databases every time. Shared dependencies are a cooperation value, like everyone depending on the same Postgres version.
    • Naval and Max both stopped writing code for years, then started building software they use daily through agents, on the strength of understanding how the pieces fit rather than syntax.
    • With agents you stop getting stuck on narrow debugging problems that used to consume indefinite time. The intrinsic frustration that was once “how you learn” is largely gone.
    • Boom turned siloed hardware engineering, much of it trapped in Excel and VBScript with no source control, into real software with automated testing and repeatable flows.
    • Software engineers now build the architectures and hardware engineers vibe code their pieces, letting two engineers design an entire jet engine where a single turbine-blade analysis once took one engineer a full day across a thousand blades.
    • Enterprise collaboration software and even spreadsheets are getting cooked, because you can now code the exact custom tool you need instead of approximating it.
    • AI will soon generate step files and PCB layouts, bringing the current software boom to mechanical and electrical engineering, likely within the year.
    • China is betting on open-source models because its hardware and supply-chain superiority pairs with on-demand software generation to erase Silicon Valley’s software advantage. Fall behind on generating software and you fall behind on generating everything.
    • In real usage, frontier intelligence dominates the top. Gemini “slaps at scale” as an industrial production model for support and browser automation, while Chinese models are not in the frontier coding tier.
    • Intelligence is an unalloyed good. Because mistakes are invisible and models are cheaper than people, you reach for the smartest available model rather than running a weaker one many times.
    • Max’s vertical integration thesis: when you cannot buy a part, you make it. Science owns a captive MEMS foundry because tighter integration toward a single block of bonded matter yields lower power, smaller size, and longer life.
    • AI’s biggest near-term impact inside hardware companies is regulatory: generating documentation and tracing which of thousands of ISO standards apply, work that used to occupy a quality team for months.
    • Junior engineers got promoted to senior and junior engineering got handed to agents. The same pattern hits law, where basic NDAs and red lines no longer require a lawyer.
    • Humans are becoming verifiers. Signing off on a PR means standing behind its consequences via tests, proofs, and type checkers, not reading every line. Creating software is easy; keeping it secure, tested, and maintained 1000 days out is the real question.
    • A RAG over regulatory documents collapses a 200-page compliance test plan from months to minutes, which cuts change aversion: you can alter the airplane and regenerate compliance instead of crying over rework.
    • Regulations can act as a test suite and exit criteria for agent loops, as long as they are non-contradictory and reasonable. The alternative is shipping slop directly into the air.
    • Physical building is guilty until proven innocent, illustrated by the absurdity of pre-filing a driving plan before every trip. The fix is more enforcement-based regulation rather than pre-approval, though agents on both sides could trigger a red queen race and DDoS overwhelmed agencies.
    • Regulation often fails to make things safer, only slower: the 737 Max shipped a single sensor with full authority over pitch, and the NRC kept us perfectly safe by approving almost no nuclear plants for decades.
    • The deeper problem is the voters and the regulator’s asymmetric incentives. Approve a bad thing and your career ends; block a good thing and nobody notices. Removing one agency just elects its replacement.
    • Targeted fixes beat blanket deregulation: bar adverse inferences across users of a compound, use single-patient IND pathways, create opt-in innovation and YIMBY zones, or adopt Europe’s competitive notified-body reviewers.
    • Healthcare is a fixed bucket of money tied to tax receipts, not a growth industry, so spending 10x more on it would be a catastrophe rather than a triumph. With no private market you run a small communist society inside a capitalist one.
    • The escape is lower cost-to-market, not single payer, so people can finance care like a car. China’s lower approval costs and its already-approved implantable BCI point that direction. LASIK, dental, and plastic surgery advance because patients pay directly.
    • End-of-one medicine works at the high end, as with GitLab’s Sid Sijbrandij outliving his cancer prognosis through a self-built escalation ladder, but it demands enormous agency at the patient’s weakest moment. AI should democratize that knowledge.
    • Vercel automated much of site reliability engineering: anomalies fire alerts, an agent investigates, can open an incident, and begins remediation, stopping just short of changing production itself.
    • Running an open-sourced security tool against the whole monorepo with 10,000 concurrent agents produced several quarters of security research in a couple of days for about $14,000 in tokens. Code translation and optimization are similarly autonomous now.
    • Blake stopped all project work for a week and had everyone, receptionist to engineers, build something with AI and demo it. He expected mostly silly projects and got mostly needle movers, including a real automation from shipping and receiving.
    • The autonomous company of the future may have a workforce that trains the agents doing the work rather than doing it directly, with tooling that extracts reusable skills from your inputs and outputs.
    • Returns are shifting from intelligence toward agency for humans, since agents supply the intelligence. The people best fit for the future open a coding agent and ask what to build instead of defaulting to passive consumption.
    • Maybe 10x more people are coding than a year ago, yet around 99% still never will, because to a non-coder the starting step remains unimaginable. Vibe coding is described as more addictive and entertaining than video games, with real output.
    • AI video lacks taste and judgment for now, but by 2030 expect fan-made films: dozens of Lord of the Rings takes, or generating unmade seasons of The Expanse from the books. The bigger prize is a genuinely new imaginative work, not a remix.
    • What humans uniquely do is generate meaningful surprise out of the training distribution, with intent that makes it mean something. Gödel stepping outside the formal system is the archetype; Claude’s identical-looking websites are the counterexample of in-distribution slop.
    • Higher productivity historically means you hire more, not fewer, of the productive people. Expect a larger number of smaller teams, an entrepreneurship explosion, and generalists winning as credentials matter less than creativity, taste, and judgment.
    • The throughline is people with AI versus people without AI. The single best investment right now is getting genuinely good with the tools and learning the exact edges of what they can and cannot do.

    Detailed Summary

    Software Factories and the Thousand-X Engineer

    Guillermo Rauch opens with the idea that has him “pilled”: the engineer’s job has changed from shipping output directly to building the factory that produces multiplicative outputs. That reframes how you evaluate people and surfaces an old, controversial truth. He used to get flamed on Twitter for asserting 10x engineers, since it offends an equality instinct, but in intellectual and digital domains the real spread is 100x or 1000x, and choosing the right thing to work on is an infinite multiplier on top. AI leverage makes this less controversial, except that people now confuse token spend for productivity. The group agrees token leaderboards are the new lines-of-code. Max Hodak adds that a model is about as good as you are in a domain, so a capable developer gets a powerful collaborator while a junior gets junior-grade help, and the sporadic feedback you give, the reprompting, disproportionately determines the result. Naval’s posture is the opposite of fussy: he ignored every prompt-engineering trick on the bet that the models would improve faster than he could learn to game them, types less and less, and brute-forces problems by throwing multiple models at them. Waste tokens, save time, because tokens are cheaper than people.

    Is Pure Software Dead, and the Building-Block Economy

    Rauch describes models crossing from junior to principal engineer: they now return with several routes and explicit tradeoffs, push back when you try to jam high-cardinality telemetry into Postgres, and suggest ClickHouse or Athena instead. That elevates taste and judgment as the human contribution. He then poses the hard question: is pure software engineering obsolete now that models speak fuzzy, sloppy English and you no longer need code to communicate with them? For hardware founders it is a boon, echoing Patrick Collison’s line that software is art and artists are hard to hire. To temper the “agents reinvent everything” fantasy, he invokes Mitchell Hashimoto’s building-block economy: you do not want your agent rebuilding a queue from first principles every time it sends an email, and shared dependencies like a common Postgres version carry real cooperation value. Reusable infrastructure becomes more valuable in the agentic era, functioning like libraries and dependencies, or even a token cache, so models fork from existing starting points instead of burning a trillion tokens to recreate what exists. Naval and Max both note they had not written code in years and now build daily through agents, because understanding how APIs, data flow, and performance fit together matters more than syntax, and vibe coding is just transmitting intent the way a good engineering leader already did through people.

    Vibe Coding Hardware at Boom Supersonic

    Blake Scholl explains how AI changed the role of software and hardware developers at Boom. A great deal of hardware engineering lives in complex Excel spreadsheets and VBScript on individual laptops, with no source control and no automated testing, and handoffs happen manually over email like it is the 1990s. Boom had long tried to turn these flows into real software but could never afford enough software engineers. The new model is that software engineers create the architectures, because they understand systems, algorithms, and separation of concerns, and hardware engineers vibe code their own pieces. The result is mind-blowing productivity for small teams. His example: a turbine blade is cold at rest and expands when hot, so you must design both the cold and hot shapes and convert between structures and aerodynamics, work that took one engineer a full day per blade across a thousand blades in a jet. With a combined software-and-hardware tool you can now change blade geometry and see structural and aerodynamic results in real time, letting two engineers design an entire jet engine. The group extends this to the death of enterprise collaboration software and even spreadsheets, since you can now code the exact custom tool you need, and predicts AI will soon generate step files and PCB layouts, carrying the boom into mechanical and electrical engineering.

    China, Open Source, and Which Models Actually Get Used

    Naval argues China is going all-in on open-source models because its hardware and supply-chain superiority pairs naturally with on-demand software generation, which erases Silicon Valley’s software edge, and because the Chinese government has a history of funding ecosystem-wide efforts in network-effect businesses. Without frontier coding models there is no self-improvement, so a country that cannot generate frontier software falls behind on generating everything downstream. He notes the irony that almost all the open-source heft now comes from China, since OpenAI is not open, Grok and Google’s local models trail, and Anthropic ships no open models. On real usage, Rauch reports from Vercel’s AI gateway that frontier intelligence dominates the top, with a caveat: frontier intelligence at the right cost and performance, like Gemini, slaps at scale and is the best industrial production model for support and browser automation, while Chinese models are not in the frontier coding tier. Naval frames intelligence as an unalloyed good, since model mistakes are invisible and a smarter model is still cheaper than a person, which pushes everyone toward the most intelligent option and risks an oligopoly in AI.

    Vertical Integration, Verifiers, and the Slop Problem

    Max Hodak lays out Science’s vertical integration: the preference is always to buy, as with cheap PCBs from Asia, but when components do not exist you must make them, and the closer a product gets to a single block of covalently bonded matter the better it performs. Science owns a captive MEMS foundry on the east coast because there was no other way to do the packaging and assembly it needed. He notes AI’s most surprising internal impact so far is regulatory: generating documentation and tracing which of thousands of ISO standards apply, work that once tied up a quality team for months. Rauch raises the slop problem: mountains of AI-generated code arriving as pull requests nobody can read line by line. His standard is that an engineer must be able to say they understand and will stand behind the consequences of a PR, backed by the test harness, proofs, and type checkers, even without reading it all. Naval generalizes this into humans becoming verifiers, with lawyers, engineers, and operators moving to verifying the stack and standing behind it, and Rauch warns that creating software is the easy zero-to-one part while keeping it secure, tested, performant, and maintained a thousand days later is the real test.

    Regulation as Test Suite, and the Voter Problem

    Blake describes building a RAG that compresses a 200-page lightning-strike compliance test plan from months of a “monkey at keyboard” engineer’s work into minutes, with a powerful second-order effect: change the airplane and you regenerate compliance in minutes instead of crying over months of rework, which slashes change aversion and lets a small number of creative engineers iterate. Max reframes regulations as potentially good guard rails, a test suite and exit criteria for agent loops, provided they are non-contradictory and reasonable, since the alternative is shipping slop into the air. Naval warns of a red queen race of agent-on-agent compliance and agencies getting DDoSed by clever entrepreneurs flooding them with documents. Blake pushes for enforcement-based rather than pre-approval regulation, using the analogy that we would never tolerate filing a driving plan before every trip, yet that is exactly how physical infrastructure works: guilty until proven innocent. He cites the 737 Max’s single all-authority sensor and the NRC permitting almost no nuclear plants for decades as proof that this makes us slower, not safer. Hodak supplies the counterweight: the deeper issue is the voters and the regulator’s asymmetric incentives, where approving a bad thing ends a career and blocking a good thing goes unnoticed. Remove an agency and the electorate installs its twin. Naval and Max agree the real reforms are narrow, including innovation zones, opt-in YIMBY zones, and the experimental laboratory of fifty states.

    Drug Discovery, Healthcare Economics, and End-of-One Medicine

    Hodak explains why innovation zones do not solve drug discovery. The right-to-try act and single-patient IND already exist, and the FDA approves over 99% of such requests, sometimes by phone, but dosing requires clinical-grade drug that only the IP owner has, and the FDA will draw an adverse inference against the whole program if a very sick patient does worse. A targeted fix is to prohibit adverse inferences across different users of a compound. He points to Europe’s notified-body system, private certifiers blessed by governments, as a way to scale review capacity, and to China’s CFDA, which already approved an implantable brain-computer interface and brings products to market far cheaper. His core economic argument is that healthcare is a fixed bucket of money that grows only with tax receipts, unlike phones and laptops where falling prices expanded the market, so spending 10x more on healthcare would be a catastrophe rather than the triumph that 10x AI spending would be. With no private market you run a small communist society inside a capitalist one, with the lines and frozen quality that implies. The way out is lower cost-to-market so patients can finance care like a car, which is the direction China is pushing. Naval’s twist is a healthcare plan where the first 20% of income is the deductible to recreate a private market, citing LASIK, dental, and plastic surgery as fields that advance because patients pay directly. The group closes the segment on GitLab’s Sid Sijbrandij, who outlived a rare-cancer prognosis by building his own escalation ladder of drugs, noting that end-of-one medicine works at the high end but demands enormous agency exactly when a patient is weakest, which is where AI should democratize access to knowledge.

    Autonomous Software, Hackathons, and the Autonomous Company

    Asked how much autonomous software they run, Rauch describes Vercel automating much of site reliability engineering: instead of hand-set alarm thresholds, anomalies in error rate, latency, or throughput fire an alert, an agent investigates, can open an incident that loops in people, and begins remediation, stopping just short of changing production. Vercel also runs autonomous optimization and security research, and an open-sourced security tool run against the entire monorepo with 10,000 concurrent agents produced several quarters of security research in a couple of days for about $14,000 in tokens, the equivalent of months of red teaming. Max shares a vibe-coded bug-reporting queue where TestFlight users submit logs and screenshots, a daemon analyzes and fixes issues in the background, and ships him a build to try, raising the prospect of apps effectively built by their users, with the caveat that you would get a Homer Simpson car of every feature. Blake recounts stopping all project work for a week and requiring everyone, from the receptionist to the engineers, to build something with AI and demo it. He expected mostly silly projects and got mostly needle movers, including a genuinely useful automation from the shipping and receiving associate, concluding that most people have an idea worth building but cannot tell a good first idea from a bad one until they can iterate on a real thing. Rauch extends this to a workforce that trains the agents doing the work rather than doing it directly, and a coming feature to extract reusable skills from your inputs and outputs.

    Creativity, Out-of-Distribution Surprise, and What Humans Can Uniquely Do

    On the intelligence-versus-agency split, Max suggests returns to humans tilt toward agency since agents supply intelligence, while Naval counters that you stay 99% intelligence and 1% agency because the agents exercise the agency for you. They agree the humans best suited to the future are the agentic ones who open a coding agent and ask what to build. Coding has perhaps 10x more participants than a year ago, yet roughly 99% still never will, because the first step is unimaginable to a non-coder, even as vibe coding proves more addictive and entertaining than video games while producing something real. On AI video, the group notes it still lacks taste and judgment, but expects fan-made films by 2030, dozens of Lord of the Rings takes or generated seasons of The Expanse, while prizing a genuinely new imaginative work over a remix. The long closing debate turns on definitions. Hodak defines art as meaningful out-of-distribution behavior, broad enough to include a military maneuver, and expects models to reach it. Naval defines art as conveying emotion with intent, which makes attribution decisive: the same photo means more taken by a human, and a hardware-attestation startup gains a real use case. They cite Gödel stepping outside the formal system as the human archetype and the identical look of every Claude-built website as in-distribution slop. Naval lands the episode on optimism: productivity gains mean hiring more, not fewer, of the creative and AI-fluent, the future is a larger number of smaller teams and an entrepreneurship explosion where generalists thrive and credentials fade, and the single best move is to get extremely good with the tools, because it is people with AI versus people without AI.

    Notable Quotes

    “Now clearly there’s 100x or a thousandx engineers and the world hasn’t fully adjusted to this.”

    Guillermo Rauch, on why AI made the spread between engineers impossible to ignore

    “Just waste tokens, save time. Don’t look at the tokens either as inputs or outputs. Just look at your time and look at the final output.”

    Naval Ravikant, on the right way to measure AI’s return

    “We had to learn code to communicate with the models. Now the models speak English and they speak fuzzy sloppy English like a human and they understand things.”

    Guillermo Rauch, asking whether pure software engineering is now obsolete

    “It allows two engineers to design an entire jet engine, which is just wildly different.”

    Blake Scholl, on Boom turning hardware engineering into software

    “You need to be able to say I am signing off on understanding the consequences of this PR.”

    Guillermo Rauch, on what it means to stand behind code you did not read line by line

    “That is absolutely the way we build physical infrastructure in this country. It’s guilty until proven innocent. And what we should actually do is make more of these things enforcement based rather than pre-approval based.”

    Blake Scholl, comparing the permitting process to filing a driving plan before every trip

    “You’re basically running a small communist society inside a larger capitalist society. And that’s what we’re doing in healthcare.”

    Max Hodak, on why there is no real private market in healthcare

    “I expected we would get a large number of silly projects and a small number of needle movers. And what we got was a large number of needle movers and a very small number of silly projects.”

    Blake Scholl, on the week he had the whole company build with AI

    “If a person takes the photo versus AI generates the exact same photo down to the last pixel, the person taking the photo will have more meaning for me.”

    Naval Ravikant, on why intent and attribution make something art

    “It’s about people with AI versus people without AI. And so the single best thing you can be doing right now for yourself is just getting really good with these tools.”

    Naval Ravikant, closing the conversation on the only divide that matters

    Watch the full conversation here: The AI Industrial Revolution on the Naval Podcast YouTube channel.

    Related Reading

    • Part one: Waste Tokens to Save Time, our writeup of the first segment, on software factories, the thousand-x engineer, token leaderboards, and whether pure software is dead.
    • Part two: Vibe Coding Hardware, our writeup of the second segment, on AI-designed jet engines, vertical integration, China’s open-source bet, and humans as verifiers.
    • Naval Ravikant’s official site, the canonical home for Naval’s essays and podcast on technology, judgment, and leverage.
    • Boom Supersonic, Blake Scholl’s company building supersonic aircraft and its own jet engines, source of the turbine-blade and two-engineers example.
    • Science Corporation, Max Hodak’s brain-computer interface company, whose captive MEMS foundry and FDA arguments anchor the hardware and healthcare segments.
    • Vercel, Guillermo Rauch’s company, whose AI gateway data and autonomous SRE work inform the usage and automation discussion.

  • Vibe Coding Hardware: Naval, Guillermo Rauch, Blake Scholl, and Max Hodak on AI-Designed Jet Engines, Vertical Integration, China’s Open-Source Bet, and Why Humans Become Verifiers

    This is part two of Naval Ravikant’s conversation with frontier founders Guillermo Rauch of Vercel, Blake Scholl of Boom Supersonic, and Max Hodak of Science. Where the first part argued that you should waste tokens to save time and that the job of an engineer is now to build the factory rather than the output, this segment drags that thesis out of pure software and into atoms. The question on the table is what happens to hardware when models can vibe code the spreadsheets, the simulations, and eventually the step files and PCB layouts that aerospace, semiconductors, and biotech are built on. This segment is one half of the discussion, and you can watch and read the full episode here. The full conversation is on the Naval Podcast YouTube channel.

    TLDW

    Blake Scholl describes how Boom Supersonic took hardware engineering workflows that used to live in siloed Excel spreadsheets and VBScript on individual laptops, with handoffs done by email like it was the 1990s, and turned them into versioned, testable software. The new model is that software engineers build the architectures and the tools while hardware engineers vibe code their own domain-specific pieces, which collapsed a turbine-blade analysis that once took one engineer one day per blade into something where two engineers can design an entire jet engine in real time. Naval generalizes this into the cataclysm of enterprise software: there is no longer a startup that can sell you hardware collaboration tools because companies just code the exact thing they need on demand, and even spreadsheets are cooked because they only existed as a proxy for custom software nobody could previously afford to build. Blake predicts that within 2026 AI will move from generating software to generating step files and PCB layouts, which reshapes mechanical and electrical engineering. The group debates China’s open-source push as a way to neutralize Silicon Valley’s software advantage and protect its hardware and supply-chain superiority, lands on the point that if you fall behind on generating software you fall behind on generating everything, and Guillermo notes that frontier coding intelligence still dominates real usage while cheaper models like Gemini win at scale for support and browser automation. Max Hodak explains Science’s vertical integration, including a captive MEMS foundry on the East Coast, because the most innovative hardware cannot be bought off the shelf, and argues that software still needs hands since a model that cannot make physical things hits real boundaries. The conversation closes on the shift from writing to verifying: junior engineering got absorbed by agents while juniors got promoted, the same way paralegals could be seen as fired or promoted, and humans across law, engineering, and operations are becoming the verifiers who sign off on systems they did not write line by line.

    Thoughts

    The most important shift in this segment is that vibe coding stops being a software-industry story and becomes a deep-tech story. In part one the examples were Postgres, ClickHouse, and deploy targets. Here Blake Scholl is talking about turbine blades that change shape when they heat up, and the brutal fact that converting between cold and hot geometry, and between aerodynamics and structures, used to eat one engineer for one full day per blade in an engine that has a thousand blades. That is the kind of math that quietly kills ambition. When he says two engineers can now design an entire jet engine because the structural and aerodynamic results update in real time as you change the geometry, that is not a productivity improvement, it is a change in what a small team is allowed to attempt. The interesting move is the division of labor: software engineers build the architecture and the framework because they understand systems and separation of concerns, and the hardware engineers vibe code the pieces only they understand. Nobody has to become both.

    Naval’s “cataclysm of enterprise software” is the most investable idea in the episode, and it is darker than it sounds for anyone selling B2B tools. His claim is that the entire category of internal collaboration software is being eaten from the inside, because a company that can generate exactly the tool it needs on any given day will not pay a vendor for an approximation of that tool. His follow-on that even spreadsheets are cooked is the sharpest version of the point. The spreadsheet won for forty years precisely because it was the closest thing to custom software that a non-programmer could produce. Remove the constraint that custom software is expensive and the spreadsheet loses its reason to exist. The counterweight, which the group raised in part one with the block-economy thesis, is that the infrastructure primitives agents reach for get more valuable, not less. So the safe place to build is not the collaboration layer on top, it is the primitive underneath.

    The China discussion is the geopolitical center of the conversation and it lands on a genuinely uncomfortable insight. The argument is that China leans into open-source models not only because it is a model or two behind, but because open weights neutralize Silicon Valley’s software advantage and let China lean on what it already dominates: hardware, supply chains, and component ecosystems. If software can be generated on demand from open models, then the country with the factories wins the stack. The sharpest line is that if you fall behind on the ability to generate software, you fall behind on the ability to generate everything, because software is now upstream of every hardware pipeline. That reframes the open-versus-closed debate as a question about who controls the means of producing the means of production. It also quietly flatters the American frontier labs, since the same logic says self-improvement requires frontier coding models, and on that narrow axis the consensus at the table is that the Chinese models are not yet in the race.

    Max Hodak provides the necessary cold water, and it is the most grounding contribution in the episode. Everyone else is describing software eating the design layer, and Max points out that you still have to make the thing. Science owns a captive MEMS foundry on the East Coast not as a flex but because there was no other way to do the packaging and assembly for products that approach a single block of covalently bonded matter. His framing that the software still needs hands is the real boundary condition on all the AI-eats-everything talk: a model can be smarter than every engineer in the building and still be unable to deposit a layer, bond a wafer, or pass a regulatory inspection. The optimistic version, which he also makes, is that he has instrumented the foundry so that as models improve, the gains show up immediately in cell engineering and material science. The pessimistic reading is that the physical world remains a hard rate limiter, and the companies that own the atoms will capture more of the surplus than the companies that only own the bits.

    The closing thread on verification is where the whole conversation resolves into a job description for humans. Guillermo’s point that the biggest problem in software is mountains of slop arriving as a pull request, and that the answer is not pretending to read every line but being able to say “I am signing off on the consequences of this PR, and I wrote the harness, the simulations, the proofs, and the type checkers that let me,” is the most practically useful idea in the episode. It generalizes cleanly. The lawyer you trust is not the one who wrote every clause by hand, it is the one putting their reputation on the line that the document is sound. The production engineer who gets paged at 3am is the one signing off that the system is safe to ship. As models absorb the junior tier of every knowledge profession, the surviving human role is the verifier who carries the accountability. That is a promotion for the people who can hold it and an extinction event for the people whose value was doing the work nobody now needs done by hand.

    Key Takeaways

    • The factory framing from part one carries straight into hardware: you are judged on whether you build the system that produces multiplicative outputs, not on the single artifact, and the real multiplier was always 100x or 1000x, not 10x.
    • AI completely changes the role of software and hardware developers rather than just speeding either one up.
    • A huge amount of hardware engineering lives in complex Excel spreadsheets and VBScript on individual engineers’ laptops, with no source control, no automated testing, and handoffs done manually over email. It is software that is not treated as software.
    • Boom Supersonic’s move from day one was to turn traditional hardware engineering workflows into real software frameworks that are automatable and repeatable, to drive down the cost of iteration.
    • The old bottleneck was never being able to afford enough software engineers to build those frameworks. AI removes that constraint.
    • The new model: software engineers create the architectures because they understand systems, algorithms, and separation of concerns, and hardware engineers vibe code the domain pieces only they understand.
    • A turbine blade is cold when it starts and hot when it runs, so it changes shape, and you must design both the cold and hot geometry across aerodynamics and structures. Classically that was one engineer, one day, for one blade, in an engine with a thousand blades.
    • With software and hardware people combined, you can now change blade geometry and see the structural and aerodynamic results in real time, which lets two engineers design an entire jet engine.
    • Naval’s cataclysm of enterprise software: no startup can sell hardware collaboration tools anymore because companies just code the exact thing they need at any given time.
    • Even spreadsheets are cooked. Spreadsheets won only because nobody could build custom software, so a spreadsheet full of VBScript was the closest available approximation. Remove the cost barrier and the approximation loses.
    • Engineers are moving from Excel to Python models that produce believable simulations of physical systems.
    • AI can generate software today, but within 2026 it is expected to generate step files and PCB layouts, which opens up mechanical and electrical engineering as the next frontier.
    • The hardware software boon is biggest for small gadget and parts companies that historically shipped bad software because they could not afford good software. Now they can ship good-enough software, or skip the human front end entirely and expose hardware agentically for voice and agent control.
    • China goes all in on open-source models partly to neutralize Silicon Valley’s software edge: if software can be generated on demand from open weights, China’s hardware and supply-chain superiority stops being offset by a software disadvantage.
    • Other reasons cited for China’s open-source push: it is a model or two behind, it is distilling models, and the government has a history of funding efforts that lift the whole ecosystem, especially in network-effect businesses.
    • Open-source heft is coming almost entirely from China. OpenAI is not open, Grok publishes models but is seen as a model or two behind, Google’s local models are not very competitive, and Anthropic is not known for open-source releases.
    • Without frontier coding models you do not get self-improvement, and if you fall behind on generating software you fall behind on generating everything, because software now sits upstream of every hardware pipeline.
    • Real AI gateway usage shows open models do get used, but the top is heavily dominated by frontier intelligence.
    • Frontier intelligence at the right cost and performance slaps at scale. Gemini models are underrated and excel as industrial production models for support tasks and browser automation, even if they are not the top pick for coding.
    • For pushing the frontier you need the best possible coding model, which is now only two or three models, and the Chinese models are not among them.
    • One contrarian view at the table: use DeepSeek for 97% of tasks because it is cheap, run it repeatedly for harder problems, and reserve frontier models for the most advanced work. The counterargument: intelligence is an unalloyed good, mistakes are invisible and costly, and a smarter model is always cheaper than a person, so you default to the most intelligent option.
    • Always wanting the most intelligent model risks creating a monopoly or oligopoly in AI, because when two models disagree you cannot tell which is right, so you trust the smarter one and stop asking the weaker one.
    • Vertical integration is forced, not chosen: if you cannot buy it, you have to make it. The preference is always to buy when a vendor offers a service at a great price, like PCBs from Asia.
    • The closer a product gets to a single block of covalently bonded matter, the better it performs: lower power, smaller, higher performance, longer lasting. The components for that level of integration simply are not available to buy.
    • Science owns a captive MEMS foundry on the East Coast, bought because there was no other way to do the packaging and assembly the company needed.
    • One of the biggest near-term AI impacts inside hardware companies is regulatory and documentation work: tracing which of thousands of ISO standards apply used to occupy a regulatory and quality team for months, and now AI just knows.
    • Software still needs hands. A model can be smarter than us and still hit real boundaries if it cannot physically make things, which is why Science has instrumented its foundry so model improvements show up immediately in cell engineering and material science.
    • Basic legal work is already going away. People have stopped asking lawyers for NDAs and routine agreements, because law is spaghetti code in English with no real APIs, and the basic tasks are handled by AI.
    • Junior engineers got promoted to senior engineers while junior engineering itself got taken over by agents. The same framing applies to paralegals: fired, or promoted to senior lawyers who now spend their time thinking about the law.
    • What you value in a lawyer is a trusted authority who puts their reputation on the line, not someone who read every clause. The same trust model is coming to engineering.
    • The biggest problem in software engineering today is mountains of slop arriving as a pull request. The old norm of reading every line of a PR is gone.
    • The new standard is being able to say “I understand and I am signing off on the consequences of this PR,” backed by the test harness, simulations, proofs, and type checkers you built, even without reading every line.
    • Embrace a world where code is spaghetti you do not fully understand, but build the evaluators that give confidence, and rely on production engineers to sign off because someone gets paged if the system goes down.
    • Creating software is easy from zero to one. The hard part is a thousand days from now: is it secure, tested, production grade, and performant, and are you still motivated to invest the tokens to maintain it in prod?
    • Humans are becoming verifiers. The same way models are trained on good verification data, the old functions of lawyers, engineers, and operations people are moving to verifying the stack and standing behind it.

    Detailed Summary

    Turning Hardware Engineering Into Software

    Blake Scholl opens by describing how AI completely changes the role of software and hardware developers at Boom Supersonic. From day one the company tried to take traditional hardware engineering workflows and turn them into software. For anyone who has not been around hardware engineering, he explains that an enormous amount of it happens in complex Excel spreadsheets on individual engineers’ laptops, sometimes with VBScript code, all of which is actually software but is not treated as software. There is no source control, no automated testing, and when an aerodynamicist hands work to a structures engineer it is done manually with a spreadsheet over email, like it is the 1990s. Boom started building software frameworks to automate and make those flows repeatable so the cost of iteration would drop, but progress was slow because the company could never afford enough software engineers.

    Two Engineers, One Jet Engine

    The mind-blowing change, in Blake’s words, is a new division of labor. Software engineers create the architectures because they understand systems, algorithms, and separation of concerns, and then hardware engineers vibe code the pieces that draw on what they uniquely know about hardware. The result is wildly different productivity for small teams. His example is the turbine blade: it starts cold and gets bigger as it heats up in operation, so you have to design both the cold shape and the hot shape, converting between them and between structures and aerodynamics. Classically that was one engineer, one day, for one blade of analysis, in a jet engine with a thousand blades, which means you simply could not do much. Now, with software and hardware people working together, you can change blade geometry and see the structural and aerodynamic results in real time, which allows two engineers to design an entire jet engine.

    The Cataclysm of Enterprise Software

    Picking up on the point that software engineers now build the tools and architectures for everyone else, Naval names what he calls the cataclysm of enterprise software. There is no longer a startup that can build and sell hardware collaboration tools, because internally companies just code the right things they need at any given moment. Even spreadsheets are cooked, he argues, because the reason spreadsheets succeeded is that no one could build custom software, so a spreadsheet stuffed with VBScript functions was the closest available approximation. With that constraint gone, the proxy collapses. He notes he has personally moved almost entirely from Excel to Python models where he can get believable simulations of things.

    Generating Step Files and PCB Layouts

    The next frontier, Blake suggests, is the thing AI has not reached yet but probably will within 2026: today it can generate software, but soon it will generate step files and PCB layouts, and when it comes for mechanical and electrical engineering that will be a whole other thing nobody has seen yet. On the hardware side this is described as a particular boon for the many small gadget and parts companies that historically wrote bad software because they could not make great software. Now they can make good-enough software, or skip a human front end entirely and expose the hardware agentically, so that an agent accesses it and a person controls the hardware by voice.

    China’s Open-Source Bet and Hardware Superiority

    This leads into one of the reasons China is described as going all in on open-source models. With hardware superiority, complex supply chains, and deep component chains, China’s logic is that if it can generate software on demand it no longer suffers a software disadvantage against Silicon Valley. That is framed as not the only reason: China is also a model or two behind, it is distilling models, and the government has a history of funding efforts that lift the entire ecosystem, especially in network-effect businesses. Ironically, the open-source heft comes from China precisely because OpenAI is not open, Grok publishes models but is a model or two behind, Google’s local models are not very competitive, and Anthropic is not known for open releases. The deeper point is that without great frontier coding models you do not get self-improvement, and if you fall behind on the ability to generate software you fall behind on the ability to generate everything, because generating software is embedded in every piece of the hardware pipeline.

    Frontier Intelligence vs. Cheap Models

    Naval raises a dinner-table argument from the night before, where someone claimed you will use DeepSeek for 97% of things because it is cheap, run it repeatedly when you need more intelligence, and reserve OpenAI or Anthropic for the most advanced tasks. Naval pushes back: intelligence is an unalloyed good, you always want more of it, model mistakes are invisible, and a smarter model is always cheaper than a real person in real time, so you default to the most intelligent model available. He notes the downside is that this tends toward a monopoly or oligopoly, because when two models give different answers you often cannot tell which is correct, so you trust the smarter one and gradually stop asking the weaker one. Guillermo confirms with AI gateway data that open models do get used, but the top is heavily dominated by frontier intelligence. His caveat is that frontier intelligence at the right cost and performance slaps at scale: Gemini models are underrated but are excellent industrial production models for support tasks and browser automation, while for pushing the frontier you need the best possible coding model, now only two or three models, and the Chinese models are not in that set.

    Vertical Integration and the Captive MEMS Foundry

    Asked about his push into vertical integration and extreme urgency, Max Hodak explains that for many things you cannot buy what you need, so you have to make it. The preference is always to buy when a vendor offers a service at a great price, and he points to PCBs, which are basically free and available in unlimited quantity from Asia. But the closer a product gets to being a single block of covalently bonded matter, the better it is: lower power, smaller, higher performance, longer lasting. The components for that level of integration are not available, so to innovate beyond piecing together off-the-shelf parts you have to learn to do it yourself, which shows up as vertical integration. Science owns a captive MEMS foundry on the East Coast, bought because there was no other way to do the packaging and assembly work the company wanted.

    Software Still Needs Hands

    Max expects AI to heavily affect all of this over the next few years, though it is not quite there yet. Ironically, one of the biggest impacts already seen is in regulatory interactions and documentation: figuring out which of thousands of ISO standards apply to a product change, and tracing it through, used to occupy a regulatory and quality team for months, and now the AI just knows. But for things like the surgical program or the MEMS fab, he argues the software still needs hands. It will be smarter than us, but if it cannot make things, those are real boundaries. Science has instrumented its foundry and many other parts of the company so that as models get better, the improvement shows up immediately in cell engineering and material science.

    Lawyers, Paralegals, and the Promotion of Junior Work

    The discussion turns to law as a parallel to engineering. It has been a while since anyone at the table generated a basic legal document using a lawyer. Routine work like NDAs and standard agreements is gone, because law is essentially spaghetti code that contradicts itself and has no real APIs, expressed in complicated English. Junior engineers got a promotion to senior engineers while junior engineering itself was taken over by agents, and the same framing applies to paralegals: you can say they were fired, or you can say they were promoted to senior lawyers who now spend their time thinking about the law. What you actually value in a lawyer is a trusted authority who went to law school and puts their reputation on the line when they tell you a document is legit.

    Slop PRs, the Thousand-Day Problem, and Humans as Verifiers

    Guillermo argues the biggest problem in software engineering today is mountains of slop ending up as a pull request. The old meme of reading every line of a PR is gone. In infrastructure he wants engineers to be able to say they understand and are signing off on the consequences of a PR, backed by the test harness, simulations, proofs, and type checkers they wrote, so they have confidence it will be safe in production even without reading every line. There is a world where everyone embraces that the code is spaghetti nobody fully understands, but builds the evaluators that give confidence and relies on production engineers to say it is fine to ship, because someone gets paged if the system goes down. The further warning is that creating software is easy from zero to one, but a thousand days from now you have to ask whether it is secure, tested, production grade, and performant, and whether you are still motivated to invest the tokens to maintain it in prod. The resolution is that humans are becoming verifiers, the same way models are trained on good verification data, and the old functions of lawyers, engineers, and operations people are moving to verifying the stack and standing behind it.

    Notable Quotes

    “What I found is it completely changes the role of software and hardware developers.”

    Blake Scholl, on how AI reshaped engineering at Boom Supersonic.

    “If you want to hand something off from like an aerodynamicist to a structures engineer that’s done manually with like a spreadsheet over email. It’s the 1990s. It’s terrible.”

    Blake Scholl, describing the state of traditional hardware engineering workflows.

    “It allows two engineers to design an entire jet engine, which is just wildly different.”

    Blake Scholl, on collapsing turbine-blade analysis with real-time structural and aerodynamic feedback.

    “Even spreadsheets are kind of cooked, right? Because the reason spreadsheets were successful is that no one could build custom software.”

    Naval Ravikant, on the cataclysm of enterprise software.

    “Right now it can generate software, but soon it’ll be able to generate step files and PCB layouts. And when it comes for mechanical and electrical engineering, that will be a whole other thing that we haven’t seen yet.”

    Blake Scholl, on the next frontier for AI in hardware.

    “If you fall behind on your ability to generate software, you fall behind on the ability to generate everything.”

    Naval Ravikant, on why software now sits upstream of every hardware pipeline.

    “Anytime I’m working to push the frontier you need the best possible coding model, and that’s basically now like two or three models, and the Chinese are certainly not in it.”

    Guillermo Rauch, on where frontier coding intelligence actually lives.

    “You can’t buy it, so you got to make it somehow. The closer that our products get to being like a single block of covalently bonded matter, the better they’ll be.”

    Max Hodak, on why Science is forced into vertical integration.

    “The software still needs hands. It’s going to be smarter than us, but if it can’t make things, then those are real real boundaries.”

    Max Hodak, on the physical limits of AI in hardware.

    “You need to be able to say I am signing off on understanding the consequences of this PR, or I wrote the test harness, the simulations, the proofs, the type checkers, to be able to say even without reading this, I have confidence it’s going to be safe in production.”

    Guillermo Rauch, on what code review becomes in the age of slop PRs.

    “Creating software is really easy 0 to one. But think about a thousand days from now. Is it secure? Is it tested? Is it production grade? And are you still motivated to invest all of those tokens in maintaining it in prod?”

    On the long-term cost of software that is cheap to create and expensive to keep alive.

    Watch the full conversation on the Naval Podcast here.

    Related Reading

    • Full episode: The AI Industrial Revolution, the complete hour-long conversation this clip is drawn from, covering software factories, hardware, regulation, healthcare economics, autonomous companies, and creativity.
    • Part one: Waste Tokens to Save Time, the first half of this same conversation, where Naval, Guillermo Rauch, Blake Scholl, and Max Hodak argue that the job of an engineer is to build the factory and that pure software is not dead.
    • Boom Supersonic, Blake Scholl’s company building supersonic civilian aircraft and its own jet engines, the source of the turbine-blade and two-engineers example.
    • Science Corporation, Max Hodak’s company, whose captive MEMS foundry and surgical program anchor the vertical-integration argument.
    • Vercel, Guillermo Rauch’s company, whose AI gateway data informs the point about frontier intelligence dominating real usage.
    • Microelectromechanical systems (Wikipedia), background on the MEMS technology behind the captive foundry Max Hodak describes.

  • Keith Rabois on How to Operate: A Deep Dive into Startup Success

    TL;DR: In a recent interview on the Alex LaBossiere podcast, Keith Rabois—a titan of startup investing and operations—shared his hard-earned wisdom on building exceptional companies. Despite the video’s horrendous audio quality, the content shines through as a treasure trove of insights. Rabois, a Managing Partner at Khosla Ventures and CEO of OpenStore, draws from his storied career (PayPal, LinkedIn, Square, and early investments in Airbnb, DoorDash, and Stripe) to discuss founder scarcity, vertical integration, talent acquisition, raising capital, and operational rigor. Key ideas include the rarity of world-class founders, the power of vertically integrated solutions, the critical need to identify “barrels” (force-multiplying individuals), and a shift from measuring outputs to inputs for long-term success.

    Detailed Summary

    The Bottleneck to Innovation: Great Founders Are Scarce (1:56)

    Rabois kicks off with a stark reality: the bottleneck to creating more exceptional startups isn’t capital—it’s founders. He likens world-class founders to Major League Baseball pitchers who can throw a 90-mph fastball: only a tiny fraction of people (5-15 per year) possess the “superpower” to bend an industry to their will. This scarcity drives the frenzy among VCs and angel investors chasing the same few visionaries. For Rabois, you either have this innate potential or you don’t—training can amplify it, but it can’t create it from scratch.

    Vertical Integration: The Path to Trillion-Dollar Businesses (4:35)

    Rabois doubles down on his pinned tweet philosophy: target large, fragmented industries with low Net Promoter Scores (NPS) and deliver a vertically integrated solution. Companies like Apple (smartphones) and Tesla exemplify this—by controlling hardware, software, and chips, they create moats competitors can’t breach for decades. Vertical integration demands more capital and talent, but the payoff is a near-unassailable market position.

    The Hollywood Model: Startups Are Invented, Not Discovered (6:24)

    Rejecting the Silicon Valley trope of “talk to users and iterate,” Rabois advocates a “Hollywood model” where startups are forged through vision and willpower. Like producing a movie, you start with a script (your idea), cast the right co-founders to tackle key risks, and execute relentlessly. This contrasts with throwing ideas at the wall—Rabois believes startups succeed by design, not serendipity.

    “Why Now?”: Timing the Wave (7:41)

    The “Why now?” isn’t about being first, but riding an enabling technological or societal shift. Amazon capitalized on the web’s infancy, while Google thrived as the 11th search engine by leveraging a maturing internet. Rabois cites Nvidia’s pivot to AI chips as a masterstroke of spotting a wave others missed—founders must find cracks in inertia to gain momentum without brute force.

    Multi-Product Companies: Opportunistic Growth (9:50)

    Should you plan to be multi-product from Day 1? Rabois says no—it’s usually opportunistic. Start with one killer product, achieve product-market fit, then expand organically as customers demand adjacent solutions. Forcing multiple products to boost economics (e.g., in SaaS) is less compelling than responding to real synergies.

    Iteration vs. Pivots: Stay Grounded (10:58)

    Rabois estimates 70-90% of successful startups he’s backed stuck to their initial risks and ideas by the seed stage. Pivots work, but only if one foot stays planted—like PayPal shifting from Palm Pilot payments to email-based transactions, leveraging its core email identifier concept.

    Picking Co-Founders: Complementary Superpowers (12:52)

    Co-founders must complement your strengths and align on first principles (e.g., remote vs. in-office). Rabois values partners who sharpen his thinking—someone who, over coffee, asks questions that reframe problems. Misalignment on fundamentals can fracture a startup’s DNA once it solidifies.

    Talent: The Moneyball Strategy (14:51)

    Startups can’t outbid Google for obvious talent, so Rabois hunts for “mispriced” individuals—young prodigies with few data points, disruptive personalities big companies reject, or those with unique histories he’s witnessed firsthand. This arbitrage is a startup’s edge.

    Attracting and Assessing Talent (17:20 – 24:02)

    To attract talent, Rabois suggests a compelling mission (e.g., Palantir’s democracy defense) or differentiated cultural values. Assessing strangers is tough—he relies on sharp questions to gauge potential quickly, but admits prior context (e.g., knowing DoorDash’s Tony Xu) gives him an unfair advantage. References? Crucial but tricky—ask the right questions (e.g., “Can they be a world-class founder?” not “Are they a good employee?”).

    Closing Hires: Matchmaking, Not Selling (25:56)

    Rabois closes hires by aligning roles with candidates’ goals, highlighting challenges they’ll conquer, and addressing blockers (a trick from Jack Dorsey). It’s less about hard-selling and more about ensuring fit—anti-selling, as Mike Maples Jr. does at Floodgate, filters out mismatches.

    Thinking Ahead: The 6-Month Edge (28:28)

    Great leaders think 3-6 months ahead, anticipating problems and prepping solutions. Rabois recalls engineers who scaled systems for traffic spikes—those who react “just in time” miss opportunities requiring lead time.

    Hiring Longevity and Talent Monopolies (31:36 – 33:28)

    Rabois interviewed candidates at Square until 500 employees; DoorDash’s Tony Xu went to 2,000. It’s about setting a high bar early. Creating a talent monopoly (e.g., SpaceX for aerospace, OpenAI for AI) is ideal—if not, vertical execution (like Ramp’s engineering intern pipeline) can draw the best.

    Raising Capital: Aim for Lift, Not Runway (35:44)

    Fundraising isn’t about extending runway—it’s about hitting milestones that prove “lift.” Define inflection points (e.g., growth rate, tech breakthrough), calculate the capital needed, and pitch investors on that trajectory. Too much cash can bloat spending without focus.

    Screening Investors and Building Boards (37:40 – 41:21)

    Rabois urges founders to reference-check investors—70% add little value. Look for those who stay out of the way or offer rare expertise. Boards, per Jack Dorsey’s Square playbook, should be visionaries you’d hire but can’t, spotting blind spots to avoid fatal errors.

    Operating: Triage, Edit, and Empower (44:11 – 59:21)

    • Triaging Problems: Startups are chaotic—Rabois likens it to an ER. Focus on high-leverage issues with 10x upside or downside, letting minor colds resolve themselves.
    • Editing, Not Writing: CEOs edit initiatives for a consistent voice (like The Economist), ensuring alignment across products and teams.
    • Transparency: Share data (dashboards, board decks) so everyone decides with the same context.
    • Barrels: Rare individuals who turn concepts into reality—expand their scope to find them (2-3 per 100 employees is healthy).
    • Task-Relevant Maturity: Sample work based on experience—daily for novices, quarterly for veterans.
    • Delegation: High-conviction, high-consequence decisions stay with the CEO; low-conviction, high-consequence ones need data hunts or 70% certainty for speed.

    Measuring Inputs Over Outputs (59:21)

    Rabois flipped from output-obsessed to input-focused. Outputs discourage risk-taking (e.g., 10% success odds); inputs—like quality of thinking—reward tackling hard problems. Jeff Bezos and coach Bill Walsh echo this: perfect the process, and results follow.

    Underrated Metrics: CAC Payback Rules (1:02:58)

    Rabois obsesses over Customer Acquisition Cost (CAC) to payback ratio—it reveals value proposition strength and capital efficiency. Sub-6 months is thrilling, over 12 months is a red flag. It’s physics applied to business: minimizing friction drives growth.

    Closing Thoughts: Sleep and Challenge (1:05:22)

    What should people ponder? Sleep—for health and success—and challenging yourself. Quoting Ben Franklin, Rabois urges us to “write something worth reading or do something worth writing about.”

    Final Note

    Despite the video’s abysmal audio—think muffled voices and static—this interview is a goldmine for startup enthusiasts. Rabois distills decades of experience into actionable frameworks, blending philosophy with practicality. Plug in some headphones, crank the volume, and absorb the wisdom—it’s worth the effort.