Skip to content

By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.

Dalton + MichaelDalton + Michael

How to Build an MVP in the AI Coding Era

Dalton + Michael revisit the classic startup advice around building an MVP and update it for the AI coding era.

Michael SeibelhostDalton Caldwellhost
May 18, 202612mWatch on YouTube

Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.

Great conversations run long. Their best ideas don't have to.

uListen is free on iPhone, iPad, Android, Chrome, and Claude.

See how

Transcript

0:00 – 1:19

Why MVP advice needs updating for the AI coding era

Michael Seibel 0:00 I think for better or for worse, the consistent problem has always been how do you help your customers be more successful? If you had asked me five years ago, "Oh, the price of building features has decreased, that's obviously good," I think I would've probably said yes. And I think that, like, the TLDR of this video is, like-

Dalton Caldwell 0:20 Unclear.

Michael Seibel 0:23 [upbeat music] This is Dalton + Michael, and today we're gonna talk about how to build an MVP in the age of AI. This is interesting topic, 'cause I actually think we have to disagree with our former advice.

Dalton Caldwell 0:37 Yep.

Michael Seibel 0:37 Or there's a different set of constraints now. It used to be the case you had to figure out what's the smallest set of features to build that would create value, because building features was costly. We're now in maybe a different situation. [laughs]

Dalton Caldwell 0:52 [laughs]

Michael Seibel 0:53 What, what environment are we in now? [laughs]

Dalton Caldwell 0:55 I think that's completely right. I think much has been said of how to build an MVP and get first customers, and there's-

Michael Seibel 1:00 Yes

Dalton Caldwell 1:00 ... you know, we've talked about it. There's great content out there. But I think that advice needs updating-

Michael Seibel 1:04 Yes

Dalton Caldwell 1:05 ... to AI tools.

Michael Seibel 1:06 Yes.

Dalton Caldwell 1:06 And I could speak to this myself a little bit-

Michael Seibel 1:08 Mm-hmm

Dalton Caldwell 1:08 ... because I recently built a product and, and launched it. You know, it's called StandardDB if people wanna check it out. But we won't, we won't talk about the specifics, but-

Michael Seibel 1:16 Mm-hmm

Dalton Caldwell 1:17 ... guys, I've gone, I've gone through this. I just built and launched a product.

Michael Seibel 1:19 Yes.

1:19 – 2:20

AI-driven feature creep: when building is too easy

Dalton Caldwell 1:19 And so let me start with what's different. Number one, it is so much easier to build features-

Michael Seibel 1:24 [laughs]

Dalton Caldwell 1:25 ... that for me to launch that, I had to delete 80% of the features that I built in the MVP.

Michael Seibel 1:33 That's, that-

Dalton Caldwell 1:34 [laughs]

Michael Seibel 1:34 ... that is not an old problem. That is a very new problem. [laughs]

Dalton Caldwell 1:37 I built this crazy, huge thing with my co-founder Brian in two weeks, and I'm like, "Oh, this is bad. This is, this is, like, a bunch of crap."

Michael Seibel 1:47 Gotta cut. [laughs]

Dalton Caldwell 1:47 And so I had to, I had to cut.

Michael Seibel 1:49 Yeah.

Dalton Caldwell 1:49 And that feels very different to me-

Michael Seibel 1:51 Yes

Dalton Caldwell 1:51 ... than just trying to build a product.

Michael Seibel 1:54 Yeah.

Dalton Caldwell 1:54 Like, the difficulty of building something prevented you from, from getting into that feature creep.

Michael Seibel 1:57 Yeah. Or that feature creep would take months.

Dalton Caldwell 2:01 Yes.

Michael Seibel 2:02 Whereas you're basically, you got feature creep in two weeks.

Dalton Caldwell 2:04 I got feature creep in two weeks.

Michael Seibel 2:04 [laughs]

Dalton Caldwell 2:04 And so you see people just vibe coding just crap.

Michael Seibel 2:08 Yes.

Dalton Caldwell 2:09 And it's because it's so easy to just keep adding and adding and adding.

Michael Seibel 2:13 Yes.

Dalton Caldwell 2:14 And so I think that you almost have to be more of an editor than you did in the past.

Michael Seibel 2:19 That's a big one.

Dalton Caldwell 2:19 Right?

2:20 – 2:59

The temptation to avoid users and build “everything they’d want”

