Jordan Tigani, CEO and cofounder of MotherDuck, knows what world class infrastructure looks like. He spent years building Google BigQuery before taking those lessons into the startup world. In this episode, he breaks down why building infrastructure products is fundamentally different from typical SaaS and why founders who don’t understand that difference are in for a painful surprise.

What You'll Learn

There are no shortcuts in infrastructure. You can’t just wire together existing open source components and call it a product. Real infrastructure requires contributing meaningfully to the state of the art, and that takes time, money, and deeper technical investment than most founders expect.

Starting with startups, not enterprises, is often the smarter play. Early stage infrastructure companies should target other startups first because they’re more comfortable with bleeding edge tech, have lower security barriers, and won’t force you to spend three engineers building custom auth instead of your actual product.

Scaling down is the new scaling up. Jordan saw pressure at SingleStore to make databases smaller and more efficient, not just bigger. That insight led to MotherDuck, which is built on DuckDB—a database that can run in a car, scale to massive cloud instances, and challenge the coordination overhead of legacy distributed systems.

Bottoms up engineering cultures win in infrastructure. At BigQuery, engineers close to customer problems could ship fast and independently. Jordan’s recreating that at MotherDuck by removing layers between engineers and customers, because creative problem solving requires understanding business constraints, not just technical ones.

Convincing people you can scale is half the battle. The best proof is customers who look like your next target and can vouch for you. Next best is real data and benchmarks. If you don’t have those yet, lean on implementation support and help prospects test at scale themselves. Early on, sometimes all you have is your word.

Timestamped Highlights

[01:22 ] Why infrastructure takes longer to build than typical SaaS products and why there’s no shallow way to do it

[06:57 ] The MVP dilemma: finding product market fit when enterprises demand reliability from day one

[11:44 ] Lessons from BigQuery and SingleStore—what to carry over from big tech and what to leave behind

[21:21 ] The gap in the market that led to MotherDuck: why distributed databases don’t scale down and why that matters now

[26:10 ] Redefining scale: why 100 users on one giant instance isn’t necessarily better than 100 auto scaling individual instances

[29:08 ] The hierarchy of proof: from customer testimonials to benchmarks to trust me, it’ll work

A Line to Remember

“If you really want to build an infrastructure product, you can’t just string existing components together. You actually have to contribute meaningfully to improving the state of the art.”

Stay Connected

If this breakdown of infrastructure startups resonated with you, subscribe so you don’t miss future episodes. And if you’re building in this space or thinking about it, connect with Jordan on LinkedIn. He’s committed to paying forward the help he got as a founder.