May 15, 2025 · 55m · mad
Jeremy Howard on Building 5,000 AI Products with 14 People (Answer AI Deep-Dive)
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this episode of The MAD Podcast, host Matt Turck interviews Jeremy Howard, co-founder of Answer.ai and Fast.ai, about building an Edison-inspired AI R&D lab that leverages open-source models and human-AI collaboration to ship thousands of products with a lean 14-person team. Howard critiques compute scaling hype, refutes near-term AGI claims, and showcases Answer.ai's innovative software stack including Solve-It, ShellSage, and FastHTML.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Matt holds 19.7% of the talking time here. How this is scored →
speaking balance: gold is Matt, purple is the guest (3 minute bins)
Jeremy forcefully criticizes OpenAI's spend-heavy culture, calling the GPT-4.5 release an inevitable debacle where costs far outweighed practical utility.
Hardest push from Matt ▶ 12:32 Challenging Diminishing Returns SkepticismMatt directly challenges Jeremy's skepticism about exponential progress, asking if he is dismissing genuine performance gains as mere psychological perception.
Biggest teaching moment ▶ 23:28 R&D Lab vs. Research Lab DistinctionsJeremy stops Matt to explicitly correct his premise, explaining why Answer.ai functions as an Edison-style R&D lab rather than a traditional academic research lab.
Matt holds his own ▶ 43:53 Mapping Answer.ai's Full Technical PortfolioMatt demonstrates deep domain preparation by reciting Answer.ai's obscure and varied software stack releases across encoders, search tools, and web frameworks.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Matt as informed peer | Guest teaching | Guest disagreement | Matt pushing back | Why |
|---|---|---|---|---|---|---|
| Reflections on ICLR Singapore and Academic vs. Practical AI | 4 | 4 | 3 | 2 | Matt guides the conversation across the model landscape, citing OpenAI's upcoming models, Phi, and Gemma. Jeremy provides practical realities from Answer.ai, dismissing vaporware press releases. | |
| The DeepSeek "Sputnik Moment" and Public Perception Shifts | 4 | 6 | 5 | 3 | Matt prompts Jeremy using Jeremy's own social media posts regarding OpenAI's business model. Jeremy forcefully critiques OpenAI's 4.5 compute spending and reframes public perception surrounding DeepSeek. | |
| Test-Time Compute, Inference Scaling, and Economic Realities | 5 | 6 | 4 | 4 | Matt presses Jeremy on whether raw model improvements contradict his view on diminishing exponential returns. Jeremy educates on inference compute limits and reframes AGI timeline hype as user interface perception tricks. | |
| Jeremy Howard's Early Path: Philosophy, McKinsey, and Kaggle | 2 | 3 | 2 | 1 | Matt prompts Jeremy on his academic background and transition into AI. Jeremy reflects on dropping out of university math and outperforming academics in early Kaggle competitions through self-taught practical experience. | |
| The Origins of Kaggle Inc. and the Creation of Fast.ai | 3 | 4 | 1 | 1 | Matt connects Kaggle to Fast.ai. Jeremy clarifies Fast.ai's underlying R&D cycle, using an analogy to restaurant research labs to show how teaching drives software development. | |
| Introduction to Answer.ai and Edison's R&D Lab Philosophy | 3 | 6 | 3 | 1 | When Matt introduces Answer.ai as an AI research lab, Jeremy immediately corrects the premise, emphasizing that it is an R&D lab modeled after Thomas Edison's Menlo Park laboratory. | |
| Structuring Answer.ai as a Public Benefit Corporation (PBC) | 4 | 3 | 1 | 2 | Matt demonstrates knowledge of Answer.ai's corporate structure and fundraising figures ($10M plus $8M). Jeremy outlines the Public Benefit Corporation charter and internal beta strategy. | |
| High Team Velocity and Evaluating Autonomous AI Agents (Devin) | 4 | 5 | 5 | 4 | Matt asks if future model improvements will fix autonomous agents like Devin. Jeremy strongly rejects fully autonomous handoffs, explaining why vibe-coded software fails unpredictable tasks. | |
| Solve-It: Reimagining AI Workflows via Dialogue Engineering | 3 | 4 | 2 | 2 | Matt asks if Solve-It is strictly a coding tool. Jeremy clarifies that it spans non-coding domains like book writing and business operations through dialogue engineering. | |
| Overcoming LLM Limitations through Agentic Search and R&D Loops | 3 | 4 | 3 | 2 | Matt asks how Solve-It circumvents common LLM issues like hallucinations. Jeremy details grounding mechanisms and notes he doesn't face common user complaints due to his human-in-the-loop workflow. | |
| ShellSage: Bringing Context-Aware AI into the Command-Line Terminal | 2 | 4 | 1 | 1 | Matt transitions to secondary tools. Jeremy details how ShellSage leverages TMUX to feed full terminal context into an LLM session. | |
| Building the FastHTML, Monster UI, and Plash Developer Stack | 5 | 6 | 3 | 2 | Matt lists Answer.ai's tool suite but mispronounces ColBERT, which Jeremy playfully corrects. Jeremy then details Python M-expressions and web stack efficiencies behind FastHTML. | |
| Defining the AI Substrate and Team Architecture | 4 | 4 | 3 | 3 | Matt inquires about product selection criteria among thousands of options. Jeremy explains the underlying substrate concept and non-traditional management systems built into Discord. | |
| Five-Year Outlook and Product Strategy | 3 | 3 | 2 | 1 | Matt asks about long-term team scaling. Jeremy rejects traditional headcount expansion, outlining a 5-year focus on building commercial consumer applications rather than raw model infrastructure. |