Michael Seibel 2:20 I might argue it also makes it far more challenging when you're building a product for someone else. 'Cause when you're building a product for yourself, at minimum you can use it throughout the MVP process and see if you're getting value. When you're building a product for someone else and you can build infinite features, your brain can be like, "Well, they would want this feature."

Dalton Caldwell 2:39 Yeah.

Michael Seibel 2:39 "They would want that feature. They would want..." Why would I wanna go to them with something that doesn't have all the features they're gonna want?

Dalton Caldwell 2:44 Right. Why don't I give them all the features they want right in the beginning? [laughs]

Michael Seibel 2:47 Well, and it's addicting-

Dalton Caldwell 2:48 Yeah

Michael Seibel 2:49 ... to write the feature. It's fun to, like, tell Codex.

Dalton Caldwell 2:51 [laughs] Yeah. Yeah.

Michael Seibel 2:52 And so I think what I'm arguing is it's more tempting now than ever-

Dalton Caldwell 2:57 Yes

Michael Seibel 2:57 ... to not talk to users-

Dalton Caldwell 2:59 Yes

2:59 – 4:19

Why building every requested feature is now dangerously possible

Michael Seibel 2:59 ... and to not launch with something small. I wanna extend that. And when you talk to users and they gave you the laundry list of features, in the past you knew you couldn't build all that, so, or at least smart people did, and so your instinct would be, "Let me try to dig deeper. Let me try to figure out what they really need, what's really going on." Now when they hand you a list of features, like, "Hey, can you describe those in more detail?"

Dalton Caldwell 3:21 I mean-

Michael Seibel 3:21 We can literally just give those to- [laughs]

Dalton Caldwell 3:23 Yeah. Let me make an extreme point. You could take notes-

Michael Seibel 3:26 Yes

Dalton Caldwell 3:26 ... with Groena of you talking to a user and feed them to Codex, and Codex will build every feature the user asked for.

Michael Seibel 3:34 Yes.

Dalton Caldwell 3:34 And I'm saying that's really bad. [laughs]

Michael Seibel 3:36 Yeah. [laughs]

Dalton Caldwell 3:37 Like, don't do it.

Michael Seibel 3:38 That's the counterintuitive bit, is it's always been a theorem build, to build every feature a user wants, but now it's an exponential theorem because you can. Like, you actually could do that, and that's really, really, really bad. Unfortunately, I think as a result, knowing yourself about the problem is way more important now. Because, like, if you don't know about the problem and users are telling you features and they're excited and you don't know what the hell's going on, you can get yourself in... Like, you, you, you basically have created a tar pit.

Dalton Caldwell 4:11 Yes.

Michael Seibel 4:12 Like, like, like, where one never maybe have existed, you, you're, you are the tar pit. [laughs]

Dalton Caldwell 4:16 Yeah. And, and again, I'm saying I experience, like, I, I feel this viscerally-

Michael Seibel 4:19 Yes

4:19 – 4:59

Resisting broad complexity: earn features through user pull

Dalton Caldwell 4:19 ... where it's so easy to crank stuff out. And so I think the advice here, founders, is you have to try harder than ever-

Michael Seibel 4:27 Yes

Dalton Caldwell 4:27 ... to resist the temptation of building super complex, broad surface area products. And of course you should add more features to it, but it should be because users are pulling you-

Michael Seibel 4:39 Mm-hmm

Dalton Caldwell 4:39 ... towards building more stuff, I think.

Michael Seibel 4:41 Mm-hmm.

Dalton Caldwell 4:41 And not because Codex can crank it out. [laughs]

Michael Seibel 4:45 Yeah. Well, let's talk about that users bit. So okay, it's easier to build products. I was about to say I can't believe I'm saying this, but of course I can believe I'm saying this. Spamming is easier, too. Spamming always gets easier. [laughs] Like, that's the history. [laughs] So let's talk about that.

4:59 – 5:40

“Talking to users” vs. AI-enabled spam: quality over quantity

Dalton Caldwell 4:59 You know, the old advice is have 100 people that love your product. The old advice is talk to as many users as possible. Again, it's all true.

Michael Seibel 5:06 Yes.

Dalton Caldwell 5:06 We're not saying that's wrong. Here's the problem. It's easier than ever to have your claw spam people-

Michael Seibel 5:13 Yeah

Dalton Caldwell 5:13 ... or you to go buy a bunch of leads online-

