1
10 Comments

Should AI builders ask questions before they start building?

Something I’ve been thinking about while working around AI app builders:

Maybe the best response to

“Build me a booking app”

isn’t immediately generating a booking app.

Maybe it should first ask:

Who is booking?
Who accepts the booking?
Do they pay?
Is there one staff member or ten?
What actually needs to exist in v1?

Those answers can completely change the product.

I’m involved with built.new, so this is obviously something I’m close to, but I think there’s a bigger question here for AI tools in general.

Should an AI builder simply follow instructions as fast as possible?

Or should it occasionally push back and help reduce the scope first?

Personally, I’d rather answer one annoying question upfront than end up with five screens I never needed.

on September 22, 2026
  1. 1

    Interesting approach. What was the hardest part to get right?

  2. 1

    Thanks for writing this up. Bookmarking it for later.

  3. 1

    Interesting take. Would you still recommend this approach to someone starting today?

  4. 1

    Thanks for sharing the numbers, that makes it much easier to follow.

  5. 1

    Solid lesson. Which channel has worked best for you so far?

  6. 1

    Solid lesson. Which channel has worked best for you so far?

  7. 1

    This is useful. How are you finding your first users so far?

  8. 1

    Helpful post. How did you get your first bit of traction?

  9. 1

    Great breakdown. What feedback have you had from early users?

  10. 1

    What made you pick this stack over the alternatives?