How detailed should my first prompt be?

As detailed as you can stand. Every decision you leave out — page names, what each form collects, what happens after someone submits — becomes a correction round later. The prompt on this page is long on purpose; filling in its brackets properly is the single highest-return thing you can do.

What if the first version looks nothing like what I imagined?

That is normal and fixable. Do not rewrite the whole prompt — pick one section, describe the end state you want in plain language, and send that as a single follow-up. Changing one thing at a time is how you steer a build without tangling it.

Can I really build a working app if I have never written code?

Yes, for the kind of app this prompt produces — pages, forms, stored data, a simple admin area. What you actually need is clarity about what the app should do; the builder handles the code. The limit is complexity, not coding: unusual logic, heavy integrations or high-volume systems still need a developer.

Getting Started

Turn your idea into a working MVP

Go from a one-line idea to a working first version, with the right pages and data.

Time: ~30 minutes for the first version Difficulty: Beginner Works with: Base44 / Lovable / v0

When to use this

The very first prompt when you start a new app or site.

Before you start

An account on your chosen builder (Base44, Lovable or v0) — the free tier is enough to see your first version.
Ten minutes of thinking, ideally in a free AI chat: who this is for, what a visitor should be able to do, and the pages you want. Bring that into the brackets below.
Nothing to install, no keys, no payment details.

The prompt

I want to build [ONE-LINE IDEA, e.g., "a booking site for my yoga studio"].
Before building anything, restate in plain English: WHO this is for, WHAT it helps them do, and WHY they'd use it — and ask me up to 3 short questions if anything is unclear.
Then build a first working version with:
- The core pages: [e.g., Home, Services, Book, About, Contact].
- The main thing a user should be able to do: [e.g., see classes and request a booking].
- A clean, mobile-first design that feels [e.g., calm and modern / bold and playful], in [brand colors].
- Placeholder text and images I can replace, and content that's easy for me to edit myself.
Keep it simple for v1 — no advanced features yet. When done, show me the pages you created and tell me the 3 things I should try next.

Already building? Paste this into your project. Starting fresh? Open a free account with a compatible builder below.

Build it on

Start free with Base44 Read Review: Base44

Start free with Lovable Read Review: Lovable

Start free with v0 Read Review: v0 by Vercel

How we make money

What this creates

A working first version of your app with real navigation between pages
The pages you listed, each with sensible placeholder content
A basic data structure behind the scenes (the "objects" your app stores, like Clients or Bookings)
A responsive layout that already works on a phone
A live preview link you can open and click through immediately

Check it worked

Paste the prompt, wait for the build to finish, then confirm these — in plain language, no technical checks needed:

You can open a preview link and click between every page you asked for
Your business name and the words you wrote appear on the home page — not lorem ipsum
It looks reasonable on your phone, not just the desktop preview
Where you asked for a form or a list, something is there (even if it's empty)
Nothing is "coming soon" that you explicitly described in the prompt

Something missing? That's normal — ask for it in one short follow-up message rather than re-running the whole prompt.

Next steps

Make it sound like you

After the first version exists, before showing anyone

Rewrite all the placeholder text on the site in my voice: [DESCRIBE YOUR TONE, e.g. warm and straightforward, no corporate jargon]. Keep the structure and layout exactly as they are. Use these real details: [PASTE YOUR REAL ABOUT TEXT, SERVICES, ANYTHING TRUE].

You'll know it worked when: Every page reads like you wrote it, and no placeholder sentences remain.

Fix the mobile view

After checking the preview on a real phone

Review every page on a phone-sized screen and fix what breaks: text that is too small to read comfortably, buttons that are hard to tap, anything that requires sideways scrolling, and images that overflow. Do not change the desktop layout.

You'll know it worked when: You can use every page one-handed on your phone without pinching or scrolling sideways.

Add the page you forgot

Anytime a missing page becomes obvious

Add a new page called [PAGE NAME] to the site and to the main navigation. It should contain: [DESCRIBE THE SECTIONS, IN ORDER]. Match the existing design exactly — same colors, fonts, spacing and header/footer.

You'll know it worked when: The new page appears in the menu and looks like it was always part of the site.

Watch out for

It will look 70% right, not 100%. That's the normal starting point — the next messages are where it becomes yours. Don't re-run the whole prompt; correct one thing at a time.
Vague brackets produce vague results. "[MY BUSINESS]" left unfilled gets you a generic template. Fill every bracket before pasting.
Don't ask for payments, logins and email in this first prompt. Get the shape right first; each of those has its own prompt on this site and works far better added deliberately.

Platform notes

Works on Base44, Lovable and v0. On Base44 the database and auth are set up for you automatically; on Lovable connect Supabase when it offers; on v0 you'll assemble backend pieces as you go.

Spend fewer credits

Every builder charges you for the work its AI does — so the cheapest habit is thinking before you build. These six rules cut most of the waste, whichever platform you choose.

Plan in a free chat first. Sketch the whole thing in ChatGPT, Claude or Gemini — pages, features, what each form collects, what it should look like. Thinking there is free; thinking inside a builder is billed.
Start from a written prompt, not a sentence. "Make me a website" is the most expensive sentence in AI building. A complete first prompt — like the ones on this site — saves dozens of correction rounds.
Don't be lazy with the details. Every detail you leave out comes back as a correction you pay for. Business name, colors, every page, every form field, what happens after someone submits — put it all in the first prompt.
One change per message afterwards. "Fix the header, and the form, and the colors" produces a tangle that costs more to unpick than it saved.
Stuck? Stop patching. If the same fix fails about three times, don't send a fourth correction — describe the whole section's desired end state in one fresh message instead.
Start free. Upgrade when you need more. Use the free allowance to build and explore your first version. Upgrade when you need more usage or paid features, and check any connected service costs before launch.

The prompts on this page are written to do most of this work for you — that's the point of them.

Read the full guide

Related playbooks

Related prompts

mvp planning scaffolding getting-started

Last reviewed: 2026-07-27