Michael Seibel 5:15 Yes, yes

Dalton Caldwell 5:16 ... and spam people.

Michael Seibel 5:17 Yes.

Dalton Caldwell 5:17 And so a lot of founders, their version of talking to users-

Michael Seibel 5:21 It's perverted. [laughs]

Dalton Caldwell 5:22 ... is to, it's to, like, spam.

Michael Seibel 5:24 Yes.

Dalton Caldwell 5:24 And it's easy, and the numbers are big.

Michael Seibel 5:26 Yes.

Dalton Caldwell 5:26 And again, so here's the counterintuitive thing. Don't do it.

Michael Seibel 5:30 Yeah.

Dalton Caldwell 5:30 [laughs] That is noise.

Michael Seibel 5:32 Yes.

Dalton Caldwell 5:33 And a smaller number of high-quality conversations where you really listen-

Michael Seibel 5:38 Yeah

Dalton Caldwell 5:38 ... is much better than spamming 1,000 people.

5:40 – 6:19

Users don’t have the full playbook—go deeper than feature requests

Michael Seibel 5:40 If we wanna go one step deeper, right, if startups were as simple as talk to users, build what they want, so many more startups would be successful. Fundamentally, you have to assume that most of your users want their business or their project to be successful, and they don't exactly know how. So some fundamental part of what you're doing... is 10X harder because you're trying to figure out how to help your customer's business do better, and your customer doesn't have that playbook perfectly. By talking to a smaller number of customers more intimately, it massively increases the chances that you can actually make an impact in their business. And then that spins a flywheel that's not spam, it's word of mouth.

6:19 – 7:37

StandardDB lesson: fewer features made the product click

Dalton Caldwell 6:19 A- again, let me give you my real example for what I did with StandardDB.

Michael Seibel 6:22 Yes.

Dalton Caldwell 6:22 We built a bunch of stuff, and then I set up 12 Zoom calls-

Michael Seibel 6:27 Yes

Dalton Caldwell 6:28 ... with founders that I knew, that I- that are in the- that could be users of it.

Michael Seibel 6:32 Yes.

Dalton Caldwell 6:32 My cofound- founder and I joined, and I- we just asked them. And a lot of people didn't really understand what it was-

Michael Seibel 6:39 Yeah

Dalton Caldwell 6:39 ... because it was too complicated.

Michael Seibel 6:40 Yeah.

Dalton Caldwell 6:41 And my... I tried to explain what it was, and like, "Oh, I don't know."

Michael Seibel 6:44 [laughs]

Dalton Caldwell 6:44 And so we- when we stripped out 80% of the functionality-

Michael Seibel 6:48 Yeah

Dalton Caldwell 6:48 ... they were like, "Yeah, I, w- I'm signing up right now."

Michael Seibel 6:51 There you-

Dalton Caldwell 6:51 Like, someone signed up on the call.

Michael Seibel 6:52 [laughs] There you go.

Dalton Caldwell 6:53 And so-

Michael Seibel 6:53 That's counterintuitive. Less features, more usage. [laughs]

Dalton Caldwell 6:56 Isn't that weird?

Michael Seibel 6:57 Yes.

Dalton Caldwell 6:57 And it's because they didn't- they were, like, overwhelmed-

Michael Seibel 6:59 Yeah

Dalton Caldwell 6:59 ... by too much complexity.

Michael Seibel 7:01 Yes.

Dalton Caldwell 7:02 And my vision, I had this expansive vision of what it could be, but man, like, users don't care about that. They just wanna know how this solves their short-term problems.

Michael Seibel 7:08 No.

Dalton Caldwell 7:09 Right?

Michael Seibel 7:09 No. I think for better or for worse, the consistent problem has always been, how do you help your customers be more successful? And if you had asked me five years ago, "Oh, the price of building features has decreased, that's obviously good," I think I would've probably said yes. And I think that, like, the TLDR of this video is, like-

Dalton Caldwell 7:31 Well-

Michael Seibel 7:32 ... unclear.

Dalton Caldwell 7:33 I was-

Michael Seibel 7:33 [laughs]

Dalton Caldwell 7:34 Look, I think about this a lot.

Michael Seibel 7:35 Yes.

Dalton Caldwell 7:35 So I, I was tweeting about this a little bit, so I don't know if you saw.

Michael Seibel 7:37 Yes.

7:37 – 9:20

