Build the First Version of Your App With AI

1. 1

   Frame the idea in one sentence

   "[User] can [do one thing] so that [outcome]." If it needs an "and", it's two products.

2. 2

   Turn it into an MVP plan

   Use the prompt below to get scope you can actually build.

3. 3

   Build the screens

   Four maximum. Landing, main workflow, results, and history only if required.

4. 4

   Put it in front of one person

   Say nothing. Watch where they hesitate.

5. 5

   Fix the one thing that broke

   Then repeat. Don't add features between tests.

Help me turn this idea into a focused MVP.

Give me:
1. The single user this serves
2. The one problem it solves
3. The one workflow that must work end to end
4. What is explicitly out of scope for v1
5. The screens required
6. The data that must be stored
7. Where AI is genuinely needed vs. where it's decoration
8. The riskiest assumption
9. How to test whether users find it valuable

Keep the scope small enough to prototype in an AI application builder.

Idea: [DESCRIBE IT]

Build the first version of this app.

Create these screens:
1. Landing page
2. Main workflow screen
3. Results screen
4. Saved items or history — only if the workflow requires it

For each screen, define the empty state, loading state, and error
state. Keep the visual system consistent. Do not add features that
aren't in the MVP plan above.

MVP plan: [PASTE]

• What did they misunderstand?
• Where did they hesitate?
• What did they expect to happen that didn't?
• Where did they stop?
• Would they use it again on Monday?

• Database tables for the records your workflow saves
• Row-level security so users only see their own data
• Storage, if users upload files
• Server-side functions for anything that touches a secret
• Environment variables — never keys in client code
• API integrations, with timeout and failure handling

• One user is clearly defined
• One workflow works end to end without you helping
• Empty, loading, and error states exist on every screen
• Auth works and permissions are enforced server-side
• No secrets in client code
• Someone who isn't you completed the workflow
• You know the one metric that tells you it's working