Professor G Markets$SpaceX Goes Public Tomorrow — Look Out Below
- This post includes paid content that is not available publicly. See the original source.
Brex co-founder and CEO Pedro Franceschi describes a company-wide transformation built on a single conviction: that AI adoption inside an existing company requires refounding its self-identity from scratch, not layering automation onto old processes, and he ends by arguing the CEO, not any team, has to personally drive that refounding.
Franceschi traces his own shift to what he calls "electricity being invented" — the moment reasoning models and coding harnesses crossed from research curiosity into genuinely useful tools, around the GPT-4.5 era in December. He describes going deep personally, giving a self-hosted AI agent read access to his email and Slack, then wanting to grant it write access into Brex's own systems, which Brex's security team initially refused. His solution, later open-sourced as "Crab Trap," proxies every HTTP request an agent makes and uses a separate LLM to judge whether it matches an approved policy; after training on one day of traffic, it auto-approves roughly 98% of requests, which he says was the unlock that got Brex's security team comfortable letting agents operate in production.
He frames company-wide AI adoption in three tiers: engineers who "token-max" inside coding harnesses, average engineers getting a fraction of that productivity, and the rest of the company still interacting with AI in "Google search mode" through chatbots. Brex's bet is building an equivalent harness for non-technical teams, a "virtual employee" reachable on Slack and email that can join meetings and take notes, which let him and a handful of colleagues plan 60 partner dinners for Startup School by talking through Slack, with no one opening a coding tool.
Franceschi's most counterintuitive argument is that AI should tighten founders' discipline, not loosen it. He points to Stripe's original API-only product, Brex's own terminal-only MVP, and Airbnb's single-form booking flow as evidence successful companies compress a problem into one disciplined interaction; he worries AI's ease of building many things tempts founders into skipping that compression rather than finding a smaller way to solve the real problem. This connects to his view on ideas generally: models can now execute almost anything, so the founder's remaining job is judgment, extracting from a customer conversation the "unspoken signal" a customer's own words can't fully capture, since a customer will describe their problem through their own limited framing, not hand over a billion-dollar answer.
Operationally, he describes Brex building a "customer world model" that ingests every touchpoint — dashboard clicks, support tickets, sales calls — to predict what a customer needs next, and redesigning entire processes like KYC from scratch rather than bolting an agent onto the existing flow, which surfaced a new insight: since AI makes compliance checks nearly free, Brex can now run them earlier, on leads rather than signed customers, reshaping who the company targets. On cost, Brex built an internal tool, Magpie, attributing every dollar of token spend to a product, customer or employee, and Franceschi says the data shows most companies, even large, well-funded ones, chronically underspend on tokens relative to what the economics justify, with usage and revenue growth both concentrated in a roughly ten-mile radius around San Francisco and New York.
He closes by arguing the CEO must personally act as "chief AI officer" because only someone with visibility across the whole company can see where old processes should be torn up rather than patched, and that internal resistance to disruptive change, what he calls organizational "antibodies," has to be overcome by deliberately speeding up escalation paths for risk-taking, since waiting for consensus reliably favors keeping the old way.
Chip Huyen, author of Designing Machine Learning Systems and AI Engineering (which the host says was the most popular item on O'Reilly's platform last year), ends up arguing that as AI drives the cost of building software toward zero, the durable work lies in systems design, evaluation, people problems, human-AI interfaces, and the physical world. She has turned her own attention to physical AI, in work the host describes as in stealth.
Systems over skills. Huyen says she turned to system design around 2018–2019 after TensorFlow 2.0 forced her to redo about 80% of a course's tutorials, looking for knowledge that does not churn. Her GitHub notes became a Stanford course and then the first book, criticised at first for having no code. Her view is that narrower skills are easier to automate, so system thinking grows in value.
ML versus AI engineering. ML engineering meant collecting data and training models from scratch; AI engineering starts from a hosted model, so time to market is far faster. Real products mix both: her customer-support example uses classical classifiers to filter off-topic requests and route FAQ questions away from expensive models. She calls prompt writing and context and memory design central skills.
Start simple. She picks the simplest fix for each observed failure, partly so failures can be traced to a component. Prompting goes far, but long prompts with many authors accumulate contradictions; running her own prompt through a model exposed them, and a stray example about New York offices had skewed every research summary. Missing information is a main cause of hallucination, so documents and web search matter, but search is "painfully expensive": prediction-market agents cost her $1–2 per request, and one run hit about 1,000 URLs with only 20 unique. She says tool-use tokens, not reasoning, dominate agent costs. She is sceptical of fine-tuning, which is easy to do but hard to serve, and companies tell her new models outclass workarounds every two to three months; she no longer fine-tunes and uses AI mainly for labelling. Inference and feedback. For token costs, her lever is offloading suitable traffic to smaller models. User feedback, sliced by user, use case and location, reveals where to improve and feeds automated evaluation in production.
Evaluation. She promotes "evaluations-driven development" and asks whether no AI system is worse than one nobody knows is working, noting teams that claim savings they cannot measure. Writing LLM-as-judge guidelines is the hard part; one case study spent 80% of development time on it. Her test is for a human to grade examples using the guideline.
When building is free. Her GitHub-ranking micro-tool drew about 300,000 views in a week and an AI clone the next day; the host adds a Rust re-creation of the leaked Claude Code repo. The host relays METR data that Opus 4.6 handled about 8-hour tasks at 50% success and Mythos was placed at 16 hours, past METR's reliable tests. Huyen concludes software can be copied, so the open question is what to build.
Physical AI. She maps digital agents onto physical ones as perceive-act-feedback loops, but says the physical world lacks documentation: nothing specifies how much force breaks an egg. She splits robot intelligence, following Unitree's CEO, into reasoning, which AI is getting good at, and movement, where he expects arbitrary motion generation within 6 months. Problems that remain. Asked how people can future-proof careers, she names people problems no tool fixes, human-AI interfaces built on legacy tools like terminals, agents that need a laptop open, and an AI-ready world, from better APIs and permissions to city streetlight APIs for delivery robots. On AGI she notes Microsoft has reportedly invoked its contract's AGI clause with OpenAI.
Mukund Jha, co-founder and CEO of Emergent, traces the company from the depressed aftermath of his previous startup's collapse to a nine-month-old business generating $100 million in annualized revenue, arguing throughout that unstructured tinkering and betting on where AI models are heading, not where they currently stand, explain the speed of the outcome.
Jha's prior company, Dunzo, had scaled to roughly a million delivery riders and 10 million monthly orders on $200 million-plus in funding before its 2023 collapse, which he says he initially caused by believing the company was "too big to fail." What followed was six months of what he calls pure, objective-free tinkering, up to twelve hours a day experimenting with new AI models, an escape from disappointment that also convinced him coding itself was about to be disrupted quickly.
Pitching that instinct to VCs went badly at first: roughly a dozen investors rejected the idea of automating software engineering, since AI copilots were the fashionable pitch of the moment and reviewers judged full automation unrealistic. Jha and his co-founder, his twin brother, responded by deliberately building toward an extrapolated, six-months-ahead version of what models would be capable of rather than their current state, for instance ignoring a JSON-output-parsing problem that roughly 20 to 30 other YC companies were separately trying to solve, betting the next model generation would simply fix it.
Lacking a settled product idea, the team spent three months chasing SWE-bench, the hardest available coding benchmark, partly as a way to stop the team from pivoting weekly; becoming the world's top-ranked system on it with four people became the technical base — parallelized test-time compute, cross-agent memory, custom container-snapshotting infrastructure — that the eventual product was built on. Jha says Emergent differentiates from earlier AI website builders by insisting on shipping real, working software with a genuine backend and database rather than front-end "demoware," a bet validated by outperforming competitors on head-to-head prompts.
He closes with advice for founders building from India: a global company is no harder to build than a local one given today's reach, so founders should think global from day one, trust their own intuition over conventional advice, and aim at ambitions ten to a hundred times bigger than their first instinct, since "it's not time to attack the floor, it's time to attack the ceiling."