GarageBand metaphor: democratized tools don’t increase demand or winners

Dalton Caldwell 7:37 I'll tell you about it. Think about how hard it was to get a record made in the '60s.

Michael Seibel 7:45 Mm.

Dalton Caldwell 7:46 You needed a label deal, you had to pay for studio time, you needed instrumen- you know, it was, like, super expensive. How many people created a radio-quality record in the '60s? Thousands?

Michael Seibel 7:57 Mm-hmm.

Dalton Caldwell 7:59 Now, you buy a Mac-

Michael Seibel 8:00 [laughs]

Dalton Caldwell 8:01 ... and it comes with GarageBand.

Michael Seibel 8:03 Yes.

Dalton Caldwell 8:03 And a lot of number one hits, you can research this, were made-

Michael Seibel 8:06 Built there, yes

Dalton Caldwell 8:06 ... in GarageBand.

Michael Seibel 8:07 Yes.

Dalton Caldwell 8:07 So you're using the same tools-

Michael Seibel 8:09 Yes

Dalton Caldwell 8:09 ... that the greatest people in the world are using.

Michael Seibel 8:11 Yes.

Dalton Caldwell 8:11 Now, how much more demand is there for music than there was in the '60s?

Michael Seibel 8:18 Mm.

Dalton Caldwell 8:18 It's flat.

Michael Seibel 8:19 Mm.

Dalton Caldwell 8:19 Like, how many hours a day can people listen to music?

Michael Seibel 8:22 People are not living more than 24 hours a day. [laughs]

Dalton Caldwell 8:24 And how many people wake up every day being like, "Man, I really wanna hear some songs written by, you know, some guy in Illinois-

Michael Seibel 8:31 That no one's ever heard of [laughs]

Dalton Caldwell 8:31 ... no one's ever heard of. Gee, I really..."

Michael Seibel 8:33 [laughs]

Dalton Caldwell 8:34 Like, like, no one wants that.

Michael Seibel 8:36 Yeah.

Dalton Caldwell 8:36 And so this is my metaphor for a lot of the vibe coding stuff-

Michael Seibel 8:39 Yeah

Dalton Caldwell 8:39 ... which is, in the right hands, it's awesome.

Michael Seibel 8:43 Yes.

Dalton Caldwell 8:43 As a thing to do for fun, I love making songs in GarageBand. I'm not gonna release that. Sorry, folks. But, like, it's fun to make music-

Michael Seibel 8:49 Yes

Dalton Caldwell 8:49 ... but I am under no, uh, delusions-

Michael Seibel 8:51 [laughs]

Dalton Caldwell 8:53 ... that, like, the crap that I make in GarageBand-

Michael Seibel 8:55 Yeah

Dalton Caldwell 8:56 ... is gonna be a number one hit.

Michael Seibel 8:57 It's gonna put you on tour.

Dalton Caldwell 8:58 I don't think so.

Michael Seibel 8:58 [laughs]

Dalton Caldwell 8:59 Well, there's no demand for it.

Michael Seibel 9:00 Exactly.

Dalton Caldwell 9:00 I'm not- I don't have the talent.

Michael Seibel 9:01 Exactly.

Dalton Caldwell 9:01 And so my theory is the democratization of these tools is awesome, and it's gonna allow more young people to be discovered and to, like-

Michael Seibel 9:10 Yes

Dalton Caldwell 9:10 ... break into the industry, hooray.

Michael Seibel 9:12 Yes.

Dalton Caldwell 9:12 But the total, um-

Michael Seibel 9:14 Winners

Dalton Caldwell 9:15 ... number of winners is not obviously gonna go up.

Michael Seibel 9:18 No.

Dalton Caldwell 9:19 Right, man?

9:20 – 10:12

Where AI tools may help most: empowered employees vs. startups

Michael Seibel 9:20 Well, and what's funny about this is that when you're building tools for yourself, um, you know, I would argue that, like, an employee inside of a company is now so much more empowered with these tools. When they have a clear job to do and they know how to do it-

Dalton Caldwell 9:33 Yep

Michael Seibel 9:33 ... and now it's like they don't have to tax the company's resources, they probably get a much higher multiplier effect than the startup.

Dalton Caldwell 9:41 It's true. I mean, it's the, it's like think about how many people are employed, um, making videos for, like, internal training purposes or for whatever-

Michael Seibel 9:50 Yes

