Speaker B advises founders to build prototypes in a single weekend, abandoning ideas that need longer. Use low-fidelity tools like Typeform or simple forms, sometimes with AI, to test one core feature and get early feedback fast.
Chapters
How do you talk to founders and help them suggest what is the minimum features they need to get them to launch in the weekend and get it out there?
Usually my rule, for example, when I'm building a prototype over the weekend, if I imagine a feature and I cannot build it over the weekend, I don't even build the startup. So that's all the ideas that I've had. I didn't get— I was confident I can build it in a day or a weekend. And if I can't build a core product, especially in the age of AI in a weekend, I usually don't want to build it. So that's, of course, if you're building like a much more complex product for a much more complex problem, that might take a bit longer. But generally for like the base prototype, that forces me to be creative about the ways that I'll get to test the product with users. So sometimes if that's even a form, then I go with the form because I think the product might be much too complex to build. Maybe I can use uForm or one of those form platforms or Typeform to create just a mini prototype of a form. And make it look beautiful. So that constraint forces me to think in terms of one core feature.