Why an Ex-Googler Bet Everything on an Open-Source Database
Show notes
Jordan Tigani helped create Google BigQuery, then got fired as Chief Product Officer on a Friday morning. He planned to hack on DuckDB to learn Rust. Investors offered to fund it before he'd decided to start a company. That company became MotherDuck
In this episode, we cover:
- The DuckDB Labs partnership: why MotherDuck gave the open-source creators a co-founder share instead of going open-core
- From alpha to paid product: 11 founders, 3 to 4 months to alpha, two years to something people would pay for
- AI on top of the data warehouse: vibe-coded dashboards (Dives), pipelines (Flights), a context layer (Guides), and why business users catch mistakes analysts miss
- Are dashboards dead? Jordan wrote "Big Data Is Dead"; his answer on dashboards is different
- Career advice: why you shouldn't want to work on the query optimizer, and the skill Jordan says matters more
For engineers curious about database and infrastructure companies, open-source business models, and how AI is changing who gets to ask questions of data.
Timestamps:
00:00:00 - Intro
00:00:32 - Fired on a Friday: how MotherDuck accidentally started
00:04:50 - Giving DuckDB Labs a co-founder share of the company
00:07:43 - Why most open-source SaaS products are just "managed"
00:09:31 - Why VCs said yes: Snowflake, DuckDB, and BigQuery credibility
00:10:50 - The 11-person founding team that skipped the wrong designs
00:12:20 - Alpha in 4 months, beta in a year, paid in two
00:15:20 - Vibe-coded BI: Dives, Flights, Guides, and an agent harness
00:20:10 - The questions business users ask that analysts never do
00:24:14 - Are dashboards dead in the age of agents?
00:27:57 - Everybody wants to work on the optimizer (don't)
00:31:23 - The engineer superpower most engineers look down on
00:33:20 - Writing: the one skill Jordan would learn (and still hates)
00:36:05 - Does contributing to DuckDB get you hired at MotherDuck?
00:37:20 - Why a database company leaned into the duck