Dalton Caldwell 9:50 ... versus people that are making Hollywood blockbusters.

Michael Seibel 9:52 [laughs] Yes, yes.

Dalton Caldwell 9:52 You know? Like, or how many directors are in the world.

Michael Seibel 9:54 Yes, yes.

Dalton Caldwell 9:54 And so probably there's lots and lots of people who use these tools to get their job done-

Michael Seibel 9:58 Yes

Dalton Caldwell 9:58 ... that might not be creating the next Facebook.

Michael Seibel 10:00 Exactly, exactly.

Dalton Caldwell 10:01 [laughs]

Michael Seibel 10:02 So TLDR, building an MVP in the AI world, different. Features, I've always thought features are bad, but now features are cheap. Oof, scary.

10:12 – 11:03

Build-in-public in the AI era: avoid content slop, be idiosyncratic

Dalton Caldwell 10:12 You just have to be picky, and, like, maybe one more thing is a lot of our advice was always to build in public and to publish a lot about what you're doing.

Michael Seibel 10:20 Mm-hmm.

Dalton Caldwell 10:20 And the problem is the claws make it so easy-

Michael Seibel 10:24 Yeah

Dalton Caldwell 10:25 ... to create crap on LinkedIn and X about what you're building, and it's all the same.

Michael Seibel 10:31 Yes.

Dalton Caldwell 10:31 Versus if you take the time to write really unique stuff, you can build a following. And so I j- again, I see a lot of founders just putting out slop versus, like, Arkle, he writes about file systems all the time, Hunter does constantly.

Michael Seibel 10:43 Yes.

Dalton Caldwell 10:44 And he's building a following 'cause it's super idiosyncratic writing about file systems.

Michael Seibel 10:48 Yes.

Dalton Caldwell 10:49 Ironically also, the best content to learn about what the labs are working on is the Twitter accounts of people that work at the labs.

Michael Seibel 10:57 Mm-hmm.

Dalton Caldwell 10:57 And they are definitely not writing all that stuff [laughs] for the LLMs.

Michael Seibel 11:00 [laughs]

Dalton Caldwell 11:01 Do you get what I'm saying?

Michael Seibel 11:02 It's a weird-

Dalton Caldwell 11:02 Like, they're leaking alpha.

11:03 – 12:21

Fake traction loops and the competitive edge of focus and editing

Michael Seibel 11:03 Exactly. It's a weird game. It's basically like it's become easier for a startup to basically look like it's going through a positive feedback loop when it's actually secretly going through a negative feedback loop.

Dalton Caldwell 11:14 Yep.

Michael Seibel 11:14 Spam a bunch of customers, get their usage, they don't like the product, they all churn out, keep doing it, da da da da. But that's an advantage in a weird way. Like, if more of your competition's doing that-

Dalton Caldwell 11:25 Great

Michael Seibel 11:26 ... and you're not, you can figure out how to use these tools in the measured way to actually create value for people. There's tons of advantage to pick up right now. Tons of advantage.

Dalton Caldwell 11:37 And it's almost like the people that are the best at editing or creating white space-

Michael Seibel 11:44 Yeah

Dalton Caldwell 11:44 ... and focusing-

Michael Seibel 11:45 Yes

Dalton Caldwell 11:46 ... I think are, like, really well-positioned when everyone else is doing the opposite.

Michael Seibel 11:51 Yes.

Dalton Caldwell 11:51 Like, that's a way to stand out from the crowd.

Michael Seibel 11:52 Yes.

Dalton Caldwell 11:53 Right?

Michael Seibel 11:53 We have two features that work-

Dalton Caldwell 11:55 [laughs]

Michael Seibel 11:56 [laughs] ... that actually make your business better, uh-

Dalton Caldwell 11:58 Yeah

Michael Seibel 11:58 ... or make your life better, yes, as opposed to 150 that you might be confused initially. Obviously, the thing with 150 features is better. Then when you start using it, you're like, "No, thank you."

Dalton Caldwell 12:08 You got it.

Michael Seibel 12:09 All right. Cheers, Dalton.

Dalton Caldwell 12:10 All right, thanks. [laid-back music]

Episode duration: 12:22

In the uListen app, the transcript lights up word by word as you listen. Get uListen

Transcript of episode rQtrzBcf_Us

Get more out of YouTube videos.

Read along on your phone, search it beside the video, or ask your favorite AI app what was said.